Update: RTL 0.10.0

RTL 0.10.0 released TODO: Add to v1.6.3 release.
https://twitter.com/RTL_App/status/1340815355959267329?s=20

PR merged. final testing.

Install works fine - will be part of release 1.6.3 - closing issue.


Fix small copy paste error in documentation

Problem
What is being fixed?  Examples:

Fix small copy paste error in documentation

Change overview
Fix small copy paste error in documentation
Testing
How was this tested? (at least one bullet point required)

N/A

Fast tracking docs update


missing commands for pets

pets doesn't have command to attack at habitat and attack  other player's pets

Yeah, thanks for pointing that out. I just checked and the commands are:
PetsDungeonFight:{use_mushroom}/{habitat_id}/{enemy_pos(1-20?)}/{player_pet_id}
and
PetsPvPFight:0/{enemy_id}/{habitat_id}
(posting them here so I do not forget)
Need to test them a bit to make sure they work, but should be relatively easy to add to the regular commands


Suggestion : Keybind to toggle the mod

I want to toggle first person model anytime i want.

It's F6 by default.


Adding coe-cli assets to pipelines.

Fixes microsoft/coe-starter-kit#3523

Instead of calling coe-linux and coe-win, please consider the pattern the actions team takes with pac?  They put the different executables in different directories per platform.
https://github.com/microsoft/powerplatform-actions/tree/main/dist
Also, I still wonder what confusion we may be causing by distributing a linux executable when our pipelines still don't work with linux agents.  Perhaps add a readme to explain?
The coe-win.exe --version command returns 0.0.1.  Ideally, we'd formally version the cli consistently with the rest of our releases.  Given the time sensitivity of the release we want to include this in, it's ok to keep the version for this PR.  However, let's consider formal versioning in the next release as well as making the exe part of our releases moving forward.

Instead of calling the exes coe-linux and coe-win.exe, please consider the pattern the actions team takes with pac? They put the different executables (same name) in different directories per platform. https://github.com/microsoft/powerplatform-actions/tree/main/dist
Also, I still wonder what confusion we may be causing by distributing a linux executable when our pipelines still don't work with linux agents. Perhaps add a readme to explain?
The coe-win.exe --version command returns 0.0.1. Ideally, we'd formally version the cli consistently with the rest of our releases. Given the time sensitivity of the release we want to include this in, it's ok to keep the version for this PR. However, let's consider formal versioning in the next release as well as making the exe part of our releases moving forward.

I've moved the linux executable to a subdirectory similar to pac and updated the version. Will incorporate this into build pipelines. I think leaving the linux executable and pipeline logic for eventual linux support can be useful to others who may want to use our pipelines as a reference even if the specific code won't be executed in the context of our full pipeline as of today.


Improve visual design of public study withdrawal page

See https://www.openhumans.org/public-data/withdraw

Can by now be found under https://www.openhumans.org/public-data/deactivate Could be part of #693 but is low priority.


Clear cached filtered dependencies

When we clear the previous traversal exclusions, we need to clear the
cached filtered dependencies as we no longer are able to assess whether
the filter changed or not.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.


raft-small-words.txt: Added more source code versioning systems

Source: https://nitter.kavin.rocks/intigriti/status/1533050946212839424

Thank you!


Results

In Section 4.1 you say "The laplacian loss proposed by Hou et al. [13] gives a significant reduction in errors across all metrics. We note this network, training and loss configuration is enough to achieve state of the art results, see Table 4."
I am unsure as to what differentiated your model from others and lead to quite a substantial new state of art as by this point you have not used fg/bg prediction nor data augmentation.
From what I gather it can be attributed to:

Batch size=1 with GN and WS
4 loss functions of laplacian, L1, composite, gradient
9 channel input
Adding pyramid pooling in the decoder
Clipping instead of sigmoid

Is there anything I am missing? I am only refering to the Ours_alpha in Table 4. Can you give some comment on why you think this performed so much better than previous models listed in table 4?

Hi, yes the changes you have listed contribute to the better accuracy of our model. Except pyramid pooling is similar to aspp in the AlphaGAN paper. In the paper we provide the measurements for the effect of batchsize, GN+WS, and clipping. Comparing model (1) in Table 2. to the rest in Table 4. we see that it matches the state of the art, and with the changes made in models (1-7) we improve accuracy,
Also to look at is our strong data-augmentation, using the ETZH synthesizability dataset as an additional source of background, and using multiple scales for each image during training. The RAdam optimizer, and our training schedule. There were many components to this work.
Although the key take-away is still that great F,B, Alpha prediction can be gotten simultaneously without any drawbacks.
We will release a clear version of the full code for training once the paper is accepted.

Thank you for your response. I don't think you mentioned the ETZH synthesizability dataset in your paper but that's a great idea. I though of something similar where I was getting the mean color in the trimap region and composting that on a background of that color to make it harder for my model.
For augmentation you have only mentioned "For data augmentation, we adopt random flip, mirroring, gamma, and brightness augmentations" which are standard.
Yes, F,B, Alpha prediction can be gotten simultaneously but I was surprised to see it did not yield to much gain for alpha prediction as it did in Context Aware Image Matting. You achived SOTA without it with training implementation.

Thanks for pointing that out, I will need to add that in the final version of the paper.
Your bg color idea is a nice one but it's a balance between the training examples being too easy and being too difficult.
True those augmentation are common, but they all have a large effect. I was surprised to see gamma augmentation worked very well.
Our architecture differs from Context Aware Matting in that they have a separate foreground prediction branch, which would give higher accuracy. So it's hard to compare directly. Nonetheless the benefit they gain from foreground prediction is very minor. MSE of 8.8 instead of 9.0. (Models (4)vs. (6).)
There's much research to be done in the area :)

Thanks. Can you also give me any intution you have about why batch size = 1 would make such a difference? You compared GN+WS on larger batch size to BN and isolated batch size to be the factor that lead to performance increase on bs=1. I'm a bit confused as isint a higher batch size with GN+WS just a parallel version of GN+WS with bs=1? How could it make a difference in that case as the GN/WS parameters are independant of the batch and the gradient is the same gradient as before just an averaged across the samples.

I am confusing about multi-scale training.

I'm confusing about multi-scale training you mentioned above. Does it mean "Additionally, every second mini-batch is sampled from the 2× image of the previous image, so as to increase the invariance to scale", which has been written in section 3.6? If that, every second mini-batch resample from the upsampled image which used in previous mini-batch. "Resample" means that randomly cropping image with paths and re-generate trimap by "random erosion and dilation of 3 to 25 pixels", which you mentioned in your paper.


As a user, I want to add products to Cart

To get to a Cart Page user has to click Cart icon on Navbar.
Cart is empty by default.

If Cart is empty, user can click “Shop now” button on Cart Page, and be redirected to Home Page. Then user can choose products from 3 catalogs: Backpacks, Bags and Accessories.
User can click “Add to cart” button on Product Detail Page and product will be added on Cart Page.
If user clicks “Add to cart” button twice, three times or more, the quantity of the product will be displayed on Navbar according to amount of clicks, made by user. User has to choose size, if it is available for certain types of backpacks.
If Cart is not empty, the page contains the following attributes:

image
title (clickable)
color (If available)
size (If available)
quantity (-/ editable field /+). User can change number of chosen products using “-”, "+" buttons or  editable field
price
total price (save)
"Delete" button
"Go to check out" Button
"Continue shopping" Button (History back). Redirects user  to the previous page

Acceptance criteria:

Product image, title (clickable), color, size, quantity, price of product and total price on Cart Page must correspond to user’s choice, made on Product Detail Page.
When user adds some products to Cart, they are stored on Cart Page.
When user clicks “Delete” button, the product will be deleted from Cart.
When user clicks “Go to check out” button he/she is redirected to Checkout Page.
When user clicks “Continue shopping” button (History back) he/she is redirected to the last visited page.

Ukrainian language mock-ups are also added.

#148

September 2020
The team has decided to combine the chat page with the checkout page.


Add RFS to CDK

Description
Note: This builds off changes being reviewed here: https://github.com/opensearch-project/opensearch-migrations/pull/566
This changes adds RFS as an ECS service that can be enabled in the migration CDK.
Also included are changes to make RFS usable in the E2E test script.
Issues Resolved
https://opensearch.atlassian.net/browse/MIGRATIONS-1604
https://opensearch.atlassian.net/browse/MIGRATIONS-1637
Testing
CDK and E2E script deployment testing
Check List

[ ] New functionality includes testing

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Given that this is an open-source monorepo for a growing number of projects, I have a strong preference to limit the tracked artifacts to just code/configs. This PR includes test data and that's a very slippery slope that we've so far avoided.
In this case, I think that its easy to workaround the issue with docker layers. Longer term, we should discuss how we'd like to share larger datasets or those that cannot be easily regenerated from code.

I share these concerns over time, I'd suggest looking at how benchmarks does this for its test workloads [1].  I think there is a sweet spot in the project cycle to locally optimize, but we might be exiting that phase with ever increasing sized test datasets.

[1] https://github.com/opensearch-project/opensearch-benchmark-workloads

I haven't looked into how OSB handles workloads yet, but here's a Dockerfile that uses build phases to do a once, when used, dataset build.  It also self-documents how we've constructed the tarball since anybody can run it.  Note that I built on ARM, so I had to install development tools to build a dependency for OSB... all of that will be independent of our final ES image layer - it's only a one-time charge when building the image the first time.
FROM docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2 as base

ENV ELASTIC_SEARCH_CONFIG_FILE=/usr/share/elasticsearch/config/elasticsearch.yml

# without this line, elasticsearch will complain that there aren't enough nodes
RUN echo "discovery.type: single-node" >> $ELASTIC_SEARCH_CONFIG_FILE

FROM base as makeDataSet1

RUN cd /etc/yum.repos.d/ && \
    sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS-* && \
    sed -i 's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*
RUN yum install -y python3.9
RUN yum install -y gcc python39-devel
RUN yum install -y vim git less

