Hoisted scripts missing in both dev/prod for content collection entry with MDX

I added mdx integration to astro for richer blog content, and created an astro component to use in the mdx documents. I think I followed all directions to do so clearly, but client side script tags don't seem to be working in mdx documents.
I have the component @components/ImagePreview.astro, and if I use it in, say pages/index.astro, it works fine. But if I import it to content/blog/my-blog-post.mdx and use it there, the HTML is rendered but the script does not work. I bumped up to "astro": "^2.10.4", and  "@astrojs/mdx": "^0.19.7", because I saw the Astro issue regarding this was closed.
I left a comment in that issue thread, saying that this still seems to be an issue for me, but I wasn't sure maybe AstroPaper had some conflicting configurations that I wasn't able to figure out. Link to my comment on the issue
I can get it to work with the is:inline directive, but according to the docs, it seems like it should properly work...
I've enabled the experimental assets, if that makes any difference, which I doubt because even if I change it to img instead of Image from astro:assets, the behaviour is identical.
ImagePreview.astro component for reference:
---
import { Image } from "astro:assets";

export interface Props {
  src: string;
  alt: string;
  width: number;
  height: number;
}

const props = Astro.props;
---

  <Image {...props} />
  {props.alt ?
{props.alt}
 : ""}

    <Image
      {...props}
      class="animate-fade-in h-[100%] w-[100%] object-contain"
    />
    {
      props.alt ? (

{props.alt}

      ) : (
        ""
      )
    }

Submitted a new issue on astro as per the advice of the author of the original issue

Hello @noidwasavailable
Sorry for my late response.
I assume it is the problem with Astro itself and I guess they are still working on this.
Is this still occurring in Astro v3.1?

@satnaing Yes, I think it's an Astro problem. I upgraded to Astro v3 manually, but on 3.0.13, the issue persists. I'll try it again on the latest versions and let you know how it goes.

@satnaing Hi, I finally had the time to get around testing stuff. On upgrading AstroPaper, and manually updating the dependencies for astro to ^3.2.2 (latest), I can confirm, this issue no longer persists, even though there is no mention of hoisted scripts being fixed anywhere on astro 3.0 release.

Okay, thanks for confirming this.
I'll close this issue for now. Feel free to reopen or create new issues if you encounter any further problems.


Usage of a corporate idententy

As suggested in juiceshop copy 2.pdf page 3 we should use other colors for information like solving challenges.
Thanks to @lisa-devseccon.

You mean fixed colors for challenge notifications and solved/unsolved badged that stay static even when a different theme is used via the config mechanism?

Yes, but the colors should be defined in the config for easy overwriting.

Different Angular Material themes will be provided for customization. Static colors (i.e. solved/unsolved markers and notifications) have been changed to the suggested colors from https://github.com/bkimminich/juice-shop/files/2080970/juiceshop.copy.2.pdf.


Doesn't work with new version of jukebox

just updated jukebox and got this error

that's weird.. I just updated jukebox to v2.7.0 as well and redownloaded v0.0.2 from the index and I don't get this error..

ill remove all my mods other than jukebox and auto nong and try

Ah. auto nong works but when downloading any song it crashes when trying to set it.

just removed all other mods and the error still occurs

can you try this? https://file.io/llPj8ZVgiNea
@OM3GA6400
I updated to the new jukebox version

bet


[META] Making all copies of shards spread evenly across all Awareness Attribute

Is your feature request related to a problem? Please describe.
In cloud HA deployments , customer usually deploy over  multiple zones.  zone is usually the awareness.attributes in there . However, there is no enforcement of all copies spread evenly across all zones . This can cause uneven distribution of shards and also create shard hotspots. Failure in a single zone might also cause data loss and unavailability for that shard if the copies aren't evenly spread out.
Describe the solution you'd like
There are two solutions to this approach :

A boolean cluster level setting balanced_across_awareness_attribute which is false by default . When true, we would validate that total copies is always a multiple of awareness attribute value count . If not, we will throw a validation exception. If there are multiple awareness attributes, the balance needs to ensure that every variant of awareness_attribute is equally balance. For ex, if there are 2 Awareness Attributes, zones and  rack ids, each having 2 possible values , total copies needs to be multiple of 4.
A boolean cluster level setting  auto_balance_across_awareness_attribute. If this is true, we would increase the total copies to be a multiple of AZ count . For instance, there are 3 AZs and index creation request comes with 7 replica. OpenSearch will create 8 replica, to ensure that there are total 9 copies .

Both the solutions will take in effect only  upon cluster.routing.allocation.awareness.attributes and cluster.routing.allocation.awareness.force.zone.values   being set  . If not, the setting will not take in effect .
Trade offs
First approach : The plugins like ISM, CCR needs to do proactive validation while creation and updation of policy. If not, the actions/replication will fail silently at later point of time.  As and when new policies or index creation paths are created , we will need to keep adding the validation there for a good experience.
Second approach : Since the replica count is adjusted by OpenSearch, the plugin and new index creation/modification paths don't need any handling and is very low maintenance. However, the fact that we are deviating from API supplied parameter may not look like a good user experience.
User  Experience

User sets cluster.routing.allocation.awareness.attributes and cluster.routing.allocation.awareness.force.zone.values
If user enables balanced_across_awareness_attribute , the total copy needs to be a multiple of all possible values of awareness attribute. If not , we will do one of the following

Reject the create/update index
Auto expand the replica count as per need.

Why it should be built
This is to ensure that OpenSearch cluster remains well balanced as well as resilient to failures of zone/Rack etc.
What will it take to execute?
Changes in OpenSearch as well Plugins to honor the new flag .

Requesting community and also pinging @shwetathareja @dblock  to provide feedback on above .

Thanks @gbbafna for opening this issue
Some initial thoughts

I see value in doing both, starting with a validation exception post enabling the settings enforce_awareness_attribute_balance (suggested name)
The auto_balance seems very similar to auto_expand_replica : 0-all, and looks like a good reasonable extension to 1.
The behaviour with both 1 and 2 at the time of index creation with non-compliant replica count could be a validation exception so as to not acknowledge the response with conflicting settings. Is the idea not to throw a validation exception in case of 2.
We should ensure all API responses(cat indices/cat shards etc) are consistent with the settings, reflecting the latest index metadata

Thanks @gbbafna , I clearly see the benefits but there are some concerns as well. Primarily, the basic premise I have seen in many deployments is that clusters are quite dynamic by nature, with that:

The auto_balance_xxx (2nd approach) should probably disable the manual replica management. In this regards I sound @Bukhtawar 's concern related to auto_expand_replica. It seems to me the number of replicas should be dictated by cluster topology + awareness attributes (with caveats to preserve HA).
Cluster may not only grow (new nodes / zones / racks added) but also shrink on purpose (decommissioning nodes / racks / zones), it plays well with 1st point (disable the manual replica management). The behavior should be aligned with delayed allocation rules [1] to trigger the process.

[1] https://www.elastic.co/guide/en/elasticsearch/reference/7.10/delayed-allocation.html

Thanks @Bukhtawar , @reta for your feedbacks.

Thanks @gbbafna for opening this issue Some initial thoughts
1. I see value in doing both, starting with a validation exception post enabling the settings `enforce_awareness_attribute_balance` (suggested name)

Makes sense. We can break this into two parts and start with enforce_awareness_attribute_balance first.

2. The auto_balance seems very similar to `auto_expand_replica` : 0-all, and looks like a good reasonable extension to 1.

Agreed. For search use cases, replica count can be a multiple of zone attribute values , so as to scale for reads. We can have auto_balance_xxx as well as count_per_awareness setting  on index level for same.

3. The behaviour with both 1 and 2 at the time of index creation with non-compliant replica count could be a validation exception so as to not acknowledge the response with conflicting settings. Is the idea not to throw a validation exception in case of 2.

In case of 2, replica count will not even be an accepted parameter at the time of index creation.

4. We should ensure all API responses(cat indices/cat shards etc) are consistent with the settings, reflecting the latest index metadata

Agreed .

Thanks @gbbafna , I clearly see the benefits but there are some concerns as well. Primarily, the basic premise I have seen in many deployments is that clusters are quite dynamic by nature, with that:
1. The `auto_balance_xxx` (2nd approach) should probably disable the manual replica management. In this regards I sound @Bukhtawar 's concern related to `auto_expand_replica`. It seems to me the number of replicas should be dictated by cluster topology + awareness attributes (with caveats to preserve HA).

Yes.

2. Cluster may not only grow (new nodes / zones / racks added) but also shrink on purpose (decommissioning nodes / racks / zones), it plays well with 1st point (disable the manual replica management). The behavior should be aligned with delayed allocation rules [1] to trigger the process.

[1] https://www.elastic.co/guide/en/elasticsearch/reference/7.10/delayed-allocation.html

Taking full control of replica count management makes a lot of sense for ease of management . We can have auto_balance_xxx as well as count_per_awareness on index level to completely disable manual replica management.
Summarizing above points, I propose breaking the feature in two parts  :

Start with enforce_awareness_attribute_balance setting  :  I can get started on LLD  for this.
auto_balance :   This will expand the replica as per current awareness attributes , more on the lines of auto_expand_replica.  This will also have count_per_awareness on index level setting . This can be a follow up item .

Thanks, @gbbafna just curious how enforce_awareness_attribute_balance would impact the changes in awareness attributes? Fe the cluster + indices were created in one zone initially (with rack awareness only), but later on scaled across multiple zones (with another attribute of zone awareness added). What will happen with existing indices in this case?

The validation setting enforce_awareness_attribute_balance  is enforced only at the time of index creation and updation . So for the above mentioned case, the existing indices would remain as it is . Only the update calls to those will have the awareness checks . It is not the ideal user experience, but better than the existing behavior. We are putting that responsibility to the user to modify replica count of existing indices during their scaling up/down. This behavior is kept status quo in this approach.
The second part of the feature auto_balance would take care of this and is completely hands free. But this is a much bigger change compared to the , which we can take up as a follow up item .
Thoughts ?

A few questions:

the awareness.attributes
What else is this used for?

