Verus crashes when returning closure type from a spec function

Hi Verus team,
I am trying to write some spec functions that take a (spec) closure as a function parameter and return another (spec) closure, like
spec fn transform_foo (foo: impl Fn(Cat) -> bool) -> impl Fn(Seq<Cat>) -> bool {
    move |cats: Seq<Cat>| foo(cats[0])
}

However, Verus crashes with
thread 'rustc' panicked at 'The verifier does not yet support the following Rust feature: type impl Fn(pervasive::seq::Seq<apis::Cat>)-> bool', rust_verify/src/rust_to_vir_base.rs:318:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
verification results:: verified: 0 errors: 0

It seems to me that Verus cannot accept function return value being a closure.
I am wondering what is the best way to write a spec function that takes a closure as an input parameter and also returns a closure?
Besides, is there a way to specify the closure as spec code?

This is something we'll hopefully fix soon - we're planning to add a type (not a trait) which can represents functions in spec-code. Then it will be possible to return a function type. (Although, in exec code, we will always be restricted by what Rust allows.)
In the meantime, my recommendation as a workaround would be to use a Set, e.g.,
spec fn transform_foo (foo: impl Fn(Cat) -> bool) -> Set<Seq<Cat>> {
    Set::new(|cats: Seq<Cat>| foo(cats[0]))
}

Thank you @tjhance !

Thanks for the report @marshtompsxd. I'm going to close this as a feature request for something that's planned. Feel free to re-open if you have other questions regarding this.