RUN pip3 install opensearch-benchmark

RUN /usr/local/bin/docker-entrypoint.sh eswrapper & echo $! > /tmp/esWrapperProcess.pid && sleep 10 &&\
     opensearch-benchmark execute-test --distribution-version=1.0.0 --target-host=http://localhost:9200 \
    --workload=geonames --pipeline=benchmark-only --test-mode --kill-running-processes  \
    --workload-params "target_throughput:0.5,bulk_size:10,bulk_indexing_clients:1,search_clients:1" &&  \
    tar -cvzf esDataFiles.tgz /usr/share/elasticsearch/data

FROM base

RUN echo y | /usr/share/elasticsearch/bin/elasticsearch-plugin install https://maven.search-guard.com/search-guard-suite-release/com/floragunn/search-guard-suite-plugin/7.10.2-53.5.0/search-guard-suite-plugin-7.10.2-53.5.0.zip
# add search-guard, which provides TLS, as well as other features that we don't need to consider
RUN pushd /usr/share/elasticsearch/plugins/search-guard-7/tools ; chmod ugo+x ./install_demo_configuration.sh ; yes | ./install_demo_configuration.sh ; popd

ENV PROXY_TLS_CONFIG_FILE=/usr/share/elasticsearch/config/proxy_tls.yml
COPY disableTlsConfig.sh enableTlsConfig.sh /root/
RUN chmod ugo+x /root/disableTlsConfig.sh /root/enableTlsConfig.sh
ENV PATH=${PATH}:/usr/share/elasticsearch/jdk/bin/
RUN sed 's/searchguard/plugins.security/g' $ELASTIC_SEARCH_CONFIG_FILE |  \
    grep ssl.http > $PROXY_TLS_CONFIG_FILE

# The following two commands are more convenient for development purposes,
# but maybe not for a demo to show individual steps
RUN /root/enableTlsConfig.sh $ELASTIC_SEARCH_CONFIG_FILE
# Alter this config line to either enable(searchguard.disabled: false) or disable(searchguard.disabled: true) HTTP auth
RUN echo "searchguard.disabled: false" >> $ELASTIC_SEARCH_CONFIG_FILE

COPY --from=makeDataSet1 /usr/share/elasticsearch/esDataFiles.tgz /root/esDataFiles.tgz

CMD /usr/local/bin/docker-entrypoint.sh eswrapper

I'd like to see a comment explaining why the base starts as late as it does. Please add a line item to https://opensearch.atlassian.net/browse/MIGRATIONS-1628 to update this to 'un-migration-consolify' this image

Sure have added a TODO on the Dockerfile and updated the Jira task


GPIO pin for inter-device communication

Required Info

Camera Model
D415

Firmware Version
5.9.14

Operating System & Version
Win 10

Platform
PC

SDK Version
2.15

Language
C++

Segment
VR/AR

Issue Description
Hello, trying to locate the documentation regarding the GPIO pins i noticed that it has been deleted in a previous commit (https://github.com/IntelRealSense/librealsense/commit/28371bc6de865f10b54265f808cdcd8f50bdbe07).
The past version can be found at: https://github.com/IntelRealSense/librealsense/blob/28371bc6de865f10b54265f808cdcd8f50bdbe07/doc/rs400/external_devices.md
Is this still supported? According to this issue #2512, it is not.
We need this to be able to send a signal on demand from one of our D415's to other D415s via the GPIO pin in order to establish global time correspondences when recording from a set of HW-synced devices connected via LAN.

Page 47 of the November 2018 edition of the RealSense 400 Series data sheet document contains a table of pin details.

The data sheet can be downloaded from the link below:
https://www.intel.co.uk/content/www/uk/en/support/articles/000026827/emerging-technologies/intel-realsense-technology.html
One of the Intel guys (I do not work for Intel) can best inform you about the extent to which pin access is supported in the camera's firmware driver.


remove Stack::pop()

I'm not very sure if this is a good fix. Seems like no direct usage of GlobalStack::pop() through out the tree.

Thanks for the PR! I think that this is actually unused nowadays, but the previous implementation was the intended implementation for this feature. Since it's unused, though, want to remove it entirely?

into_abi(&mut GlobalStack::new())
Here GlobalStack is used as trait Stack, so we can't remove impl Stack for GlobalStack entirely.
Just mark its push and pop methods as unreachable!()? This feels uncomfortable.

Ah yes what I mean is removing the pop function from GlobalStack as well as the implementation, I don't believe its used anywhere any more

r? @alexcrichton


OTA plus Tick Counter Callback causes a crash (IDFGH-6056)

Environment

Development Kit:      [none]
Module or chip used:  [ESP32-C3-MINI-1]
IDF version: v4.3.1
Build System:         [idf.py]
Compiler version (run xtensa-esp32-elf-gcc --version to find it):
// 1.22.0-80-g6c4433a
Operating System:     [Linux]
Using an IDE?: [Yes (Geany)]
Power Supply:         [external 3.3V]

Problem Description
I encountered a system crash (guru meditation error) during function call esp_ota_write(). According to what I could see, the crash was caused by the parallel running tick counter callback. Only by deregistering the tick counter callback (using esp_deregister_freertos_tick_hook()) before calling esp_ota_write(), I could run esp_ota_write() successfully. Please check if you can repeat this behaviour. Thanks!
partitions.csv:
ESP-IDF Partition Table
Name,   Type, SubType, Offset,  Size, Flags
nvs,      data, nvs,     0x9000,  0x4000,
otadata,  data, ota,     0xd000,  0x2000,
phy_init, data, phy,     0xf000,  0x1000,
factory,  app,  factory, 0x10000,  1M,
ota_0,    app,  ota_0,   0x110000, 1M,
ota_1,    app,  ota_1,   0x210000, 1M,
Expected Behavior
No crash.
Actual Behavior
See above.
Steps to reproduce
See above.
Code to reproduce this issue
// the code should be wrapped in the ```cpp tag so that it will be displayed better.
#include "esp_log.h"

void app_main()
{
	// A BLE GATT server is up and running as well in its own task.
	esp_register_freertos_tick_hook(tick_hook_cb);
}
void tick_hook_cb() // runs at 100 Hz (period 10 ms). Here we run the msgos idle AND counter!
{
	// Execution time of this function is guaranteed < 1 ms!
	general_counter+=10; // fake milliseconds
	msgos_main_loop();
}

esp_ota_handle_t update_handle = 0;
const esp_partition_t* update_partition = NULL;

bool Init_Ota()
{
	esp_err_t err;
	const esp_partition_t* running;
	/* update handle : set by esp_ota_begin(), must be freed via esp_ota_end() */
	ESP_LOGI(TAG, "Init");

	if(update_handle != 0){
		esp_ota_abort(update_handle);
		update_handle = 0;
	}
	update_partition = NULL;

	const esp_partition_t* configured = esp_ota_get_boot_partition();
	running = esp_ota_get_running_partition();
	update_partition = esp_ota_get_next_update_partition(NULL);

	ESP_LOGI(TAG, "Running    partition type %d, subtype %d\t(address 0x%08x)", running->type, running->subtype, running->address);
	ESP_LOGI(TAG, "Configured partition type %d, subtype %d\t(address 0x%08x)", configured->type, configured->subtype, configured->address);
	if(update_partition){
		ESP_LOGI(TAG, "Update     partition type %d, subtype %d\t(address 0x%08x)", update_partition->type, update_partition->subtype, update_partition->address);
	}else{
		ESP_LOGE(TAG, "No update partition found!");
		return false; // error: cannot get update partition!
	}

	if((err = esp_ota_begin(update_partition, OTA_WITH_SEQUENTIAL_WRITES, &update_handle)) != ESP_OK) {
		ESP_LOGE(TAG, "esp_ota_begin() failed: %s", esp_err_to_name(err));
		return false;
	}

	ESP_LOGI(TAG,"Init_Ota() OK! handl = 0x%X", update_handle);

	return true;
}

bool Write_Ota(const void* data, uint32_t len)
{
// Calling esp_ota_write() leads to a crash!
	esp_err_t err;
	if((err = esp_ota_write(update_handle, data, len)) != ESP_OK){
		ESP_LOGE(TAG, "esp_ota_write() failed: %s", esp_err_to_name(err));
		return false;
	}
	return true;
}

Debug Logs
Debug log goes here, should contain the backtrace, as well as the reset source if it is a crash.
Please copy the plain text here for us to search the error log. Or attach the complete logs but leave the main part here if the log is *too* long.

Other items if possible

[x] sdkconfig file (attach the sdkconfig file from your project folder)
[ ] elf file in the build folder (note this may contain all the code details and symbols of your project.)
[ ] coredump (This provides stacks of tasks.)
partitions.csv
sdk_etc.zip

Thanks a lot for this swift answer! That explains it perfectly.
Would be nice if that would be mentioned in the documentation as well (see
https://docs.espressif.com/projects/esp-idf/en/v4.3.1/esp32c3/api-reference/system/freertos_additions.html?highlight=tick hook#hooks
)
Thanks!
On Wed, 20 Oct 2021 at 20:43, Ivan Grokhotkov @.***>
wrote:

@Muragavino https://github.com/Muragavino please note that the tick
hook may be executed at the time when cache is disabled, so code from flash
isn't accessible. For this reason, tick hook function and any functions
called from it must be placed into internal instruction RAM (IRAM). This is
the same requirement as for the interrupt handlers
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/storage/spi_flash_concurrency.html#iram-safe-interrupt-handlers,
since the tick hook is invoked from an interrupt. You can use IRAM_ATTR
attribute of the linker fragment files to place code into IRAM (docs
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/memory-types.html#how-to-place-code-in-iram
).
Note that since you are calling msgos_main_loop from a tick hook, you
will have to place that function and any functions called from it,
recursively, into IRAM as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/espressif/esp-idf/issues/7740#issuecomment-947981283,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASHSJQNMWKGNXWJU4YA3YM3UH4LUPANCNFSM5GLK2PJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Eclipse Che support?

This IDE is also supported, since it implements the LSP?
You like to include it in the README then: https://eclipse.org/che/

Related with #438?


Examine other Rules Expression Language before building our own for Submission Requirement

Breaking requirements for a rules expression language, aka why we have our own (@csuwildcat):

Picking between a set: "one of these two", "three of these five"
Can reference. Looked at JSONLogic, etc. assume what they are selecting over is inside an object, not supporting a reference to an input group such as "ProofOfAddress"

Design criteria:

Use cases using real JWTs/JSON-LDs/etc. must be reasonable
Usability and understandability is a goal of Presentation Exchange, so humans should be able to make sense of these requirements

(@OR13, @wyc) what are rules expression languages and off-the-shelf tooling relevant to our criteria?

JSON Logic
MongoDB Querying

https://meta-guide.com/data/data-processing/automated-reasoning/json-rule-engines-2019

https://www.openpolicyagent.org/docs/latest/#expressions-logical-and
^ we have used this before... and its part of CNCF.... it has built in support for JWTs....
https://www.openpolicyagent.org/docs/latest/http-api-authorization/#8-optional-use-json-web-tokens-to-communicate-policy-data
Roadmap for JSON Schema support:
https://github.com/open-policy-agent/opa/issues/1449
Downside is it relies on a DSL "Rego"... upside is that it has lots of other supporters... who don't care about VCs... and its not a new thing...

Example, from Dapr explaining why OPA is a thing:
https://github.com/dapr/dapr/issues/1617

https://github.com/open-policy-agent/opa

Resolved, with prejudice.


Holding Alt activates random token image (without hovering)

For some reason holding Alt causes a random image to pop up as if you're hovering over it, even if you're not.

Hello GambetTV
Thanks for reminding me of this issue, it is now fixed in v1.1.3.


Use HTTPS instead of HTTP

It looks like this module has been removed. So the PR is no longer relevant.


bots: Add complete test coverage for yoda bot.

Add error handling support for empty messages and invalid
input to yoda bot, which was previously making the bot crash.
Add comments to describe tests.
This is as a followup for #53. I wasn't sure where to put the check for invalid input as the bot code was not responding to invalid input of special characters. Initially, I thought of putting a check by regular expressions (re.match)  but on further exploration, I found out that it is indeed sending an empty reply which is not handled properly by the code.

Merged, thanks @abhijeetkaur!  @derAnfaenger FYI; I wonder if we want to move the handling of empty messages into some piece of common framework code, so that individual bots don't need to write something unless they want to do something special.

You mean some optional function handle_empty_message/handle_mention ? I can see this being useful, since crashing for empty messages has been a bug for several bots now. I feel that a new method for this rare case would be a little unproportionate. What do you think of adding a generic test case for this scenario to the test_lib.py BotTestCase class, given that this is possible?

I think a good approach might be to have default behavior for empty messages provided by the library of sending the user an error back that is controlled by whether or not the ACCEPT_EMTPY_MESSAGES = 1 is set on the class object.  If it is, then the default behavior doesn't run, but if it is, then the bot will automatically block ignore empty messages.  And then we just need a couple tests at the framework level for whether that feature works correctly, and the 95% of bots that don't want to process empty messages don't need to think about this.

Will create an issue for it.


nameof preferred to magic string

for "context.People.Include("School").ToList()" read "context.People.Include(nameof(School)).ToList()"

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

ID: 25a3ce6e-43ab-e0af-01b3-a82fdaf3cb31
Version Independent ID: 320e7305-e0a3-a1c6-77f2-1d3029b660b1
Content: Eager Loading of Related Data - EF Core
Content Source: entity-framework/core/querying/related-data/eager.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @roji
Microsoft Alias: avickers

We discussed this, but since the code is showing explicitly that a string can be used, we would rather leave it as an explicit string literal. You can, of course, use nameof if you know the property at compile time, but it's more common to use the string overloads when you're dynamically finding the name.


[CWS] improvements to jsonschema documentation extraction

What does this PR do?
The main goal of this PR is to allow the definition of different fields with comments instead of json struct tags.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Thanks, created DOCS-3640 to track as an editorial review!


Search Trashed

Is there anyway that your package can return trashed results?
By adding a flag, or indicator can the query results will return trashed items. I'm thinking something like
app()->searchy->assets('model', 'serial', 'service_tag', 'asset_tag')->query($search)->withTrashed()->get();
The DB::table should return all results, but at some point the search results filter out the soft deleted items.

Hmm... haven't touched the code in a while so can't remember what I am doing off the top of my head that would be filtering the trashed objects. Yes, it should return them using the Query Builder ... as far as I know.
I'll take a peek at this in the next few weeks. Happy for you to submit a pull request if you'd like to see it resolved sooner. Or, if you can see where they are getting filtered out, I'll jump in and make the necessary updates as it's an important use case :smile:
Thanks for letting me know about this one.

I am getting all results, even soft deleted. Raw SQL confirms theres nowhere in the software filtering soft deletes. I would check how your calling it.

https://github.com/TomLingham/Laravel-Searchy/pull/26


GEODE-7128: Add Resume Async Event Queue Dispatcher gfsh command

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

This PR is an update to https://github.com/apache/geode/pull/4031


Filter aer warnings in deprecated FakeBackend V1 class

Summary
The recent qiskit-aer 0.15 release has introduced deprecation warnings for BackendV1 inputs in NoiseModel.from_backend. We were using this method in the deprecated FakeBackend class (which is, by definition, V1) and this is triggering test failures. I suggest filtering the warnings in FakeBackend until the class is removed in 2.0.
Details and comments

Changed :) This actually how I initially approached it, but then I thought it could be more practical for the removal to just have it in FakeBackend directly (I remembered the cleanup we had to do on the QiskitTestCase class not so long ago because we would forget to get rid of the filters past their "expiration date"). It should be fine though, now that we are aware of it.


