Converted Mostly all PNGs to Vectors in the app

Description
PNG's are not scalable and consume large size, hence must be avoided wherever possible in an app. Instead SVG is a better format, these are converted to XML's when imported in an Android App.
Most of the PNG's in drawable folder are converted to vector assets as mentioned in #711 for this I used online tool https://svg-converter.com/
Some PNG's were intentionally not converted to vectors this is because they lost a lot of quality while conversion from PNG(Raster) to SVG(Non Raster) (This Screenshot will make clear what I am trying to convey) these include:

drawable/arrow.png
drawable/compass.png
drawable/compass_unavailaible.png
drawable/currency.png
drawable/eur.png
drawable/ss.png
drawable/worldclock.png
drawable/xag.png
drawable/xau.png

The following showed an error while importing as vector and hence are not converted to Vectors:

drawable/shadow_1.9.png

PNGs in assets/images folder do not show up in app when converted to Vectors and hence are not converted to Vectors
Fixes #711
Type of change
Just put an x in the [] which are valid.

[ ] Bug fix (non-breaking change which fixes an issue) (N/A)
[ ] New feature (non-breaking change which adds functionality) (N/A)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) (N/A)

How Has This Been Tested?

App is tested on Firebase Test Lab on Google Pixel (API 26) Test Results
App is also tested on an AVD I navigated through whole app manually and no crashes were detected.
Please describe the tests that you ran to verify your changes.
[x] ./gradlew assembleDebug assembleRelease
[x] ./gradlew checkstyle

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas (N/A)
[ ] I have made corresponding changes to the documentation (N/A)
[X] My changes generate no new warnings

Great work @sankalpchauhan-me 👍 💯


Changing books stays at the Pagination from the previous book

Changing books stays at the Pagination from the previous book:

Open a book in tN, i.e Titus.
Go to the next page.
Switch to a different book, say, Romans.
The Book opens at the same page level where the user was previously on the Titus book.

The new book should open at the First page/Introduction page.

Verified in Beta-10. Looks good. When a new book/file is selected, it opens on the Introduction page, regardless of the pagination from the Previous book.


chore: Remove unused field port in the backends variable

Remove the unused field port in the definition of the variable backends.

Thanks for the PR! 🚀✅ Lint checks have passed.

We have had lots of churn on the "port" argument throughout this repo. I don't feel confident in removing it.


[Feature] Skip existing for advantage modules

Allows to ask the advantage modules to skip the value network if its output is already present.
@matteobettini @albertbou92
Curious to hear your thoughts about this:
Should all modules skip existing keys by defaults? This could have some unexpected consequences if someone does this
collector = SyncDataCollector(env, policy=actor_cricic, ...) # the collector will also return the value!
for data in collector:
    loss(data)  # the critic is not queried bc the key is already there

What about the other way around? by default not skipping.
In that case we should make sure in the advantage module the value is computed without gradients.

Could you explain a bit more why your example constitutes a problem?
Wouldn't the value computed during rollout be the same if we just compute it later in the loss?
Also I wonder if this is a small step in the direction of #1000.
Because here we are allowing to precompute values  (maybe on bigger batches) outside losse forward.
And in #1000 we want to allow also precomputing targets (maybe on bigger batches) outside loss forward.

Could you explain a bit more why your example constitutes a problem? Wouldn't the value computed during rollout be the same if we just compute it later in the loss?
Also I wonder if this is a small step in the direction of #1000. Because here we are allowing to precompute values (maybe on bigger batches) outside losse forward. And in #1000 we want to allow also precomputing targets (maybe on bigger batches) outside loss forward.
PS in #1000 advantages would not even have access to neural networks. Only losses will. and thus it will make all this even simpler

you can perfectly not pass a network and it will work fine.
I'd like to keep the networks bc it's much easier, otherwise we are decomposing things and we'll be asking users to do
value_net(td)
value_net(td.get("next"))
gae(td)

instead of
gae(td)

Yep i didn't see that we could pass None, that works perfectly.
Thinking about this more, if losses start skipping existing keys by default, this may have some bad consequences if collected data (from collectors or buffers) has some of the loss keys of interest (cause they might be old).
But thinking of #1000 we definitely need a way to precomupte keys for losses (values and targets) and make losses use those precomputed keys.
I think it would be fine to use that skip_existing by default also in the losses and if users feed the losses data with old values it is their problem.
batch = rb.sample(60_000)
loss_module.compute_value_target(batch)
for _ in range(n):
    minibatch = subsample(batch, 1000)
    loss_vals = loss_module(minibatch) # by default uses the precomputed targets

Alternatively, what @albertbou92 says also makes sense, the losses could recompute everything by default and we would need to
batch = rb.sample(60_000)
loss_module.compute_value_target(batch)
for _ in range(n):
    minibatch = subsample(batch, 1000)
    loss_vals = loss_module(minibatch, skip_exisitng=True) # we need to enforce it to not recompute the targets

I am leaning more towards the first option tho

Thinking about this more, if losses start skipping existing keys by default, this may have some bad consequences if collected data (from collectors or buffers) has some of the loss keys of interest (cause they might be old).

yes this is why I set it to False, and why I was asking you guys what you were thinking. I guess we'll leave it as it is.

But thinking of #1000 we definitely need a way to precomupte keys for losses (values and targets) and make losses use those precomputed keys.

if you don't pass the value net to the module an error will be raised bc the entry is missing.

I think it would be fine to use that skip_existing by default also in the losses and if users feed the losses data with old values it is their problem.

yep that's the idea.
There are 2 things you could do
with set_skip_existing(True):
    loss_fn(td)

or
loss_fn.make_value_estimator(..., skip_existing=True)

I am more for the first of the 2 since you are not bound to smth at init time.
Regarding the default of skip_existing i am leaning more towards True but I am fine with anything

I am more for the first of the 2 since you are not bound to smth at init time.

then use that one 😉

Regarding the default of skip_existing i am leaning more towards True but I am fine with anything

Let's put it that way:
worst that can happen when True: wrong value -> no training -> torchrl sucks
worst that can happen when False: slow training -> good training, but slow -> issue

I am more for the first of the 2 since you are not bound to smth at init time.

then use that one 😉

Regarding the default of skip_existing i am leaning more towards True but I am fine with anything

Let's put it that way: worst that can happen when True: wrong value -> no training -> torchrl sucks worst that can happen when False: slow training -> good training, but slow -> issue

Yes  I like the idea of having something that works out of the box, even if there is later on margin for improvement in terms of performance and requires being a bit of an advanced user


Wrong documentation title

As my understanding, this is just to configure http proxy for .net application, not reverse proxy.

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

ID: a0ec145b-37e3-39d7-f7ef-2ea43a3a9b3a
Version Independent ID: 30705b5a-301b-63d9-45df-91b1910990cf
Content: Configure reverse proxies for on-premises environments - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/deployment/onprem-reverseproxy.md
Service: dynamics-ax-platform
GitHub Login: @sarvanisathish
Microsoft Alias: sarvanis

The topic has been renamed.


Always push initial MCP response for new streams

Some users of MCP client (e.g. Pilot) may want an explicit indicate when the initial per-type state has synced. The MCP server layer currently does not push a response until there are resources available for the requested type. Consider pushing an empty response (per type) on new streams.

Is this needed for 1.1?

Possibly. I believe the FullSync indication is hooked up to Pilot's readiness checks.

Fixed by #9553


[InputDatePickerFormField] adds acceptEmptyDate to InputDatePickerFormField Widget

Adds acceptEmptyDate property to InputDatePickerFormField.
Fixes: #117511

acceptEmptyDate is false
acceptEmptyDate is true

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

auto label is removed for flutter/flutter, pr: 124143, due to This PR has not met approval requirements for merging. You have project association CONTRIBUTOR and need 1 more review(s) in order to merge this PR.

Merge guidelines: You need at least one approved review if you are already a MEMBER or two member reviews if you are not a MEMBER before re-applying the autosubmit label. Reviewers: If you left a comment approving, please use the "approve" review action instead.

This pr needs one more approval.

Thank you Viren 💙


Code to face to a heading based off button press

Code written and committed, will test soon tm

Nvm we don't need this


Adapt the loader for microscopy data

AIMS

Load BIDS microscopy data for training and inference
Remove “bids_neuropoly” dependency and replace by “pybids”

Preliminary questions

Use BIDS (following #301)?
Alternatives:
-> Loader that accept multiple data structures
-> Task specific loader
Deal with dataset splits and patches (ADS currently creates new files on disk when splitting and extracting patches)

UPDATE
This issue was divided into 5 steps:

Generate a dataframe with all data and metadata from one or more BIDS dataset
Split the dataset in train/valid/test sets
Refactor BidsDataset classes to use new dataframe and splitting method
Load microscopy data as numpy arrays
Preprocessing of microscopy data for training (2d patching)

I ran some preliminary tests (Unet2D, 1 contrast, 1 label, Center Crop) with the SEM example dataset in PNG format.
This is a breakdown of the 4 main issues I found so far. Specific smaller issues and PR will be open to address them separately.

Sample filename and split

BIDS microscopy uses filename sub-label_sample-label_modality.png with multiple samples per subject.
BIDS microscopy has an additional file samples.tsv to list unique samples ID with participants ID.
ivadomed splits per_patient (microscopy would need a split per sample).
ivadomed uses bids_neuropoly to fetch subjects and filenames.
-- The subject lists are based on unique participants ID.
-- The parsing of the filenames returns subject_id.

File format

ivadomed and bids_neuropoly expects Nifti files (extension nii and nii.gz).
ivadomed uses nibabel library and functions to load files and metadata from header.
Microscopy files will most likely be PNG or OME-TIFF format (not confirmed).

3D vs. 2D

Some for loops failed with a single 2D slice

Unknown issue with metadata when applying preprocessing transforms (still to investigate)

* BIDS microscopy uses filename `sub-label_sample-label_modality.png` with multiple samples per subject.

Would it be possible to drop here a screenshot (ie organisation & hierarchy) of one of your BIDS dataset? so that we could be more familiar with it.

* ivadomed uses `bids_neuropoly` to fetch subjects and filenames.

I would be happy to absorb the code of bids_neuropoly within ivadomed. And as you suggested, we should pull a pair (filename_image, filename_gt) instead of Participant-ID. Or.. alternatively.. to adjust the code for your needs.. could we pull ParticipantYY_sampleXX instead of ParticipantYY.

1. File format

Yeah .. I see! thanks for explaining this. So it will impact the nib.load in the loader and the pred_to_nii current functions.

* Some for loops failed with a single 2D slice

As you mentioned, I think that adding a channel when single slice (and loop across this channel) should fix this.

1. Unknown issue with metadata when applying preprocessing transforms (still to investigate)

Maybe because of bids_neuropoly? or the fact that PNG do not have metadata? or maybe both? eheh, keep us posted :-)

