Small issue with story and the buttons

A small issue: In a story if you click on the picture: "See post". It goes to the IG post. But the Icons from IDB are at the top next to the name. It doesn't work when you click on download. Refreshing don't solve it.
But if you click on the profile and find the post, it works fine, the icons are at the bottom.

Just take a look, this is caused by the post page html changing.
I will try to fix.


Handshake records larger than max_fragment_length in DTLS 1.2?

We are trying to get a DTLS client to restrict the network packets sent by either end of the connection because the network in question drops with UDP packets over 1400 bytes or so. The server-side also talks to clients on other networks that don't have this issue, so we'd like to make the choice on the client.
To accomplish this, we attempted to SSL_CTX_set_tlsext_max_fragment_length(ctx, TLSEXT_max_fragment_length_1024);  to force both ends to send at most 1024 byte records, which should keep the packet size under control. This succeeded in forcing both sides to send smaller UDP packets, so now the DTLS handshake no longer fails because some packets get dropped.
However, it still doesn't succeed. Instead we are now seeing Record Overflow alert from the client.
After reading RFC 6066 section 4, it's not quite clear to us if this should happen during the handshake. The specification certainly talks about restricted buffer size as one of the motivations for using the extension, but it also talks about fragmentation support in handshake, which made us think that handshake records larger than max_fragment_length would not be an issue.
Is this a bug in OpenSSL, or are we trying to make max_fragment_length do something it wasn't supposed to do?

Are client and server both using OpenSSL?

Only the client is OpenSSL. The server is, I believe, Scandium.

Instead we are now seeing Record Overflow alert from the client.

Do you mean a record overflow alert is sent by the client, or a record overflow is received by the client? If it is sent by the client do you have any OpenSSL error log information detailing the problem further?

Record overflow alert is sent by the client. Here is a screenshot from Wireshark showing the client receiving fragmented records from the server and responding with record overflow alert:

Which OpenSSL version are you using?

We have tested with 1.1.1g and 1.1.1h.

Can you get a packet capture of a failing connection?

We should be able to make a packet capture available later, or perhaps an executable test.

I can't seem to attach pcap files here.

zip file?

Also, it would be very useful to see the error message generated by the client when it sends the alert.

I believe this is the error message (using OpenSSL 1.1.1h in case it matters): "error:14101092:SSL routines:dtls1_process_record:data length too long"
Here is the zipped pcap (I believe this test used OpenSSL 1.1.1g, in case it matters):
dump_dtls_data_length_too_long.zip

This appears to be due to a bug in the server side implementation - potentially because of a misunderstanding about the RFC that specifies this behaviour.
There are in fact 2 different contexts in which the word "fragment" is used in TLS/DTLS - which is quite unfortunate. In TLS it is used in RFC 5246 (TLSv1.2) in section 6.2.1:
6.2.1.  Fragmentation

   The record layer fragments information blocks into TLSPlaintext
   records carrying data in chunks of 2^14 bytes or less.  Client
   message boundaries are not preserved in the record layer (i.e.,
   multiple client messages of the same ContentType MAY be coalesced
   into a single TLSPlaintext record, or a single message MAY be
   fragmented across several records).

      struct {
          uint8 major;
          uint8 minor;
      } ProtocolVersion;

      enum {
          change_cipher_spec(20), alert(21), handshake(22),
          application_data(23), (255)
      } ContentType;

      struct {
          ContentType type;
          ProtocolVersion version;
          uint16 length;
          opaque fragment[TLSPlaintext.length];
      } TLSPlaintext;

So, in this context, it is talking about fragmenting information from some higher layer across records. A TLS record consists of its type, protocol version, fragment length and the fragment data.
DTLS 1.2 is specified in RFC 6347 - and basically refers to the TLS RFC to say "its like that, but with these differences". Unfortunately the DTLS RFC also talks about fragments in an entirely different context:
4.2.3.  Handshake Message Fragmentation and Reassembly

   As noted in Section 4.1.1, each DTLS message MUST fit within a single
   transport layer datagram.  However, handshake messages are
   potentially bigger than the maximum record size.  Therefore, DTLS
   provides a mechanism for fragmenting a handshake message over a
   number of records, each of which can be transmitted separately, thus
   avoiding IP fragmentation.

   When transmitting the handshake message, the sender divides the
   message into a series of N contiguous data ranges.  These ranges MUST
   NOT be larger than the maximum handshake fragment size and MUST
   jointly contain the entire handshake message.  The ranges SHOULD NOT
   overlap.  The sender then creates N handshake messages, all with the
   same message_seq value as the original handshake message.  Each new
   message is labeled with the fragment_offset (the number of bytes
   contained in previous fragments) and the fragment_length (the length
   of this fragment).  The length field in all messages is the same as
   the length field of the original message.  An unfragmented message is
   a degenerate case with fragment_offset=0 and fragment_length=length.

In this context we are talking about handshake messages only (so not application data) and how those handshake messages are broken up. Those handshake messages are ultimately then sent in records.
The max_fragment_length extension is specified in RFC 6066. It is intended for use in both TLS and DTLS, and its use of the word fragment is very clearly related to the first of the above contexts, i.e. record layer fragments:
   The negotiated length limits the input that the record layer may
   process without fragmentation (that is, the maximum value of
   TLSPlaintext.length; see [RFC5246], Section 6.2.1).

In the pcap file that you sent me I can see that both client and server agree on a max fragment length of 1024. I then see that the server has sent the following record:

From this it is clear to see that the handshake fragment length is 1024 but the record fragment length is 1036. Since the max_fragment_length applies to the record fragment length this is too long and hence the client fails with the record overflow alert.
Probably your next step is to raise this with Scandium.

Thank you for the thorough analysis!