Don't works: "Error executing luv callback"

nvim --version: NVIM v0.9.1 Build type: Release LuaJIT 2.1.0-beta3
git --version: 2.41.0
Operating system/version: Archlinux
Terminal name/version: Konsole

Steps to reproduce
copy the lines of the configure in the nvim init.lua
Actual behaviour
Error executing luv callback:
...afocl/.local/share/nvim/pckr/pckr.nvim/lua/pckr/jobs.lua:26: attempt to call field 'system' (a nil value)
stack traceback:
        ...afocl/.local/share/nvim/pckr/pckr.nvim/lua/pckr/jobs.lua:26: in function 'fn_or_ret'
        ...focl/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:30: in function <...focl/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:7>
Press ENTER or type command to continue

Expected behaviour
install and works
packer files

packer log file
~/.cache/nvim/packer.nvim.log is not exist

packer compiled file
contents of packer_compiled.vim is not exist

vim.system is only available in nightly. The README needs to be updated.

does this mean that pckr.nvim cannot be run on a non-nightly neovim?

Yes


Data loss with async hasMany

Steps to reproduce:

Define a model with at least two async hasMany associations.
Create an instance with values in one of the associations and save it.
Clear the store's cache (e.g., by reloading the app or by using store.unloadAll).
Load the instance
Set a value in the other association
Save the instance
Clear the store's cache again
Load the instance and attempt to read values from the first association

Expected: the values would still be present in the first association
Actual: the first association is empty
I've reproduced this in a test case: humanpractice/ember-indexeddb-adapter@7baf61ae2cd5f3e6748152090e05886db41955fa. (N.b., that branch builds on PR #20 since it needs some of the same test infrastructure.)
While the README for this project indicates that you should not use async associations with it, synchronous associations also have issues (see #13).

hello, did you solve this issue, having the same problem here

After getting no response on PR #20, I stopped using this adapter. I use ember-pouch instead now. It also has the benefit of working on browsers where indexeddb support is poor (e.g., Safari) without using a shim.


Get time remaining?

I'm using Neotimer wonder if there's a way to determine how much time is left before the timer expires?

why is version 1.1.7 with the getellapsed method still not available in the libs for use on the arduino, when are they going to publish it?


OSS License

Had a quick question, would you be willing to add an OSS license to the package? This would allow companies to use the module. I would suggest MIT.
Thanks!

@stevelacy good idea! Sorry for the delay here as well. I need to setup better notifications for issues/PRs for this repo so I can address them sooner


Add Dockerfile

Add Dockerfile and fix issue with pyperclip in Docker.

Looks straightforward.  Thank you.  Can you tell me a little about the pyperclip issue with docker?

Looks straightforward. Thank you. Can you tell me a little about the pyperclip issue with docker?

The error may be linked to the fact that I tried it on WSL.
It looks like this :
Traceback (most recent call last):
  File "/1filellm/onefilellm.py", line 679, in <module>
    main()
  File "/1filellm/onefilellm.py", line 670, in main
    pyperclip.copy(uncompressed_text)
  File "/usr/local/lib/python3.12/site-packages/pyperclip/__init__.py", line 659, in lazy_load_stub_copy
    return copy(text)
           ^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pyperclip/__init__.py", line 506, in copy_wsl
    p = subprocess.Popen(['clip.exe'],
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/subprocess.py", line 1026, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/local/lib/python3.12/subprocess.py", line 1955, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'clip.exe'


Excel Download issue

I used your library to create Excel files and I got this issue:
While creating Multiple Sheets everything works as expected until I initialize download of the created Excel using method ->download, which did not work. As a temporary solution, I use ->store. Excel is than saved in project folder. I could find any examples but yours https://docs.laravel-excel.com/3.1/exports/multiple-sheets.html in the web, so please advise if I'm doing something wrong, or is there an error in this particular version of your product (there are no errors while using download, library version maatwebsite/excel  3.1.11)
Simple example https://docs.laravel-excel.com/3.1/exports/ works correctly.

Hello @AndreyKuzmenko1989 can you fill in the issue template, specifically the parts about sharing your code and sharing any exceptions you are getting. It's difficult to guess what's going wrong if you only state that "it did not work" :)

Prerequisites

[X] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[X] Checked that your issue isn't already filed.
[X] Checked if no PR was submitted that fixes this problem.

Versions

PHP version: 7.2.17
Laravel version: 5.6.16
Package version: 3.1.11

Description
Download method doesn't work as expected (file is not downloading). Upon calling a method download file doesn't get saved on a computer, but calling method store works as expected.
Steps to Reproduce
Expected behavior:
Excel file should be downloaded and saved to user's computer.
Actual behavior:
Downloading process doesn't start.
Additional Information

an Excel table generated with store method of this library
report(4-2004__5-2019).xlsx
ReportKindSheet.txt
ReportExport.txt

Yeah, I already figured that out.
Thank you, the issue is solved.

Yeah, I already figured that out.
Thank you, the issue is solved.

Glad you managed to solve it :)

