Hive cli schema:publish unable to publish schemas to a federated project when --url has no protocol

yarn hive schema:publish ./schema.graphql --url /my-service/graphql --service my-service
The latest hive-cli fails with the following error when publishing to a Federated project. This worked previously for me.
✖ Missing service url Please use the '--url ' parameter.
It works if we switch the --url to include a protocol.
yarn hive schema:publish ./schema.graphql --url https://my-service/graphql --service my-service
When a build service function is implemented in the gateway, publishing without a protocol is helpful, as this can be set later via an environmental variable.
Thank! and please reach out if I can assist in anyway.

Hi @alanquigley-toast
We've recently fixed a bug with the schema validation checks, and introduced a validation for the URL. So now the published URL from the Hive CLI must be a fully valid URL.
The URL published must be valid because otherwise it will results in a broken Supergraph for Apollo Gateway.

That makes sense; we implemented our solution https://www.apollographql.com/docs/apollo-server/using-federation/api/apollo-gateway/#the-buildservice-function. Where we build the URL based on the ENV variables. But supporting a more rigid URL pattern is an easy refactor.

@alanquigley-toast has your issue been addressed and fixed by @dotansimha 's response?
If so, please close this issue as fixed.
If you do have any other issues, don't hesitate to create a new issue.
Thanks for trying out GraphQL Hive


[RFE] Refactor AccessStore key hashing

Is your feature request related to a problem? Please describe.
I noticed while working on #47318 that the key of the cache is calculated based on the status of the rules, which are later fetched separately in the case of a cache miss.
This is enough for the happy path, but it could be a problem if the cache changes in between (e.g. if any of the involved resources changes), ending up caching an incorrect value.
Describe the solution you'd like
The key/hash should be calculated on the same payload later being used to generate AccessSets.
Describe alternatives you've considered
N/A
Additional context

This is additional work on top of #47318 so closing this issue in favor of that one for testing purposes.


How can I pass a custom User Agent string through this crawler?

How can I pass a custom User Agent string through this crawler? I know it's using request under the hood, but just curious what the proper way to do this is?

new crawler({
    userAgent: 'your user agent string'
});

new crawler({
    userAgent: 'your user agent string'
});


Upload files in chunks

Adds function for uploading a file in chunks as described on https://www.mediawiki.org/wiki/API:Upload#Example_3:_Upload_file_in_chunks. The chunks are created as temporary files and are removed once uploaded.
For #4303

Replaced by #6510.


mat.GetArray always throws an exception.

Summary of your issue
mat.GetArray always throws an exception.
Environment
win8.1 64bit
opencvsharp (<IP_ADDRESS>00421)
vs2019 .net core 3.1
Example code:

            // test.jpg 608x608x3=1108992
            var imageFile = Path.Combine(BaseDir, "test.jpg");
            var mat1 = new Mat(imageFile);
            var mat2 = new Bitmap(imageFile).ToMat();
            //mat1.GetArray<byte>(out byte[] data);
            mat2.GetArray<byte>(out byte[] data);

Output:

Unhandled exception. OpenCvSharp.OpenCvSharpException: Provided data element num
ber (369664) should be multiple of the Mat channels count (3)
   at OpenCvSharp.Mat.CheckArgumentsForConvert[T](Array data)
   at OpenCvSharp.Mat.GetArray[T](T[]& data)

What did you intend to be?
read an image and conver it to tensor,
the code looks like below,
but performance is too low.
maybe with some extra preprocessing.
finally  the type of  float[] is expected.
public unsafe static byte[] ToTensor(BitmapData bmData)
        {
            // params
            int width = bmData.Width, height = bmData.Height, stride = bmData.Stride;
            byte* p = (byte*)bmData.Scan0.ToPointer();
            byte[] t = new byte[3 * height * width];
            int pos = 0;

            // do job
            for (int j = 0; j < height; j++)
            {
                int k, jstride = j * stride;

                for (int i = 0; i < width; i++)
                {
                    k = jstride + i * 3;

                    t[pos++] = p[k + 2];
                    t[pos++] = p[k + 1];
                    t[pos++] = p[k + 0];
                }
            }

            return t;
        }

Since the mat is a color image, you need to write the following
var mat1 = new Mat(imageFile);
mat1.GetArray<Vec3b>(out var pixels);

