FileChooserNativeBuilder drops the filters

Creating a dialog with a filter like
let gif_filter = gtk::FileFilter::new();
gif_filter.add_mime_type("image/gif");
gif_filter.set_name(Some("GIF (image/gif)"));

let file_chooser = gtk::FileChooserNativeBuilder::new()
    .accept_label("Open")
    .cancel_label("Cancel")
    .modal(true)
    .title("Open a GIF to display")
    .transient_for(self)
    .action(gtk::FileChooserAction::Open)
    .filter(&gif_filter)
    .build();

wouldn't show up which is normal as the filter isn't a prop as the builder somehow assumes? and should use the method in FileChooserExt::add_filter to assign all those filters which would require writing the builder manually I guess
Works fine btw
let gif_filter = gtk::FileFilter::new();
gif_filter.add_mime_type("image/gif");
gif_filter.set_name(Some("GIF (image/gif)"));

let file_chooser = gtk::FileChooserNativeBuilder::new()
    .accept_label("Open")
    .cancel_label("Cancel")
    .modal(true)
    .title("Open a GIF to display")
    .transient_for(self)
    .action(gtk::FileChooserAction::Open)
    .build();
file_chooser.add_filter(&gif_filter);

Sounds like the documented behavior https://developer.gnome.org/gtk3/stable/GtkFileChooser.html#gtk-file-chooser-set-filter
Maybe it's possible to make the list managed by add_filter a property upstream. Then we would get the feature that you want as well.

Yeah it's just confusing. I think the property should have been called default-filter or something like that. I'm going to go ahead and close this one as I don't believe it's something actionable from our side. What would be nice to have though is for gir to generate comments for each property setter based on the props documentation if there are any?

Ran into this again, was really confusing. Is there any reason why we don't panic in builders when setting the same property twice? This would have prompted me to the mistake a lot quicker


Support redirect lists

~This is a draft because we are waiting for a cloudflare-go release.~
Closes #1342

acceptance tests are all green
TF_ACC=1 go test $(go list ./...) -v -run "^TestAccCloudflareList_" -count 1 -parallel 1 -timeout 120m -parallel 1
?       github.com/cloudflare/terraform-provider-cloudflare     [no test files]
=== RUN   TestAccCloudflareList_Exists
--- PASS: TestAccCloudflareList_Exists (9.30s)
=== RUN   TestAccCloudflareList_UpdateDescription
--- PASS: TestAccCloudflareList_UpdateDescription (16.59s)
=== RUN   TestAccCloudflareList_Update
--- PASS: TestAccCloudflareList_Update (36.95s)
PASS
ok      github.com/cloudflare/terraform-provider-cloudflare/internal/provider   63.258s
?       github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/changelog-check   [no test files]
?       github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/maintainer-only-file-check        [no test files]
?       github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/tf-log-check      [no test files]
?       github.com/cloudflare/terraform-provider-cloudflare/version     [no test files]

thanks @orium!

Thanks :laughing:

Any ideas when this version will be publicly available?

@KevinM2k There's likely going to be a new release tomorrow.

Hey thanks for releasing so quickly...
This enables me to create the redirect lists, however how do we actually create the bulk redirects that use the list that we've created?
Thanks

Also once the list has been created, ive gone in to make a change to it, the plan works but it fails on apply with the following error:
\│ Error: error creating List Items: invalid value for redirect at position 0: invalid redirect status code (10047), invalid value for redirect at position 1: invalid redirect status code (10047), invalid value for redirect at position 2: invalid redirect status code (10047), invalid value for redirect at position 3: invalid redirect status code (10047), invalid value for redirect at position 4: invalid redirect status code (10047)

@KevinM2k I'm not able to reproduce it.  Can you post a tf file that reproduces the problem?

resource "cloudflare_list" "redirects" {
  account_id  = var.cloudflare_account_id
  name        =  redirects"
  description = "Legacy Redirecs"
  kind        = "redirect"

  dynamic "item" {
    for_each = local.redirects
    content {
      value {
        redirect {
          source_url           = item.key
          target_url           = item.value.target_url
        }
      }
    }
  }
}

Then modify one of the entires, and you should get the problem. The fix for this was to simply add the status_code as 301.
With regards to the actual creation of the bulk list, the docs in TF just doesn't mention how to use the redirect kind and the list_from option isn't available (is in api)

Thanks :)
On Wed, 13 Jul 2022, 10:31 Diogo Sousa, @.***> wrote:

Hi @KevinM2k https://github.com/KevinM2k. This should be fixed in the
new release. Let me know if you have any issues.
—
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/terraform-provider-cloudflare/pull/1700#issuecomment-1182991978,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACUAN7CJFTKJGGRVUBP4HLVT2EGZANCNFSM5Y3K2ZVA
.
You are receiving this because you were mentioned.Message ID:
@.***
com>


Add Cargo Packager support

Enable the bundling of the Verso Browser using Cargo Packager.

Now, we can bundle the Verso browser using Cargo Packager
cargo fmt is run to eliminate formatting issues.
Placeholder icon is used
Already tested on Linux packages ( AppImage )

I mentioned we could probably embed the resource files instead. I'm not fond of two different behaviors between debug and release.
Is there any problem when using something like include_bytes?

I mentioned we could probably embed the resource files instead

We can deal that separately I guess

I'm not fond of two different behaviors between debug and release.

Well, it is not different at all. We are just using resource resolver to resolve the resources in the build environment.
But if we want to embed the files, we can do that later.

What ended up happening here?

There were several build fails. And I would like to figure out https://github.com/versotile-org/verso/issues/21 and https://github.com/versotile-org/verso/issues/26.
I think it would be easier if we can focus on one platform only instead of bundling every platform.

I think we can revisit this feature again. All we need to worry is bundling the resource directory together.

I created an issue to follow the status: https://github.com/versotile-org/verso/issues/85
Since the PR's base is pretty old, I created another branch for this and added @naman-crabnebula as a co-author.


Major refactor of getting-started (w/shortcodes)

Pushed to https://kdf.csco.cloud
preview:

Per discussion with @dcwangmit01 , closing this in favor of #4


Change Strings to be quoted in the toString() representation of in-clause operations. Fixes #224.

I believe I addressed the feedback.
Agreed. New feedback incoming :grin:

Looks good. Thanks for the contribution. Merging.


biblatex release for 2.11 ?

Can we have a release of the matching biblatex-3.11 tds, please ?

Nothing should be released for biblatex 3.11/biber 2.11 yet as SOurceforge has upload issues which are blocking the release currently.

On Sat, Feb 17, 2018 at 09:56:52AM +0000, plk wrote:

Nothing should be released for biblatex 3.11/biber 2.11 yet as SOurceforge
has upload issues which are blocking the release currently.

Thanks.  I saw some of sourceforge was back, will wait until normal
service is resumed.

- Unseen Academicals


OOM when using Redis clustering

I'm using Bottleneck pretty extensively across three limiter ids that sync from different data sources. I'm using it for frequent data syncing across multiple scripts that sometimes run concurrently. Everything is working fine on my local environment where the load is low but when running on production, I'm getting these out-of-memory errors. Any suggestions on how to solve this issue other than bumping up max memory on the redis server?
limiter-id { ReplyError: ERR Error running script (call to f_081727f152360d42d3fac68bacc404106bcfa968): @user_script:87: @user_script: 87: -OOM command not allowed when used memory > 'maxmemory'.
    at parseError (/var/www/site/node_modules/redis-parser/lib/parser.js:193:12)
    at parseType (/var/www/site/node_modules/redis-parser/lib/parser.js:303:14)
  command: 'EVALSHA',
  args:
   [ '081727f152360d42d3fac68bacc404106bcfa968',
     3,
     'b_limiter-id_settings',
     'b_limiter-id_running',
     'b_limiter-id_executing',
     'iknao23dejl',
     '1',
     '60000',
     '1530868561182' ],
  code: 'ERR' }

Hi, thanks for using Bottleneck.
Version 2.5.1 was released a few days ago and it fixes a memory leak issue. If you're not already using 2.5.1, upgrading to it will most likely solve your issue.
However, if you're still seeing this error on 2.5.1, I need to ask you a few questions to debug the issue:

What is your Bottleneck config?
Are you using Groups?
Are you using JobOptions, if so, what are they?
Can you provide a rough estimate to the number of requests/minute are going to the Redis Cluster?

Thank you!

I've upgraded to 2.5.1 but also upgraded the redis server. I can't reproduce the issue at the moment but I'll re-open this if I do later.


New Package: ShipDigital.PullWatch version 1.0.1

Signed-off-by: Alessandro De Blasis<EMAIL_ADDRESS>for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.9 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

Hi! Not sure what the problem is, the error message is quite confusing:
Installation Validation
View raw log
12/4/2024 11:53:13 AM

Installation Verification

Status: Started
Task         : Installation Validation
Description  : Invoke an Azure Function
Version      : 1.220.0
Author       : Microsoft Corporation
Help URL     : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/azure-function
POST ?code=&
Request body: {
"operationId": "WinGetSvc-Validation-27-196181-20241204-1",
"buildId": "32404",
"planUrl": "https://dev.azure.com/shine-oss/",
"hubName": "build",
"projectId": "8b78618a-7973-49d8-9174-4360829d979b",
"planId": "5de84000-8200-4b99-b3a1-afc7de1701f7",
"jobId": "68997d86-8ece-5ae8-3ac5-ccdbfa458731",
"timelineId": "5de84000-8200-4b99-b3a1-afc7de1701f7",
"taskInstanceId": "b79910ce-dca5-5e27-ad7f-bd285eecb5a2",
"authToken": ***
"pullRequestNumber": "196181"
}
Response Code: OK
Response:
12/4/2024 11:56:43 AM

Installation Verification

Status: Completed
Result: Result: Failed

Automatic Validation ended with:

No errors to post.

(Automated response - build 899.)

Hi @stephengillie ! Do I have to do/change anything? Thanks!

@wingetbot run

Hello @deblasis,
The package manager bot determined there was an issue with installing the application correctly. Please check the application installs correctly. Once repaired, please push an update to your pull request.
Template: msftbot/validationError/installation/general

It installs locally using
winget install --manifest ./manifests/s/ShipDigital/PullWatch/1.0.1
without any issue

@wingetbot run

Verify:


Added Parade and 24 Heures

Only issue is both projects are still open. I don't think this will be a problem for sharing specific mints, but will probably not work well with the randomBot. Seeing as 24 Heures may be open a long time, I think it's worth it as there is a ton of sharing in Alexis' channel.

Thanks!
When asking for a random #? token from a project that is not yet fully minted, artbot currently may return "undefined" if it randomly chooses a token that has not yet been minted. I'll add an issue to update that logic because our project api does return invocations, which we could be using instead of Maximum Invocations.


Address weakness in notification/observer system

Over the years both @theod and I have been bitten some really difficult to track bugs stemming from pointers going out of scope or leaking in the observer and notification system.  This is still at the heart of our worst AudioGraph problems that we need to solve.
I have two insights that together could revolutionize our system:

From C++11 smart pointers -- Objects being observed are all shared pointers.  The objects that issue notifications can track them using weak pointers, which know when the underlying object goes away!

RAII -- An observer (let's call it TTObserver, assuming that name isn't taken) should be a class of it's own.  An object which wishes to observe another object should create an instance of TTObserver.  Then when it goes out of scope everything cleans up after itself neatly, unlike the wild west manual cleanup that happens currently (and problematically in some cases).

This implies that TTObject ref counting and other "smart pointer" stuff which we have implemented manually migrate to standard C++ smart pointers.

+1 for smart_pointers !
and I never seen any object called TTObserver. Is this class isn't relative to the TTCallback class (which can be used to observe notifications send from another class) ? is the TTCallback will still be useful ?

I also mention that for the time being if I change an attribute I have to take care to notify its observers (which is normal but a bit convoluted : see here in TTData::notifyObservers)).

And finally why we don't have TTNotification class for a TTObject like we have TTAttribute and TTMessage ?
this would match the Max concept of parameter, message and return and maybe allow to move them directly at the TTObject level (for the record we currently need to create a TTData with @service equal to "parameter", "message" or "return"). Of course this will implies to move all the TTData internal processings inside what we call the TTAttribute "properties" with a smart design pattern to allow to choose which kind of processing we want to make on the values (repetition filtering, ramping, ...).
is this make sense for you @tap ?


WarpCTC Plugin fails to compile on OSX with CUDA support

Environment info
Operating System: OSX
Compiler: Clang (Apple LLVM version 8.0.0 (clang-8<IP_ADDRESS>))
Error Message:
ers/sebastianb/git/warp-ctc/include -I/Users/sebastianb/Software/mxnet2/cub -DMXNET_USE_NVRTC=0 -MM -MT build/plugin/warpctc/warpctc_gpu.o plugin/warpctc/warpctc.cu >build/plugin/warpctc/warpctc_gpu.d
In file included from plugin/warpctc/warpctc.cu:7:
In file included from plugin/warpctc/./warpctc-inl.h:10:
/Users/sebastianb/Software/mxnet2/dmlc-core/include/dmlc/logging.h:11:10: fatal error: 'cstdio' file not found
#include <cstdio>
         ^
1 error generated.
make: *** [build/plugin/warpctc/warpctc_gpu.o] Error 1

Steps to reproduce
Change config.mk:
WARPCTC_PATH = /Users/sebastianb/git/warp-ctc
MXNET_PLUGINS += plugin/warpctc/warpctc.mk

and set USE_CUDNN = 1, USE_CUDA_PATH = /usr/local/cuda, USE_CUDA = 1.

@piiswrong: MXNet with GPU builds correctly on OSX now (after #6131). However, the WarpCTC plugin breaks the build.
I'm using the latest master of WarpCTC (https://github.com/baidu-research/warp-ctc).

Could you compile on ubuntu and do a fix?

Also please move ctc_loss to contrib asap

I've moved this op to contrib (#6154).
Yes, I'll use a ubuntu machine to do the fix.

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


possible issue in DPX info mapping

Hello,
This code looks like it is incorrectly mapping colorspace to transfer characteristics and vice-versa:
https://github.com/MediaArea/MediaInfoLib/blob/master/Source/MediaInfo/Image/File_Dpx.cpp#L814-L815

Ooooooooops. Wondering how it was possible for the author of such code (me) to do this mistake...
I guess it was not caught because most values are same.

Great catch!


AducIotAgent: error while loading shared libraries: libdeliveryoptimization.so.0 during installation

Hi
I'm in the process to install the device update feature on my Raspberry PI 3B. As I couldn't find Ubuntu 18.04 LTS anymore, I installed Ubuntu 20.04 LTS on the device. Then I followed the steps according to the documentation Device Update Agent Provisioning. Of course I replaced 18.04 with 20.04 where applicable.
Everything is fine up to the installation of the device update agent: IoT Edge Runtime installed, device connected to IoT Hub successfully.
Now I experience problems with the installation of the agent.
sudo apt-get install deviceupdate-agent
Expected Behavior
Installation of device update agent should end successful.
Current Behavior
The installation process fails with the following output (it also showed the same error when I started the installation the 1st time):
>> sudo apt-get install deviceupdate-agent
Reading package lists... Done
Building dependency tree
Reading state information... Done
deviceupdate-agent is already the newest version (1.0.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up deviceupdate-agent (1.0.1) ...
******************** Running /var/lib/dpkg/info/deviceupdate-agent.postinst configure ***********************
Setting directories and files...
Generate the template configuration file...
Generating the diagnostics configuration file...
Create data dir...
drwxrwx--- 4 adu adu 4096 Jan 18 09:37 /var/lib/adu
drwxrwx--- 2 adu adu 4096 Jan 18 09:37 /var/lib/adu/downloads
Register all reference update content handlers...
/usr/bin/AducIotAgent: error while loading shared libraries: libdeliveryoptimization.so.0: cannot open shared object file: No such file or directory
dpkg: error processing package deviceupdate-agent (--configure):
 installed deviceupdate-agent package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
 deviceupdate-agent
E: Sub-process /usr/bin/dpkg returned an error code (1)

Steps to Reproduce
I strictly followed the steps described in Device Update Agent Provisioning.
Device Information

Host OS: Ubuntu 20.04.5 LTS (Focal Fossa)
Architecture: arm64
Provisioning Method: NA

Logs
No logs are available in "/var/log/adu/"
Additional Information
I used Raspberry Pi Imager v1.7.3 to create the SD card. From there I selected the Ubuntu version 20.04.5 LTS (64-bit) for installation. This build of the OS was used on the device.

You might have a try with these 18.04 images :)
https://cdimage.ubuntu.com/releases/18.04/release/
But same problem as yours, I was looking for an answer too. Funny thing is that I figured this out once, but couldn't remember how I did it.

First try installing arm64 packages for DeliveryOptimization(DO) in this release tarball:
https://github.com/microsoft/do-client/releases/download/v1.0.0/ubuntu2004_arm64-packages.tar
wget https://github.com/microsoft/do-client/releases/download/v1.0.0/ubuntu2004_arm64-packages.tar
tar -xvf ubuntu2004_arm64-packages.tar
apt install deliveryoptimization-agent_1.0.0_arm64.deb libdeliveryoptimization_1.0.0_arm64.deb

# if you want to proxy apt traffic through DO
# apt deliveryoptimization-plugin-apt_0.5.1_arm64.deb

# if doing DO development
# apt install libdeliveryoptimization-dev_1.0.0_arm64.deb

Did not work for me, still same error.

You might have a try with these 18.04 images :)
https://cdimage.ubuntu.com/releases/18.04/release/
But same problem as yours, I was looking for an answer too. Funny thing is that I figured this out once, but couldn't remember how I did it.

Thanks, @jelalanne for the Ubuntu 18.04 link. I installed it on a 2nd Raspberry and were able to successfully install the device update agent (with the same ansible script as with Ubuntu 20.04). However, Ubuntu 18.04 is kind of old and I'd rather prefer at least Ubuntu 20.04.

I am working on 20.04 so you might want to wait for us to find a solution ;)

Did not work for me, still same error.

Same here. Also not working on Ubuntu 20.04.

Using do-client version 0.8.2 worked, but it's quite old. But it worked with installing deviceupdate-agent v0.8.2 too, not 1.0.1 which is the latest (annoyingly, its release file for arm64 is not available on the github release page). I remember now, that is what I was doing to overpass the problem last time.
`wget https://github.com/microsoft/do-client/releases/download/v0.8.2/ubuntu2004_arm64-packages.tar
tar -xvf ubuntu2004_arm64-packages.tar
sudo apt install -y ./deliveryoptimization-agent_0.6.0_arm64.deb ./libdeliveryoptimization_0.6.0_arm64.deb
wget https://github.com/Azure/iot-hub-device-update/releases/download/0.8.2/deviceupdate-agent_0.8.2_public_preview_arm64.deb
sudo apt install -y ./deviceupdate-agent_0.8.2_public_preview_arm64.deb`
NOTE: don't forget the relative path indicator './' before the file names, files might not be found otherwise.
IMPORTANT: @buentead just in case you didn't take that in account, installing ADU with IoT Edge is not enough. Don't forget to prepare the disk partitions to use A/B Update, install SWUpdate and everything. Sorry I don't have any tutorial, and that misses from MSFT documentation. I'm still trying to figure everything out.
@jw-msft Am I alright or did I say something wrong? Anything to advise?

Later today, I'll install arm64 ubuntu20.04 via RPi imager later and respond back on status of 1.0.1, which is recommended over 0.8.2

I tried out ubuntu 20.04.5 LTS on RPi3 via RaspberryPi Imager.
The problem is that 1.0.1 DU agent .deb package and AducIotAgent binary have an incorrect shared object dependency of libdeliveryoptimization.so.0.
Instead it should be libdeliveryoptimization.so.1  (NOTE: the .1 on the end).
For now, the workaround is to just a symlink to the .so.1 like this:
sudo ln -sf /usr/lib/libdeliveryoptimization.so.1.0.0 /usr/lib/libdeliveryoptimization.so.0
Here are the full steps I used to successfully install 1.0.1 DU agent:

Flash sd card using raspberry pi imager app https://downloads.raspberrypi.org/imager/imager_latest.exe
Login with ubuntu/ubuntu
Enter current password again for change password flow
Enter new password

$ cat /proc/cpuinfo | grep Model
Model           : Raspberry Pi 3 Model B Plus Rev 1.3

ubuntu@ubuntu:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Install DO from release asset packages:
Release v1.0.0 (2022-10-28) · microsoft/do-client (github.com)

wget https://github.com/microsoft/do-client/releases/download/v1.0.0/ubuntu2004_arm64-packages.tar
tar xvf ubuntu2004_arm64-packages.tar
sudo apt-get install ./deliveryoptimization-agent_1.0.0_arm64.deb
sudo apt-get install ./libdeliveryoptimization_1.0.0_arm64.deb
wget http://packages.microsoft.com/ubuntu/20.04/prod/pool/main/d/deviceupdate-agent/deviceupdate-gent_1.0.1_ubuntu2004_arm64.deb
sudo apt-get update --fix-missing
sudo apt-get install libcurl4-openssl-dev
Workaround for missing libdeliveryoptimization.so.0 error:  sudo ln -sf /usr/lib/libdeliveryoptimization.so.1.0.0 /usr/lib/libdeliveryoptimization.so.0
sudo apt-get install ./deviceupdate-agent_1.0.1_ubuntu2004_arm64.deb
create a valid /etc/adu/du-config.json