As a reference, the first version of an example dataset in PNG format can be found here. The subject sub-rat3 is an example of subject with multiples samples.
The directories/files hierarchy template is here in the official BIDS extension proposal.

* move data-management APIs outside of "utils.py" (which is a non-specific file name) and put it in a data-management API file, e.g. . It is [good practice](https://breadcrumbscollector.tech/stop-naming-your-python-modules-utils/) to avoid as much as possible to dump things in a file called utils

Could you please point out what you are referring to here? Are you refering to ivadomed/loader/utils.py.
Data management is very much done by the files in this folder: ivadomed/loader and by bids-neuropoly. We are hoping to absorb the latter within ivadomed in a near future.

As a reference, the first version of an example dataset in PNG format can be found here. The subject sub-rat3 is an example of subject with multiples samples.
The directories/files hierarchy template is here in the official BIDS extension proposal.

Very helpful, thank you!
To summarize the differences between MRI and microscopy, I can see:

anat vs microscopy folder
.nii,gz vs .png
subXX_contrast* vs. subXX_sample_contrast*

Am I missing something?
Looks manageable / on our reach :-)

Could you please point out what you are referring to here? Are you refering to ivadomed/loader/utils.py.
Data management is very much done by the files in this folder: ivadomed/loader and by bids-neuropoly. We are hoping to absorb the latter within ivadomed in a near future.

sorry my mistake-- i've updated my comment  https://github.com/ivadomed/ivadomed/issues/304#issuecomment-705629719

To summarize the differences between MRI and microscopy, I can see:

anat vs microscopy folder
.nii,gz vs .png
subXX_contrast* vs. subXX_sample_contrast*

Am I missing something?

There is also the samples.tsv file which identify each unique samples ID and the corresponding participant ID.

File format:
The 2020-10-20 version of the BEP now accept both PNG (.png) and OME-TIFF (.ome-tif) formats.
Split in train/valid/test group:
For microscopy, the following optional entities in filename anticipated with the BEP:
ses-<label> = session (same as MRI)
down-<factor> = downsampling factor
ce-<label> = contrast enhancement agent (same as MRI)
run-<label> = multiple images of the same sample (present in MRI with a different definition)
Example of run label (not part of the SEM example dataset r2020108):
sub-01_sample-01_run-01_SEM.png
sub-01_sample-01_run-02_SEM.png
sub-01_sample-02_run-01_SEM.png
sub-01_sample-02_run-02_SEM.png

run-<label> must be part of the split, all runs from a same sample from a same subject should be in the same group.

Update on the 5 steps of the issue
STEP 1: Generate a dataframe with all metadata from one or more BIDS datasets
Status: completed with minor retrocompatibility issues
Related issues and PR:

Issue #519/PR #538: Generate dataframe for new loader
Issue #563/PR #584: Write a test for create_bids_dataframe function
Issue #595/PR #648: BidsDataframe class for new loader
PR #687: New loader: input from multiple BIDS datasets

TODO (retrocompatibility issues):

Issue #708: Add entity and metadata filtering in new loader

STEP 2: Split the dataset in train/valid/test sets
Status: completed
Related issues and PR:

Issue #564/PR #591: Adapt splitting methods for new loader

TODO (new development in BEP031):

sample_id is no longer unique across a dataset, this will affect the split dataset per sample_id, the topic is still in discussion in the development of the BEP031, we should wait before making changes.

STEP 3: Refactor BidsDataset classes to use new dataframe and splitting method
Status: completed with minor retrocompatibility issues
Related issues and PR:

Issue #596/PR #691: Refactor BidsDataset classes for new loader
Issue #698/PR #699: First integration of new loader in pipeline
Issue #716/PR #721: Add support for CT-scan files in new loader
Issue #718/PR #725: Update test_loader.py
Issue #726/Issue #742/PR #746: Remove merge_bids_dataset from loader/utils.py and Drop bids_neuropoly

TODO (retrocompatibility issues):

Issue #706: Keep only typical config files + Standardise them
Issue #707: Prepare_dataset_vertebral_labeling does not produce bids compliant files
Issue #710: Adapt FiLM "contrasts" metadata option for new loader
Issue #717: Update tutorial "One-class segmentation with 2D U-Net"

STEP 4: Load microscopy data as numpy arrays
Status: completed for PNG/TIF/JPG files only
Related issues and PR:

Issue #733/PR #734: Load PNG/TIF/JPG microscopy files as numpy array in new loader

TODO:

Issue #739: Load OMETIFF microscopy files as numpy array in new loader

STEP 5: Preprocessing of microscopy data for training (2d patching)
Status: in-progress
Related issues and PR:

Issue #747/PR #763: Generate 2D patches for microscopy loader

TODO:

Issue #306: Implement the inference procedure to be able to test the 2d patching
Issue XX: “bounding box” feature has dependencies to NifTI files/Nibabel objects


Add code of conduct

As discussed, this is essentially the same CoC as for Project Jupyter.

We are not making a distinction between the steering committee and the code of conduct.
I have left the link to the enforecement document out until I add the enforcement document.

We need to set up an email to the steering committee, and a reporting google form.

@jasongrout @kaiayoung @ChakriCherukuri feel free to merge this as we iterate on the document.


EntityFrameworkCore has AddRange Method

In ORM Cookbook/Recipes.EntityFrameworkCore/LargeBatch/LargeBatchScenario.cs
          foreach (var employee in employees)
                context.Employees.Add(employee);

can be replaced with
            context.Employees.AddRange(employees);

as described in https://docs.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.dbset-1.addrange

Thank you for the correction.


net::ERR_ABORTED 404 (Not Found)

Pulse Version
1.0.0-beta-5
Laravel Version
10.35.0
PHP Version
8.2.0
Database Driver & Version
No response
Description

Also saw some existing issues created for this, none of those helped, also noticed none of them had a path in the url
Steps To Reproduce
So installed the new version of Pulse and did all the necessary steps to publish it. And then when I get to the dashboard this is what I see. But the APP_URL has a path associated with it and the URL called in the console doesn't take that path Pulse

I have that issue too.

Check that the route actually exists with php artisan route:list. It is a route that livewire adds.
It should look like this
GET|HEAD        livewire/livewire.js ........................................................................................................................................................... Livewire\Mechanisms › FrontendAssets@returnJavaScriptAsFil

Just noticed that you have /public in your url. Seems you didnt set up your webserver to point to the public directory

Fix this first.

https://admin.blablabla/livewire/livewire.js?id=f477dd12. I can open in a new tab, I see the code, but fetching with XHR results 404.
I alos have the route

@sandesh556 Just noticed that you have /public in your url. Seems you didnt set up your webserver to point to the public directory

Fix this first.. Or use php artisan serve to serve the website while developing

This doesn't explain why the APP_URL is not being taken. Tried a new laravel app using Serve that works, pulse renders the dashboard. But if there is a path involved in the APP_URL why is it not being considered

What version of Livewire are you using? Also, I believe @sinnbeck is on to something, Laravel isn't meant to be configured under a sub-directory like that.

Fixed
location = /livewire/livewire.js {
   expires off;
   try_files $uri $uri/ /index.php?$query_string;
}

in Ngnix

Opened a PR to address this moving forward: https://github.com/laravel/pulse/pull/266


RUN-1016: cleanup and work toward fixing getterValues

https://linear.app/replay/issue/RUN-1016/fix-pauseobjectpreviewgettervalues
NOTE: This is not fixed yet. I deprioritized this because I went into this as a result of a misunderstanding, so i just push what I have so far and move on to other issues for now.

Let's wait on reviews until we're ready to focus on this.


Hook up Smithy model validation through the polymorph CLI

This comes for free with the Smithy build plugin interface. e.g. if you do .gradlew build in the TestModels/aws-sdks/sqs test model, you'll see warnings like:
WARNING: com.amazonaws.sqs#MessageSystemAttributeName (ModelDeprecation)
     @ /Users/salkeldr/Documents/GitHub/smithy-dafny/TestModels/aws-sdks/sqs/model/sqs.json
     |
3370 |         "smithy.api#enum": [
     |                            ^
     = The enum trait is deprecated. Smithy 2.0 models should use the enum shape.
...

This validation can potentially catch a number of model errors/warning as part of polymorph library development.
Related to https://github.com/smithy-lang/smithy-dafny/issues/315, as we'll get more milage out of this if we also define the right validation rules for polymorph traits like @reference and @javadoc.

Alternatively, it might be better to accelerate the deprecation of the polymorph CLI and add the missing features to the Smithy build plugin, since then we get all the benefits of the Smithy build pipeline.

Technically, the CLI is already running validation on the model, it's just that we don't output any of the validation events unless there are ERROR or DANGER level events. https://github.com/smithy-lang/smithy-dafny/pull/355 makes a change to always output events if there are any, so I think it's enough to resolve this issue.


refactor: validator's naive N GenServer and Supervisor removal

Motivation
This is part of the effort for removing all GenServers and redesign the concurrency architecture from scratch
Description
In this PR I'll tackle the most basic way for the GenServer removal, it doesn't deal with some well-needed refactors (like sharing duties and avoid duplicated work), it just starts to manage state at the ValidatorManager level, ~with a simple Agent (which could be easily replaced later by storing the state in the DB if needed).~ After going through some issues regarding the attestation and block proposal its not posible to execute the notification for Validators Synchronously inside the Clock as it was done. Temporarily reintroduce one GenServer for the ValidatorManager.

A validator's state has a head_slot and head_root, which are shared by all. We might want to have them in the validator manager instead, and add those to the function calls. Not sure if that simplifies or complicates the code, but it deduplicates the variables.

Yes, totally agree, I'll be more explicit in the PR description about this, I'll gathered it upon the "it doesn't deal with some well-needed refactors", but yes, both head and slot as well as duty management should be shared. I didn't know either if it simplifies things or not but also agreed that's not the place for it. I just tried to touch ligic as fewer as possible in this PR, and add more logging.

Maybe we should have the uninitialized validators in a separate variable instead of having them mixed and notifying them all. This is completely up to discussion and opinionated, but I do find it a bit weird to have a try_setup on every notification instead of trying that in the manager each time there's a change of target state.

Also agree, they are hard to track, up until now it wasn't an issue except for the validators just being there doing nothing, and as far as i could see the condition for them not being able to initialize is the lack of the public key in the validators set. I just ignore the calls in those cases for now instead of retrying the setup which wouldn't work in the new schema, holding all the validators until this ones correctly set up. I also think this is part of the deeper refactor.


[AppService] az webapp list: Fix the bug --show-details fails while resource group name is not specified

Related command

az webapp list
Description

az webapp list is throwing unexpected error while using --show-details without specifying parameter -g. It is not an expected behavior and this PR is used to fix the bug.
Testing Guide

Run test created for the command or run command az webapp list --show-details
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

AppService


The program does not show all images

The program shows only 100 images, although the author has more than 1000

Hi,
thanks for the feedback! Yes, these are the current limitations of the official API. I will implement a "load more" button in few weeks.
Any other issues on your system? Does the app what it supposed to? :)