If you need a byte array output, you can use Unsafe, fixed, or GCHandle to copy Vec3b array to byte array.
ref var bytes = ref Unsafe.As<Vec3b, byte>(ref pixels[0]);
var dst = new byte[pixels.Length * 3];
Unsafe.CopyBlock(ref dst[0], ref bytes, (uint)dst.Length);

unsafe
{
    fixed (Vec3b* dst3b = &pixels[0])
    {
        byte* dst = (byte*) dst3b;
        ...
    }
}

@shimat
opencvsharp is great.
thanks for for your efforts !
actually I want to do inference using onnx model.
the input should be a tensor of type  float[]  with some preprocessing.
how to perform color normalize using opencvsharp ?
python code looks like below , src /mean/std is numpy ndarray
def color_normalize(src, mean=np.array([0.485, 0.456, 0.406]), std=np.array([0.229, 0.224, 0.225])):
    """Normalize src with mean and std"""
    src -= mean
    src /= std
    return src

then convert to float[] after color normalize .
now I'm a little new to opencvsharp.
would you like to give some more details about this ?
thanks!


Date is always January 19

All transcripts have the month as January and the incorrect day and time.

Thank you for reporting, @SSSTREDDD. I will have a look at this. Could you verify that all dates on the right side are correct?
Could you download the latest release of this custom visual here and add this to the report? It seems that you are using the Custom Analytics report and this is not using the latest version yet.

That's a good observation, this would definitely be the same issue, however the screenshot is from an early release version. 😀. I will investigate this!
Which channel are you using on Power Virtual Agents? (e.g. WebChat / Teams / Omnichannel)

@SSSTREDDD, could you give https://github.com/iMicknl/powerbi-botframework-chat-transcripts/suites/3826403466/artifacts/94732656 a try? This beta build is generated by the pipeline of https://github.com/iMicknl/powerbi-botframework-chat-transcripts/pull/73.
Do you have any specific requests? Like specifying a custom date time format, or adapting the date time to a time zone. It would be good to learn more about how this is used and what is currently lacking.

@SSSTREDDD this should be fixed in 0.8.0, https://github.com/iMicknl/powerbi-botframework-chat-transcripts/releases.
If you have any other specific requests, e.g. specifying a custom date time format (24h?) or adapting the date time to a time zone, let me know.

@iMicknl Missed your messages. Thank you for looking into this! I will apply and test when I can. Thanks again.

SSSTREDDD this should be fixed in 0.8.0, https://github.com/iMicknl/powerbi-botframework-chat-transcripts/releases.
If you have any other specific requests, e.g. specifying a custom date time format (24h?) or adapting the date time to a time zone, let me know.

Thank you, this was indeed fixed in 0.8.0. (I work with SSSTREDDD)
There are some other display issues in relation to time that I would like to see changed:

As you've mentioned, adapting the date/time to the local time zone is beneficial, as the time/date in the transcript doesn't match the conversation date field in the table from CDS:

The other display issue I am seeing is that the transcript viewer shows "Yesterday" as the timestamp when the conversation time is actually 2 days ago, due to the time zone issue. I prefer to see the actual timestamp of messages sent/received, instead of simply "Yesterday".
The following image shows my system time, along with the conversation time in the table (2 day difference) yet displaying Yesterday in the transcript viewer.

Could you perhaps create a new issue for your feature request? (or even split per feature).
Regarding your time issue, there was an issue with the Custom Analytics report that you use, where the Conversation date listed in the table wasn't the correct date. You can temporary download the version from here: https://github.com/microsoft/PowerVirtualAgentsSamples/pull/64, to test if this solves your issue around time mismatch.


fix(cli): env file load for commands with subcommands

Closes #2735

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


Fix documentation favicon, avatar image and background pattern.

Fixes PR #49
Preview:

Love the addition of the favicon and the transparent Mutato image in the docs, nice touch!


Fix broken "Resource communication" page

Issue #179
The page was broken because of "Exports".
Because of this title an element gets created with the id "exports" which breaks the whole highlight.js code.
Also renamed "Imports" so it stays similiar.

Thanks alot 👍


feat: use n-bit mux for switching PLONK verification keys

Description
This PR changes the mux from Lookup2 to selector.Mux which allows arbitrary switching. The change is backwards compatible (previously we threw an error if had more than 4 keys).
Fixes #966
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How has this been tested?