[#1441,#1442] Component Governance security vulnerabilities for moment 2.29.1

Fixes # 1441
Fixes # 1442
Purpose
This PR upgrades the moment dependency from 2.29.1 to 2.29.4 due to the CVE-2022-24785 security vulnerability.
Changes

Upgrade moment from 2.29.1 to 2.29.4.

The version in the PR's description doesn't match the version used.

Done, thanks!

/promoted 1457


add version match & package plugin

Codecov Report

Merging #14 (f4025d3) into master (2632f1d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #14   +/-   ##
=========================================
  Coverage     76.49%   76.49%
  Complexity      151      151
=========================================
  Files            22       22
  Lines          1468     1468
  Branches        228      228
=========================================
  Hits           1123     1123
  Misses          206      206
  Partials        139      139

Continue to review full report at Codecov.

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


Device not supported: Fairphone 5

App Version: 2.2.1 (21)
App Build Type: release
App Installer: com.google.android.packageinstaller
Software: Android 13 (33)
Light Levels: 1
Manufacturer: Fairphone
Brand: Fairphone
Model: FP5
Device: FP5
Board: Fairphone
Supported ABIs: arm64-v8a,armeabi-v7a,armeabi

@TBen2000 Thanks for the report.
Device will be excluded


Store subscription map in etcd

What this PR does / why we need it:
Store subscription map in etcd.
Which issue(s) this PR fixes:

Fixes #183
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Additional documentation:

Checklist:

[ ] Added relevant tests or not required
[ ] Didn't break anything

I will handle the tasks(#207, ...) that need to be handled earlier and reopen this.


Update 0088-adjustment-of-dao-utility-a-score.md

Changed the whole premise of HIP 88 to change the A factor to be calculated by taking the # of active devices multiplied by the onboarding fees those active devices paid.

Merging author's submission.


An unhandled NilObjectException occurred.

no other details were provided.
Packets.ParseSID_CHATEVENT%b%o<BNETSocket>s
Packets.Parse%b%o<BNETSocket>u1ss
Packets.ReceiveSID%%o<BNETSocket>
Packets.Receive%%o<BNETSocket>
BNETSocket.Event_DataAvailable%%o<BNETSocket>
Delegate.Invoke%%
Application._CallFunctionWithExceptionHandling%%o<Application>p
_Main
% main

Related: #39

I should refactor Packets.ParseSID_CHATEVENT


Create new popup box to list representatives using the Amplify app and the /representatives endpoints

In order to send a Twitter after someone makes a contribution, we can list them with the name. A button to send a Twitter message that tags them by using the Amplify/ProgramEquity API that will be extended in our project.

Error: the key you are using for the project does not have the API enabled.
{     "error": {         "code": 403,         "message": "Google Civic Information API has not been used in project<PHONE_NUMBER>93 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/civicinfo.googleapis.com/overview?project=125442285693 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.",         "errors": [             {                 "message": "Google Civic Information API has not been used in project<PHONE_NUMBER>93 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/civicinfo.googleapis.com/overview?project=125442285693 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.",                 "domain": "usageLimits",                 "reason": "accessNotConfigured",                 "extendedHelp": "https://console.developers.google.com"             }         ],         "status": "PERMISSION_DENIED",         "details": [             {                 "@type": "type.googleapis.com/google.rpc.Help",                 "links": [                     {                         "description": "Google developers console API activation",                         "url": "https://console.developers.google.com/apis/api/civicinfo.googleapis.com/overview?project=125442285693"                     }                 ]             },             {                 "@type": "type.googleapis.com/google.rpc.ErrorInfo",                 "reason": "SERVICE_DISABLED",                 "domain": "googleapis.com",                 "metadata": {                     "service": "civicinfo.googleapis.com",                     "consumer": "projects/125442285693"                 }             }         ]     } }

#23


Ensure pull requests aren't works-in-progress

This ensures that the pull request doesn't contain [WIP] in the title, i.e. it's a work-in-progress.

I had originally intended for this to do things like ensuring PRs have been reviewed by someone other than the author, but that appears to be better handled by GitHub's built-in branch protection configuration.

We've been using a rule of "someone else reviews the PR, but the submitter is the one who merges it"  That way, we don't end up stepping on each other's PRs when some people are working remotely. But, if you'd rather the approver merges, that would work, too.


gh-1658 - Implemented remove property method.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@92d8849). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             develop   #1677   +/-   ##
=========================================
  Coverage           ?   65.8%
  Complexity         ?    1956
=========================================
  Files              ?     802
  Lines              ?   25827
  Branches           ?    3322
=========================================
  Hits               ?   16995
  Misses             ?    7493
  Partials           ?    1339

Impacted Files
Coverage Δ
Complexity Δ

...va/uk/gov/gchq/gaffer/data/element/Properties.java
95.65% <100%> (ø)
0 <0> (?)

.../java/uk/gov/gchq/gaffer/data/element/Element.java
72.91% <100%> (ø)
0 <0> (?)

Continue to review full report at Codecov.

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


Ignore relative/local links?

Would it make sense to ignore relative and local links? And perhaps bitcoin links too?
[✖] /bots/
[✖] #past-sponsors
[✖] #page-content
[✓] https://twitter.com/algorithm_club
[✖] /resources/libraries-frameworks/#language
[✖] bitcoin:18WDyJFShLcLVCRyiEm3MijbCsBjcxG4mH?amount=0.025&label=Botwiki

While relative link support was added via issue #2, it wasn't working with local files. I wonder if this was what you are running into. I personally want relative links to be checked.

There are a few issues here and they're are all sort of related... relative links, local relative links, links with different schemes (e.g. bitcoin:) and hash links (e.g. #page-content). I've got some ideas, which I wrote on pull request #13, that I'll implement.

👍

I have the exact same problem. I tried the feature implemented in #13 but that didn't work for me. I need a command that works both locally and on CI (Travis). It needs to check recursively all md files inside a folder.
How can I do that?

Is this solved by #41 / with version 3.5.0?


Fixed #32645 -- Fixed QuerySet.update() crash when ordered by joined fields on MySQL/MariaDB.

Thanks Matt Westcott for the report.
Regression in 779e615e362108862f1681f965ee9e4f1d0ae6d2.
ticket-32645

@gasman Can you confirm that it works for you?

@felixxm Yup, just tested - all looks good and works well here.

Thanks y'all :confetti_ball:


Add ForwardsClientCallsAttribute in Get[Resource] method

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check for Azure.ResourceManager.AppConfiguration
API changes are not detected in this pull request for Azure.ResourceManager.AppConfiguration

API change check for Azure.ResourceManager.Resources
API changes have been detected in Azure.ResourceManager.Resources. You can review API changes here

API change check for Azure.ResourceManager.Compute
API changes are not detected in this pull request for Azure.ResourceManager.Compute

API change check for Azure.ResourceManager.KeyVault
API changes are not detected in this pull request for Azure.ResourceManager.KeyVault

API change check for Azure.ResourceManager.CosmosDB
API changes are not detected in this pull request for Azure.ResourceManager.CosmosDB

API change check for Azure.ResourceManager.EventHubs
API changes are not detected in this pull request for Azure.ResourceManager.EventHubs

API change check for Azure.ResourceManager.DeviceUpdate
API changes are not detected in this pull request for Azure.ResourceManager.DeviceUpdate

API change check for Azure.ResourceManager
API changes have been detected in Azure.ResourceManager. You can review API changes here

API change check for Azure.ResourceManager.Sql
API changes are not detected in this pull request for Azure.ResourceManager.Sql

API change check for Azure.ResourceManager.Monitor
API changes are not detected in this pull request for Azure.ResourceManager.Monitor

API change check for Azure.ResourceManager.Cdn
API changes are not detected in this pull request for Azure.ResourceManager.Cdn

API change check for Azure.ResourceManager.ServiceBus
API changes are not detected in this pull request for Azure.ResourceManager.ServiceBus

API change check for Azure.ResourceManager.Network
API changes are not detected in this pull request for Azure.ResourceManager.Network

API change check for Azure.ResourceManager.EdgeOrder
API changes have been detected in Azure.ResourceManager.EdgeOrder. You can review API changes here

API change check for Azure.ResourceManager.StoragePool
API changes are not detected in this pull request for Azure.ResourceManager.StoragePool

API change check for Azure.ResourceManager.Communication
API changes are not detected in this pull request for Azure.ResourceManager.Communication

API change check for Azure.ResourceManager.ExtendedLocation
API changes are not detected in this pull request for Azure.ResourceManager.ExtendedLocation

API change check for Azure.ResourceManager.WebPubSub
API changes are not detected in this pull request for Azure.ResourceManager.WebPubSub

API change check for Azure.ResourceManager.DesktopVirtualization
API changes are not detected in this pull request for Azure.ResourceManager.DesktopVirtualization

API change check for Azure.ResourceManager.ConnectedVMwarevSphere
API changes have been detected in Azure.ResourceManager.ConnectedVMwarevSphere. You can review API changes here
API changes
-     public class ErrorDetail {
-         public string Code { get; }
-         public IReadOnlyList<ErrorDetail> Details { get; }
-         public string Message { get; }
-         public string Target { get; }
-     }
-         public IReadOnlyList<ErrorDetail> ErrorDetails { get; }
+         public IReadOnlyList<ResponseError> ErrorDetails { get; }

API change check for Azure.ResourceManager.Hci
API changes are not detected in this pull request for Azure.ResourceManager.Hci

API change check for Azure.ResourceManager.Dashboard
API changes are not detected in this pull request for Azure.ResourceManager.Dashboard

API change check for Azure.ResourceManager.DnsResolver
API changes are not detected in this pull request for Azure.ResourceManager.DnsResolver

API change check for Azure.ResourceManager.HybridConnectivity
API changes are not detected in this pull request for Azure.ResourceManager.HybridConnectivity

API change check for Azure.ResourceManager.AppService
API changes have been detected in Azure.ResourceManager.AppService. You can review API changes here

API change check for Azure.ResourceManager.Storage
API changes are not detected in this pull request for Azure.ResourceManager.Storage

Close this one because the autorest change will be merged in #27962


luci-app-samba4: add support for new UCI option

add support for new UCI option "allow_legacy_protocols"

@jow- can maybe comment on this, but include ../../luci.mk is the standard form that should be used, I think.

Merged, thanks @Andy2244


Add initial documentation

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (110a1e2) to head (7dacd00).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          155       155
  Branches        18        18
=========================================
  Hits           155       155

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


workbench is not loading after running gulp serve.

Category

[x] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

Expected or Desired Behavior
Expecting to be presented with the local workbench to work with SharePoint Framework dev.
Observed Behavior
After setting up environment to start creating SharePoint Framework solutions I am unable to follow the step in the article https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/build-a-hello-world-web-part
Output from gulp serve -
Build target: DEBUG
[15:44:29] Using gulpfile C:\users\zachr\Documents\sharepoint\helloworld-webpart\gulpfile.js
[15:44:29] Starting gulp
[15:44:29] Starting 'serve'...
[15:44:29] Starting subtask 'configure-sp-build-rig'...
[15:44:29] Finished subtask 'configure-sp-build-rig' after 10 ms
[15:44:29] Starting subtask 'spfx-serve'...
[15:44:29] Starting server...
Starting api server on port 5432.
Registring api: /workbench
Registring api: /
[15:44:29] Finished subtask 'spfx-serve' after 544 ms
[15:44:29] Starting subtask 'pre-copy'...
[15:44:29] Finished subtask 'pre-copy' after 19 ms
[15:44:29] Starting subtask 'copy-static-assets'...
[15:44:29] Starting subtask 'sass'...
[15:44:31] Server started https://localhost:4321
[15:44:31] LiveReload started on port 35729
[15:44:31] Running server
[15:44:31] Opening https://localhost:5432/workbench using the default OS app
[15:44:32] Finished subtask 'sass' after 2.35 s
[15:44:32] Starting subtask 'tslint'...
[15:44:34] Starting subtask 'typescript'...
[15:44:34] [typescript] TypeScript version: 2.4.2
[15:44:34] Finished subtask 'copy-static-assets' after 4.16 s
Warning: no-duplicate-case rule is deprecated. Replace your usage with the TSLint no-duplicate-switch-case rule.
Warning: valid-typeof rule is deprecated. Replace your usage with the TSLint typeof-compare rule.
[15:44:36] Finished subtask 'tslint' after 4.31 s
[15:44:52] Finished subtask 'typescript' after 18 s
[15:44:52] Starting subtask 'ts-npm-lint'...
[15:44:52] Finished subtask 'ts-npm-lint' after 14 ms
[15:44:52] Starting subtask 'api-extractor'...
[15:44:52] Finished subtask 'api-extractor' after 577 μs
[15:44:52] Starting subtask 'post-copy'...
[15:44:52] Finished subtask 'post-copy' after 261 μs
[15:44:52] Starting subtask 'collectLocalizedResources'...
[15:44:52] Finished subtask 'collectLocalizedResources' after 4.49 ms
[15:44:52] Starting subtask 'configure-webpack'...
[15:44:53] Finished subtask 'configure-webpack' after 1.38 s
[15:44:53] Starting subtask 'webpack'...
[15:44:55] Finished subtask 'webpack' after 1.38 s
[15:44:55] Starting subtask 'configure-webpack-external-bundling'...
[15:44:55] Finished subtask 'configure-webpack-external-bundling' after 1.22 ms
[15:44:55] Starting subtask 'copy-assets'...
[15:44:55] Finished subtask 'copy-assets' after 29 ms
[15:44:55] Starting subtask 'write-manifests'...
[15:44:56] Finished subtask 'write-manifests' after 1.44 s
[15:44:56] Starting subtask 'reload'...
[15:44:56] Finished subtask 'reload' after 4.62 ms
I can browse to https://localhost:4321 and view the directories
I have tried running $env:NODE_NO_HTTP2="1" and the issue still persists.
Steps to Reproduce
Followed steps outlined in linked article above. Running gulp serve I am presented with the following error messages from their respective browsers.
IE 11 / Edge: Can't connect securely to this page - this might be because the site uses outdated or unsafe TLS security settings.
Firefox:  Secure Connection Failed - The connection to the server was reset while the page was loading.
Chrome: This site can't be reached - The connection was reset.
Node Version: v8.11.3
@microsoft/sharepoint version: 1.5.1
Let me know if you need any more information. Thank you for your help!

Figured it out, not sure what was happening or what was using the port but I changed the port number in serve.json file to 8080 and it worked after that.
Thanks,
Zach

For me it worked like that:

And after I ran
Npm run dev

Normally port 5432 is used by postgresql if you have it installed


Official release for Xcode 10.1

Hi,
Currently in my project we are using the tip of the master cause 1.1.0 doesnt build with xcode 10.1. Are there any estimates when there is going to an official release for xcode 10.1
any thoughts , @marmelroy ?
Thanks.

Perhaps the author didn't maintain the project again ,there are lots of issues ,by the way you can choose some other tool ,or you write the framework by yourself ,there is less framework about it ....I don't know why it's not fashion , @marmelroy perhaps doesn't have enough time to do it .

This is outdated now. I am always looking for additional contributors to help manage Zip. Please reach out on twitter if you're interested.


MonacoEditor: updates for current version of monaco-editor 0.27.0

The current version of monaco-editor is 0.27.0, updated by dependabot. It still works, but there are few new features that need to be added manually:

Update EditorOptions for version 0.27.0 of monaco editor, see https://microsoft.github.io/monaco-editor/api/interfaces/monaco.editor.istandaloneeditorconstructionoptions.html
Use primefaces type declarations directly from NPM
Update all dependencies, especially devDependencies, to their latest major version. Required a few minor adjustments to the webpack build
Fix serialization for org.primefaces.extensions.model.monacoeditor.*
Set new option domReadOnly in readonly mode, see https://microsoft.github.io/monaco-editor/api/interfaces/monaco.editor.istandaloneeditorconstructionoptions.html#domreadonly
Add new option overflowWidgetsDomNode to MonacoEditorInline, see https://microsoft.github.io/monaco-editor/api/interfaces/monaco.editor.istandaloneeditorconstructionoptions.html#overflowwidgetsdomnode

Excellent work as always. Thanks for the PR!


external flash format watchdog triggered during formating (IDFGH-8487)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
wtachdog timer got triggered during chip erase in external flash.

code flow
external flash init
unmount & format
mounting again for the purpose of writing to fresh chip then its showing failed to open file for reading with some backtrace

what may be the isuue

	void ext_flash_begin()
{
	/**************************************************************************/
		// Set up SPI bus and initialize the external SPI Flash chip
	    flash = example_init_ext_flash();
	    if (flash == NULL) {
	        return;
	    }
	    // Add the entire external flash chip as a partition
	    const char *partition_label = "storage1";
	    example_add_partition(flash, partition_label);
	   // List the available partitions
	    example_list_data_partitions();

	    // Initialize FAT FS in the partition
	    if (!example_mount_fatfs(partition_label)) {
	        return;
	    }
	    // Print FAT FS size information
	    size_t bytes_total, bytes_free;
	    example_get_fatfs_usage(&bytes_total, &bytes_free);
	    ESP_LOGI(TAG, "FAT FS: %d kB total, %d kB free", bytes_total / 1024, bytes_free / 1024);

	    /**************************************************************************/
}

	void ext_flash_unmount()
{
	 ESP_LOGI(TAG, "Unmounting EXT FAT filesystem");
	 ESP_ERROR_CHECK( esp_vfs_fat_spiflash_unmount(base_path1, s_wl_handle));
	 ESP_LOGI(TAG, "Done");
	 return;
}

bool example_mount_fatfs(const char* partition_label)
{
    ESP_LOGI(TAG, "Mounting FAT filesystem");
    const esp_vfs_fat_mount_config_t mount_config = {
            .max_files = 4,
            .format_if_mount_failed = true,
            .allocation_unit_size = CONFIG_WL_SECTOR_SIZE
    };
    esp_err_t err = esp_vfs_fat_spiflash_mount(base_path1, partition_label, &mount_config, &s_wl_handle);
    if (err != ESP_OK) {
        ESP_LOGE(TAG, "Failed to mount FATFS (%s)", esp_err_to_name(err));
        return false;
    }
    return true;
}

	void ext_flash_format()
{
	esp_flash_erase_chip(flash);

}

**function calls in order**

ext_flash_begin();
ext_flash_unmount();
ext_flash_format();
example_mount_fatfs("storage1");
memset(rd_fdata,0,sizeof(rd_fdata));
ext_flash_write("/extfile.txt",wt_data,32);
printf("before extformat \n :%s\n\r",wt_data);
ext_fat_read("/extfile.txt",rd_fdata,32);
printf("before extformat1 \n :%s\n\r",rd_fdata);

the read write and begin function is working
but  calling formating there is some isuue

I've hit this issue as well.
My non-ideal solution was to disable the Idle Task Watchdog during formatting, etc.
esp_task_wdt_delete(xTaskGetIdleTaskHandleForCPU(0));
esp_task_wdt_delete(xTaskGetIdleTaskHandleForCPU(1));

// call format code here

esp_task_wdt_add(xTaskGetIdleTaskHandleForCPU(0));
esp_task_wdt_add(xTaskGetIdleTaskHandleForCPU(1));

My non-ideal solution was to disable the Idle Task Watchdog during formatting, mounting, etc.

okay will check on that @chipweinberger thanks😊

This looks like a duplicate of #9212.

its been observed that there is significant change in heap size (xPortGetFreeHeapSize using this function) after calling the external flash using fat file system @igrr do you have any suggestion for this to use minimal heap area.

its been said that it is by default 4096 sector size which is the minimum erase size

esp_flash_t ext;
ext.chip_drv->sector_size=16;
will this do the functionality as its been said on that Do not call chip driver functions directly in other contexts.
is there any possible way to erase only specifc number of bytes from external flash instead of sectors of 4096 @igrr
`
/** @brief SPI flash chip driver definition structure.
*

The chip driver structure contains chip-specific pointers to functions to perform SPI flash operations, and some
chip-specific numeric values.

@note This is not a public API. These functions are called from the public API (declared in
esp_flash.h). They assume the caller has already validated arguments and enabled relevant protections
(disabling flash cache, prevent concurrent SPI access, etc.)

Do not call chip driver functions directly in other contexts.

A generic driver for generic chips and its related operations are defined in
spi_flash_chip_generic.h which can be used as building blocks for written
new/specific SPI flash chip drivers.

@note All of these functions may be called with SPI flash cache disabled, so must only ever access IRAM/DRAM/ROM.
*/
struct spi_flash_chip_t {`

You need to erase the whole sector, and then rewrite any bytes you want to keep.

I think there may be a helper function for this already, if you search ESP-IDF.

yes there is where multiples of sector size 4096 can be erased
here our need is that to erase only specific area is there any way to make it possible.

not possible.
This is a limitation of NAND flash


Missing Doc Step - Place centos8 iso in /build/isos

The centos8 iso needs to be placed in /build/isos/ prior to building. This step is missing from the documentation.

wonder if we can just have a curl command to fetch that?

@sethpeterson if possible, please make a PR with this fix

README updated in https://github.com/ManageIQ/manageiq-appliance-build/pull/399.
@sethpeterson If you add "Closes <issue #>" (like: Closes https://github.com/ManageIQ/manageiq-appliance-build/pull/399) in the git commit message in your PR, the referenced issue will be automatically closed by bot when PR is merged. FYI, for your future issues/PRs 😄


Treat README-THING.template

README-THING.template used to exist, but does not exist anymore. However, it is linked from README.md:

README-THING.template is replace by lib/uc/README.md and must be change to be self-contained

The reference from the main README.md can be removed.

Removed it at https://github.com/ultimate-comparisons/ultimate-comparison-BASE/commit/170783abcfcb517f3084668ab04f98a342c4cca1.


Fix for issue #7

Use existing paywall when creating the property if available. Fixes issue #7

Nice, thanks for a prompt fix :)


Its not working Any more ?

.on method is not working in the request :( !!!!!!!!!!
const _progress = progress(_request)                                 .on('progress', (stats) => {})                                 .on('error', (err) => {})                                 .on('end', () => {})                                 .pipe(fs.createWriteStream(filePath));

I don't thinks that's the correct syntax. You're not supposed to pass your request as a variable but actually call it in progress' parameter list, like so:
const _progress = progress(_request(url)).on('progress', ...


2 Frame Progress Bar

The progress bar for 2 frame isn't working, just displaying 0/100 until the next process starts.

For both frame set sub and two-frame sub


The litgpt evaluate command attempts to download config files from gated repos

If you want to evaluate a checkpoint that you previously downloaded, you may run into the issue that the checkpoint is of a model that is gated on huggingface:
litgpt evaluate --checkpoint_dir checkpoints/google/gemma-7b/ --out_dir out/evaluation --tasks mmlu --limit 10

2024-04-24:13:02:43,993 INFO     [huggingface.py:162] Using device 'cuda'
Traceback (most recent call last):
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/utils/_errors.py", line 304, in hf_raise_for_status
    response.raise_for_status()
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://huggingface.co/google/gemma-7b/resolve/main/config.json

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/transformers/utils/hub.py", line 398, in cached_file
    resolved_file = hf_hub_download(
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/utils/_validators.py", line 119, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1403, in hf_hub_download
    raise head_call_error
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1261, in hf_hub_download
    metadata = get_hf_file_metadata(
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/utils/_validators.py", line 119, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1674, in get_hf_file_metadata
    r = _request_wrapper(
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 369, in _request_wrapper
    response = _request_wrapper(
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 393, in _request_wrapper
    hf_raise_for_status(response)
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/huggingface_hub/utils/_errors.py", line 321, in hf_raise_for_status
    raise GatedRepoError(message, response) from e
huggingface_hub.utils._errors.GatedRepoError: 401 Client Error. (Request ID: Root=1-66293b34-73019ffb2df5e5921ce33e51;32481442-1f5b-4114-b085-a8a7af4c710c)

Cannot access gated repo for url https://huggingface.co/google/gemma-7b/resolve/main/config.json.
Access to model google/gemma-7b is restricted. You must be authenticated to access it.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/adrian/.conda/envs/lit-gpt/bin/litgpt", line 8, in <module>
    sys.exit(main())
  File "/home/adrian/repositories/lit-gpt/litgpt/__main__.py", line 143, in main
    fn(**kwargs)
  File "/home/adrian/repositories/lit-gpt/litgpt/eval/evaluate.py", line 102, in convert_and_evaluate
    model = HFLM(repo_id, state_dict=state_dict, device=device, batch_size=batch_size, dtype=dtype, local_files_only=True)
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/lm_eval/models/huggingface.py", line 188, in __init__
    self._get_config(
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/lm_eval/models/huggingface.py", line 453, in _get_config
    self._config = transformers.AutoConfig.from_pretrained(
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/transformers/models/auto/configuration_auto.py", line 928, in from_pretrained
    config_dict, unused_kwargs = PretrainedConfig.get_config_dict(pretrained_model_name_or_path, **kwargs)
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/transformers/configuration_utils.py", line 631, in get_config_dict
    config_dict, kwargs = cls._get_config_dict(pretrained_model_name_or_path, **kwargs)
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/transformers/configuration_utils.py", line 686, in _get_config_dict
    resolved_config_file = cached_file(
  File "/home/adrian/.conda/envs/lit-gpt/lib/python3.10/site-packages/transformers/utils/hub.py", line 416, in cached_file
    raise EnvironmentError(
OSError: You are trying to access a gated repo.
Make sure to have access to it at https://huggingface.co/google/gemma-7b.
401 Client Error. (Request ID: Root=1-66293b34-73019ffb2df5e5921ce33e51;32481442-1f5b-4114-b085-a8a7af4c710c)

Cannot access gated repo for url https://huggingface.co/google/gemma-7b/resolve/main/config.json.
Access to model google/gemma-7b is restricted. You must be authenticated to access it.

This happens because the eval harness wants the config file and goes through HF to download it:
https://github.com/EleutherAI/lm-evaluation-harness/blob/3196e907fa195b684470a913c7235ed7f08a4383/lm_eval/models/huggingface.py#L190-L194
This makes sense if the config file is not already downloaded, but in our case it is. So it is pointless to try to download it. I need to find a way to work around this because my token doesn't have access to all models. Probably needs to be addressed somehow upsream.

Hm yeah, this sounds annoying. In an ideal world, they would check for the file locally before attempting to download. Not sure, but could be wortwhile raising this issue in the harness repo


Improve error handling

At the moment, the code is wrapped in top-level try/catch blocks.
https://github.com/netlify/netlify-plugin-gatsby/blob/133cd048b998e231f719e8e70483375bb817d770/plugin/src/index.js#L76
This pattern would create the following problems:

This does not distinguish between plugin errors and user errors. Namely: every exception will be reported as a user error.
Prefixing error messages with Error message might be redundant
Since Bugsnag groups errors using the error message, all errors will be grouped together in Bugsnag, which will not allow us to see new error instances and might take away some of the benefits of error monitoring

Instead, most plugins usually follow the following pattern:

Wrap try/catch block around each specific function or line of code that might throw due to user errors
For each of those, use a descriptive error message for the specific case
Avoid wrapping the whole code with try/catch so that plugin bugs exceptions are propagated and reported as plugin errors

It seems like the only place where a user error might throw at the moment is when loading gatsby-config.js, i.e. this might be the only place which would need a try/catch block.

Done in #72.


SE2 support

This is a draft PR with support for the SE2 staging deploy. For now this one doesn't have multitenant support/tenant creation.

Obsolete


i18n(zh-cn): Update islands.mdx

Description (required)
Update islands.mdx
Note:
I found that there are some <h3> tags in headings from the English Version Docs in this page, so I replace them with markdown syntax ###.
Related issues & labels (optional)

#9240
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

zh-cn/concepts/islands.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

"群岛"是一个概念，当涉及到整体或者复数 islands 时，我们可以翻译为 "群岛"。
当 island 为单数形式时，并且场景描述 单个岛屿组件，不可翻译为 "群岛"

嗯嗯，我当时翻译的时候经历了3个阶段：

第一阶段是为了统一，索性都用“群岛”；
第二阶段是遵循单数用“岛屿”，而复数用“群岛“；
第三阶段是用全站搜索了“岛屿”后，发现没有群岛使用频率那么高，所以又回退到都用“群岛”了。


Issue/7722 agent executor code version caching

Description
closes https://github.com/inmanta/inmanta-core/issues/7722
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
- [ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in 9ac222108f377b600b6a6b7473a6eb4ef3749f27


Update to 1.4.1 and all datas are gone

I followed the instruction to update Alarmo
Manual: Download the latest release as a zip file and extract it into the custom_components folder in your HA installation, overwriting the previous installation.
and all settings are gone 👎

That is very strange.
All settings are kept in .storage/alarmo.storage, so they shouldn't be affected by updating.
From which version where you updating?
Is anything displayed in the logs?

That is very strange.
All settings are kept in .storage/alarmo.storage, so they shouldn't be affected by updating.
From which version where you updating?
Is anything displayed in the logs?

Hi nielsfaber,
i update from 1.4.0
One I replaced the Alarmo folder and reset HA. All codes, users, sensors and settings are gone. It is like when I first installed this :(

Hi nielsfaber,
i update from 1.4.0
One I replaced the Alarmo folder and reset HA. All codes, users, sensors and settings are gone. It is like when I first installed this :(

Can you check the .storage/alarmo.storage file?
It is only deleted when you uninstall the integration from HA (by Configuration -> Integrations), so your data could be still there.

Can you check the .storage/alarmo.storage file?
It is only deleted when you uninstall the integration from HA (by Configuration -> Integrations), so your data could be still there.

sorry where would it be?
this is all i have:

sorry where would it be?
this is all i have:

The .storage folder is on top level (so not in custom_components)

The .storage folder is on top level (so not in custom_components)

I don't think i have it then :-|

I don't think i have it then :-|

here it is

here it is

This is indeed where the file should be.
It is not affected by replacing the alarmo directory in the custom_components.
The file will only be deleted by going to Configuration -> Integrations and clicking delete for Alarmo (or reload).
For every change you make in the configuration, the file will be saved (with 10 seconds delay).
I have no idea how the file disappeared for you.
I guess it has nothing to do with the update of the component.
Is there anything printed in the logs that could give some help?

This is indeed where the file should be.
It is not affected by replacing the alarmo directory in the custom_components.
The file will only be deleted by going to Configuration -> Integrations and clicking delete for Alarmo (or reload).
For every change you make in the configuration, the file will be saved (with 10 seconds delay).
I have no idea how the file disappeared for you.
I guess it has nothing to do with the update of the component.
Is there anything printed in the logs that could give some help?

I just deleted all at once and reinstall Alarmo from HACS.
version is still 1.4.0 and there is no alarmo.storage file. Do I have to create this file?

I just deleted all at once and reinstall Alarmo from HACS.
version is still 1.4.0 and there is no alarmo.storage file. Do I have to create this file?

The alarmo.storage file is created/updated 10 seconds after you make a change to the configuration.
If it doesn't, then we have a bug to investigate (but i haven't heard of anyone else with these problems).

The alarmo.storage file is created/updated 10 seconds after you make a change to the configuration.
If it doesn't, then we have a bug to investigate (but i haven't heard of anyone else with these problems).

Thanks a lot for your time. I have just tried and saw this file.

Thanks a lot for your time. I have just tried and saw this file.

No problem.
Sorry about your data loss.
Hope it’s a one time incident.
Take care to backup that storage file so you won’t lose the data again.

No problem.
Sorry about your data loss.
Hope it’s a one time incident.
Take care to backup that storage file so you won’t lose the data again.

I had the same issue after updating from 1.3... Alarmo died on me as well. Any luck sorting this one out?


make it send every files in the download, documents, image and video folder

just like the title said, yes, most people save their files in those locations

Not a bad idea, will keep it in mind.


Fix/virtual input properly expose include dirs for local builds

Hi @bramoosterhuis, do we need to expose build interface also through the library ? Actually I thought to make it private and clear the dependency from the users side.


Fix Http and Websocket compiler plugin NPE failure

Purpose

$subject

Fixes #17639
Approach

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

Samples

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

Remarks

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

Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

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

[ ] Increased Test Coverage
[ ] Added necessary documentation

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

Codecov Report

Merging #17640 into master will decrease coverage by 4.93%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #17640      +/-   ##
==========================================
- Coverage   19.76%   14.82%   -4.94%
==========================================
  Files          51       46       -5
  Lines        1336     1214     -122
  Branches      214      193      -21
==========================================
- Hits          264      180      -84
+ Misses       1058     1020      -38
  Partials       14       14

Impacted Files
Coverage Δ

composer/packages/tracing/src/ToolBar.tsx

composer/packages/tracing/src/TraceList.tsx

composer/packages/tracing/src/DetailView.tsx

composer/packages/tracing/src/TraceLogs.tsx

composer/packages/tracing/src/index.ts

Continue to review full report at Codecov.

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


Revert "Add lateinit and dynamic keywords"

Reverts mathiasfrohlich/vscode-kotlin#7

Thanks again for the contribution.
Will preform some tests and then publish.

It is now Live
Thanks for the contribution


change Taphath range and tuning tab in k-time

kTaphath?
holup! wouldn't some of the GENs be able to do that?
also the table morphing ops? wanna look into those

ooo ftslice!

ugh this shit is messy! I can just go with a tablekt (tablexkt if we're gonna keep in mind #19) and give her extra range inputs..
(1 meal later)
okay, yeah definitely going with range arrays (overloaded version). but still not sure about the k-time table (the switching tables)..

different pitch range for each step! epico!
so it's gonna be a Taphy that optionally accepts 2 range arrays, and.. oh..
Taphath, Taphathkt, Taphath3, Taphath3kt.. nooooo! and an overloaded version for each! aaaa! what have I done!?
or we can just leave the cubic iterpolation stuff for now? oo add it as an extra optional parameter for them all? no need to have diff versions! just add it as a o input, it won't break older stuff

overload Taphath to take range arrays
copy those two definitions into Taphathkt and change the table reading part

with that we have taphy that can change range and/or tuning table in k-time (so long as the tables are of the same length)
I'll do the interpolation stuff later and in it's own issue

the reason we can't just have them all just take k-time tables is the it would break all the older stuff that takes an i-time table, and it would break if the user (my ass a few days later) just wants to use an i-time table (usual, no switching biz)
Imma go watch she-ra!

hbout another overload that takes a kfn instead of ifn? would that work? it would mean 2 overloads (this and a range arr version of it) but still the same opcode! 4 versions in one! and we just add those interpolation inputs to all 4, no need for extra opcodes! I need to study this k-time function tables biz though

tablekt seems fun! you could store the table numbers (returned by ftgen) in an array for example and switch between them using a trigger for example and store the active one's number in a k-time variable, which will be the input given to taphy, allowing you to switch keys/scales/removing or adding certain notes to the scale (all this in performance time)
this is fascinating! I'm in heaven!

now there's no need to make different tables with different ranges, I can just make a big 10 octave one and limit my instances

I love you, taphy 💜


Rename ConfiguratorFactory to ContainerAdapterFactory

This somehow got missed.

Blocked by https://github.com/tomphp/config-service-provider/pull/37.

@tomphp
:+1:


bump confluent version to fix CVE-2024-26308 CVE-2024-25710

Kafka Schema Registry Client has been reported with following vuln  CVE-2024-26308
CVE-2024-25710 due to vulnerable dependencies.
fixes: #32675
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Thanks for starting on this change! Can you try to resolve the precommit issues?

on it, I had troubles reproducing the issue.

PreCommit Xlang Generated Transforms

@johnjcasey can you help me dig error messages for KafkaIOT tests (e.g link to gcp console with this test..) Failing check is not giving too many detals.

Run Xlang_Generated_Transforms PreCommit 3.9

Run Xlang_Generated_Transforms PreCommit

Run Xlang_Generated_Transforms PreCommit

I've run ./gradlew :sdks:python:test-suites:direct:crossLanguageWrapperValidationPreCommit --info locally and I don't have any errors. Is it flaky?

Run Xlang_Generated_Transforms PreCommit

ok, found why we have checks failing - fix in flight here - #33353

Can you update the PR name / description? this looks like a revert from 7.6 to 7.5


Decrease thumbnail upstream timeout and add timing logs for thumbnail requests

Fixes

Fixes #4570 by @sarayourfriend
Description

This PR decreases the thumbnail upstream request timeout as discussed in the linked issue. It also decreases the timeout for the HEAD request for the extension to the same default value. Finally, it adds timing logs for both these requests so we can further evaluate appropriate timeouts for each. For example, hopefully we can decrease the HEAD request timeout significantly (like 0.5 seconds at least). But, because the analysis in the linked issue was done with timings of the entire thumbnail request, it's not possible to know which part of the request actually takes 4 seconds. Therefore, the total timeout of outbound requests is now 8 seconds, which is still way lower than the 25 total seconds and still a good improvement in line with the goals of the issue.
To facilitate request timing in any circumstance we might want it, I've created an aiohttp TraceConfig to log timing with context variables we've used so far. This only affects requests that configure themselves to activate the timing logs, as verified in the unit tests for the new trace config. This generalises the functionality added in #4508 for dead link checks, and therefore is able to replace that original implementation. As such, you'll see the code to manually time those requests is gone now, replaced by the trace config version. Because of that, I've also removed the separate timeout status we were caching before. This is safe for existing data because we check for specific live status codes when using the cached data, and never actually referred to the difference between the timeout and general error statuses returned from _head except when inserting them into the cache.
Testing Instructions

All existing unit tests must continue to pass without modification.
Run the API locally with ov just api/up. Open the logs with ov just logs web and make thumbnail requests and see the timing logs are present. Follow the testing instructions from #4508 and confirm they still work. The logs produced in this PR should be identical to the ones described in the linked PR, including the same contextual information, as well as provider, which was added later in #4598.
Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[N/A] I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
PRs) or the media properties generator (ov just catalog/generate-docs media-props
for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

I thought I had created an issue to investigate the extension timings, but I'll do so after merging, and include looking at both timings, not just the extension timings.


Some question about the version of Animatediff used in experiments

Hello, I would like to ask this side of the Modelscope T2V and Animatediff are what version, is it sd v1.5 v2 or v3 version, or based on sd-xl build?

Thank you for your interest! Both Modelscope T2V and Animatediff use sd v1.5, which are the latest official releases. Details about the models are provided in the appendix of our paper, feel free to have a look.


[vendor change] Add B3 codec to Jaeger tracer to enable mixer trace to be included in the application trace - and extended zipkin test to check for the mixer span

Cherry picked from #5116 as suggested by @douglas-reid here.
Note: the vendor change from dep ensure has resulted in more than just the jaeger/zipkin dependency being added, it has resulted in a number of unused (I assume) dependencies being removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hklai
Assign the PR to them by writing /assign @hklai in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @objectiser. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/assign @douglas-reid

/ok-to-test
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: douglas-reid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [douglas-reid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@objectiser: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
f7ff03df5f47d4bf0a894476328667efb7a991cb
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@objectiser: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
f7ff03df5f47d4bf0a894476328667efb7a991cb
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-unit-tests.sh
f7ff03df5f47d4bf0a894476328667efb7a991cb
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfo-envoyv2-v1alpha3
/test istio-unit-tests

@objectiser: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
f7ff03df5f47d4bf0a894476328667efb7a991cb
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfo-envoyv2-v1alpha3

@objectiser: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
f7ff03df5f47d4bf0a894476328667efb7a991cb
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@objectiser: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
661ad95bd5333a64353b704f34ca570a3a5895d3
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@douglas-reid All the required tests seem to have passed, but the Submit Queue seems dependent upon the circleci/racetest passing - which it doesn't seem to be doing on most recent PRs - so would you be able to manually merge this?

closing this PR as we are merging master into 0.8


docs(samples): add update table cmek

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[X] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[X] Ensure the tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[X] Appropriate docs were updated (if necessary)

https://source.cloud.google.com/results/invocations/179efcdc-fae0-41de-9417-85c4d6287cb7/targets/github%2Fjava-bigquery%2Fsamples%2Fsnapshot%2Ftarget%2Ffailsafe-reports/tests failure

https://source.cloud.google.com/results/invocations/179efcdc-fae0-41de-9417-85c4d6287cb7/targets/github%2Fjava-bigquery%2Fsamples%2Fsnapshot%2Ftarget%2Ffailsafe-reports/tests failure

Fixed #622


[5.1][CodeCompletion] Completion support for static subscript

(Cherry-pick of #24180 into swift-5.1-branch)
rdar://problem/49131687

@swift-ci Please test


download hybridnet chart online

Pull Request Description
Describe what this PR does / why we need it
Use online hybridnet helm chart to build ackdisro images with specified version.
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

lgtm


v3.4.3 release prep

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Version pre for v3.4.3 bumping tag in in VERSION cloudbuild.yaml dependencies.yaml workspace_status.sh
Signed-off-by: Adolfo García Veytia (Puerco<EMAIL_ADDRESS>Which issue(s) this PR fixes:
None
Special notes for your reviewer:
/cc @justaugustus @saschagrunert @cpanato
Does this PR introduce a user-facing change?
NONE

/lgtm


Profile B not implemented

Hello,
while I was trying to implement profile A and profile B schemes, I changed the configuration in free5gc-ue.yaml in UERANSIM and chose protection scheme 1 and profile A was implemented successfully.. when I tried profile B, I got the following error:

So profile B is not implemented in free5gc? I'm wondering because I saw public and private key corresponding to profile B in udmconfig..
Thank you in advance..

Hello,
The free5GC had implemented Profile B in UDM.
However, the reason for "Protection Scheme 2 not implemented" was produced by UERANSIM; you can refer to this line.


Add "stackwalk_version" to the JSON schema?

socc-pair keeps pulling this value down now. I'm not sure if this was something @willkg was working on and didn't finish, or something he hacks into the JSON as a post-processing step, but it's not something we actually produce.
I do like the idea of the JSON containing some versioning info, as this tends to be helpful for maintaining a stable schema that users can manage updates to. We also currently always publish all the crates in this repo with lockstep versions, so minidump-processor and minidump-stackwalk do always agree on the version.
That said, I would like us to have some ability to distinguish between "published" releases and prereleases (random commits). Something like "stackwalk_version": "0.9.8-alpha", so that there's some hint that the user has a non-standard copy and the semantics of the format are a blur between two versions (possibly with transient breaks!).

If there's some macro or whatever to get the version from the Cargo.toml, perhaps the "post release" commit should update everything to NEXT_VERSION-alpha.
e.g. the tree looks like:

some_random_commit: "minidump-stackwalk 1.0.2-alpha"
1.0.2 release: "minidump-stackwalk 1.0.2"
post release cleanup commit: "minidump-stackwalk 1.0.3-alpha"

I would need to experiment with this a bit.

If there's some macro or whatever to get the version from the Cargo.toml, perhaps the "post release" commit should update everything to NEXT_VERSION-alpha.

You're already using one :slightly_smiling_face: :
https://github.com/luser/rust-minidump/blob/d8b246d6a75348c5341859cf5edfa4148a6a973a/minidump-stackwalk/src/main.rs#L27

I like cargo-release for automating the whole version bump-tag-commit-version bump + cargo publish cycle. I don't think I've tried it with a workspace like this, so it's worth verifying that it works OK, but I've found it to be a huge time saver for other crates like sccache:
https://github.com/mozilla/sccache/blob/18614d55aa7b646b5d3ab323c5f68b29b1f5a12b/Cargo.toml#L3
https://github.com/mozilla/sccache/commit/6b6d2f7d2dceefeb4f583712aa4c221db62be0bd#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542
If you suspect you're going to wind up using arbitrary versions from master in prod (this feels inevitable), you might also want to stick the git rev in there for pre-release versions. (IDK where the binaries that Socorro uses are being built? You could just pass the rev in an env var if desired.)

Yeah we're already using arbitrary version in prod. Will appends some metadata to get more detailed versions strings in socorro like
minidump-stackwalk 0.9.6 aef123eaef23 (2021-11-12)

Socorro doesn't depend on the format of that string at all. It's structured that way because I figured we'd have questions like:

which specific version did this processing?
oh, but we don't pin to versions, we pin to commits, so which commit did this processing?
how old is that commit?

I'm game for whatever you want to populate it with. Plus Socorro can always augment that with additional details if we want it to do that.
Also, I stuck the data in the json_dump along with the rest of the stackwalker output because Socorro runs minidump-stackwalk on all the minidumps and this was the best way to keep the metadata with the data it was meta-ifying. That's not set in stone--we can change it.
I have another bug for rethinking the schema for a "processed crash" that better splits out metadata around how it was ingested from actual data so it's clearer what came from where and it's easier to work with. I think working on that is a bit further out, but these sorts of problems are all related.

It's an excellent thing to have because you definitely run into situations where something looks broken but you're pretty sure it was fixed at some point, so you can verify whether the version with the fix was in use.

The super duper magic is that it's indexed in Elasticsearch so we can reprocess all the crash reports that were processed with version XYZ which takes so much risk out of minidump-stackwalk issues.


Bug when inputting GitHub handle (?)

I just submitted a job... and I got this upon submitting, when I included a github handle: {"success":false,"data":["github_handle"],"rawError":{"_smErrorCode":"INVALID_FIELDS","data":["github_handle"]},"errorCode":"INVALID_FIELDS"}
When I deleted the github handle (on Eriol's suggestion), the form submitted correctly.

My best guess is that file staticman.yml in the jobs repo is missing github_handle from its allowedFields, it should be added. So it currently reads:
   allowedFields: ["organization", "org_url", "compensation",
                   "paid_details", "title", "description", "deliverables",
                   "how_to_apply", "links", "tags", "status", "date_posted",
                  "layout", "rate", "role"]

But should be:
   allowedFields: ["organization", "org_url", "compensation",
                   "paid_details", "title", "description", "deliverables",
                   "how_to_apply", "links", "tags", "status", "date_posted",
                  "layout", "rate", "role", "github_handle"]

I can submit this as a PR to jobs repo. Looks like this is hosted on Heroku though, who can deploy/update it? Or is it updated automatically from the repo?

@Ian2020 I think you've got much more chance of someone reviewing the PR if you submit to the jobs repo. Looks like a solid proposal to me and I think you'll get more help via a PR 😄

Pretty sure this is the same issue as this: https://github.com/opensourcedesign/opensourcedesign.github.io/issues/119

Thanks @Erioldoesdesign, PR submitted to jobs as suggested.

Looks like a recent job was submitted ok and included a GitHub handle: https://github.com/opensourcedesign/jobs/pull/661. As OP already resubmitted their failed job without a handle I think this can be closed.


JSHint reports error for failing to recognize statement labels inside the catch (e) {}

Consider:
function labelExample() {
    "use strict";
    var i;
example:
    for (i = 0; i < 10; i += 1) {
        try {
            if (i === 5) {
                break example;
            } else {
                throw new Error();
            }
        } catch (e) {
            continue example;
        }
    }
}

JSHint reports:
Line 12: 'example' is not a statement label.
JSLint reports:
Line 12: unexpected continue.
Continue may or may not be necessary in this case but no matter what the contents of the catch are definitely within the same scope and have access to the loop label.

This is fixed in #2435 and I added a test to #2468


GAction does only work with ugly cast

# https://wiki.gnome.org/HowDoI/GAction
# https://developer.gnome.org/gtk3/stable/GtkApplicationWindow.html#GtkApplicationWindow.implemented-interfaces
# GtkApplicationWindow implements AtkImplementorIface, GtkBuildable, GActionGroup and GActionMap.
# but we need an ugly cast for GActionMap
#
import gintro/[gtk, glib, gobject, gio]

proc saveCb(action: SimpleAction; v: Variant) =
  echo "saveCb"

proc appActivate(app: Application) =
  let window = newApplicationWindow(app)
  app.addWindow(window)
  window.show
  let action = newSimpleAction("save")
  discard action.connect("activate", saveCB)
  addAction(cast[ActionMap](window), action)###
  let button = newButton()
  button.label = "Save"
  button.show
  window.add(button)
  button.setActionName("win.save")
  showAll(window)

proc main =
  let app = newApplication("org.gtk.example")
  connect(app, "activate", appActivate)
  discard run(app)

main()

Fixed, see
https://github.com/StefanSalewski/gintro#gaction


[bug]: border-border styling not applying to the component

index.css file:

shadcn component using border-border styling:

Output using border-border styling:

shadcn component using border styling:

Output using border styling:

Isn't the styling should be like border for border-border or i am mistaken?
Affected component/components
Every components that used border-border styling
How to reproduce
...
Codesandbox/StackBlitz link
https://stackblitz.com/edit/vitejs-vite-4zwmdh?file=src%2FApp.tsx
Logs
No response
System Info
Browsers

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

“border-boder” is the styling for the color of ”border”
I think “border boder-boder” would be correct to achieve the behavior you want

“border-boder” is the styling for the color of ”border” I think “border boder-boder” would be correct to achieve the behavior you want

So it is not a bug?, because i tried to use a old version for shadcn and it did work as example with Output using border styling thing

“border-boder” is the styling for the color of ”border” I think “border boder-boder” would be correct to achieve the behavior you want

So it is not a bug?, because i tried to use a old version for shadcn and it did work as example with Output using border styling thing

I don't know if it's a bug, but if you just use “boder”, the logic below will turn it into “border boder-boder”
https://github.com/shadcn-ui/ui/blob/a2abc4ad958c06260600a2b977dfe320e1388ab8/packages/shadcn/src/utils/transformers/transform-css-vars.ts#L138


Plugins - add info about entrypoint requirements

When distributing a plugin (e.g. via PIP) the setup.py file needs to define a list of entrypoints according to a specific standard.

@matmair could you write something brief for this in the "getting started" docs for plugins?


Docker images are using 1.0.0-alpha.4 but v1.0.2 is available

Here:
https://github.com/mantlenetworkio/networks/blob/main/docker-compose-mainnetv2.yml#L12
is using 1.0.0-alpha.4
but from the docker registry we can find a more up to date image:
https://hub.docker.com/layers/mantlenetworkio/op-geth/v1.0.2/images/sha256-662ede9f3e8fa5021d9d126c66301826ef02feb07d6c8ce13b4c2a247126c90b?context=explore
Which one to use?
I suggest to make this repo a bit more up to date with latest?

Apparently v1.0.2 is for Sepolia. Use the default images specified in docker-compose-mainnetv2.yml


Fix street and housenumber in Erie County, NY

My coworker @riordan might have messed this one up :P

Classic @riordan.

This is what happens whenever I try to do a computer science.
On 12/2/15 15:10, migurski wrote:

Classic @riordan https://github.com/riordan.
—
Reply to this email directly or view it on GitHub
https://github.com/openaddresses/openaddresses/pull/1467#issuecomment-161418852.


Allow to recv and send file descriptors when using EpollDomainSocketChan...

...nel.
Motiviation:
When using domain sockets on linux it is supported to recv and send file descriptors. This can be used to pass around for example sockets.
Modifications:

Add support for recv and send file descriptors when using EpollDomainSocketChannel.
Allow to obtain the file descriptor for an Epoll*Channel so it can be send via domain sockets.

Result:
recv and send of file descriptors is supported now.

@trustin please review

First pass done. Please ping me for another pass.

@trustin ping :)

Cherry-picked into 4.0 (495fa6be3cf725a0abc68cefd71116ab718fff3e), 4.1 (3030b4afe30f96b59807b24bd4f5250d41de283f) and master (cabecee127264e53acaa093ca45d3900b138b881)


Disable incremental compilation to resolve issue 252

Apologies for the onslaught of pull requests lately, but this one should resolve the underlying problem from #252.
I found that incremental compilation will disregard the value of codegen-units, causing multiple output files to be created when using -o foo --emit=bar.  This was why the issue only occurred in nightly and beta debug, stable rustc and release builds do not use incremental compilation.
I opened rust-lang/rust#48147 to rustc, but we can mitigate the issue for the playground immediately by disabling incremental compilation via Cargo.toml.

Incremental is probably not useful for a case like the playground anyway, so this seems like a better place to be anyway.

Apologies for the onslaught of pull requests lately,

Never! So long as we make forward progress, it's nice to have progress on the playground. 😺


Allow provideCompletionItems to return IterableIterator and AsyncIterableIterator

Hey, I think provideCompletionItems' return value should extend to include IterableIterator and AsyncIterableIterator.
That way in case the completions take a while to generate (like when workspace files are being consulted for suggestions, the items can start popping in ASAP as opposed to taking a while to all get dumped in at once.
An alternative extension developers can use today is to keep a workspace index and cache the intermediate data used to fuel the suggestion list, so this is not strictly necessary, but I think it would simplify extension development a little bit without too much impact. (Albeit I am incapable of assessing how much impact would it have for the core to actually support it.)
Maybe there are other API candidates which could benefit from this, too.

The "streaming results"-discussion isn't new (we have discussed this for reference search for instance) but the unsolved challenge is in the UI. Showing results and updating them at the same time isn't a nice user-experience. There are two options and both aren't good:

new results are always added to end of the suggestions list which means potentially good results are never prominently shown
new results are intermixed with existing results which means confusion, esp when this happens at the exact moment in which you select an item

Yeah. I guess this is a pretty well known UX challenge, I personally have found a way which works for me in my projects and have received zero complaints about: append it suggestion list is hovered over, order if it isn't (keyboard selection is fine, it will just move, no biggie). Of course one missing component to this is touch, which I don't think is a problem for VS Code really, but my solution to that is just to fall-back to append-only on touch devices and potentially reorder only between touch down and up events in different places (knowing touch isn't and won't be occurring in the suggestion list during that time). Still, one problem is left, which is multi-touch, someone can still tap the suggestion list with their other finger while tapping something with their first finger, but that was always an edge-enough case for me to not have to worry about.


Nested models, collection types, and complex types: I think this section already is included by default

In section Nested models, collection types, and complex types, for me validation for complex objects works without any special or further attempts. I think it is already included by ASP.Net version 6.

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

ID: eef47457-c8cf-74a4-b884-c1fe5c2ef52d
Version Independent ID: 09a02d10-2834-467d-d8c2-3fd19ceb3863
Content: ASP.NET Core Blazor forms and validation
Content Source: aspnetcore/blazor/forms-validation.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @abdollahkahne ... They haven't rolled the package into the framework yet, but they plan to do so for .NET 7 ...
https://github.com/dotnet/aspnetcore/issues/28640
If you have a concern about what you're seeing ... like it seems like the guidance is incorrect, then I recommend asking them directly because they haven't indicated to me that anything has changed in these regards. Open an issue for the product unit at ...
https://github.com/dotnet/aspnetcore/issues
Reference this article/section:
https://docs.microsoft.com/en-us/aspnet/core/blazor/forms-validation?view=aspnetcore-6.0#nested-models-collection-types-and-complex-types
Please add ...
cc: @guardrex https://github.com/dotnet/AspNetCore.Docs/issues/25013

... to the bottom of your opening comment so that I follow along. I might re-open this for doc work depending on what they say.


I just installed Flutter on windows 11 and when i try to run flutter doctor in the cmd it crashes,I added the Paths but it still does not work

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Writing the command Flutter doctor in the cmd
Actual results
Cmd crashes
Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output
It crashes

PS. I dont have System32 or SysWOW, only place i found a powershell folder was in program files and program files (x86)


How can I get live logs with loguru and pytest? (hashtag611)

I have tried many of the options like --log-cli-level, --log-level but I'm not able to run my tests seeing the output of the logs live.

You should try with the --capture=no option.

You should try with the --capture=no option.

Just tested it, but still does not work, this is the only output:
============================= test session starts =============================
platform win32 -- Python 3.10.1, pytest-6.2.5, py-1.11.0, pluggy-1.0.0 -- C:\xxxxxxxxxxxxxx\.venv\Scripts\python.exe
cachedir: .pytest_cache
metadata: {'Python': '3.10.1', 'Platform': 'Windows-10-10.0.19044-SP0', 'Packages': {'pytest': '6.2.5', 'py': '1.11.0', 'pluggy': '1.0.0'}, 'Plugins': {'html': '3.1.1', 'metadata': '1.11.0'}, 'JAVA_HOME': 'C:\\Program Files\\Java\\jre1.8.0_211'}
rootdir: XXXXXXXXXXXXXXXXXXXX, configfile: pytest.ini
plugins: html-3.1.1, metadata-1.11.0
collecting ... collected 3 items

Can you please provide a reproducible example? It works fine when I test it.

Can you please provide a reproducible example? It works fine when I test it.

Yes, I just prepared it:
test.py:
"""
Test loguru error
"""
from loguru import logger
from subprocess import Popen, PIPE

def main():
	"""
	Execute the tests
	"""
	pytest_args = []

	report_path='./report.html'

	pytest_args.append(f'--html={report_path}')
	pytest_args.append(f'--self-contained-html')
	pytest_args.append(f'--capture=no')
	pytest_args.append('./t/')

	hashtag _retcode = pytest.main(pytest_args)

	with Popen(['pytest',
			*pytest_args,
			str(__file__)], shell=True, stdout=PIPE, stderr=PIPE, bufsize=1, close_fds=True,
			encoding='utf8',
			universal_newlines=True) as p:
		for line in p.stdout:
			print(line, end='')

	logger.info('Tests finished')

if __name__ == '__main__':
	main()

t/my_test.py:
import time
from loguru import logger

def test_loguru(my_value):
    """
    test
    """
    logger.info(f'Testing value {my_value}...')
    logger.info(f'Testing value {my_value}...')
    logger.info(f'Testing value {my_value}...')
    time.sleep(5)
    assert my_value <= 4, "Test value."

conftest.py:

from loguru import logger
import pytest
from _pytest.logging import LogCaptureFixture

def caplog(caplog: LogCaptureFixture):
	"""
	Make pytest work with loguru. See:

	"""
	handler_id = logger.add(caplog.handler, format="{message}")
	yield caplog
	logger.remove(handler_id)

def my_value():
	"""
	Some random value
	"""
	return 5

requirements.txt
loguru==0.6.0
pylint==2.12.2
pytest==6.2.5
pytest-html==3.1.1
selenium==4.1.0

Output:
============================= test session starts =============================
platform win32 -- Python 3.10.1, pytest-6.2.5, py-1.11.0, pluggy-1.0.0
rootdir: C:\Users\HMG28\Desktop\delete_me_2
plugins: html-3.1.1, metadata-1.11.0
collected 1 item

t\my_test.py F

================================== FAILURES ===================================
_________________________________ test_loguru _________________________________

my_value = 5

    def test_loguru(my_value):
        """
        test
        """
        logger.info(f'Testing value {my_value}...')
        logger.info(f'Testing value {my_value}...')
        logger.info(f'Testing value {my_value}...')
        time.sleep(5)
>       assert my_value <= 4, "Test value."
E       AssertionError: Test value.
E       assert 5 <= 4

t\my_test.py:13: AssertionError
- generated html file: file://C:\Users\HMG28\Desktop\delete_me_2\report.html --
=========================== short test summary info ===========================
FAILED t/my_test.py::test_loguru - AssertionError: Test value.
============================== 1 failed in 5.13s ==============================
2022-03-04 18:44:33.605 | INFO     | __main__:main:39 - Tests finished

Thanks for the snippets. How are you running the tests? If work fine for me both when using pytest or python test.py.
============================= test session starts ==============================
platform linux -- Python 3.10.2, pytest-6.2.5, py-1.11.0, pluggy-1.0.0
rootdir: /home/delgan/Programmation/loguru, configfile: tox.ini
plugins: freezegun-0.4.2, cov-3.0.0
collected 1 item

my_test.py F                                                             [100%]

=================================== FAILURES ===================================
_________________________________ test_loguru __________________________________

my_value = 5

    def test_loguru(my_value):
        """
        test
        """
        logger.info(f'Testing value {my_value}...')
        logger.info(f'Testing value {my_value}...')
        logger.info(f'Testing value {my_value}...')
        time.sleep(5)
>       assert my_value <= 4, "Test value."
E       AssertionError: Test value.
E       assert 5 <= 4

my_value   = 5

my_test.py:13: AssertionError
----------------------------- Captured stderr call -----------------------------
2022-03-04 22:07:39.685 | INFO     | my_test:test_loguru:9 - Testing value 5...
2022-03-04 22:07:39.685 | INFO     | my_test:test_loguru:10 - Testing value 5...
2022-03-04 22:07:39.685 | INFO     | my_test:test_loguru:11 - Testing value 5...
=========================== short test summary info ============================
FAILED my_test.py::test_loguru - AssertionError: Test value.
============================== 1 failed in 5.10s ===============================
2022-03-04 22:07:44.853 | INFO     | __main__:main:31 - Tests finished

This is maybe a problem specific to Windows.

Hi, I'm running it with python test.py. I think your output is also not working, I'd expect to see after the line collected 1 item the 3 logger.info messages, as there is a delay of 5 seconds after them.
They do not appear live but at the end of the script when it has finished.

These 3 lines are logged from within an external Process so there is no way to display them in live because they are redirected to the configured PIPE and later displayed with the for line in p.stdout loop.

These 3 lines are logged from within an external Process so there is no way to display them in live because they are redirected to the configured PIPE and later displayed with the for line in p.stdout loop.

Thank you, but I don't understand why the rest of the lines are printed live, for example:
============================= test session starts ==============================
platform linux -- Python 3.10.2, pytest-6.2.5, py-1.11.0, pluggy-1.0.0
rootdir: /home/delgan/Programmation/loguru, configfile: tox.ini
plugins: freezegun-0.4.2, cov-3.0.0
collected 1 item

Then here the lines are not printed, and it continues until the subprocess finishes:

my_test.py F                                                             [100%]

=================================== FAILURES ===================================
_________________________________ test_loguru __________________________________

my_value = 5

    def test_loguru(my_value):
        """
        test
        """
        logger.info(f'Testing value {my_value}...')
        logger.info(f'Testing value {my_value}...')
        logger.info(f'Testing value {my_value}...')
        time.sleep(5)
>       assert my_value <= 4, "Test value."
E       AssertionError: Test value.
E       assert 5 <= 4

my_value   = 5

my_test.py:13: AssertionError
----------------------------- Captured stderr call -----------------------------
2022-03-04 22:07:39.685 | INFO     | my_test:test_loguru:9 - Testing value 5...
2022-03-04 22:07:39.685 | INFO     | my_test:test_loguru:10 - Testing value 5...
2022-03-04 22:07:39.685 | INFO     | my_test:test_loguru:11 - Testing value 5...
=========================== short test summary info ============================
FAILED my_test.py::test_loguru - AssertionError: Test value.
============================== 1 failed in 5.10s ===============================
2022-03-04 22:07:44.853 | INFO     | __main__:main:31 - Tests finished

Why is the rest of the lines of pytest printed but not the ones from loguru in the subprocess?

One thing is that Loguru will be default write logs to stderr and not to stdout. This is one reason for which it's not appearing in live, I guess.
I also noticed that I had to set shell=False if you want Pytest not to capture the stderr output, but I don't know why. :confused:

One thing is that Loguru will be default write logs to stderr and not to stdout. This is one reason for which it's not appearing in live, I guess.
I also noticed that I had to set shell=False if you want Pytest not to capture the stderr output, but I don't know why. 😕

I am using loguru, the output content is not utf8 encoded
![1648903144(1)](

The encoding depends of the sink encoding. It might be a problem related to your terminal or pytest.
See also: [Resolving UnicodeEncodeError and other encoding issues](

I'm closing this ticket as I guess it's solved.

You should try with the --capture=no option.

I had a problem with loguru live logs when using PyCharm's test runner. Adding --capture=no in Additional Arguments of the runner configuration solved the problem.


Adding HTTPS options for WebHDFS

Currently, Hue is hard coded to http for webhdfs (return "http://%s:%s/webhdfs/v1" % (host, port)).  This PR makes it dynamically pull SSL from hdfs-site settings with the ability to override the port from hue.ini
Note -> i just moved the port into the hdfs-site.py so i need to test that and make sure it works since previously i was injecting it in webhdfs.py (this seemed cleaner though it does seem to break the convention of no hue.ini settings in hdfs-site.py).

Updated per comments

https://review.cloudera.org/r/13779/


Filter incompatible targets

For some reason, cquery returns incompatible targets that need to be filtered using the config operator.

Commit 1 produces correct result but may be too slow for large projects since it calls bazel for each configured target. I will try an approach described here - https://bazel.build/extending/platforms#cquery-incompatible-target-detection

@illicitonion Please review the latest commit. It performs much better than the first commit since it makes only one extra bazel-cquery call.

Thanks for the help Dave. Are the tests failing due to this change? It did not look related to me.

Ish :) The remaining tests are failing because bazel 3.7.1 didn't support starlark cqueries, but we shouldn't be running tests against bazel 3.7.1 any more, so I'm updating to make sure we only test our supported range of Bazel versions.

Ah, I see. So I guess the testdata repository needs to be updated?

We should be able to merge this after we merge https://github.com/bazel-contrib/target-determinator/pull/50 :) I just pushed a cherry-pick to this branch so we can see CI hopefully go green 🤞
Thanks again for the contribution (and patience!)

Sorry this has taken so long - thanks so much for the contribution!

Thanks for shepherding it through


Overhaul the Horn solver with regard to name collisions

The central commit in this PR is  660fe5a, the commit message in which explains the essence of the issue.  Fundamentally the problem is that of "abuse of notation where it doesn't lead to confusion".

FYI @janvrany


Added limit file size example to Readme

Hi there! I corrected a sentence and added an example on how to use file size limit.

I think a limit example should demonstrate more than attaching a listener to the event that’s already documented. How about covering the necessary error handling and cleanup?

Hi @charmander :wave: , thanks for your feedback. Sure, I'll be happy to do that. Clean up: are you referring to cleaning up the temp (truncated) file ?  Also, could you give me some hints about the error handling you are referring to? Thanks!


Can not find grid areas: in Angular 5 with Angular Material

Angular CLI: 1.6.7
Node: 9.3.0
Angular: 5.2.3
~package.json
"scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build --prod",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^5.2.3",
    "@angular/cdk": "^5.1.1",
    "@angular/common": "^5.2.0",
    "@angular/compiler": "^5.2.0",
    "@angular/core": "^5.2.0",
    "@angular/forms": "^5.2.0",
    "@angular/http": "^5.2.0",
    "@angular/material": "^5.1.1",
    "@angular/platform-browser": "^5.2.0",
    "@angular/platform-browser-dynamic": "^5.2.0",
    "@angular/router": "^5.2.0",
    "angularfire2": "^5.0.0-rc.5-next",
    "core-js": "^2.4.1",
    "firebase": "^4.9.1",
    "hammerjs": "^2.0.8",
    "promise-polyfill": "7.0.2",
    "rxjs": "^5.5.6",
    "zone.js": "^0.8.19"
  },
  "devDependencies": {
    "@angular/cli": "1.6.7",
    "@angular/compiler-cli": "^5.2.0",
    "@angular/language-service": "^5.2.0",
    "@types/jasmine": "~2.8.3",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "~6.0.60",
    "codelyzer": "^4.0.1",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~2.0.0",
    "karma-chrome-launcher": "~2.2.0",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.1.2",
    "ts-node": "~4.1.0",
    "tslint": "~5.9.1",
    "typescript": "~2.5.3"
  }

~src/app/style.scss
body{
  position: fixed;
  top:0;
  left: 0;
  height: 100%;
  width: 100%;
  margin: 0;
  font-family: 'Roboto', sans-serif;
}
app-login{
  height: 100%;
  display: grid;
  grid-template-columns: 1fr auto 1fr;
  grid-template-rows: 1fr auto 1fr;
  grid-template-areas: " . . ." " . wrapper . " " . . .";
}

~src/app/login/login.component.scss
.form-wrapper{
  background: white;
  grid-area: wrapper;
  border-radius: 4px;
  box-shadow: 0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12);
}

Warning Message
WARNING in ./node_modules/css-loader?{"sourceMap":false,"import":false}!./node_modules/postcss-loader/lib?{"ident":"postcss","sourceMap":false}!./node_modules/sass-loader/lib/loader.js?{"sourceMap":false,"precision":8,"includePaths":[]}!./src/styles.scss (Emitted value instead of an instance of Error) autoprefixer: /Users/marmikthakkar/projects/deepblue/src/styles.scss:16:3: Can not find grid areas: wrapper NonErrorEmittedError: (Emitted value instead of an instance of Error) autoprefixer: /Users/marmikthakkar/projects/deepblue/src/styles.scss:16:3: Can not find grid areas: wrapper     at Object.emitWarning (/Users/marmikthakkar/projects/deepblue/node_modules/webpack/lib/NormalModule.js:117:16)     at result.warnings.forEach (/Users/marmikthakkar/projects/deepblue/node_modules/postcss-loader/lib/index.js:149:49)     at Array.forEach (<anonymous>)     at postcss.process.then (/Users/marmikthakkar/projects/deepblue/node_modules/postcss-loader/lib/index.js:149:27)     at <anonymous>  @ ./src/styles.scss 4:14-191  @ multi ./src/styles.scss
So when i remove the line  grid-template-areas: " . . ." " . wrapper . " " . . ."; in  ~src/app/style.scss it complies without any warnings.
Can anyone help me with this issue?
Thank you in advance.

Global and component stylesheets existing within separate and distinct contexts.  As a result autoprefixer cannot find the wrapper grid area as it does not exist within the context of the component.  An Angular component should ideally be self contained (theming is a typical exception) and therefore should include necessary styles within its component stylesheets.

@clydin Is it possible to disable this warning through .angular-cli.json somehow or similar?

Why is this closed if there is an obvious stated exception to the rule?


[BUG] copyMessage return message caption is too long

Can't copyMessage from channel with premium user caption length
Action:
copyMessage message_id from channel send to any user.

This is not a bug.
You should not copyMessage that contains any premium feature such as custom emoji or long caption length. Instead use forwardMessage.

This is not a bug.
You should not copyMessage that contains any premium feature such as custom emoji or long caption length. Instead use forwardMessage.

Thank for the info.
But copyMessage with premium caption length FROM bot TO channel or user it can send successfully, only FROM channel problem occur.

Do you add reply_markup, or specify teply_to_message_id in the copyMessage request?

I can't reproduce the issue. If message is copied as is, then the request succeeds. The mentioned error can be received, only if the bot tries to edit the copied message, replacing its caption, reply_markup, or reply_to_message_id, which is expected to fail for non-premium users and bots.


Update Causal_Reasoning_in_Probability_Trees.ipynb

Fix typos s/creata/create/g

@googlebot I signed it!

@googlebot I signed it!


GBM Announcement

Hi Chase, Bharat, or Christian,
here's the announcement and it's ready to go on the blog.

@bmiddha  - It looks like this CI check won't ever pass on forked branches...  Do you think we need to add a condition to only match a specific organization? Or maybe to not fail the pipeline when Azure deployments don't work?

@bmiddha - It looks like this CI check won't ever pass on forked branches... Do you think we need to add a condition to only match a specific organization? Or maybe to not fail the pipeline when Azure deployments don't work?

we can try enabling the skip_deploy_on_missing_secrets setting suggested in the logs

The deployment_token is required for deploying content. If you'd like to continue the run without deployment, add the configuration skip_deploy_on_missing_secrets set to true in your workflow file

@clee231 we can try enabling the skip_deploy_on_missing_secrets setting suggested in the logs

The deployment_token is required for deploying content. If you'd like to continue the run without deployment, add the configuration skip_deploy_on_missing_secrets set to true in your workflow file


Constant ZERO should have UPPER_SNAKE_CASE name, e.g. Z_E_R_O

For the following code
pub const ZERO: Millis = Millis(0);

Visual Studio Code reports (attributed to rust-analyzer)
Constant `ZERO` should have UPPER_SNAKE_CASE name, e.g. `Z_E_R_O`

Using a quick fix results in
pub const Z_E_R_O: Millis = Millis(0);

which is consistent with the error message but very likely not the expected convention.
Offering
pub const Zero: Millis = Millis(0);

Correctly results in
Constant `Zero` should have UPPER_SNAKE_CASE name, e.g. `ZERO`

(which gives the above follow-up problem)
I expected ZERO to be the correct convention and rust-analyzer to not complain. Looks like some PascalCase parser went rogue.

This should've been fixed in https://github.com/rust-analyzer/rust-analyzer/pull/6350, are you on the latest stable plugin version?

Wild guess: this looks like a probable cause. "URL" might be both: UPPER_SNAKE_CASE or an abbreviation in "UpperCamelCase".
https://github.com/rust-analyzer/rust-analyzer/commit/854b1331810b503e266be96708ed753db2677865#diff-f29185bc15c9578d498a392c122f4077942cc2fa20ade33f9213c510a5f2ae4cR37

Totally fixed - the extension required a reload for the changes to become active.
Sorry for the noise and thanks for the quick reply!


Migrate token-script NPM package from @alphawallet to @tokenscript organisation

Let's do this as a task when the other changes are in place, also confirming:

The status: Alpha, Beta, Production Ready state of Package
Package key words
If time / application of Github actions to help manage the CI of the package management


Add roadmap section to README with links to more information

It would be helpful for the README to include a couple links to our roadmap.
Specifically, I'm thinking that the Restructuring the Dataverse UI as a Single-Page Application doc gives a good overview of the plan and the Dataverse - SPA MVP Strategy doc gives a nice amount of detail about what's ahead. There's also Dataverse - SPA MVP Definition.
I would suggest linking to various docs under a heading call "roadmap" or similar.

The latest doc is Proposal: SPA Beta Features for Q2 2024.


GeoIP Support

Hi,
Can we get GeoIP support? Is it possible to use a legacy version of it?

If you are using ubuntu 16 this is now supported
for existing installs use the command 'sudo apt-get install php-geoip'
and it should work after reloading rutorrent


jenkins_home reset when i commit and run

hello
when i commit container and run new images
I found that the jenkins directory in the new container was reset. The old jenkins data is gone.
what should i do to commit /var/jenkins_home data

Hey. You need to use a Docker volume when you run the container, so the next time you run it you use the same data. For example, run it like:
docker run -v jenkins_data:/var/jenkins_home xmartlabs/jenkins-android:

I also recommend you to use a volume for /opt/android-sdk-linux, so the Android SDK tools and libraries you install once get installed forever.
I'm gonna close this issue, but feel free to comment if you think the issue hasn't been solved.


VL.Stride.Graphics shouldn't reference VL.Stride.Rendering

VL.Stride.Rendering may reference VL.Stride.Graphics.

one solution would be to introduce a csharp project on VL side per Stride package (e.g. VL.Stride.Graphics.API.csproj) together with a vl document (VL.Stride.Graphics.vl).
So if the Stride.A package references the Stride.B package, this gets mirrored on csproj and vl doc level on our side. By that it's very well defined what belongs where.
A step in between (we don't really want too many cs projects) is to have a vl document VL.Stride.API.vl which imports all the necessary original Stride types (therefore references Stride.A, Stride.B ...). This document VL.Stride.API.vl gets referenced by other documents like VL.Stride.Graphics.vl. It is now defined where the external types all come from and where the API category is to be found. All imports happen here. By that the system doesn't come up with messages like RenderDrawContext is no RenderDrawContext...

one solution would be to introduce a csharp project on VL side per Stride package (e.g. VL.Stride.Graphics.API.csproj) together with a vl document (VL.Stride.Graphics.vl).
So if the Stride.A package references the Stride.B package, this gets mirrored on csproj and vl doc level on our side. By that it's very well defined what belongs where.
A step in between (we don't really want too many cs projects) is to have a vl document VL.Stride.API.vl which imports all the necessary original Stride types (therefore references Stride.A, Stride.B ...). This document VL.Stride.API.vl gets referenced by other documents like VL.Stride.Graphics.vl. It is now defined where the external types all come from and where the API category is to be found. All imports happen here. By that the system doesn't come up with messages like RenderDrawContext is no RenderDrawContext...

4819e7305357470cc02be274df65e5d57de253cf

4819e7305357470cc02be274df65e5d57de253cf