A boolean cluster level setting balanced_across_awareness_attribute which is false by default . When true, we would validate that total copies is always a multiple of awareness attribute value count . If not, we will throw a validation exception...

Is this on indexing, rebalancing, some other operation or multiple?

A boolean cluster level setting auto_balance_across_awareness_attribute. If this is true, we would increase the total copies to be a multiple of AZ count . For instance, there are 3 AZs and index creation request comes with 7 replica. OpenSearch will create 8 replica, to ensure that there are total 9 copies .

How is the AZ count specified?

User Experience

User sets cluster.routing.allocation.awareness.attributes and cluster.routing.allocation.awareness.force.zone.values
If user enables balanced_across_awareness_attribute , the total copy needs to be a multiple of all possible values of awareness attribute. If not , we will do one of the following
Reject the create/update index
Auto expand the replica count as per need.

Are these live reloaded settings or require cluster restart? Any new REST APIs?

A few questions:

the awareness.attributes

What else is this used for?

This is used to distribute the shards across the AZs/racks. If there are 2 copies of a shard and 2 zones, 1 zone will have 1 copy of shard.

A boolean cluster level setting balanced_across_awareness_attribute which is false by default . When true, we would validate that total copies is always a multiple of awareness attribute value count . If not, we will throw a validation exception...

Is this on indexing, rebalancing, some other operation or multiple?

This is on operations which create/modify index .

A boolean cluster level setting auto_balance_across_awareness_attribute. If this is true, we would increase the total copies to be a multiple of AZ count . For instance, there are 3 AZs and index creation request comes with 7 replica. OpenSearch will create 8 replica, to ensure that there are total 9 copies .

How is the AZ count specified?

Assuming cluster.routing.allocation.awareness.attributes specifies zone as the attribute,  AZ count is specified via cluster.routing.allocation.awareness.force.zone.values .
Below settings illustrate same for two awareness attributes.
cluster.routing.allocation.awareness.attributes : ["zone", "rack"]
cluster.routing.allocation.awareness.force.zone.values: zone-1, zone-2
cluster.routing.allocation.awareness.force.rack.values: rack-1, rack-2

User Experience

User sets cluster.routing.allocation.awareness.attributes and cluster.routing.allocation.awareness.force.zone.values
If user enables balanced_across_awareness_attribute , the total copy needs to be a multiple of all possible values of awareness attribute. If not , we will do one of the following
Reject the create/update index
Auto expand the replica count as per need.

Are these live reloaded settings or require cluster restart? Any new REST APIs?

These are dynamic cluster level settings . Existing APIs to update settings will be reused to modify these

@gbbafna is this tracking 2.2? Can we add two labels to this? 1/ "roadmap" to highlight this improvement on the project roadmap 2/ the version of OpenSearch this is targeting? Thanks!

Yes, we are tracking 2.2 for this.  @Bukhtawar , can you please help with same as I don't have permissions ?

Thanks! I see it now. Can we also open an issue in the docs repo to track any documentation updates that might need to happen for this?

@gbbafna can this issue be closed? I see https://github.com/opensearch-project/OpenSearch/issues/3461 which tracks the first solution here, with https://github.com/opensearch-project/OpenSearch/pull/3462 as the PR to main and https://github.com/opensearch-project/OpenSearch/pull/4086 as the backport to 2.x


Bugfix/45 java gateway error

@zhukovgreen, it is strange that lint fails on files that @ValeriiKhalimendik hasn't changed.

@zhukovgreen, it is strange that lint fails on files that @ValeriiKhalimendik hasn't changed.

Maybe @ValeriiKhalimendik just didn't install the pre-commit hooks, in this case, git commit won't run them. To install git hooks you need to:
pre-commit install --install-hooks

Please, insert the license to
pramen-py/tests/test_utils/__init__.py

Interestingly, I can add a comment to an empty file 😆


Module 'dataset' is missing

https://github.com/gotutiyan/ged_baselines/blob/b093193916f2909f21577ea8e6f4bfbd6333f904/token_ged/train.py#L16
The module is missing.
Trying to install with pip install dataset installs library for databases.

Thank you for your question!
I forgot to push dataset.py, so I've uploded it.
It seems to work now.


Feature Support hash

This includes PR #91 from @zentuit and adds hash support in pushRoute, replaceRoute, prefetchRoute

Coverage decreased (-1.7%) to 93.145% when pulling 9e5ab012db5997769df64c8e2fdd575142e6e644 on revolunet:support-hash into 08e8bbeaa76c5ec194abea388a193bedac7f35fc on fridays:master.

Guys... Please merge this PR. We need this feature.

Hello,
Any news here?


FTL Two queries for the same block (2965714) got a diff # of TXs

Using this config, i consistently get the same error.
FTL Two queries for the same block (2965714) got a diff # of TXs
    [log]
    level = "info"
    pretty = true

    [base]
    addressRegex = "osmo(valoper)?1[a-z0-9]{38}"
    addressPrefix = "osmo"
    api = "http://osmosis-archive-1.nodes:1317"
    # startblock = 2612600
    startblock = 2965612
    endblock = 7444264
    RewardsStartBlock = 3104870
    throttling = 0.0005
    rpcworkers = 1
    blockTimer = 1000
    waitForChain = false
    preventReattempts = true
    waitForChainDelay = 1
    indexingEnabled = true
    exitWhenCaughtUp = false
    osmosisRewardsOnly = false
    RewardIndexingEnabled = true
    Dry = false

    [lens]
    # rpc = "http://osmosis-archive-1.nodes:26657"
    rpc = "http://osmosis-archive-1.nodes:26657"
    key = "default"
    accountPrefix = "osmo"
    keyringBackend = "test"
    chainID = "osmosis-1"
    chainName = "osmosis"

@danbryan Looks like this is handled by David K in #254 with the alternate RPC. Can you look that over and see if what he did there will work?

@esaari1 nope, that did not work, I am confident all osmosis nodes have the same "bad data" and having a backup RPC node is not the way to solve this.  Based on a conversation I had with @KyleMoser yesterday, we both agree that  the correct way to solve this is described in my comment above.  Would you like to sync with @KyleMoser and I and we can go over this in more detail tomorrow?

I'm gonna make an attempt at this tomorrow, making a new function that will handle the second query. I'll let you know how it goes.

GetBlockByHeight() does not seem to include transaction hashes with the returned data. I am guessing those hashes are rather important to this whole thing. I have tried to find another way to get them. Only other useful function was GetBlock(). This also returns a series of transactions, but here each transaction is just a raw byte array.  Not sure what (if anything) I can do there to get anything meaningful out of that.
Anyone have any advice?


textgen-silence-output-feature in terminal

Hello,
Added the new feature to silence TextGen's output in the terminal.

Description: Added a new feature to control printing of TextGen's output to the terminal.,
Issue: the issue #TextGen parameter to silence the print in terminal #10337  it fixes (if applicable)

Thanks;

@hwchase17 Thanks for letting me know.

thanks @Abonia1!


DataGrid: prevent trimming of FilterOperator

Description
@henon another trimming issue
Fixes #5131
Usually this would not happen, since type.GetFields() has annotation with DynamicallyAccessedMemberTypes.PublicFields, but those are not working with literals...
NB! In ticket I mentioned one more issue that is not related to trimming.
How Has This Been Tested?
By hands with trimming mode enabled on the wasm project.
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Great, thanks a lot!


Fly fails to work after a tp/warp - though it lists as "on" and fall damage is still off

When using tp or warp commands with fly on, we're unable to fly. Calling /fly disables it. /fly again will enable it, and fly works as expected.

I don't have this issue on 6.9c Version of Eseentials. Try updating first

This is still occurring, v7.2e, sponge 1138. It's happening across multiple servers with very different plugins, and one server where essentials is the only plugin loaded. It's 100% consistent.

/fly broke recently, I am looking into the cause - it may be SpongeCommon related.

Does this issue still happen? @hsyyid
If it is, a simple solution may be that before teleporting, check if the player is flying and store that value and teleport. after teleport apply the value.

@kinggoesgaming The entire /fly command doesn't appear to work anymore..

@hsyyid ok thats weird.. AFAIK Flying is using Data API unless I am mistaken. If it is then it is possible that FlyData could be broken...

? I don't have any issue with /fly, teleportation or regardless. Maybe something to do with the way it handles FlyData on specific setups?
SpongeForge 1145
EssentialCmds 7.4

@12AwsomeMan34 I've tried it out again and while in survival on SpongeForge, couldn't fly despite my capabilities being updated via SpongeCommon.
SpongeCommon Issue

@hsyyid I can fly in survival :/
http://i.imgur.com/qkk9HIP.jpg
SpongeForge 1151
EssentialCmds 7.4c

Hooray for fly hacks #derps


tree-work should be in window namespace

The proposed tree API should be defined in the window name, but in workspace. The former is UX'is things (like status bar, editors eat) whereas the latter is for things that are related to currently open folder (like documents, search, settings)

I feel it should be parallel to workspace.registerTextDocumentContentProvider though.

Nope - it about UX not content


feat(websocket): websocket connector implementation

Closes gravitee-io/gravitee-cockpit#301

PR has been closed while trying to setup the CI. Seems impossible to reopen. I'll create a new one.


Add verbose weights

python lora-inspector.py -v /mnt/900/lora/boo_v2.safetensors

down_block_0_proj_in weight average magnitude: 1.4924503799105646
down_block_0_proj_in weight average strength: 0.017584813472947592
down_block_0_proj_out weight average magnitude: 1.5157774537695803
down_block_0_proj_out weight average strength: 0.017854483676551985
unet_down_block_0_transformer_block_0_attentions_to_k weight average magnitude: 1.462021831711949
unet_down_block_0_transformer_block_0_attentions_to_k weight average strength: 0.014734332086778964
unet_down_block_0_transformer_block_0_attentions_to_out_0 weight average magnitude: 1.5096795979790278
unet_down_block_0_transformer_block_0_attentions_to_out_0 weight average strength: 0.017774835308342455
unet_down_block_0_transformer_block_0_attentions_to_q weight average magnitude: 1.445551043693953
unet_down_block_0_transformer_block_0_attentions_to_q weight average strength: 0.017098382122298614
unet_down_block_0_transformer_block_0_attentions_to_v weight average magnitude: 1.4463436289083411
unet_down_block_0_transformer_block_0_attentions_to_v weight average strength: 0.01456201074246142