[x] TestMux for non-native elements
[x] TestMux for G1 elements (native and 2-chains)
[x] Implemented PLONK aggregate verification with 5 keys instead of four.

How has this been benchmarked?
PLONK recursion over 10 proofs increase from 313833 to 314402.
Checklist:

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I did not modify files generated from templates
[x] golangci-lint does not output errors locally
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@gbotrel - included you for review as I'm doing some reflect stuff to switch over all fields in verification key.

high level tests looks decent to me, not sure about the specifics of the f.enforceWidthConditional and normalize each time I read emulated package I'm confused as to when to / when not to use them TBH.

Regarding f.enforceWidthConditional - it is essentially to assert that witness limbs are in range. If it is already constrained the it is no-op, otherwise we range check.
I need normalize, as the the inputs may have different number of limbs or overflow. So the result needs to be with maximum number of limbs and overflow for further correct computations. I only need to use normalize for Select, Lookup2 and Mux.


Update RxSwift in .podspec to ~>5.1.0

Hello, where do you plan to update Moya with updated RxSwift version to which uses deprecated UIWebView.
https://developer.apple.com/news/?id=12232019b
https://github.com/ReactiveX/RxSwift/releases/tag/5.1.0

Hey @dimpiax - please take a look at https://github.com/Moya/Moya/issues/2003, we should be already supporting RxSwift 5.1 and above. Running pod update should help (and update to 5.1.0 if you don't have any other version pinning set-up) but let me know if you need any more guidance.

@sunshinejr all right then, thanks.

woooh woke up on a nightmare man
one of my apps for a big client just got rejected because of that
just updated to 5.1 and it works


Add zoom feature?

Love this tool. Thank you very much for making it. I think you have a great start but one thing that I think would be great is to have some kind of zoom capability.

@rsimon's https://github.com/recogito/annotorious/issues/121#issuecomment-866014041 suggests implementing zoom by means of a magnifying lens on the cursor. Cool!
I wanted to add a second interpretation of "zoom" that could be valuable. This would be the ability to scale the rendering of the image up (or down, in fact) past its natural px size, without affecting the annotation functionality.
Something like https://jsfiddle.net/hfm97pw8/1/. The annotation layer doesn't quite do the right thing when encountering an image scaled with CSS.
I imagine this might be problematic to achieve, the magnifying lens would still be amazing on its own.

Good point - yes, this could also achieve zooming. FWIW: you can make the annotation layer adjust to the size of a zoomed image with a little CSS + HTML trickery. This would work, for example:

In general, the trick is always to wrap the image in a DIV and apply all the styles to the DIV rather than the image.


Remove confusion of the MapService's methods names

Make a clear difference between geodesic-related and projected-related methods.

Resolved by #1626


Cannot get direct messages from one user

Describe the bug
I cannot see direct messages sent to one of the users (see screenshot 'missing_direct_messages.jpg'). I can see the same messages in desktop client (MS Windows) without problems.
I am not sure if this is related but I cannot see mobile client / server version (see 'settings_missing_version.jpg').
To Reproduce
It happened with direct messages to one user only so I cannot reproduce it easily.
Expected behavior
I should be able to the same messages as in desktop application.
Screenshots
See attachments:

Devices and Versions
Your Rocket.Chat.Android version: 3.4.1
Your Rocket.Chat Server version: 1.0.3
Issue occurs:
Mobile device model and OS version: Samsung Galaxy S9 (SM-960F) - Android 9
Issue does not occur:
Rocket Chat desktop app for MS Windows: 2.15.3
Additional context
Reinstalling mobile client / removing stored data does not help

Same for one of my users.
But he can't do anything, he doesn't see any chats or can logout of the server.
A reconnect to the server skips the login.
Reinstalling also does not help.
For now he uses the experimental version.
Devices and Versions
Your Rocket.Chat.Android version: 3.4.1
Your Rocket.Chat Server version: 1.0.3
Issue occurs:
Mobile device model and OS version: Samsung J5 - Android 8.1

Same here with v3.4.1

How to get the experimental version?
The latest one I can see on Github is 3.4.1:
https://github.com/RocketChat/Rocket.Chat.Android/releases
pon., 20 maj 2019, 21:05 użytkownik Vlad<EMAIL_ADDRESS>napisał:

Same here with v3.4.1
—
You are receiving this because you authored the thread.


Refactor and add tests

