Diagnostics Visual Profiler Improvements

Porting over latest changes from https://github.com/Microsoft/VisualProfiler-Unity including:

Adding support for Unity's FrameTimingManager to get more accurate frame times on supported platforms (this also unlocks GPU frame timing for supported platforms).
Optimizations around how strings are formatted and missed frame indicators are rendered (instanced when available).
UX improvements around how the window can be anchored.
Minor tooltip/documentation improvements.

Thank you David and Jerome for the review! I just made the suggested changes.


Live Feeds Stopped

I am subscribed to live feeds for orderbook, candles and user account data. Just observed the data stop coming through.
All websockets are done through the RetryTaskController. No internet drop out at all.
It appears that Binance itself just stopped... Is there anything we could maybe do to subscribe to get a notification in this event?
Here is the end of my log:
[dbug] 08/02/2018 00:28:34 +00:00
DepthWebSocketClient: "{"lastUpdateId":61381760,"bids":[["7784.02000000","0.00027300",[]],["7784.01000000","0.00350000",[]],["7784.00000000","0.00350000",[]],["7783.99000000","0.00300000",[]],["7783.98000000","0.00650000",[]],["7783.97000000","0.00970900",[]],["7783.96000000","0.00650000",[]],["7783.95000000","0.00650000",[]],["7783.94000000","0.00650000",[]],["7783.93000000","0.00650000",[]],["7783.92000000","0.70000000",[]],["7783.91000000","0.10684500",[]],["7783.90000000","0.00350000",[]],["7783.84000000","0.00300000",[]],["7783.82000000","0.00650000",[]],["7783.81000000","0.50900500",[]],["7776.57000000","0.00280000",[]],["7775.17000000","1.13837300",[]],["7774.43000000","0.04803000",[]],["7774.01000000","0.00259000",[]]],"asks":[["7789.90000000","0.18342100",[]],["7790.00000000","0.06768000",[]],["7794.87000000","0.00650000",[]],["7794.88000000","0.88799100",[]],["7794.91000000","2.69621300",[]],["7796.21000000","0.00280000",[]],["7797.24000000","0.00280000",[]],["7800.28000000","0.00280000",[]],["7800.75000000","0.00280000",[]],["7801.77000000","0.00280000",[]],["7809.93000000","0.46100000",[]],["7809.94000000","0.60375000",[]],["7810.00000000","0.22260000",[]],["7812.77000000","0.00280000",[]],["7818.97000000","0.04721300",[]],["7818.98000000","1.13246500",[]],["7819.00000000","9.24307000",[]],["7819.30000000","0.04564300",[]],["7819.32000000","0.01120000",[]],["7822.61000000","0.00378800",[]]]}"
[dbug] 08/02/2018 00:29:10 +00:00
CandlestickWebSocketClient: "{"e":"kline","E":1518049747510,"s":"BTCUSDT","k":{"t":1518049680000,"T":1518049694788,"s":"BTCUSDT","i":"1m","f":14776398,"L":14776497,"o":"7790.00000000","c":"7784.02000000","h":"7794.91000000","l":"7783.81000000","v":"8.15356400","n":100,"x":true,"q":"63515.48081620","V":"6.60431900","Q":"51454.16786924","B":"0"}}"
[dbug] 08/02/2018 00:29:10 +00:00
CandlestickCache (BTCUSDT): Updating candlestick (open time: 08/02/2018 00:28:00).  [thread: 24]
[dbug] 08/02/2018 00:32:11 +00:00
SingleUserDataWebSocketClient.OnKeepAliveTimer: User stream keep alive ("4jmcGH7DngUB0DTpVszE5ZqhKPRUTnvuRvAoNz2TpXtlY2emz4siNpdfRJu0").  [thread: 23]
[dbug] 08/02/2018 00:32:11 +00:00
BinanceHttpClient.RequestAsync: [PUT] "/api/v1/userDataStream?listenKey=4jmcGH7DngUB0DTpVszE5ZqhKPRUTnvuRvAoNz2TpXtlY2emz4siNpdfRJu0"
[dbug] 08/02/2018 00:32:12 +00:00
BinanceHttpClient: "{}"

If this was related to the recent Binance outage (the timing fits), they just added a new API endpoint to check if the API is down for "maintenance".
Link to Official Docs
GET /wapi/v3/systemStatus.html

Response:
{
    "status": 0,              // 0: normal，1：system maintenance
    "msg": "normal"           // normal or system maintenance
}

This together with a watchdog timer would be perfect


Events with previous week start date and this week end date displayed incorrectly

Where did you get the code?

[x] Downloaded from GitHub
[ ] Downloaded from the Microsoft Graph quick start tool
[x] Followed the tutorial from Microsoft Graph tutorials

Describe the bug
If the event starts previous week and ends this week - it will be displayed incorrectly (under the wrong day of week).
To Reproduce
Steps to reproduce the behavior:

Create an event in calendar that starts previous week and ends this week
Go to the Calendar in the menu.

Expected behavior
An event is not displayed or displayed under the day it ends.
Screenshots

Desktop (please complete the following information):

OS: Windows 10 Pro N build 19041
Browser: Chrome
Version: 85

** Suspected cause and proposed solution **
suspected cause:
        private IEnumerable<CalendarViewEvent> GetEventsForDay(System.DayOfWeek day)
        {
            return _events.Where(e => e.Start.DayOfWeek.Equals(day));
        }

proposed solution:
       private IEnumerable<CalendarViewEvent> GetEventsForDay(System.DayOfWeek day)
        {
            return _events.Where(e => ((e.Start.DayOfWeek.Equals(day)) & (e.Start.Date >= _startOfWeek)) | ((e.End.DayOfWeek.Equals(day)) & (e.Start.Date < _startOfWeek)));
        }

Thanks for reporting this! You're right - this is one of the dangers of trying to create a calendar UI yourself :D. I took a pretty simplistic approach. I'll take a look at how this can be improved. Your solution is definitely better, but I'm not sure having the entry show up only on the day it ends is right either (your 9/10 - 9/17 event). Arguably it should span days, but that adds complexity to the UI that's not really the point of the sample.


Devices from zway are not in homekit apps

Hi,
I run zway and homebridge on a Paspberry Pi2. When I start the homebridge everything seems fine but my Smarhome App´s like "Eve" or "myHome" just see the homebridge no zway or any devices from there. I only installed a danalock in zway which works fine from there.
Here´s what I get when I run homebridge:
`pi@raspberrypi ~ $ homebridge
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
Loaded plugin: homebridge-legacy-plugins
Registering accessory 'homebridge-legacy-plugins.AD2USB'
Registering accessory 'homebridge-legacy-plugins.Carwings'
Registering accessory 'homebridge-legacy-plugins.ELKM1'
Registering accessory 'homebridge-legacy-plugins.FileSensor'
Registering accessory 'homebridge-legacy-plugins.GenericRS232Device'
Registering accessory 'homebridge-legacy-plugins.HomeMatic'
Registering accessory 'homebridge-legacy-plugins.HomeMaticThermo'
Registering accessory 'homebridge-legacy-plugins.HomeMaticWindow'
Registering accessory 'homebridge-legacy-plugins.HttpGarageDoorOpener'
Registering accessory 'homebridge-legacy-plugins.HttpHygrometer'
Registering accessory 'homebridge-legacy-plugins.HttpThermometer'
Registering accessory 'homebridge-legacy-plugins.Tesla'
Registering accessory 'homebridge-legacy-plugins.X10'
Registering accessory 'homebridge-legacy-plugins.mpdclient'
Registering platform 'homebridge-legacy-plugins.Domoticz'
Registering platform 'homebridge-legacy-plugins.HomeAssistant'
Registering platform 'homebridge-legacy-plugins.HomeSeer'
Registering platform 'homebridge-legacy-plugins.ISY'
Registering platform 'homebridge-legacy-plugins.LIFx'
Registering platform 'homebridge-legacy-plugins.SmartThings'
Registering platform 'homebridge-legacy-plugins.TelldusLive'
Registering platform 'homebridge-legacy-plugins.ZWayServer'
Loaded plugin: homebridge-zway
Registering accessory 'homebridge-zway.ZWayServer'
Registering platform 'homebridge-zway.ZWayServer'
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

Homebridge is running on port 51826.`
And here´s my json.config:
`{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "",

"accessories": [
],

"platforms": [
    {
    "platform": "ZWayServer",
    "url": "http://<IP_ADDRESS>:8083/",
    "login": "admin",
    "password": "raspberry"
    }
]

}`
Many Thanks
Stephan

What version of ios are you using? If you're using 9.3 beta you must update to the newest version of Homebridge(3.1). I would also suggest uninstall the legacy plugins and installing just the zway plugin which will be more developed if that's the only plugin you are using out of the legacy plugins. Here is the Link to the Github page


az keyvault certificate show returns disabled entry

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az keyvault certificate show
Errors:
Disabled current version is being returned (pretty likely that the same goes for secrets).
To Reproduce:
Have a current version whose state is disabled.
Expected Behavior
Disabled entries should not count as current version.
Environment Summary
Windows-10-10.0.19045-SP0
Python 3.10.10
Installer: MSI

azure-cli 2.46.0 *

Extensions:
account 0.2.5

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional Context
Appending --query "[?attributes.enabled]" seems to return nothing.

Thank you for opening this issue, we will look into it.

It is correct disabled versions will still be returned. Only the private portion of certificate is not returned (through secret portion).


Error: Could not find or load main class pattypan.Main

In OpenJDK 1.8.0_92, I cannot launch the jar:
$ LANG=EN java -jar pattypan.jar
Error: Could not find or load main class pattypan.Main
$ java -version
openjdk version "1.8.0_92"
OpenJDK Runtime Environment (build 1.8.0_92-b14)
OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode)

It's on Ubuntu? I will download VM and take a look at it.

Yes, this was Ubuntu

OK, it looks like OpenJDK 8 do not contains JavaFX equivalent. Please try to install package below:
sudo apt-get install openjfx

I'm closing this one, please reopen if you will have problems in the future.

I've not yet tested because I didn't quickly find openjfx for Fedora
(see also
https://ask.fedoraproject.org/en/question/63037/is-there-openjfx-for-fedora-yet/
) and I didn't have access to the Ubuntu machine.
In any case, it would be good for the README to state the actual
requirements of this software.

In any case, it would be good for the README to state the actual requirements of this software.

Definitely. I started documentation some time ago at project wiki. At some point it can be included to the repo and copied to Commons documentation.

#78 This pull request adds the documentation for the same.


Make st2actions and st2tests packages available on PyPi

My current development workflow is basically code in PyCharm, rsync to my stackstorm host, and test there. (There's probably a better workflow using st2workroom or something that I haven't tried.) But anyway, it'd be nice to be able to write (and run) my tests locally for development. But I can't easily install these dependencies.
Workaround: Build st2tests From Source
git clone https://github.com/StackStorm/st2
cd st2/st2tests
source ~/.virtualenvs/my-awesome-new-pack
python setup.py build
python setup.py install
Issue Building st2actions from source on Mac OS X:
Collecting pyinotify<=0.10,>=0.9.5 (from -r requirements.txt (line 13))
  Downloading pyinotify-0.9.6.tar.gz (60kB)
    100% |████████████████████████████████| 61kB 8.6MB/s
    Complete output from command python setup.py egg_info:
    inotify is not available on macosx-10.10-intel

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/tmp/pip-build-TfxaiK/pyinotify/

Currently you can do that by using a StackStorm development VM (st2workroom).
In any case, we do plan to push individual components to PyPi in the near future. We have started that work when starting to work on the new debian / rpm packages. We are quite close to that at this point (each component has setup.py file, etc.), we just need to polish it and add some automation (StackStorm! :)) around publishing packages to PyPi.