How can you solve it?

很高兴你设法解决它:)
how to use ajxa to download

How can you solve it?

Not sure about your issue, but recently we've added the possibility to add headers to Laravel Excel downloads. Please refer to https://docs.laravel-excel.com/3.1/exports/export-formats.html#csv


Text coding error in Chinese

Text coding error in Chinese

Click on Download

See two buttons text error

at macOS Big Sur 11.1
ipfs-desktop 0.13.2

https://github.com/ipfs-shipyard/ipfs-desktop/pull/1729 should fix this.

https://github.com/ipfs-shipyard/ipfs-desktop/pull/1729 should fix this.


StorageLoader: write JSON path for com.unbounce/event_context/jsonschema/1-0-0

Migrated to https://github.com/snowplow/iglu-central/issues/539

Descheduling


Requests does not support session key logging

I would really like requests to support session key logging.  Firefox and Chrome both support logging the symmetric session key used to encrypt TLS traffic.  This makes it easy to analyze traffic with Wireshark.
Requests should write symmetric session keys to the file set in user variable “SSLKEYLOGFILE”.

Requests cannot do this in normal operation because OpenSSL does not expose appropriate APIs to extract this keying information. Both Chrome and Firefox use other TLS implementations (BoringSSL and NSS) which do have the appropriate APIs.
I am currently working on a patch to enable this functionality in openssl/openssl#1646. Please track that issue, as until it merges it will not be possible for Requests to support this function. It will also be limited to OpenSSL 1.1.0 and modern Python versions.

Hi Cory, it seems your change has been merged to OpenSSL. Is the key logging supported in requests now?

Nope. Adding support for this requires first that OpenSSL 1.1.1 be released, and second that bindings for these functions be added to our dependencies. When OpenSSL 1.1.1 releases I'll add bindings to PyOpenSSL, but the stdlib will take a long time to catch up.

OpenSSL 1.1.1 is out!
News on the dependencies front?

Better to ask pyOpenSSL if they support it yet. Then convince urllib3 to expose a way to utilize it from their pyOpenSSL shim. .... Then it will be actually useful to bug us about how to use it within requests.

Is this feature available yet in requests? It would provide a very easy way to debug some of the requests in my script.

Just use https://pypi.org/project/sslkeylog/, it works for me.

@gtors
I've tried the sslkeylog (0.2.0) module but with mixed success.  A line is written into the sslkeylog.log file for each request.{get/put} but wireshark only seems to recognize and use some of them.  For example, if my code has six requests.get() calls, six entries will be written to sslkeylog.log but wireshark will only be able to decode, say, three of the calls in a trace.
I suspect this is because 'requests' uses 'pyopenssl' but that's just a guess. This code is beyond my python knowledge.
If anyone has a suggestion, I would love to hear it.
Thanks


mysql8 sql syntax REPLACE INTO throwing errors after v24.0.3

Description
Context
The following bug does not occur in CE v24.0.2
Query & Table Schema
Table Schema
-- Table definition
CREATE TABLE `Table` (
  `col1` varchar(128) NOT NULL,
  `col2` varchar(45) NOT NULL,
  `col3` int NOT NULL DEFAULT '0',
  `col4` varchar(10) NOT NULL DEFAULT '*',
  `col5` text NOT NULL,
  `updated_at` timestamp NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`col1`,`col3`,`col2`,`col4`),
  KEY `some_key_name_idx` (`col3`,`col4`),
  KEY `some_key_name_2_idx` (`col2`,`col3`,`col4`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3;

In custom SQL Script, created by clicking on Scripts tab (^])
INSERT INTO `dbName`.Table (col1,col2,col3,col4,col5) VALUES
  ('some_value_1','some_value_2',0,'*','some_value_5');

REPLACE INTO `dbName`.Table (col1,col2,col3,col4,col5) VALUES
  ('some_value_1','some_value_2',0,'*','some_new_value_5');

when REPLACE INTO query is at the top of the script

when REPLACE INTO query is below another query in the same script
The REPLACE INTO query gets evaluated together with the above query when executing a query under the cursor or clicking ^⏎

SQL Error [1064] [42000]: You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use near 'REPLACE INTO
`dbName`.Table at line 5

Error position: line: 4

DBeaver Version
Community Edition Version <IP_ADDRESS>404211624
Operating System
macOS Sonoma 14.0 (23A344)
Database and driver

Steps to reproduce

use v24.0.3
create table per above schema
insert a row per above query
attempt to replace values in the row per above query
see error

Additional context
No response

potentially related to https://github.com/dbeaver/dbeaver/issues/26447 & https://github.com/dbeaver/dbeaver/issues/25061

Thank you for bug report. It's a duplicate of #26416
We're working on fix
As a workaround, you could try switching Blank line is statement delimiter setting to Always

hey @E1izabeth, thanks for the work around. it did solve some of the problem but there are still lingering errors when trying to run multi-lined queries here and there in a large sql script
downgrading to v24.0.2 seems to be a simpler solution

Does downgrading help?
Could you clarify the cases where it doesn't work as expected?

downgrading to v24.0.2 helped, even with the following issues -
recalling from memory, a few cases that didn't work well even with blank line as delimiter set to always:

REPLACE INTO query under a large multi-line query
multi-line SELECT query under another query works, but trying to filter the SELECT query result failed

i'm uncertain if this is the direct cause of the same issue as i just tried upgrading back to v24.0.3 again to recreate the issue but it no longer breaks
thanks for the fix 🔥

Actually, we haven't delivered a fix yet, so I suppose you reinstalled the same version with the bug.
The fix will be included in 24.0.4 version and also available in Early Access version (https://dbeaver.io/files/ea/) tomorrow


As a user, I want to retrieve the top N populated countries in a specific continent, where N is specified by me, so that I can analyze the demographics and population distribution within that continent according to my preferences

User report and sql statement issue 5 - The top N populated countries in a continent where N is provided by the user
src/main/resources/report-issue5.html
src/main/resources/report-issue5.csv
src/main/resources/report-issue5.xml
sql-issue5.sql
2 parameters needed:
continent - %continent%
Number of countries - %N%
Use world;
SELECT country.Name, country.Population
FROM country
WHERE country.continent = '%continent%'
ORDER BY country.Population DESC
LIMIT %N%;

SQL:
select country.Code , country.Name, country.Continent, country.Region, country.Population, city.Name as Capital
from country inner join city on country.Capital  = city.ID
where country.Continent = '%continent%'
order by country.Population desc limit %n%;
Parameters:
%continent%
%n%


Add functionality to download file

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@4dcbc80). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev       #8   +/-   ##
======================================
  Coverage       ?   75.10%
======================================
  Files          ?        8
  Lines          ?      241
  Branches       ?        0
======================================
  Hits           ?      181
  Misses         ?       60
  Partials       ?        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 4dcbc80...f491d3b. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@4dcbc80). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev       #8   +/-   ##
======================================
  Coverage       ?   83.26%
======================================
  Files          ?        8
  Lines          ?      239
  Branches       ?        0
======================================
  Hits           ?      199
  Misses         ?       40
  Partials       ?        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 4dcbc80...a88508f. Read the comment docs.


Allow protecting images with specified tags

what

Allow protecting images with a given set of tag names

why

At Transcend, we tag images with dev, staging, and prod for deployments in addition to their SHA tags. We want to expire images, but not those actively is use.

references

https://github.com/aws/containers-roadmap/issues/637
https://docs.aws.amazon.com/AmazonECR/latest/userguide/lifecycle_policy_examples.html

Note: This change is fully backwards compatible

/test all

/rebuild-readme

/test all

At Transcend, we tag images with dev, staging, and prod for deployments in addition to their SHA tags. We want to expire images, but not those actively is use.

Okay, I see your point about using both SHA and stage tags on the images. While you deploy with the SHA tag, the stage stages ensure the underlying bits aren't lifecycled. It's actually something we wanted to look into.

@maximmi see ☝


Remove About > Accessibility

Currently, there is no actual accessibility page, so this avoids a 404
in the docs. More fundamentally, though, it makes more sense for
accessibility advice to be directly integrated in the docs (which we're
doing, for the most part - though we should ensure that we do
cover/mention everything where appropriate), so there's no need for a
separate accessibility page.
http://getbootstrap.com/getting-started/#accessibility in the old docs always felt a bit of a catch-all of random bits of advice. if we still think some of these nuggets of info are useful, we should integrate them where appropriate rather than segregating them into a separate sub-page that nobody will look at :)

/cc @cvrebert @mdo

Currently, there is no actual accessibility page

Actually there is, though it's not properly linked from anywhere:

http://v4-alpha.getbootstrap.com/getting-started/accessibility/
https://github.com/twbs/bootstrap/blob/v4-dev/docs/getting-started/accessibility.md

X-Ref: #17986