This change cleans up the main package somewhat, by refactoring to eliminate globals, remove unused types, and make function dependencies explicit. This makes it easier to use this tool as a library. Also made an "expired" state distinct from "expiring" and fixed the logic for that.
Added tests for check() function.

@paulsmith can you rebase against master?

@cgansen ok, rebased, PTAL.


feat!: rewrite to TS and adjust to the v2 ParserJS

Description

Rewrite to TS.
Adjust exported module to the new v2 ParserJS Custom Schema Parser interface - new validate() function.
Improve testing and move to the Jest.
Update Readme.
Add @magicmatatjahu to the codeowners.

Related issue(s)
Resolves https://github.com/asyncapi/openapi-schema-parser/issues/140

@magicmatatjahu I think using next-major as target branch its a better approach, so this can be merged and released as beta first.

I have same question as https://github.com/asyncapi/avro-schema-parser/pull/168#pullrequestreview-1171929231, but this PR is a bit different and points to master directly. Should we really release it as major and automatically bump it in generator?

@derberg

Should we really release it as major and automatically bump it in generator?

We will but it doesn't work with parser in generator. In this PR I made integration https://github.com/asyncapi/generator/pull/833 but I'm fighting with snapshots 😆

but this PR is a bit different and points to master directly.

Yeah, because I didn't have next-major in this repo :)

relevant

@fmvilas @derberg can any of you create the next-major branch? I want to move forward with this PR. Once is done, @magicmatatjahu would u mind changing the base branch and update it?
Thanks

@fmvilas @derberg please approve when you have a chance. Last change was just the fix on dependencies


problem running AlphaCUtter

AlphaCutter.zip
This is the directory I have, and I cannot run it.

Could you please share the error messages?


Update Configurations View to support subdirectories

Including operations of

new
refresh
clone
delete
rename

Do we need to even do this?


[SuperEditor] Create IME visualizer (Resolves #1120)

[SuperEditor] Create IME visualizer. Resolves #1120.
This PR is a starting point for #1120.
This PR introduces a TextInputDebugger class, which collects events related to text input. It collects events about call to updateEditingValueWithDeltas, performAction, setEditingState and key events.
We could also introduce a SuperEditorDebugTools class which can hold debuggers for other areas, for example, commands, requests, etc.
https://github.com/superlistapp/super_editor/assets/7597082/18a24ffc-08d7-4f6c-8bcb-9042de60bdc0

Let's start with the UX. I think we definitely want to reduce the default amount of information shown. We can include small icons on each list item to expand deeper areas of info about each item in the list, but I think we should only show the minimal relevant info for each item.
We can include a small toolbar at the top. That toolbar can include buttons to expand a type of information for all list items, or collapse that information. We can also move that "clear" button into an icon in that toolbar at the top. I'd also like to see the total number of logged events in the toolbar, too.
Looking at the video, I don't know what the up and down arrows mean on the left.
Also, I'm not sure if this is happening or not, but can we mark divisions between group of deltas so that we know what we got in a single batch?
From a brightness standpoint, let's make those whole panel dark to help communicate that it's a developer tool and not part of the editor.

@matthew-carroll  Updated.

Looking at the video, I don't know what the up and down arrows mean on the left.

The key pointing down means it's an event generated by Flutter, e.g, a key event or a delta. The arrow pointing up means it's an event we generated, like a call to setEditingState.

Also, I'm not sure if this is happening or not, but can we mark divisions between group of deltas so that we know what we got in a single batch?

If we get multiple deltas in the same batch, we will see one expansion tile for the updateEditingStateWithDeltas call and each delta is displayed when the tile is expanded.
https://github.com/superlistapp/super_editor/assets/7597082/c1b85bb8-ba2c-4b56-802e-eb6528f8ed2f


Accessing Current Slide Attributes in onAfterChange after 1.4 update

Previous method which was working before the update:
console.log($(slide.$slides.get(index)).attr('id'))
No longer works. Any suggestions as to how I might make this happen? Based on docs, I tried to pull .data() from
var currentSlide = $('.your-element').slick('slickCurrentSlide');
but that didn't work either.

var cur = $(".slider").slick("slickCurrentSlide");
var $slides = $(".slider").slick("getSlick").$slides;
var id = $slides.eq( cur ).get(0).id;

Thanks for contributing, but please provide a jsfiddle in future :smile:

Doesn't work. Fiddle: http://jsfiddle.net/fpbgbgrd/

Yes. It Does.
http://jsfiddle.net/3b4kqy9p/

@kenwheeler Thanks for taking a look. I'm trying to return data attributes from the current slide though, what you've shown only gives me the current slide as an integer.
If I try  $('.get-the-title').text(currentSlide).data('title');
then that doesn't work.

@heytomsmith ... the code I gave you should have been enough for you to get this working, which is why the issue was closed :smile:
http://jsfiddle.net/3b4kqy9p/2/
If you ever find you dont understand something it's perfectly OK to ask for help! :grinning: , but for future reference you should really only be raising tickets on github if you're absolutely certain there's a problem and you can prove it... otherwise please head to stackoverflow.com and ask your questions there, there's thousands of people to help you :)
Simon.