Trying to figure out the best way to break up the blocks. Also need to look into how to identify the block appropriately. There are tools out there with in/mid/out "layers" or something like in DAAM and block weight merging. But the keys do not have these relevant associations so I'm not sure of the connections there.
This representation may be appropriate and then some cleaning up of what values should be together. Attention weights (k, v, q) are tricky to try and group separately as they associate in a process. Maybe each block should just be evaluated together in most cases and maybe a very very verbose version breaking down each individual component (like to_k, to_v, to_q, ,and so on) averages.
Also not sure if its even a good idea to break this up into blocks. But maybe this will be good enough for some specific purpose.
Let me know what you think.

Verbose weights needs to include Text Encoder and Conv blocks as well.
Clarify unet naming on all appropriate keys


Use parents from resource when there are not exist in MetricRollup

Select parents from resource when there are nils in MetricRollups records
In this PR https://github.com/ManageIQ/manageiq/pull/11648 we
introduced selecting rates according to first MetricRollup
record of group. We can do it because group of these records
belong to one resource.
Selection is based on
MetricRollup#parent_host or parent_ems_cluster or
parent_storage or parent_ems but sometimes this fields in
MetricRollup are nil and it produces empty cells on the
report - it is because proper rate was not selected.
Fix provides that we are selecting parents from
the resource direcly when there are not exists in
MetricRollup.
Screenshot of issue: MetricRollup#parent_storage was nil in May records.
before

after

@miq-bot add_label chargeback, bug, reporting
@miq-bot assign @gtanzillo

@miq-bot add_label wip

@miq-bot remove_label wip

After disscussion with @isimluk we realized that these changes should be done also for determination of key in the method
so before it I moved determination of resource parents (host, ems_cluster, storage and tenant) to the one method in first two commits and then I did described changes on the one place.
thanks @isimluk  and please review

@gtanzillo I think this is step in the right direction.

The question remains, why the metric rollup records without values had existed.

Euwe Backport details:
$ git log -1
commit 9910726a39da3ebd18159b90f3a10998f74e71d6
Author: Gregg Tanzillo<EMAIL_ADDRESS>Date:   Tue Nov 1 09:08:04 2016 -0400

    Merge pull request #12164 from lpichler/select_parent_when_missing_in_metric_rollup

    Use parents from resource when there are not exist in MetricRollup
    (cherry picked from commit 70617181fdcfa9ba625dcef95989d3a48a182f32)


AMD/Require Transpilation Option

It would be useful to get an AMD/Require source option available in NPM form to avoid a transpilation step for developers.  If we provide a dev framework that supports AMD that adds OT as a dependency, they won't be able to use that dependency without manually transpiling.

We have a browser client framework that is consumed by developers as an NPM module.  This framework currently uses RequireJS AMD modules.  We are trying to uptake the OpenTelemetry API and add @opentelmetry/api as a package.json dependency.  The issue is - even if we transpile it ourselves to compile the framework (which we would need to if we're using the standard NoOp impl - see Issue #114), we run into an issue where:

Dev installs our framework with dependencies and a predefined Require config
Dev cannot run the app they've developed with our framework since @opentelemetry/api will not be able to be resolved by RequireJS.

We could instrument our code with untyped objects to get around the direct OT dependency altogether (this is our current solution) but a first-party AMD/Require distribution would make this less painful to consumers of our tools.  I'm assuming any framework supporting this standard (ESM isn't really fully baked yet for browsers) for the foreseeable future will run into the same problem.
K