Seems to be working for me:
2023-01-20T00:27:27.3786Z 3760[3760] [D] Log file created: /var/log/adu/du-agent.20230120-002727.log [zlog_init]
2023-01-20T00:27:27.3803Z 3760[3760] [I] Agent (linux; 1.0.1) starting. [main]
2023-01-20T00:27:27.3804Z 3760[3760] [I] Supported Update Manifest version: min: 4, max: 5 [main]
2023-01-20T00:27:27.3820Z 3760[3760] [I] Health check passed. [HealthCheck]
2023-01-20T00:27:27.3824Z 3760[3760] [I] Initializing PnP components. [ADUC_PnP_Components_Create]
2023-01-20T00:27:27.3824Z 3760[3760] [I] ADUC agent started. Using IoT Hub Client SDK 1.7.0 [AzureDeviceUpdateCoreInterface_Create]
2023-01-20T00:27:27.3824Z 3760[3760] [I] Calling ADUC_RegisterPlatformLayer [ADUC_MethodCall_Register]
2023-01-20T00:27:27.3827Z 3760[3760] [I] Loading extension 'Content Downloader'. Reg file : /var/lib/adu/extensions/content_downloader/extension.json [LoadExtensionLibrary]
2023-01-20T00:27:27.4055Z 3760[3760] [D] Determining contract version for content downloader. [LoadContentDownloaderLibrary]
2023-01-20T00:27:27.4056Z 3760[3760] [D] Got Contract 1.0 for content downloader [LoadContentDownloaderLibrary]
2023-01-20T00:27:27.4057Z 3760[3760] [I] Initializing command listener thread [InitializeCommandListenerThread]
2023-01-20T00:27:27.4059Z 3760[3760] [I] Command register at slot#0 [RegisterCommand]
2023-01-20T00:27:27.4059Z 3760[3760] [I] Agent running. [main]
2023-01-20T00:27:27.4061Z 3760[3761] [I] Command FIFO file created successfully. [TryCreateFIFOPipe]
2023-01-20T00:27:27.4063Z 3760[3760] [I] Attempting to create connection to IotHub using type: ADUC_ConnType_Device  [ADUC_DeviceClient_Create]
2023-01-20T00:27:27.4064Z 3760[3760] [I] IotHub Protocol: MQTT [GetIotHubProtocolFromConfig]
2023-01-20T00:27:27.4065Z 3760[3760] [I] IoTHub Device Twin callback registered. [ADUC_DeviceClient_Create]
2023-01-20T00:27:27.4066Z 3760[3760] [I] Refreshing the handle for the PnP channels. [ADUC_PnP_Components_HandleRefresh]
2023-01-20T00:27:27.4066Z 3760[3760] [I] Successfully re-authenticated the IoT Hub connection. [ADUC_Refresh_IotHub_Connection_SAS_Token]

Does this work for armhf architectures to?

@jw-msft : Works perfectly on my side as well. Thank you so much for the detailed workaround. Very helpful indeed.
Shall I keep the issue open until the new package will be available?

@jelalanne I know that Deb10 on armhf works. I will try it with Ubuntu 20.04 32-bit (based on Debian 11) on rpi3 and let you know.
@buentead Yes, let's keep this issue open until we've updated the package.
@nihemstr Please update here once package is updated.

@jelalanne  microsoft/do-client and DU Agent do not build armhf .deb, but installing the Debian 10 armhf .deb works on 32-bit ubuntu 20.04.5 LTS server armhf.
NOTE: it also needs the libdeliveryoptimization.so.0 symlink workaround and we'll need to check and update all the assets at this point.  //cc @nihemstr
I was able to get it working with the following:
wget https://github.com/microsoft/do-client/releases/download/v1.0.0/debian10_arm32-packages.tar
tar -xvf debian10_arm32-packages.tar
sudo apt-get install ./deliveryoptimization-agent_1.0.0_armhf.deb
sudo apt-get install ./libdeliveryoptimization_1.0.0_armhf.deb
wget http://packages.microsoft.com/debian/10/prod/pool/main/d/deviceupdate-agent/deviceupdate-agent_1.0.0_debian10_armhf.deb
sudo ln -sf /usr/lib/libdeliveryoptimization.so.1.0.0 /usr/lib/libdeliveryoptimization.so.0  # Workaround
sudo apt-get install ./deviceupdate-agent_1.0.1_debian10_armhf.deb

Hello!
That didn't work for me...

I'm using Ubuntu 20.04.5 preinstalled server from cdimage
Maybe a step I missed?

Issues have been resolved with patch release 1.0.2  that was released today.
Please see this doc I created for steps to install the following from packages.microsoft.com after setting up /etc/apt/sources.list.d/:
https://github.com/Azure/iot-hub-device-update/blob/user/jw-msft/rpidoc/docs/agent-reference/how-to-install-deb-pkg-on-rpi.md
(which should eventually end up in develop branch here and in main here)

ubuntu20.04+aarch64 on rpi3
debian10+armhf on rpi3
and ubuntu20.04+aarch64 on rpi4:

PR is here for the doc -> develop: #377


add taxonomy to biom

If we want the analysis plugin to be able to generate Taxonomy plots, we need to add the taxonomy to the files. This step was left out this plugin by mistake.

Thanks @antgonza


Skins not being detected

Reports below:
https://privatebin.nexusmods.com/?0b1922a591fba93b#8uybQiBPdrbqQBGrLUNRQTBy9nrpiGRmuwZALyhwizRL
https://privatebin.nexusmods.com/?2b245451ae78b8f2#rJj5TaY3yzttPR62aDoqMucXZ9bMvR2AzzBJSanc7yZ
https://privatebin.nexusmods.com/?b9bc56dffe008ab4#AQLf7qvQY3WVXFdQa87DpkQLDwCmUVSjQFnByaune74A

Just to let you know, I can replicate this now (I was installing different files) and I think I have a fix for it, but need to do some more testing.

I overhauled how the detection works again in 0.3.0, so we should be detecting those (and a few of the other edge cases more reliably now). Going to close this now, let me know if you see more that aren't picked up properly.

I saw, and thank you! Only two skins are not being detected now:
https://www.nexusmods.com/acecombat7skiesunknown/mods/476
https://www.nexusmods.com/acecombat7skiesunknown/mods/932 -- This one may be because it uses a different loading method. I'm using the "Experimental" version.

Yep, because of how light weight packing works, I don't think I'll be able to support detection for them, likely ever.
As for that MTD skin, yeah I have no f'ing idea how that was packed and it's the only one I've seen like that. Nothing I can do for that one either, unfortunately.

Haha, no worries, thank you for all your work 👍


Hard code Google DNS

Per https://github.com/benbalter/site-inspector-ruby/issues/18.

@konklone any reason you'd see to not to this?

Yeah, I don't see any reason not to do it. Worst case, down the line DNS servers can become a configurable option in Ruby and over the CLI.


Support for emissive-only materials

This PR fixes two related problems:

https://github.com/AnalyticalGraphicsInc/cesium/issues/5838 - When a glTF 2.0 model does not have normals the color is black.
Emissive only materials would generate plain-gray shaders because processPbrMetallicRoughness only runs if material.pbrMetallicRoughness is defined. Effectively the emissive texture gets ignored.

The code follows @emackey's suggestion in https://github.com/AnalyticalGraphicsInc/cesium/issues/5838#issuecomment-380102060:

Lately I've been pondering whether Cesium could just show "unlit" materials (baseColor * occlusion + emissive) in the absence of normals.  It's technically not what the spec advises, but it's quick to implement and would get us visibility of models that are currently pitch black.

TODO :

[x] More testing
[x] Update CHANGES.md
[ ] Open a PR into gltf-pipeline

@lilleyse, thanks for the pull request! Maintainers, we have a signed CLA from @lilleyse, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.
:warning: I noticed that a file in one of our ThirdParty folders (ThirdParty/, Source/ThirdParty/) has been added or modified. Please verify that it has a section in LICENSE.md and that its license information is up to date with this new version. Once you do, please confirm by commenting on this pull request.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

I can confirm that this fixes it using the AGI HQ with an emissive-only texture.

Updated

@lilleyse Just FYI, my suggestion was poorly received by the rest of the glTF WG.  They would strongly prefer that engines do calculate the normal vectors, which shouldn't look bad once the rest of the 2.0 lighting issues are fixed.
That said though, certainly the glTF spec does not call for "pitch black", so, unlit isn't any more out of compliance than we are currently.  I think unlit would be a good stepping stone to have in place so long as normals are still on the roadmap somewhere.
It looks like glTF pipeline 1.0 does have automatic calculation of normals in a helper class, and that class was never upgraded to 2.0.

Yeah I guess generating normals is the right thing to do. It would make sense then to implement KHR_materials_unlit as soon as possible to support photogrammetry.
But I agree, that doesn't necessarily need to hold up this PR. We could keep #5838 open after this is merged.

Updated.

Travis apparently failed here.  Doesn't look like the fault of this branch, but it's hard for me to tell.

The PR-side passed, so it was definitely just a travis/build hiccup.

OK, thanks @mramato.  Merging.


Remove "Work in progress"

This implies that the code is not ready for use. I believe that this project is mature enough to remove this.

Sounds good to me :+1:


reverse entries in log

as requested in #414, all entries in the log are now shown in reverse order (latest first), unless the desired log format is json

seems like the failing checks are unrelated to the log?

yeah this looks good!


Bbox support

Adds support for providing bounding boxes and reading them in image queries

There will be test failures until the BE change is deployed

We need an update before tests pass to reflect renaming in the BE


Fixed annotation dragging behavior

Problem encountered without this change
Updating the position of any annotation on the map would cause dragging of another annotation to be stopped. We encountered this issue when trying to implement a polygon with draggable vertices.
Solution
Only stop the drag if the updated annotation is also the dragged annotation.

For me it makes sense to separate the two.

Are the unit tests expected to pass? :sweat_smile:

Are the unit tests expected to pass? 😅

At some point :)

May I ask how it works with releases? Should we expect those changes to be pushed to a maven repository at some point? innocent

@ovivoda: kindly pinging here? :slightly_smiling_face:


As a user who is new to this app, I want to have a tutorial for all the features so that I can learn how this app works quickly.

Acceptance Test:
-With a first time launch of the app.
-A tutorial pops up to guide through the uses of main features.


Test: Smoke test Microsoft auth on MSAL-node in VS Code Desktop - Round 2

Refs: https://github.com/microsoft/vscode/issues/178740 https://github.com/microsoft/vscode/issues/229415 https://github.com/microsoft/vscode/issues/229431

[ ] windows @mjbvz
[ ] windows @Yoyokrazy
[ ] macOS @jrieken
[x] linux @rzhao271

Complexity: 4
Create Issue

You must wait for this PR to be released: https://github.com/microsoft/vscode/pull/235048
A Microsoft Authentication extension based on MSAL is almost ready for prime time.
To enable it, apply this setting:
"microsoft-authentication.implementation": "msal"

and restart VS Code.
This release we have a ton of polish, but also, the adoption of the Native Broker on Windows. This means that on Windows, we can sign in via an Operating System flow, rather than going through the browser:

On macOS & Linux, it still gets the MSAL "goodness" but doesn't have a broker implementation... yet.
I'm gonna list a couple of extensions and features, and I'd like it if you'd try logging in to a few of them.