Added the "load more" button to the v0.0.2.
Thank you for contributing.


This plugin doesn't support Windows, does it?

I tried to compile this program on Windows, but failed.

Hi @dengzhicong and sorry for the late reply.
We currently do not provide pre-built packages for Windows. I am checking if we can quickly add a Windows pipeline without too much trouble, with the caveat that Windows is not really a priority for us.
This is one of the areas where we would really appreciate contributions from the community.


docs: elaborate on debugging jasmine node tests

The existing instructions don't quite cover a full debugging setup and miss some flags that allow debugging without modification of BUILD files.
PR Checklist
Please check to confirm your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

The changes were merged into the following branches: main, 18.2.x


JsRT: When calling resolve, the resolve function is thrown if JsSetPromiseContinuationCallback hasn't been called

Example case:
(function() {
    var resolve, reject;
    var p = new Promise(function(res, rej) {
        resolve = res;
        reject = rej;
    });

    p.then(function(val) {
        echo('The result is ' + val); // 'echo' is host-provided to output to console
    });

    try {
        resolve(10);
    }
    catch (ex) {
        echo('Failed to resolve: ' + ex.toString());
        echo(typeof ex);
    }
})();

If this code is evaluated and JsSetPromiseContinuationCallback has not been called, the failure case (catch branch) is invoked, and the following is output:
Failed to resolve: function() {
    [native code]
}

function

The thrown thing appears to be the resolve function itself instead of a meaningful error.  A meaningful error should be thrown instead, e.g., TypeError: Promises may not be executed because the host has not provided a continuation callback in which to enqueue pending tasks.

I agree. The current error is not pointing people at the right direction. @Yongqu would you mind taking a look?

Agree. It's a good error to have.


terraform_0_14: 0.14.5 -> 0.14.6

Motivation for this change
Update to 0.14.6
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111971 run on x86_64-darwin 1

1 package built:

terraform_0_14


why the previous column is nil can affect the value of the next column?

$go version
go version go1.8.3 darwin/amd64

Assuming my table has two columns，name(VARCHAR),sex(TINYINT)
select name,sex from mytable
if the name has nil value, the next column sex will be zero even though is not zero,
have anybody this problem?

Thank you for raising this issue. Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions. We only use our bug tracker for tracking bugs and tracking proposals going through the Proposal Process.
Please see https://golang.org/wiki/Questions for good places to ask questions.


[feaLib] Unknown glyph class @MMK_R_period.right

This is a new behaviour - not certain if this is correct error reporting (then we have a problem with the glyphs file) or this is an issue/problem in fealib.
When processing NotoSansDisplayItalic-MM.glyphs
Archive.zip
(attached) we get the following error:
File "/usr/local/lib/python2.7/dist-packages/FontTools/fontTools/feaLib/builder.py", line 13, in addOpenTypeFeatures
builder.build()
File "/usr/local/lib/python2.7/dist-packages/FontTools/fontTools/feaLib/builder.py", line 50, in build
self.parseTree = Parser(self.featurefile_path).parse()
File "/usr/local/lib/python2.7/dist-packages/FontTools/fontTools/feaLib/parser.py", line 40, in parse
statements.append(self.parse_feature_block_())
File "/usr/local/lib/python2.7/dist-packages/FontTools/fontTools/feaLib/parser.py", line 820, in parse_feature_block_
self.parse_block_(block, vertical)
File "/usr/local/lib/python2.7/dist-packages/FontTools/fontTools/feaLib/parser.py", line 867, in parse_block_
self.parse_position_(enumerated=False, vertical=vertical))
File "/usr/local/lib/python2.7/dist-packages/FontTools/fontTools/feaLib/parser.py", line 448, in parse_position_
self.parse_glyph_pattern_(vertical)
File "/usr/local/lib/python2.7/dist-packages/FontTools/fontTools/feaLib/parser.py", line 246, in parse_glyph_pattern_
gc = self.parse_glyphclass_(accept_glyphname=True)
File "/usr/local/lib/python2.7/dist-packages/FontTools/fontTools/feaLib/parser.py", line 181, in parse_glyphclass_
self.cur_token_location_)
fontTools.feaLib.error.FeatureLibError: /tmp/tmpYZ6X6d:5:24: Unknown glyph class @MMK_R_period.right
tmpYZ6X6d is also attached

Archive.zip

I assume the following (using different glyphs as input) is related:
==== building src/NotoSansHebrew-MM.glyphs ====
[...]

WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.
WARNING: Non-existent glyph class @MMK_R_period.right found in kerning rules.

Excerpt from the attachment:
feature kern {
    pos B<EMAIL_ADDRESS>-10;
} kern;

This is invalid syntax, and the compiler is correctly rejecting it. (Also, makeotf rejects it as well). Perhaps the input should have looked like the following? Anyhow, looks like a problem in an earlier stage.
feature kern {
    @public.kern2.MMK_R_period.right = [A B C D];
    pos B @public.kern2.MMK_R_period.right -10;
} kern;

Hm, I wanted to file a bug on fontmake, but fontmake -g NotoSansDisplayItalic-MM.glyphs from your attached Archive.zip actually worked just fine. Could not reproduce.

However, I ran into the same problem with another font; see https://github.com/googlei18n/fontmake/issues/11.


Add Decimal Type support in Native Parquet Reader

@majetideepak Is there any progress on this issue?

Resolved with
https://github.com/facebookincubator/velox/pull/2714
https://github.com/facebookincubator/velox/pull/2822
https://github.com/facebookincubator/velox/pull/2921


Missing type for PEP695 TypeAliasType vs TypeAlias when using TypeAdapter

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
There seems to be a difference between the type that is returned from TypeAdapter when used on a PEP695 TypeAliasType compared to when it is used on a TypeAlias. See example below. When TypeAdapter is used on a TypeAlias, the correct type is shown. However, when the TypeAliasType is used, the type is shown as TypeAliasType. This causes the type-checker to see red.
Example Code
from typing import TypeAlias, reveal_type

from pydantic import TypeAdapter

my_type_alias: TypeAlias = list[dict[str, list[int]]]
x: my_type_alias = [{"a": [1, 2, 3]}]

res = TypeAdapter(type=my_type_alias).validate_python(x)
reveal_type(res)  # type of res is "list[dict[str, list[int]]]"

type my_type = list[dict[str, list[int]]]
x: my_type = [{"a": [1, 2, 3]}]

res = TypeAdapter(type=my_type).validate_python(x)
reveal_type(res)  # type of res is "TypeAliasType"

Python, Pydantic & OS Version
pydantic version: 2.6.3
        pydantic-core version: 2.16.3
          pydantic-core build: profile=release pgo=true
                 install path: /usr/local/lib/python3.12/site-packages/pydantic
               python version: 3.12.2 (main, Feb 13 2024, 09:17:46) [GCC 12.2.0]
                     platform: Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.36
             related packages: pyright-1.1.352 pyright-1.1.353 typing_extensions-4.10.0 pydantic-extra-types-2.6.0 fastapi-0.110.0 pydantic-settings-2.2.1
                       commit: unknown

Relates to https://github.com/pydantic/pydantic/discussions/7094

@einarwar,
Thanks for reporting this. Also related is https://github.com/pydantic/pydantic/issues/8984. pydantic doesn't offer robust support for the new type syntax yet, it seems. Not sure how difficult this will be to support, but PRs are of course welcome!

I believe this issue is related:
from pydantic import AnyHttpUrl, TypeAdapter

def ensure_url(url: AnyHttpUrl | str) -> AnyHttpUrl:
    if isinstance(url, AnyHttpUrl):  # pyright: ignore [reportArgumentType]
        return url
    return TypeAdapter(AnyHttpUrl).validate_python(url)  # pyright: ignore [reportCallIssue, reportReturnType]

Hopefully something can be done to remove the requirement for those ignore comments.


[0.9.0] Panic if database is not specified on query via API

I opened a influx console tool and forgot to run USE db_name. Than selected something select * from response_codesand everything that I got: ERR: Get http://localhost:8086/query?db=&q=select+*+from+response_codes: EOF` and influxdd panics.
Is it ok that every one can kill my influx server this way?

Dupe of issue #2932.


Dependency / installation issues