Ok thanks, Simon. I'll do that in the future. I'm still learning :sweat:. Thank you both for your help @kenwheeler.


Implement support for Tensorflow-based models

Create pipeline for neural net

The branch for using Neural Networks is in development but it couldn't be finished before the deadline of the kaggle challenge.
--> Closed


Performance/RedundantMerge Auto-Correction Issue

Was running the last version of the rubocop code with ruby 2.3.0 and got the following auto-correction:
-      event.merge!('$first_name' => sba.name, '$last_name' => sba.surname) if store && sba
+      event['$first_name'] = sba.name
+      event['$last_name'] = sba.surname if store && sba

The if should go around both lines, instead of only the last one.

Nice catch!

I have a fix for this. Waiting for my open PR to be merged before I open another.

If there is a fix that is going to be merged for me the issue can be closed.
Thanks in advance :)

It will be closed soon. :smile:


Clean up document names on the UI by removing dataset prefix

Is your feature request related to a problem?
Currently, document names on the UI are prefixed with the name of the dataset (e.g., wiki_animals_2000_pages-Acanthobrama telavivensis, where wiki_animals_200_pages is the dataset name and Acanthobrama telavivensis is the actual document name). I think that this makes the document names harder to read, as (a) they become long and (b) one has to always read and ignore the dataset name before getting to the actual name of the document.
What is the expected behavior?
To make document names easier to read, I think that it would help to remove the dataset name prefix from them. If we want to still display the dataset name on the UI, in a discussion I had with @martinscooper, he suggested displaying the dataset name on the left panel under the workspace name. Since the dataset is a property of a workspace, I agree that seems to be the natural location for it.
What do you think?

I agree. Sounds like we should do these two changes together (remove from the document id and move to the left panel)


How to run git submodule update --init within Docker container

I am using dal with Django 1.11. My deployment environment is Divio cloud.
However, I hadn't pinned dal down to my requirements.in file, therefore when I tried to rebuild the project it failed due to a reference of the new version (>3.3.0-rc6) to code that only exists in django 2:
from django.contrib.admin.widgets import SELECT_2_TRANSLATIONS
When I try to roll back to a previous version of dal adding into my requirements.in file the following:
https://github.com/yourlabs/django-autocomplete-light/archive/3.3.0-rc6.zip#egg=django-autocomplete-light
... I get an error due to submodules not included automatically for archive versions as also mentioned in the docs at the Note section.
In my deployment environment I am working within a Docker container. What would be the correct way of dealing with this issue? i.e. how to run git submodule update --init within the Docker container? I failed doing it via the bash:
root@xxxxx:/app# git -C /virtualenv/lib/python2.7/site-packages/dal submodule update --init fatal: Not a git repository (or any of the parent directories): .git
I had to resort to locally cloning dal, then checking out version 3.3.0-rc6, then running git submodule update --init and then copying this into my own project's django apps. It works, but it's not pretty.

Did you try pip install -e instead of copying files to your project ?

Hi @jpic ,
I could not explicitly do pip install -e due to working with pip-tools. I can only specify dependencies inside a requirements.in file.

I don't think 3.3.0 is really compatible with Django 1.11 but pull requests are welcome.
3.3.0 relies on django.contrib.admin vendorizing of select2 in django 2

Indeed, that is why I am trying to roll back to tag 3.3.0-rc6 which still works for django 1.11

So, did you try with a regular pip install of 3.3.0-rc6  ?


Refactor guide