From: Daniel Dyla @.>
Sent: Friday, August 27, 2021 1:02 PM
To: open-telemetry/opentelemetry-js-api @.>
Cc: Kevin Cirone @.>; Author @.>
Subject: [External] : Re: [open-telemetry/opentelemetry-js-api] AMD/Require Transpilation Option (#115)
Can you provide an example that you would expect to work that isn't?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/open-telemetry/opentelemetry-js-api/issues/115*issuecomment-907344289__;Iw!!ACWV5N9M2RV99hQ!c9yltnjKsd88eoPUQ_2UEaH_Fm8RZv4eW47j6IYYWBOhxKkGOb8WMoGKZFj7DjdPbw$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AGKZT7RP42KKJ6OEXG6COR3T67AKNANCNFSM5CBLCNDQ__;!!ACWV5N9M2RV99hQ!c9yltnjKsd88eoPUQ_2UEaH_Fm8RZv4eW47j6IYYWBOhxKkGOb8WMoGKZFh_hdgGeg$.
Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!ACWV5N9M2RV99hQ!c9yltnjKsd88eoPUQ_2UEaH_Fm8RZv4eW47j6IYYWBOhxKkGOb8WMoGKZFhfAiP7uw$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!ACWV5N9M2RV99hQ!c9yltnjKsd88eoPUQ_2UEaH_Fm8RZv4eW47j6IYYWBOhxKkGOb8WMoGKZFjr86EsQg$.

After looking into this a little more it seems there are many ways to handle this. Just looking at the https://github.com/umdjs/umd/tree/master/templates repository shows many possible "official" ways of handling this.
Can you provide a concrete proposal for changes we can make which would satisfy you concern?


powercat timeout not working?

I'm trying a powercat with a -t 2 for a two second timeout and seeing 2 minutes. Actually I see two minute timeout regardless of what I set -t
PS C:\Users\tfulmer> date;powercat -c <IP_ADDRESS> -p 22 -t 2;date
Thursday, February 23, 2017 3:22:40 PM
SSH-2.0-OpenSSH_7.1
Thursday, February 23, 2017 3:24:40 PM

The timeout option means it will give up on setting up the connection after -t seconds. Since you see the SSH banner, the connection was successful and the timeout doesn't apply anymore. If you want to disconnect right after connecting you can use -d.


Does this violate their TOS?

If I use this in a project, do you know if it breaks Ultimate Guitars TOS, or are the actual tabs on an open license?

I really don't know, my guess would be that it breaks their TOS. I built this for personal purpose.
https://www.ultimate-guitar.com/about/tos.htm


[#168] hide the jolokia test panels in production

Make sure the test panels aren't displayed in prod.
Here's a screen capture of a prod build:

Here's a screen capture of a dev build:

@lavocatt , looks good!.
just  one query from my side. for production build i am unable to login to jolokia in my local when i run the production build it's pop up the login failed modal.

@lavocatt , changes for both dev and prod looks good!. just one query from my side. for production build i am unable to login to jolokia in my local when i run the production build it's pop up the login failed modal in my case. @howardgao can you please double check this?

This most probably happens because you were running the prod with yarn instead of using the container. Can you retry by following the documentation on how to build the docker image please?


from_env causes io-unsafety in child processes

(copied from https://github.com/rust-lang/rust/pull/113730#issuecomment-1869013070)
These lines seem questionable: https://github.com/rust-lang/jobserver-rs/blob/b4bc5db730a93d01cf8d0d868a2b6f553f535d2d/src/unix.rs#L152-L153
They lead the fds not being available to child processes by default (unless reverted by Client::configure) but from_env_ext() does not remove the environment variables. Which means child processes are instructed to access file descriptor numbers for jobserver communication that aren't open anymore and may have been reopened to point to other files. This seems like a violation of IO-safety (https://github.com/rust-lang/rust/issues/116059#issuecomment-1733591651).
Either cloexec shouldn't be set or the environment variables should also be removed and only be added back via configure.

I think removing the env arg makes sense?

I suspect that in a typical case you do want to pass the created or inherited jobserver to children processes.
In all cases caught by https://github.com/rust-lang/rust/pull/113730 the right solution was to pass the jobserver further (except one case when it didn't matter much).

https://github.com/rust-lang/jobserver-rs/pull/65 is a draft PR that reverses the current behavior - jobserver is inherited by default, but the inheritance can be disabled by explicitly calling a method.

I think the best way to fix this is to use named fifo instead of annoymous pipe.
Passing pipe by fd also shares its file description, meaning whenever one process sets O_NONBLOCK it affects all the other processes.
I've got bitten by this the hard way in cc


Got “unexpected rune” with --preview

Hello,
I got this error while using --preview as a script.
The error is reproducible with:
cat <<'EOF' | fzf --preview 'text=$(echo {})'
1
2
3
EOF

Output:
Parse error: unexpected rune ')'
code from -c, line 1: text=$(echo '1')

Here is the complete example.

Did you manage to fix it @alexherbo2?


What happened?
I subclassed beam.transforms.stats.ApproximateQuantilesCombineFn in the following way:
class ApproxQuantileCombiner(ApproximateQuantilesCombineFn):
    def __init__(
        self,
        metric_key: tfma.metrics.MetricKey,
        num_quantiles: int = 100,
        max_num_elements: int = 20_000_000,
        epsilon: float = 0.01,
        num_buffers: int = None,
        buffer_size: int = None,
        return_quantile: int = 50,
    ):
        # The create method will calculate the buffers
        dummy_cls = ApproximateQuantilesCombineFn.create(
            num_quantiles, epsilon, max_num_elements
        )
        # print(estimated_buffer)
        super(ApproxQuantileCombiner, self).__init__(
            num_quantiles=num_quantiles,
            buffer_size=buffer_size or dummy_cls._spec.buffer_size,
            num_buffers=num_buffers or dummy_cls._spec.num_buffers,
            input_batched=True,
        )
        self._metric_key = metric_key
        self.num_quantiles = num_quantiles
        self.max_num_elements = max_num_elements
        self.epsilon = epsilon
        self.return_quantile = int(return_quantile)

    def __reduce__(self):
        # need to match exactly to the __init__ args
        return (
            self.__class__,
            (
                self._metric_key,
                self.num_quantiles,
                self.max_num_elements,
                self.epsilon,
                self._spec.num_buffers,
                self._spec.buffer_size,
                self.return_quantile,
            ),
        )

    def extract_output(self, accumulator):
        outputs = np.array(super().extract_output(accumulator))
        if self.return_quantile:
            return {self._metric_key: float(outputs[self.return_quantile])}
        else:
            return {self._metric_key: outputs}

My preprocessor DoFn returns an list of float numbers which I want to compute the median on. This works on a local direct runner or in one instance of the Dataflow pipeline I was running. However, in another instance of the run, the Dataflow pipeline throws the following error:
Root cause: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py",
line 287, in _execute response = task() File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py",
line 360, in <lambda> lambda: self.create_worker().do_instruction(request), request) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py",
line 596, in do_instruction return getattr(self, request_type)( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py",
line 634, in process_bundle bundle_processor.process_bundle(instruction_id)) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py",
line 1003, in process_bundle input_op_by_transform_id[element.transform_id].process_encoded( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py",
line 225, in process_encoded decoded_value = self.windowed_coder_impl.decode_from_stream( File "apache_beam/coders/coder_impl.py",
line 1519, in apache_beam.coders.coder_impl.ParamWindowedValueCoderImpl.decode_from_stream File "apache_beam/coders/coder_impl.py",
line 1520, in apache_beam.coders.coder_impl.ParamWindowedValueCoderImpl.decode_from_stream File "apache_beam/coders/coder_impl.py",
line 1009, in apache_beam.coders.coder_impl.AbstractComponentCoderImpl.decode_from_stream File "apache_beam/coders/coder_impl.py",
line 1195, in apache_beam.coders.coder_impl.SequenceCoderImpl.decode_from_stream File "apache_beam/coders/coder_impl.py",
line 1557, in apache_beam.coders.coder_impl.LengthPrefixCoderImpl.decode_from_stream File "apache_beam/coders/coder_impl.py",
line 240, in apache_beam.coders.coder_impl.StreamCoderImpl.decode File "apache_beam/coders/coder_impl.py",
line 548, in apache_beam.coders.coder_impl.FastPrimitivesCoderImpl.decode_from_stream File "apache_beam/coders/coder_impl.py",
line 583, in apache_beam.coders.coder_impl.FastPrimitivesCoderImpl.decode_from_stream File "apache_beam/coders/coder_impl.py",
line 273, in apache_beam.coders.coder_impl.CallbackCoderImpl.decode_from_stream File "stringsource",
line 17, in apache_beam.transforms.stats._QuantileBuffer.__setstate_cython__
TypeError: Expected tuple, got dict
Worker ID: beamapp-root-0516134446-3-05160644-xj8p-harness-zzz3,

Also, the job does not fail until ~30 min later, instead of failing immediately. I am wondering what could be causing this issue as the error message does not seem very obvious to me what's the source of the problem.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[X] Component: Google Cloud Dataflow Runner

I'm not sure but possibly somehow the CombineFn invariants got broken. Could you  instantiate the CombineFn with necessary parameters instead of having to subclass it?

In general, Dataflow fails after retrying the same bundle 4 times; it is possible that there is some non-determinism in how data gets distributed & aggregated and the bug doesn't always manifest.

@tvalentyn Hi. I am able to resolve the issue "most of the time". This is what I mean:
I modified the above subclassing to the following.
class ApproxQuantileCombiner(ApproximateQuantilesCombineFn):
    def __init__(
        self,
        metric_key: tfma.metrics.MetricKey,
        num_quantiles: int = 100,
        max_num_elements: int = 20_000_000,
        epsilon: float = 0.01,
        num_buffers: int = None,
        buffer_size: int = None,
        return_quantile: int = 50,
    ):
        # The create method will calculate the buffers
        dummy_cls = ApproximateQuantilesCombineFn.create(
            num_quantiles, epsilon, max_num_elements
        )
        buffer_size = buffer_size or dummy_cls._spec.buffer_size
        num_buffers = num_buffers or dummy_cls._spec.num_buffers
        # This is a guess, but if we do num_quantiles=num_quantiles
        # the beam job will fail, since the pickle job will think it is
        # dictionary input (kwargs) instead of tuple inputs (args)
        # So make sure to use positional arguments.
        super(ApproxQuantileCombiner, self).__init__(
            num_quantiles,
            buffer_size,
            num_buffers,
            input_batched=True,
        )
        self._metric_key = metric_key
        self.num_quantiles = num_quantiles
        self.max_num_elements = max_num_elements
        self.epsilon = epsilon
        self.return_quantile = int(return_quantile)

    def __reduce__(self):
        # Need to match exactly to that of the __init__ inputs
        # fmt: off
        return (
            self.__class__,
            (
                self._metric_key,
                self.num_quantiles,
                self.max_num_elements,
                self.epsilon,
                self._spec.num_buffers,
                self._spec.buffer_size,
                self.return_quantile
            )
        )
        # fmt: on

    def extract_output(self, accumulator):
        outputs = np.array(super().extract_output(accumulator))
        if self.return_quantile:
            return {self._metric_key: float(outputs[self.return_quantile])}
        else:
            return {self._metric_key: outputs}

Notice my comments at the super() instantiation. I changed from kwargs to args. As described in my comment, my guess is that, pickle thinks the arguments are kwargs and will compile it into a dict, while positional args will be compiled into a tuple. So when reconstructing the instances back across different workers (by unpickling the instance), it will reinstantiate the instances using either dict or tuple, depending on if it is kwargs or args.
I am saying this is resolved "most of the time" is because, although this allows me to run the beam pipeline most of the time, I still sometimes see this error. However, rerunning the pipeline allows me to successfully complete the pipeline again. It's truly mysterious what's unstable.

Editor: I forgot to mention that upgrading to 2.46.0 is also part of the solution to this.

Thanks, are you saying this is not reproducible in 2.46.0 ?

Thanks, are you saying this is not reproducible in 2.46.0 ?

Friendly reminder about the question above. Thanks!

Closing due to no response, but please feel free to reopen if still an issue.


Changed PaiPal to PayPal

Hey,
There was a slight typo on the readme. I have updated that and you can take a look. Please let me know if I can be of any more help.
Thanks!

wow, that's a typo.  I can't even imagine how I allowed it.  Many thanks

Well, many eyes crossing your project. You're covered @uPagge :)


Filtering is broken when using only custom columns.

I needed to use custom columns(no field-name) for all columns in some pages, on those pages when I type something on search field, all items disappear. If I remove the text on the filter box, the items do NOT appear back.

As I probably mentioned before, "Computed Fields" with an angular filter or customizing the body cell for an existing field will do the trick. The demo site has examples inside the Columns section, and I also added a test case for x-editable. Let me know if you guys still experience issues.


Data Preprocessing

Which datasets should I download? And how to do data preprocessing?

Thanks for your interest! You can download the full nuscenes from the official website without additional data processing.


random sidecars with another metrics

I have an important metric to check the occupied space inside the pvc (i used longhorn)
for this I use sidecar joins to each psql cluster replica in other psql operators (zalando as example)
essentially, I'm checking how much space is left.
what about using cnpg ?
i didn't see in crd records the ability to join another sidecars with commonplace pvc
my metrics: https://github.com/vasyakrg/df-exporter

Hi @vasyakrg
You mean like providing a metric with the space left in the storage of the database? in that case it's a big complicated since you may have the space of pgdata and the space for wal storage, currently we provide a metric with the name cnpg_pg_database_size_bytes
If you want to get the space used inside the PVC I'd suggest to get that metric from the CSI driver, or if you have an a idea on how we can provide that metric internally, will be also great, but need to consider that any system command may not be available since it could be a distroless image, even for PostgreSQL that's possible and a user could be using one like that.
In the meantime, I'm turning this into a discussion since doesn't look like an issue yet, but we can open an issue starting on the discussion.


Add feature to add all events from a race week to Apple Calendar app

Description
I added a feature to add all events from a race week to the Apple Calendar application. It basically uses AppleScript to access the Mac application, retrieve calendars, and add events to the selected calendar.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

hi @qeude - nice changes! Hope you don't mind, I've sneaked a small change in as well 😅
A couple of mentions:

Could you update the CHANGELOG.md file to reflect this change?
Trying to add the sessions to a calendar I'm not allowed to write to results in the extension crashing:

https://user-images.githubusercontent.com/1155589/165083569-0f5f4fe9-3946-4d7a-b477-e1681cddaea4.mov
Let me know once you've had a chance to fix the issue or if you need some help either here or on Slack 😸

I'm going to take a look at these feedbacks ASAP 🙌🏼

@sxn No worries about adding some changes, it's always ok to improve an extension together 😄
I've made the changes you requested:

Changed the CHANGELOG.md.
Changed the used AppleScript so it doesn't list calendars that are not writable.
Didn't change moment.js for the reason explained here. Even if I tend to be a "no-third" dependency guy, I feel that moment.js is pretty mature to be used and useful for readability here.

nice! 🎉

thx guys...


Moved projects into subfolders by type

ApiPort* projects (and tests) moved into ApiPort folder
Microsoft.Fx* projects (and tests) moved into lib folder

@mjrousos There appears to be an issue in our build.sh from the CI builds... maybe it's no longer able to locate the test file?

Yea, I just saw that. Turns out that build.sh builds each project individually (whereas build.ps1 builds the sln) so it should have been updated with the new, more nested, csproj paths. Fixing now...

@dotnet-bot test OSX10.12 please


fix(code): fix child keys warning

GitHub Issue - #873
Before the fix:

After the fix:

@artemrys we miss some key for a group model. Can we restrict label to be unique across groups to let us use it as a key?

@artemrys we miss some key for a group model. Can we restrict label to be unique across groups to let us use it as a key?

Missed this notification.
If you are talking about these groups (https://splunk.github.io/addonfactory-ucc-generator/advanced/groups_feature/), then I think we can do that.
There is no reason to specify duplicate labels for the groups anyways.

Alright, the label field serves well as a key. Unfortunately, we can't validate uniqueness by key with JSON Schema

Okay, we can do that in the Python code during the build.
This PR needs to wait until I implement this change, I'll try to do it this week.


does the cloud init livekit version needs update?

Hello,
do we need to update the version here to 0.15.2?
https://raw.githubusercontent.com/livekit/livekit-server/master/deploy/cloud-init.ubuntu.yaml
https://github.com/livekit/livekit-server/blob/master/deploy/cloud-init.amzn2.yaml

Hey @ahmed-adly-khalil, we really should.. I'm in the process of updating docs, but we'll be moving to the new deployment generator as outlined here.
We'll make a note in here shortly.


TypeError: Cannot read property 'slice' of undefined

I got this error randomly when typing. A new error appeared every time I entered or removed a character. Saving the file fixed the error. Have not been able to reproduce.
(node:18036) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'slice' of undefined
    at Object.t.default (c:\Users\Misode\.vscode\extensions\spgoding.datapack-language-server-1.13.8\dist\server.js:1:1739218)
    at c:\Users\Misode\.vscode\extensions\spgoding.datapack-language-server-1.13.8\dist\server.js:1:207092
(node:18036) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'slice' of undefined
    at Object.t.default (c:\Users\Misode\.vscode\extensions\spgoding.datapack-language-server-1.13.8\dist\server.js:1:1739218)
    at c:\Users\Misode\.vscode\extensions\spgoding.datapack-language-server-1.13.8\dist\server.js:1:207092
(node:18036) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:18036) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:18036) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:18036) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[Error - 3:52:32 AM] Request textDocument/completion failed.
  Message: Request textDocument/completion failed with message: Cannot read property 'length' of undefined
  Code: -32603

Thank you! The error stack really helps.
The error was thrown while handling incremental updating. However I have no idea why it happened because the string that slice was called on should never be undefined 🤔

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:

This just happened again.
TypeError: Cannot read property 'slice' of undefined
    at Object.t.default (c:\Users\Misode\.vscode\extensions\spgoding.datapack-language-server-2.0.0\dist\server.js:1:2626156)
    at c:\Users\Misode\.vscode\extensions\spgoding.datapack-language-server-2.0.0\dist\server.js:1:300986
info.strings = execute as @s run scoreboard players add #manager temp 1
execute if score #manager temp matches 1 run datapack disable "file/DirectEntityTest"
execute if score #manager temp matches 1 run tellraw @s [{"text":"Dropcompressing ","bold":true},{"text":"disabled","color":"red","bold":true},{"text":".","color":"black","bold":true}]
execute if score #manager temp matches 2.. run scoreboard players set #manager temp 0
execute if score #manager temp matches 0 run datapack enable "file/DirectEntityTest"
execute if score #manager temp matches 0 run tellraw @s [{"text":"Dropcompressing ","bold":true},{"text":"enabled","color":"green","bold":true},{"text":".","color":"black","bold":true}]
execute as @s run scoreboard players set @s temp 0

* * * * * *
range = {"start":{"line":9,"character":4},"end":{"line":9,"character":4}}

:tada: This issue has been resolved in version 2.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


PR view removes first char of each line in some files

Recently I started seeing a bug in pull request view. The first few files in the pull request have first char removed from every line. It's annoying to review code properly when what I see is different from what everyone else sees.
Here is a screenshot of a PHP file (with some censored parts for any copyright or security reasons) where lines should begin with "use", but I can only see "se".

What have I discovered on my own:

It affects the "Files" tab of Pull Request view
It does NOT affect Code view
It also affects other types of files, like .env, Makefile and several others.
I think that it only applies to first one or two files cause most of the time other files are displayed properly.
It doesn't matter if affected files have any Github PR review comments attached or not.
It's not a matter of display or scroll. I've checked the source code view in Chrome and there really is a "se" instead of "use".
The proper version is visible for a really short time while loading the page and then first chars are removed.
Disabling "Refined Github" extension fixes it but obviously that's not something that I would like to stick with.

I really like this plugin, but I'm disabling it until this bug is fixed.

See https://github.com/sindresorhus/refined-github/issues/1444 and especially this comment: https://github.com/sindresorhus/refined-github/issues/1444#issuecomment-408274280

Oh, sorry for posting a duplicate. I was looking for similar issues but somehow didn't found this one. I'm closing this.


App setup

Basic App Setup
:recycle: Current situation & Problem
Addressing Issue #1 (sorry I didn't have the permissions at the time to create a branch straight from the issue)
Template app needs to be customized to our 3 tabs
:bulb: Proposed solution
Added Trends and Profile tabs. I have left the contacts tab in so we can use for inspiration, but we should remove before presentation. Also have no touched onboarding flow yet, let's create a plan + language before we do that.
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

@jenlmoore wanna review and merge this?


How to disable point to scroll outside the handle?

I want to put some content in the handle container, but when i tap on my content the handle starts sliding to the point I clicked. Is there an option to disable this?

I implemented it:
scrollToTap
onWrapperMouseDown: function(e) {
      if (!this.options.scrollToTap) {
          return;
      }
      Cursor.refresh(e);
      preventEventDefaults(e);
      this.startTap();
  },

Cool!
On Dec 22, 2016 20:09, "Marco Castignoli"<EMAIL_ADDRESS>wrote:

Closed #119 https://github.com/skidding/dragdealer/issues/119.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/skidding/dragdealer/issues/119#event-903313279, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAPTfsvwaL1rU8FItHr9qZ6otl8PQw6wks5rKrzMgaJpZM4LUFmG
.

Are you sarcastic? There was already another feature like this?

There was already another feature like this?

No.
Not sarcastic. Happy you found a solution so quick. Feel free to create a PR to make it an official option.


Added some zero trust topics on infra

Added some relevant articles about zero trust for infrastructure that is relevant for this section in ALZ.

Learn Build status updates of commit 15d0cb4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/ready/landing-zone/design-area/security.md
:warning:Warning

Details

docs/ready/landing-zone/design-area/security.md

Line 107, Column 27: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/security/zero-trust/zero-trust-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 118, Column 27: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/security/zero-trust/azure-infrastructure-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 118, Column 164: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/architecture/example-scenario/gateway/application-gateway-before-azure-firewall' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 107, Column 27: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/security/zero-trust/zero-trust-overview' will be broken in isolated environments. Replace with a relative link.
Line 118, Column 27: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/security/zero-trust/azure-infrastructure-overview' will be broken in isolated environments. Replace with a relative link.
Line 118, Column 164: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/architecture/example-scenario/gateway/application-gateway-before-azure-firewall' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@froand,
Can you implement Tim'ssuggestions above?

@timwarner-msft.
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@MicrosoftDocs/pnpftes, this PR updates content in the cloud-adoption-framework repo.
Can you review the proposed changes?

Hi @froand Do we have a work item for this one?
@JanetCThomas

Lets put a pin into this change for now.  The ZT content landscape is currently undergoing a massive update. When that settles, we will update the ALZ article accordingly.


Errors in mir_eval library

I'm running with the following parameters in train.py
batch_size = 4
sequence_length = 327680
model_complexity = 16

And I got the following error:
0%|          | 499/500000 [01:32<25:51:47,  5.36it/s]/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription.py:167: UserWarning: Estimated notes are empty.
  warnings.warn("Estimated notes are empty.")
/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/multipitch.py:275: UserWarning: Estimate frequencies are all empty.
  warnings.warn("Estimate frequencies are all empty.")
  1%|          | 2999/500000 [10:07<25:37:36,  5.39it/s]/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py:185: FutureWarning: `rcond` parameter will change to the default of machine precision times ``max(M, N)`` where M and N are the input matrix dimensions.
To use the future default and silence this warning we advise to pass `rcond=None`, to keep using the old, explicitly pass `rcond=-1`.
  ref_matched_velocities)[0]
ERROR - train_transcriber - Failed after 0:10:13!
Traceback (most recent calls WITHOUT Sacred internals):
  File "train.py", line 117, in train
    for key, value in evaluate(validation_dataset, model).items():
  File "/home/lab/Documents/CS224NProject/Sample/onsets-and-frames/evaluate.py", line 70, in evaluate
    p, r, f, o = evaluate_notes_with_velocity(i_ref, p_ref, v_ref, i_est, p_est, v_est, velocity_tolerance=0.1)
  File "/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py", line 291, in precision_recall_f1_overlap
    offset_min_tolerance, strict, velocity_tolerance)
  File "/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py", line 178, in match_notes
    ref_matched_velocities = ref_velocities[matching[:, 0]]