I'm having trouble getting the app working after installing into a fresh virtual environment python 3.10.
Note I did have to pip install dask[dataframe] after installation from pip install . of this repository.
/SpatialProteomicsQC/py310-env/lib/python3.10/site-packages/param/init.py", line 1347, in validate_class
raise ValueError(
ValueError: ClassSelector parameter None value must be an instance of (function, tuple), not <function size at 0x73804b9f3930>.
I did try a few other versions of param as well, but without luck.
/SpatialProteomicsQC/py310-env/lib/python3.10/site-packages/param/__init__.py", line 1347, in _validate_class_
    raise ValueError(
ValueError: ClassSelector parameter None value must be an instance of (function, tuple), not <function size at 0x73804b9f3930>.

the call to param comes from some portion of loading of hvplot or holoviews I believe.
(py310-env)~/t/S/webapp (master)> pip freeze --all
bleach==6.1.0
bokeh==2.4.3
certifi==2024.8.30
charset-normalizer==3.3.2
click==8.1.7
cloudpickle==3.0.0
colorcet==3.1.0
cycler==0.12.1
dask==2024.9.1
dask-expr==1.1.15
datashader==0.16.3
domaps==1.0.1
et-xmlfile==1.1.0
fonttools==4.54.1
fsspec==2024.9.0
holoviews==1.14.9
hvplot==0.10.0
idna==3.10
importlib_metadata==8.5.0
Jinja2==2.11.3
joblib==1.4.2
kiwisolver==1.4.7
llvmlite==0.43.0
locket==1.0.0
Markdown==3.7
MarkupSafe==2.0.1
matplotlib==3.5.3
matplotlib-venn==0.11.6
multipledispatch==1.0.0
natsort==7.1.1
networkx==3.3
numba==0.60.0
numpy==1.26.4
openpyxl==3.1.5
packaging==24.1
pandas==2.2.3
panel==0.14.2
param==1.12.3
partd==1.4.2
patsy==0.5.6
pillow==10.4.0
pip==22.0.2
plotly==4.14.1
pyarrow==17.0.0
pyct==0.5.0
pyparsing==3.1.4
python-dateutil==2.9.0.post0
pytz==2024.2
pyviz_comms==3.0.3
PyYAML==6.0.2
requests==2.32.3
retrying==1.3.4
scikit-learn==1.5.2
scipy==1.14.1
setuptools==59.6.0
six==1.16.0
statsmodels==0.14.1
threadpoolctl==3.5.0
toolz==0.12.1
tornado==6.4.1
tqdm==4.66.5
typing_extensions==4.12.2
tzdata==2024.2
UpSetPlot==0.9.0
urllib3==2.2.3
webencodings==0.5.1
xarray==2023.1.0
zipp==3.20.2

Hello, yes this is an issue with the holoviews/networksx and an error I have encountered before. Try installing with python 3.8, please. This should work with the specified requirements. If that still does not work, I can post a pip freeze of my own environment.

Thank you a fresh venv with python3 .8 worked.
I had tried 3.10 and 3.9 previously (after 3.12 which also failed).
with python 3.8 and pip install . of the root of this repository I've successfully loaded and processed an example dataset provided


BotBuilder, as a library, should not pin 3rd party dependencies

Version
4.11.0
Describe the bug
I'm trying to add BotBuilder to an app that already has ibm-watson as a dependency.
The conflict is due to botbuilder-core pinning a very old version of PyJWT.
ibm-watson needs ibm-cloud-sdk-core which needs PyJWT. ibm-cloud-sdk-core uses a range of versions, specifying PyJWT>=2.0.0a1,<3.0.0 in the last few versions, but for all older versions, it required PyJWT>=1.7.1.
https://github.com/microsoft/botbuilder-python/blob/11b08778beb6f3d31c65fb35b54beabb89fb4bdc/libraries/botframework-connector/setup.py#L12
BotBuilder is a library meant to be embedded in other applications, so pinning 3rd party deps is dangerous.
Looking through the dependencies in the various botbuilder libraries, it looks like several have dependencies that are pinned instead of specifying a range of valid versions. For the microsoft-provided deps, pinning makes perfect sense. For 3rd party deps, please do not pin the dep version (instead specify a range) and allow the application that is using the botbuilder framework to pin its own deps
To Reproduce
Steps to reproduce the behavior:

pip install --upgrade pip (in a virtualenv) to use the new resolver that refuses to install conflicting dependencies
pip install ibm-watson botbuilder-core==4.11.0
pip backtracks for awhile until it gets to some very old versions of ibm-watson that it can't process and dies.
even if pip could process the old versions, no version of the ibm lib ever supported version 1.5.3 of PyJWT that was released in 2018.

Expected behavior
For microsoft/azure libraries, go ahead and pin the deps. The botbuilder itself is versioned together, so pinning makes perfect sense.
If you want to pin the version 3rd party deps in requirements.txt, that also is fine so that you can say "This is the most tested/supported version". But please, in setup.py, specify a range of valid versions for 3rd party deps to ease integrating BotBuilder in existing applications.
Additional context
Here are the 3rd party dependency lines in setup.py that pin 3rd party deps in 4.11.0 (the deps are still pinned in main/4.12.0):
PyJWT, requests, cryptography
very common packages, likely to cause conflicts. Caused a conflict for me
https://github.com/microsoft/botbuilder-python/blob/11b08778beb6f3d31c65fb35b54beabb89fb4bdc/libraries/botframework-connector/setup.py#L10-L12
aiohttp
very common package, likely to cause conflicts
https://github.com/microsoft/botbuilder-python/blob/11b08778beb6f3d31c65fb35b54beabb89fb4bdc/libraries/botbuilder-integration-aiohttp/setup.py#L12
https://github.com/microsoft/botbuilder-python/blob/11b08778beb6f3d31c65fb35b54beabb89fb4bdc/libraries/botbuilder-integration-applicationinsights-aiohttp/setup.py#L9
https://github.com/microsoft/botbuilder-python/blob/11b08778beb6f3d31c65fb35b54beabb89fb4bdc/libraries/botbuilder-ai/setup.py#L11
babel
common package, likely to cause conflicts
https://github.com/microsoft/botbuilder-python/blob/11b08778beb6f3d31c65fb35b54beabb89fb4bdc/libraries/botbuilder-dialogs/setup.py#L14
jsonpickle
less common package, so I'm not as concerned.
https://github.com/microsoft/botbuilder-python/blob/11b08778beb6f3d31c65fb35b54beabb89fb4bdc/libraries/botbuilder-core/setup.py#L11
https://github.com/microsoft/botbuilder-python/blob/11b08778beb6f3d31c65fb35b54beabb89fb4bdc/libraries/botbuilder-azure/setup.py#L12

Why is cryptography listed in the deps for botframework-connector? It is not imported anywhere by botframework-connector. And, these deps specify their own dependencies:

adal==1.2.1 requires cryptography>=1.1.0
msal==1.6.0 requires cryptography>=0.6,<4
PyJWT>=1.5.3,<2.0.0 requires cryptography>=1.4.0,<4.0.0 (newer versions bump the min, but not the max)
requests>=2.23.0,<3.0.0 requires cryptography>=1.3.4

I think cryptography should be removed from the requirements of botframework-connector.

Why is cryptography listed in the deps for botframework-connector? It is not imported anywhere by botframework-connector. And, these deps specify their own dependencies:

adal==1.2.1 requires cryptography>=1.1.0
msal==1.6.0 requires cryptography>=0.6,<4
PyJWT>=1.5.3,<2.0.0 requires cryptography>=1.4.0,<4.0.0 (newer versions bump the min, but not the max)
requests>=2.23.0,<3.0.0 requires cryptography>=1.3.4

I think cryptography should be removed from the requirements of botframework-connector.

You beat me to creating an issue about this. I am facing the same hurdle, my application uses latest pyjwt 2.0 whilst botframework uses the rather ancient 1.5.3.

You beat me to creating an issue about this. I am facing the same hurdle, my application uses latest pyjwt 2.0 whilst botframework uses the rather ancient 1.5.3.

sferdi0: Can you check out where botframework-connector is using PyJWT to see what it would take to upgrade to 2.0? It is safe to upgrade to <2.0 without code changes (based on reading the changelog), but several things changed in 2.0.

sferdi0: Can you check out where botframework-connector is using PyJWT to see what it would take to upgrade to 2.0? It is safe to upgrade to <2.0 without code changes (based on reading the changelog), but several things changed in 2.0.

@cognifloyd I can't validate incoming messages for my Bot, e.g: my route is /api/messages and Microsoft sends me, for example, a conversationUpdate (when an user adds my app/bot to their Teams) - and this code tries to validate the incoming request first using it's Authorization header:
https://github.com/microsoft/botbuilder-python/blob/c491636b2df31e074d211586b0204192fcaf58e1/libraries/botframework-connector/botframework/connector/auth/skill_validation.py#L58
In the new(er) PyJWT 2.0 that should be:
token = jwt.decode(token, options={"verify_signature": False})

There are more places where JWT is used throughout the code. I don't think a migration would be complicated at all.

@cognifloyd I can't validate incoming messages for my Bot, e.g: my route is /api/messages and Microsoft sends me, for example, a conversationUpdate (when an user adds my app/bot to their Teams) - and this code tries to validate the incoming request first using it's Authorization header:
https://github.com/microsoft/botbuilder-python/blob/c491636b2df31e074d211586b0204192fcaf58e1/libraries/botframework-connector/botframework/connector/auth/skill_validation.py#L58
In the new(er) PyJWT 2.0 that should be:
token = jwt.decode(token, options={"verify_signature": False})

There are more places where JWT is used throughout the code. I don't think a migration would be complicated at all.

OK. I tested with the following dependency updates and all tests pass without any code changes.
requests, ~crptography~, PyJWT

libraries/botframework-connector/setup.py#L10-L11

Note that this drops the explicit cryptography requirement, as botframework-connector does not use it directly.
-    "requests==2.23.0",
+    "requests>=2.23.0,<2.26",

-    "cryptography==3.2",

-    "PyJWT==1.5.3",
+    "PyJWT>=1.5.3,<2.0.0",

aiohttp

libraries/botbuilder-ai/setup.py#L11
libraries/botbuilder-integration-aiohttp/setup.py#L12
libraries/botbuilder-integration-applicationinsights-aiohttp/setup.py#L9

-    "aiohttp==3.6.2",
+    "aiohttp>=3.6.2,<3.8.0",

aioresponses

libraries/botbuilder-ai/tests/requirements.txt#L1

-aioresponses==0.6.3
+aioresponses>=0.7.1

jsonpickle

libraries/botbuilder-azure/setup.py#L12
libraries/botbuilder-core/setup.py#L11

-    "jsonpickle==1.2",
+    "jsonpickle>=1.2,<1.5",

babel
I didn't test updating babel.

OK. I tested with the following dependency updates and all tests pass without any code changes.
requests, ~crptography~, PyJWT

libraries/botframework-connector/setup.py#L10-L11

Note that this drops the explicit cryptography requirement, as botframework-connector does not use it directly.
-    "requests==2.23.0",
+    "requests>=2.23.0,<2.26",

-    "cryptography==3.2",

-    "PyJWT==1.5.3",
+    "PyJWT>=1.5.3,<2.0.0",

aiohttp

libraries/botbuilder-ai/setup.py#L11
libraries/botbuilder-integration-aiohttp/setup.py#L12
libraries/botbuilder-integration-applicationinsights-aiohttp/setup.py#L9

-    "aiohttp==3.6.2",
+    "aiohttp>=3.6.2,<3.8.0",

aioresponses

libraries/botbuilder-ai/tests/requirements.txt#L1

-aioresponses==0.6.3
+aioresponses>=0.7.1

jsonpickle

libraries/botbuilder-azure/setup.py#L12
libraries/botbuilder-core/setup.py#L11

-    "jsonpickle==1.2",
+    "jsonpickle>=1.2,<1.5",

babel
I didn't test updating babel.

At a glance, bumping to PyJWT 2.0 will also require bumping msal and possibly others, as that also requires <2.0.
I would be okay with any updated PyJWT requirement (whether or not that includes v2.0) as long as it allows installing PyJWT>=1.7.1.
Please and thank you!

At a glance, bumping to PyJWT 2.0 will also require bumping msal and possibly others, as that also requires <2.0.
I would be okay with any updated PyJWT requirement (whether or not that includes v2.0) as long as it allows installing PyJWT>=1.7.1.
Please and thank you!

Also, if anyone else can submit a PR, that would be awesome. Sorry, I'm unable to contribute a PR myself, but I hope I've left enough breadcrumbs for others to get this updated.

Also, if anyone else can submit a PR, that would be awesome. Sorry, I'm unable to contribute a PR myself, but I hope I've left enough breadcrumbs for others to get this updated.

Hello @cognifloyd thanks for bringing this up to our attention. We have decided in the past for a pinning strategy due to breaking changes bydependencies updates appearing on our daily/PR builds.
With the arguments and situation presented in this thread we're considering to move to a "version range" policy, but we would have to draft a process for continuous development.
We will be updating this thread with any decisions taken in the following weeks, with solutions potentially similar to the one you proposed.
Let us know if you have further comments.

Hello @cognifloyd thanks for bringing this up to our attention. We have decided in the past for a pinning strategy due to breaking changes bydependencies updates appearing on our daily/PR builds.
With the arguments and situation presented in this thread we're considering to move to a "version range" policy, but we would have to draft a process for continuous development.
We will be updating this thread with any decisions taken in the following weeks, with solutions potentially similar to the one you proposed.
Let us know if you have further comments.

I think even though we move forward on the "version range" policy. After every release of the SDK, we should bump every dependencies to their latest version.
It's good for hygiene, progression on technical debts, and reducing chances of vulnerabilities.
@axelsrz could you bring this up in R13 planning?

Is there any progress on this? I'm also running into this with the requests library.
If an exploit was to be found in requests then all applications using this SDK are required to remain vulnerable until botbuilder update their pinned dependency. Requests is currently pinned to a version from over a year ago.
All other SDKs that used by applications that also declare this dependency are also being forced into specifiying a low range by this library.
If the policy is to continue pinning, then the dependencies must be tested and frequently updated as a priority. But I've not experienced an instance of requests making a breaking change without incrementing the major version, I don't really see a justification for pinning it to a minor.

Thanks for all the work and investigation, @cognifloyd and other contributors here, it's fantastic to receive such detailed feedback.

Why is cryptography listed in the deps for botframework-connector? It is not imported anywhere by botframework-connector. And, these deps specify their own dependencies:
* `adal==1.2.1` requires `cryptography>=1.1.0`

* `msal==1.6.0` requires `cryptography>=0.6,<4`

* `PyJWT>=1.5.3,<2.0.0` requires `cryptography>=1.4.0,<4.0.0` (newer versions bump the min, but not the max)

* `requests>=2.23.0,<3.0.0` requires `cryptography>=1.3.4`

I think cryptography should be removed from the requirements of botframework-connector.

I'm sure adal should also be removed as it is unused: #1620


TypeError: Cannot call method 'match' of undefined

Any thoughts on this? Am I the only one that's seeing this?
This is being caught in: config/routes.js#completeRegistration
slide-server-server-21 (err): TypeError: Cannot call method 'match' of undefined
slide-server-server-21 (err):     at Layer.handle (/home/gmike/projects/slide-server/src/server2/node_modules/subdomain/lib/subdomain.js:41:26)
slide-server-server-21 (err):     at trim_prefix (/home/gmike/projects/slide-server/src/server2/node_modules/express/lib/router/index.js:226:17)
slide-server-server-21 (err):     at c (/home/gmike/projects/slide-server/src/server2/node_modules/express/lib/router/index.js:198:9)
slide-server-server-21 (err):     at Function.proto.process_params (/home/gmike/projects/slide-server/src/server2/node_modules/express/lib/router/index.js:251:12)
slide-server-server-21 (err):     at next (/home/gmike/projects/slide-server/src/server2/node_modules/express/lib/router/index.js:189:19)
slide-server-server-21 (err):     at Layer.methodOverride [as handle] (/home/gmike/projects/slide-server/src/server2/node_modules/method-override/index.js:48:5)
slide-server-server-21 (err):     at trim_prefix (/home/gmike/projects/slide-server/src/server2/node_modules/express/lib/router/index.js:226:17)
slide-server-server-21 (err):     at c (/home/gmike/projects/slide-server/src/server2/node_modules/express/lib/router/index.js:198:9)
slide-server-server-21 (err):     at Function.proto.process_params (/home/gmike/projects/slide-server/src/server2/node_modules/express/lib/router/index.js:251:12)
slide-server-server-21 (err):     at next (/home/gmike/projects/slide-server/src/server2/node_modules/express/lib/router/index.js:189:19)

Actually - I think I saw a post from someone mentioning that in cases of DDoS's, host isn't set. Not sure where I saw that from. It was when I was first looking for a lib to do this.

Nevermind. Just need to update.

:+1:

Have you updated NPM? When I NPM install I'm not getting the lastest code.


Instastoriesdownload.com Bridge

Hello,
here is a bridge for instastoriesdownload.com.
You can download stories from each Instagram public profile.

Looks dead: http://instastoriesdownload.com/


Change order of applying changes

What this PR does / why we need it:

Which issue(s) this PR fixes
Issue #667
Special notes for your reviewer:
Checklist:

[ ] squashed commits into logical changes
[ ] includes documentation
[ ] adds unit tests
[ ] adds or updates e2e tests
[ ] backport needed

It is not changing the order of some actions, you are moving the whole part under
	// check addon monitoring
	if config.Spec.Monitoring != nil {

section


Add linter

Use same rules as crc so that we can merge repos easily.

I updated the commit message and added golangci-lint in the Dockerfiles.


Extremely long buffer times for drive playback

On the connect app I can start playing back video immediately but on the explorer web app I have seen wait times of up to 2+ minutes before being able to start watching a drive. If I skip ahead/back in the video it restarts the waiting for the buffering again,

the log parsing was removed in the latest release, this should decrease the buffer time by a lot


Please Add option to show value with inventory close.

Can you add the ability to always show the value even with inventory closed?

Fits very nicely under minimap when setting correct x y to monitors resolution. Even a stickied location under minimap would be sick. Please have option to have open at all times, looks too good. Amazing plugin :)


redact vs reacted

just a minor spelling mistake in the console output
[16:29:08 INFO]: xyz[/<IP_ADDRESS>:0] logged in with entity id 12901 at ([REACTED] 0.0, 0.0, 0.0)

This was fixed recently but not released yet


wslCode.sh not found

Issue Type: Feature Request
I´ve reinstalled my wsl ubuntu and it do not found the "/mnt/c/Users/my_user/.vscode/extensions/ms-vscode-remote.remote-wsl-0.66.3/scripts/wslCode.sh". I tried uninstall and install the Remote - WSL to sove the problem, but it´s worong yet.
VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Connection to 'WSL: Ubuntu' could not be established  VS Code Server for WSL closed unexpectedly.
Check WSL terminal for more details.

Can you access that location from the Ubuntu side?


OTLP endpoint may become unresponsive

Describe the bug
I import older telemetry (traces/logs/metrics) via OTEL Collector to standalone Aspire Dashboard.
Aspire telemetry limits are computed before import and set to appropriate environment variables and Aspire Dashboard container is restarted.
Sometimes Aspire OTLP endpoint may become unresponsive and traces/logs UI as well.
Maybe there are too many telemetry records to be ingested by Aspire or too big record batches...
OTEL Collector`s log shows:
2024-07-25 11:24:44 2024-07-25T09:24:44.520Z    info    exporterhelper/retry_sender.go:118      Exporting failed. Will retry the request after interval.        {"kind": "exporter", "data_type": "traces", "name": "otlp/aspire", "error": "rpc error: code = DeadlineExceeded desc = context deadline exceeded", "interval": "35.536333315s"}
2024-07-25 11:25:24 2024-07-25T09:25:24.992Z    info    exporterhelper/retry_sender.go:118      Exporting failed. Will retry the request after interval.        {"kind": "exporter", "data_type": "traces", "name": "otlp/aspire", "error": "rpc error: code = DeadlineExceeded desc = context deadline exceeded", "interval": "35.153775693s"}
2024-07-25 11:26:04 2024-07-25T09:26:04.946Z    info    exporterhelper/retry_sender.go:118      Exporting failed. Will retry the request after interval.        {"kind": "exporter", "data_type": "traces", "name": "otlp/aspire", "error": "rpc error: code = DeadlineExceeded desc = context deadline exceeded", "interval": "25.6975388s"}
2024-07-25 11:26:35 2024-07-25T09:26:35.567Z    error   exporterhelper/queue_sender.go:101      Exporting failed. Dropping data.        {"kind": "exporter", "data_type": "traces", "name": "otlp/aspire", "error": "no more retries left: rpc error: code = DeadlineExceeded desc = context deadline exceeded", "dropped_items": 5522}

Expected Behavior
I would like to see all traces/logs in Aspire and not being dropped due to unresponsiveness.
Steps To Reproduce
Import telemetry data via OTEL Collector`s file import and export it to Aspire Dashboard OTLP endpoint in the same OTEL Collector pipeline.
Exceptions (if any)
No problem can be seen in Aspire Dashboard container log, just:
2024-07-25 12:03:33 info: Aspire.Dashboard.DashboardWebApplication[0]
2024-07-25 12:03:33       Aspire version: 8.0.0+7d0dde4108a2640ded4f9787fe28ce0f12d83633
2024-07-25 12:03:34 info: Aspire.Dashboard.DashboardWebApplication[0]
2024-07-25 12:03:34       Now listening on: http://<IP_ADDRESS>:18888
2024-07-25 12:03:34 info: Aspire.Dashboard.DashboardWebApplication[0]
2024-07-25 12:03:34       OTLP server running at: http://aspire-dashboard:4317

Container

image: aspire-dashboard:8.0.0
environment variables:

                        "Dashboard__Otlp__AuthMode=ApiKey",
			"Dashboard__Otlp__PrimaryApiKey=***",
			"Dashboard__Frontend__AuthMode=Unsecured",
			"Dashboard__TelemetryLimits__MaxTraceCount=40598",
			"Dashboard__TelemetryLimits__MaxLogCount=289958",
			"Dashboard__TelemetryLimits__MaxMetricsCount=49115",
			"Dashboard__ApplicationName=Telemetry",
			"DOTNET_DASHBOARD_OTLP_ENDPOINT_URL=http://aspire-dashboard:4317",
			"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
			"APP_UID=1654",
			"ASPNETCORE_HTTP_PORTS=",
			"DOTNET_RUNNING_IN_CONTAINER=true",
			"DOTNET_VERSION=8.0.7",
			"ASPNET_VERSION=8.0.7",
			"ASPNETCORE_URLS=http://<IP_ADDRESS>:18888"

@rolfik-mycronic Hi Marek, is it possible to share a repo that we can use to try and investigate this issue further?
CC: @samsp-msft

@rolfik-mycronic Hi Marek, is it possible to share a repo that we can use to try and investigate this issue further?

Unfortunately, I cannot share sensitive data for reproduction.
But I have not seen the problem in Aspire 8.1 yet, so You can close it for now.
If I will find it later, I will open another one.
Thank You


Changing the conditions of replacement in toDash

If string from customClass prefix ends with a number does not work
replacement regexp. For example "classname2" -> classname2wrapper
instead of classname2-wrapper

Codecov Report

Merging #178 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #178   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines         374    374
=====================================
  Hits          374    374

Impacted Files
Coverage Δ

src/jquery.selectric.js
100% <100%> (ø)
: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 0a9755a...5145813. Read the comment docs.

Hi!
Can you create a test for it?
Thanks!!

I'll close this PR and open a new one including the missing test case.


correct nargs errors for vim 8.2.3150+

https://github.com/vim/vim/pull/8544 introduced a change that displays an error when nargs is not defined and/or defined incorrectly. As a user, this will display an error message each time upon starting up. The error shows up as
Error detected while processing ~/.vim/plugged/vim-ripgrep/plugin/vim-ripgrep.vim:
line  149: E1208: -complete used without -nargs
Press ENTER or type command to continue

This fix to add -nargs=? to each of the commands.
Fixes #57

For the same or similar purpose as #56?

Worked for me. 👍🏼

I can confirm this fixed #57 on my end as well.

Can we get this merged? Or is this plugin repo abandoned?

I can too confirm that this patch works. Would like this merged if possible.

🙏

:pray:

Just ran into this also :pray:

While i wait for the maintainer, i forked and made the fix here: https://github.com/vNNi/vim-ripgrep.. but i really don't want to use them for a long time.

@vNNi For what it's worth, you could also just use 68ec5ba64d23212c5b3ae56599fb758254a2f435 from this PR itself.
That's what I've pointed my vim-plug config at in the meantime, at least. 😅

@AaronM04
I created a fork and implemented this PR along with some misc docs improvements. Any and all contributions are welcome.
https://github.com/mi544/vim-ripgrep

Why close it? It's an unfixed issue.

Was this resolved?

@cmorgannorris yes, see #56.


⚠ Bofrost.be has degraded performance

In 9315469, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1042 ms

Resolved: Bofrost.be performance has improved in 2485d9a.


shaka-packager v2.6.1 is really old?

This project uses shaka-packager v2.6.1 which seems to be outdated.
Current version is v3.2.0, see https://github.com/shaka-project/shaka-packager/releases/tag/v3.2.0
Is an upgrade useful and possible and will it fix some issues with incompatible files?

Hi @schuettecarsten,
At the time of development of this tool, v2.6.1 was the only version available so that why we chose it.
Yes, the new packager should have fixes to some issues.  There were two fixes that @duggaraju and @xieyubo contributed to the shaka packager codebase that weren't in the v.2.6.1 release, e.g.

fix: Fix handling of non-interleaved multi track FMP4 files (#1214)
fix: Fix failure on very short WebVTT files (#1216)

Unfortunately, we don't have the resources currently to test the new build of shaka packager.
You are welcome to try the new build, you can modify the AMSMigrate.csproj to grab the new build

https://github.com/shaka-project/shaka-packager/releases/download/v2.6.1/packager-win-x64.exe
https://github.com/shaka-project/shaka-packager/releases/download/v2.6.1/packager-linux-x64
https://github.com/shaka-project/shaka-packager/releases/download/v2.6.1/packager-osx-x64
we would be interested in learning your experiences with the new tool.

@pohhsu Thanks, I will update and let you know if it fixes some of my issues.

@schuettecarsten , thanks!
Just a heads up, I don't think the new shaka packager version will help you with the issues you hit in issue:
https://github.com/Azure/azure-media-migration/issues/251

as those two errors are raised in Azure Migration Tool, prior to calling shaka packager.  Sorry about that...

#253


[FR] Change cmpopts.SortSlices param from interface{} to func(a,b interface{}) bool

I just tried using cmpopts.SortSlices, and I know.. there are no generics in Go yet, but I think the current signature is not intuitive.
Current state of the world:
opt := cmpopts.SortSlices("yay") // can do whatever I want, it's an interface{}
cmp.Diff(someFoo, otherFoo, opt)

My desired state of the world:
// Can still mess things up, but it's more obvious.
opt := cmpopts.SortSlices(func (a, b interface{}){ return a.(Foo).Val < b.(Foo).Val })
cmp.Diff(someFoo, otherFoo, opt)

This proposal goes against Issue #67 but we could make it work like...
opt := cmpopts.SortSlices(cmpopts.DefaultSort) // renamed GenericLess to DefaultSort
cmp.Diff(someFoo, otherFoo, opt)

Hi, I'm not sure how I can get that to work though. When the signature of the input changes from func(a, b T) bool to func(a, b interface{}) bool, I no longer know what which slice types to apply the transformation to. Currently, the implementation looks at the less function to determine that it is supposed to sort []T as opposed to []R.

With generics seriously being considered for Go2, I think it be best to just leave the API as is and see how can we make it better. There are other cases where generics would have been very helpful.

The problem I have with  SortSlices is that it takes a "less" function typed as interface{}, I immediately think of sort.Slice() which has the param type func(i, j int) bool, but no, this one takes func (a, b T) bool which is currently impossible to represent in Go.
I had to read a couple times the documentation on how to get this to work, and sure it does, however I think saying the func takes a param type func(a, b interface{}) bool and say that a and b have to be type asserted by the user feels like a better API.
I agree this would be nicely solved by Go2, but it sounds like that's probably happening until 2 or 3 more years.

You didn't really address the problem I posed earlier about how func(a ,b interface{}) removes information needed to properly implement the function.

I already mentioned that in "My desired state of the world" and on the previous comment that the user would be responsible for doing type assertion in this world without generics.
e.g.
func (a, b interface{}) bool { a.(Foo).Val < b.(Foo).Val }

A desired state of the world isn't helpful if it is not implementable. As it stands, I don't think there is anything actionable here. The proposed API can't work and the other alternative is to wait for generics.

What do you mean by not implementable? Should I send a PR? Maybe I'm not explaining myself properly.
Right now the API accepts an interface{} that says nothing, I can pass a string and it will compile. I know that it will fail at runtime but it's not obvious. My proposal is that for now we change the signature of SortSlices(interface{}) to SortSlices(func(a,b interface{})bool) until generics exist.
Could you clarify why is having no types better than having some types and passing the responsibility of type-asserting to the user?

Right now the API accepts an interface{} that says nothing

interface{} says nothing to the compiler, but still says something at runtime. Reflection tells me what the type of the arguments are.
func(interface{}, interface{}) bool says a little more to the compiler, but says nothing at runtime when performing type introspection.

See this example: https://play.golang.org/p/hcpppV3sJEL

Ah... so IIUC SortSlices is not intended to be applied only to A and B in cmp.Diff(A, B), it's intended to sort any slice because if I pass a map or a struct, then each entry/property is navigated like a tree and when a slice is found if it matches the type of my less function, then the function is applied to it.
I think that's what you tried to point out on your first reply, but it wasn't that obvious. I thought SortSlices was used iff I was comparing 2 slices. Now that I get it I agree with you and waiting for generics is the best thing to do.
Thanks for the discussion 😃


Turned off autocomplete for TOTP codes

Small QOL change to turn off autocomplete when entering TOTP codes since they're one time use only.

Thanks for offering this @ImMattic, Seems like a sensible improvement.
I just double checked the auto-complete attribute on MDN, and I saw there's a specific one-time-code option that looks like it's for this kind of thing.
I wonder if that would also work to prevent standard autofill, while also making it known to  browser/extension auth systems for potential autofill?
Also, thanks for the sponsorship!

No problem! I'm always a big proponent of supporting open source whenever possible, especially if I use it.
I didn't know about that OTP attribute. I did just try it on my instance though and unfortunately it doesn't prevent autofill (at least on Firefox). I definitely see how having the OTP attribute would help extensions like Bitwarden to autofill the OTP though. Is it maybe possible to stack attributes together?

Thanks @ImMattic,
Yeah, looking further it's not a supported attribute in Firefox.
Setting off at the form level, then one-time-code at the input level seems to still prevent autofill (tested in Firefox and chrome) while still having one-time-code there for potential other helpful usage.
Additional tweaks made in bc24a1360f8a1f7e3be3656de9392a0802328d90 and d5a689366c7ceca8f7949caf0d919bb13fb56499, which also copies these changes for backup code MFA, and adds some tests to cover.
Now all merged to be part of the next patch release.


[VT-25] vit; moar default keybindings: Home, End, Insert, Delete

David Patrick on 2013-09-03T04:35:27Z says:
The keys have obvious functions for vit, and if possible, they should be active by default.
Home and End, top and bottom of the list
Delete selected task(s)
Insert new task (add)

Migrated metadata:
Created: 2013-09-03T04:35:27Z
Modified: 2014-02-09T01:16:50Z

David Patrick on 2013-10-13T10:09:46Z says:
Works!


Rendered text for planned maintenance need more spacing for titles

When a planned maintenance is added, the Markdown text is rendered on the main page.
The titles should get a little more spacing (e.g. a little tuning to the CSS) to make the result easier to read.
Here's a simple example of text to render to see the spacing issue:
## What
Our system administrators are going on a boat ride .... in the data center!

## How
Pray for the best, there may be crocodiles or sharks in there.

## Why

Servers usually don't go along too well with crocodiles.

## How

* take a boat
* row all the way up to the crocs
* use eloquent speach to convince crocs to leave the DC
* Make sharks tag along the crocs
* Pump water out
* Get out with the boat

The Markdown is rendered into HTML for me, is this not the case for you?

@jbrooksuk yes it is. the issue is with presentation (css). titles would look better if they were spaced more from the text.

We welcome pull requests (to the L5 branch please).


Implemented a minimal init command using the templates

This is very basic, just a bridge between ./cabal and the templates on Github.

hmmm, this wont work as open source i think....

Could this command be added to the usage text as well?

(our templates are private atm)

@domdere we are already referencing some private things in this file (mafia). I think that "open-source" doesn't always mean "fully executable". People can also fork and modify, or we can open source our templates in the future.
@olorin init was already in the usage section, but not wired to anything! In the fixup I add a bit more doc on what init does.

"open-source" doesn't always mean "fully executable"

thats disappointing :(.
would it be so terrible to have the init comment take in `ambiata/haskell-foo.template" instead of "foo"?

Not actually reference mafia yet, just using it a the cache for alex and happy executables. Name is just for forwards compatibility (future open source project etc)

@domdere I changed the args so that init now takes the repository path like ambiata/haskell-library.template
@markhibberd I fixed the copying of dot files

I changed the args so that init now takes the repository path like ambiata/haskell-library.template

Thanks, sorry for whinging
:palm_tree: :shell: :sunglasses: :ocean:


Android: App requires prominent disclosure. What info does this package collect?

Describe the bug
This package and its documentation does not make it clear what info it collects and returns to Stripe.
To Reproduce
Steps to reproduce the behavior:

Integrate this package with your RN project.
Generate an app bundle and submit it to Google Play
Get a notice from Google.

Expected behavior
A clear and transparent full disclosure in the docs about what info is collected, why Stripe collects it, and an example of how to address it so that our apps conform to the store requirements.
Screenshots

Smartphone (please complete the following information):
Android, and probably iOS as well.
Additional context
Related to this, what disclosure should we be adding to our App Store Privacy card for the iOS version of the app?
Guidance from Stripe on this is needed.
Thanks!

@multiplegeorges There are previous versions of the Stripe library that were causing this issue.

If you're integrating an old version of the SDK, we've provided hotfixes so you can easily upgrade:
- 9.x → 9.4.0
- 10.x → 10.5.0
- 11.x → 11.3.0
- 12.x → 12.9.0
- 13.x → 13.3.0
If you're using tipsi-stripe, you must upgrade to v9.1.0+ (it depends on 16.10.0 of the android-sdk, anything before that depends on a violating version of the SDK)
You don't have older versions of your app bundled in your active release (to support older Android versions, for example)
You don't have older versions of your app available in testing tracks on Google Play Console.

I tried re-submit my app with the latest package version 0.2.2 but getting the same rejection from Google Play. Any ideas what else could be missing?

Hey @ilyagru can you share the content of the 'dependencies' section of you app/build.gradle file?
This is what I have for the stripe sdk:
dependencies {

    implementation 'com.stripe:stripe-android:17.1.1'

}

@YoQuieroDistraerlo I'm using @stripe/stripe-react-native package with the latest version which uses 'com.stripe:stripe-android:17.1.1', so yes.

Hey @michelleb-stripe @trag-stripe can you acknowledge what Google Play reviewers are saying or, provide us with an explanation or statement we can present to them?
Thank you!

Yeah, my updated app on 0.2.2 was also rejected.
My app/build.gradle doesn't specify a stripe-android dependency, but my<EMAIL_ADDRESS>has:
dependencies {
  ...
  implementation 'com.stripe:stripe-android:17.1.0'
  ...
}

@YoQuieroDistraerlo I apologize that you are still having issues, and we would like to work with you to remove any problems associated with the Android SDK.

Is your message from Google identical to the one reported by @multiplegeorges?

I want to make sure that an old stripe-android version isn't being included in another way.  Can you open the Android project in Android Studio, open the File -> Project Structure, then click on Dependencies in the left pane.   If you can look through  in your project and verify that no other versions of stripe-android are included?

In regards to the Google Play Console:
a. Does the updated version of your app have an updated version number and version code?
a. Were you able to upload a version of your app with the updated react-native library to all the tracks: production, open, closed, and internal?
c. Is your app the only active version in each of the tracks: production, open, closed, and internal?
d. Were you able to upload a version of your app with the updated library to all the tracks: production, open, closed, and internal?

I’m about to send my app for review with this new library but haven’t yet. I’m concerned about @ilyagru reported issue.
Let’s wait for additional comments from @ilyagru.

@michelleb-stripe @YoQuieroDistraerlo Yes, I'm a bit confused too, to be honest. At our company, we've got the Staging version of the app which we are testing through the Internal track on Google Play. We are using only one track currently for the app. All tracks are inactive now. Everything was fine but unexpectedly it got removed from Google Play with a similar message.
At the moment of removal, the version of "@stripe/stripe-react-native" was "^0.1.4" (which is also fine?), then I updated it to the latest  "^0.2.2" and re-submitted the app but the update got rejected as well.
I just went through the dependencies, it has only `stripe-android:17.1.0.
I see some other people started to experience this issue too https://stackoverflow.com/questions/69072021/stripe-android-sdk-doesn-t-comply-with-the-user-data-and-mobile-unwanted-softwar
Could it be a problem with the privacy policy not being precise then? But if those bits causing the issue are removed from the Stripe package, what should be put in there in this case?

@ilyagru Let me reach out to you directly on email, and we will report back here with more information.

@ilyagru One more thing for you to check in your Google Play Console.  In the Google Play Console you can click on a release and see all the App Bundles associated with it.  Can you compare the App Bundle ID shown in the Google Play Console with the App Bundle ID in the email: 15735757 and make sure they match?

@michelleb-stripe yes, of course they match. Please write to me<EMAIL_ADDRESS>

@michelleb-stripe it looks like Google requires us to update the privacy policy to disclose that we are using Stripe which might be collecting Installed Application and Phone Number information. Could you please specify or give a link to Stripe's privacy policy where it is described? But quite confusing that you are saying you don't collect that information but Google is saying you do...

The issue was with another track on Google Play where there was an older build with the outdated SDK. Although the channel was inactive, Google takes all channels into account while reviewing - that was quite confusing bit. I managed to solve it by updating that track as well.  Thanks for help!

Google Play where there
@ilyagru which track was concerned ? I have the same issue with the play store. I have created a release only in production track, and my updates are rejected for the same reasons ...  I don't know what i'm missing.

@ilyagru One more thing for you to check in your Google Play Console. In the Google Play Console you can click on a release and see all the App Bundles associated with it. Can you compare the App Bundle ID shown in the Google Play Console with the App Bundle ID in the email: 15735757 and make sure they match?

Ultimately this comment is what it solved it for me.
Once I looked at the Email again and compared version codes, it happened to be a internal testing app we release over a year ago that was on a paused track. Really misleading and very aggressive to get removed for an internal testing app apk that is much older than the current release.
Thanks for pointing that out!

Same for me - the problem was with a old track/release! Thanks for that hint!

Same problem here, @michelleb-stripe I'm using tipsi-stripe which is using v16.10.0
Do you know if we have to patch tipsi stripe with a new version?

Closing this issue since the problem was caused by older releases on different tracks.

One more thing for you to check in your Google Play Console. In the Google Play Console you can click on a release and see all the App Bundles associated with it. Can you compare the App Bundle ID shown in the Google Play Console with the App Bundle ID in the email: 15735757 and make sure they match?

The issue was with another track on Google Play where there was an older build with the outdated SDK. Although the channel was inactive, Google takes all channels into account while reviewing - that was quite confusing bit. I managed to solve it by updating that track as well. Thanks for help!

Once I looked at the Email again and compared version codes, it happened to be a internal testing app we release over a year ago that was on a paused track. Really misleading and very aggressive to get removed for an internal testing app apk that is much older than the current release.


Bug 2086759: Bump retries for UEFI boot configuration

Testing proved to need more retries on the HW where we could
reproduce this problem

/bugzilla refresh
I'll submit upstream if this proves to fix the problem.

/bugzilla refresh

/test e2e-metal-ipi

/test e2e-metal-ipi

/cherry-pick release-4.10


Rectify checksum computed by the cluster resolver

Currently, trusted resources computes the checksum of the task/pipeline object (after some preprocessing that removes unwanted annotations etc.).
However, the cluster resolver computes the checksum of the Spec instead of the pre-processed object, which makes it incomplete
annotations and labels could be used by controllers to control things like network policy and its relatively common for annotations to act as feature flags for per-resource behaviour. See discussions in this thread.
We should make the checksum computation of the task/pipeline in the cluster resolver to be the same as what trusted resources  does.
cc @wlynch @lcarva @chuangw6 @Yongxuanzhang
/kind bug

/assign chitrang

/kind bug

/assign

Implemented in PR https://github.com/tektoncd/pipeline/pull/6964.
Closing


⚠ TorrentLeech has degraded performance

In 8955837, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 2380 ms

Resolved: TorrentLeech performance has improved in b08cc3a after 12 minutes.


Add support for callouts in emoji keyboard

With the new Emoji skin tone variant support, the EmojiKeyboard should let you long press an emoji to show the available skin tones as secondary callout actions. We also want to show the emoji in a callout when it's tapped.
This is however currently not possible, since the gestures that the KeyboardGestures applies blocks the emoji keyboard scroll view from scrolling. We must thus fix so that the KeyboardGestures doesn't block the scroll view. After that we can just apply keyboard gestures to each emoji button to get this to work automatically. Everything else is prepared.
I've been struggling with this for a while, so any information you can provide me with would be of great value.

This is fixed in the upcoming 6.6.
The emoji keyboard will now apply a brand new gesture engine, that lets it handle a bunch of new gestures. This unlocks the same actions as in the regular keyboard, and lets us show input and secondary action callouts.
You will now get input callouts on iPhone, as well as action callouts with skin tone variants if you are using KeyboardKit Pro.


Linear cell mode

A few changes to add to the clearafter...does the following things:
When a cell is run:

The N+1th cell gets a "stale" class added to it

The > N+1th cell gets a "stale" class added and becomes uneditable
When a cell that is stale is run:

All cells above this one which are also stale are run (in order) first

I also refactored the logic a little bit...
Stuff that is broken or needs doing:

I can't figure out how to get the CSS to load
The "all previous stale cells run first" bit is executed after the current cell is run, but it should be before
There should be a button somewhere to switch this on or off

An example of what this looks like:

(NOTE: this is just my general thinking+suggestions here, lemme know what you think)

OK I think the latest version works. See the attached GIF of what it looks like (I chose an example where we redefine "data" a few times and visualize it each time, then show how the confusion could be avoided w/ linear mode on.
(disregard the exact position of the cursor, it's my GIF recording thing being wonky)

(note that we may wanna change some UX things...I'm still not sold on making stale cells uneditable, but I do like making them greyed out etc)

@yuvipanda would you rather I close this PR? It sounds like there are other tools in this space as well (e.g., https://github.com/stitchfix/nodebook) so I'm not sure if you intend on continuing on this project. LMK!

@choldgraf I made you a collaborator :) do what you think is right!

I think I'm gonna close this one, since neither of us seem to have the time to work on this repo, LMK if you disagree and happy to make a push if needed!


Avoid "process is not defined" error

UPDATE 2023-03-02: 6.0.3-alpha.0 avoids this problem by removing all the dev-mode logic from the distributed files. It includes ".development" variants of the default exports in case someone wants to use them:
import { QueryBuilder } from 'react-querybuilder/dist/index.development.mjs';
// OR
const { QueryBuilder } = require('react-querybuilder/dist/index.development.cjs');

I'll publish v6.0.3 properly soon.

Certain environments fail when importing RQB v6.0.2 because of the process?.env?.NODE_ENV checks to enable/disable development-mode warnings.
Figure out how to avoid the problem altogether, potentially by building separate dev and prod bundles.

Currently encountering this issue as well. Can someone from the team help us? Will appreciate it so much.

@warjohn123 see my update about v6.0.3 at the top of this issue.

@warjohn123 see my update about v6.0.3 at the top of this issue.


The issue template screen in this repo is misleading

This is what it looks like:

I was very surprised to then be told by GH support that I should file an issue here, instead of contacting support. Perhaps this screen should offer more options explicitly, or explain in what specific situations GH support should be contacted.

Thanks for the report; it looks like we do have some communications at cross-purposes happening at our end.
I'll dig into how much support GitHub Support is supposed to deliver for the CodeQL action, and then try to make the banner and reality align better, one way or the other.


Fix panic if CONNECT transport is not a net.TCPConn

handleHttps would panic if Dial returned something other than a
net.TCPConn which was then used for a non MITM CONNECT request.
For example the golang.org/x/crypto/ssh package returns a net.Conn
when opening a tunnel through an ssh connection.  This is backed
by a wrapped ssh.Channel which also implements CloseWrite() so using
a type assertion achieves the same result in a portable fashion.

fwiw here's my program that uses goproxy to tunnel http requests over an SSH connection without requiring openssh, putty, etc https://github.com/gwatts/sshproxy
Other than the small patch, goproxy made it very easy to write the above, so thanks for that :-)

Hi,
My problem with it is, that I'm not sure if the logic would work correctly if you completely close the connection.
Wouldn't a better idea would be to accept a goproxy.CloseWriter interface, and then in your code you'll wrap net.Conn with a CloseWriter implementation?
interface CloseReadWriter {
   CloseWrite() error
   CloseRead() error
}

type closeWrite struct {
    Closer io.Closer
}

func (c *closeReadWriter) CloseWrite() { c.Closer.Close() }
func (c *closeReadWriter) CloseRead() { c.Closer.Close() }

sshConn := CloseReadWriter{ssh.Dial(...)}

What do you think?

I agree that Close is probably not going to do the right thing within that call
OTOH even the http.Hijacker interface only returns a net.Conn; there's no guarantee that has a CloseWrite either; perhaps it should just test for CloseWrite and use that if available, else assume that writes are unbuffered and synchronous (net/http appears to follow this practice)
Additionally the code currently spawns those two goroutines to do the copy, but doesn't block on them, so  handleHttps is going to exit while the copy is still in progress, which doesn't seem ideal.
Finally it should still ensure Close is called on both connections before the handler exits, which doesn't appear to be the case currently.
I'm happy to update the PR with a rethought implementation if you agree with the above

How can you implement tunneling robustly without CloseWrite?
Regarding to the fact that the copy goroutine outlive the request handler. This is by design.
What benefit do you see for keeping the handler goroutine alive? The tunneling could be literally kept for hours.

@gwatts any update?

@gwatts can you please see if de25c6ed252fdc01e23dae49d6a86742bd790b12 fixes it for you?


Can i fire menu item from code ?

I just want to ask if i can fired/triggered menu item from code? if it's possible please give me the code block to do that.

Read the readme ;)


Via DRC Violation Issue

Expected Behavior
The V1.1 violation will pop up when a via size is less than 0.26*0.26
Actual Behavior
I accidentally used 0.22*0.22 vias all over my layout and this V1.1 didn't show up when running the drc. Those four violations are the density violations.

Steps to Reproduce the Problem

Create a small block consisting of M1, M2, and via1 in my layout. Then copy to a new layout called testvia.txt and run the DRC. No V1.1 violation shows.

To figure out what happens. I create a new, identical layout called testvia2.txt manually(this time not copy from my previous layout). V1.1 violation shows

Now I compare testvia.txt  with testvia2.txt, The only difference are time stamp and the name of layout.

These steps shows a weird issue of this via violation.

@msaligane @proppy @andylithia
Specifications

Version: v0.0-1450-g140b622
Platform: klayout

@StanleyAlwaysLoveYou Could you please use: https://github.com/efabless/globalfoundries-pdk-libs-gf180mcu_fd_pv/tree/main/klayout/drc  instead of the DRC here?

It's no longer the case @proppy. What in the PR repo is not up to date as PV. We have cleaned the DRC significantly due to the review we are doing with you. We improved the performance and fixed a handful of DRC bugs. And @RTimothyEdwards has just migrated the source of DRC from PR to PV:
https://github.com/RTimothyEdwards/open_pdks/commit/7ddd413a3495a9055f03ae60b4320b14d0d6dc55
I'm going to remove DRC from this PR repo as we have originally planned.

@RTimothyEdwards has just migrated the source of DRC for open_pdks from PR to PV:

Awesome!

I'm going to remove DRC from this PR repo as we have originally planned.

Perfect, maybe also add a line to the README to inform people of the new location.
Do we still plan to merge most of the content in https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pv? /cc @mithro

Yes, that has been always the plan to move to Google. But I think we are stuck with the issue of meeting the complex linting requirements for ruby at that point.

But I think we are stuck with the issue of meeting the complex linting requirements for ruby at that point.

Let's discuss this in https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pv/issues/40 I didn't realize it was a blocker.

Thanks @proppy

@StanleyAlwaysLoveYou I'll keep this ticket open until, I hear back from you about the results using pv version.

I used the drc in pv version and still shows the different result:
testvia.gds doesn't have the V1.1 rule violation while testvia2.gds has.

I guess there is some difference in these two .gds while they look identical in klayout, even the .txt files translated from the corresponding .gds file look the same. However I can't run the drc on the .txt file so it is hard to figure out what happens between these two "identical" layouts.

@StanleyAlwaysLoveYou Could you please upload the files this way we could test?

I am not sure how to directly upload the files. I'll put them in a zip folder:
testvia.zip

Found another way, in case the file will change during compression. The below is the link of the two gds files
link
Thanks a lot!

@FaragElsayed2 Could you please take a look at this?

@atorkmabrains
The difference between them is database unit

This cause an issue in extended command as we have used 0.001 db value not um.

I have opened an issue for  to make DRC rules independent of DB unit.
https://github.com/efabless/globalfoundries-pdk-libs-gf180mcu_fd_pv/issues/86

Thanks @FaragElsayed2

@StanleyAlwaysLoveYou Will be fixed soon.

Thanks @FaragElsayed2 @atorkmabrains
So the problem is I used the different database unit in these two layouts? May I ask what exactly the database unit is?

@StanleyAlwaysLoveYou Precision is a number that is stored in the layout file GDS/OASIS to tell it what each integer number represent in the layout. For example, if the precision is 1000, then each database unit is 0.001 um. If precision is 10000, then each database unit is 0.0001um. So on so forth.

Oh I see. I saved testvia.gds as a new file with 0.001um database unit, then the V1.1 violation did work.

@StanleyAlwaysLoveYou and @proppy Fixed in https://github.com/efabless/globalfoundries-pdk-libs-gf180mcu_fd_pv/pull/88


chore: update build tasks

PR Checklist

[ ] Unit Tests have been added for new changes
[ ] API tests have been updated if applicable
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. open-amt-cloud-toolkit/repo#365 )

:tada: This PR is included in version 2.3.5 :tada:
The release is available on:

GitHub release
v2.3.5

Your semantic-release bot :package::rocket:


YachtsManager error

Assets\YachtsManager.cs(66,51): error CS1061: 'IYachtControls' does not contain a definition for 'getApparentWindVector' and no accessible extension method 'getApparentWindVector' accepting a first argument of type 'IYachtControls' could be found (are you missing a using directive or an assembly reference?)

I'm seeing this issue as well.

I'm seeing this issue as well.

you can just comment out line 66