Hmm, interesting. I've added the link to the correct section. However, I still feel that fundamentally we should give relevant accessibility guidance "in situ" where needed - for instance, the prose about adding role for button groups should really live directly under http://v4-alpha.getbootstrap.com/components/button-group/ and not be shunted here; the skip link is interesting, but feels oddly specific and yet out of place here - maybe it could be used as a good example for the http://v4-alpha.getbootstrap.com/components/utilities/#screen-readers-and-keyboard-users section instead; the bit about headings just again feels very specific and disconnected...and it's not one of the most pressing accessibility issues, truth be told...
I'd say worth revisiting this once relevant advice has been added to the relevant sections, as I think beyond some basic info about striving to do the right thing, and pointing out that many components will have specific accessibility requirements that are in callouts throughout the docs, there's not much more we want/need here.

However, I still feel that fundamentally we should give relevant accessibility guidance "in situ" where needed

No objection here :smile:


Database connection collision

Apparently it occurred during /connect
https://sentry.io/organizations/iasql/issues/3239613744/events/4a43547b1e414f99a3f64e80c39d7bc3/?project=6106929
Error: Connection database-172713 already exists

I actually ran into that once in the test suite, too. There's just not enough entropy in that Math.random call to actually avoid collisions. Might make more sense to just switch the connection IDs to uuids?

I actually ran into that once in the test suite, too. There's just not enough entropy in that Math.random call to actually avoid collisions. Might make more sense to just switch the connection IDs to uuids?

probably that'd be the best solution


refactor: extracted chat and step from cli.py into new chat.py

[!IMPORTANT]
Refactor chat and step functions into chat.py and move interrupt handling to interrupt.py for better code organization.

Refactoring:

Extracted chat and step functions from cli.py to chat.py.
Moved interrupt handling logic to new interrupt.py.

Imports:

Updated imports in cli.py to reflect new file structure.

Tests:

Updated test_server.py to import init from init.py instead of cli.py.

This description was created by  for cafed4912e079e26262fc06141f6446b009c8d5a. It will automatically update as commits are pushed.

Codecov Report
Attention: Patch coverage is 87.35632% with 22 lines in your changes missing coverage. Please review.

Project coverage is 79.40%. Comparing base (1a7e4ef) to head (352f1be).

:white_check_mark: All tests successful. No failed tests found.

Files with missing lines
Patch %
Lines

gptme/chat.py
86.62%
21 Missing :warning:

gptme/config.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #158      +/-   ##
==========================================
- Coverage   80.37%   79.40%   -0.97%
==========================================
  Files          54       56       +2
  Lines        3281     3297      +16
==========================================
- Hits         2637     2618      -19
- Misses        644      679      +35

Flag
Coverage Δ

anthropic/claude-3-haiku-20240307
79.40% <87.35%> (+0.10%)
:arrow_up:

openai/gpt-4o-mini
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


[native] Added native parquet writer tests

Issue: https://github.com/facebookincubator/velox/issues/5796
Test cases for the other compression types will be added as soon as they are supported in Velox.
Merged the ParquetWriterTestBase and ParquetReaderTestBase class into one to avoid duplication of code.
Added a new function in the ParquetReader for exposing the file Metadata from the ReaderBase. This is used in unit tests to verify the compressionKind.

Thanks @pdabre12.
I'm bulk importing all Arrow parquet unit tests in this PR (https://github.com/facebookincubator/velox/pull/6830), including compression specific tests. Once this is one gets merged, we could start looking into refactoring and better organizing them along with the ones we currently have.

@pedroerp Okay, I will wait for the merge to land. Thanks!

@czentgr Please review.

@majetideepak  Please review.

@majetideepak Please review.

@pdabre12 the PR still shows as draft, if it's ready for review, could you change the status?

@pedroerp FYI, the goal of these tests is to cover the Velox Writer API. We want to test that the writer options are plumbed through as expected.

@majetideepak Please review.

@pdabre12 the PR still shows as draft, if it's ready for review, could you change the status?

Yes, my bad, it slipped my mind. Thanks!

@pdabre12 I also see two independent tasks here.

Refactor to have a common ParquetTestBase
Add a Parquet writer test for compression.
We should create a PR for each. Can we first do the refactoring?

@pdabre12 I also see two independent tasks here.

Refactor to have a common ParquetTestBase
Add a Parquet writer test for compression.

We should create a PR for each. Can we first do the refactoring?
Yes, I will get on it.

@majetideepak
Opened a PR for refactoring the testBase classes.
#6921

@pdabre12 now that the refactor PR got merged, do you want to finish this PR off?

@czentgr Already opened a PR for that. https://github.com/facebookincubator/velox/pull/7332
Closing this.


#158 adding new about us image to the form sucess and fail pages

Current coverage is 45.74%

Merging #206 into master will not affect coverage as of bc24b7d

@@            master    #206   diff @@
======================================
  Files           21      21
  Stmts          341     341
  Branches         0       0
  Methods          0       0
======================================
  Hit            156     156
  Partial          0       0
  Missed         185     185

Review entire Coverage Diff as of bc24b7d

Powered by Codecov. Updated on successful CI builds.