This is a feature I would like, to be able to use ST2-provided Mock objects in my tests. Looks like, as of v3.2.0 and (current) v3.3dev there is no setup.py provided for the st2tests package.
I'm installing Stackstorm packages directly from GitHub, so I do not necessarily need the packages published to PyPI, so my needs would be satisfied by adding the file (and other changes like adding the version to its __init__.py

@StephenWeber Looks like you know best what exactly is needed there.
We’ll be happy to accept PR for that! 👍


[BUG]: Radbolt Chamber module output direction buggy from SW through N

Which Mod?
Rocketry Expanded
Description of the bug/crash
If I set the radbolt chamber module output direction to SW, W, NW, or N, the output does not appear to be facing in the correct direction. There seems to be no way to get the output to point directly upwards.  All other directions work as expected.

Steps To Reproduce
Build a radbolt chamber module. Try to aim it up. Look at it.
Player.log
Player.log

And just as a suggestion, it would be nice if the radbolt module allowed for external power to be supplied. My rocket silo is deep underground and it's not particularly sunny there, and potentially convenient solutions like carved lumen crystals don't seem to work (See pic).  I guess I just don't understand the rationale behind making the module solar power-only, so you just lose all your radbolts every night unless you set up sun lamps (which I guess are the only option besides a shit ton of shine bugs), which don't exactly fit well in a rocket silo.

technically it doesnt require light, it requires sky visibility (as a "fake" solar because modules cannot actually consume power)

Then I'm even more confused

it might be sunlight sky visibility only, it has been a while since I coded that

I see, you don't want to render the vanilla radbolt chamber pointless, since you could just use this one as a no-power-required replacement.  I'll try a rocket pad that's closer to the sky.  I can't think of any better alternative to prevent cheesing if modules really can't require power :(

My plan was to eventually find out how to hack together module power consumption that does work and then swap the module to that.
but I did not have success with that so far (and Im currently preoccupied with another mod)

As a stop-gap until then (maybe when you fix this bug? wink wink), could you add a status to the chamber that indicates when it considers itself powered?  I don't currently see anything like that, so the only way to check it to shoot some radbolts in it and see fi they decay or not.


Revert "Changed UI of Website"

Reverts ridsuteri/Awesome-Chrome-Extensions#464

Production build is having issues with navigation bar due to recent changes. Reverting this. @SujalSamai  Please look into navigation bar functionality


bug: ERR failed to retrieve block from DALC

Summary
using the following versions from this PR preview
results in the chain starting, successfully, but there are issues on retreival of data. the light node is in fact synced, which eliminiates probability that it is due to a lower height synced than the head of the chain.
go mod edit -replace<EMAIL_ADDRESS>go mod edit -replace<EMAIL_ADDRESS>go mod tidy
go mod download

Rollkit versions
<EMAIL_ADDRESS><EMAIL_ADDRESS>Full logs
Can be found here https://app.warp.dev/block/VFftl2wPfAUQJBcayZEbWW
Address of Celestia address of light node
https://explorer-arabica-8.celestia-arabica.com/arabica-8/account/celestia1xcd9hwv76sxmlaydqxj7vkqaj64x7hhfvqwh6e
unfortunately, the transaction view doesn't work

duplicate of #1009

got it! flagging that the versions in this ticket are different and the most recent


STATUS_ENTRYPOINT_NOT_FOUND error under tch 0.18.0

I copied the code from examples/basics.rs and tried to run it on Windows. I have installed CUDA 12.4 on my computer and have set the environments of libtorch. I've downloaded the libtorch 2.5.0 cu124 for windows at https://download.pytorch.org/libtorch/cu124/libtorch-win-shared-with-deps-2.5.0%2Bcu124.zip according to the readme file. The program can be successfully complied when I'm using dependency
[dependencies]
tch = {version = "0.18.0"}

, but it throws the error
error: process didn't exit successfully: `target\debug\yolo_self.exe` (exit code: 0xc0000139, STATUS_ENTRYPOINT_NOT_FOUND)

when I tried to execute cargo run.
Then I tried libtorch 2.5.0 under cu121, cu118 and cpu and they all failed to run under the same error. When I switched to using tch = "0.17.0" and libtorch 2.4.0 cu124 downloaded from https://download.pytorch.org/libtorch/cu124/libtorch-win-shared-with-deps-2.4.0%2Bcu124.zip, the program can be successfully compiled and run. So I think that it might be the problem that tch 0.18.0 cannot support libtorch 2.5.0.

I have found out how it occurred. When I tried to stop executing the exe file through console and directly opened it, it popped out an error window that "Cannot locate the entrypoint _kmpc_masked on F:\libtorch_251_cu124\lib\torch_cpu.dll".

So I used Dependencies to investigate the exe file and found that the libiomp5.dll is wrongly referenced to that in C:\Program Files (x86)\Common Files\Intel\Share Libraries.

It turns out that there is an item "INTEL_DEV_REDIST" in my environment variable, which also provides the libiomp5.dll, but at a lower version that does not contain the function "_kmpc_masked". I renamed the dll file and the newly-compiled program can now be executed.
But it brings a new problem: CUDA and cuDNN cannot be found when I use tch=0.18.1, which works under tch=0.17.0. I checked the exe file with Dependencies again and found that it didn't refer to torch_cuda.dll but only torch_cpu.dll. I don't know if it's related with the new version.

The solution of manually loading the "torch_cuda.dll" by @Anivie and @kylanoneal is useful for me, it now recognizes cuda and cudnn.
@Anivie's solution worked for me on Windows 11:
use std::ffi::CString;
use std::os::raw::c_char;
use winapi::um::libloaderapi::LoadLibraryA;

fn main() {

    let path = CString::new("X:\\path\\to\\torch_cuda.dll").unwrap();

    unsafe {
        LoadLibraryA(path.as_ptr() as *const c_char);
    }

    println!("cuda: {}", tch::Cuda::is_available());
    println!("cudnn: {}", tch::Cuda::cudnn_is_available());
}

_Originally posted by @kylanoneal in https://github.com/LaurentMazare/tch-rs/issues/907#issuecomment-2518111644_


Add connect_timeout method to Telnet struct

First up, thanks for this crate! It's been very helpful.
One thing that would be great to have, to pair with the read_timeout, is a timeout on connect. I'm no TcpStream expert but i assume if they have a separate method for connecting with a timeout then the vanilla method will just sit forever waiting.
The downside of this is it is a straight passthrough to the connect_timeout method, which explicitly takes a SocketAddr which isn't as ergonomic. For example we might have to build an address with something like this now
use std::net::{IpAddr, Ipv4Addr, SocketAddr};
use std::str::FromStr;
let address = SocketAddr::new(IpAddr::V4(Ipv4Addr::from_str(ADDRESS)?), PORT);
let mut telnet = Telnet::connect_timeout(address, 1024, Duration::from_secs(2))?;

I'm open to trying to make this better by adapting that so that the inputs could be more or less the same but i thought i'd see what people thought with the super simple passthrough case first.

Sure thing - added an example (which is a bit verbose, happy to tidy if you have a style preference) and also made the fn take a reference to the address to be in line with the underlying function which was the suggestion of a friend of mine. Although it does now make it different to the normal connect which takes ownership, although of a more trivial object.

I think it would be better to add one more sentence in the first line to describe the intention of the function. For example, Opens a telnet connection to a remote host using a TcpStream with a timeout.

Done! I also added a note about the zero Duration, though this might not be necessary so am happy to remove it if you want. I was also considering something like "if a zero duration is passed, treat as 'infinite duration', fall back to non-timeout connection" but that is probably non-obvious behaviour which might cause issues.


Precision on NativeFlowBench & docker image

I'm also doing research on android native code. I'm currently evaluating existing tools. I tried JuCify on NativeFlowBench.
To make the evaluation process easily reproducible, I packed JuCify into a docker image: https://github.com/am009/JuCify/tree/6897c58_docker and https://hub.docker.com/r/warrenwjk/jucify.
After solving some problems, I finally got it running on NativeFlowBench. I modified some scripts to save the output of running jar and nativediscloser. Here is the result: Jucify-NativeFlowBench-6897c58-2022-6-6.zip. Only 2 cases (native_set_field_from_arg and native_source) can be detected that have flow through native?

The symbolic_expression_usage branch is currently not merged into master, so I guess this functionality is still not useable? ( The symbolic_expression_usage branch in nativediscloser is merged though). In current master branch, this seems to result in a mismatch between JuCify and nativediscloser on .result file format.

in commit 6897c58(recommended in readme), the scripts folder appears to contain a copy of nativediscloser code. and launch_native_disclosurer.sh is executing python3 ./main.py instead of python3 ../nativediscloser/main.py ?

When I run cases from NativeFlowBench, there are plenty of small problems, like

AttributeError: 'NoneType' object has no attribute 'rebased_addr' this is fixed in https://github.com/gaojun0816/nativediscloser/commit/d0dad4438f29b6cf1eefa2eb6226e426d7a78c31#diff-beb8b2c78df610b0316d0fcbd066c83a8e2e420898f3290ec87c4ea9738e867f but not after checkout to old commit (Jucify @ 6897c58 points to nativediscloser @ 1682a22).
TypeError: relocate() takes 1 positional argument but 2 were given This exception is thrown from angr's project.py, It seems to be angr's fault?
No call graph present in Scene when analysing native_pure_direct_customized.apk. it seems to relate to https://github.com/secure-software-engineering/FlowDroid/issues/171 .

Finally, I noticed that, because of latest angr's API change, it seems not an easy task to port nativediscloser to latest Angr?

Hi @am009,
Thank you for reaching out.
First, regarding NativeFlowBench, it is highly dependent on the lists of sources and sinks that you consider for the taint analysis. Second, JuCify, as described in the paper, is not intended to handle purely native leaks yet. Indeed, in its current form, it reconstructs Android API calls in the native code but does not consider purely native functions, we are currently working on a more robust version.

It is indeed not yet usable, we are working on it.
At first, we used a working copy of NativeDiscloser which was still under dev. The latest version is stable. If you use the scripts provided, you will have the same environment used for the paper.

Thanks for the response! I think I'll just use this version (6897c58) for possible future evaluation.
Regarding NativeFlowBench, can I make easy changes to improve results on it? (like adding some sources and sinks). If not or you guys don't know much about it, I guess I'll just stay with current result.

Actually, in order for JuCify to detect a leak, an app would need to call an Android API source whether in bytecode or in native code, same for sinks. If data is leaked in pure native code, e.g., with socket-based calls, it would not work with the current version.
If you want to improve the result, you would have to inject Android API calls in the native call, such as:
jclass telephonyManagerClass = (*env).FindClass("android/telephony/TelephonyManager");
jmethodID getImeiMid = (*env).GetMethodID(telephonyManagerClass, "getDeviceId", "()Ljava/lang/String;");
jstring imei =  (jstring)(*env).CallObjectMethod(telephonyManagerObject, getImeiMid);

I understand now. If JuCify cannot detect __android_log_print as a sink, then it's reasonable that it cannot detect cases like native_leak, native_method_overloading, native_multiple_interactions and native_multiple_libraries. (After reading through NativeFlowBench's source code).
But it's still not clear why native_heap_modify, native_set_field_from_native and native_set_field_from_arg_field cannot be detected. The sinks in these cases are in java side using Log.i or Log.d.
Log.i and Log.d are included in src\main\resources\SourcesSinks.txt, and the sources are TelephonyManager.getDeviceId.

native_heap_modify: Java side passes a Data instance as an argument, and Native side calls getDeviceId and set data.str = imei.
native_set_field_from_arg_field: Native side propergates data between two ComplexData instances' fields.
native_set_field_from_native: Native side set complexData.data = getSystemService(Context.TELEPHONY_SERVICE)).getDeviceId().