IndexError: too many indices for array

BTW, another issue, I first tried all the default parameters, and I kept getting GPU out of memory message. My system should meet the minimum system requirements.
Does anyone have insights into these two issues?

Hi @yuanshenli , This is because of an mir_eval issue where it fails when there is no matching which was only recently fixed. This no-matching situation inevitably happens in early iterations. There is a recent path merged to mir_eval to fix this, but this hasn't made it through a new release at the moment.
So for now, I'd recommend installing the latest commit of mir_eval by:
pip install git+https://github.com/craffel/mir_eval.git

in order to install the most recent version of the mir_eval package out of the master branch.
After doing this, the training should run just fine; let me know if you encounter any issues.

Hi @yuanshenli , This is because of an mir_eval issue where it fails when there is no matching which was only recently fixed. This no-matching situation inevitably happens in early iterations. There is a recent path merged to mir_eval to fix this, but this hasn't made it through a new release at the moment.
So for now, I'd recommend installing the latest commit of mir_eval by:
pip uninstall mir_eval
pip install git+https://github.com/craffel/mir_eval.git

in order to install the most recent version of the mir_eval package out of the master branch.
After doing this, the training should run just fine; let me know if you encounter any issues.

Thank you so much for the timely reply! so far it made through the first 2000 iterations, it did get the warning  warnings.warn("Estimated notes are empty.") at first 500 iterations like before, but as you suggested it just happed in early iterations.
May I ask what values you used for batch_size and model_complexity? I kept getting cuda out_of_memory error. below is my gpu configuration:
Mon Mar  4 18:32:31 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.77                 Driver Version: 390.77                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX TIT...  Off  | 00000000:02:00.0 Off |                  N/A |
| 57%   83C    P2    89W / 250W |    525MiB / 12212MiB |      4%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 108...  Off  | 00000000:03:00.0 Off |                  N/A |
| 29%   60C    P2   133W / 250W |   2951MiB / 11178MiB |     84%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 108...  Off  | 00000000:04:00.0  On |                  N/A |
|  0%   48C    P8    14W / 280W |    657MiB / 11175MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