(built in) Settings Sync
(built in) Cloud Changes (fka Edit Sessions)
Remote Tunnels
Azure Repos
Azure Resources
Microsoft To Do (Unofficial)
Outlook (Unofficial)
Live Share
(Advanced) Fugio

Please try to log in with your corp Microsoft and also try to log in with your personal Microsoft account. Mix and match, do a few of one and then log out and do some of the other... your choice.
Additional stuff to check

Wait a few hours, are you still logged in?
When you reload the window, are you still logged in?
Using multiple windows does log in state get updated in the other windows (sign in and sign out)?
When you log out, does your account disappear from the account menu as it should?

Additional broker-related stuff for Windows testers

Does the auth window render on top of the window that you started the auth flow in? (we had issues early on where the OS dialog would show behind VS Code)
Trigger Fugio via the Command Palette in an Auxiliary Window (right click on a file and click "Move into New Window")

Does the OS dialog show above the auxiliary window?
If you go back to the main window and trigger it, does it show above that window?

On windows using a40fbb1ac10ad5c797d331eb75d1d99332ef9cbe, I still see it opening a browser for sign in:

This is for setting sync and I confirmed I have the setting enabled. Is there anything else I need to do to get the new flow?

Just used the login command from your unofficial outlook extension, seems to use the OS auth flow correctly. Attached a video in case I'm misinterpreting anything. (didn't finish the login flow bc finding that password seemed like a hassle)

Logged out of and into a variety of accounts personal and msft accounts, functionality all seems stable with msal auth. Reloads and multiple windows appear to be working on my end as well. Going to remove assignment but I'll file issues if I find myself logged out in the evening or tomorrow morning.

Ah... I'm sorry @mjbvz are you using an ARM Windows? This OS dialog behavior only shows up on x64. MSAL only supports this at this time


mat_phong 0 not working

i have the latest version of the config and when i put mat_phong 0 in the autoexec file it wont work it worked before i got the config but it wont work now please help
EDIT my full autoexec file is:
mat_phong 0
hud_combattext_batching 1
hud_combattext_batching_window 2.0
cl_updaterate 66
cl_cmdrate 66
cl_interp .033

As written in the installation instructions, your autoexec.cfg will be used. Instead, use a custom.cfg file.

it still wont work

if you need reference here's my full autoexec file
mat_phong 0
hud_combattext_batching 1
hud_combattext_batching_window 2.0
cl_updaterate 66
cl_cmdrate 66
cl_interp .033

Rename autoexec.cfg to custom.cfg which should be in /tf/cfg.

already tried that but it still wont work

Can you share a picture of your tf/cfg/ folder?

file:///C:/Users/Brandon/Pictures/Screenshots/Screenshot%20(1).png my .cfg folder

You have to upload the picture to a service like imgur and then link it here.

https://imgur.com/a/AMvcZ like this

Ok can you also share a screenshot of your custom folder?
Also what exact version of the config do you have? 6.4.2 or the latest beta, 6.5.0-b7?

https://imgur.com/a/dAjLs i think i have 6.4.2

Ah, you are using the ZIP installation method so you will have to go into the mastercomfig_exec/cfg folder and then open up autoexec.cfg. Then, go to the bottom and remove the // in front of exec custom.

Thanks for all the help it works now

Closes #34

fix #34


Fixing a couple of network plugin life-cycle mgmt issues

Fixes https://github.com/docker/docker/issues/29447 : Reference count is managed for network plugins using ACQUIRE and RELEASE mechanism in createNetwork and deleteNetwork.
Fixes https://github.com/docker/docker/issues/29471 : libnetwork remote driver init is modified to lookup active plugins and registered with drvRegistry
Fixes https://github.com/docker/docker/issues/29473 : Since plugin rm is not fully propagated to drvRegistry, we allowed overriding the drvRegistry map to cleanup stale plugin socket

cc @anusha-ragunathan @tiborvass

Please include https://github.com/docker/docker/commit/151d1cfb5775dcbd6b1eae616577a04ce3a10949 in this PR, since it is refcount related. If you are not inclined to, I can make a separate pr for that.

@anusha-ragunathan sure. picked up your change as well. With this we will also have docker plugin  disable honor the refcount. Thanks. PTAL.

@anusha-ragunathan Inclusion of your patch causes TestPluginVolumeRemoveOnRestart (and possibly others ?) to fail. Hence I backed off your commit. Since your commit is addressing a different issue of docker plugin disable honoring the refcount, it can go in its own PR. Could you please handle that ?

@mavenugo : I will open a new PR for moving refcount from remove to disable.

@mavenugo : https://github.com/docker/docker/pull/29599 opened. PTAL

👍 I built the binary of the PR and verified that #29447 #29471 #29443 have all been addressed. The code change in the pull request looks good to me as well (not a maintainer).
Note: I only tested with network plugin, not IPAM plugin.

DockerSwarmSuite.TestAPIServiceUpdatePort panic
10:16:28 goroutine 27751 [select, 5 minutes]:
10:16:28 net/http.(*persistConn).roundTrip(0xc420ae1100, 0xc420218360, 0x0, 0x0, 0x0)
10:16:28 	/usr/local/go/src/net/http/transport.go:1840 +0x93b
10:16:28 net/http.(*Transport).RoundTrip(0xc420b8c1e0, 0xc420b8c2d0, 0xc420b8c1e0, 0x0, 0x0)
10:16:28 	/usr/local/go/src/net/http/transport.go:380 +0x4ee
10:16:28 net/http.send(0xc420b8c2d0, 0x1bacc60, 0xc420b8c1e0, 0x0, 0x0, 0x0, 0x8, 0xc420495a78, 0x410318)
10:16:28 	/usr/local/go/src/net/http/client.go:256 +0x15f
10:16:28 net/http.(*Client).send(0xc420b83598, 0xc420b8c2d0, 0x0, 0x0, 0x0, 0xc420495a78, 0x0, 0x1)
10:16:28 	/usr/local/go/src/net/http/client.go:146 +0x102
10:16:28 net/http.(*Client).doFollowingRedirects(0xc420b83598, 0xc420b8c2d0, 0x1417908, 0x3, 0x1, 0x0)
10:16:28 	/usr/local/go/src/net/http/client.go:528 +0x5e5
10:16:28 net/http.(*Client).Do(0xc420b83598, 0xc420b8c2d0, 0x131dec6, 0x6, 0x0)
10:16:28 	/usr/local/go/src/net/http/client.go:184 +0x1ea
10:16:28 github.com/docker/docker/integration-cli/daemon.(*Daemon).StartWithLogFile(0xc421ab3e00, 0xc4200272b8, 0xc4219faf40, 0x2, 0x2, 0x0, 0x0)
10:16:28 	/go/src/github.com/docker/docker/integration-cli/daemon/daemon.go:303 +0xd9b
10:16:28 github.com/docker/docker/integration-cli/daemon.(*Daemon).StartWithError(0xc421ab3e00, 0xc4219faf40, 0x2, 0x2, 0x0, 0xc420393800)
10:16:28 	/go/src/github.com/docker/docker/integration-cli/daemon/daemon.go:209 +0x226
10:16:28 github.com/docker/docker/integration-cli/daemon.(*Daemon).Start(0xc421ab3e00, 0x1bb0b20, 0xc420adf1d0, 0xc4219faf40, 0x2, 0x2)
10:16:28 	/go/src/github.com/docker/docker/integration-cli/daemon/daemon.go:196 +0x53
10:16:28 github.com/docker/docker/integration-cli/daemon.(*Daemon).StartWithBusybox(0xc421ab3e00, 0x1bb0b20, 0xc420adf1d0, 0xc4219faf40, 0x2, 0x2)
10:16:28 	/go/src/github.com/docker/docker/integration-cli/daemon/daemon.go:325 +0x61
10:16:28 github.com/docker/docker/integration-cli.(*DockerSwarmSuite).AddDaemon(0xc42038d400, 0xc420adf1d0, 0x1bc0101, 0xc421ae09a8)
10:16:28 	/go/src/github.com/docker/docker/integration-cli/check_test.go:286 +0x255
10:16:28 github.com/docker/docker/integration-cli.(*DockerSwarmSuite).TestAPIServiceUpdatePort(0xc42038d400, 0xc420adf1d0)
10:16:28 	/go/src/github.com/docker/docker/integration-cli/docker_api_service_update_test.go:22 +0x57
10:16:28 reflect.Value.call(0x130ba80, 0xc42038d400, 0x1613, 0x131be85, 0x4, 0xc420b83f30, 0x1, 0x1, 0x1bff9e0, 0x1300020, ...)
10:16:28 	/usr/local/go/src/reflect/value.go:434 +0x5c8
10:16:28 reflect.Value.Call(0x130ba80, 0xc42038d400, 0x1613, 0xc420b83f30, 0x1, 0x1, 0xc420aabef0, 0xc420a3decf, 0x0)
10:16:28 	/usr/local/go/src/reflect/value.go:302 +0xa4
10:16:28 github.com/docker/docker/vendor/github.com/go-check/check.(*suiteRunner).forkTest.func1(0xc420adf1d0)
10:16:28 	/go/src/github.com/docker/docker/vendor/github.com/go-check/check/check.go:816 +0x6b8
10:16:28 github.com/docker/docker/vendor/github.com/go-check/check.(*suiteRunner).forkCall.func1(0xc420c59b90, 0xc420adf1d0, 0xc420218140)
10:16:28 	/go/src/github.com/docker/docker/vendor/github.com/go-check/check/check.go:672 +0x7c
10:16:28 created by github.com/docker/docker/vendor/github.com/go-check/check.(*suiteRunner).forkCall
10:16:28 	/go/src/github.com/docker/docker/vendor/github.com/go-check/check/check.go:673 +0x251

@anusha-ragunathan the test is timing out waiting for AddDaemon call to return. This doesnt seem related to this change, but we never know. I will investigate further.
@vdemeester do you know what might be going on ?

Daemon fails to start.
10:16:29 goroutine 27753 [syscall, 5 minutes]:
10:16:29 syscall.Syscall6(0xf7, 0x1, 0xb44, 0xc420c37100, 0x1000004, 0x0, 0x0, 0x7f37a835a8c0, 0xc4219fa020, 0x20)
10:16:29 	/usr/local/go/src/syscall/asm_linux_amd64.s:44 +0x5
10:16:29 os.(*Process).blockUntilWaitable(0xc421972810, 0xc42001a001, 0xc420a39e80, 0x43d48c)
10:16:29 	/usr/local/go/src/os/wait_waitid.go:28 +0xbc
10:16:29 os.(*Process).wait(0xc421972810, 0x130c9c0, 0xc420431310, 0xe13)
10:16:29 	/usr/local/go/src/os/exec_unix.go:22 +0xab
10:16:29 os.(*Process).Wait(0xc421972810, 0x1, 0x1, 0x86266f)
10:16:29 	/usr/local/go/src/os/doc.go:49 +0x2b
10:16:29 os/exec.(*Cmd).Wait(0xc420c31760, 0x16, 0xc420a39f98)   ---> daemon fails to start.
10:16:29 	/usr/local/go/src/os/exec/exec.go:434 +0x6d
10:16:29 github.com/docker/docker/integration-cli/daemon.(*Daemon).StartWithLogFile.func1(0xc420b7c4e0, 0xc421ab3e00)
10:16:29 	/go/src/github.com/docker/docker/integration-cli/daemon/daemon.go:268 +0x36
10:16:29 created by github.com/docker/docker/integration-cli/daemon.(*Daemon).StartWithLogFile
10:16:29 	/go/src/github.com/docker/docker/integration-cli/daemon/daemon.go:271 +0xa2e