Probably JuCify currently does not fully support field access operations? There is only GetObjcetField, no SetObjectField in procedures.py @ 1682a2. In lateset procedures.py, the SetField class only does some prints.

Thank you so much for the response.


Document recommended usage of .toObject()

Query.toObject() expects as first argument the prototype for the newly-created object. I'm pretty proficient in JavaScript, but prototypes have never become second nature to me.
Usually, what I want is just a plain object, as if I had created it via { ... }. It would be great if the documentation gave an example of this most likely case. That way, I wouldn't have to wonder each time: Do I pass Object? Object.prototype? {}? null? (No, probably not null.)

I've added additional documentation and a minor API update to make this easier.
Fixed in aebf92701cec30e6fdf2016709d6f75b74eaad8d
Published as<EMAIL_ADDRESS>

Thanks!


ffmpeg is not installed via installer script

Are You on the Latest version?
You did a git pull and are running the latest version/build?
Y
Please describe the bug
Installer script (Windows_Install_Update.bat) does not install ffmpeg resulting in transcribe/ summarize errors.
Is the bug reproducable reliably?
Yes
Steps to to reproduce the issue
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

What was the expected behavior?
A clear and concise description of what you expected to happen, if there was no bug.
Screenshots

Desktop (please complete the following information):

OS: [Windows]
Browser [Firefox]
Date you performed the last git pull: Today

Any Additional context
Please add any other context about the problem here. Thank you!

Thanks for filing the issue, I've resolved this in the latest update.
Problem was that ffmpeg was downloaded but not placed into the 'Bin' folder.


Add queries for janet-lang

Adds queries for working with https://janet-lang.org.
Nvim uses the janet_simple parser by default, hence the directory name.

Thanks again for the pr. The query lgtm. I'll add it to the readme


Cross validations

Opening a pull request to organize the discussion to solve https://github.com/JuliaEarth/GeoStats.jl/issues/128

@juliohm, about your initial points, I think it's more a difference about how the problems deal with CV. Because I ran a test with CrossValidation() and it's doing what other softwares do in kriging cross validation
Just to organize my thoughts, check if it makes sense: in LearningProblem there's all the workflow of dividing into training and tests sets, fit to features in the training set and predict something in the test set. In the EstimationProblems (OK, SK, UK, IDW...) we'll almost always have the hard data simultaneously as training and test set and an estimation domain with unknown information. All the geostats book I know just consider a k-fold CV in these cases using all the samples (usually a leave-one-out or some kind of leave-ball-out for close samples of same drillhole). It's a drawback, people question CV usefulness in these cases, but I don't know if there's some other way to deal with it. It's more an optional tool to help tuning parameters (search, variogram, etc) or select best methods, with no guarantee that these parameters are the best in the end.
In that sense, the code do that job and return the expected MSE after error(solver, EstimationProblem, Validation(n)) for CrossValidation, BlockCrossValidation, LeaveBallOut and WeightedCrossValidation as they only deal with dataset/training set. I'll add specific Travis tests if you think that approach is okay
DensityRatioValidation seems to deal also with the estimation domain/test set, then adaptations would be necessary. But not sure if it'd be useful for EstimationProblem where we are estimating :Z using :Z (plus spatial coordinates), maybe it'd be better to let it available only for LearningProblems as it is right now. What do you think?

Thank you @rmcaixeta for the PR. I will try to review it over the weekend.
I don't know if I followed your comment about using all samples, but cross-validatory procedures require us to hide (or subset) samples in order to achieve an estimate of the error. I've submitted a paper last month to the Machine Learning journal on the CV methods implemented here, and I wish I could share it with you already. It should come out in the following months :pray:
If other software out there use all the samples (the hard data) in every fold, may I ask how they compare the obtained results of the estimator with the ground truth? We can also try to setup a meeting to discuss this if it is too hard to explain in raw text on GitHub. Alternatively, if you are on the Zulip forum, we could try to write down some LaTeX there to make things more precise.

Nice about the paper, I'll read it after published
About "all samples", I only mean by not dividing samples into training and test set, but considering everything as training set (where we know the ground truth). The rest remain the same (hiding one fold, and use the others to estimate the hidden one)

I think I get it. You are saying that other implementations will use all the hard data as training set as usual, but then they will try to estimate the entire domain containing all locations even when they are not part of the hard data locations. Is that it? So they post-process the results to compute losses for a subset of the domain as I understand it. Either way, I think we would need to modify the code in the PR to either (1) create sub-problems with sub-domains (preferred option for performance), or (2) evaluate losses only on hard data locations in the hidden fold (preferred for generality given that some solvers may not work with any kind of domain, and may require regular grid domains for example).
Please let me know if it makes sense. It would be awesome to support both EstimationProblem and LearningProblem in these methods.