Hi @yuanshenli , This is because of an mir_eval issue where it fails when there is no matching which was only recently fixed. This no-matching situation inevitably happens in early iterations. There is a recent path merged to mir_eval to fix this, but this hasn't made it through a new release at the moment.
So for now, I'd recommend installing the latest commit of mir_eval by:
pip uninstall mir_eval
pip install git+https://github.com/craffel/mir_eval.git

in order to install the most recent version of the mir_eval package out of the master branch.
After doing this, the training should run just fine; let me know if you encounter any issues.

Just as I thought it was working, same error occurred:
  0%|          | 499/500000 [01:36<26:19:05,  5.27it/s]/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription.py:167: UserWarning: Estimated notes are empty.
  warnings.warn("Estimated notes are empty.")
/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/multipitch.py:275: UserWarning: Estimate frequencies are all empty.
  warnings.warn("Estimate frequencies are all empty.")
  0%|          | 2499/500000 [09:13<26:18:47,  5.25it/s]/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py:185: FutureWarning: `rcond` parameter will change to the default of machine precision times ``max(M, N)`` where M and N are the input matrix dimensions.
To use the future default and silence this warning we advise to pass `rcond=None`, to keep using the old, explicitly pass `rcond=-1`.
  ref_matched_velocities)[0]
ERROR - train_transcriber - Failed after 0:09:22!
Traceback (most recent calls WITHOUT Sacred internals):
  File "train.py", line 117, in train
    for key, value in evaluate(validation_dataset, model).items():
  File "/home/lab/Documents/CS224NProject/Sample/onsets-and-frames/evaluate.py", line 70, in evaluate
    p, r, f, o = evaluate_notes_with_velocity(i_ref, p_ref, v_ref, i_est, p_est, v_est, velocity_tolerance=0.1)
  File "/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py", line 291, in precision_recall_f1_overlap
    offset_min_tolerance, strict, velocity_tolerance)
  File "/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py", line 178, in match_notes
    ref_matched_velocities = ref_velocities[matching[:, 0]]
IndexError: too many indices for array

Hi @yuanshenli , This is because of an mir_eval issue where it fails when there is no matching which was only recently fixed. This no-matching situation inevitably happens in early iterations. There is a recent path merged to mir_eval to fix this, but this hasn't made it through a new release at the moment.
So for now, I'd recommend installing the latest commit of mir_eval by:
pip uninstall mir_eval
pip install git+https://github.com/craffel/mir_eval.git

in order to install the most recent version of the mir_eval package out of the master branch.
After doing this, the training should run just fine; let me know if you encounter any issues.

Just as I thought it was working, same error occurred:
  0%|          | 499/500000 [01:36<26:19:05,  5.27it/s]/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription.py:167: UserWarning: Estimated notes are empty.
  warnings.warn("Estimated notes are empty.")
/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/multipitch.py:275: UserWarning: Estimate frequencies are all empty.
  warnings.warn("Estimate frequencies are all empty.")
  0%|          | 2499/500000 [09:13<26:18:47,  5.25it/s]/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py:185: FutureWarning: `rcond` parameter will change to the default of machine precision times ``max(M, N)`` where M and N are the input matrix dimensions.
To use the future default and silence this warning we advise to pass `rcond=None`, to keep using the old, explicitly pass `rcond=-1`.
  ref_matched_velocities)[0]
ERROR - train_transcriber - Failed after 0:09:22!
Traceback (most recent calls WITHOUT Sacred internals):
  File "train.py", line 117, in train
    for key, value in evaluate(validation_dataset, model).items():
  File "/home/lab/Documents/CS224NProject/Sample/onsets-and-frames/evaluate.py", line 70, in evaluate
    p, r, f, o = evaluate_notes_with_velocity(i_ref, p_ref, v_ref, i_est, p_est, v_est, velocity_tolerance=0.1)
  File "/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py", line 291, in precision_recall_f1_overlap
    offset_min_tolerance, strict, velocity_tolerance)
  File "/home/lab/.linuxbrew/Cellar/python/3.7.2_2/lib/python3.7/site-packages/mir_eval/transcription_velocity.py", line 178, in match_notes
    ref_matched_velocities = ref_velocities[matching[:, 0]]
IndexError: too many indices for array

Hmm just realized that my mir_eval wasn't updated properly, let me try again.


Components not getting updates via context from JSS/ThemeProvider

The following example shows how the theme is correctly toggled using React and React-dom. Switching to react-compat breaks it. Something todo with context being used by ThemeProvider?
https://stackblitz.com/edit/react-vxvdmr
What we found:

CSS selectors is changed in the header as expected
React Component do re-render as expected
The classes object sent via Context from ThemeProvider is not updated (rerender with the original classNames that does not have a definition anymore)

!!
Our example offline at least renders using preact-compat with the default theme, but at stackblitz it stops as soon we try to mount a component that is wrapped by injectSheet hoc.

Hmm - have you tried this outside Stackblitz? I don't see any aliases defined there, so when react-redux or react-jss import react, they're still getting React proper (not compat).  That's definitely going to break things, it's never a good idea to run preact-compat and react on the same vtree.

Hi, ahh yes, the issue was first found in local project with aliases setup in webpack:
resolve: {
alias: {
react: "preact-compat",
"react-dom": "preact-compat" ...
Then it at leasts runs without errors. Do you want me to setup a repo with it all?

If you have the time, otherwise it's pretty hard to tell what's going on.


Copy text with right-click in SQL results table

When viewing SQL results, it is often desirable to copy a single row, column, or cell value. Currently, the user has to right click, then click view, then select the text, then hit ctrl-C.
Feature request
Add a feature to right-click menu, allowing user to copy cell value.
Right click -> copy

Hi @brylie ,
We just released 2.12.0 with this feature you requested. Would you be kind to test it and provide your feedback? Thanks in advance!
Regards,
William

Closing this now.


Enable auto-sharing of speeches when retrieved, to be able to add an iframe with otter UI into Roam

What I want to achieve is being able to embed otter ui for the speech directly into Roam (arguably a better version of #6). If I just use the speech url now - it won't load, but if I enable sharing for the speech I get the result like:

So the proposal here is to allow people to opt-in to automatically enable sharing for ingested speeches, to make the iframe thing work.

example api request:
await fetch("https://otter.ai/forward/api/v1/share_speech?otid={otid}&userid={userid}", {
    "credentials": "include",
    "headers": {
        "Accept": "application/json, text/plain, */*",
        "Accept-Language": "en-US,en;q=0.5",
        "X-CLIENT-VERSION": "Otter v2.3.114",
        "Sec-Fetch-Dest": "empty",
        "Sec-Fetch-Mode": "cors",
        "Sec-Fetch-Site": "same-origin"
    },
    "method": "GET",
    "mode": "cors"
});

works for me! prs welcome


Remote SSH broken after upgrading to 1.95

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.95.0
OS Version: Windows 11

Steps to Reproduce:

Upgrade VSCode to 1.95.0
Connect any remote host by Remote-SSH

The output indicated a connection timeout, and an error window popped up. However, the logs continued to print, showing that the connection to the remote host was actually established.

One more clue is that the VSCode keeps asking the OS of remote host,  then I select Linux, after that the error window pops out.

I come here to do exactly this post, thanks, UP

code command seems to be broken aswell. code . or code --wait passed to git to use the editor don't work anymore in Remote SSH

@ruijzhan are you using VSCode profiles by chance?  I had this problem in one VSCode instance but not another, and the difference ended up being that the instance that didn't work had an enabled profile.  The instance that used a profile also worked if I reverted to 1.94.2.  When I opened the settings.json for the profile and my user settings.json and moved over the relevant settings, the failing instance started working as expected.
I think VSCode 1.95 is erroneously applying settings that are supposed to apply across all profiles on a per-profile basis.  Since they are supposed to apply to all profiles, you can't set these settings for the profile except through the profile's settings.json (though you really shouldn't need to do so; it's just a workaround that seems to work for me).

@ruijzhan are you using VSCode profiles by chance? I had this problem in one VSCode instance but not another, and the difference ended up being that the instance that didn't work had an enabled profile. The instance that used a profile also worked if I reverted to 1.94.2. When I opened the settings.json for the profile and my user settings.json and moved over the relevant settings from the user settings to the profile settings (even though they're supposed to be "across all profiles" settings), the failing instance started working as expected.
I think VSCode 1.95 is erroneously applying settings that are supposed to apply across all profiles on a per-profile basis. Since they are supposed to apply to all profiles, you can't set these settings for the profile except through the profile's settings.json (though you really shouldn't need to do so; it's just a workaround that seems to work for me), so they use the default value. Since one of these settings is remote.SSH.remotePlatform, it tries to take the value from a profile (which is empty), so it asks you the platform, and it doesn't save to the profile settings (since it's not supposed to), so your platform selection never takes, and it asks you every time you connect.

Thank you. You are right. When I switched to Default profile, it works.
@joshspicer please refer to this

Same issue, VSCode 1.95, MacOS.
Error msg:
Setting up SSH Host xxx.xxx.xxx.xxx: Copying VS Code Server to host with scp

@ruijzhan are you using VSCode profiles by chance? I had this problem in one VSCode instance but not another, and the difference ended up being that the instance that didn't work had an enabled profile. The instance that used a profile also worked if I reverted to 1.94.2. When I opened the settings.json for the profile and my user settings.json and moved over the relevant settings from the user settings to the profile settings (even though they're supposed to be "across all profiles" settings), the failing instance started working as expected.
I think VSCode 1.95 is erroneously applying settings that are supposed to apply across all profiles on a per-profile basis. Since they are supposed to apply to all profiles, you can't set these settings for the profile except through the profile's settings.json (though you really shouldn't need to do so; it's just a workaround that seems to work for me), so they use the default value. Since one of these settings is remote.SSH.remotePlatform, it tries to take the value from a profile (which is empty), so it asks you the platform, and it doesn't save to the profile settings (since it's not supposed to), so your platform selection never takes, and it asks you every time you connect.

Hi,
One more update here:
When I switch to the Default profile, everything works fine. However, if I edit the settings.json of non-default profiles to include the host platform, VSCode no longer prompts for the host platform at startup. Despite this, the error window still appears, although the connection continues running in the background.