Transfer to use reactour pkg from byte-guide, which has better support on page resizing.
BUG Fix: share audio play button sometimes wrongly get sticked to pause state.
[Memory Leak] add ffmpeg woker terminate logic to avoid memory leak.

directly closing the guide with esc can still cause .terminate method being used. -> runtime errors


new branch with @only1chunts' xlsx updates, to be merged into main

https://github.com/only1chunts/mixs-cih-fork/raw/main/mixs/excel/mixs_v6.xlsx

The 6.1 release's XLSX file is https://github.com/GenomicsStandardsConsortium/mixs/raw/main/mixs/excel/mixs_v6.xlsx

The 6.1 release's XLSX file is https://github.com/GenomicsStandardsConsortium/mixs/raw/main/mixs/excel/mixs_v6.xlsx

I made the brach but then just barged ahead and merged @only1chunts work into main (once the build process completed.)


Pass through default tls-cipher-suites

Proposed Changes
Pass through default tls-cipher-suites to kube-apiserver
Types of Changes
feature request
Verification
Check reported flags passed to kube-apiserver
Testing

Linked Issues

https://github.com/k3s-io/k3s/issues/6724

User-Facing Change

The K3s default cipher suites are now explicitly passed in to kube-apiserver, ensuring that all listeners use these values.

Further Comments

Codecov Report
Base: 9.67% // Head: 9.66% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (facbc52) compared to base (a298bfd).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##           master   #6725      +/-   ##
=========================================
- Coverage    9.67%   9.66%   -0.01%
=========================================
  Files         139     139
  Lines       10227   10228       +1
=========================================
  Hits          989     989
- Misses       9034    9035       +1
  Partials      204     204

Flag
Coverage Δ

unittests
9.66% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/cli/server/server.go
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Can you open a Docs PR that adds the new arguments to https://docs.k3s.io/security/hardening-guide#control-plane-execution-and-arguments please?

@dereknola do you have a suggestion on how to cover this in the docs? We already ship with hardened defaults so this isn't a big change on K3s. This fix is mostly for RKE2 where the apiserver wasn't using these because we weren't passing the defaults through - only the supervisor ports was using the hardened cipher list.

My understanding is that this is largely for a pull-through to RKE2 yeah? looks sane to me

@dereknola do you have a suggestion on how to cover this in the docs? We already ship with hardened defaults so this isn't a big change on K3s. This fix is mostly for RKE2 where the apiserver wasn't using these because we weren't passing the defaults through - only the supervisor ports was using the hardened cipher list.

Iin the docs for hardening, as part of explaining the underlying code, we break out the kubeapiserver arguments K3s automatically passes. We need to at to that with the tls-cipher-suites argument.

@dereknola https://github.com/k3s-io/docs/pull/72


PreviewProps is not a function

Component or Package Name: Preview
Component or Package Version: 1.7.2
@jsxp-email/cli Version?:
Operating System (or Browser): Chrome
Node Version: 20.10.0
Link to reproduction (⚠ read below): N/A

Expected Behavior
Using a sample, it should open in the email preview with the defined props in PreviewProps.
Actual Behavior
Preview page is blank, console.log throwing "PreviewProps is not a function" error.
Additional Information
Using any example from the email samples out-of-the-box is not working as most of them have PreviewProps defined. If this is a docs issue, please let me know how to provide template props for previews.

Not sure what you're describing. That url works fine?

I am sorry for not being clear enough. The url is for referencing the samples that are not working locally.
If I copy the code from that sample page, for example the Airbnb-review, and use it as it is in my local dev environment, it is not working.
AirbnbReviewEmail.PreviewProps = {   authorName: 'Joker',   authorImage: ${baseUrl}batman-twilight.jpg,   reviewText: "Batsy's stay at my Airbnb Batcave was a riot! Batman surprised with a hidden sense of humor, engaging in epic banter and a prank war. His detective skills impressed, and the Batcave remained spotless. Game night and snacks were a hit, and even during downtime, he couldn't resist a Bat-signal. Hosting Batsy was chaos perfected – if you want a guest with brooding intensity and unexpected laughter, Batman's your Bat. Hahahahahahahahahaha! " } as AirbnbReviewEmailProps;
It seems that the above snippet, the PreviewProps definition is not working locally as it is not recognized. Am I doing something wrong?

Am I doing something wrong?