./configure: line 4238: syntax error near unexpected token `-mavx,' under Mac OSX

./configure
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
Using git revision: 4.00.00alpha-358-g362b68e
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... config/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking whether make supports nested variables... yes
checking dependency style of g++... gcc3
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-apple-darwin16.4.0
checking host system type... x86_64-apple-darwin16.4.0
./configure: line 4238: syntax error near unexpected token -mavx,' ./configure: line 4238: AX_CHECK_COMPILE_FLAG(-mavx, avx=true, avx=false)'

Some issues with the same problem mention that installing autoconf-archive as a fix. However it is already installed on my system

brew info autoconf-archive
autoconf-archive: stable 2017.03.21 (bottled)
Collection of over 500 reusable autoconf macros
https://savannah.gnu.org/projects/autoconf-archive/
/usr/local/Cellar/autoconf-archive/2017.03.21 (582 files, 3.4MB) *
Poured from bottle on 2017-03-30 at 17:48:56
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/autoconf-archive.rb
==> Dependencies
Required: autoconf ✔

https://github.com/tesseract-ocr/tesseract/issues/777#issuecomment-288116640


Added gameCoin Flip

PR Description 📜

Added game Coin Flip
Fixes #885

Coin Flip Game

The Coin Flip Game is a simple web-based game where players can guess the outcome of a coin flip.
The goal is to guess whether the coin will land on "Heads" or "Tails" correctly.
The game provides a fun way to test your luck and see how many correct guesses you can make.

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @VSatwika ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

follow proper guideline and create PR again !!!

Thank you  @VSatwika , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


[Algo] Fast Modulo Exponentiation

Algorithm

[x] I have gone through the repository and made sure this algorithm has not been implemented

Information about my new algorithm

Algorithm Name: Fast Modulo Exponentiation

Programming Language:  C++

Time complexity:  O(Log y)

Is this your first contribution to this repository?
Yes

I want to work on this issue


Use jira-azuredevops-migrator on apple devices

Hey Guys, i saw your migrator is only working on windows devices. Is It possible to create something like this for apple devices?
I tried some stuff with Wine Crossover but it didn't work as expected.

Hello!
I have not tried running the migration tool on a Mac personally, but I will talk with the maintainer of this project on Monday and see if the project can run on an Apple device. In the meantime, could you tell me more about your experience trying to run the migrator using Wine Crossover? 😄

The tool should be buildable/runnable under Mac-based systems using the .NET Core CLI. But we do not officially support the macOS platform yet  :)


Tentative fix for compiler warning

There's an unused variable in a function in xsimd_avx_int64.hpp. I just removed the unused variable and renamed the other vars accordingly, but I have no idea if that's correct :)
There are also some static inline functions in xsimd_rem_pio2.hpp clang is complaining about, with messages such as:
/home/yardbird/.local/include/xsimd/math/xsimd_rem_pio2.hpp:449:29: warning: 'static' function '__ieee754_rem_pio2' declared in header file should be declared
      'static inline' [-Wunneeded-internal-declaration]
        static std::int32_t __ieee754_rem_pio2(double x, double* y)

I can apply the suggested change in the PR if it makes sense.

Thanks for catching this! See my review for the fix of the unused variable, about the warnings regarding the static functions, I think we can drop the static specifier and use inline only.

No problem, thanks for the great library. I updated the PR.


Revert "CSS styles to overwrite jekyll styles"

Reverts AY2122S1-CS2103-T14-4/tp#231

Codecov Report

Merging #232 (b56db09) into master (e338af9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #232   +/-   ##
=========================================
  Coverage     44.72%   44.72%
  Complexity      683      683
=========================================
  Files           175      175
  Lines          3557     3557
  Branches        409      409
=========================================
  Hits           1591     1591
  Misses         1863     1863
  Partials        103      103

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 e338af9...b56db09. Read the comment docs.


rules_scala CI broken with Bazel@HEAD

Sample breakage: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1903#fe2ada5b-1ca7-486e-8840-ee4175e2c2cd
Sample error:
ERROR: /var/lib/buildkite-agent/builds/bk-docker-zx07/bazel-downstream-projects/rules_scala/third_party/dependency_analyzer/src/main/BUILD:6:39: in scala_library_for_plugin_bootstrapping rule //third_party/dependency_analyzer/src/main:scala_version:
--
  | Traceback (most recent call last):
  | File "/var/lib/buildkite-agent/builds/bk-docker-zx07/bazel-downstream-projects/rules_scala/scala/private/rules/scala_library.bzl", line 137, column 22, in _scala_library_for_plugin_bootstrapping_impl
  | return run_phases(
  | File "/var/lib/buildkite-agent/builds/bk-docker-zx07/bazel-downstream-projects/rules_scala/scala/private/phases/api.bzl", line 70, column 32, in run_phases
  | new_provider = function(ctx, current_provider)
  | File "/var/lib/buildkite-agent/builds/bk-docker-zx07/bazel-downstream-projects/rules_scala/scala/private/phases/phase_compile.bzl", line 47, column 34, in phase_compile_library_for_plugin_bootstrapping
  | return _phase_compile_default(ctx, p, args)
  | File "/var/lib/buildkite-agent/builds/bk-docker-zx07/bazel-downstream-projects/rules_scala/scala/private/phases/phase_compile.bzl", line 105, column 26, in _phase_compile_default
  | return _phase_compile(
  | File "/var/lib/buildkite-agent/builds/bk-docker-zx07/bazel-downstream-projects/rules_scala/scala/private/phases/phase_compile.bzl", line 130, column 28, in _phase_compile
  | out = _compile_or_empty(
  | File "/var/lib/buildkite-agent/builds/bk-docker-zx07/bazel-downstream-projects/rules_scala/scala/private/phases/phase_compile.bzl", line 186, column 23, in _compile_or_empty
  | _compile_scala(
  | File "/var/lib/buildkite-agent/builds/bk-docker-zx07/bazel-downstream-projects/rules_scala/scala/private/rule_impls.bzl", line 194, column 24, in compile_scala
  | ctx.actions.run(
  | Error in run: run() got unexpected keyword argument 'diagnostics_file'

Strangely enough, I can't find any evidence that diagnostics_file has ever been a parameter of ctx.actions.run(), nor is it as an experimental feature.
Is it possible this codepath has always been broken in anticipation of a feature, and this is being now triggered in Bazel@HEAD builds but wasn't before? The logic to assess this code path is:
 if len(BAZEL_VERSION) == 0 and enable_diagnostics_report:

Perhaps as of recently BAZEL_VERSION is 0 for Bazel@HEAD builds?
Regardless, I think the easiest solution is to disable this (broken) codepath for now.

Thanks for opening this issue @c-parsons!
@andrefmrocha do you have time to look into this?

Is it possible this codepath has always been broken in anticipation of a feature, and this is being now triggered in Bazel@HEAD builds but wasn't before?

I think that should be the case of what's happening here. I will open a PR for this.

Strangely enough, I can't find any evidence that diagnostics_file has ever been a parameter of ctx.actions.run(), nor is it as an experimental feature.

This has been related to the work of outputting diagnostics through the BEP that was being done here: https://github.com/bazelbuild/bazel/pull/11766 . At the time, this was being worked on at the same time as this feature, but I, unfortunately, haven't had any feedback on it for quite a while now.


[ohentai] Add new extractors

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
New extractor

All videos are from outside sources.
No hentai videos are hosted on this server.
Copyrights and trademarks for the hentai, and other promotional materials are held by their respective owners and their use is allowed under the fair use clause of the Copyright Law.

You sure this site's legal?

their use is allowed under the fair use clause of the Copyright Law.

I can see a lot of full length episodes on their front page. Uploading full episodes of series is not fair use. And considering they say "All videos are from outside sources", I am pretty sure they dont have re-distribution rights for them either. If you have proof to the contrary, let me know


[Helm] Meshery as an addition to the KubeSphere App Store

Current Behavior
KubeSphere App Store is a Helm-based store for application lifecycle management on the back of OpenPitrix, an open-source web-based system to package, deploy and manage different types of apps.
Meshery is not available as an application in this App Store.
Desired Behavior
Meshery available as an application in this App Store.
Implementation
@pengfei to advise.
Meshery Charts - https://meshery.io/charts/
KubeSphere Helm chart repo - https://github.com/kubesphere/helm-charts/tree/master/src/stable
Acceptance Tests

Meshery is available and deployable as an app in KubeSphere's catalog.

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

@pengfei, new versions of Meshery Charts are being published with each Meshery release. In terms of implementation, should we consider dynamically pushing to the KubeSphere App Store or do you recommend that this be a manual procedure?

Hi @leecalcote and Meshery team,
There are two ways that KubeSphere users could install Meshery with ease.

Import the Meshery Helm repo to KubeSphere and then install it from the KubeSphere App template (See an example)
Submit the Helm chart of Meshery to the KubeSphere Helm repo then it could be loaded into the KubeSphere App Store by default.

As for Meshery, option 2 is more convenient and visible to KubeSphere users since it could be available from the built-in App Store in KubeSphere. But it requires a manual upgrade to the Helm chart since the dynamic upgrade is not supported in KubeSphere so far. The dynamic upgrade will be supported in the future release.
So I recommend you to submit the Meshery Helm chart to KubeSphere Helm repo as the first step, then we could collaborate to add the installation guide to KubeSphere documentation and promote it in the community.

We can write a GitHub action job to push helm chart to KubeSphere repository after helm chart published in Artifact Hub.
Actions file to append the job:
https://github.com/meshery/meshery/blob/master/.github/workflows/helm-chart-releaser.yml
KubeSphere Helm chart repository where to do PR:  https://github.com/kubesphere/helm-charts/tree/master/src/stable
Universal Solution

Contribute a GitHub action in GitHub Marketplace to publish helm charts to KubeSphere Repository

Create Custom GitHub action for KubeSphere.
https://github.com/kubesphere/kubesphere/issues/4886

As @kethavathsivanaik mentioned above. I beleive this is a good idea. But I have a consideration here, may we add Helm chart of meshery to it's Helm repo first. I mean we can finish this short-term task first then the further feature would be warm welcome.

@Aisuko I worked on the short term goal to publish the chart to KubeSphere but it's majorly written in bash. So, I converted it into github action in this weekend. I will shortly do the PR with the feature..

Thank you @kethavathsivanaik .

Hi team,
I see Meshery has been added to the KubeSphere App Store.

Assuming that Kubesphere users put this Meshery entry to use, we'll set about automating the process of getting any changes to the helm charts pushed to update the KubeSphere App Store. 👍

@karnatisrinivas, your help here would be fantastic.

Yep Sure @leecalcote, I'll open an issue in the Kubesphere repo regarding the same.

Opened a PR in KubeSphere for the Meshery Installation guide from Kubesphere App store
https://github.com/kubesphere/website/pull/2530

Opened a PR in KubeSphere for the Meshery Installation guide from Kubesphere App store
kubesphere/website#2530

@karnatisrinivas will you share this update on the websites call today?


Develop

I worked Solo

home page built
comments section built
test integrated

@bimbolabuari  Hello  thanks but I can't submit on dashboard review still pending


dataJar autopkg recepie

An dataJar recepie download/munki for Notifier would be great :)

One exists, Notifier.download.recipe from moofit-recipes. Try that one.

ty @wegotoeleven


GPII-2951: DNS Route53 with subdomain delegation to Google DNS

Terraform code to create the DNS zone at Route 53 and delegate subdomain to Google DNS
WARNING: Do not merge this PR yet
Before merging this PR consider the comments at https://issues.gpii.net/browse/GPII-2951

Hmm, whatever you are doing with commits is making github confused. Your whole branch shows up at the bottom of this PR, below all my comments, but commits are from 27 days ago. This prevents me from seeing what commits I've already reviewed and which ones are new.
My only clue as to what has changed since my last review are the emails github sends when you push a commit. The SHAs mentioned in these emails don't exist in this PR.
Ok now I'm seeing that the Commits tab has better information, i.e. correct dates. But the SHAs are still all different. This might be enough information, but please evaluate how you manage commits to prevent this problem in the future. Thanks.


Reliance on libxmljs produces compilation error with node12

See this issue: libxmljs issue 546

Hmm not sure what to do about this, besides waiting for a patch :/

It seems like the issues with node 12 are finally resolved. I just published version 0.2.0 which now requires libxmljs version 0.19.7.


No visible output

What am I missing?

you need to configure your php cli interpreter
Settings->Language & Frameworks->PHP

If it's not the interpreter settings please let me know. You should have received an error message with what the issue is but i could have missed an exception.

Also, quick hint, you can instead of this print_r thing also just do \App\User::all(); without putting it in a variable to print it nicely immediately.

https://prnt.sc/ue69j5
How to change color?

@matro-skin tried to repair this in 1.1.1 but it seems a restart of the IDE fixes it for now. I created a new issue, #19 , I will tryu to make it work without a restart.

@Roboroads added a new issue #22 for output display format change

I'm going to assume the main issue got fixed.


assignment 6 KT

Why did the programmer quit his job?
Because he didn’t get arrays.

Good job. 100 points


Remove obsolete buttons and enable editing in metadata page

@FrankyHollywood maybe it's good to check the saturn tests again after the jdk upgrade - many of them seem to be failing on your previous commit: https://api.travis-ci.com/v3/job/562831576/log.txt
but at the end the build is passing, because last change did not triggered backend tests to be run...


Release for protoc 3.10.x

https://github.com/protocolbuffers/protobuf/releases 3.11 now

Released protoc-jar 3.10.1


Profile's name should be unique

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Profile should be unique,  so we should not have two profiles with same name.
Actually, we can not create two profiles with same name and same type, but we can create two profiles with same name and different types, which is unreasonable.
What you expected to happen:
Can not create two profiles with same name, even though they have different types.
How to reproduce it (as minimally and precisely as possible):
Create a profile with name A and type B.
Then create another profile with name A and type C, this profile would be created successfully.
Anything else we need to know?:
Environment:

Hotpot(release/branch) version: latest
OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS (Xenial Xerus)
Kernel (e.g. uname -a): Linux ubuntu 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Install tools:
Others:

Hi, Did you try to create profile using Dashboard? or some other mode cli/API?
I just tried to create profile with same name but different Storage Type and it gives 'Name is existing' error

@kumarashit Using CLI, I tried creating profile with same name but different Storage Type, it allowed me to create the profiles. However, I found another issue that there is no check/validation for the accessprotocol. I tried some random wrong combination for profile creation.

Got it. @himanshuvar thanks for confirming. For the access protocol issue we can create one.


I dont know whats going on here

I know what this is but cant tell in words what a shame awwwh

now i know whats wrong its fixed


https kestrel causes script to load 4-5 times slower than without

I originally thought the bug was part of mvc, but it might be from kestrel.
Information can be found on this thread:
https://github.com/aspnet/Mvc/issues/7704
But to sum it up, if you follow these instructions to get a new core 2.0 project:
https://docs.microsoft.com/en-us/aspnet/core/getting-started?view=aspnetcore-2.0
Then add https in UseKestrel in program.cs, the program loads super slow. A 38mb script when loaded with the new/clean project took me about 8-9 seconds, where as with https kestrel it took 35s to 1min.
If I load the same 38mb script in a clean .NET Core 1.1 project, it takes around 2-3 seconds. So the clean Core 2.0 project without the https kestrel is still approximately 3 times slower than a .NET Core 1.1 project
A reproducible example can be found in the mvc thread in my last comment.

/cc @sebastienros

@davidfowl Are there any potential work arounds to get https working without using kestrel to avoid the performance hit?

You can use IIS or HttpSys.

@Tratcher If i'm using a mac to develop, would HttpSys be out of the picture? I checked the documentation and it says it only supports windows. If my server, however, is on Azure that should be fine right?

@Tratcher Oh so if I'm using the listenOptions in kestrel to provide the ssl cert, I can just remove that bit of code and replace it with useIIS and place my cert in the azure portal?

That's the idea.

Oh okay i'll give that a shot. We should probably still investigate why kestrel has a performance hit though right? And would it just be as simple as adding UseIIS() to the WebHostBuilder?

You shouldn't need to add anything, IIS Support is included via WebHost.CreateDefaultBuilder.

I can run the static files scenario on https with different sizes and compare 2.1 to 2.0.

Correct. You'll want a flag so you don't tring to publish or load that certificate for production.
This should get easier in 2.1 where we provide a default development cert.

@sebastienros Did you add static file scenarios?  Any larger file scenario?

I measured 2.0 vs 2.1 for diverse file sizes on Linux, under load.

Description
RPS
Avg. Latency (ms)

2.0 https 1KB
38,424
85.5

2.1 https 1KB
85,143
82.2

2.0 https 16KB
37,307
114.8

2.1 https 16KB
65,120
53.6

2.0 https 512KB
2,044
1260

2.1 https 512KB
2,165
1170

2.0 https 1MB
828
1920

2.1 https 1MB
1,031
1920

2.0 https 5MB
155
3510

2.1 https 5MB
155
3170

Once you hit 5mb I assume you're saturating the network?
This ask was a bit different. How long does a single large download take on average? And how close does it get to saturating the network on its own?

Got it, will measure single accesses then.

@sebastienros Also note that is not about a perf regression from 2.0->2.1 but from 1.1->2.0.

We won't be making any changes here. We recommend moving to 2.0.

@muratg muratg The issue was with 2.0. I did a 1.1 -> 2.0 , which is where I noticed the performance issue. As noted by @halter73.


FIX #2814 Improve VT-x detection in PreCreateCheck

Signed-off-by: David Gageot<EMAIL_ADDRESS>

ping @docker/machine-maintainers

Closing since it doesn't seem to work on win7 either


Script for inductive training

Hi,
Can you please share your code for training and evaluating PPI dataset as well?
Thanks

Also, could you please share your code for large dataset like reddit? As in the paper, sampling is essential to avoid huge GPU memory usage, but it is not in this repo.

You can use GraphSAGE in DGL for mini-batch training.


[UI] Toster notification shows installed successfully when we delete a configuration in Management.

Description
When we delete a configuration in an adaptor using the :wastebasket: icon, upon successful deletion it shows [config] installed successfully
Expected Behavior

It should show [config] deleted successfully
Screenshots/Logs

Environment:

Meshery Version: 0.5.19
Kubernetes Version: 1.18
Host OS: ubuntu
Browser: Chrome

Contributor Resources:

(Contributing Docs](https://docs.meshery.io/project/contributing)

May I work on this issue ??

sure, @abhijeet007rocks8

@abhijeet007rocks8 Any blockers I can help you out with?

@abhijeet007rocks8 Any blockers I can help you out with?

Sir I am facing an issue to setup the backend server for meshery on local. I was not getting the meshes, to check the issue.
I joined slack and try to fix someone told me. If that does'nt work. I'll contact you.

Hello @dhruv0000, is this issue is still open? I wanted to work on this.

Sure @yash112-lang .

Sorry, for the delay but it was due to my exams, but now it's over so I will start working on this😀.

I am unable to locate the file from which this issue is happening if anyone helps me on which file I have to work on?

Hey @yash112-lang are you still working on this issue? There haven't been any updates from your side?

No updates @yash112-lang ?

@SirZeck I'm not working on this issue now. You can assign it to any other.

Sure @yash112-lang . You can go ahead and look for some other issue which you can work on. If you face any issue or have some doubt then ask in the slack channel after doing your homework though.

@dhruv0000 can i give it a try?


Minor edits for improved readability

#holdoff
@j-martens

@jimmart-dev : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"


Fix: Limit rules's prop expression

Type inference is difficult because I currently have so many object types.
I have proven that it is possible, but since autocompletion rarely works, we need to change it to as concise a form as possible.
It may be reintroduced in the future through performance improvements and updates to TypeScript.
// == Maintained Syntax =======================================================
// 1. Property with Array
rules({
  props: ["color", "background"]
});

// 2. Property with targets
rules({
  props: {
    size: {
      targets: ["padding", "margin"]
    }
  }
});

// == Disappearing Syntax ======================================================
// 1. Property with base value
rules({
  props: {
    background: {
      base: "red"
    }
  }
});

// The targets should bd specified.
rules({
  props: {
    background: {
      base: "red",
      targets: ["background"]
    }
  }
});

// 2. Property with aliased
rules({
  props: {
    size: ["padding", "margin"]
  }
})

// Should be created as an Object structure.
rules({
  props: {
    size: {
      targets: ["padding", "margin"]
    }
  }
});

Summary by CodeRabbit

New Features

Introduced a new rules() API for dynamic and declarative style definitions.
Added support for variants, toggles, and compound variants for conditional styling.
Enhanced property grouping with a new props feature for better state management.
Improved syntax for nested property definitions to enhance clarity.

Documentation

Updated documentation with examples demonstrating the use of the new rules() API and its features.
Ensured backward compatibility with existing styling implementations.

/fast-forward


Move older log from Archive folder to some other location instead of deletion

Hi!
Once Archive limit is reached, instead of deleting old files, I want to copy the older log file to another location on network. So that we have less older logs at location configured in "archiveFileName" and much older logs somewhere on archive server.
Is there a way that we can achieve it through nlog.config file.
We are crating more than 2 GB data in a week so want to keep older logs (more than 3 month old which we do not open/read frequently) on archive server.
NLog version: 4.5.11
Platform: .Net 4.5
Current NLog config
<target name="file" xsi:type="Iit.AsyncWrapper">
      <target type="File"
            archiveAboveSize="10000000"
            archiveEvery="Day"
            maxArchiveFiles="200"
            archiveNumbering="Rolling"
            archiveFileName = "${logDirectory}/archive/log.{#####}.txt"
            fileName="${logDirectory}/log.txt"
            layout="${longdate}|${level}|${processid}|${threadid}|${message}"
            concurrentWrites="false"
            keepFileOpen="true"
            encoding="iso-8859-2" />
    </target>

We need to have older logs(4-5 month old) some where on my archive sever but few logs on configured archive path in archiveFileName

In another way- Is it possible to get a notification when file target deletes the oldest archive file and any event can be added to the delete event? In that way same can be achieved.

I assume your question has been answered, if not, please let us know!


Unable to log into YAP - Server Timeout Error 500

Describe the bug
Login attempts simply time out.
What version are you running?
YAP 3.9.5  BMLT 2.15.1 (tried upgrading from 3.9.3 to resolve the issue but it still exists)
Did this happen on prior versions to the one you are running?
Yes 3.9.3
To Reproduce
Steps to reproduce the behavior:

enter credentials at YAP admin page https://na.org.au/yap3/admin.php
Press enter
server times out (I can see a cookies in the backend from users who've attempted to login)

Expected behavior
Login should work
Screenshots

Additional context
To me this feels a bit like the same error we've been getting when we try and run reports.
That's the only thing that's caused timeouts on our YAP instance.

we also know about a bug with the caching layer that will be fixed soon.
this is known to cause DB issues.
try running truncate table cache;  on your yap database

That didn't seem to make any difference.

We still cannot login.
We have tried a BMLT database restore back to 8 Oct (the last change to users that was made)
We have not tried a YAP Database restore.
These timeouts feel very much like the same timeouts we get when we try to invoke reporting.  It just times out.

To deal with the incident, it was recommended that the user switches to native Yap users.  After further investigation, it was discovered that this was related to the hosting provider blocking at a network level HTTP POST requests to the following two URIs.
%s/local_server/server_admin/xml.php?admin_action=get_permissions
%s/local_server/server_admin/xml.php?admin_action=logout

This code was introduced in Yap 2.0.0-beta1 and has largely not been changed (ref: https://github.com/bmlt-enabled/yap/commit/389a31a3324950491703eb297cd099d91297cd82).
HTTP POST is not actually required to enable this feature to work, so it was suggested to use a patched version of Yap with POST disabled.  This cleared up the issue.
Yap 3.9.6 will be introducing file-less cookie storage for BMLT authenticated users.  As part of that change HTTP POST will be disabled as seen in this commit: https://github.com/bmlt-enabled/yap/commit/ceacef77bac0dd61b7f429ee819ec722a3dec7f6


guided_json for vllm and openai use

Fixes https://github.com/h2oai/h2ogpt/issues/1526

Working for all except Cohere, which should be native vLLM json


Add GraphQLSchema.context to context in runGraphQL

This was causing a TypeError in vulcan-files because the file collection was not being added to the context that is passed to the resolvers in that package when querying with runGraphQL

Just out of curiosity why merging with the graphQL schema context solves this? As far as I understand the file collection does not belong so it's missing in the Collections object, that was your issue?

The vulcan-files package adds the file collection to the context with
GraphQLSchema.addToContext({ [collectionName]: FSCollection });
and all of its resolvers expect to be able to find the collection at context[collectionName]. But the collection is missing from the context object when run with runGraphQL because only the apollo-server context initialization did the merge, but not runGraphQL.
That was the specific issue we were facing, but in general, it seems that GraphQLSchema.addToContext should be respected regardless of whether the entry point to the query is from the client via the apollo server or a server-side query via runGraphQL.
Does that make sense? Happy to clarify further.

Yeah I think I undestand, I didn't even know about this addtoContext (I barely actually use Vulcan GraphQL related features outside of automated generation)

The collection should be registered in the Collection object somehow I think, it's overkill to extend the contextfor this, but you are right that some other part of the code could want to update the context for other reasons through this method.
I think my idea was to use a callback instead to enhance the context, this may need some clarification in future releases.


Add retries to autoboot in ipxe script:

Description

This gives the autoboot (in the embedded script) a chance to overcome transient network issues or similiar.
Why is this needed

Fixes: #
How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[ ] added unit or e2e tests
[ ] provided instructions on how to upgrade

Pending a basic test from @nshalman

It's actually not behaving as expected for me. I'll see if I can figure out why.

The more I think about this, the less I like the automated retries, but I do like the offer of a shell after a failure.
In the situation where a machine ought to be booting from disk, but is accidentally booting from the network, 5 retries could burn a lot of boot time. An offer of a shell to an operator watching after failure on the other hand might be hugely helpful for debugging while being less intrusive.
Also, I've been unable to get the retry logic to work. :(

The more I think about this, the less I like the automated retries, but I do like the offer of a shell after a failure. In the situation where a machine ought to be booting from disk, but is accidentally booting from the network, 5 retries could burn a lot of boot time. An offer of a shell to an operator watching after failure on the other hand might be hugely helpful for debugging while being less intrusive.
Also, I've been unable to get the retry logic to work. :(

Agreed, i think this is part of the reason i had this on hold for a while. the trade-offs of retrying weren't sitting right with me.

Agreed, i think this is part of the reason i had this on hold for a while. the trade-offs of retrying weren't sitting right with me.

I'm glad you never merged it as-is.

I did test the following which did appear to behave as I would expect:
diff --git a/binary/script/embed.ipxe b/binary/script/embed.ipxe
index b2c582b..5c85080 100644
--- a/binary/script/embed.ipxe
+++ b/binary/script/embed.ipxe
@@ -25,7 +25,9 @@ echo Booting from net${idx}...
 autoboot net${idx}

 :autoboot
-autoboot
+autoboot ||
+prompt --key 0x02 --timeout 2000 autoboot failed. Press Ctrl-B for the iPXE command line... && shell
+exit

 :boot-with-vlan
 set idx:int32 0

So I think I'm a :-1: on both the idea and the implementation of the retry logic, but I would be open to the brief offer of a shell after failure.

closing, please see conversation above.


Messenger bot is not receiving any messages

I have carefully fallowed every step from readme-facebook.
I copied the code:
require('dotenv').config();
var Botkit = require('botkit');
var controller = Botkit.facebookbot({
        access_token: process.env.access_token,
        verify_token: process.env.verify_token,
})
var bot = controller.spawn({
});
controller.setupWebserver(process.env.port,function(err,webserver) {
  controller.createWebhookEndpoints(controller.webserver, bot, function() {
      console.log('This bot is online!!!');
  });
});
controller.on('facebook_optin', function(bot, message) {
    bot.reply(message, 'Welcome to my app!');
});
controller.hears(['hello'], 'message_received', function(bot, message) {
	console.log('just heard "hello"');
    bot.reply(message, 'Hey there.');
});
controller.hears(['cookies'], 'message_received', function(bot, message) {
    bot.startConversation(message, function(err, convo) {

        convo.say('Did someone say cookies!?!!');
        convo.ask('What is your favorite type of cookie?', function(response, convo) {
            convo.say('Golly, I love ' + response.text + ' too!!!');
            convo.next();
        });
    });
});

I created .env file and store there access_token and verify_token and also set port to 3000.
Next I executed node index.js (index.js is name of my main file) and got this:

C:\Users\User\Documents\karlis\node\test>node index.js
Initializing Botkit v0.5.4
info: ** No persistent storage method specified! Data may be lost when process shuts down.
info: ** Starting webserver on port 3000
info: ** Serving webhook endpoints for Messenger Platform at: http://<IP_ADDRESS>:3000/facebook/receive
This bot is online!!!

Then I installed ngrok and got my forwarding link. I then set Facebook webhook url https://*****.ngrok.io/facebook/receive. At this point I got

Connections                   ttl     opn     rt1     rt5     p50     p90
1       0       0.00    0.00    0.57    0.57
HTTP Requests
GET /facebook/receive          200 OK

in ngrok terminal.
So at this point everything seems to be correct but I do not receive any messages. My page is not published but I can access it as admin. When I start typing the green dot appears indicationg that bot is live but I dont get any messages to my server.
I am new to node (wanted to switch for a long time) so maybe I have missed something. Please ask question, tell me what more info to provide. I am completeley out of options as I trully believe that evertything is set as from readme.
MAybe I am wrong but could there be problem with  Serving webhook endpoints for Messenger Platform at: http://<IP_ADDRESS>:3000/facebook/receive? I have not used ngrok before so dont now ecatly how it works. In docs there was place:

Run the example bot app, using the two tokens you just created. If you are not running your bot at a public, SSL-enabled internet address, use the --lt option and note the URL it gives you.
page_token= verify_token=<MY_VERIFY_TOKEN> node examples/facebook_bot.js [--lt [--ltsubdomain CUSTOM_SUBDOMAIN]]

I dont get [--lt [--ltsubdomain CUSTOM_SUBDOMAIN]] part. Is that what I am missing?

I had missed one tick for "messages" webhook....

So everything is working now? I am closing the issue, but feel free to reopen if you still have trouble!


Fix a small bug in peak truth

What does the code in this PR do / what does it improve?
Fix a small bug introduced by #226
Can you briefly describe how it works?
Can you give a minimal working example (or illustrate with a figure)?
Please include the following if applicable:

[ ] Update the docstring(s)
[ ] Bump plugin version(s)
[ ] Update the documentation
[ ] Tests to check the (new) code is working as desired.
[ ] Does it solve one of the GitHub open issues?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.28%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

fuse/plugins/truth_information/peak_truth.py
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2321

Relevant Lines:
2965

💛  - Coveralls


Does Microsoft Flow throttle flow runs?

 Learn more about run limits/quota on the pricing page: https://preview.flow.microsoft.com/pricing/
Thanks,
Deon

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

ID: 845c4db9-1f3a-26d1-5061-c018cb1fe336
Version Independent ID: c2a03981-a0aa-64a5-2659-e10202e5bb14
Content: Limits and configuration - Azure Logic Apps | Microsoft Docs
Content Source: articles/logic-apps/logic-apps-limits-and-config.md
Service: logic-apps
GitHub Login: @jeffhollan
Microsoft Alias: LADocs; jehollan

Yes, Microsoft Flow throttles flow run if you exceed your run limit/quota. Learn more about run limits/quota on the pricing page: https://preview.flow.microsoft.com/pricing/
#sign-off


uBlock blocks text on buttons

at https://learnosm.org/en/
system
Firefox 74 on Linux/Fedora
many add-ons installed, but nothing special seems to be blocked.

Ah okay, found the issue: It's uBlock origin.
It blocks that, because you named it "ads", the ID at least. And well… that's blocked.

@rugk Could you please give our staging site http://nick-tallguy.github.io/en/ a try? I just changed those subdivision names - the coloured buttons at the top are no advertisements anyway.

Not sure if this is relevant, but yesterday I was updating the site using a Raspberry Pi running 32bit Raspbian, and suffered this problem. At the time I assumed it was because I was trying to get the machine to do too much.
Today I'm using a 64 bit laptop running Ubuntu 18.04 and all is working fine.
I'll try my raspberry pi again shortly to see if the problem is persisting there.

Yes - still got the problem on the raspberry pi - using Chromium!  May be a 32 bit problem ? I have had problems in the past with other sites and the raspberry pi

Could you please give our staging site http://nick-tallguy.github.io/en/ a try? I just changed those subdivision names - the coloured buttons at the top are no advertisements anyway.

Yes, works.

Hi,
Having investigated a little more.
Using a Raspberry Pi, 32 bit running raspbian. Using Chromium, the site does not display the text on the 'buttons', but click on uBlock, then switch off 'cosmetic filtering for the site', and then refresh the web page, and the text appears.

Could you maybe discuss this in a different issue? This is totally off-topic…

@rugk This seems fixed now.


All items are re-rendered when filtering or adding items to the array

When filtering or changing the array of items externally (by either adding or removing items), all the items are re-rendered. This happens because of the GroupNgRepeatExpression. Groups are tracked by $$hashKey and new groups are created whenever the array changes.
A solution would be to track groups by group name, since it is unique by definition. This can produce a significant performance improvement for large arrays of items. Is there any I am overlooking for which "track by $group.name" is not an option?

+1


[CNI] Return retriable error for transient errors

cni to return retriable error for transient errors

Reason for Change:

This PR addresses CNI to return retriable error for transient errors so that cri would retry on error. This will prevent ipleaks in case if cni cannot connect to cns or cni cannot remove endpoint due to transient error
Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:

linux dualstack pipeline succeeded after i retrigger manually. so should be transient failure https://msazure.visualstudio.com/One/_build/results?buildId=52794160&view=results


Locating Specific Docker CypressBrowsers image

Hello,
I am trying to locate a specific CypressBrowsers Docker image to use in my application.
Needs to be Node version 20 LTS
And Cypress version 12.0.0
I looked in Docker Hub -- there is only information on the Node version on the tags.
How can I tell which tag to use for my requirements.
Your help is much appreciated ...

@bantao-kainos We don't have a published docker image with Cypress 12 and Node 20. You're welcome to use our provided docker factory to create you own image with a combination of Cypress versions/Node versions/browser versions. Instructions are here: https://github.com/cypress-io/cypress-docker-images/tree/master/factory


Can't use this parser with flow types

Hey,
I use Flow types types inside javascript part of .vue files.
Then using this parser for '.vue' files I get unexpected token errors from Flow. Then switching back, to use 'babel-eslint' and 'eslint-plugin-html' to parse .vue files, Flow error dismiss.
I don't know if this is a right place for an issue, but it looks like 'vue-eslint-parses' somehow makes Flow to check also html part of the file instead of only the script.
Flow type checking is done by 'eslint-plugin-flowtype' and 'eslint-plugin-flowtype-errors' packages.
Error looks like:
 11:11  error  Unexpected token !:       flowtype-errors/show-errors
In .vue file this line is Html comment.

Thank you for this issue.
It looks confliction that vue-eslint-parser cannot solve.

The eslint-plugin-flowtype and eslint-plugin-flowtype-errors seem to require only inside of <script>, so it has to strip the code by preprocessors.
The eslint-plugin-vue requires outside of <script> to verify templates, so does not work if it strips the code by preprocessors.

You have to separate those. For example:
$ eslint "src/**/*.vue" -c vue.eslintrc.js && eslint "src/**/*.vue" -c flow.eslintrc.js

I got an idea.
It needs the supports of eslint-plugin-flowtype and eslint-plugin-flowtype-errors.
The Program node (the root of AST) has the range of the source code of the program. In general, this is whole the source code. However, the JS code of .vue files are inside of the top-level <script> element, so the range of the Program node is the inside of the top-level <script> element.
If eslint-plugin-flowtype and eslint-plugin-flowtype-errors plugins use only the source code of Program node, we can get good collaboration with eslint-plugin-flowtype and eslint-plugin-flowtype-errors, and eslint-plugin-vue.

Thanks for an quick answer. Should I create issue about this in eslint-plugin-flowtype repo?

Yes, please.
After re-look, eslint-plugin-flowtype is no problem since it's using AST. But eslint-plugin-flowtype-errors is using source code text instead of AST, so it has this problem now.
Please open issue in eslint-plugin-flowtype-errors.

Closing this issue as favor of https://github.com/amilajack/eslint-plugin-flowtype-errors/issues/95.


[filters] Prevent a filter from sending local reply and continue

Signed-off-by: Asra Ali<EMAIL_ADDRESS>Commit Message: Prevent filter iteration on headers after sending a local reply and returning FilterHeadersStatus::Continue.
Additional Description:
Before, the test hits this crash:
[ RUN      ] Protocols/ProtocolIntegrationTest.ContinueAfterLocalReply/IPv4_Http2Downstream_Http2Upstream
[2020-12-14 16:51:35.110][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] Caught Segmentation fault, suspect faulting address 0x0
[2020-12-14 16:51:35.110][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
[2020-12-14 16:51:35.110][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:92] Envoy version: 0/1.17.0-dev/test/RELEASE/BoringSSL
[2020-12-14 16:51:35.111][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #0: __restore_rt [0x7fc14cdc68a0]
[2020-12-14 16:51:35.115][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #1: Envoy::ConnectionPool::ConnPoolImplBase::attachStreamToClient() [0xc378d6]
[2020-12-14 16:51:35.120][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #2: Envoy::ConnectionPool::ConnPoolImplBase::onUpstreamReady() [0xc3824d]
[2020-12-14 16:51:35.124][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #3: Envoy::ConnectionPool::ConnPoolImplBase::onConnectionEvent() [0xc39118]
[2020-12-14 16:51:35.128][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #4: Envoy::Network::ConnectionImplBase::raiseConnectionEvent() [0x10eda1b]
[2020-12-14 16:51:35.132][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #5: Envoy::Network::ConnectionImpl::raiseEvent() [0x10e4889]
[2020-12-14 16:51:35.136][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #6: Envoy::Network::ConnectionImpl::onWriteReady() [0x10e744e]
[2020-12-14 16:51:35.140][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #7: Envoy::Network::ConnectionImpl::onFileEvent() [0x10e64e9]
[2020-12-14 16:51:35.144][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #8: std::__1::__function::__func<>::operator()() [0x10d0971]
[2020-12-14 16:51:35.148][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #9: Envoy::Event::FileEventImpl::assignEvents()::$_1::__invoke() [0x10d174c]
[2020-12-14 16:51:35.152][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #10: event_process_active_single_queue [0x17c33f8]
[2020-12-14 16:51:35.156][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #11: event_base_loop [0x17c1dce]
[2020-12-14 16:51:35.160][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #12: Envoy::Server::WorkerImpl::threadRoutine() [0xac9688]
[2020-12-14 16:51:35.164][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #13: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::{lambda()#1}::__invoke() [0x17bb2a3]
[2020-12-14 16:51:35.164][29][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #14: start_thread [0x7fc14cdbb6db]

The downside here is iteration_state_ isn't modified to stop iteration. I don't think this matters since it's changed to StopSingleIteration in maybeContinueDecoding right after.
Risk Level: Low/medium in case this changes expected filter iteration?
Testing: Added test that shows message logs and behavior passes.
Fixes part of https://github.com/envoyproxy/envoy/issues/13737

Thanks for the fix!  mind checking out CI and pinging back when it's sorted?

Just to double check, oauth2 filter sends a local reply and then sends StopAllIterationAndBuffer (the test failure). Is it possible that people can send a local reply and then continue header iteration?
The most minimal constraint would be changing the condition to "don't return continue after local reply" rather than "must return stopiteration after local reply"

I wonder if it's an attempt to drain the connection so it can be reused (for HTTP/1.1 etc.)?
cc @rgs1 @derekargueta @snowp

Just to double check, oauth2 filter sends a local reply and then sends StopAllIterationAndBuffer (the test failure). Is it possible that people can send a local reply and then continue header iteration?
The most minimal constraint would be changing the condition to "don't return continue after local reply" rather than "must return stopiteration after local reply"

Thanks for this fix! I somehow forgot to follow-up with a fix here when we first bumped into this internally... this should be StopIteration. Our internal copy of this filter -- and similar filters -- have already being fixed... And that made the crash go away.

I wonder if it's an attempt to drain the connection so it can be reused (for HTTP/1.1 etc.)?
cc @rgs1 @derekargueta @snowp

Which part? The Stop and Buffer as opposed to full Stop? Or continuing header iteration post local reply...? Afaik this was just a bug/omission on our side, not something to reset the connection state...

Ah cool.  If it's just broken I'd be inclined to restore your last push and fix oath upstream too, WDYT?

Sorry about the back and forth! All set with just preventing continue after a direct response. No changes to oauth2 (which maybe can be a TODO)

Not sure if the wait is to update filter_manager to restrict back to stopiteration after local reply (rather than just "not continue"). Tests pass with @rgs1's Oauth PR merged.


[ICON REQUEST]

Describe the icon you'd like to be added
past time, audit log , history
Sample icon

Hi @iAutistic, this icon has been added to the library. Search history or rewind and you should see it.


ocamlPackages.magic-trace: 1.2.1 -> 1.2.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/janestreet/magic-trace/releases.
meta.description for ocamlPackages.magic-trace is: Collects and displays high-resolution traces of what a process is doing
meta.homepage for ocamlPackages.magic-trace is: https://github.com/janestreet/magic-trace
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.2 in filename of file in /nix/store/wnfimhg5gx15gxq09yl1misf52zvia91-ocaml5.1.1-magic-trace-1.2.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wnfimhg5gx15gxq09yl1misf52zvia91-ocaml5.1.1-magic-trace-1.2.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.magic-trace https://github.com/r-ryantm/nixpkgs/archive/e8af9b29ca27292906b3d21faf165b132b1e9f90.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e8af9b29ca27292906b3d21faf165b132b1e9f90#ocamlPackages.magic-trace

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wnfimhg5gx15gxq09yl1misf52zvia91-ocaml5.1.1-magic-trace-1.2.2
ls -la /nix/store/wnfimhg5gx15gxq09yl1misf52zvia91-ocaml5.1.1-magic-trace-1.2.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

ocamlPackages.magic-trace

Maintainer pings
cc @Alizter for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/janestreet/magic-trace/releases.
meta.description for ocamlPackages.magic-trace is: Collects and displays high-resolution traces of what a process is doing
meta.homepage for ocamlPackages.magic-trace is: https://github.com/janestreet/magic-trace
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.3 in filename of file in /nix/store/4qsnacas3ahmazfvbmwavpdhzf8wjr4l-ocaml5.1.1-magic-trace-1.2.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4qsnacas3ahmazfvbmwavpdhzf8wjr4l-ocaml5.1.1-magic-trace-1.2.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.magic-trace https://github.com/r-ryantm/nixpkgs/archive/97752082ddd77922146cb260ce41befc74c00305.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/97752082ddd77922146cb260ce41befc74c00305#ocamlPackages.magic-trace

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4qsnacas3ahmazfvbmwavpdhzf8wjr4l-ocaml5.1.1-magic-trace-1.2.3
ls -la /nix/store/4qsnacas3ahmazfvbmwavpdhzf8wjr4l-ocaml5.1.1-magic-trace-1.2.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

ocamlPackages.magic-trace

Maintainer pings
cc @Alizter for testing.


IA-2462 Cypress submissions list

Period year was hardcoded in test and computed in the frontend to take last ten years.
Related JIRA tickets : IA-2462
Self proofreading checklist

[x] Did I use eslint and black formatters
[x] Is my code clear enough and well documented
[ ] Are my typescript files well typed
[ ] New translations have been added or updated if new strings have been introduced in the frontend
[ ] My migrations file are included
[ ] Are there enough tests
[ ] Documentation has been included (for new feature)

Changes
Compute year
How to test
I'll run cypress on this branch

https://github.com/BLSQ/iaso/actions/runs/7500169900


Trouble with getting started with SSR using NextJS

Hello, I am having trouble getting a simple Unity webgl project to render in my React page despite following the quick start instructions (as well as some instructions from the community). I am hoping someone can point out what I am doing wrong!

Creating a component for my Unity content (Viewer.js)

Importing into my index.js

With the following file structure:

But I am getting the following error:

Thanks in advance for any input!

Forgot to mention that this is a Next.js app.

Hey,
I'm not sure if this is how it is supposed to work.
Generating a new UnityContext is done with the following function (using UnityCONTEXT) (Same for the Html Tag)

Can you please try that and report back if it worked?
Best
Max

Hey,
I'm not sure if this is how it is supposed to work.
Generating a new UnityContext is done with the following function (using UnityCONTEXT) (Same for the Html Tag)

Can you please try that and report back if it worked?
Best
Max

Hi @leskodan, the module is currently not supporting server side rendering. I'm trying to look into it any time soon.

Hi @leskodan, the module is currently not supporting server side rendering. I'm trying to look into it any time soon.

I will be working on the feature on a separate branch which can be monitored from #140. This PR might need testings in the future.

I will be working on the feature on a separate branch which can be monitored from #140. This PR might need testings in the future.

Hi @jeffreylanters, that was what I expected, thanks for looking into this! I'm really happy with how this works in pure React, but excited to see it progress in the context of Next.js and server side rendering.

Hi @jeffreylanters, that was what I expected, thanks for looking into this! I'm really happy with how this works in pure React, but excited to see it progress in the context of Next.js and server side rendering.

Thanks! I'll keep you posted, but I'm completely new to SSR so I have to take some crash courses and look into it. it might take a while before I publicly release support on NPM.

Thanks! I'll keep you posted, but I'm completely new to SSR so I have to take some crash courses and look into it. it might take a while before I publicly release support on NPM.

Got it. I can try this on my end, but do suspect that using 'next export' to statically generate the HTML would work for the time being? As far as I understand, this is an alternative to SSR in Next.js.

Got it. I can try this on my end, but do suspect that using 'next export' to statically generate the HTML would work for the time being? As far as I understand, this is an alternative to SSR in Next.js.

Update on my end:

        { process.browser && <UnityComponent/>}

Using the following code forces Next to use client side rendering for the Unity component. This serves as a workaround for the lack of support for SSR.

Update on my end:

        { process.browser && <UnityComponent/>}

Using the following code forces Next to use client side rendering for the Unity component. This serves as a workaround for the lack of support for SSR.

you are a lifesaver @leskodan . I have also been attempting to implement with Next js. Thank you jeffrey for a wonderful package!

Thanks @Clokk! I'm still planning on building this in, but I have to look into this first. I've never used server side rendering before. @Leskodan's example is a good start, but he's excluding the entire module from SSR. I want to try excluding it partially. If any of you have some tips let me know, or feel free to contribute.

Hi @jeffreylanters , really just started looking at this today - but from what I gathered I could not get SSR to work in production mode even with leskodan's fix. An alternative approach that I got working fairly quickly is to dump the files in an amazon s3 bucket, ensure that the files are public and properly set CORS. I have it working in production now with SSR. I just had to point UnityContent params to the new amazon urls rather than locally in public file path.
IMO you don't need to rush to this, especially when a solution as I have laid out exists with fairly easy implementation. Thanks again!

I'm having a hard time getting either of these solutions to work on my NextJS build. I'm also having a hard time determining exactly where my build is failing. I don't get any error messages in console and the UnityContext.on events don't seem to fire at all. It would be beautiful to get a NextJS example added to the ReadME

.....So after my build failing on Chrome for a couple days it turns out it's actually working on Brave? I realized this from cloning your template repo and noticing it only runs on my Brave browser as well (not Chrome). So for anyone else experiencing my issue I would recommend trying different browsers.


Updated to run with python3

Hey, I updated the project to be able to run with Python 3.4.
Be aware that this installation will not work if you use Python 2.7.
Note that there is an change to the requirements file, as pdfminer has changed for Python 3.
Additionally, I have not tested for every file this project support, but I have had the time to test for pptx, xlsx and docx.
Any comments are greatly appreciated.

In order to convert the text to a Python 3 string the following code can be used:
import textract
text = textract.process(your_file_path)
pythonString = str(text, 'utf-8')

What is the status on this PR?  We rely on Textract and I'm currently working on porting to Python 3.  Is there a plan to make Textract Python2/3 compatible?

@Nift -- This is a great idea and I appreciate you getting the ball rolling on this. I'm a python3 n00b, but I look forward to figuring this out.
@nesnahnoj -- thanks for bringing this to the top of my inbox today and for putting a vote to having python3 support. As you'll see below, I had a few lingering things that I haven't had the time to jot down. Please accept my apologies for my relatively slow response.
I'm admittedly having a very hard time following this pull request though, and I do not think I can figure out how to merge this in on my own. This pull request includes a lot of files copied into the textract directory (all of them?), causing nearly the entire codebase to be duplicated inside of that directory. The textract directory is intended to only hold the python code of the package, not all of the other cruft that's necessary for development, documentation, testing, etc. This makes it very difficult to understand what, specifically, had to change to provide python3 support. I'm going to close this particular pull request, but its my sincere hope that we incorporate python3 support.
@Nift -- If you or anyone else would like to create a separate pull request that provides python3 support, I'd encourage you to create a feature branch based off of the current deanmalmgren/master branch and only change the files that are necessary to incorporate python3 support. I would be happy to hop on skype/hangout/etc to help you get started if you'd like.
Admittedly, I don't know a whole lot about python3, but here are a few things that I think are important to keep in mind as we adapt textract to being python3 compatible:

I would like to understand how bigger python projects manage both the python2 and python3 support. I could imagine handling this either (i) by adapting having the codebase support python2 and python3 simultaneously and making releases on the same 1.x version sequence, (ii) by killing python2 after the next 1.x version release and only continue support in python3 starting in the 2.x version release, or (iii) by maintaining support for python2 and python3 on separate branches and releasing python3 releases on a new 2.x version sequence. I'm leaning toward options (ii) or maybe (iii), simply because it makes the code less kludgy and easier to maintain, but I'd appreciate input from anyone else that has experience with this or preferences one way or another. Advice welcome!

My understanding is that python3 has a much more straightforward treatment of byte string encodings and unicode. I'm not sure how that will impact many of the parsers, but several of the command line tools output byte-encoded strings. This is why we create a unicode sandwich when we process output from command line tools (and other tools) and why we have to guess the encoding of the incoming byte string. Python 3 may make this easier, but we should address this situation in a consistent way.

I have no idea how many of textract's dependencies are python3 compatible. Ideally we wouldn't have to sacrifice any currently supported functionality when we make the python3 switch, but I'm not necessarily married to that. @Nift mentioned pdfminer is an issue; are there others?

I can't think of anything else, but this list of concerns is one of the reason it took me a while to respond to this pull request. Thanks again to @Nift for getting the ball rolling on this, and I look forward to working with you and others to get python3 incorporated in a separate PR soon.


CORS Error Has Been Resolved

Before  :

After  :

@LynxSumit  Your system is handling the changes well, but when I attempt to view your deployment preview, I'm stuck with a loading shimmer UI for an extended period (data isn't loading). I've tried various methods like disabling CORS, using CORS, and even incognito mode, but it appears that these changes may only work with specific systems. It appears that we might need a CORS extension for this app to be accessible to all users.
can you please check once.
With CORS :

Without CORS :

Incognito mode :

@LynxSumit Your system is handling the changes well, but when I attempt to view your deployment preview, I'm stuck with a loading shimmer UI for an extended period (data isn't loading). I've tried various methods like disabling CORS, using CORS, and even incognito mode, but it appears that these changes may only work with specific systems. It appears that we might need a CORS extension for this app to be accessible to all users.
can you please check once.
With CORS :
Without CORS :
Incognito mode :

Yeah Bro I can See the issue with you can you try on tapping home Tab, cuz in my system i have opened same link and it workz well

Bother, I've given it a shot with the home nav, but I'm still facing the same issue. Would you mind taking a look at it and seeing if you can come up with a resolution? Feel free modify the code whatever way you're comfortable with.

just a heads-up – these tweaks might do the trick on certain devices, but not on all. It's worth considering that this approach might not be the ultimate solution for granting app access without the trusty CORS extension.
hence closing the PR


Add a sink connector to export stream data to Alluxio

Alluxio is an open-source virtual distributed file system that provides a unified data access layer for hybrid and multi cloud deployments. For some application cases, someone may expect to provide a sink connector to export pulsar messages to Alluxio.

I think having an Alluxio Source would be great too.

@murong00 Are you interested in implement this feature?

@codelipenghui This feature is already supported based on version 1.8.1, you can refer to #3823 for some detail, I have addressed sijie's comment, you can help to review it again.


Fix misleading exception of Jenkinsfile.run_parallel_tests

Signed-off-by: Yixin Qian<EMAIL_ADDRESS>related: #2730

https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1074/console

Thanks @OscarQQ for the quick response!
Could you update the title to reflect the change? And could you run Grinder with parallel and non-parallel?

thanks for the thorough testing via Grinders!


Fixed the dashboard reload issue and follow user issue in search page

Verified and merged with the master

Verified and merged with the master


Cache stream placement info

Description
Right now placement of remote stream is read from the contract on each access, cache and update from events to speed up request to the remote strams.

(fixed)


Added additional fields to class Trade

Added new fields to reflect current IB's Trade flex query

Yes, this is how you do it.  However, I'm not too sure about the types here... looking at the data you posted in your original bug report, it seems that fineness and weight are actually decimal numbers, and should be defined as such.
The types defined here also need to be harmonized with your test cases too... in the other pull request you checked in a test asserting that Trade.fineness is a decimal, but then here give it a type annotation that instructs the parser to convert this to a string.  It's easy to predict that inconsistency is going to blow up in our faces.
It's not a big deal, but the usual convention is to check in the changes in the data model and the tests that exercise these changes at the same time, in the same pull request.  The idea is that you never want to check in code that blows up your test suite (on the one hand) or that is untested (on the other hand).
deliveryType and commodityType are probably enums, I would guess, but until we get some actual data for these we should leave them as strings, as you have.

Sorry, my bad!
fineness is indeed decimal, but weight is given as weight="0.0 ()" in the sample I provided. Would this still be classified as decimal?

weight="0.0 ()"
Yeah that's not good.  It looks like this is metadata for a commodity, so the type here is most likely a decimal plus a unit of measure in parentheses... something like 136.5 (oz) or 2.34 (kg).  It's just blank in your case because the commodity you're trading is dimensionless.
The ibflex library does not yet have types defined to deal with this sort of thing, and I'm certainly not going to run out and write them on spec without a bunch of hard data to fit.  So I guess let's just leave the weight as type str for now.
Thank you.


[Camera Plugin] CameraPreview blurred and stretched on Android API 30 - Samsung S20

camera: ^0.9.4+5
Future _startLiveFeed() async {
    final camera = cameras[_cameraIndex];
    _controller = CameraController(
      camera,
      ResolutionPreset.max,
      enableAudio: false,
      imageFormatGroup: PlatformChecker.which == PlatformType.ios
          ? ImageFormatGroup.yuv420
          : ImageFormatGroup.unknown,
    );

    await _controller?.initialize().then((_) async {
      if (!mounted) {
        return;
      }

      _controller?.startImageStream(_processCameraImage);
      setState(() {});
    });
  }

Camera plugin

Device camera

Hi @ViniciusSossela, thank you for filing this issue. I verified on the latest master and stable channel using camera 0.9.4+5
and the issue is reproducible. I tested this on a Samsung S10+ api 30 device.

output
device camera

flutter camera

code sample
// Copyright 2019 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

// ignore_for_file: public_member_api_docs

import 'dart:async';
import 'dart:io';

import 'package:camera/camera.dart';
import 'package:flutter/material.dart';
import 'package:path_provider/path_provider.dart';
import 'package:video_player/video_player.dart';

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      title: 'Material App',
      theme: ThemeData.dark(),
      home: PicturePage(),
    );
  }
}

class PicturePage extends StatefulWidget {
  @override
  State<StatefulWidget> createState() => _PicturePage();
}

class _PicturePage extends State<PicturePage> {
  List<CameraDescription>? cameras;
  int index = 0;
  CameraController? controller;

  @override
  void initState() {
    super.initState();

    init();
  }

  @override
  void dispose() {
    controller?.dispose();
    super.dispose();
  }

  init() async {
    cameras = await availableCameras();
    await initThisCamera(0);
  }

  initThisCamera(int id) async {
    controller = CameraController(cameras![id], ResolutionPreset.max,
        enableAudio: false);
    index = id;
    await controller?.initialize();
    if (!mounted) return;
    setState(() {});
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      extendBodyBehindAppBar: true,
      backgroundColor: Theme.of(context).backgroundColor,
      body: body(),
    );
  }

  Widget body() {
    if (controller == null || !controller!.value.isInitialized)
      return Center(child: CircularProgressIndicator());
    return Stack(
      children: [
        CameraPreview(controller!),
      ],
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 2.5.3, on macOS 11.6.1 20G224 darwin-x64, locale en-US)
    • Flutter version 2.5.3 at /Users/flo/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (7 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/flo/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 13.1, Build version 13A1030d
    • CocoaPods version 1.11.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.62.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (5 available)
    • SM G975U (mobile)                  • R58M95MA95E   • android-arm64  • Android 11 (API 30)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • sdk gphone64 x86 64 (mobile)       • emulator-5556 • android-x64    • Android 12 (API 31) (emulator)
    • macOS (desktop)                    • macos         • darwin-x64     • macOS 11.6.1 20G224 darwin-x64
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 93.0.4577.63

! Doctor found issues in 1 category.

✓] Flutter (Channel master, 2.6.0-12.0.pre.868, on macOS 11.6.1 20G224 darwin-x64, locale en-US)
    • Flutter version 2.6.0-12.0.pre.868 at /Users/flo/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fff85f9c57 (7 hours ago), 2021-11-30 23:09:05 -0500
    • Engine revision c2fcadef89
    • Dart version 2.16.0 (build 2.16.0-56.0.dev)
    • DevTools version 2.8.0

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/flo/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.62.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (5 available)
    • SM G975U (mobile)                  • R58M95MA95E   • android-arm64  • Android 11 (API 30)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • sdk gphone64 x86 64 (mobile)       • emulator-5556 • android-x64    • Android 12 (API 31) (emulator)
    • macOS (desktop)                    • macos         • darwin-x64     • macOS 11.6.1 20G224 darwin-x64
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 93.0.4577.63

! Doctor found issues in 1 category.

Thank you

Hi @ViniciusSossela
I see there's an open issue addressing the case you described https://github.com/flutter/flutter/issues/56760.
Please follow up on that issue, I'm closing the current one as a duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you


feat: added login and update livepeer.js

@hthillman do we really need all these extra fields? I'm in favor of least amount of friction as possible for signups. Nearly all developer platforms these days ask for an email address or allow you to sign up with github and nothing else.

@adamsoffer @0xcadams
My only real requirement here is Company Name, if someone is using Studio for work. This is so that we can correctly associate Studio accounts with our sales pipeline.
I am okay with removing everything else other than email.

@adamsoffer all the rest is legacy, in general we should revisit the FTUX

I would also love to allow sign-in with github +google but assuming that's a bigger lift

Okay great - so I can remove name fields and keep company name.
FWIW these signups usually have more screens to them once you enter email/password. The low friction is usually on entering email and then they add more signup friction as a second step.

@0xcadams yeah this is a good callout. IMO we need a wholesale rethink of the account creation flow. We can get a lot of valuable data during this process to help us fine-tune the onboarding and give users a clear and workflow-specific path to success

Okay, I removed first name and last name fields and simplified the UI. Let me know if this looks good to merge.

@0xcadams
Nit: Studio -> Livepeer Studio
Also, wdyt about changing  "Are you using Studio for work" to "I am using Livepeer Studio for work"? That feels more apt since there is a checkbox
Lastly, does this information get logged to Hubspot as well as the DB? or just the DB

@victorges @gioelecerati could you guys take a quick look at this and give any feedback on why it's failing to create a user? The API is responding with user not created and not sure why. Maybe firstName/lastName are required fields in the DB?

bump @victorges @gioelecerati! When you have a moment, could you give Chase a review?

@0xcadams just pushed a commit to fix the issue I believe you were having: replication delay in our DB.
I reviewed the user registration flow and there's no validation on the first/last name fields. I did find that there is a logic that creates the user and immediately reads it back though. The problem was that it was reading from a read replica so sometimes it would not find the user depending on the replication lag (I could not reproduce the issue, cause it's not a consistent thing). I believe the issue is unrelated to the change here, but I've fixed it anyway. Should be good to go


docs(table): seleteMenu is obscured

🔗 Linked issue

❓ Type of change

[x] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

before:

after:

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

I don't reproduce this on https://ui.nuxt.com/components/table#columns 🤔

Oh I see, maybe we should add a min-height to the Table instead then?

Oh I see, maybe we should add a min-height on the Table instead then?哦，我明白了，也许我们应该在桌子上添加一个min-height ？

If min-height is set, there will be some blank space after deselecting all and then closing the drop-down. Will it look ugly?

This is the effect after trying to set min-height. If you think it's okay, I will modify it like this

Yeah I think it's fine because removing the overflow-hidden might break the display on mobile!

Thanks 😊


Remove diode footprint from the top surface

Restore progress from #6

I think with the current verion there are still some Problems.

A lot of useless vias.
The pathing is less optimal and goes through the picture

If you don't mind I will open a PR to yours with a few changes.

Old PCB for comparision

Yes, feel free to submit a PR

This PR was deprecated in favor of #10


feat(apps/prod/tekton/configs): auto add nightly and latest tag for image

for nightly tag
when master or main tag pushed, it will add nightly tag.
for latest tag
when no-pre semver tag added, it will add latest when the version is higher than the exist no-pre semver tags.

/approve


Add support for java runtime

Taking another shot at implementing Java runtime in PR #1922

Will this be merge in master ?

Re-implementing in PR https://github.com/serverless-stack/sst/pull/1922


Forms do not render correctly for added elements

At first I would like to say thank you for this framework, it is brilliant and easy to use!
I render the form to each of the objects in the list, but sometimes there are situations where the form does not display properly. After examining an item, you can't even see its source code
Suppose we add an item form for each tag in the todo application. For such an added element, the code contained in form tag completely disappears
`