Yeah, I did the same.  I also had to add dev.containers.dockerPath to my profile-specific settings.json in order to work with podman, and that setting is also supposed to apply to all profiles, so I think the issue affects to all applies-to-all-profile settings.

@mlawson27
Great find. I confirm that this solves the problem and it must certainly be something related to the scope of the settings.
What I did:

I didn't change the profile to the default. I continued on my profile.
F1 -> Preferences: Open User settings (JSON).
Put     "dev.containers.dockerPath": "podman" in settings.
Vscode warned that this configuration is out of scope but I ignored it.
Try to attach to the container, and the connection was made as always.

Thank you all for the investigations.  I'm looking into if there were any changes to VS Code profiles in the last release that we can handle better in this extension

@joshspicer Yes, the issue persist in version 1.95.1 as related here:
https://github.com/microsoft/vscode-remote-release/issues/10426#issuecomment-2451891277

I'm unfortunately not able to repro.  I tried creating a new profile (not tweaking any of the settings in the new profile).  I then swapped to that profile and ssh'd to a host.
Some asks for anyone that can repro:

Share information on your profile (screenshots of that configuration) and perhaps a video demo'ing the issue to help me catch what I may be missing.
Running https://github.com/microsoft/vscode-bisect to narrow down this behavior to a single VS Code commit, so I can take that back to the core VS Code folks

I'm unfortunately not able to repro. I tried creating a new profile (not tweaking any of the settings in the new profile). I then swapped to that profile and ssh'd to a host.
Some asks for anyone that can repro:

Share information on your profile (screenshots of that configuration) and perhaps a video demo'ing the issue to help me catch what I may be missing.
Running https://github.com/microsoft/vscode-bisect to narrow down this behavior to a single VS Code commit, so I can take that back to the core VS Code folks

Hello, this is one of my profile that I have problem with Remote-SSH. When I was on this profile and I tried to connect to a remote host via ssh  in VSCode, the problem can be reproduced.
https://vscode.dev/profile/github/29935e3ae18f67ccb4e06424003d9578
Let me know if you need any more information

Sorry for the delay and thanks all for the data.  I can indeed repro, I just don't see the crash due to the properties of the host I am SSH'ing to.  I do get prompted each time for the remote platform on 1.95, which is enough to prove the bug

@joshspicer Can you please verify this?

Can some one please verify if this issue got fixed in the following builds
VS Code Build: bc150766acea3bb8ff2dfc6e543ec2b8dc967b10

darwin
darwin-arm64
darwin-universal
win32-arm64
win32-arm64-archive
win32-arm64-user
win32-x64
win32-x64-archive
win32-x64-user

validated from a windows host to a linux remote host.  When using a non-deafult profile I no longer see a prompt on each connection to select the remote platform

Verified from Win11 to remote Ubuntu host. Problem solved. Thank you.


Remove transport client from tests

Description
Transport client has been deprecated and is getting removed in OpenSearch 2.0.  This commit removes all usages of the transport client from tests.
This is split from the PR #1781
Issues Resolved
Part of #1669
Check List

[x] All tests pass
[x] Commits are signed per the DCO using --signoff

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

Do we need to split it up? Easier to track in a single PR to remove deprecation plus all the tests, no?

Do we need to split it up? Easier to track in a single PR to remove deprecation plus all the tests, no?

Ideally yes. However, in this case, the original PR is a bit bigger to review at one go. It's the strategy we are adopting for other similar changes as well (e.g. removal of V_6.x constants).


Fixed race condition for ListenBucketNotification.

If you begin listening to a bucket and upload in rapid succession, you will miss notifications because ListenBucketNotification returns instantly. This is becauseListenBucketNotification returns a chan for reading before the actual GET request starts.
To solve this, I added a semaphore which signals once either a preflight error occurs or after the first request has been accepted by the server.
I would have loved to add a test for this, but I wasn’t sure how to do so since this is a Minio-only feature. The other client methods seem to use AWS S3.

If you begin listening to a bucket and upload in rapid succession, you will miss notifications because ListenBucketNotification returns instantly. This is becauseListenBucketNotification returns a chan for reading before the actual GET request starts.

The channel blocks until any data is written so until GET is successful there is no data for the caller to read where would the events be lost?,  can you provide an example?

Closing this due to age. Please re-open if still relevant.


landing page improvements

Users are suggesting adding some information about buymeacoffee.js usage and why they should use this API wrapper to their project and place that information on the front page.
In addition, I guess we can add the official icon to the landing page @thomasbnt? Aside from the text buymeacoffee.js

Improved and added a description to the landing page at bf64902


[BEAM-5467] [Python Flink VR] Return to docker based execution until process environment is stable.

The situation has gotten worse with the changes from https://github.com/apache/beam/pull/6532. Builds are now timing out and even the single successful build takes longer than the Docker equivalent.
https://builds.apache.org/job/beam_PostCommit_Python_VR_Flink/
I think that there are some basic issues with how the process environment is setup and run though the container boot code that we should fix first.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

Run Python Flink ValidatesRunner

Run Python Flink ValidatesRunner

Thanks @tweise
I am debugging the TFX pipelines and will take a look at it after that.


Is it possible to have a video as the stage via shaders?

Describe your problem here.
I'm running on a version of psych that has shaders, yes. I was wondering if I could import a video as the stage bg to play throughout the song. (Please provide example script if you can, thanks!)
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Not that I'm aware of.

currently, no. videos are just for cutscenes right now, you would have to modify some of the FlxVideo code in haxe to have it work as a sprite


Refactor Service entity type to not have version as an attribute that is separate from the MRN

Currently the MIR has a unique constraint on the combination of version and MRN in the Service entity type, which consequently allows several service entities to have the same MCP MRN, which is a violation of the specification.

In order to not break backwards compatibility for existing services the Service type will continue to have the version field, but for any new services being created it will not be allowed to give this a value.


MAINT: Check name URLs

Currently we don't check anyone's names.inc URLs but we should. This adds a little extension that outputs a generated/_names.rst when using the linkcheck builder.
I see some failures locally with the check so I'll push that first to make sure we see it on CIs, then I'll add another commit to fix them.

@agramfort feel free to merge if you're happy with the URLs. I basically tried to find a personal url; then a current research-group-page url; then a GitHub URL.


Can I use with "local: ." ?

Is it possible to use with local: . in my workflow?
    - uses: actions/checkout@v2
    - uses: horochx/deploy-via-scp@master
      with:
        local: .
        remote: /home/${{ secrets.PRD_USERNAME }}/folder/
        host: ${{ secrets.PRD_HOST }}
        port: ${{ secrets.PRD_SSH_PORT }}
        user: ${{ secrets.PRD_USERNAME }}
        key: ${{ secrets.PRD_PRIVATE_KEY }}

I got an error and I'm not sure if this is possible.