Probably not :)
Could you put together a reproduction using https://stackblitz.com/edit/jsx-email-repro when you have the chance? I'm not able to reproduce locally, but that doesn't mean your issue doesn't exist. A reproduction will help me see the same code in the same environment as you so that I can debug.

Sure thing, here it is: https://stackblitz.com/edit/jsx-email-repro-vzgqmc

Perfect thanks


Rate Limit

Mastodon is rate limiting

Temporarily decreased schedule from every 1 minute to every 10 minutes.

At roughly ~50-100 active incidents at any given time, only about ~1-10 every minute is actually new.
Previously, we were making 50-100 requests/min to Mastodon.
Now, with an incident Redis cache added in https://github.com/kevinyou/dallas-alerts/commit/b9d97091f9a30c2846328c03db44aac64547d276, this should drop down to 1-10 requests/min to Mastodon, which hopefully should be much more tolerable for Mastodon.
Also dialed the schedule back up to every 1 minute.


mvcc: store.restore taking too long triggering snapshot cycle fix

#5317
@xiang90 Currently i have commented the test cases. Will fix all the test cases and also add the benchmark test case for this in this PR. There are too many test cases dependent on this. Will start fixing them one by one.
Thank you!

Please don't comment out so many tests, it makes the PR difficult to read. Most (e.g., the e2e ones) should work as-is if the fix is good...

@heyitsanthony its still initial phase will be un-commenting all these cases in this PR itself after fixing them all. Or shall i remove all these commented code and keep it as original itself?

@heyitsanthony as you suggested will keep only the changes here. Once the all test cases have been fixed, this PR should automatically pass.

@xiang90 @heyitsanthony PTAL.
Thank you!

Benchmark results:

@sinsharat Do you have the result before this PR?

@xiang90 No i don't have the result. I had done the changes based on you suggestion. If you want will take the benchmark result for the older one.

@xiang90 sure will do it and post the before change PR result here.

@xiang90 The bench test case i had written was not working with old code. So i had to modify the code as below:
st := time.Now()
s = NewStore(be, &lease.FakeLessor{}, &i)
b.Logf("Took %v for restoring %v keys\n", time.Since(st), b.N)

After modifying the bench test, the following were the readings with old and new code:
Old Code:
BenchmarkStoreRestoreRevs10-4             	   50000	     25233 ns/op
--- BENCH: BenchmarkStoreRestoreRevs10-4
	kvstore_bench_test.go:117: Took 43.911ms for restoring 10 keys
	kvstore_bench_test.go:117: Took 67.0137ms for restoring 200 keys
	kvstore_bench_test.go:117: Took 150.127ms for restoring 2000 keys
	kvstore_bench_test.go:117: Took 81.0395ms for restoring 20000 keys
	kvstore_bench_test.go:117: Took 563.2987ms for restoring 200000 keys
	kvstore_bench_test.go:117: Took 1.1537436s for restoring 500000 keys

New Code:
BenchmarkStoreRestoreRevs10-4             	  100000	     17500 ns/op
--- BENCH: BenchmarkStoreRestoreRevs10-4
	kvstore_bench_test.go:117: Took 58.8606ms for restoring 10 keys
	kvstore_bench_test.go:117: Took 93.2865ms for restoring 100 keys
	kvstore_bench_test.go:117: Took 96.471ms for restoring 1000 keys
	kvstore_bench_test.go:117: Took 81.7109ms for restoring 10000 keys
	kvstore_bench_test.go:117: Took 412.4868ms for restoring 100000 keys
	kvstore_bench_test.go:117: Took 566.0508ms for restoring 300000 keys
	kvstore_bench_test.go:117: Took 1.5504294s for restoring 1000000 keys

@sinsharat Can you also try 1 rev per key case?

@xiang90 sure will do it.

@xiang90 Please find below the result for 1 rev per key case:
Old Code:
BenchmarkStoreRestoreRevs1-4              	  200000	      5922 ns/op
--- BENCH: BenchmarkStoreRestoreRevs1-4
	kvstore_bench_test.go:116: Took 43.6651ms for restoring 1 keys
	kvstore_bench_test.go:116: Took 76.5179ms for restoring 10 keys
	kvstore_bench_test.go:116: Took 64.1562ms for restoring 100 keys
	kvstore_bench_test.go:116: Took 138.4179ms for restoring 1000 keys
	kvstore_bench_test.go:116: Took 134.2355ms for restoring 10000 keys
	kvstore_bench_test.go:116: Took 584.6538ms for restoring 100000 keys
	kvstore_bench_test.go:116: Took 1.0278762s for restoring 200000 keys