Fix memory leak which occurs when a client-side response stream is closed unexpectedly (#632)

Motivation:
A client-side response can be closed unexpectedly due to various
reasons, most notably due to a ResponseTimeoutException. When it
happens, an HTTP/1 connection has to be closed and an HTTP/2 stream has
to be reset with CANCEL error code. We don't do anything.
Modifications:

Close the connection when a response of an HTTP/1 connection is closed
unexpectedly.
Reset the stream with CANCEL error code when a response of an HTTP/2
connection is closed unexpectedly.

Result:
Memory leak is fixed.

@kojilin @minwoox Will merge once CI passes since it's the same patch with #632


Better Pages Debugging

So, I've got a semi-Pico-3.0 related issue to bring up.  ~It could probably be it's own issue if you want to have a discussion on it.~
Yeah, went ahead with that. 😅
In older versions of Pico (below 2.0, not a typo) I could easily inspect pages using the | json_encode filter to help get an idea of what things looked like.  You know, sometimes in programming it's helpful to actually inspect your data structure so that you can *facepalm* when you realize you didn't lay things out like you meant to. 🤦🏻♀
Somewhere along the line, I assume with Pico 2.0, next_page and previous_page became actual references to those pages (I assume), causing an Array Recursion error when attempting to print them using | json_encode.
I tend to get around this by doing a "Smiley Slice", lol, by accessing page[:-3] instead of page. 😂
(On a related note, I don't really have a good way to do this for all pages, as Twig doesn't seem to like me stringing together two slices like pages[:][:-3] or something.)
Anyway, with Pico 3.0, I no longer see this Array Recursion error, the | json_encode just silently fails.  No idea if this was a change in Twig, a change in its default configuration, or just something different about my test environment specifically.  It has been a little annoying though, when trying to poke and prod at the pages data.
I'd originally planned to include a reference to this clever "Smiley Slice" in the Docs rewrite as a "ProTip" kind of thing, but it also feels a bit clunky.
Going forward to Pico 4.0 and the idea of Pages as Objects would probably break this hacky workflow of mine even further. 😉
So, what are your thoughts on, in the future (eg, not Pico 3.0, but maybe a point release, or even 4.0), including some debugging functions, like a way to "Pretty Print" the collection of Page Objects?  Something formatted a little nicer than the | json_encode filter.
Idk, maybe it's just me that needs that "facepalm reminder" that I used page.meta.config.option instead of page.meta.option, and that's why nothing's working as expected. 😂
Might also be useful for making sure that pages() returns the data you expected.  (I know there's probably a few cases where I've used depth or depthOffset in a manner other than I really intended to)
Any thoughts on this?  Any other ideas for debug tools Pico could provide for theme developers?

I can only assume that json_encode started detecting the recursion and thus bails.
Actually the only real solution to this is to finally implement page objects. With objects we gain full control on what is being encoded to JSON (https://www.php.net/manual/en/jsonserializable.jsonserialize.php), as well as what is being dumped when using the dump() function (https://www.php.net/manual/en/language.oop5.magic.php#object.debuginfo)

I can only assume that json_encode started detecting the recursion and thus bails.

Well, yeah, I don't think it's smart enough to figure that out. 😂
Point being just that it used to throw an error and now it doesn't (though, again, could just be my setup).
Mostly just wanted to start thinking about what this would look like in the future.  I'd rather see a replacement for | json_encode in the form of a filter or function that would make something more readable.  JSON is a bit dense for combing through a large amount of data like this anyway.
To take this idea to more of an extreme, maybe it could inject some HTML with inline-styles for a richer breakdown of the data requested (all of pages or just a subset returned by pages()).  Maybe some collapsable/expandable sections to deal with sheer amount of data.
In my head, could be kind of like how phpinfo() will kind of "hijack" the page to show it's own table of data, regardless of where you put it (just, maybe a little more gracefully).
Idk, that wasn't even part of my idea before, so I guess the brainstorming is already working. 🤔
Honestly, I just kind of wanted to mention my "Smiley Slice", and the fact that the recursion error had disappeared for me. 😂 😉

IMO the reason why debugging is hard right now is because of the recursion, not because of the output not being styled :wink: You could write a debug_pages Twig macro though if you really want to (simply skip the recursive keys with https://twig.symfony.com/doc/1.x/filters/filter.html). We will get rid of the recursion with page objects.

IMO the reason why debugging is hard right now is because of the recursion, not because of the output not being styled 😉

I just like going above and beyond with stuff. 😂
You make a good point about making a Twig macro though. 🤔


How to use packages installed with npm?

I wonder how I can use a package installed with NPM in mix?
I have run npm install jquery-validation
Then in my bootstrap.js file I have added: require('jquery-validation');
and in app.js:  require('./bootstrap');
My mix file:
mix.js('resources/assets/js/app.js', 'public/js')   .extract(['lodash', 'vue', 'axios',  'jquery-validation']); mix.sass('resources/assets/sass/app.scss', 'public/css'); mix.scripts([   'resources/assets/js/libs/vals.js',   'resources/assets/js/libs/rules.js' ], 'public/js/libs.js');
But I get the error: Uncaught TypeError: Cannot read property 'addMethod' of undefined in libs.js
this is the code:
$(document).ready(function() { $.validator.addMethod("nowhitespace", function(value, element) {     return this.optional(element) || /^\S+$/i.test(value);   }, "No white space please"); });
But why is addMethod undefined when I have added require('jquery-validation');  in my bootstrap.js file?
Also since I am using jquerys cdn I have removed in from my bootstrap.js and webpack config:
new webpack.ProvidePlugin(Mix.autoload || {     //jQuery: 'jquery',     //$: 'jquery',     //jquery: 'jquery'   }),

If I am not wrong, bootstrap.js comes with jQuery by default. Running the package's jQuery and CDN jQuery might have just caused the issue.

@ruchern I have removed all refrence to jquery so I am 100% sure I am using jquery via CDN.
Anyways, I solved my problem by adding this in my webpack.mix file:
mix.autoload({
  validator: ['validator', 'window.validator']
});

Now it seems that I can access validator outside the vendor.js file


McAfee WebAdvisor  scanning bar appeared in ADS

I downloaded the update extension of SQL Server 2019 (Preview) 0.12.1 using Google Chrome. The start point was Azure Data Studio - Marketplace). When it finished downloading the extension, the McAfee safety advisor bar appeared in Azure Data Studio as seen in the following picture.

Azure Data Studio Version:
Version: 1.6.0 (system setup)
Commit: eb35dae1d1238e03f1cab3bd45e151f381b22aef
Date: 2019-04-17T07:11:15.944Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134

Steps to Reproduce:

Install McAfee web advisor
Click on update extension from the marketplace (in my case it is SQL Server 2019 (Preview) )
Download it, the safety advisor bar should appear in Azure Data Studio when it is downloaded.

I'm not sure there is anything we can do on our side to resolve this.  I think the bug should be logged against McAfee, unless I'm missing something.


Add relative start param for time filters

CATEGORY

[ ] Bug Fix
[x] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
#6721 introduced the possibility to use time filters that end right now as opposed to midnight. However, this also made the start date reference the current time, leading to a moving window. While this might be fine for some use cases eg. line graphs with fine granularity, the full start day is often preferred in bar charts and similar; otherwise the start day will start dropping observations, as the day progresses. This PR introduces a new parameter DEFAULT_RELATIVE_START_TIME, which defaults to today.
BEFORE
As can be seen below, when setting DEFAULT_RELATIVE_END_TIME = 'now', the start date starts to drop off observations prior to the current time.

AFTER
When setting DEFAULT_RELATIVE_START_TIME = 'today' and DEFAULT_RELATIVE_END_TIME = 'now', the start date starts at midnight, while the end date is relative to the current time.

TEST PLAN
Tested to work in practice.
REVIEWERS
@agrawaldevesh as this extends your original PR, I would be interested in hearing your thoughts on this.

Codecov Report

Merging #7525 into master will increase coverage by <.01%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master    #7525      +/-   ##
==========================================
+ Coverage   65.29%   65.29%   +<.01%
==========================================
  Files         432      432
  Lines       21386    21389       +3
  Branches     2357     2357
==========================================
+ Hits        13963    13966       +3
  Misses       7303     7303
  Partials      120      120

Impacted Files
Coverage Δ

superset/config.py
93.9% <100%> (+0.03%)
:arrow_up:

superset/utils/core.py
88.17% <100%> (+0.02%)
:arrow_up:

superset/viz.py
71.95% <66.66%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

lgtm

@betodealmeida @john-bodley

This got me thinking more broadly about time filters. I think default behaviour for the presets (Last x days/weeks/etc) should apply the time grain to the where clause. For example, when applying a "Last Year" with quarterly grains, the first quarter will almost always have an incomplete set of rows, as the where clause will start somewhere between the start and and of the first quarter. It would be more logical to omit the first quarter entirely to make sure that all quarters are true full quarters. Applying the time grain to the time filter would rake care of this automatically. Thoughts?

@villebro wold you be able to provide some unit tests?

@john-bodley I added unit tests for both relative start and end, and made the now case more realistic (was equal to today before). I also noticed that relative start/end logic was missing from QueryObject, so added that there, too.


Add 2020-09-01-hybrid profile overrides for Java tags

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

This pull request is created for changes in code generation for the Azure Stack-compatible resource manager track-2 Java packages in https://github.com/Azure/azure-sdk-for-java/pull/25103. It adds overrides that makes downgrading API versions to make them compatible with the 2020-09-01-hybrid version so that fewer SDK related changes were required.

go and python timeout after 2hours

/azp run

/azp run

@akning-ms
Hello Arthur, would you help us to force merge this PR?
It only change README.java.md on tag for AzureStack, and it only affect Java. It touched a number of major service with big readme, and particularly go and python build takes too long.
The CI runs a day and still not finished, tried 3 times.

/azp run

/azp run


What is unreal version ?

It keep say that it not the right version

Unreal Engine 4.18

i have the same error every time :(


New PR to test SignCLA at 2019-04-18 16:21:40.677533441 -0400 EDT m=+5.112544654

Body of PR

indiv-pass-staging: test succeeded


Greenkeeper/sinon 5.0.0

Coverage remained the same at 91.304% when pulling 1cdb9be3e64beb988562055784c09ef77b3775e1 on greenkeeper/sinon-5.0.0 into b2c8ee171cd74aef5c1d90e288e2c8a7e4638e82 on master.


Text overlapping in JEN address bar popup

https://github.com/barbushin/javascript-errors-notifier/issues/18#issuecomment-112180741

This issue start again!

Fixed 30 minutes ago https://github.com/barbushin/javascript-errors-notifier/issues/21 Sorry about that. And thanks for report!


API Management API Import for OAS 3.1 does not support nullable schema properties

Documentationin question: https://learn.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions#openapi-specifications
Reproduction Steps
Take the test schema below and try to import it into API Management v2 (note the "TestId" property in the components/schemas section).
Expected
Imports successfully
Actual
Throws syntax error and references previous version of oas validation (3.0.1)
It says open api 3.1.0 is supported for import, but when I import a valid 3.1 specification, I receive the following error from APIM:
One or more fields contain incorrect values:

    Parsing error(s): Cannot create a scalar value from this type of node. [#/components/schemas/Test/properties/TestId/type]
    Parsing error(s): The input OpenAPI file is not valid for the OpenAPI specification https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md (schema https://github.com/OAI/OpenAPI-Specification/blob/master/schemas/v3.0/schema.yaml).

Issue opened with the OAS specification which clarifies the test OAS below should be allowed: https://github.com/OAI/OpenAPI-Specification/issues/3148#issuecomment-1403719138
The test OAS:
{
    "openapi": "3.1.0",
    "info": {
        "title": "test2232",
        "description": "",
        "version": "1.0"
    },
    "servers": [{
        "url": "https://myapim.azure-api.net/testestestes"
    }],
    "paths": {},
    "components": {
        "schemas":{
            "Test":{
                "type": "object",
                "properties":{
                    "TestId":{
                        "type": ["string", "null"]
                    }
                }
            }
        },
        "securitySchemes": {
            "apiKeyHeader": {
                "type": "apiKey",
                "name": "Ocp-Apim-Subscription-Key",
                "in": "header"
            },
            "apiKeyQuery": {
                "type": "apiKey",
                "name": "subscription-key",
                "in": "query"
            }
        }
    },
    "security": [{
        "apiKeyHeader": []
    }, {
        "apiKeyQuery": []
    }]
}

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

ID: be16b5c5-40c4-3e6c-0b0d-840373c63f9f
Version Independent ID: ced6b3ba-8da1-dd3d-9d1c-8a21dabd44fe
Content: Restrictions and details of API formats support - Azure API Management
Content Source: articles/api-management/api-management-api-import-restrictions.md
Service: azure-api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

@shawnmurtagh
Thanks for your feedback! We will investigate and update as appropriate.

@shawnmurtagh
Thank you for bringing this to our attention.
I've delegated this to content author @dlepow, who will review it and offer their insightful opinions.

Hi, is there an update on this issue?


core: Add asynchronous components

Summary
Add asynchronous components that run on the GLib main context.
Checklist

[x] cargo fmt
[x] cargo clippy
[x] cargo test
[x] updated CHANGES.md

Can this be applied to Factory Components as well?

Closes #342

I just realized that factories don't render anything inside async components.

I just realized that factories don't render anything inside async components.

Can you provide an example for that?

I was using a factory inside my component, once I turned into an async one the factory was no longer displayed.
You can try to use the same factory in a sync and async component.

Ok, I'll try to modify the factory example to reproduce this.

Okay, let me know if you can replicate this.

No, can't replicate. Switching to SimpleAsyncComponent in the factory example works just like the regular version.

That's strange, I might be missing something then. In that case, I think it's safe to merge.

That's strange, I might be missing something then. In that case, I think it's safe to merge.

I agree, let's merge this. We already have enough open PRs :sweat_smile:
Also, factories and components might need some clean-ups anyway after the dust has settled on all the things happening currently.


Track invalid transactions by sender

Describe the feature
The docs state
https://github.com/paradigmxyz/reth/blob/87a615fe265137fab0831fb9047268addbbe4d2c/crates/transaction-pool/src/traits.rs#L748-L753
but we only track the hash here:
https://github.com/paradigmxyz/reth/blob/87a615fe265137fab0831fb9047268addbbe4d2c/crates/transaction-pool/src/pool/best.rs#L95-L98
the docs even mention this but the impl is incorrect
TODO

track SenderId here

perhaps @greged93 ?
Additional context
No response

down for this yes!


chromuim browsers returns M1 as macIntel platform & useragent

https://stackoverflow.com/questions/64853342/whats-the-value-of-navigator-platform-on-arm-macs
https://user-images.githubusercontent.com/25513724/216495699-2de90760-620f-4e1e-8da5-9f137594ebf1.mov

Was about to make an issue about this as well.
My chromebook is detected as a macbook on the new site.
My useragent is:
Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

Has this been pushed to the site yet? (chromebooks are still showing macos download instead of linux)


[InputNew]: Password Input

name: 'Pull request'
about: A new pull request
New Pull Request
Checklist

[ ] I am not disclosing a vulnerability.
[ ] My code is conform the code style
[ ] I have made corresponding changes to the documentation
[ ] I have updated Typescript definitions when needed

Issue Description

Inside form on enter key press password visibility toggles
Related issue: #FILL_THIS_OUT
Solution Description
Changing type of div to button, fixes the issue

merging it since it is a very small change 😄


Sorry.

I was wondering if you whom tryied to help me out ones about no carousel issue that I was in... I am missing you and can´t find you on github... I´ll try the tutorial again. Would you contact me??

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

ID: cad5909e-e1c6-aa8e-82f1-f2851c1caced
Version Independent ID: 42292330-aa69-9df0-5bd7-e07c9daed995
Content: Use Azure Event Grid to automate resizing uploaded images
Content Source: articles/event-grid/resize-images-on-storage-blob-upload-event.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

Hey... just found you on the close tab. Shame on me.

@sique976 : I am assuming that you found the guy you were looking for , if that's the case please do reply back and I will go ahead & close this issue .

@sique976 : Since we have not heard back from you on this  , we are going ahead and closing the issue.

Hi! Good morning! Yeah, I found him. He was in the closed tabs. But I also try to reach him on GitHub but couldn´t. Thanks!!!
Enviado do Emailhttps://go.microsoft.com/fwlink/?LinkId=550986 para Windows 10

De: himanshusinha-msft<EMAIL_ADDRESS>Enviado: Sunday, April 14, 2019 1:02:38 AM
Para: MicrosoftDocs/azure-docs
Cc: San; Mention
Assunto: Re: [MicrosoftDocs/azure-docs] Sorry. (#29358)
@sique976https://github.com/sique976 : I am assuming that you found the guy you were looking for , if that's the case please do reply back and I will go ahead & close this issue .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/29358#issuecomment-482917932, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbWHK6yVePPgR2J2l-duYMyab-Njv8_Dks5vgqhegaJpZM4cuOqA.


CI: docs generate index page and bump peaceiris/actions-gh-pages

Why did you add -Zunstable-options ?

Why did you add -Zunstable-options ?

because the enable-index-page is unstable, see: https://github.com/rust-lang/cargo/issues/8229#issuecomment-633153513

And what improvements are on this version of the action btw?

And what improvements are on this version of the action btw?

A year of development :)
And in v3 the configuration is given via with not as environment variables, other then that not sure.

Thanks!


Changes the temporary dir location to work on every system

uses the system temp dir + pid combination to avoid renaming child
folder to a parent folder, which fails on linux;
cleans up the temporary folder during emergency shutdown to avoid
leaving orphan files;
still fails on linux when providing existing folder to the example
command;
still does not initialize modules for the cloned example.

Thanks @ZloeSabo this is very helpful. I'll have final look this weekend.
Can you please let me know which Linux distribution + version you are using?

@Manvel i've checked with Alpine 3.8 and Mint 19.

Thanks @ZloeSabo I've created a followup here https://github.com/Manvel/cmints/issues/115 hope to tackle them this week.


Fixes for all Missing Context warnings, mostly tests but some core fixes

Some core changes where context was not passed through
Enum is using default foam.context for created values
Tests look a bit messier, but could be refactored with a create() helper
FoamByExample test disabled pending major refactor where test failures and missing context warnings can be fixed

Rolled back for anything inside the "foam" root package. This means DAOs don't give a missing context warning.


Simply list of base colors

I think this is a good thing. I needed to use such a list in my project.

Thanks for PR. But could you give some explanation? Why need this list in the library?

It's like a basic color palette. And for some cases it's easy to have full list of it. Especially if you want to make pure material style.
As for me, I did a custom styles for chart library  and I needed to use this basic colors variables, basic ones. And it's definitely not comfortable to scroll though the long file.

Hmm, sounds pretty good. Fix the comments and I'll take this PR.

Are you talking about title?
//
// List of base colors
//

Change to this?
//
// List of base colors

Lines 13 - 15 in Less version and Stylus version.

Fixed it)

Thanks for work :muscle:


Concurent imports from map get stuck in "pending" state

Context
Running smoke tests and trying to set up a map with an org users.
Steps to Reproduce

Create an empty map
Click on "ADD" to add a new layer
Click on "CONNECT DATASET" and select a file.
Repeat steps 2 and 3 a couple of times, do not wait for the imports to finish.

Current Result
I saw a brief error message, then the first import did not succeed and the other two are stuck in "pending" state.
Expected result
All 3 layers are imported correctly
Browser and version
Google Chrome	49.0.2623.87 (Official Build) (64-bit)
OS	Linux

.carto file
I could not export the map. I created a separate ticket for it: https://github.com/CartoDB/cartodb/issues/10594
Additional info

I don't really know if it can be reproducible. It may be a race condition.
user: smoke711-4
It probably has nothing to do with the Builder but with the import API. I'll investigate it.

#SMOKE_MG03

False alarm. What I found in the logs:
2016-11-07 17:21:03 UTC: ogr2ogr call:            OSM_USE_CUSTOM_INDEXING=NO PG_USE_COPY=YES PGCLIENTENCODING=UTF-8  /usr/bin/ogr2ogr2.1 -f PostgreSQL...
2016-11-07 17:21:03 UTC: ogr2ogr output:          ERROR 1: PQconnectdb failed.
could not fork new process for connection: Cannot allocate memory

but this can be a blocker for testing. cc/ @javisantana @luisbosque

This is running in a staging which sometimes gives memory problems while deploying. Maybe its related? If it becomes a blocker for testing at some point, let's deploy to another server.

I'd deploy somewhere else for sure. Double-checking because of this is just very time-consuming. It is for me but could be worse if somebody less technical open issues and we need to confirm them.


Installing jq makes whole travis job file prematurely

@ShahimEssaid installing jq in the travis job makes it fail altogether, probably because the travis ubuntu distro does not have the correct repositories installed. Is installing jq really necessary? It is often pre-installed.

Yes, the default Ubuntu distribution for a Travis build does not have a jq
package. I think it is 16.04 if I remember correctly. I changed the build
to use 18.04 by adding:
dist: bionic
to the Travis build. I'm not sure if it is installed by default in the
image used by Travis. I have a:
sudo apt install jq
step to to make sure it's available.
Sent from mobile. Excuse brevity, typos, and the ever helpful
auto-incorrect.
On Sun, Jun 23, 2019, 10:44 AM Nico Matentzoglu<EMAIL_ADDRESS>wrote:

Assigned #742 https://github.com/monarch-initiative/mondo/issues/742 to
@ShahimEssaid https://github.com/ShahimEssaid.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/monarch-initiative/mondo/issues/742?email_source=notifications&email_token=ABELXUPVDU5GLFVLMMOQUSTP36ZAZA5CNFSM4H2ZMQAKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSD663AQ#event-2432560514,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABELXUMAV6FVAXGUZ6SGIGTP36ZAZANCNFSM4H2ZMQAA
.

Yeah, looks like this is the right direction! Still, right now, the travis job cant run at all with that sudo apt install jq.
https://travis-ci.org/monarch-initiative/mondo/builds/548814275?utm_source=github_status&utm_medium=notification
Any idea on how to fix this? Thanks a lot Shahim!

Oh, I see. You meant the setup I had is no longer working. I'll look into
this tomorrow. I'm not sure if they changed their bionic image and the apt
sources are not the same. It should be easy to modify the build to add the
needed source to make it work.
Sent from mobile. Excuse brevity, typos, and the ever helpful
auto-incorrect.
On Sun, Jun 23, 2019, 11:12 AM Nico Matentzoglu<EMAIL_ADDRESS>wrote:

Yeah, looks like this is the right direction! Still, right now, the travis
job cant run at all with that sudo apt install jq.
https://travis-ci.org/monarch-initiative/mondo/builds/548814275?utm_source=github_status&utm_medium=notification
Any idea on how to fix this? Thanks a lot Shahim!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/monarch-initiative/mondo/issues/742?email_source=notifications&email_token=ABELXUOJFHNRZPAEJ7CFC7DP364KXA5CNFSM4H2ZMQAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLD76I#issuecomment-504774649,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABELXUOMPVDXGG6YWZKO443P364KXANCNFSM4H2ZMQAA
.


Wrong formatter when saving .blade.php

Hi,
    "[blade]": {
        "editor.defaultFormatter": "jkillian.custom-local-formatters"
    },
    "[php]": {
        "editor.defaultFormatter": "jkillian.custom-local-formatters"
    },
    "customLocalFormatters.formatters": [
        {
            "command": "/var/www/stdin-blade-stdout.sh",
            "languages": [
                "blade"
            ]
        },
        {
            "command": "/var/www/stdin-pint-stdout.sh",
            "languages": [
                "php"
            ]
        }
    ],

I need to format 2 types of files, .blade.php and .php
They are known to VSCode as blade and php
But when I save on .blade.php files, stdin-pint-stdout.sh gets executed instead

Any ideas why? Thank you!

I found the issue.
I uninstalled the other blade formatters and it caused the blade language to disappear. The fix was to reinstall one of them. Perhaps allowing users to add define their own languages can be part of this package, although it doesn't seem possible from my quick glance of the VSCode docs. :)


Fix Python telemetry

Custom spans haven't been working in Python since the move to the http OTLP exporter:

https://github.com/dagger/dagger/pull/7315

Simplest solution is to replace the package dependency from the grpc exporter to http, but apparently these env vars are no longer set by the engine too:

OTEL_LOGS_EXPORTER=otlp
OTEL_METRICS_EXPORTER=otlp
OTEL_TRACES_EXPORTER=otlp

\cc @TomChv for TypeScript

I'm currently working on the TS SDK to also use the HTTP client instead of GRPC. will open a PR soon


Add Jenkins Jobs to run the trestle-bot commands

Context
Complete an implementation of trestle-bot in Jenkins through the creation of reusable Jenkins logic. There are multiple options here and the approach should explored in the comments on this issue.
Completion Criteria

[ ] Create the reusable jobs via Jenkins Job builder
[ ] Create documentation for usage of the jobs

@beatrizmcouto Perhaps we should transfer this to https://github.com/RedHatProductSecurity/jenkins-trestlebot-examples


[Spike] Client/Server proof of concept

Exit criteria: a design of how client/server would look (or if it would even work)

We spent a few days on this and presented it to the larger team. We'll have more issues to open in the coming days.


Created the Added Loan Feature

I have created the add loan  following the django rest framework  viewset ...

@omidiora your code standards needs attention, i found out Codacy uses pyflakes analyzes and detect file errors.
install pyflakes so you can fix your errors before submiting a pr :wink:

@omidiora check the Django CI/build errors


Provide MacOS ARM Binary

Description
There's currently no pre-built binary for ARM-based MacOS. I'm currently having issues trying to build the cli locally:
Building wheels for collected packages: lru-dict
  Building wheel for lru-dict (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [12 lines of output]
      running bdist_wheel
      running build
      running build_ext
      building 'lru' extension
      creating build
      creating build/temp.macosx-10.9-universal2-3.9
      clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -I/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/include/python3.9 -c lru.c -o build/temp.macosx-10.9-universal2-3.9/lru.o
      lru.c:629:17: error: incompatible function pointer types initializing 'PyCFunction' (aka 'struct _object *(*)(struct _object *, struct _object *)') with an expression of type 'PyCFunctionWithKeywords' (aka 'struct _object *(*)(struct _object *, struct _object *, struct _object *)') [-Wincompatible-function-pointer-types]
          {"popitem", (PyCFunctionWithKeywords)LRU_popitem, METH_VARARGS | METH_KEYWORDS,
                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      1 error generated.
      error: command '/usr/bin/clang' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for lru-dict
  Running setup.py clean for lru-dict
Failed to build lru-dict
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (lru-dict)

ethstaker-deposit-cli, which is a fork, has macOS ARM binaries.
Caution that we’re currently relying on the original security audit done on staking-deposit-cli. Re-audit kicks off in October.


Add documentation

Here's what I changed:

Change default documentation folder from doc/ to docs/. Update README accordingly.
Change default package configuration file from setup.py to pyproject.toml as according to pep517 (under review)
Add flake8 configuration to enable consistent code style among all contributors.

Reference: #38

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.IgnisDa seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Regarding the move to poetry, I can add all relevant documentation including setting up the project locally in the root README.md

Sure that is perfectly fine by me. But the project doesn't contain any requirements.txt or am I missing something here?

Can you please tell me what formatted you use? The one I use (autopep8) doesn't allow me to use tabs for indentation. I can convert the spaces back to tabs, that's not an issue.

I will remove the .flake8 assuming I can get the formatter you use to work.

I will incorporate my .gitignore with yours, not an issue again.

You're right; Sorry. I meant listing the requirements in setup.py.
I don't use any formatter. I just write my code by hand.
Thanks!
Also thanks :hugs:

You're right; Sorry. I meant listing the requirements in setup.py.

Would it be okay to add a requirements.txt? This will hugely benefit future contributors when they are trying to set up the project locally for development.

I'd be okay with that, in which case it would be great if setup.py did not hard-code the same dependencies, but loaded them from requirements.txt and requirements-dev.txt and/or requirements-test.txt.
Thanks!

Even though that can be done, it's not recommended. See https://stackoverflow.com/a/16624700/11667450

Closing this because the master branch has a lot of merge conflicts #42


Link R and Python packages in README of other language

To make sure everyone that comes across this understands it both R and Python.

I think it is a good idea to be more explicit with the links; you can see what I did for the R package at rstudio/vetiver-r#106.


Update juniper_rocket for Rocket 0.4-rc.1

Path handling changed in Rocket 0.4 and this commit updates the way
those paths are handled. It adds an implementation of the
FromFormValue trait to the GraphQLRequest object. It also changes
the documentation to use the multi-segement query string syntax.
All existing tests pass as expected.
Let me know if you have any questions or concerns!

It looks like the test failures are caused by upstream dependencies using the new crate keyword not supported in Rust 1.23. I could be wrong, though.
Let me know if I need to do anything to get the tests to pass before this gets reviewed (and potentially merged).
Thanks!

Sorry for the slow response, this looks great! I'm hoping to get CI green in the next day or so and will look at merging this.

@LegNeato Sounds good! Let me know and I can rebase it so we can get CI green again. I'm looking forward to this being merged in!
Actually, I'll update this PR since rc2 for Rocket 0.4 just came out.

Great, please add an entry to the CHANGELOG for juniper_rocket as well mentioning the min required Rocket version as well 🍻

@LegNeato Sure, can do!
I also need to figure out how to get juniper_rocket to play nicely with the new database support in Rocket 0.4. It's probably just me not knowing how juniper_rocket worked nicely with databases in Rocket 0.3. Either way, when I figure it out, I'll submit a PR with documentation/example updates.

FWIW, I fixed CI on master.

@LegNeato great! I’ll rebase my branch later today to get us green.

@LegNeato Whoops, just saw your comment. I'll try to get this wrapped up today for you.

@LegNeato Do you want me to bump the version in juniper_rocket's Cargo.toml file?

Thanks so much for the PR and sticking through with the changes! 🎉 I hope to do a release later tonight or early tomorrow. 🍻


SecurityCheckError still being called even though i did give it the permission

same problem here, is there a fix

I have an alternate tool that works:
PS C:\> googleplay -a com.google.android.youtube
Title: YouTube
UploadDate: Mar 2, 2022
VersionString: 17.08.34
VersionCode:<PHONE_NUMBER>
NumDownloads: 11.378 B
Size: 40.737 MB
Files: 4
Offer: 0.00 USD

https://github.com/89z/googleplay

No matter what I did I also got this error. Insecure account access enabled (only relevant for another month as a workaround even if it did work, Google is removing this option in 1 month)


Microsoft Exchange Server

Can we send mails using microsoft exchange server, if yes, please suggest a sample. thanks Aravind

If the exchange server supports standard SMTP, then sure. I think the Exchange server needs to be configured for SMTP first?

Hi,
MS exchange server is not smtp support., I tried ews-java-api., it is giving connection reset error when email message has been try to send... Please suggest.
Regards,
Aravind

I don't have experience with Exchange or ews-java-api. This library will work with any server that properly implements the SMTP specification.


README: Make it more beginner-friendly

In the beginning, I found myself quite lost as I was not totally sure how to use Uhyve. This change introduces some additional background information and pointers for people looking to hack on the source code.

Make "code blocks" more consistent
Make some wording more consistent
Additional Markdown magic
Cut the length of some sentences
Add cargo run method for developers
Introduce GitHub-styled admonition boxes

I addressed the review comments and made some additional changes to make them "fit" well, such as adding clearer headers and separating the content better - this introduces some new changes without changing the substance.
Perhaps it would be better if a CONTRIBUTING.md file were to be written in the future instead of cramming everything in the README file, but it should be adequate enough for now.

Oh, and I'd stash these changes into a single commit...

Wait, one more rebase!


allow only supplementalGroups greater 0

If the minimum version of Kyverno needed to support this is 1.3.6, we need to add the relevant annotation as seen here. This also needs to be held until 1.3.6 releases.

@chipzoller should I add this annotation?

Yes, let's go ahead and add this annotation now that 1.3.6 is released.


Set timeout on server stop

Description
Make sure that the tests cases set a timeout on the action of stopping the server. The goal is to:

Prevent that the test suite hangs indefinitely.
Improve the ability to investigate why the test suite is hanging.

Self Check:

[ ] 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)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master in d354d0b8ea8f739429ce1f475bd9ef1829860ba2

Processing #4038.


Use a proper data type for settings.sig_hup

This PR does not attempt to fix #386, but rather only fix SIG_HUP by assigning settings.sig_hup a proper data type (see here for further references).

was there a bug (ie; total loss of sig_hup flip) or similar? I wanted to avoid an extra memory barrier in the clock handler since 1) it's only checked once per second and 2) it's fine if it's off by multiple seconds, even.
I guess it's wrong because the clock handler is also a writer, flipping it to false... but still just a technicality given what's actually going on here.

First, sig_atomic_t does not need to emit a memory barrier, as it only guarantees that the write cannot be interrupted by a signal and is actually performed to memory. Basically, it does not change anything versus what the code is currently expected to do anyway. Unlike the other "atomic" types, this type is not intended to be safe for use in multi-threading, and does not guarantee inter-thread ordering of memory accesses.
Second, the potential bug waiting to happen here is that the clock_handler may theoretically screw up the if that deals with settings.sig_hup. For example, consider that settings.sig_hup is either false, or will be set to false afterwards. This would enable the following transformation, which then begins swallowing "some" signals:
if (settings.sig_hup) {
    settings.sig_hup = false;
    authfile_load(settings.auth_file);
}

->
if (settings.sig_hup) {
    authfile_load(settings.auth_file);
}
settings.sig_hup = false;

With an aggressive enough optimizer, you could then follow this further, e.g., through the whole loop into the following (after all, the ordering is not enforced in any way, and the variable is never written anywhere else):
settings.sig_hup = false;
if (settings.sig_hup) {
    authfile_load(settings.auth_file);
}

The next step is obvious: drop the whole if.
Now, of course there is no reason to be alarmist: This will probably not occur anytime soon. But AFAIK there is no real reason to not do it correctly in this specific instance.

that's fair, thanks!

(though your example makes sense; and I've not had enough coffee to remember things properly today, if I ever saw a compiler "optimize" something outside of a loop conditional for the same variable like that I'd be throwing pitchforks. I'd buy that a computer might reorder things accidentally though)

Well, C and C++ are great areas for program testing and verification research, because they sometimes allow things that make developers throw pitchforks ;).

Out in 1.5.20