Add

    {% if tasks %}

        {% for task in tasks %}

{{ task }}

        <form unicorn:submit.prevent="add">
            <input type="text" unicorn:model.lazy="name" value="test" id="name"></input>
        </form>

        <button unicorn:click="add({{forloop.counter0}})" data-dismiss="modal">Add</button>

        {% endfor %}

    <button unicorn:click="$reset">Clear all tasks</button>
    {% else %}
    No tasks 🎉
    {% endif %}

`

Ensure that each form has a unique ID. The id attribute in your form should be unique for each form on the page. Having multiple forms with the same ID can lead to rendering issues.

Sorry @lancernik I definitely missed this issue in the past. Usually this happens because morphdom gets a little confused about which elements should be on the page. I have made a few changes recently that should potentially help with this situation or @VidyaYadavv1519's solution of adding a a unique id will probably help as well! I'm going to close this, but let me know if you still run into problems.


The pipeline sidebar isn't being fully displayed and is non-scrollable

When I click on any pipeline page, the sidebar isn't being fully displayed.
To reproduce, click on any pipeline page with a longer sidebar, e.g. https://nf-co.re/sarek.
It would be nice to have a scrollbar for smaller screens?

Ah, I think I probably just didn't scroll down far enough, it gets stuck in the middle,  to wait for the main page to reach the bottom:

Probably not an issue, I'll close it!

thanks for digging this one up. I added now a max-height + overflow in #1872

Great, thank you! 🙏🏻


Poor handling of truncated streams

Currently InflateStream::update nearly always returns Ok for truncated streams, and this flows through to the higher level APIs. There should be some way to determine that more data is still expected, but I don't see how the current API allows for this. The documentation says to call InflateStream::update until it returns 0 bytes, but none of the current callers do this, and I don't see how it can work. In general, the last call that passes some input data to InflateStream::update will make progress, and then there is no further input data to pass, so the caller will never get 0 bytes returned.
The one exception that I can see was introduced in #24, and that only occurs if there are less than 4 bytes currently available when in state CheckCRC. Actually, this check is wrong, because the CRC may be split over two update calls.

The caller can detect truncated streams if it knows how many bytes it expects (gzip, PNG, etc.).
Or are you talking about knowing whether there are unused bits, or I guess if the current block hasn't ended yet? IIRC it might be possible to have a complete block and not be able to tell (from the stream itself) that any more data follows but I could be wrong, it's been ages.

Ahh, so there's both an end of block marker and that bit. Yeah then we could have a method, e.g. is_finished or is_complete.

Ah, I wasn't aware that callers generally knew how many bytes to expect. In that case, this probably doesn't matter much. I just noticed it because of the test to check for missing CRC.
An is_finished method on InflateStream is simple to add.
Should InflateWriter also have this method? Another option is for InflateWriter::finish to return an error if the stream isn't finished.
Similarly, should inflate_bytes return an error? There's no other way for it to signal truncation.