New Code:
BenchmarkStoreRestoreRevs1-4              	  200000	      5472 ns/op
--- BENCH: BenchmarkStoreRestoreRevs1-4
	kvstore_bench_test.go:116: Took 61.997ms for restoring 1 keys
	kvstore_bench_test.go:116: Took 57.2608ms for restoring 10 keys
	kvstore_bench_test.go:116: Took 66.9507ms for restoring 100 keys
	kvstore_bench_test.go:116: Took 105.1183ms for restoring 1000 keys
	kvstore_bench_test.go:116: Took 119.1674ms for restoring 10000 keys
	kvstore_bench_test.go:116: Took 541.6184ms for restoring 100000 keys
	kvstore_bench_test.go:116: Took 998.8248ms for restoring 200000 keys

@sinsharat OK. I thought 1 rev case should be slower. But it seems that the overhead is minimum.
Does these result make sense to you? I will give this a closer look today or early tomorrow.

@xiang90 yes what i can figure out is that the new code, for smaller number of keys takes slight;y more time, but as the keys to restore grows, the restoration becomes faster than the old code. Also if you see the operation time, overall its quite less for newer code for both 10rev/key(17500 ns/op) and 1rev/key(5472 ns/op) as opposed to older code having10rev/key(25233 ns/op) and 1rev/key(5922 ns/op).

Defer to @heyitsanthony

@xiang90 I have done the changes as per your suggestion. PTAL.
Thank you!

lgtm

@xiang90 Request you to provide feedback on this.
Thank you!


bugfix:github_action单测输出修改

Codecov Report

Merging #361 (78e7913) into v2.6.x_develop (68ac40b) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop     #361   +/-   ##
===============================================
  Coverage           62.76%   62.76%
===============================================
  Files                 441      441
  Lines               26860    26860
===============================================
  Hits                16860    16860
  Misses              10000    10000

Continue to review full report at Codecov.

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


Can't create a DC + Plugin with TTK + Kiota for Github API

What are you generating using Kiota, clients or plugins?
Kiota plugin
In what context or format are you using Kiota?
Source Build
Client library/SDK language
None
Describe the bug
Can't create a DC + Plugin with TTK + Kiota for Github API

Expected behavior
Should generate the plugin
How to reproduce
Create a DC + Plugin from TTK
Select OpenAPI Spec
Search for Github and select first option
Select GET endpoint and click generate
Open API description file
No response
Kiota Version
v1.18.100000001
Latest Kiota version known to work for scenario above?(Not required)
No response
Known Workarounds
No response
Configuration
No response
Debug output
Click to expand log
```
2024-09-11 14:32:33.474 [warning] OpenAPI warning: #/components/responses/actions_runner_labels/content/application~1json/examples/default/value/total_count - Data and type mismatch found.
2024-09-11 14:32:33.474 [warning] OpenAPI warning: #/components/responses/actions_runner_labels_readonly/content/application~1json/examples/default/value/labels/0/id - Data and type mismatch found.
2024-09-11 14:32:33.474 [warning] OpenAPI warning: #/components/responses/actions_runner_labels_readonly/content/application~1json/examples/default/value/labels/1/id - Data and type mismatch found.
2024-09-11 14:32:33.474 [warning] OpenAPI warning: #/components/responses/actions_runner_labels_readonly/content/application~1json/examples/default/value/labels/2/id - Data and type mismatch found.
2024-09-11 14:32:33.474 [warning] OpenAPI warning: #/components/responses/actions_runner_labels_readonly/content/application~1json/examples/default/value/total_count - Data and type mismatch found.
2024-09-11 14:32:33.474 [warning] No paths were found matching the provided patterns. Check your configuration.
2024-09-11 14:32:33.475 [error] error adding the client: The urls in the Postman collection supplied could not be found.
</details>

### Other information

_No response_

Duplicate of https://github.com/microsoft/kiota/issues/5300

@MuyangAmigo, This is fixed in the main branch which should have a new release soon. Follow original issue #5300 for futher details


[Stable] Merge main into stable

@lgalis After checking out this PR and doing a diff against main, there's a ton of files that are different, which is concerning. Not sure why/how that happened, though 😢