Isn't this already creating a sub-problem with subdomains?
probcall = getfield(Main, nameof(probtype))
thirdarg = EP ? Tuple(ovars) : task(problem
...
subproblem = probcall(train, hold, thirdarg)

The original train and hold variables before the PR were juts subsets of the data object, not  the domain object.
To instantiate a learning problem, we use two data objects: train data and test data.
In the case of CV:

train data = remaining folds from original data
test data = hidden fold from original data.

To instantiate an estimation problem, we use a data object and a domain object.
In the case of CV:

data object = remaining folds from original data
domain object = locations from original domain where the data from the hidden fold is found.

So although a data object has an underlying domain, and things may work if you pass it as the second argument to the EstimationProblem constructor, it is expecting a domain object. This is related to that discussion we had some time ago about instantiating estimation problems with two data objects. I think we should add an assertion in the problem constructors: https://github.com/JuliaEarth/GeoStats.jl/issues/131
Before we address this issue, we need to consider refactoring the various CV methods into a single implementation with the only difference being the method for creating folds: https://github.com/JuliaEarth/GeoStats.jl/issues/132

Ah ok, got it
I was assuming everything before was ok
I'll close this for now then, let it rest for some time, the issue is getting big for the weekend


Raspbee addin board prevents boot

Home Assistant release with the issue:
0.83.2
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Description of problem:
Hass.io will not boot when the card is installed into the Raspberry. It enters first stage and scans for USB devices, then just output garbage (looks like it is serial data from the addincard as it blinks in same pace as garbage is produced. Cannot prevent it going into this state. When the card is removed the boot works and completes flawlessly. Rasbian and others boot without issues.
https://www.dresden-elektronik.de/funktechnik/solutions/wireless-light-control/raspbee/?L=1&cHash=c9c902ccdb43164696acccf81b62b2bd

This was solved after some tinkering with the firmware on the device. When updated via another device it worked and is now stable. Perhaps an addition to the documentation?


PERL-1129 Apply TLS options from URI

Prior to this commit, TLS options were parsed, but not applied to the
client.  This commit sets IO::Socket::SSL options based on tls options
on the URI.

Coverage decreased (-0.2%) to 73.965% when pulling 3e1db16748434c2f951d3acfc4aae528fc07d6af on PERL-1129-tls-options into e597b621e78f70777e5aed20f8cc4c31f30bf3df on master.


Meta Issue: metatensor atomsitic models integration with simulation engines

This is a meta-issue to serve as a list of the different integrations between metatensor atomistic models and simulation engines. Any longer discussion should be split into a separate issue and linked back here.
Finished integrations

[x] Energy calculator for ASE (in this repo)
[x] Energy calculator for i-PI (https://github.com/i-pi/i-pi/tree/master/examples/clients/metatensor)

Current prototype integrations

[ ] Energy calculation in LAMMPS: https://github.com/lammps/lammps/pull/4163
[ ] Collective variable calculation in PLUMED: https://github.com/plumed/plumed2/pull/1082

Next integrations/Improvements

[ ] GROMACS, using https://gitlab.com/gromacs/gromacs/-/issues/5039
[ ] Bindings to the kokkos version of LAMMPS
[ ] Computing more than energies in LAMMPS

Desired integrations

[ ] OpenMM, maybe using https://github.com/openmm/openmm-torch
[ ] Tinker-HP already have a very nice API, we could maybe link to it (although it seems to go through Python): https://github.com/TinkerTools/tinker-hp/blob/master/GPU/Deep-HP.md
[ ] CP2K: we need to look into how we can do this

CP2K: we need to look into how we can do this

FORTRAAAAAN ❤
Cool, we might also want to add espresso since they seemed interested.


fixed documents

Hello @trishitchar
Thanks for your contribution.
Let's connect ->
GitHub -> @Suryansh1720001 (Follow)
LinkedIn -> https://www.linkedin.com/in/suryanshprajapati17


feat(web): optimize the state of app

optimize the state of app when I control app to start or restarting or stop.
Before

After

the "phase" field can only be used by backend, try another method:
Pause the application and poll the backend api to request the app state

add "cursor-pointer" to the icon, don't add to CopyText directly

This PR is about app state

Done


Add support for 'msg' and 'block'

Added support for special commands like 'msg' and
'block'. Return a struct containing all the
required data.
Fixes issue #7

@raineorshine please have a look.

@raineorshine I have updated my PR. Please have a look.

block.blockhash is giving the following error:
> block.blockhash
Error compiling Solidity:

1  pragma solidity ^0.4.19;
2  contract ReplContainer {
3    function Main() constant returns (function (uint256) view returns (bytes32)) {
4
5      return block.blockhash;
6    }
7  }

  :3:37: TypeError: Internal or recursive type is not allowed for public or external functions.
  function Main() constant returns (function (uint256) view returns (bytes32)) {
                                    ^----------------------------------------^
 :3:37: TypeError: Internal or recursive type is not allowed for public or external functions.
  function Main() constant returns (function (uint256) view returns (bytes32)) {
                                    ^----------------------------------------^

Error compiling Solidity

Thanks! I'll take a look. I can see now that block.blockhash has been deprecated, so you can ignore that one.

@raineorshine I will be updating my PR ASAP.

@raineorshine I have tried to address all of your suggestions, please have a look.

@raineorshine I have done the required changes. I have also added tests. Please have a look.
If I remove .toString from there, then its throwing error.

@raineorshine I was wrong about the result thing, there was no need for .toString as result is already an array, I ignored the fact that the typeof command returns object for arrays too!
I have removed the local variable returnType and have used the inline declarations in both places.
Please have a look.

Thank you!


Add GitHub Actions workflow for publishing Python distributions to PyPI and TestPyPI

In this pull request, I have added a new GitHub Actions workflow that automates the building and publishing of Python distributions to PyPI and TestPyPI. This workflow is triggered on push to the main branch, pull requests targeting the main branch, and manual workflow dispatches. (https://packaging.python.org/en/latest/guides/using-testpypi/)
Here is a brief overview of the steps included in the build-n-publish job:
Checkout the repository using the actions/checkout@v2 action with the main branch as the reference.
Set up Python 3.10 using the actions/setup-python@v2 action.
Install the necessary dependencies, including pip and build.
Run linting using flake8, with some exceptions for specific rules (E501 and E722).
Build the binary wheel and source tarball using python -m build.
Publish the distribution to TestPyPI using the pypa/gh-action-pypi-publish@master action, with the package_glob set to include both wheel and tar.gz files.
By implementing this workflow, we ensure that the Python distributions are automatically published to PyPI and TestPyPI when changes are pushed to the main branch or merged via a pull request. This automation will save time and streamline the release process.
Please review the changes, and let me know if you have any questions or suggestions for improvements.

You have register here:  https://packaging.python.org/en/latest/guides/using-testpypi/

Hi Tuhin,
thanks! So far, I've done the PyPI stuff manually... I also already have an account on Test-PyPI, so I guess I don't have to create a new account for it, or do I?
Best,
Ralph

No, you don’t have to. Did you upload your distribution to testpypi?
maybe this will be of some help : https://dev.to/arnu515/create-a-pypi-pip-package-test-it-and-publish-it-using-github-actions-part-1-3cp8


[Document view] : Need to correctly handle ObjectID-like data when specified in nested fields

Courtesy @Danlock for pointing this out. Pasting comment below:
Prior discussion here
Related to this issue, nested objectId are not set as object ids properly, in the case of:
{
  "_id": "5aa0150e1430142dda49b551",
  "createdAt": "2018-03-07T16:36:30.436Z",
  "data": {
    "Quasi": "8590406b-67fa-4e08-819d-2860f5fdca79"
  },
  "name": "g6d-car",
  "sensors": [
    {
      "_id": "5adf3b43194dd500010542ea",
      "createdAt": "2018-04-24T14:12:19.693Z",
      "type": "camera"
    }
  ],
  "type": "car",
  "updatedAt": "2018-04-24T14:12:19.693Z"
}

If I make any changes the inner sensor ids will be overwritten with "5adf3b43194dd500010542ea" instead of ObjectId("5adf3b43194dd500010542ea").
I can make another issue if you want, but this seems relevant.

@PrashanthCorp  Thanks for looking out, but that much info is fine. Mostly autogenerated.
I also want to stress that the key, "_id" doesn't really matter, the objectid value ObjectId("5adf3b43194dd500010542ea") is being overwritten and thats the problem, even if the keys isn't "_id".
For example a nested field like so
{
  "_id": "5aa0150e1430142dda49b551",
  "createdAt": "2018-03-07T16:36:30.436Z",
  "data": {
    "Quasi": "8590406b-67fa-4e08-819d-2860f5fdca79"
  },
  "name": "g6d-car",
  "sensors": [
    {
      "_id": "5adf3b43194dd500010542ea",
      "createdAt": "2018-04-24T14:12:19.693Z",
     "foreignIDs": ["5adf3b43194dd500010542ea","5adf3b43194dd500010542ea"]
      "type": "camera"
    }
  ],
  "type": "car",
  "updatedAt": "2018-04-24T14:12:19.693Z"
}

They would also need to be persisted as ObjectId("5adf3b43194dd500010542ea") instead of "5adf3b43194dd500010542ea" to avoid corruption.
Thanks a lot for your work, for reading data this plugin is very convenient to use.

I see the issue. That means this issue probably also applies to ISODate() and other mongoDB types too.
If you guys are married to strict JSON output then you could peek into every value for certain prefixes then stringify the whole thing
ISODate("2018-04-24T14:12:19.693Z") -> "ISODate("2018-04-24T14:12:19.693Z")"

I'm just come here after spending the day figuring out why my back-end was suddenly broken and all sorts of things in my app (commenting, up-voting etc.) were no longer working. It's because I tried out the extension yesterday and opened the document with cosmos DB - all of the object ID's in my docs were turned to literal strings, and my MongoDB/mongoose operations were no longer finding the docs.
Lucky I was still in development, but if I wasn't, using Cosmos DB would have completely broken my MongoDB database and app. Serious stuff! Is this a recent issue and I just got unlucky? Seems like it was only posted today (and @danlock even commented while I was typing this out).

The result JSON has always been this way as far as we know, even in the original mongo extension that later became this extension.  However, I think the update functionality is newer, but still at least several months old without any comments.
Sorry for the inconvenience, and for letting us know about the issue and the seriousness of it. We were not aware of the possibility of data loss and will definitely be looking into how to fix this.

I have a fix for the issue. See above PR.
For test, I tried the following document:
{
  "_id": {
    "$oid": "5abeb30758236b43548ba89a"
  },
  "relatedTo": [
    {
      "$oid": "5a8ca0b0918a2f3c14611736"
    },
    {
      "$oid": "5abeb30758236b43548ba89c"
    }
  ],
  "createdAt": {
    "$date": "2018-04-24T14:12:19.693Z"
  },
  "sampleTime": {
    "$timestamp": {
      "t": 0,
      "i": 0
    }
  },
  "parent": {
    "$undefined": true
  },
  "sampleMinKey": {
    "$minKey": 1
  },
  "sampleMaxKey": {
    "$maxKey": 1
  },
  "entree": {
    "name ": "sushi",
    "base": "rice",
    "grainsOfRiceUsed": {
      "$numberLong": "9223372036854775807"
    },
    "weightInGrams": {
      "$numberDecimal": "80.321"
    }
  }
}

Let me know if there's any major cases I'm missing.
Let us know if you'd like a pre-rel vsix. That could help you work on your databases.

there is also a UUID() constructor, and undefined is deprecated so it's probably unnecessary to test for.
Also should probably test for arrays of these values. Other than that looks good enough for me.

I have a basic test for arrays under the relatedTo property.
From my understanding, UUID is part of the binary data type, of sub-type 3 or 4 here and in the spec - under non-terminals.
For testing that the constructed UUID remains consistent, I used the mongo shell to create a UUID(with a 32 digit hex seed), insert that in a document, and verify that the uuid property (24 chars, different from the 32 digit seed) is consistent across out extension and the shell. Run a few updates on the doc in the extension, and the uuid remains unchanged.
For basis, I used the seed from the [mongo docs] (https://docs.mongodb.com/v3.2/reference/method/UUID/). The generated UUID matches the example through the updates.
Hope this helps!

Just wondering if this has been fixed and merged yet/if the plugin is safe to use?

The fix has been merged.
I've used it and nothing appears to be on fire yet.
One thing to keep in mind is that it updates a document by overwriting it, so you have to be careful not to to overwrite other changes.


Mark jsxFactorySymbol as referenced for noUnusedLocals even in verbatimModuleSyntax

Fixes #59117
markJsxAliasReferenced itself checks canCollectSymbolAccessibilityInfo before marking the symbol as referenced for elision purposes (which is not necessary in verbatimModuleSyntax), but marks the symbol as isReferenced for unused locals checking purposes beforehand. That needs to happen unconditionally, but markLinkedReferences bails immediately if canCollectSymbolAccessibilityInfo is false.
I re-read all the changes in https://github.com/microsoft/TypeScript/pull/58366 and tried and failed to break other features in combination with verbatimModuleSyntax.

@typescript-bot cherry-pick to release-5.5

I think this is okay, though it does break the abstraction of markLinkedReferences...

Yeah, personally, if we think the isReferenced setting behavior is needed independently of the .referenced setting behavior (because it's used for errors and not emit), we should probably pull it out of the whole markLinkedReferences tree of functions and just do it inline.

(That and all of these functions could be moved inside of markLinkedReferences to not be directly callable)

That had measurably worse performance last I tried, since they all become closures :(


Create LICENSE

Awesome, thank you so much for your work on this!!!
Br,
Shane Hicks
On Tue, May 3, 2022, 8:48 AM T.FUJIKI @.***> wrote:

Merged #1
https://github.com/t-fujiki/com.takaaki.urcap.eipmonitor/pull/1 into
master.
—
Reply to this email directly, view it on GitHub
https://github.com/t-fujiki/com.takaaki.urcap.eipmonitor/pull/1#event-6541363193,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARLO7JBWV4EYXTWHEPAZ7NDVIE4CBANCNFSM4UV6SG3A
.
You are receiving this because you are subscribed to this thread.Message
ID: <t-fujiki/com.takaaki.urcap.eipmonitor/pull/1/issue_event/6541363193@
github.com>


t5 with sdpa is slower than PyTorch eager, even though math path benchmarked alone is faster

System Info
/

Who can help?
No response
Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[X] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
It feels like we have some overhead from the self.orig_layer in BetterTransformer implementation. We are not seeing any speedup although using https://github.com/fxmarty/efficient-attention-benchmark/blob/main/benchmark.py we do see it.
Expected behavior
At least on par

Among others, looks to be due to the overhead of getattr. I will refactor to remove it.

Closed with https://github.com/huggingface/optimum/pull/934


Regression issue, SIOPV2 and OIDC4VP failed

this issue in independant of the changes I have done thsi week end on with https://github.com/TalaoDAO/AltMe/issues/1955
that evolution is a breaking change for the tests


Refactor store frame information.

This PR refactors the store frame information to eliminate the copying of
data out from CompiledModule.
It also moves the population of a BTreeMap out of the frame information and
into CompiledModule where it is only ever calculated once rather than at
every new module instantiation into a Store. The map is also lazy-initialized
so the cost of populating the map is incurred only when a trap occurs.
This should help improve instantiation time of modules with a large number of
functions and functions with lots of instructions.

Requesting re-review for the new commit.


Issue and Pull request templates

Added Issue and Pull request templates.[Please do enable the Issue tab on the repository :) ]

@vishalda Sorry for not getting back to you at first, this is appreciated!


What is the minimum radius?

Hi,

What is the minimum  radius one can set
What is the measurement, your example states 3000, does this stand for 3000 meters ?

The minimum can be set low but both Android and iOS state that a minimum of around 100-200 meters is needed for decent accuracy. As for the measurement, yes 3000 is 3000 meters.


Generating TFVars shouldn't generate blocks

Only dictionaries are generated

Codecov Report

Merging #101 into master will increase coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #101      +/-   ##
==========================================
+ Coverage   56.61%   56.67%   +0.06%
==========================================
  Files          62       62
  Lines        4753     4753
==========================================
+ Hits         2691     2694       +3
+ Misses       1876     1872       -4
- Partials      186      187       +1

Impacted Files
Coverage Δ

hcl/utilities.go
79.35% <100%> (ø)
:arrow_up:

hcl/hcl.go
49.09% <0%> (+5.45%)
:arrow_up:

Continue to review full report at Codecov.

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


Allow parameterizing svg font ID in font-source-declaration

Bourbon version
4.2.7
Background
I'm using the following snippet:
@include font-face($font-family: 'Open Sans',
                   $file-path: 'opensans/OpenSans-#{$variant-name}-webfont',
                   $asset-pipeline: true,
                   $file-formats: eot woff ttf svg);

The above snippet leads to a couple of problems -

bad URI(is not URI?) exception in font-source-declaration (See #686 and #195)
users are forced to use an SVG ID ($font-family) that's not configurable. I have an SVG that uses a font id that's not the same as $font-family . It is currently hardcoded to "#{$file-path}.svg##{$font-family}"

I'm happy to submit a PR that allows font-source-declaration to accept an (optional) $svg-id parameter, that falls back to using $font-family

Hi @ketan! Feel free to submit a PR for that.

I’m going to close this as SVG font support in browsers has not been consistent or seen traction. In fact, Chrome has removed support for SVG fonts.


Add fake Span and SpanBuilder to simplify testing.

/cc @zhangkun83 @carl-mastrangelo

Have you considered WannaBeSpan or PoserSpan?

Codecov Report

Merging #410 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #410   +/-   ##
=========================================
  Coverage     89.97%   89.97%
  Complexity      583      583
=========================================
  Files            98       98
  Lines          2034     2034
  Branches        210      210
=========================================
  Hits           1830     1830
  Misses          150      150
  Partials         54       54

Continue to review full report at Codecov.

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

Does this PR replace #371?

Correct @sebright

Yeah mocks are a pain (you can use powermock to mock callsite of a final
method, but yeah...) if mock is desired as opposed to an in-memory test
tracing component, likely you may need to unfinal a lot perhaps using a
base type with a package private ctor to seal the class within its package
instead of final.
On 6 Jul 2017 01:43, "Carl Mastrangelo"<EMAIL_ADDRESS>wrote:

@carl-mastrangelo commented on this pull request.
In testing/src/main/java/io/opencensus/testing/trace/MockableSpan.java
https://github.com/census-instrumentation/opencensus-java/pull/410#discussion_r125711054
:

  // Here can verify options set when build the Span:

  // verify(spySpanBuilder).setRecordEvents(eq(true));

  // Here can verify events recorded to the Span:

  // verify(spySpan).addAnnotation(eq(Annotation.fromDescription("My annotation text")));

  // Here can verify the end of the Span:

  // verify(spySpan).end(EndSpanOptions.builder().setStatus(Status.OK).build());

}

}

}

*/
+@VisibleForTesting
+public class MockableSpan extends Span {

FYI, all final methods cannot be mocked, and iirc mockito won't even
complain about this. Span exposes
addAnnotation()
getContext()
getOptions()
and()
Will users want to mock these methods?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/census-instrumentation/opencensus-java/pull/410#pullrequestreview-48127372,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD61xgFEYwA8Rp0ZAqstrgX9J2ApcSyks5sK8tPgaJpZM4OMxrx
.

Friendly ping.
Should we merge this PR?

@bogdandrutu Is this PR still needed?

Closing for now, since this PR isn't active.  I opened an issue instead: #1195


Removed calls to AP deprecated in openssl 1.1

In openssl 1.1, there is no need to initialize the library.  It is automatically done when first used.  This patch allows to compile openvswitch against openssl 1.1.0 with deprecated API disabled.
Signed-off-by: Eneas U de Queiroz<EMAIL_ADDRESS>

Thanks for the patch.
Just above the code that you commented out is a call to CRYPTO_malloc_init() inside #ifdef _WIN32.  Is this now unnecessary too with OpenSSL 1.1+, or is it still needed?
Thanks,
Ben.

The call has changed to OPENSSL_malloc_init.  I suspect that it is not needed anymore, but I can't tell you for sure.  It may be worth investigating.
I'm not very familiar with Windows programming, but reading INSTALL.W32 in openssl-1.0.2, the call is a workaround for compiling applications that don't use multi-threaded DLL.  There is no such warning in 1.1.0.
Both functions (1.0 and 1.1) have a very similar definitions.  The detail that makes me suspect it is not needed--besides the removal of it's mention in the NOTES.WIN file--is that in openssl 1.0.2 crypto/dh/dhtest.c, it was called within #ifdef OPENSSL_SYS_WIN32, and it is gone in 1.1.0 test/dhtest.c.  While there is no clear definition, I will change the commit to include the call only with Openssl  < 1.1.0.

Thanks, I applied the new patch to master.


Phonegap Build support

is planned in the future the support to the PhoneGap build system ?

Afaik it already does
----- Reply message -----
From: "Medioman92"<EMAIL_ADDRESS>To: "chariotsolutions/phonegap-nfc"<EMAIL_ADDRESS>Subject: [phonegap-nfc] Phonegap Build support (#165)
Date: Tue, Jan 20, 2015 17:57
is planned in the future the support to the PhoneGap build system ?
—
Reply to this email directly or view it on GitHubhttps://github.com/chariotsolutions/phonegap-nfc/issues/165.

This plug is on PhoneGap Build https://build.phonegap.com/plugins/1058
FWIW you can now add any plugin from the cordova plugin repo to your phonegap build project  http://phonegap.com/blog/2014/12/09/phonegap-build-new-features/


Qt as a application container

Once the Electron version is complete, say 1.0.0, try to accomplish the same with Qt.
http://www.qt.io/developers/

https://gitlab.com/paazmaya/keirakutaiso


chore support statement to show views from table

Proposed changes
Issue Number: close #xxx
MySQL [test]> show views;
+----------------+
| Tables_in_test |
+----------------+
| t1_view        |
| t2_view        |
+----------------+
2 rows in set (0.00 sec)

MySQL [test]> show views like '%t1%';
+----------------+
| Tables_in_test |
+----------------+
| t1_view        |
+----------------+
1 row in set (0.01 sec)

MySQL [test]> show views where create_time > '2024-03-18';
+----------------+
| Tables_in_test |
+----------------+
| t2_view        |
+----------------+
1 row in set (0.02 sec)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run p0

run p0

run buildall

run buildall

run buildall

run external


Update Baltic countries holidays, add l10n support

Proposed change

Estonia, Latvia, Lithuania:

update holiday names and relevance periods
migrate Estonia and Latvia to holiday_groups
add l10n support (official language + en_US, uk)

Type of change

[ ] New country/market holidays support (thank you!)
[x] Supported country/market holidays update (calendar discrepancy fix, localization)
[ ] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency upgrade (version update)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good: make pre-commit
[x] All tests pass locally: make test, make tox (we strongly encourage adding tests to your code)
[x] The related documentation has been added/updated (check off the box for free if no updates is required)

Now I'm working on the rest of the European countries that don't have English localization: Belgium, Croatia, Czechia, Luxembourg, Slovenia).

coverage: 100.0%. remained the same when pulling 3520e0a5dbddfc57e6ca0713bc57015961350199 on KJhellico:upd-baltic into 401e17381aa53b0e8339ce735fa1260ca9570701 on dr-prodigy:beta.

Now I'm working on the rest of the European countries that don't have English localization: Belgium, Croatia, Czechia, Luxembourg, Slovenia.

Thanks for the heads up; I'll check out other non-European ones in the meantime after wrapping up Malta :pray:


Modular Input - java.lang.ArrayIndexOutOfBoundsException

Hello,
I am trying to implement a Java Modular input.
I am using splunk-sdk-java.
When trying to use the writeEvent method or synchronizedWriteEvent from the eventwriter i get an exception:
java.lang.ArrayIndexOutOfBoundsException.
Could you please advise.
This issue seems to be similar to this one:
https://answers.splunk.com/answers/577416/java-modular-input-javaxxmlstreamxmlstreamexceptio.html
Best regards.

Hello,
I am facing exactly the same issue, any update?
Tested on Splunk 7.2.6 with sdk <IP_ADDRESS> on ubuntu 18.04 with Java 8 or 11
Best regards

Hi @SplunkingArnaud & @smndf,
We have tried to reproduce this issue using one of the test case available with us. We could not encounter such behaviour.
Also, we recommend users to update your sdk to updated version (v1.7.1) along with JDK 1.8 and Maven build.


Audio PlaybackSettings volume setting doesn't correspond to human perception of volume well

Bevy version 0.10.1
If I set volume to 0.01 only then will it be subjectively about 3-5 times quieter than on default. 3-5 as in lowering volume on youtube to 33% or 20%
How to reproduce:
use bevy::{prelude::*};

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_startup_system(produce_sound)
        .run();
}

fn produce_sound(
    audio: Res<Audio>,
    asset_server: Res<AssetServer>
) {
    let sound_effect_1 = asset_server.load("audio/pluck_001.ogg");

    let playback_settings = PlaybackSettings {
         repeat: false,
         volume: 0.003f32, //this value for me lowers sound subjectively to about 2%, try different values
         speed: 1f32,
     };
     audio.play_with_settings(sound_effect_1.clone(), playback_settings);
    }
}

audiofile: https://fastupload.io/pKOtqjihV6SkJlH/file

As far as I understand, this is intentional. The documentation of the original rodio docs is as follows:

Changes the volume of the sound.
The value 1.0 is the “normal” volume (unfiltered input). Any value other than 1.0 will multiply each sample by this value.

Audio volume is logarithmic. This means that if the volume is set to 0.01 compared to the original 1.0, the sound will be exactly two times quieter than the default[^1], not 100x quieter.
My opinion is that this isn't a problem. However this should probably be indicated in the documentation. OR, probably make a more intuitive setter method based on Volume::Relative.
[^1]: If 10^x = 0.01, then x = -2, which means two times quieter.

With an amplitude (volume) of 0.01 your power would be 0.01^2 = 0.0001.
Which would be 10,000 times less loud, or 10log(0.0001) = -40 dB which will be very quiet.
Perceived doubling of audio goes by every 10 dB, so if we go the other way, -10dB:
10^(-10/10) = 0.1 power ratio, sqrt(0.1) = 0.316 amplitude ratio. So you would have to set the volume to 0.316 to halve the perceived audio.

If I set volume to 0.01 only then will it be subjectively about 3-5 times quieter than on default.
And when I try this I'm definitely getting different results, 0.01 is barely audible, almost less than 1% on youtube.
So maybe it's not just a documentation issue.

@Telov Do you have the same issue with this file? The download link for yours seems to have expired https://github.com/bevyengine/bevy/blob/main/assets/sounds/Windless Slopes.ogg


Upgrade to wgpu 0.11

Upgrades both the old and new renderer to wgpu 0.11 (and naga 0.7). This builds on @zicklag's work here #2556.

Lets see if using the "adapter limits" helps with that. Not a default I want to carry over into the new renderer, but I want to get this merged.


Read one modality in delete_layer component.

Changelog
MERGE #530 first!
Read one modality in delete_layer component.
Issue ticket number and link
In partial fulfillment for #326 (Replace xxxx with the GitHub issue number)
Checklist before requesting a review

[x] I have performed a self-review of my code

[x] Conforms to the Contributor's guide

Check the correct box. Does this PR contain:

[ ] Breaking changes
[ ] New functionality
[ ] Major changes
[x] Minor changes
[ ] Documentation
[ ] Bug fixes

[x] Proposed changes are described in the CHANGELOG.md

[x] CI tests succeed!

Waiting for #530 to be merged first :)


sops: 3.8.0 -> 3.8.1

Diff: https://github.com/getsops/sops/compare/v3.8.0...v3.8.1
Changelog: https://github.com/getsops/sops/blob/v3.8.1/CHANGELOG.rst
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

2 packages built:

kubernetes-helmPlugins.helm-secrets
sops


ns: sa_set: ... (Invalid argument) messages during startup

Hello. I'm attempting to configure baresip v1.1.0 on my OpenBSD-current system. The last time I used baresip was a few years ago, and I don't recall seeing the following messages (or something similar) printed while starting up the program.
ns: sa_set: <IP_ADDRESS> # resolvd: em0 (Invalid argument)
ns: sa_set: fd00:10::1 # resolvd: em0 (Invalid argument)
Earlier this year, OpenBSD introduced resolvd(8) [1], and as a result, the nameserver entries in /etc/resolv.conf are now formatted by resolvd as follows:
nameserver <IP_ADDRESS> # resolvd: em0
nameserver fd00:10::1 # resolvd: em0
I wasn't able to confirm this on my own, so I just wanted to check if the addition of "# resolvd: em0" to the nameserver entries is possibly causing this message/issue.
[1] https://man.openbsd.org/resolvd

I will try to test the Git version this weekend, but it may take a bit longer. Regardless, improving the way comments are handled seems like a positive change.

I just finished testing the Git versions of baresip, re, and rem. Unfortunately I'm still seeing the same messages.
If you're up to it, I can only recommend visiting the CVS link I posted above, where you can look for any changes introduced in the OpenBSD port (Makefiles, patches, etc.) that could be affecting the expected behavior. I don't know what to look for, so I wouldn't be much help with that.

Sorry fo the delay. What compiler do you use? I just realized OpenBSD has a modificated/old gcc as system compiler:
man gcc-local
gcc does not search under /usr/local for include files nor for libraries: as a system compiler, it only searches the system paths by default.
You can try:
gmake CC=clang

No problem. OpenBSD switched the system compiler to clang back in 2017.
$ clang --version
OpenBSD clang version 13.0.0


documentation TODO

@stonier

Concert

[ ] Quick Demos
[ ] Create Your Own Solution
[ ] Make Your Robot To Join Concert
[ ] Introspect The Concert In Runtime
[ ] Configure Waypoint Navigation Service in Your Environment

Concert Services

[ ] Create Your Own Concert Service
[ ] Add Service in Your Solution

Software Farm

[ ] Create Your own Software
[ ] How To Use Software In Your Service

Gazebo Concert

[ ] How To Start Gazebo Concert
[ ] Add Your Gazeobo Robot In Concert

Appable Robot

[ ] Make Your Robot Appable
[ ] Add Rocon URI
[ ] Pairing Mode
[ ] Capabilities
[ ] Rapp Development
[ ] Interaction Developement


Items facing camera upwards.

First issue is that items follow the camera even upwards which isn't bad but isn't accurate to how fast dropped items used to look. If this is intentional could you add another option to disable the items from facing upward?

Fair enough, i can try pulling off this effect and make an updated release later.


Set theme jekyll-theme-cayman

The master branch does not accept the merge request. If there is any modification, please do it on the basis of develop.


need train model and aflw.sqlite

hi, thank you for sharing the code.
Could you share me with aflw.sqlite and trained model ?Because I cannot download it from the link.
my email is<EMAIL_ADDRESS>thank you very much

hi, thank you for replying.
Could you tell me how to get the  aflw.sqlite or the process of  aflw.sqlite?
thank you very much

aflw.sqlite is a part of AFLW dataset and the dataset also contains face images corresponding to the sqlite file.
To download AFLW, you have to email the owner. Please read following website.
https://lrs.icg.tugraz.at/research/aflw/


Using arrows to edit the command

Writing something, then using left arrow to "move back the cursor", then edit something and hit "enter" should work.

That would be a useful addition. You'd need to teach menu about ANSI escape sequences though.

This also ties into a discussion around "cooked" and "raw" terminals. Because with a cooked terminal, the terminal does the line editing for you.


ctrlCmd+up in terminal chat input focuses chat response list

reported by @Tyriar

open terminal chat, run something
ctrlCmd+up in the input
🐛 chat response list focused

This is happening because in the chat widget, when focus is on the input, ctrlCmd+up focuses the chat list.
https://github.com/microsoft/vscode/blob/d42fad27b278543b0ac92de06b217a67ede40dcc/src/vs/workbench/contrib/chat/browser/actions/chatActions.ts#L208-L231


Restore-DbaDatabase allows red errors

There’s a couple of others as well I found while poking around
Working on them, but getting some strange errors which I think is my test env being out of sync with GitHub. Need to find time to rebuild it
On 4 December 2018 at 09:59:01, Chrissy LeMaire<EMAIL_ADDRESS>wrote:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Just found this one:
The property 'PhysicalName' cannot be found on this object. Verify that the property exists and can be set.
At C:\Program Files\WindowsPowerShell\Modules\dbatools\0.9.532\allcommands.ps1:22964 char:25

...             $_.PhysicalName = $RestoreDir + $PathSep + $DatabaseFileP ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : PropertyNotFound

WARNING: [11:40:48][Select-DbaBackupInformation] Fullname property not found. This could mean that a full backup could not be found or the command must be re-run with the -Continue switch.

@devondba what did you run to produce that?

Hey @Stuart-Moore I'm afraid I can't recall off hand, sorry at the time I thought the error would be enough, do appologise. I'll try and have a bash at repeating it this afternoon.

No problems.
I have a suspicion the fix will catch that one as well, but just want to make sure.
On 21 December 2018 at 14:19:48, devondba<EMAIL_ADDRESS>wrote:
Hey @Stuart-Moore I'm afraid I can't recall off hand, sorry at the time I thought the error would be enough, do appologise. I'll try and have a bash at repeating it this afternoon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks so much for addressing this stuart!


The "Become a mentor" button is not properly responsive on mobile devices.

Describe the bug
The "Become a mentor" button is not properly responsive on mobile devices.
To Reproduce
Steps to reproduce the behavior:

Go to the homepage on a mobile device.
Scroll down to the "Become a mentor" button.
Notice that the button does not resize properly.

Expected behavior
The "Become a mentor" button should resize properly on mobile devices to ensure a good user experience.
Screenshots

Smartphone (please complete the following information):

Device: [e.g. iPhone 12]
OS: [e.g. iOS 14.4]
Browser Brave
Version Version 1.61.114 Chromium: 120.0.6099.199 (Official Build) unknown (64-bit)

Additional context
This issue affects all pages where the "Become a mentor" button appears.
Are you working on it?

hey, where is should i replace this button? in the navbar list ? or  right side of the logo?


Fixed issue when the script tries to acces more cores than the cpu has

The problem was described in #22 .
Proposed fix is to determine the cpu entries by using the cpu_count() function.

Thanks you for pointing out this subtle bug. The proposed patch is wrong since [0-9] in glob is expanded by shell-like regular expressions. I'll push the correct one in a minute


test(e2e): add e2e tests for notification

Please provide a link to the associated issue.
Closes
Please provide a brief summary of this pull request.
Please check whether the PR fulfills the following requirements

[ ] the commit message follows the guideline:
https://github.com/SAP/fundamental-ngx/blob/main/CONTRIBUTING.md
[ ] tests for the changes that have been done
[ ] all items on the PR Review Checklist are addressed :
https://github.com/SAP/fundamental-ngx/wiki/PR-Review-Checklist
[ ] Run npm run build-pack-library and test in external application

Documentation checklist:

[ ] update README.md
[ ] Breaking Changes Wiki
[ ] Documentation Examples
[ ] Stackblitz works for all examples

please squash

please remove all non-e2e test file changes. (platform table component, etc)

https://github.com/maxym-valor/fundamental-ngx/pull/86


First entry in filter is not displayed

Sometimes the first entry in some filters is not visible.

Fixed in last version


an error message appears in the console log like this "Warning: Unknown: Support for defaultProps will be removed from memo components in a future major release. Use JavaScript default parameters instead."

an error message appears in the console log like this "Warning: Unknown: Support for defaultProps will be removed from memo components in a future major release. Use JavaScript default parameters instead."

This was fixed in v2.1.1.
Please reopen this issue if it does not solve the problem for you!


Fixes connector certificate revocation

Description
Changes proposed in this pull request:

Contains the fix for the connector certificate revocation flow

/ok-to-test

/test all


Bump github.com/nginxinc/telemetry-exporter to v0.1.0

Proposed changes
Bumps the telemetry-export library to v0.1.0
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[ ] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that all unit tests pass after adding my changes
[ ] I have updated necessary documentation
[ ] I have rebased my branch onto main
[ ] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

NONE

Interesting dependabot now is able to bump to a major version #2109 let's us that one


FAB-17315 english colon[:] illegal filename problem on windows when lifecycle chaincode install

Type of change

Bug fix

Description

Fix the problem caused by illegal English colon characters in the file name generated under the directory production\lifecycle\chaincodes on the Windows platform when lifecycle chaincode install
Additional details

Related issues

https://jira.hyperledger.org/browse/FAB-17315

never tried running fabric on windows but i believe colon is indeed illegal for filename. we probably want to give a different name when storing package on fs. However, do we need to change pkgid schema as well? @jyellick

We did have this Jira around performing this work, which was eventually decided (maybe we would come back and visit this in the future). If this is going to be undertaken, this is the Jira and the exhaustive list should exhausted

never tried running fabric on windows

We don't test or support running the peer or orderer on windows, but we do support the CLI in that space. We need to get under if/why the persistence package would be used in the CLI space and, if it is used and used appropriately, address the issue.
If it turns out that the persistence is only the server side (which is my hope), Windows is not a supported host environment for the peer at this time.
We'll dig in a bit....

never tried running fabric on windows

We don't test or support running the peer or orderer on windows

Is this written somewhere? (glad to see we don't need to support server side actually...)

If it turns out that the persistence is only the server side (which is my hope), Windows is not a supported host environment for the peer at this time.

IIRC, that persistency is only on server side.

Yes, we do not plan to support running fabric services under windows or as a chain code development environment now. There are a few things that can be determined:

On Linux or Mac systems, use an underscore _ instead of a colon: as the delimiter of package.tar.gz, all are valid characters, and have no effect on the fabric server currently running on Linux.
The English colon is illegal in the file name under windows. We will lost the compatibility of running fabric on windows later.
Through the simple modification above, I have successfully run fabric 2.0 servers on my windows 10.

Through the simple modification above, I have successfully run fabric 2.0 servers on my windows 10.

I understand that the colon is the drive separator character on windows and that it's a problem for that environment.  This does not change the fact that we do not test or support running the peer on Windows.
Additionally, the underscore is a valid character in chaincode ID labels under the new lifecycle. The changes you have proposed break the existing code when labels contain underscores.
So there are two concerns:

The code changes that are proposed are incomplete and break the logic associated with packageFileMatcher.
Even if this change is incorporated, there is no guarantee that additional changes won't be necessary and, as with this change, we lack the resources or infrastructure to test them completely at this time.

Does anybody know where the valid characters for label are defined? It seems that colons within the label actually works (except in Windows). At least, nothing validates that colon shouldn't be included. @jyellick @ale-linux

regexp for the label was fixed and tested here: https://github.com/hyperledger/fabric/pull/480

I understand that we are not attempting to support/test windows platform but I do empathize the need to setup dev env on it, and i think this is not really a drastic change asking for a compromise among platforms.
Also, wouldn't it be easier for an admin to pull down the pkg file and inspect, if it does not contain colon? Furthermore, if one day (i wish that day would not come though) we need to support the platform, this would not be another breaking change.
Why was colon chosen as separator initially and why cannot it be changed prior to release?

I initially typed up something a bit longer, but the short history of "why is there a colon in the name", would be because it was the shortest path to get things working, that we could always come back and mangle the package-id before writing it to the filesystem if need be.  This bug / PR seems to give us a reason to reassess.
I think we can live with a delimiter which is also in the list of allowable label characters.  Since we know the format is always <label><delimiter><fixed-length-hex>.tar.gz it's certainly possible to create safe parsing of labels no matter what delimiter we pick.
Even on UNIX, : is a bit of an annoying character to have in filenames, and since we seem to have users running up against real problems, I'm certainly amenable to seeing it changed.
In the old lifecycle, it appears that the the : was substituted for a ..  Since no one seemed to complain about that, it would be somewhat natural choice to me, though I'm open to other suggestions.

Through the simple modification above, I have successfully run fabric 2.0 servers on my windows 10.

I understand that the colon is the drive separator character on windows and that it's a problem for that environment. This does not change the fact that we do not test or support running the peer on Windows.
Additionally, the underscore is a valid character in chaincode ID labels under the new lifecycle. The changes you have proposed break the existing code when labels contain underscores.
So there are two concerns:

The code changes that are proposed are incomplete and break the logic associated with packageFileMatcher.
Even if this change is incorporated, there is no guarantee that additional changes won't be necessary and, as with this change, we lack the resources or infrastructure to test them completely at this time.

Yes, without breaking the current LabelRegexp expression (^[[:alnum:]][[:alnum:]_.+-]*$) , Maybe we just need to find a common character that is not in [0~9][a~z][A~Z][ _.+-], acts as file name delimiter for packageID, and it is a valid file name character for linux, Mac, windows, etc.
I chose the English wave symbol ~ as this separator, and the code has been updated.
We know that the English colon is an illegal file name character for Windows. If we can fix this problem before the Fabric 2.0 release, when we plan to support Windows in the future, we do not need to modify the name of the existing packageID file containing the colon on Linux and Mac servers.

I think we can live with a delimiter which is also in the list of allowable label characters. Since we know the format is always .tar.gz it's certainly possible to create safe parsing of labels no matter what delimiter we pick.

Why do we actually need a delimiter is we have ?  Seems we can always just split  based on the fact we know the length of .

Why do we actually need a delimiter if we have ? Seems we can always just split based on the fact we know the length of .

We can split based on the tail length and any character can be used as the delimiter that is not "special."  We all agree this can be done. We can also encode the names as base32 if we choose; there are many ways to do this.
I want to reiterate my two points:

These changes are incomplete.
There's no guarantee we won't hit other issues.

If we want these changes, we really need to address the completeness aspect here.

These changes are incomplete.

The use of ~ looks to address the "completeness" concern.

I'm ok with ~

I would prefer that we move to a more standard delimiter, like ., and use suffix matching, rather than regexp splitting to separate the label.  That being said, the move to ~ is still an improvement/fix for the current issue, so I'm fine merging as is if others would prefer.

/azp run

your commits

My commits have been squashed successfully.

@jyellick I'll handle suffix matching on top.


FlagSize does not work on ListTile leading

Hi there,
I hope you are doing well.
There is a bug with the flagSize of the country selector for draggableBottomSheet.
when I try to set flagSize for the icon on doesn't work properly. It is getting the flag in a wrong shape.
To reproduce it, just try to set a size for the flag into on country selector navigator and you will be able to see that the size does not change.

Could be an issue with the circle flags library https://github.com/cedvdb/flutter_circle_flags/blob/main/lib/circle_flags.dart
Do you have the issue with this package ? https://github.com/cedvdb/flutter_circle_flags/blob/main/lib/circle_flags.dart
I'll review a PR

Should be fixed in next release


Qdrant import / collection not working

Details
curl -L -X POST 'http://localhost:6333/collections/my_imported_collection/points/search' -H 'Content-Type: application/json' \
                                                                                --data-raw '{
                                                                                "vector": [0.69,0.69,0.59,0.74,0.18,0.44,0.91,0.76,0.35,0.8,0.31,0.61,0.62,0.49,0.85,0.41,0.26,0.43,0.09,0.34,0.41,0.07,0.16,0.75,0.24,0.87,0.89,0.29,0.43,0.78,0.55,0.78,0.97,0.28,0.68,0.44,0.01,0.41,0.63,0.64,0.41,0.69,0.36,0.92,0.29,0.52,0.37,0.49,0.83,0.53,0.24,0.04,0.78,0.7,0.04,0.48,0.81,
0.33,0.39,0.24,0.26,0.68,0.26,0.02,0.69,0.38,0.76,0.67,0.65,0.83,0.28,0.98,0.59,0.49,0.67,0.42,0.4,0.11,0.1,0.94,0.89,0.45,0.73,0.87,0.76,0.7,0.06,0.45,0.95,0.27,0.3,0.84,0.11,0.06,0.6,0.94,0.56,0.68,0.99,0.33,0.22,0.71,0.49,0.6,0.84,0.63,0.71,0.1,0.96,0.59,0.9,0.92,0.5,0.03,0.65,0.39,0.96,0.72,0.87,0.02,0.38,0.61,0.91,0.34,0.95,0.47,0.82,0.81,0.47,0.31,0.72,0.27,0.88,0.47,0
.51,0.04,0.5,0.99,0.09,0.77,0.13,0.5,0.78,0.33,0.26,0.28,0.1,0.27,0.27,0.92,0.15,0.49,0.88,0.55,0.4,0.2,0.61,0.6,0.88,0.29,0.48,0.1,0.41,0.21,0.41,0.27,0.73,0.25,0.52,0.89,0.94,0.28,0.16,0.17,0.03,0.34,0.85,0.52,0.83,0.38,0.17,0.57,0.28,0.29,0.94,0.89,0.46,0.81,0.93,0.88,0.07,0.62,0.6,0.75,0.63,0.63,0.37,0.2,0.41,0.15,0.34,0.39,0.96,0.63,0.02,0.53,0.23,0.2,0.11,0.09,0.4,0.42
,0.64,0.68,0.78,0.13,0.45,0.47,0.32,0.95,0.66,0.41,0.02,0.22,0.16,0.1,0.51,0.31,0.3,0.41,0.85,0.36,0.85,0.27,0.26,0.96,0.73,0.62,0.99,0.96,0.47,0.3,0.78,0.53,0.46,0.24,0.39,0.58,0.64,0.4,0.68,0.02,0.86,0.04,0.38,0.11,0.69,0.9,0.4,0.88,0.14,0.96,0.65,0.74,0.32,0.59,0.83,0.22,0.91,0.55,0.7,0.87,0.23,0.19,0.94,0.98,0.16,0.86,0.76,0.18,0.43,0.18,0.69,0.07,0.31,0.52,0.93,0.91,0.9
7,0.32,0.15,0.98,0.23,0.36,0.48,0.18,0.56,0.77,0.21,0.87,0.65,0.1,0.3,0.52,0.57,0.9,0.65,0.62,0.94,0.96,0.33,0.24,0.89,0.02,0.75,0.77,0.1,0.75,0.84,0.49,0.15,0.19,0.37,0.12,0.2,0.56,0.99,0.44,0.74,0.08,0.52,0.36,0.07,0.07,0.78,0.8,0.39,0.79,0.58,0.16,0,0.46,0.38,0.05,0.26,0.18,0.27,0.21,0.57,0.07,0.86,0.54,0.31,0.25,0.14,0.56,0.14,0.98,0.06,0.14,0.76,0.6,0.93,0.58,0.9,0.18,0
.46,0.33,0.27,0.34,0.89,0.27,0.69,0.89,0.41,0.05,0.07,0.28,0.28,0.17,0.88,0.62,0.81,0.92,0.05,0.13,0.11,0.82,0.23,0.96,0.88,0.07,0.71,0.12,0.38,0.11,0.1,0.94,0.63,0.38,0.25,0.54,0.85,0.93,0.65,0.33,0.52,0.6,0.99,0.24,0.47,0.09,0.94,0.65,0.44,0.52,0.35,0.24,0.66,0.59,0.59,0.68,0.37,0.3,0.22,0.28,0.25,0.4,0.6,0.98,0.94,0.88,0.33,0.94,0.59,0.2,0.48,0.96,0.52,0.56,0.13,0.1,0.05,
0.14,0.97,0.14,0.35,0.67,0.36,0.22,0.58,0.29,0.85,0.07,0.18,0.77,0.5,0.13,0.51,0.11,0.92,0.53,0.34,0.85,0.63,0.7,0.07,0.31,0.12,0.64,0.47,0.56,0.17,0.54,0.68,0.95,0.2,0.3,0.12,0.42,0.83,0.42,0.23,0.34,0.7,0.66,0.77,0.15,0.97,0.22,0.26,0.6,0.99,0.67,0.1,0.82,0.03,0.72,0.8,0.88,0.59,0.71,0.77,0.65,0.88,0.59,0.6,0.24,0.22,0.08,0.17,0.69,0.34,0.63,0.24,0.94,0.17,0.12,0.08,0.12,0
.18,0.44,0.16,0.25,0.91,0.41,0.72,0.66,0.63,0.86,0.94,0.1,0.91,0.52,0.17,0.13,0.23,0.97,0.29,0.12,1,0.95,0.7,0.31,0.09,0.68,0.18,0.82,0.88,0.11,0.43,0.75,0.51,0.77,0.41,0.87,0.3,0.39,0.99,0.27,0.44,0.42,0.84,0.86,0.77,0.28,0.26,0.62,0.99,0.32,0.41,0.45,0.95,0.85,0.13,0.28,0.18,0.1,0.54,0.37,0.86,0.86,0.79,0.36,0.64,0.98,0.79,0.07,1,0.87,0.4,0.04,0.24,0.78,0.91,0.41,0.98,0.63
,0.73,0.49,0.35,0.55,0.87,0.24,0.26,0.14,0.67,0.1,0.97,0.09,0.44,0.04,0.87,0.24,0.4,0.49,0.32,0.5,0.44,0.91,0.57,0.67,0.39,0.22,0.81,0.28,0.14,0.73,0.93,0.27,0.63,0.67,0.06,0.89,0.8,0.82,0.09,0.81,0.32,0.16,0.19,0.71,0.03,0.84,0.19,0.89,0.83,0.52,0.61,0.79,0.2,0.54,0.64,0.13,0.46,0.24,0.15,0.84,0.31,0.43,0.52,0.4,0.49,0.32,0.63,0.05,0.69,0.67,0.48,0.94,0.89,0.02,0.28,0.4,0.3
4,0.34,0.03,0.02,0.65,0.85,0.78,0.72,0.47,0.67,0.32,0.03,0.11,0.27,0.8,0.59,0.58,0.83,0.92,0.87,0.95,0.61,0.06,0.72,0.13,0.63,0.47,0.59,0.1,0.95,0.75,0.37,0.63,0.99,0.58,0.1,0.37,0.8,0.36,0.05,0.92,0.76,0.41,0.99,0.03,0.06,0.09,0.28,0.86,0.99,0.69,0.52,0.62,0.79,0.33,0.12,0.7,0.58,0.56,0.02,0.46,0.77,0.88,0.09,0.37,0.51,0.87,0.45,0.5,0.45,0.42,0.43,0.64,0.66,0.13,0.94,0.35,0
.35,0.62,0.61,0.64,0.8,0.18,0.59,0.77,0.02,0.54,0.94,0.56,0.26,0.97,0.55,0.71,0.08,0.89,0.82,0.26,0.24,0.18,0.27,0.77,0.79,0.18,0.03,0.68,0.56,0.63,0.08,0.15,0.76,0.91,0.41,0.94,0.44,0.78,0.95,0.52,0.68,0.45,0.16,0.29,0.08,0.86,0.26,0.65,0.21,0.39,0.77,0.45,0.19,0.81,0.48,0.9,0.55,0.42,0.03,0.37,0.72,0.99,0.4,0.01,0.86,0.96,0.69,0.67,0.12,0.85,0.79,0.95,0.19,0.46,0.57,0.76,0
.82,0.63,0.51,0.86,0.29,0.05,0.24,0.42,0.99,0.13,0.55,0.73,0.63,0.24,0.94,0.67,0.34,0.79,0.47,0.89,0.98,0.98,0.99,0.32,0.93,0.42,0.95,0.74,0.64,0.33,0.98,0.64,0.35,0.91,0.4,0.9,0.97,0.22,0.82,0.65,0.47,0.61,0.94,0.24,0.42,0.64,0.24,0.63,0.17,0.39,0.42,0.31,0.84,0.34,0.41,0.78,0.13,0.02,0.63,0.87,0.58,0.37,0.62,0.31,0.9,0.02,0.47,0.12,0.39,0.84,0.96,0.55,0.24,0.21,0,0.96,0.56
,0.31,0.85,0.28,0.61,0.35,0.76,0.93,0.37,0.73,0.07,0.08,0.36,0.21,0.77,0.75,0.53,0.45,0.21,0.79,0.57,0.67,0.74,0.39,0.97,0.46,0.41,0.24,0.85,0,0.51,0.19,0.4,0.41,0.48,0.64,0.86,0.75,0.79,0.65,0.4,0.59,0.69,0.44,0.77,0.85,0.95,0.06,0.94,0.61,0.2,0.19,0.21,0.32,0.38,0.99,0.58,0.38,0.16,0.9,0.2,0.18,0.16,0.78,0.41,0.22,0.57,0.88,0.78,0.56,0.91,0.12,0.14,0.74,0.97,0.68,0.32,0.8,
0.56,0.93,0.15,0.4,0.93,0.33,0.28,0.67,0.5,0.93,0.89,0.54,0.79,0.87,0.74,0.25,0.66,0.42,0.03,0.24,0.06,0.36,0.54,0.41,0.05,0.05,0.39,0.24,0.15,0.89,0.67,0.84,0.47,0.3,0.9,0.79,0.58,0.1,0.95,0.49,0.78,0.75,0.93,0.42,0.53,0.17,0.12,0.01,0.34,0.65,0.46,0.32,0.04,0.15,0.03,0.6,0.29,0.07,0.87,0.29,0.6,0.6,0.15,0.14,0.29,0.52,0.34,0.58,0.44,0.85,0.23,0.08,0.26,0.21,0.02,0.4,0.89,0
.8,0.66,0.65,0.28,0.56,0.14,0.36,0.61,0.22,0.85,0.32,0.83,0.44,0.44,0.72,0.85,0.01,0.23,0.51,0.65,0.22,0.58,0.99,0.31,0.34,0.85,0.45,0.78,0.49,0.94,0.36,0.95,0.15,0.86,0.96,0.01,0.72,0.08,0.92,0.22,0.57,0.39,0.31,0.47,1,0.34,0.29,0.82,0.31,0.44,0.07,0.5,0.25,0.25,0.77,0.03,0.66,0.96,0.46,0.52,0.1,0.52,0.92,0.61,0.07,0.24,0.81,0.73,0.81,0,0.12,0.92,0.9,0.37,0.49,0.4,0.98,0.58
,0.35,0.59,0.11,0.05,0.17,0.61,0.85,0.07,0.33,0.5,0.97,0.87,0.22,0.63,1,0.1,0.28,0.15,0.49,0.5,0.25,0.68,0.8,0.24,0,0.05,0.59,0.54,0.88,0.49,0.17,0.36,0.03,0.46,0.03,0.31,0.46,0.39,0.55,0.05,0.92,0.42,0.37,0.87,0.49,0.52,0.21,0.2,0.86,0.49,0.75,0.97,0.65,0.57,0.74,0.72,0.77,0.51,0.04,0.02,0.08,0.52,0.5,0.66,0.39,0.85,0.63,0.11,0.37,0.51,0.85,0.03,0.19,0.65,0.65,0.33,0.28,0.7
1,0.68,0.88,0.31,0.99,0.52,0.08,0.83,0.59,0.22,0.31,0.86,0.44,0.59,0.4,0.61,0.33,0.3,0.23,0.83,0.02,0.8,0.98,0.11,0.35,0.48,0.45,0.58,0.23,0.18,0.23,0.36,0.16,0.35,0.88,0.25,0.39,0.9,0.03,0.81,0.69,0.2,0.36,0.61,0.85,0.17,0.43,0.5,0.57,0.95,0.94,0.67,0.27,0.42,0.76,0.63,0.41,0.46,0.99,0.37,0.56,0.21,0.32,0.98,0.7,0.7,0.32,0.93,0.34,0.84,0.34,0.94,0.18,0.31,0.07,0.59,0.98,0.9
1,0.3,0.06,0.17,0.73,0.72,0.93,0.5,0.04,0.22,0.54,0.06,0.21,0.09,0.77,0.67,0.94,0.39,0.66,0.93,0.03,0.11,0.92,0.47,0.81,0.38,0.03,0.06,0.84,0.66,0.01,0.82,0.68,0.86,0.97,0.15,0.99,0.29,0.56,0.41,0.4,0.11,0.65,0.34,0.47,0.1,0.22,0.56,0.32,0.74,0.18,0.15,0.42,0.69,0.18,0.17,0.07,0.98,0,0.86,0.92,0.56,0.53,0.12,0.01,0.58,0.72,0.28,0.59,0.17,0.95,0.21,0.29,0.78,0.45,0.19,0.26,0.
8,0.29,0.33,0.48,0.53,0.73,0.44,0.95,0.9,0.49,0.32,0,0.37,0.72,0.29,0.3,0.09,0.91,0.25,0.51,0.23,0.27,0.86,0.73,0.4,0.63,0.7,0.5,0.03,0.46,0.66,0.13,0.28,0.22,0.77,0.24,0.19,0.59,0.32,0.12,0.28,0.83,0.45,0.96,0.14,0.45,0.93,0.28,0.46,0.97,0.4,0.94,0.57,0.87,0.57,0.22,0.35,0.9,0.34,0.41,0.7,0.35,0.38,0.04,0.27,0.25,0.69,0.02,0.91,0.35,0.76,0.62,0.46,0.49,0.46,0.45,0.9,0.1,0.3
2,0.09,0.91,0.13,0.87,0.83,0.06,0.84,0.1,0.97,0.11,0.31,0.18,0.02,0.76,0.51,0.5,0.17,0.61,0.12,0.25,0.51,0.65,0.01,0.93,0.59,0.27,0.35,0.22,0.43,0.02,0.7,0.55,0.9,0.37,0.92,0.41,0.32,0.21,0.57,0.49,0.64,0.54,0.85,0.98,0.87,0.14,0.43,0.15,0.04,0.71,0.01,0.43,0.1,0.72,0.32,0.96,0.34,0.83,0.72,0.96,0.82,0.07,0.95,0,0.51,0.15,0.43,0.8,0.57,0.11,0.27,0.14,0.56,0.01,0.03,0.04,0.99
,0.92,0.49,0.39,0.64,0.13,0.82,0.66,0.1,0.94,0.47,0.61,0.3,0.3], "top": 3 }'
{"status":{"error":"Wrong input: Vector params for  are not specified in config"},"time":0.001418866}

the config.json of the collection looks strange to me:

{
    "params": {
        "vectors": {
            "vector": {
                "size": 1536,
                "distance": "Cosine"
            }
        },
        "shard_number": 1,
        "replication_factor": 1,
        "write_consistency_factor": 1,
        "on_disk_payload": true
    },
    "hnsw_config": {
        "m": 16,
        "ef_construct": 100,
        "full_scan_threshold": 10000,
        "max_indexing_threads": 0,
        "on_disk": false
    },
    "optimizer_config": {
        "deleted_threshold": 0.2,
        "vacuum_min_vector_number": 1000,
        "default_segment_number": 0,
        "max_segment_size": null,
        "memmap_threshold": null,
        "indexing_threshold": 20000,
        "flush_interval_sec": 5,
        "max_optimization_threads": null
    },
    "wal_config": {
        "wal_capacity_mb": 32,
        "wal_segments_ahead": 0
    },
    "quantization_config": null
}

Probably the reason for this issue is:   "vectors": { "vector": { ... instead of
{
    "params": {
        "vectors": {
                "size": 1536,
                "distance": "Cosine"
        },
...}

Branch
No response

Checklist

[X] Modify src/vdf_io/import_vdf/qdrant_import.py ✓ https://github.com/AI-Northstar-Tech/vector-io/commit/01405c0d8695fcdffbab2a783bfa29199c2868c5 Edit

The
"params": {
        "vectors": {
            "vector": {
                "size": 1536,
                "distance": "Cosine"
            }
        },
		...

is matching the format for named vectors.
I want to better understand the sequence of your operations. Did you first import a vdf dataset into your qdrant instance, and then try to do a search via the REST API?


The repo doesn't seem to actually contain visualizer code

I've cloned the repo into packages (as well as tried using Unity's built in add package from the package manager), and I have only been able to find limited code and no shaders. The folder VX.Audio is completely empty, and the only .cs file I can find is WireframeGUI.cs

Oh wait, that is weird, I have not included the main files for some reason in this release. Gotta fix that... in the mean time checkout v1.0.0


Add ability to set PID file mode

Fixes https://tickets.puppetlabs.com/browse/MODULES-3389

Does this help with or negate #227  #251 ?  I'm seeing this on RHEL7x64.

I don't mind this pattern too much, but it does seem like just leaving the mode out entirely would make sense too.

I assumed the management of the pidfile was in there for good reason and thus left it, but added the ability to adjust the mode.
If there's no reason for management of the pidfile, then I would definitely just remove the resource entirely.

@walkamongus Yeah, I'm not convinced that the pidfile really should be managed. It appears to be a historical edge case that could probably be skipped in the next major release.

Can we revert this merge, or at least change the default value of $manage_pidfile to false? It breaks mongodb quite horribly when mongodb is stopped (which means that there's no pidfile to manage):
Error: Could not set 'file' on ensure: No such file or directory @ rb_sysopen - /var/run/mongodb/mongod.pid at /etc/puppetlabs/code/envs/rune/modules/upstream/mongodb/manifests/server/config.pp:237
Error: Could not set 'file' on ensure: No such file or directory @ rb_sysopen - /var/run/mongodb/mongod.pid at /etc/puppetlabs/code/envs/rune/modules/upstream/mongodb/manifests/server/config.pp:237
Wrapped exception:
No such file or directory @ rb_sysopen - /var/run/mongodb/mongod.pid
Error: /Stage[main]/Mongodb::Server::Config/File[/var/run/mongodb/mongod.pid]/ensure: change from absent to file failed: Could not set 'file' on ensure: No such file or directory @ rb_sysopen - /var/run/mongodb/mongod.pid at /etc/puppetlabs/code/envs/rune/modules/upstream/mongodb/manifests/server/config.pp:237
Notice: /Stage[main]/Mongodb::Server::Service/Service[mongodb]: Dependency File[/var/run/mongodb/mongod.pid] has failures: true
Warning: /Stage[main]/Mongodb::Server::Service/Service[mongodb]: Skipping because of failed dependencies
Notice: /Stage[main]/Mongodb::Server::Service/Mongodb_conn_validator[mongodb]: Dependency File[/var/run/mongodb/mongod.pid] has failures: true
Warning: /Stage[main]/Mongodb::Server::Service/Mongodb_conn_validator[mongodb]: Skipping because of failed dependencies
Notice: /Stage[main]/Mongodb::Server/Anchor[mongodb::server::end]: Dependency File[/var/run/mongodb/mongod.pid] has failures: true
Warning: /Stage[main]/Mongodb::Server/Anchor[mongodb::server::end]: Skipping because of failed dependencies
Error: Failed to apply catalog: Could not evaluate MongoDB shell command: printjson(db.getMongo().getDBs())

I kinda get the rationale for this but I really don't think this is the right place for it, and from my point of view it creates more problems than it solves.

@runejuhl I believe this PR only added the ability to manage the mode of the pidfile separate from managing the pidfile itself so reverting it would still leave the managed pidfile.
I think ultimately it was agreed that the best solution is to leave out managing the pidfile completely.

@walkamongus I'd be fine with submitting a PR if you believe that it'll get merged. Otherwise I should probably raise an issue on JIRA?

@runejuhl I assume it would me be merged as long as its complete with test coverage? I'm not one of the maintainers -- just a regular user. Pairing it with an open issue with documentation definitely shouldn't hurt.


Looks like an update is needed?

Hi,
When I'm looking into the Ignite 2018, I see a different approach in code for creating the env and context etc. Actually pipelines belong to Legacy part of the namespace now.
Could you please update these tutorials with the new releases.

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

ID: a30b3ff5-b5e6-ff02-6f60-b5cef6f34666
Version Independent ID: fdf962e2-620e-d9ad-5057-5f96f52dc60f
Content: Use ML.NET to predict New York taxi fares (regression)
Content Source: docs/machine-learning/tutorials/taxi-fare.md
Product: dotnet-ml
GitHub Login: @aditidugar
Microsoft Alias: johalex

I'm willing to update the tutorials to use the new ML.NET API.
However, there are two points to consider:

As far as I understand, the new API is still work in progress and might change in the following ML.NET versions. Thus, it might make sense to update tutorials later (with 0.7 or 0.8 version) when API is more stable. Or, tutorial-wise, API is already good enough?

Should both approaches (LearningPIpeline and new API) be presented in the docs? Or updated tutorials would replace the current ones?

@JRAlexander what do you think?

@pkulikov - Good question. @GalOshri - Thoughts here?

@GalOshri

However, we will likely want to update some of the intro material at least to help people get started with the latest APIs.

Current docs make a note of the new API and provide the links to the intro topics in dotnet/machinelearning repo:
https://docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/

@JRAlexander #8839 updates the sentiment analysis tutorial to 0.7 version. Is it fine, if I'll update the clustering tutorial meanwhile?