The panic is the same as https://github.com/docker/docker/pull/27287#issuecomment-253873534. GetAll on pluginv1 in swarm mode is buggy. Need to understand why.

 Scan was scanning left over directories from previous tests. So it was waiting on activations from plugins that were not running anymore. Goes to show that we are not cleaning up properly after using pluginv1.
I've fixed it by cleaning up the Scan directories before calling the test. This is a pointed fix. The long term fix would be to add this in the TearDownTest and TearDownSuite sections of both DockerSuite and DockerSwarmSuite.
Fix available at
https://github.com/docker/docker/commit/15c3e82a06a7270357c0957b01a64dfbe65fb646

@anusha-ragunathan I agree. We need a better fix in the test infra to cleanup stale entries. I picked up your commit and started the build again.

@anusha-ragunathan same failures now seen on other plugin tests. I guess we have to fix this in a more generic fashion rather than a point fix at this point :(
alternatively, we can introduce a V2 only GetAllByCap function (or a bool to prevent v1 plugins to be scanned). For the case that we are trying to address here, we really dont care about the v1 plugins.

@anusha-ragunathan I added a temporary patch : https://github.com/docker/docker/pull/29556/commits/4b710fe5910320edec390f64db9ef4fd9e297b22 to skip plugin-v1 from being scanned. There is only 1 place the GetAllByCap is used today and hence this is the least impactful change for now. Once the tests are done, we can decide on what can be done...

Just as a data-point, skipping plugin-v1 scan using https://github.com/docker/docker/pull/29556/commits/4b710fe5910320edec390f64db9ef4fd9e297b22 solves the problem. It may not be an ideal fix. But atleast we know that the test-case is failing because of scanning (and failing due to the absence of) v1-plugin

@anusha-ragunathan another attempt and this time cleaning up a v1-plugin immediately after use in one of the swarm network tests (https://github.com/docker/docker/pull/29556/commits/1024517569fe096c5f022026dddf4b3275fb45a2). If this works, then we are good.

The approach of getting v2 plugins only in this case, sounds okay to me. Design LGTM.

@anusha-ragunathan updated with the new vendoring changes. fingers crossed on IT :)

The CI failures in TestPluginInstallImage are unrelated and is failing for multiple PRs now.

@anusha-ragunathan @tonistiigi @tiborvass could you PTAL ? the CI issues are unrelated.

SGTM
@mavenugo Needs rebase. Use  tonistiigi/test-docker-netplugin for the test.

@tonistiigi done. Its green now !

LGTM
@mavenugo would you mind opening this PR against 1.13 branch as well ? Not sure about the vendoring part.

@tiborvass yes. I will once this is merged in the master.

LGTM

@mavenugo done

@vieux @tiborvass cherry-picked : https://github.com/docker/docker/pull/29858


DLP

This adds DLP v2beta1 to google-cloud-python.

Waiting on CI; I am sure I will have missed something.

@jonparrott Baton to you once CI passes.

Merge away. I'll do the release in a separate PR.
Let's see if our bot will merge this time.
@dpebot will you merge when tests pass?

@lukesneeringer Is the cryptic dlp really the best name we can use here?  I see that it is used on cloud.google.com, so I guess the question is really moot.

@tseaver yeah, that's going to be the name. I agree three-letter acronyms aren't the best.

Agree with the complaint, and agree that it is not going to change.

It also does not help that the name itself is not great. It is titled "Data Loss Prevention" and it does a bunch of redaction, PII detection, etc.


Add new line EOF

Purpose
This PR adds the new line EOF that changes had done with https://github.com/wso2/analytics-solutions/pull/296

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


AE comments and edits

Hey @teresashchen and @pssstl (+ @datalorax),
This is absolutely fantastic work! I honestly couldn't find any code-related edits or suggestions to make. Your functions and plots were clear, concise, and descriptive. My one substantive recommendation, however, would be to include more text in between code chunks to clearly explain each step of your process. This will be especially helpful for providing descriptions of your plots to audiences that might be unfamiliar with biomechanics.
Further, I would think more about descriptive names to give to your functions (e.g., tidy_for_v).
Overall, this project is really fascinating — and I can't wait for you to apply a shiny dashboard to it. Amazing stuff! :)
Andrew

Nice review, Andrew!
Also, I notice this has a conflict with .DS_Store. I'd recommend always including that in your .gitignore or you will run into this, unfortunately.


Option to return to previous window

I am trying to understand this UI framework.
Thank for sharing it.
Would it be possible to return to a previously opened UI panel, like with a "back" or "close"?

Hey there,
By default, Windows have history and queue built in.  This means that if you open a window while another one is already open, and then do UIFrame.CloseWindow (or UI_Close() on the Window code itself, or via a button component rigged to call that method) it will automatically pop the previous Window that is opened in the History stack.
All windows that are not flagged as Force Foreground in their properties will enter a queue, and will be opened as soon as the current window is closed. Check Part 3 of the manual here regarding operating windows and the Addendum right below it regarding opening order.


[ko] kubectl debian install guide does not mention gnupg at all

en PR https://github.com/kubernetes/website/pull/45814/files

This looks closely similar (potentially duplicated) to PR #46605


[knob-framework] Add intermediate format OptionsNew

Intermediate format OptionsNew is intended to help interface between command line arguments, JSON config files, and (in the future) knobs.

This is the larger context for the knob framework changes: #434
I am trying to break it into reviewable smaller pieces


Register JwtProof2020 or warn users not to use this library

Register it here:

https://w3c-ccg.github.io/ld-cryptosuite-registry/
https://github.com/w3c-ccg/security-vocab

its 2021, where is the full IRI for JwtProof2020 ?
https://w3id.org/did/v1 does not define JwtProof2020...
https://www.w3.org/ns/did/v1 does not define ANY proof formats (only verification methods)....
You should review https://w3c.github.io/vc-data-model/#dfn-context
and define a context which you control, where you can define all your terms for your users... see:
https://w3c.github.io/did-spec-registries/#schnorrsecp256k1verificationkey2019
https://w3c.github.io/did-spec-registries/#gpgverificationkey2020
Feel free to register your extensions in did spec registries as well.

Thank you for being vigilant about @context issues.
We came up with JwtProof2020 as a means of defining a common data type that can be used by credentials and presentations once they've been parsed and verified. This data type would more closely match the w3c spec while allowing devs to work with JWT credentials.
I'm not sure if this is the right approach for this, and this is why it's not yet registered.
I'd appreciate any input on this matter.

Thank you for being vigilant about @context issues.
We came up with JwtProof2020 as a means of defining a common data type that can be used by credentials and presentations once they've been parsed and verified. This data type would more closely match the w3c spec while allowing devs to work with JWT credentials.
I'm not sure if this is the right approach for this, and this is why it's not yet registered.
I'd appreciate any input on this matter.

there is also https://w3id.org/jws/v1 and this thread on context splitting:
https://github.com/w3c-ccg/security-vocab/issues/88
If I can register what you are doing I will, I just don't understand why you need a proof.type for a JWT.. the header has the necessary information, and the vc-data-model does not describe type as being relevant to JWT.
If you want to use JOSE to produce linked data proofs, you can. If you want to use JOSE to produce JWT or VC-JWT you can.
https://w3c.github.io/vc-data-model/ does not refer to "JwtProof".

If no JWS is present, a proof property MUST be provided. The proof property can be used to represent a more complex proof, as may be necessary if the creator is different from the issuer, or a proof not based on digital signatures, such as Proof of Work. The issuer MAY include both a JWS and a proof property. For backward compatibility reasons, the issuer MUST use JWS to represent proofs based on a digital signature.

It seems like the best course of action would be to simply remove "JwtProof2021" and show examples of JWT's that were decoded, when you want a nice JSON view.
There is also https://github.com/decentralized-identity/did-jose-extensions which is supposed to help with JOSE / DID issues, and which also does not describe proof.type.
We don't use VC-JWT for anything, but we do support it as described in the vc data model in these tests: https://github.com/transmute-industries/vc.js/tree/master/packages/vc.js/src/fixtures/test-vectors/vc-jwt
Note that none of our tests have JwtProof because it's not described by the vc data model.
I am trying to tighten up all the connection points to DID Core which includes providing examples in DID Core.... The DID Core example also does not include JwtProof, https://w3c.github.io/did-core/#example-38-verifiable-credential-as-decoded-jwt
I am concerned that this library titled "did-jwt-vc" appears to have significant differences from both W3C standards, which are not documented.
It also seems to be mostly focused on secp256k1 and ethereum.
If the library is meant to remain generic and support jwt-vc, I would recommend following both standards (DID and VC) to the letter, and if you want to innovate, make it clear that the innovation is not registered / experimental.
You might also consider replacing did:ethr in examples to convey that these libraries are meant to be generic.
If these proposals are agreeable I am happy to help make them.

there is also https://w3id.org/jws/v1 and this thread on context splitting:
https://github.com/w3c-ccg/security-vocab/issues/88
If I can register what you are doing I will, I just don't understand why you need a proof.type for a JWT.. the header has the necessary information, and the vc-data-model does not describe type as being relevant to JWT.
If you want to use JOSE to produce linked data proofs, you can. If you want to use JOSE to produce JWT or VC-JWT you can.
https://w3c.github.io/vc-data-model/ does not refer to "JwtProof".

If no JWS is present, a proof property MUST be provided. The proof property can be used to represent a more complex proof, as may be necessary if the creator is different from the issuer, or a proof not based on digital signatures, such as Proof of Work. The issuer MAY include both a JWS and a proof property. For backward compatibility reasons, the issuer MUST use JWS to represent proofs based on a digital signature.

It seems like the best course of action would be to simply remove "JwtProof2021" and show examples of JWT's that were decoded, when you want a nice JSON view.
There is also https://github.com/decentralized-identity/did-jose-extensions which is supposed to help with JOSE / DID issues, and which also does not describe proof.type.
We don't use VC-JWT for anything, but we do support it as described in the vc data model in these tests: https://github.com/transmute-industries/vc.js/tree/master/packages/vc.js/src/fixtures/test-vectors/vc-jwt
Note that none of our tests have JwtProof because it's not described by the vc data model.
I am trying to tighten up all the connection points to DID Core which includes providing examples in DID Core.... The DID Core example also does not include JwtProof, https://w3c.github.io/did-core/#example-38-verifiable-credential-as-decoded-jwt
I am concerned that this library titled "did-jwt-vc" appears to have significant differences from both W3C standards, which are not documented.
It also seems to be mostly focused on secp256k1 and ethereum.
If the library is meant to remain generic and support jwt-vc, I would recommend following both standards (DID and VC) to the letter, and if you want to innovate, make it clear that the innovation is not registered / experimental.
You might also consider replacing did:ethr in examples to convey that these libraries are meant to be generic.
If these proposals are agreeable I am happy to help make them.

@OR13 I guess the intention of this was to produce JWT-based VCs together with the pre-transformed unsigned JSON-LD VC payload and having both as the result of the creation process. One of the reasons for this is to have simpler searching and querying for VCs by operating on the pre-transformed unsigned JSON-LD VC payload only rather than supporting two different formats and "data models". This can be useful if both JWT-based VCs and LD-Proof-based VCs live in the same data storage. I agree that Jwt2020 is unnecessary and we could probably drop that from the output as it creates the impression this is a specific LD-Proof. Also note that verifyCredential won't use any information other than the actual JWT for verification purposes.

@OR13 I guess the intention of this was to produce JWT-based VCs together with the pre-transformed unsigned JSON-LD VC payload and having both as the result of the creation process. One of the reasons for this is to have simpler searching and querying for VCs by operating on the pre-transformed unsigned JSON-LD VC payload only rather than supporting two different formats and "data models". This can be useful if both JWT-based VCs and LD-Proof-based VCs live in the same data storage. I agree that Jwt2020 is unnecessary and we could probably drop that from the output as it creates the impression this is a specific LD-Proof. Also note that verifyCredential won't use any information other than the actual JWT for verification purposes.

for making JWTs searchable as JSON, I would recommend simply storing them as decoded objects.... however that is an "internal" not a standards concern....
The following should all be true of a library that implements a standard:

the library uses the standard test vectors if they exist.
the library clearly explains methods that support the standard data model, and methods that expose internal or custom data models for usability.

I don't see any value other than confusing developers by including JwtProof2020, but it could be preserved by adding a note saying something like: "all though its not standard or required, we find adding this extra json member helpful"... assuming that including it produces valid JSON-LD, which is currently false.

for making JWTs searchable as JSON, I would recommend simply storing them as decoded objects.... however that is an "internal" not a standards concern....
The following should all be true of a library that implements a standard:

the library uses the standard test vectors if they exist.
the library clearly explains methods that support the standard data model, and methods that expose internal or custom data models for usability.

I don't see any value other than confusing developers by including JwtProof2020, but it could be preserved by adding a note saying something like: "all though its not standard or required, we find adding this extra json member helpful"... assuming that including it produces valid JSON-LD, which is currently false.

@OR13 Please see #56 as a potential solution to the lack of clarity.

If the library is meant to remain generic and support jwt-vc, I would recommend following both standards (DID and VC) to the letter, and if you want to innovate, make it clear that the innovation is not registered / experimental.

It is more about the lack of bandwidth to keep up with a shifting spec than innovation.

You might also consider replacing did:ethr in examples to convey that these libraries are meant to be generic.

Noted!

If these proposals are agreeable I am happy to help make them.

If you have time to spare for this, then definitely yes!

@OR13 Please see #56 as a potential solution to the lack of clarity.

If the library is meant to remain generic and support jwt-vc, I would recommend following both standards (DID and VC) to the letter, and if you want to innovate, make it clear that the innovation is not registered / experimental.

It is more about the lack of bandwidth to keep up with a shifting spec than innovation.

You might also consider replacing did:ethr in examples to convey that these libraries are meant to be generic.

Noted!

If these proposals are agreeable I am happy to help make them.

If you have time to spare for this, then definitely yes!

awesome looks like #56 is headed in the correct direction.

awesome looks like #56 is headed in the correct direction.


Feature Request: Infer React generic class type with JSX

TypeScript Version:  2.5.2
Code
In the following example, I have a generic component with generic props and it would be awesome if the type of the component was inferred when using JSX.
interface XProps<T> {
	x: T
	fn: (x: T) => void
}

class X<T> extends React.Component<XProps<T>, {}> {}

const x = (
	<X
		x={1}
		fn={x => {
			// x is not inferred as a number
		}}
	/>
)

Related is #6395. The thing is that this is actually sort of a higher order operation on types as well, so this is either very React-specific or difficult to do.

I see. I suppose we can follow along with the other issue though. Thanks!

For cross-referencing completeness, it seems that this sort of does work now, except for the bug demonstrated in #22636.


Write a Python program to convert string to alternatingcase

Description
Write a Python program to convert string to alternatingcase
Alternatingcase is a style of writing in which each letter is converted to its opposite case.
Input  : "hello world"
Output : "hElLo WoRlD"

How to contribute

Save the solution in convert-string-to-alternatingcase.py file
Add convert-string-to-alternatingcase.py file in program/convert-string-to-alternatingcase folder

@harshraj8843 I want to contribute to this issue.

Hey @Pal-Sandeep
You can comment !assign on any good first issue you want to contribute to, to be auto-assigned 🤗
!assign


Update to the release HT and re-release as v3.1.2

Draft PR to update the v3.1.1 release HT with fixed frequencies is here: https://github.com/broadinstitute/gnomad_qc/pull/206


cdc_acm.c: make cdc-acm configurable at runtime

This allows a developer to define a callback function in their
application code which takes a pointer to a configuration structure.
This structure will be used by the cdc-acm driver at device enumeration
time to generate the device descriptor. The callback function, if
defined, will be invoked at device enumeration, right before the
descriptor is generated.
In order to use this feature, you must enable
CONFIG_USB_CDC_ACM_CONFIGURABLE; for details on how to implement the
callback function once this option is enabled, see the 'help' section in
subsys/usb/class/Kconfig

Holding on merging for now, just double-checking the licensing is OK for the new file cdc_acm_config.h


Specificity translated in HTML but not CSS

Testing #172045
From a CSS file

From an HTML file

@aeschli it looks like in both cases, this is coming from:
https://insiders.vscode.dev/github/microsoft/vscode-css-languageservice/blob/3a69a36caa7c587806bb0392dd18660226dcd42b/src/services/selectorPrinting.ts#L454
right? I tried repro'ing this and couldn't.

@sbatten can you still see this? If yes, can you open the CSS Language Server output view. There should be a line in the beginning saying l10n: Configured to...`

I can still see this. Output:
l10n: Configured to file:///c%3A/Users/raymondzhao/.vscode-insiders/extensions/ms-ceintl.vscode-language-pack-fr-1.75.2023012510/translations/extensions/vscode.css-language-features.i18n.json

Part of the file itself:
"While loop that takes an expression and repeatedly outputs the nested styles until the statement evaluates to `false`.":"Pendant que la boucle prend une expression et génère à plusieurs reprises les styles imbriqués jusqu’à ce que l’instruction ait la valeur `false`.","[ expected":"[ attendue","[Selector Specificity](https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity): ({0}, {1}, {2})":"[Selector Specificity](https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity) : ({0}, {1}, {2})","] expected":"] attendue","absolute value of a number":"valeur absolue d’un nombre"

Ah, ok, so this is an issue with un untranslated string in the french language pack.

Let's wait until the next language pack is released and try again here.

Closing this to try again in endgame testing

Not sure if the language pack got updated because I see the same behaviour.

Yep still not translated:
https://github.com/microsoft/vscode-loc/blob/main/i18n/vscode-language-pack-fr/translations/extensions/vscode.css-language-features.i18n.json#L156
Let's take a different approach... I think the markdown syntax is messing with them. Just sent a PR out to only translate the words.

Given translations can be a slow process, I'm going to push this to March for verification.

The string still has not been translated for CSS files, but I'm not sure whether it's because the translation hasn't made it through yet.
I'm using the March 22 language pack.

still not translated by translators...


[C-Api] Fix the omitted Requires section in capi-ml-inference.pc

Because of the bug in the meson file, Requires section in
capi-ml-inference.pc is empty. It causes the compile-time error when
using ML APIs. This patch fixes this bug.
It is cherry-picking from main branch.
Signed-off-by: Sangjung Woo<EMAIL_ADDRESS>Self evaluation:

Build test: [*]Passed [ ]Failed [ ]Skipped
Run test: [*]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #113. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.


WIP - Per-input evaluator classes

WIP PR
Problem & Solution Description (including issue #)
This addresses issue #14
Initial commit is a scaffolding commit for pdf-vs-pdf evaluator, with a goal to use this as a template for the other types of evaluator classes.
Code Quality

[ ] My code follows the code style of this project
[ ] I have written unit tests or justified all instances of #pragma: no cover; in the case of a bugfix, a new test that breaks as a result of the bug has been added
[ ] My code contains relevant comments and necessary documentation for future maintainers; the change is reflected in applicable demos/tutorials (with output cleared!) and added/updated docstrings use the NumPy docstring format
[ ] Any breaking changes, described above, are accompanied by backwards compatibility and deprecation warnings

This has been merged in #98 , closing this PR


AppID/client secret support

in addition to the already available username/password authentication (which is not MFA compatible when running in a non-interactive context like a GH action), a new version of the underlying pac CLI will also allow AppID (ServicePrincipal) / clientSecret authentication for actions
Work is already in progress, but no definite ETA yet

@davidjenni any progress on this?

bump. need this.

bump. need this.


EDA: Add retry logic when re-reunning an expired job

This is related to compute jobs in eda. When a compute job is expired, and a request is made to rerun the job. A minio race condition causes a non ok response to be returned.
The idea is to have the client catch that response and try again, hoping the backend issue is resolved.
There is a utility function called fetchWithRetry somewhere in our code base 🙂.

compute platform bandaid to have 500 to stop on expired workspaces
https://github.com/VEuPathDB/lib-compute-platform/commit/252dd6de740ab3948b64f51f2c00a485e71bd090


⚠ Bofrost.lu has degraded performance

In d4aeddb, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1043 ms

Resolved: Bofrost.lu performance has improved in 5e800e1 after 7 minutes.


Integrate Auto Library

Integrate Auto Library with orchestrator to achieve the following:

Calculate semantic version bumps from PRs
Skip a release with the skip-release label
Generate changelogs with headers, authors
Use labels to create new changelog sections
Generate a GitHub release

Please assign this to me.

@jainrocks done.

Thanks @bhavinshah7

@jainrocks you will need this info while setting up Auto:
Owner/ServiceAccount: https://github.com/graphquilt-svc
email<EMAIL_ADDRESS>I am giving you push access, so you can create a personal github token to set up Auto.

Sure, I will start working on this

@bhavinshah7 Can I work on this?

I am already working on this :)

Raised a PR: https://github.com/graph-quilt/graphql-service-adapters/pull/11
I am facing one issue with the GH_Token
`✖  error     Received 404!
This usually because the GitHub token you're using doesn't have the correct permissions to the repo.
The token used with auto must have at least "write" permission to your repo (https://github.com/graphquilt-svc/https://github.com/graph-quilt/graphql-service-adapters ()) to create releases and labels.
You can check the permission for you token by running "auto info".
`
Getting the above error, can @bhavinshah7 / @ashpak-shaikh  please share the token or guide me in creating the same


ENH: Support "ResultImageName" in parameter file for transformix.exe

Addressing issue https://github.com/SuperElastix/elastix/issues/672 "Feature request: specify output name for file in transformix/elastix" by Sebastian van der Voort.

Tested locally, works for me 👍
I guess it should then also be supported by the elastix executable (when "WriteResultImage" is true), right?

LGTM, and indeed this should then automatically also work for the executable.

LGTM, and indeed this should then automatically also work for the executable.

Thanks @mstaring I'll replace the other occurrences of "result." with ResultImageName as well.


Bug in stack view?

I'm having a stack view crash while stepping through code with this error:
[stack]                                                                                [0x0127:00007FFF5FBFE210]Exception in thread Thread-1:
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/Library/Python/2.7/site-packages/voltron/core.py", line 563, in run
    self.update()
  File "/Library/Python/2.7/site-packages/voltron/core.py", line 517, in update
    self.callback(results)
  File "/Library/Python/2.7/site-packages/voltron/view.py", line 396, in render
    self.render(results)
  File "/Library/Python/2.7/site-packages/voltron/plugins/view/memory.py", line 218, in render
    super(StackView, self).render(results)
  File "/Library/Python/2.7/site-packages/voltron/plugins/view/memory.py", line 161, in render
    lines = pygments.format(self.generate_tokens(results), f).split('\n')
  File "/Library/Python/2.7/site-packages/pygments/__init__.py", line 66, in format
    formatter.format(tokens, realoutfile)
  File "/Library/Python/2.7/site-packages/pygments/formatters/terminal256.py", line 206, in format
    return Formatter.format(self, tokensource, outfile)
  File "/Library/Python/2.7/site-packages/pygments/formatter.py", line 95, in format
    return self.format_unencoded(tokensource, outfile)
  File "/Library/Python/2.7/site-packages/pygments/formatters/terminal256.py", line 209, in format_unencoded
    for ttype, value in tokensource:
  File "/Library/Python/2.7/site-packages/voltron/plugins/view/memory.py", line 94, in generate_tokens
    if x != six.indexbytes(self.last_memory, c + i):
  File "/Library/Python/2.7/site-packages/six.py", line 655, in indexbytes
    return ord(buf[i])
IndexError: string index out of range

I'm using continue in LLDB, hitting a repeated breakpoint to monitor a hot area of the stack where about 80 bytes are changed each cycle. Maybe some issue with the formatting logic.


[SPARK-35204][SQL] CatalystTypeConverters of date/timestamp should accept both the old and new Java time classes

What changes were proposed in this pull request?

CatalystTypeConverters is useful when the type of the input data classes are not known statically (otherwise we can use ExpressionEncoder). However, the current CatalystTypeConverters requires you to know the datetime data class statically, which makes it hard to use.
This PR improves the CatalystTypeConverters for date/timestamp, to support the old and new Java time classes at the same time.
Why are the changes needed?

Make CatalystTypeConverters easier to use.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

new test

@brkyvz @MaxGekk

Test build #137857 has started for PR 32312 at commit 4d6e4b6.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42387/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42387/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42387/

Test build #137857 has finished for PR 32312 at commit 4d6e4b6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137857/

Test build #137865 has started for PR 32312 at commit c8dbc1a.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42395/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42395/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42395/

+1, LGTM. GA passed. Merging to master.

Thank you, @cloud-fan .

Test build #137865 has finished for PR 32312 at commit c8dbc1a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137865/


Chat green

So on my bukkit mc server
when i chat it shows up in green and then a yellow : how do i fix it because my prefixes loud if i do /online and stuff

WTF


how to limit the memory usage of GPU like TensorFlow?

In TensorFlow, we can limit the memory usage of GPU like:
gpu_options = tf.GPUOptions(per_process_gpu_memory_fraction=0.7)
sess = tf.Session(config=tf.ConfigProto(gpu_options=gpu_options))
But, in chainer, what should we do if we want to limit the memory of GPU?

I think in chainer the size of GPU memory being used is dependent on your model and batch size, i.e., if you use a small model, it will only use a small amount of memory (like several tens or hundreds MBs).
On the other hand, by default TensorFlow will occupy almost all of your GPU memory no matter the size of your model. That's why it needs to have an option to set the fraction of GPU memory it can use.
In short, I think this function is not necessary for chainer. If your model costs a lot of memory in chainer, it means that you need to make your model small or decrease the batch size.

We'll introduce this feature in CuPy v7.
https://docs-cupy.chainer.org/en/latest/reference/memory.html#limiting-gpu-memory-usage


Integer equality simplification for Haskell backend

The Java bcakend normalizes terms to use ==K, and the Haskell backend uses the more specific ==Int. So semantic rules simplifying out equalities need to be specific per backend.

Shouldn't range rules for Java also use ==K ?


Review if BigIntger is the right datatype for DEX database

Closing since DEX, not on roadmap / important.


The version of cabal in 'master' is unsupported by ghc-mod under ghc 7.8

https://github.com/kazu-yamamoto/ghc-mod/issues/429

s/cabal-install/cabal/, sorry for the confusion.

@peti, only an enhancement and not a bug?  It breaks emacs (at least) integration..

..and it constitutes a regression from haskellpackages-OldG

Well, the bug is in ghc-mod. What are we supposed to do about it? As far as I can tell, the only thing we could do is downgrade to an old version of cabal-install. That's hardly desirable, is it?

The desirability depends on one's values, I guess, as you get to weigh emacs integration against "latest and greatest" features of cabal that were added in the span.
I know nothing about the added features in cabal, and so I am unqualified to judge in general.
Personally, the inability to use emacs in haskellng is.. a bit sad : -)

I use Emacs for Haskell development all time and the current git version of haskell-mode that we have in Nixpkgs works great. I don't miss ghc-mod much, to be honest. I guess we could provide cabal-install 1.18.x optionally for those who want it, though.

Do you get error message overlays and type hinting with haskell-mode?

Sure. haskell-mode also integrates nicely with flycheck.


cannot get prefix from the object to use in query function

im trying to get the prefix name from the object, but the object are protected, so i cannot do it.
i need it to run custom query, i need something like that:
$db -> query('TRUNCATE '.$db -> prefix.'sessions');
any solution?

You can use quotation syntax <table.column> for the query, and Medoo will handle the prefix and quotation automatically.
https://medoo.in/api/query

You can use quotation syntax <table.column> for the query, and Medoo will handle the prefix and quotation automatically.
https://medoo.in/api/query

but its truncate..
so i need to do something like this?
$db -> query('TRUNCATE ');


incorrect examples for transparentize and opacify in documentation

While playing around I found following incorrect examples in the sass reference.
http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html
copied from the examples:
The alpha channel of a color can be adjusted using the opacify and transparentize functions. For example:
$translucent-red: rgba(255, 0, 0, 0.5);
p {
  color: opacify($translucent-red, 0.8);
  background-color: transparentize($translucent-red, 50%);
}

is compiled to:
p {
  color: rgba(255, 0, 0, 0.9);
  background-color: rgba(255, 0, 0, 0.25); }

but it results as:
/*
Syntax error: Amount 50% must be between 0 and 1 for `transparentize'
*/

While
$translucent-red: rgba(255, 0, 0, 0.5);
p {
  color: opacify($translucent-red, 0.8);
}

would result as:
p {
  color: rgba(255, 0, 0, 0);
}

The documentation is as follows:
//transparentize
  transparentize(rgba(0, 0, 0, 0.5), 0.1) => rgba(0, 0, 0, 0.4)
  transparentize(rgba(0, 0, 0, 0.8), 0.2) => rgba(0, 0, 0, 0.6)
//opacify
  opacify(rgba(0, 0, 0, 0.5), 0.1) => rgba(0, 0, 0, 0.6)
  opacify(rgba(0, 0, 17, 0.8), 0.2) => #001

...yet it would be very useful to transparentize by 50% of the current value.
Is this an issue or just an incorrect example (as I assumed)?

Your assumption is correct in that the examples are just out of date. As you can see in the source, the function accepts numbers between 0 and 1, as noted by the error output. Updated the documentation and submitted a pull request.
That being said, it would be nice to provide the ability to punch in a percentage for those functions as well. I would assume  either that was the plan and it never made it from documentation to the actual function, or it was in the function at one point and has since been removed.

I would love really love it if all the major functions (opacify/rgba/etc) accepted percentages. Coming from LESS I'm really used to the fade(color, 40) syntax and I just think it's much much easier to use than to have to use .4 and such.
Plus it will make the LESS -> SASS transition easier for people wanting to switch, because that will reduce the amount of modifications needed to convert the code.

@nex3 or @chriseppstein: Did either of these functions previously accept percentages? I find it odd that a percentage would have made it into the documentation if they didn't at one point.
The way they are right now, in any case, doesn't translate to percentages. They don't actually multiply the starting alpha value but simply increase or decrease the original value by the value passed to the function.

if we have for example $translucent-red: rgba(255,0,0,0.5); and want $super-translucent-red to always be 50% opacity of $translucent-red we would have to use $super-trans-red: transparentize($translucent-red,0.25);
Now if we change to
$translucent-red: rgba(0,0,0,0.3);
$super-translucent-red would be   rgba(255,0,0,0.05);
but we want it to be  rgba(255,0,0,0.15);
so we need to change $super-translucent-red to $super-trans-red: transparentize($translucent-red,0.15);
So we would have to change 2 variables which kind of kills the idea.
Now this is only a simple example but I guess you can imagine how complex it could get if a lot of transparentize and opacify results depend on variables of the same kind

I agree that it would make situations like the one you describe here easier.
Not to get off-topic, but the above could be easily remedied:
$opacity: 0.3;
$trans-red: rgba(255, 0, 0, $opacity);
$super-trans-red: transparentize($trans-red, $opacity * 0.5);

body {
  color: $trans-red;
  color: $super-trans-red;
}

That is just about the way I am doing this. Of course we could use variables for anything .
$r: 255;
$g: 100;
$b: 55;
$a: 0.3;
$my-color: rgba($r, $g, $b, $a);

But it just doesn't feel right, does it?
So I would really like to see the percentage option in future releases
...BTT

Well in the meantime you can always do
@function fade($color, $opacity)
    @return rgba($color, ($opacity / 100))

Let me try to address all the points in this issue one at a time:

The documentation was incorrect and has been updated.

We use decimals rather than percentages for opacity because that's what CSS does. It would have been nice if CSS had started out using percentages, but at this point remaining consistent is the most important thing.

If you want to scale the opacity rather than adjusting it absolutely, you can use the scale-color function. For example, scale-color($color, $alpha: -50%) will make the color half as transparent as it was before.


Enable Writable cgroups for unprivileged containers

Currently, cgroupfs is only writable when containers are running in privileged mode. For unprivileged containers with cgroup v2 enabled, the cgroup interface (/sys/fs/cgroup) is mounted read-only by default, preventing containers from managing their own cgroup hierarchies. This PR enables the support for writable cgroups in unprivileged containers via CgroupWritable field.
Fixes #10924

Curious, what's the interface for the writable cgroup feature? For the cri-o implementation PR, the author exposes the functionality via annotation.

@dentiny We are exposing through the containerd config via the field CgroupWritable- discussion here

The code looks good, but needs an integration test

/retest

The code looks good, but needs an integration test

Thanks @AkihiroSuda! I have added the integration test which is passing but I see some of the jobs are failing due to the test TestFailFastWhenConnectShim

/ok-to-test

/retest

/test pull-containerd-k8s-e2e-ec2


[Bug]:Vulnerability category and status appear language switching failure under i18n

Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.

Version
1.0.2
Installation Type
Official SaaS Service
Service Name
DongTai-Core
Describe the details of the bug and the steps to reproduce it
Increase i18n of database related fields
Additional Information
No response
Logs
No response

fixed in v1.0.3


Reimplement Show dots only when needed

In 1.6.0 Dots where only inserted if needed
  Slick.prototype.buildDots = function() {
    var _ = this,
      i,
      dot;

    if (_.options.dots === true && _.slideCount > _.options.slidesToShow) {
      _.$slider.addClass('slick-dotted');

Please reimplemet this or make it configurable.
Version 1.7.0

Cool, would you like to make a PR?

+1 Please re-implement this.

@see #3080

Merged into master. Thanks!

dots seem to show when there is only 1 slide again in 1.8

I found there is that logic in slick.js. But if I use slick.min.js it doesn't work. So if you need this feature you can try to use slick.js instead of slick.min.js.

I found there is that logic in slick.js. But if I use slick.min.js it doesn't work. So if you need this feature you can try to use slick.js instead of slick.min.js.

Thank you! This worked for me. I had to manually minifiy the .js file but that's fine


Unsupported device Dyson 360 Eye heurist

After successfully completing Dyson cloud setup, I try to register my two Dyson discovered devices using the configure button, write ip address in the host field and then it fails with "Unknown error occurred" message.
Log file contains the following exception:
...
File "/config/custom_components/dyson_local/config_flow.py", line 151, in _async_get_entry_data
device.connect(host)
AttributeError: 'NoneType' object has no attribute 'connect'
My two devices are:
Dyson 360 Eye robot vacuum
Dyson Pure Cool
Full stack trace is:
Logger: aiohttp.server
Source: custom_components/dyson_local/config_flow.py:151
First occurred: 9:03:26 AM (1 occurrences)
Last logged: 9:03:26 AM
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request
resp = await self._request_handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 499, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 56, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 172, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 129, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 150, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 60, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 106, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 158, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 216, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/config/custom_components/dyson_local/config_flow.py", line 79, in async_step_host
data = await self._async_get_entry_data(
File "/config/custom_components/dyson_local/config_flow.py", line 151, in _async_get_entry_data
device.connect(host)
AttributeError: 'NoneType' object has no attribute 'connect'
Thanks.

Can you try running the get_devices.py directly from https://github.com/shenxn/libdyson? See if it can successfully get all information needed for your devices.

yes it works, I have executed a bash inside the container and then cloned the project, this is the result:
bash-5.0# python get_devices.py
Please choose your account region
1: Mainland China
2: Rest of the World
Region [1/2]: 2
Region code: IT
Email<EMAIL_ADDRESS>Password:
Verification code: 557193
Serial: D8R-EU-****934A
Name: Aspirapolvere
Device Type: 276
Credential: *******==
Serial: PT4-EU-K****A
Name: Studio
Device Type: 455
Credential: *****==
--
Today I will cleanup everything and try again the configuration process from scratch.
Thanks for your help.

I get the same error also after reinstalling everything from scratch, a couple more tests I did that can help your analysis:
I tried adding the device using HA Integration ha-dyson-local and filled all the fields using get_devices.py output, after a while it says "Failed to connect" and nothing in the logs.
Then I tried to connect from HA container to dyson vacuum and it worked, telnet <IP_ADDRESS> 1883 was successful.
Then I have installed mqtt explorer on my machine and successfully connected to <IP_ADDRESS> port 1883 using serial as username and Credential as password, I can see some topics like N223/initialconnection/status and N223/initialconnection/credentials

I noticed that there is a device of type 276 in your device list. What is the actual model of that device?

It is a Dyson RB02, aka Dyson 360 Eye heurist.
https://www.dyson.it/aspirapolvere/robot/dyson-360-heurist
Increased log to debug ant it says:
2021-03-14 09:31:48 INFO (MainThread) [libdyson.dyson_device] Connected to device D8R-EU-****A
2021-03-14 09:31:58 DEBUG (Thread-108) [libdyson.dyson_device] Disconnected with result code 0

Thanks. That device is actually not supported yet. And I couldn't find much info about the MQTT protocol of that device. This is the cause of the error log you see. It will be very helpful if you can help me figure that out. Can you try to connect to the device with MQTT explorer and send some commands through your Dyson mobile app and see if you can see some data under topics like */*/status and */*/command.

Sure will do, will send you an initial trace and then you can ask me more details.

I have sent you the first sample by email. Hope it helps.

@loscalinohacs I've received that. At a first glance, it seems that the protocol is pretty much the same as Dyson 360 Eye (N223). I should be able to add support to this very soon.

Great news! ok, feel free to ask me more details and tests if needed, thanks a lot.

Can you also do some operations like set power mode, run a full clean, stop, resume, back to home. You don't need to finish the clean. You can stop it as long as your robot starts moving. It'll be helpful if you can post some screenshot of the mobile app as well. Thanks a lot.

mqtt trace v2.0 and screenshots sent by mail, the protocol seems simple and I hope it did not change between models.

@loscalinohacs I released version 0.8.0. It now has basic support for 360 Heurist.

Updated to 0.8.0, configuration worked and 1 device successfully recognized, 3 additional entities recognized and working: battery_charging, battery_level and bin_full.
Well done!

That's a good news. I may add zone configured cleaning later through custom services but that is going to be pretty tricky. There is one thing I would like to know though, is your 360 Heurist has the WiFi SSID and password info on a sticker used for setup just like any other Dyson devices? If so, can you send me a photo or just information on it? It is related to #17.

there is a sticker with mac address but no wifi ssid/pass, it seems that this model uses the app to send wifi SSID and pass to the device.
The only interesting thing I have found on the sticker is an 8 digits code "nnnn-nnnn" that could be related with device pairing.
This video shows how robot is paired with local wifi using app:
https://www.youtube.com/watch?v=svDMkf3REss&ab_channel=Dyson

@loscalinohacs Thanks for confirm. Looks like heurist uses Bluetooth instead of the old WiFi AP. Closing this issue. I'll ping you for testing if I figured out how to implement the zone based cleaning.


Placing EM Rail Ejector Error

I'm getting the following error when I try to place an EM Rail Ejector:
Error Type: Star Parameter Mod
Game Time: 23:05:10
Detail Log: sub type: 1, star id: 31, star type: 1, star mass: 51936, star lum: 32829, threshold lum: 27
I've tried it on all planets in the system with the same error.

Where is the error shown?

Seems to have gone away.  Can't duplicate it.


When using groupBy, it causes redraw issues with angular carousels

See issue: https://github.com/smashingboxes/OwlCarousel2/issues/674
This has also been observed to occur with slick.js

Thanks @itsthatguy
Can you please provide some example(e.g: jsbin/fiddle) ?


NFT Exchange: Nestquest Egg Sale Animations

Description
This update adds lottie animations to the flows in the nestquest egg minting process.
Additionally, enhancements and UI bug fixes were made on the menu carousel and collection sweeper.
How has this been tested?
Tested in local dev env
Types of changes

[ ] Technical Debt (non-breaking change which removes unused code/assets)
[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The related ClickUp task has been linked to this PR
[x] The person creating the pull request is listed in "Assignees"
[ ] Change requires updated documentation

Task linked: CU-3rz4vz4 UI: Menu - "Comming Soon" Mispelling

Task linked: CU-3rz4y4b UI: Menu - "Sell" Menu Item Not Active

Task linked: CU-3rz6h4r UI: Nestquest Egg Sale Animations


[MINOR] Add git ignores for vscode and metals

What changes were proposed in this pull request?

Add new git ignore entries for a Visual Studio Code with Metals Scala plugin setup.
Why are the changes needed?

To not have to constantly stash and pop my gitignore changes when changing branches.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

It ignores all the VSCode/Metals files I have locally.

Can one of the admins verify this patch?

I could try, but I mostly use it because I'm not a java developer and use VSCode for all my Python/TypeScript/everything else I do. It's mostly just the Scala Metals plugin and that's it. And it can be kinda flaky sometimes

Never mind, @Kimahriman ~

From the Scala (Metals docks) you need to add .ammonite/

Didn't know about ammonite because I use bloop, added that as well

Merged to master


[Question] Record loss when using Delta format

Hi team,
We have a CDC pipeline which is used to update records in AWS S3. Multiple collections are processed in parallel using Python + Spark. Below are the version details:
Apache Spark: 3.0.2
Python: 3.6.9
Java: 1.8.0_312
Delta: 0.8.0
While performing data sanity checks we noticed that couple of records were missing in the table, though they were available on the previous day. We were able to access the same records using time travel option "timestampAsOf". The table in question does not have any delete operations. We only perform insert or merge at any given time. Below is the sample code for merge been used in this case.
partition_list = ["year", "month"]

DeltaTable
    .forPath(sc, delta_path)
    .alias("t")
    .merge(data.alias("s"), "((t.year = 2020 AND t.month = 1) OR (t.year = 2020 AND t.month = 2)) AND t.pkey_id=s.pkey_id")
    .whenMatchedUpdateAll()
    .whenNotMatchedInsertAll()
    .execute()

Properties set at spark level:
spark.databricks.delta.schema.autoMerge.enabled: 'true'
spark.delta.merge.repartitionBeforeWrite: 'true'
delta.compatibility.symlinkFormatManifest.enabled: 'true'
spark.databricks.delta.logRetentionDuration: '10 days'

Can you guide us how we can find the root cause of the issue as no exceptions are thrown at this stage.
Note: We have confirmed that this happens while writing to the Delta table, as this records are been pushed to kafka and postgres using the same dataframe at a later stage.

Is it possible the missing records in question were the records that matched your merge condition and were updated?
Otherwise it's difficult to track this down without a repro, is it possible you could share one?

This may be related to https://github.com/delta-io/delta/issues/527


Update mockito-scala-cats, ... to 1.16.0

Updates

org.mockito:mockito-scala-cats
org.mockito:mockito-scala-scalatest

from 1.14.8 to 1.16.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito" } ]

labels: test-library-update, semver-minor

Superseded by #89.