Just use ./* instead of .,  here is an example: https://github.com/horochx/deploy-via-scp/blob/master/.github/workflows/main.yml#L20

@horochx Thanks!


400x0 is resulting in a empty response

First of all, thanks for all the effort in this project and especially in the new update 4.2.
Unfortunately one thing from the Pull Request #130  of rpong is still not working. If I only set one size and leave the other '0', then the response is empty.

Thanks for your input, @OBrown92
I've seen the Thumbor manual regarding image resize, and resize needs to be improved definitely.
We would improve this one at the next release.

Thanks for your input, @OBrown92
I've seen the Thumbor manual regarding image resize, and resize needs to be improved definitely.
We would improve this one at the next release.

@beomseoklee any idea when the next release will be? We are also seeing this issue and working on a temporary fix.

@OBrown92 and @sniprmonk4
This is the beta version AWS CloudFormation template of the next release.
https://solutions-features-reference.s3.amazonaws.com/serverless-image-handler/v4.2.1-beta.1/serverless-image-handler.template
This beta release fixes 2 issues:

The solution can support 0 resize value (e.g. 0x300, 300x0, 0x0).
As Thumbor's default resizing algorithm is crop, I've changed the default resizing algorithm to crop, which is cover by default in Sharp, for the Thumbor style URL.

Once again that is beta version to fix only this issue, I would recommend testing the feature first prior to adapting this one to your environment.
I hope this would help you.

@OBrown92
Thanks for waiting. This one is fixed in v5.0.0.


Linter incorrectly detecting manual provider

Describe the bug
I'm 100% using generated providers. However, with the latest update, the linter is warning for specific providers:
Generated providers should only depend on other generated providers. Failing to do so may break rules such as "provider_dependencies".

To Reproduce
@Riverpod(keepAlive: true)
class LaunchDarkly extends _$LaunchDarkly {
  @override
  LDClient? build() {
    return null;
  }

  void set(LDClient? client) {
    state = client;
  }
}

@riverpod
class AdministerExamFlag extends _$AdministerExamFlag {
  @override
  bool build() {
    var client = ref.watch(launchDarklyProvider);
    return false;
  }
}

It's flagging var client = ref.watch(launchDarklyProvider);.  My guess is that the linter isn't correctly detecting @Riverpod() annotations vs @riverpod annotations?
Expected behavior
Shouldn't be flagging this.

Try pressing alt in VScode and hovering a type. Or try opening the generated code.
My guess is that this is the following analyzer bug: https://github.com/dart-lang/sdk/issues/54113

Yeah, looks like doing that helped it go away. Thanks for your response.

Hopefully that issue will be fixed when possible


Only supports 4-byte and 8-byte words

This program can only support 4- and 8-byte words. We need to add documentation specifying as such and change the argument parsing to only allow 4 and 8 for the number of bytes.

Closed by #135


Does not work inside web workers

Importing the transliteration module in the context of a Web Worker does not work as expected.
  self.importScripts('/js/libs/transliteration.min.js');
  var t = transl("This line throws error");

I believe this has to do with the fact that there is no window object defined in the web worker context.

Hi @glueball,
Thanks for using the module, it's been fixed in v1.1.15. Let me know if there's still any issues.
Cheers


✨ Add a flag for work agent to set raw json length

Summary
Related issue(s)
Fixes #

LGTM

/lgtm


Support for Samsung Q60 range ?

Dear,
does anyone know if Samsungctl supports the 2019 version of the Q60R range of televisions?
(eg. QE65Q60RAL)
I've been trying to get it working from a Raspberry Pi, but without any luck, so far.
Next thing I'll try is to install the develop version and run the scan program.
But it would help knowing if the Q60R range is supported or not.
Thanks,
Patrick.

@LagaV  - Which package are you using in HASS and what is your config ?


list index out of range

C:\Temp>python -m fluke_28x_dmm_util -p COM6
Traceback (most recent call last):
  File "C:\Program Files\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Program Files\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\Thomas\AppData\Roaming\Python\Python310\site-packages\fluke_28x_dmm_util\__main__.py", line 16, in <module>
    cli()
  File "C:\Users\Thomas\AppData\Roaming\Python\Python310\site-packages\fluke_28x_dmm_util\__main__.py", line 13, in cli
    dmm_util.main()
  File "C:\Users\Thomas\AppData\Roaming\Python\Python310\site-packages\fluke_28x_dmm_util\dmm_util.py", line 627, in main
    match args.command[0]:
IndexError: list index out of range

This has already been solved.
You'll find it in next commit.
I hope this week. I'm currently working on the timeout issue which in my mind is the most important issue.

Should be solved in commit c92b1b1


RTL Support

I am trying to make it RTL but I am unable to do it. Does this have support for RTL?

It doesn't have RTL Support but with this npm rtl package you simply can wrap your text.
check it out.


Change the generator script to kube_codegen.sh

As https://github.com/volcano-sh/apis/issues/133 suggested, try to fix the current code generator issue by replacing the current codegen script with kube_codegen.sh.
It appears that the change has introduced a set of Apply methods, please confirm if this is as expected :)

All the new generated files should have a header of year 2024, maybe you can modify the template file hack/boilerplate.go.txt to achieve this.

All the new generated files should have a header of year 2024, maybe you can modify the template file hack/boilerplate.go.txt to achieve this.

Done.

I found another problem, if we change the year to 2024, the original files that already have year will also change to 2024, which is unacceptable, and according to the issue https://github.com/kubernetes/gengo/issues/24, we can directly remove the year field in license header template.

I found another problem, if we change the year to 2024, the original files that already have year will also change to 2024, which is unacceptable, and according to the issue kubernetes/gengo#24, we can directly remove the year field in license header template.

Done.

/lgtm


remove private websites

#357
Solves task number one. @scripthunter7 Could you please double-check if I missed something? This is time consuming and not high priority, so it's not that important though. I tried to find as many as I can.
note: I'll create a new txt for these rules (task 2) once this gets merged, or let me know if that's too early or you have something else in mind.

@ehrhardt06

Could you please double-check if I missed something?

At fist glance, seems ok

I'll create a new txt for these rules (task 2) once this gets merged, or let me know if that's too early or you have something else in mind.

Later please. Perhaps it would be worthwhile to create the new section after the introduction of the new compiler, as I plan to modify the sections with the preprocessor directives


grammar/typo fixes and wording improvements

yes
Got lazy after nginx.html and only fixed spelling, not grammar/wording, will probably do those later
didn't know if i should've put myself down as a contributor so i just didnt

yeah same what


feat(ts2.0): Migrate to typescript 2.0

Build error is because we first need to release a new version of stryker-karma-runner. The module integration test is depended on it.

So far it looks good to me. I still have to update the README to show the new mutators, or shall we just post them on the website once we release a new Stryker version?
I think it's a good idea to use a proper project to see if we generate the same mutants (or at least get the same score and amount of generated mutants). We could use the Juice Shop by @bkimminich.

Sounds good to me! A sanity check on the juice shop is a good idea. I'll do it tomorrow.
Did the mutators change much? Indeed just update once its merged and released.
Oh yeah, typescript 2 is awesome :)

Woot! Now that https://github.com/bkimminich/juice-shop is the almost-official-migration-guinea-pig of Stryker, I can offer to trade some Juice Shop stickers for a Stryker-T-Shirt with you guys! :grinning:

@bkimminich Of course you can! And you most certainly deserve a T-shirt  :smile:. Please send me a PM on twitter (@_nicojs) or an email with the details.


dodecagonal, estragon

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 1
deps=[d,e]

/trunk merge


Update aws sdk version to allow for new regions

The aws-java-sdk-bom version is currently 1.11.63, which means that the com/amazonaws/partitions/endpoints.json file from aws-java-sdk-core only has 4 regions, but there are a whole lot more available now.  Could you update to 1.11.114 or greater so that the other regions are included too.  (pom.xml:157)

+1
Please update this plugin to support more regions.

Update to 1.11.123. Thanks for catching this.


Cocoapods update

Please do new release and update cocoapods to point at latest release. pods version is 3.1.0 from 2016

Up

thank you! you rock!

Bump, as the latest version in https://cocoapods.org/pods/AFNetworking is still 3.1, while the 3.2 release on this repo was released on Friday, December 15, 2017 (4 days ago).
Is there a reason the pod trunk push has not been done yet?

pod 'AFNetworking', :git => 'https://github.com/AFNetworking/AFNetworking.git', :tag => '3.2.0'

Arf, I didn't notice until now that you moved your "3.2.0" tag -_-. Normally you should have made it a "3.2.1" instead, @SlaunchaMan .


How can I set the ring tone when SIP JS can't receive the freeswitch? I tried many methods, but they couldn't do it

These are typically directed to the google group.
rel100:SIP.C.supported.SUPPORTED have No effect

As you mention, this belongs on the google group. Logs would help when you post there (in a gist).


[WIP] internal: Refactor to nimbus

:house: Internal
This PR is a WIP for moving build configuration to nimbus, which is a soon-to-be open-sourced shareable build config for jest, babel, eslint, prettier, and typescript. This will help

eliminate duplicate configs across individual packages
move config to the root for consistency and easier upgrades
enable easier support for typescript in the future 😉

I will enumerate the changes as the PR evolves below, will try and convert a package at a time, I think the first couple were the hardest.
Changes (dev)

Use babel not rollup
Use yarn not npm

this will enable workspaces so that we can push all config to the root instead of duplicating across every package as is the case now

Stricter linting rules (e.g., .jsx required for React files)

Changes (consumers)

[breaking] Deprecate build/ and dist/, use lib/ and esm/

General TODO

[x] point to open-source libs when published
[x] update docs
[x] verify all package changes functionally with demo

Packages to convert

[x] root
[x] vx-annotation
[x] vx-axis
[x] vx-bounds
[x] vx-brush
[x] vx-curve
[x] vx-event
[x] vx-gradient
[x] vx-heatmap
[x] vx-marker
[x] vx-pattern
[x] vx-scale
[x] vx-text
[x] vx-voronoi
[x] vx-chord
[ ] vx-demo
[x] vx-geo
[x] vx-tooltip
[x] vx-group
[x] vx-boxplot
[x] vx-drag
[x] vx-clip-path
[x] vx-network
[x] vx-legend
[x] vx-glyph
[x] vx-stats
[x] vx-responsive
[x] vx-threshold
[x] vx-shape
[x] vx-point
[x] vx-mock-data
[x] vx-hierarchy
[x] vx-grid
[x] vx-zoom
[x] vx-vx

@hshoff @milesj @schillerk @techniq @kristw

wowza build passed 🚀😱
coverage seems like it is quite high, but consistent with the local coverage report 🤔

also upgraded to next@9 because it wasn't transpiling certain react syntax (e.g., <></>) anymore. may have been an invalid .babelrc format for babel@7.
now broke the babel build 🙉

@hshoff @milesj I think this is ready to go if you think the travis.yml and package.json changes look good 🚀 The rest is a lot of linting and file name changes.
We should test out some alpha releases before doing another patch bump. Because of the breaking changes we could also consider a 0.1.0 release 🤔

@hshoff any thoughts on the license compliance fail? it looks like it's flagging next, not sure if that's an issue if it's for the demo package?

The demos are failing on Travis, but its not failing the build.

enabled next and fixed merge conflicts.


Pangolin Avalanche QA

Review Info

Description
Info

Subgraph Reviewed
https://subgraphs.messari.io/subgraph?endpoint=robinbernon/pangolin

Schema Version
1.3.0

Subgraph Version
1.0.0

Methodology Version
1.0.0

Evidence Spreadsheet
https://docs.google.com/spreadsheets/d/1e52e4S1j7lXa9D4CoHTe5uC-6Mxy0MNQ/edit?usp=sharing&ouid=104027705798814439445&rtpof=true&sd=true

Metric to Review
Revenue
Daily Volume Data
This is not necessarily a data error, but in the past seven days, the volume data from October 11 and 13 have discrepancies of more than 10%.

Subgraph's Daily Volume data for Oct. 13
Official Website
Absolute Difference
% Difference

1,522,883.40
4,342,366
-2,819,483
-64.93%

Subgraph's Daily Volume data for Oct. 11
Official Website
Absolute Difference
% Difference

1,533,777.39
1,928,922
-395,145
-20.49%

Refer to the sheet 'Protocol'

Total Pool Count

As compared to subgraph's 3,214 pools, official website and Dexscreener only show 100 and 234 pools respectively.

Editorials
There are some errors we have noticed and are not necessarily data errors.
Pool Overview

The pool overview section cannot be accessed and it is displaying some issues as it says 'Failed to fetch'
Refer to the sheet 'Pool_Overview'

Pool

The subgraph query is not working no matter how many times the page is being refreshed.
Refer to the sheet 'Pool_vault_schema' and 'Pool_snapshots'

Events

The subgraph is not showing any data and only shows black screen.
Refer to the sheet 'Events'

Please refer to the attached worksheet for details.

Working on getting the Pool Overview and Pool pages working on the validation dashboard and will then QA them myself

this is good to go


fix: Correct inverted icons for "Body battery" and "Stress level"

Swapped the "Body battery" and "Stress level" icons to ensure they are correctly displayed.
This resolves the confusion caused by the icons being inverted in the UI.

I'll be adding a different icon for body battery and then it can be switched with the stess level to better fit in with garmins icons. I'm not too happy with the current stress level icon anyway :)