Labels overlapping, what's the replacement for checkToShowTitle

Hi,
I was before on version: 0.36.4 and used checkToShowTitle to hide some labels:
checkToShowTitle:(minValue, maxValue, sideTitles, appliedInterval, value) {
            if (minValue == value) return false;
            if (maxValue == value) return false;
            return true;
},

I updated to the latest version and tried to replace it with in getTitlesWidget:
 if (meta.min == value) return Container();
 if (meta.max == value) return Container();

but this does not hide the same as before and labels are overlapping.
Im not sure if something else could be also an issue but I can't find a solution.

Its not working because its not the max value but how it was working before?

Before the update it was inconsistent like sometimes only 3 values would be shown but it never overlapped at least.
I want to have one label at the top, one at the bottom and 2 in-between but can't make it work.
Thats my full configuration:
class ChartConfigHelper {
  static LineChartData getChartConfig(
    List<AssetHistory> points,
    MarketHistoryTimeRange range,
    Currency selectedCurrency,
    Color primaryColor,
    Color dividerColor,
    Color captionColor,
    Color scaffoldColor,
  ) {
    var largestPrice = points.map((e) => e.priceUsd).toList().reduce(max);
    var smallestPrice = points.map((e) => e.priceUsd).toList().reduce(min);
    var difference = largestPrice - smallestPrice;
    var interval = difference / 3;

    return LineChartData(
      lineTouchData: LineTouchData(
        getTouchLineStart: (barData, index) => -double.infinity,
        getTouchLineEnd: (barData, index) => double.infinity,
        touchTooltipData: LineTouchTooltipData(
          tooltipBgColor: PlatformHelper.isDesktop()
              ? primaryColor.withOpacity(0.8)
              : primaryColor,
          fitInsideHorizontally: true,
          tooltipMargin: PlatformHelper.isDesktop() ? 20 : 0,
          showOnTopOfTheChartBoxArea: PlatformHelper.isDesktop() ? false : true,
          getTooltipItems: (touchedSpots) {
            return touchedSpots
                .map((e) => LineTooltipItem(
                      '${MarketFormat.getMarketChartTooltipPriceString(e.y, selectedCurrency.currency, true)} \n\n ${DateFormat.yMd(Platform.localeName).format(points[e.spotIndex].time.toLocal())} \n ${DateFormat.jm(Platform.localeName).format(points[e.spotIndex].time.toLocal())}',
                      const TextStyle(color: Colors.white, fontSize: 14),
                    ))
                .toList();
          },
        ),
        touchCallback: (_, __) {},
        handleBuiltInTouches: true,
        getTouchedSpotIndicator: (barData, spotIndexes) {
          return _touchIndicator(
              barData, spotIndexes, primaryColor, scaffoldColor);
        },
      ),
      gridData: FlGridData(
        show: true,
        horizontalInterval: interval == 0 ? 1 : interval,
        verticalInterval: points.length / 4,
        drawVerticalLine: true,
        getDrawingHorizontalLine: (value) {
          return FlLine(color: dividerColor, strokeWidth: 1.0);
        },
        getDrawingVerticalLine: (value) {
          return FlLine(color: dividerColor, strokeWidth: 1.0);
        },
      ),
      titlesData: FlTitlesData(
        topTitles: AxisTitles(sideTitles: SideTitles(showTitles: false)),
        bottomTitles: AxisTitles(
            sideTitles: SideTitles(
          showTitles: true,
          reservedSize: 10,
          interval: points.length / 4,
          // checkToShowTitle:
          //     (minValue, maxValue, sideTitles, appliedInterval, value) {
          //   if (minValue == value) return false;
          //   if (maxValue == value) return false;
          //   return true;
          // },
          getTitlesWidget: (value, meta) {
            if (meta.min == value) return Container();
            if (meta.max == value) return Container();

            var index = value.toInt();
            var result = '';
            if (range == MarketHistoryTimeRange.twentyFourHours) {
              try {
                result = DateFormat.jm(Platform.localeName).format(
                  points[index].time.toLocal(),
                );
              } catch (e) {
                result = '';
              }
            } else {
              try {
                result = DateFormat.Md(Platform.localeName).format(
                  points[index].time.toLocal(),
                );
              } catch (e) {
                result = '';
              }
            }
            return Text(
              result,
              style: TextStyle(
                color: captionColor,
                fontWeight: FontWeight.normal,
                fontSize: 9,
              ),
            );
          },
        )),
        leftTitles: AxisTitles(
          sideTitles: SideTitles(
            showTitles: false,
            reservedSize: 26,
            getTitlesWidget: (value, meta) => Text(
              value.toString(),
              style: TextStyle(
                color: captionColor,
                fontWeight: FontWeight.bold,
                fontSize: 9,
              ),
            ),
            interval: interval == 0 ? 1 : interval,
          ),
        ),
        rightTitles: AxisTitles(
            sideTitles: SideTitles(
          showTitles: true,
          getTitlesWidget: (value, meta) => Text(
            _legendPriceFormatter(value).format(value),
            style: TextStyle(
              color: captionColor,
              fontWeight: FontWeight.normal,
              fontSize: 9,
            ),
          ),
          interval: interval == 0 ? 1 : interval,
          reservedSize: 28,
        )),
      ),
      // minY: smallestPrice * 0.99,
      // maxY: largestPrice * 1.1,
      borderData: FlBorderData(
        show: true,
        border: const Border(
          bottom: BorderSide(
            /* color: Colors.grey[200], */
            color: Colors.transparent,
          ),
          left: BorderSide(
            color: Colors.transparent,
          ),
          right: BorderSide(
            color: Colors.transparent,
          ),
          top: BorderSide(
            color: Colors.transparent,
          ),
        ),
      ),
      lineBarsData: ChartLinesHelper.getLines(points, selectedCurrency),
    );
  }

  static List<TouchedSpotIndicatorData> _touchIndicator(
    LineChartBarData barData,
    List<int> indicators,
    Color primaryColor,
    Color scaffoldColor,
  ) {
    return indicators.map((int index) {
      final flLine = FlLine(
        color: primaryColor,
        strokeWidth: 1.0,
        dashArray: [1, 2],
      );

      final dotData = FlDotData(
          getDotPainter: (spot, percent, bar, index) => FlDotCirclePainter(
                radius: 4.0,
                color: primaryColor,
                strokeColor: scaffoldColor,
                strokeWidth: 1,
              ));

      return TouchedSpotIndicatorData(flLine, dotData);
    }).toList();
  }

  static NumberFormat _legendPriceFormatter(double value) {
    var formatter = NumberFormat.compactCurrency(
      locale: 'en-us',
      decimalDigits: 2,
      symbol: '',
    );

    return formatter;
  }
}

We changed it in the 0.50.0, now we have getTitlesWidget which you can return a simple Container() when you don't want to show the title.
You can read the migration guide here

We changed it in the 0.50.0, now we have getTitlesWidget which you can return a simple Container() when you don't want to show the title.
You can read the migration guide here

Hi, thx for your response.
Yes I saw that and changed my code already but I cant make it work the way I want. I want to add one label at the top, one at the bottom and two between with the same range between. Is that currently possible?

You need to do some custom calculations to achieve that.

You need to do some custom calculations to achieve that.

Im not sure how the calculations should look like.
This would be a nice option since it looks like its more complicated.

Hi, I happen to have a similar problem when migrating from v2.3.1 to v3.0.2 where we calculate the interval by
(maxY-minY)/number_of_interval_desired.
v2.3.1

v3.0.2

May i know why the change is being implemented? Thanks.

@encikpulasan
Because we changed rendering titles from only text to any widget. That's why that property is removed. You can pass an empty Container() to hide each text that you want.

@imaNNeo  I found that the grid generated are not even, the first line after minimum value is less than the interval value. I'm having issue with this since i can't set the label and grid line correctly as i wanted.
You can see the difference from the images i shared above. Thanks.

@encikpulasan how did you resolve this?

Ok I have found this issues lessens when I use values greater than 1, my values were very small but multiplying them by 1000 helped a lot

It seems we have a duplicate issue. So I will keep the older one which is #906


Process recycling leads to defunct process

After running for a while process start to accumulate inside the docker container.
It seems that the openoffice process does not exit properly and survives as defunct
See the process here after around 3 month work:
# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
[...]
root        37     1  0  2019 ?        00:00:00 [soffice.bin] <defunct>
root        49     1  0  2019 ?        00:00:00 [soffice.bin] <defunct>
root        64     1  0  2019 ?        00:00:00 [soffice.bin] <defunct>
root        96     1  0  2019 ?        00:00:00 [soffice.bin] <defunct>
root       107     1  0  2019 ?        00:00:00 [soffice.bin] <defunct>
root       122     1  0  2019 ?        00:00:00 [soffice.bin] <defunct>
root      1532     1  0 Mar01 ?        00:00:00 [soffice.bin] <defunct>
root      1543     1  0 Mar01 ?        00:00:00 [soffice.bin] <defunct>
root      1558     1  0 Mar01 ?        00:00:00 [soffice.bin] <defunct>

Log analysis shows that new process are started with PID = previous +2
# grep "pid:" /var/log/app*
/var/log/app.log:2019-07-04 09:52:50.419 DEBUG 1 --- [ProcessThread-0] o.j.process.AbstractProcessManager       : Command line matches! Returning pid: 39
/var/log/app.log:2019-07-04 09:52:50.803 DEBUG 1 --- [ProcessThread-0] o.j.process.AbstractProcessManager       : Command line matches! Returning pid: 66
/var/log/app.log:2019-07-04 09:52:51.195 DEBUG 1 --- [ProcessThread-1] o.j.process.AbstractProcessManager       : Command line matches! Returning pid: 98
/var/log/app.log:2019-07-04 09:52:51.555 DEBUG 1 --- [ProcessThread-1] o.j.process.AbstractProcessManager       : Command line matches! Returning pid: 124
/var/log/app.log:2020-03-01 10:08:29.952  INFO 1 --- [ProcessThread-1] org.jodconverter.office.OfficeProcess    : Trying to forcibly terminate process: 'host=<IP_ADDRESS>,port=2003,tcpNoDelay=1'; pid: 124
/var/log/app.log:2020-03-01 10:08:31.432 DEBUG 1 --- [ProcessThread-1] o.j.process.AbstractProcessManager       : Command line matches! Returning pid: 1534
/var/log/app.log:2020-03-01 10:08:31.794 DEBUG 1 --- [ProcessThread-1] o.j.process.AbstractProcessManager       : Command line matches! Returning pid: 1560
/var/log/app.log:2020-03-02 15:26:22.728 DEBUG 1 --- [ProcessThread-0] o.j.process.AbstractProcessManager       : Command line matches! Returning pid: 2498

My understanding is that the app detects the crash and restarts a new process. The issue is that this crash does not kill the old process

I'am not sure this would be the right place to discuss it, since this is not docker-image container related, it should got to https://github.com/sbraconnier/jodconverter since the implementation to spawn or kill processes is in there

You should also be aware that this is not really production ready, but as stated in the readme, https://github.com/EugenMayer/officeconverter should be - it does the same but it is not build as an example in that regard. Still, the issue you discovered could occur there too, IMHO


Various fixes

Changing to @Ajb2307's favicon. Fixing the issue causing server-side error if a user tries to download a non-result, whilst prompting users to raise an issue for missing data. This will additionally close #148. Send the various search options to GET instead of POST, so we can track what users are trying to do. Note this doesn't apply for the coordinate query and sql query, as those require a validation stage. Redirects people using previous bookmarks like fulltextsearch to full_text_search. Reworking of containers on all pages to have more dynamic datatables, improving the general look of the site, most notably the solo_result page.

Change to Please open an issue


GRU does not support quantification

Describe the issue:
Environment:

NNI version:2.9
Training service (local|remote|pai|aml|etc):colab
Client OS: linux(colab)
Server OS (for remote mode only): colab
Python version: python 3.7.15
PyTorch version:1.12.1+cu113
Is conda/virtualenv/venv used?:
Is running in Docker?:no

How to reproduce it?:
import torch
from torch import nn

from nni.algorithms.compression.pytorch.quantization import NaiveQuantizer

class DemoModel(torch.nn.Module):
    def __init__(self):
        super().__init__()
        self.linear = nn.Linear(5, 5,bias=True)
        self.gru = nn.GRU(input_size=5,hidden_size=5,bias=True,)
        self.relu = nn.ReLU()

    def forward(self, x):
        x = self.linear(x)
        x = self.gru(x)
        x = self.relu(x)
        return x

model = DemoModel()
config_list=[{
    'op_types': ['Linear'],
    'quant_types': ['weight'],
    'quant_bits': {'weight': 8}
},
{
    'op_types': ['GRU'],
    'quant_types': ['weight'],
    'quant_bits': {'weight': 8}
},
# {
#     'op_names': ['fc1'],
#     'quant_types': ['input', 'weight'],
#     'quant_bits': {'input': 8, 'weight': 8}
# }
]
quantizer = NaiveQuantizer(model,config_list).compress()

[2022-10-26 02:30:02] WARNING: Module gru does not have parameter "weight"
WARNING:nni.compression.pytorch.compressor:Module gru does not have parameter "weight"

hello @LXP-Never , NNI only support compressing Module which has attribute weight, and I find in torch.nn.GRU, there is no weight, but has 'weight_ih_l{}{}', 'weight_hh_l{}{}'.
https://pytorch.org/docs/stable/_modules/torch/nn/modules/rnn.html#GRU
Fortunately, NNI is planning to support compressing any parameters, buffers, inputs and outputs in the Module, this feature will be implemented in 3.0 at the earliest and 3.1 at the latest.


Slugs with different attributes for each locale?

I used a method to generate localized slugs like this
slug :generate_slug, localize: true

def generate_slug
    "#{first_name} #{last_name} #{speciality} #{city}"
end

And I have a first_name_ar and last_name_ar attributes for the arabic version of the user's name, is there an option to use them to generate the arabic version of the slug?
Something that goes along the way of this :
def generate_slug
   return "#{first_name_ar} #{last_name_ar} #{speciality} #{city}" if I18n.locale=="ar"
   "#{first_name} #{last_name} #{speciality} #{city}"
end

I think I am missing the point of your question - you can generate different slugs conditionally just like you did above. What would you like the actual slug used in the database to look like here? Are you generating an Arabic slug and getting a transliterated English result and that is the problem?

@dblock the snippet that I proposed above does not work, it always gives the default behavior to  "#{first_name} #{last_name} #{speciality} #{city}" without taking into account the locale,.. I also encountred the problem that you mentioned, I always get the transliterated English result instead of the arabic slug.

Put some debug code in there, is the locale correct? There's no reason why that wouldn't work, maybe you want to provide a minimal piece of code that shows the output that we can run?
The transliterated English is built-in and is implemented in UniqueSlug, you would have to swap that out to do something else. Before we dig up how to do that, consider whether that's really what you want - UTF8 URLs don't read well, defeating most of the purpose of this library.

@dblock Thanks for your help, I ended up using the same old links with juste some minor tweaks to show the page in the correct locale. closing this for now ...


오류 : the file will have its original line endings in your working directory

the file will have its original line endings in your working directory <-- 라는 오류가 발생
해결 방법은 ?

git config --global core.safecrlf false <-- 을 입력


Updates to version 1.2.1

contains updater function for https://github.com/code-kern-ai/refinery-gateway/pull/42, which adds the foreign key attribute id to the embeddings table

[ ] discuss how the next version will be called and change the function name accordingly

[ ] update the model after the model pr has been merged


controller: Return a more descriptive error for duplicate deployment.

Signed-off-by: Blaž Hrastnik<EMAIL_ADDRESS>

@titanous Updated.

Please add a test for this.

LGTM.


Update links to Go's 'Code Review Comments'

Summary
This article was moved out of the language's repo's wiki into a hosted wiki article. Updating the links.
Previous location: https://github.com/golang/go/wiki/CodeReviewComments
New location: https://go.dev/wiki/CodeReviewComments
CLA signed.

Hello @Celeo,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


Design guidelines on MenuSuites

Where to place departments and menu items
Hello,
I have been reading the content regarding Menusuites in the following link:
https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2013r2/jj128065(v=nav.71)
As I see it the content only explains how to create and modify Menusuites and not design guidelines itself.
I am looking for design guidelines on how to structure and where to place departments and individual menu items.
Do you have any documentation on this?
Thanks in advance.

@MortenKSorensen The content has been retired. It will not be updated in the future.

Thank you for the reply.
Do Microsoft have any materiales on this?
Retired or not.

I am following up with content owner and will get back soon.

Hi @MortenKSorensen - the latest version is published here but might not give you what you're looking for either: https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2015/jj128067(v%3Dnav.80)
The Design team are working on a new version based on the new design that we are rolling out with the next version this Fall. Their key advice is to focus on the Role Center and less on the Menu Suite. That's the thinking behind the design principles here: https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2015/jj128066(v%3Dnav.80)
I'm taking your questions to the team (I'm not a member of that team, but I sit close to them :-)) so they can make clearer recommendations in the update later this year.
I know this probably doesn't answer your question, but it's the best I can do right now. If you have access to the Dynamics Learning Portal, you'll be able to find material about the RoleTailored design that might be closer to your question.


npm ERR! Error: socket hang up

npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm info addNamed [ 'express', '' ]
npm ERR! Error: socket hang up
npm ERR!     at createHangUpError (http.js:1092:15)
npm ERR!     at CleartextStream. (http.js:1175:27)
npm ERR!     at CleartextStream.emit (events.js:88:20)
npm ERR!     at Array.0 (tls.js:731:22)
npm ERR!     at EventEmitter._tickCallback (node.js:192:40)
npm ERR! Report this entire log at:
npm ERR!     http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>npm ERR!
npm ERR! System Linux 3.0.0-12-generic
npm ERR! command "node" "/usr/local/bin/npm" "install" "express" "-d"
npm ERR! cwd /home/leisure/software/node-v0.6.2
npm ERR! node -v v0.6.2
npm ERR! npm -v 1.0.106
npm ERR! code ECONNRESET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/leisure/software/node-v0.6.2/npm-debug.log
npm not ok

see also:
https://github.com/isaacs/npm/issues/718
https://github.com/isaacs/npm/issues/1308
https://github.com/isaacs/npm/issues/1346
but the problem still here,can someone help me?

I'm seeing the same, with exactly same versions.
I'm behind a non-authenticated proxy.
Wireshark revealed that npm was sending some binary data to the proxy, which responded (on the wire) with plain text 400.
As a workaround, this worked for me:
npm config set registry http://registry.npmjs.org/
Something funny with the proxies and https?

it works ok!thanks.I think my https_proxy is broken~
npm config set registry http://registry.npmjs.org/

Had to do the same thing here.

Ditto.  'npm config set registry http://registry.npmjs.org/' worked for me too.  However it's tinyproxy and it works well with other HTTPS client applications I use...  So maybe it should be reopened.

I have had the same problem but I can't afford to change registry since I am using a corporate registry with our own librries. Has anyone found another workaround ? I have asked my specific question here : https://stackoverflow.com/questions/49055140/npm-3-10-10-install-socket-hang-up-error
Thanks for you help !


Choose a sort order for Bar Graph

Similar to #303, it would be helpful if we could choose a sort order for the items listed in a bar graph.
For example, sort in ascending or descending order by:
• name
• value (percentage or quantity)

Hi @samuraijane , thanks for opening an issue!
This seems legit, it will make totally sense to add this feature. It should also work and have a similar API as the Donut chart.
Thanks!

Fixed by Daler with #415


Updating ICP page with new AWS quick start and latest links

I updated our ICP page to include the new AWS Quick Start. I also updating IBM Knowledge Center links to go to our latest version 3.1.2. I also alphabetized our headings and Terraform modules.

/assign @bradtopol

Great job!
/lgtm
/approve


NoTouchID.kext aded

In a hope that it solves the Sleep/Wake problem, added NoTouchID.kext

This did not work. Anyway, just merging with master for the sake of it.


CHEBI:52101 wrong sum formula, mass

The InChi/key/SMILES of CHEBI:52101 are consistent and coincide with the displayed structure, while the sum formula and mass differ. Can you please have a look?

Now corrected. Thanks


Web development - added a youtube channel link

IMPORTANT: When creating your Pull Request, please use the following format for the title: Category - Resource Name & Section
Category - Web development

Please follow these steps to create the PR title correctly:

Replace "Category" with the relevant category, such as Web Development or UI & UX Design.
Replace "Resource Name & Section" with the specific name of the resource and the relevant section where it belongs. For instance, you could use something like Web development - CSS Portal & Tools or Web development - Leetcode & Challenges.

Fixes Issue

https://www.youtube.com/watch?v=bMknfKXIFA8
Description:

Added a YouTube channel link (Web development)
Resource URL:

[https://www.youtube.com/watch?v=bMknfKXIFA8]
Checklist:
Before submitting your pull request, ensure that you have completed the following tasks:

[x] I have carefully reviewed and adhered to the contributing guidelines before creating this pull request.
[x] I followed the prescribed PR title template. (Check this if you're adding a resource)

@lr2120, please can you help me with this PR?

Hi, what kind of help do you need specifically. Would you like me to write you a description for this video. How about this?
Dive into this comprehensive React tutorial by FreeCodeCamp.org, a renowned platform offering a multitude of free resources for aspiring developers.

On Oct 12, 2023, at 8:24 PM, Joseph Martin @.***> wrote:
@jfmartinz commented on this pull request.
In Web Development/README.md https://github.com/jfmartinz/ResourceHub/pull/66#discussion_r1357594908:

@@ -348,6 +348,11 @@ to everyone - everywhere!
Hitesh Choudhari is a YouTube channel that offers various courses on programming languages. It is one of the best channel to learn web development at free of cost.

   https://www.youtube.com/watch?v=bMknfKXIFA8FreeCodeCamp

Hello @RitaDee https://github.com/RitaDee It looks good but the problem is that freeCodeCamp youtube channel exist already, change it to something else and then I will merged once youre done.
⬇ Suggested change

   https://www.youtube.com/watch?v=bMknfKXIFA8FreeCodeCamp

   https://www.youtube.com/watch?v=bMknfKXIFA8FreeCodeCamp

—
Reply to this email directly, view it on GitHub https://github.com/jfmartinz/ResourceHub/pull/66#pullrequestreview-1675460221, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACMZQUVETQOWVMDAWDG3YODX7CC5FANCNFSM6AAAAAA556DTKE.
You are receiving this because you were mentioned.


Underwater reflection color

Information

Unity 2019.3.7f1
Built-in rendering pipeline
Crest v10.0.0
Platform: Windows 10
GPU: Intel UHD graphics 630

Bug description
Hello,
I noticed that from Crest v8.0.0 and forwards, the underwater reflections are displayed with wrong color (reddish). I notice this issue in the "main" scene from Crest examples v10.0.0 and when I include the Ocean Renderer in my own scene. You can see the issue in the below screenshot.

Any help would be appreciated.
Thank you.

Are you talking about the caustics? The texture was changed to a coloured one. The source file shows links to the original
https://github.com/crest-ocean/crest/blob/master/crest/Assets/Crest/Crest/Textures/Caustics/SOURCE.txt

Are you talking about the caustics?
Yes.
So, the expected behavior is for them to be displayed like this?

Yes. Ever since version 9.0.0.


[fix][test] Fix DeadLetterTopicTest.testDeadLetterTopicWithInitialSubscriptionAndMultiConsumers

Fixes #23542
Motivation
The original receiverQueueSize was 100, and the producer generated a total of 100 messages. It is possible that all messages were put into the dead letter queue by one consumer, resulting in assertion failure.
Modifications
Reduce the size of the receiverQueueSize to ensure that every consumer processes the message.
receiverQueueSize ：100 -> 20
Verifying this change

The last test was manually cancelled.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.27%. Comparing base (bbc6224) to head (e7dfcbf).
Report is 716 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #23552      +/-   ##
============================================
+ Coverage     73.57%   74.27%   +0.70%
- Complexity    32624    34316    +1692
============================================
  Files          1877     1943      +66
  Lines        139502   147050    +7548
  Branches      15299    16209     +910
============================================
+ Hits         102638   109223    +6585
- Misses        28908    29386     +478
- Partials       7956     8441     +485

Flag
Coverage Δ

inttests
27.31% <ø> (+2.73%)
:arrow_up:

systests
24.35% <ø> (+0.03%)
:arrow_up:

unittests
73.65% <ø> (+0.81%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 649 files with indirect coverage changes


FirstOrCreate runs AfterFind hook and stops on error

GORM Playground Link

https://github.com/go-gorm/playground/pull/272
Description
The FirstOrCreate should actually check if there are any rows in the db, and if it exists then run AfterFind else create the row first.

In my case however the function returns error because it runs AfterFind() before creating the row, and thus panics "Unknown related entity for entity task : "
It does not run BeforeCreate at all

FYI... I think in FirstOrCreate the AfterFind is called even if there is no rows returned, and if we have any field updation on AfterFind() it gets done too : which gets reciprocated on BeforeCreate/BeforeSave.... I believe this is an unwanted behaviour @jinzhu

https://github.com/go-gorm/playground/pull/272

Firgured out this is a problem with Find as well as FirstOrCreate... Essentially AfterFind should not run if there are no rows affected after find query
@jinzhu

https://github.com/go-gorm/playground/pull/272

Fixed, thank you for your report.


Add support for media keys (keybinding shows "unknown" for key "back" and "forward")

The same keyboard configuration works on my QtCreator but not VSCode.
The support for other keys also not good, such as "Home" and "Email".

VSCode Version:

Version 1.21.1
Commit 79b44aa704ce542d8ca4a3cc44cfca566e7720f1
Date 2018-03-14T14:46:30.761Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

OS Version:

Linux 4.14.31-1-MANJARO #1 SMP PREEMPT x86_64 GNU/Linux
Distributor ID: ManjaroLinux
Description:    Manjaro Linux
Release:        17.1.7
Codename:       Hakoila

Screenshots:

@alexandrudima Does it mean this bug will not be implemented for VSCode?

sorry, I do not have such a keyboard anymore.


Cant connect Adafruit ESP32 Huzzah

Going off the Esp32-lwmqtt sample I am trying to connect my Adafruit ESP32 Huzzah board. Previously I had it working with using a RSA256 key that I would get from an AppEngine endpoint but I want the device to be able to generate the JWT to remove the app engine endpoint call.
I used openssl to create the public/private ec.pem keys
Replaced the private_key_str with the priv value from running the command
openssl ec -in ec_private.pem -noout -text
When I run the program I print the JWT to serial and put it in jwt.io and it says the JWT has a "Invalid Signature" so naturally the mqtt library kicks back saying back username or password.
Did I miss something?
Also what is the root_cert used for? I dont see it being used anywhere in the esp32 files

Hi @tyczj I am trying to compile the lwmqtt example correctly too. But, I have this problem when I executed it.

Does you know how to solve it?
I don't have the error you have mentioned, so I don't know how to solve it.

Go lwmqtt guthun page , you can find in their error list readme

Hi @Gior80 ,
Do you refer to this link:
https://github.com/GoogleCloudPlatform/google-cloud-iot-arduino/blob/master/README.md ?

https://github.com/256dpi/lwmqtt/blob/master/include/lwmqtt.h#L243
https://github.com/256dpi/lwmqtt/blob/master/include/lwmqtt.h#L11

Back to my issue....
To rule out the known issue of

Some private keys do not correctly encode to the Base64 format that required for the device bridge. If you've tried everything else, try regenerating your device credentials and registering your device again with

I went a created new public/private ec keys and I still have the issue

Fixed my issue, I missed configuring the time before creating the JWT


Escape "$file" in the warning message.

Fix https://github.com/fisherman/fisherman/issues/389

Oops!

@igrep LOL


--dapr-http-read-buffer-size in the docs but not implemented

Expected Behavior
According to the docs, it should be possible to set the read buffer size with the flag --dapr-http-read-buffer-size.
Actual Behavior
The flag doesn't seem to exist: https://github.com/dapr/cli/blob/master/cmd/run.go#L351-L368
Steps to Reproduce the Problem
Using the flag --dapr-http-read-buffer-size is not recognized

/assign


Empty Communities

Some communities show up as empty, zero members, zero users, no description and the icon isn't loading.
Here's what it looks like on riot-anroid: https://img.ourl.ca/Screenshot_Riot.im_20180321-160304.png
And here from riot-web: https://img.ourl.ca/Screenshot_2018-03-21_16-04-05.png

Having the same issue. The group and the user who is seeing only zeros are on the same homeserver.

I have the same issue.
Account A on my Homeserver can't see the content of communityX on my Homeserver.
Account B on matrix.org can't see the content of the community

I have the same issue.
Account A is an Account on my Homeserver (Synapse 0.28.0).
Account B is an Account on matrix.org.
Community X is a Community on my Homeserver.
Community Y is a Community on matrix.org.
A can't see the Content of X, when using riot-android.
B can't see the Content of X, when using riot-android.
A can see the Content of Y, when using riot-android.
B can see the Content of Y, when using riot-android.

Hi ! Exactly the same issue for my own homeserver. I think there is 2 possibilities :

There is something wrong into the homeserver.yaml file
There is something wrong into riot-android
Maybe the both in the same time, maybe not... :)


[#56 #57] Fix building on windows

Do not use File.Separator for java resource paths
Use File.Separator for a unit test

Confirmed building on Windows Server 2012 R2 w/ 1.8.0u141 works correctly


Vue 3 and Typescript Problem

Hello mate, thanks for repo. I could not add this plugin to my vue 3 + typescript project. Can you add main.ts import example please ? thanks in advance :)
import { createApp } from "vue";
import App from "./App.vue";
import router from "./router";
import store from "./store";

createApp(App)
  .use(store)
  .use(router)
  .mount("#app");

I wrote the types file, can you post the code where you are getting the error?

Duplicate of #39


CVE-2021-44906

Hi @tracyboehrer, we reviewed the project and the minimist package is being resolved to the suggested version. Do you still see this alert?


Allow calendar wrapper to extend outside its container.

The calendar is tricky to use in a modal right now because it won't use the full screen real estate if it is contained within an element.
You can see what I mean here.

The way I've seen other calendars solve this is to have an optional "detached" mode where the calendar element re-parents itself to the div specified in the option.
Not sure if you have a better idea of how to solve this?

Btw position: fixed in dev-tools immediately fixes this. Is that an oversimplification?

Hey @antony  - I have been able to workaround this type of thing with overflow: visible on the parent.  I think this is probably the cleanest solution but if it doesn't work for you it might be helpful to see a reproduction of your specific issue (with whichever CSS you're using for your modal).

In the end I replaced my modal - but I needed to keep overflow: scroll on the parent as it is a modal and sometimes the content won't fit on the screen.

I can see the issue with this now. On a large screen the datepicker sits right in the middle with:
position: fixed
The way to fix it is to remove top and left from .contents-wrapper. Not sure what other issues this might cause though.

I have the same issue. the component sits on a sidebar which has overflow set to scroll (there is a long list). so you cant see the whole calendar.


Keyref resolution fails if input path contains ../

2.2.3 and develop.
If you do e.g. dita -i ../docsrc/userguide.ditamap -f pdf, keyref resolution fails:
[keyref] file:/tmp/docsrc/index.dita:6:55: [DOTJ047I][INFO] Unable to find key definition for key reference "release" in root scope. The href attribute may be used as fallback if it exists

If you do dita -i docsrc/userguide.ditamap -f pdf instead, it works fine.

Main should normalize path argument values.

Yeah, calling getCanonicalPath() instead of getAbsolutePath() fixes the issue.

Or, we could use java.nio.file.Path as it's the preferred way to work with paths in Java 7.


Fixed 2gp to call installer scripts

Critical Changes
Changes
Issues Closed
New Metadata
Unpackaged Metadata
Deleted Metadata
Testing Notes
Run qa_org_2gp against a prerelease org shape.

DO NOT merge until further notice.

DO NOT merge until further notice.

We should be able to merge this now.

@MatthewBlanski looks like the merge conflicts still persist

This is a false positive. Not sure why it's identified...
Matthew Blanski
Lead Member of Technical Staff
Salesforce - Salesforce.org
C:<PHONE_NUMBER>
On Tue, Feb 9, 2021 at 4:45 PM Xinnan Li<EMAIL_ADDRESS>wrote:

@MatthewBlanski https://github.com/MatthewBlanski looks like the merge
conflicts still persist
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SalesforceFoundation/k12-architecture-kit/pull/307#issuecomment-776294853,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK35XDGQKU2YHJWRK33R73DS6G3HXANCNFSM4XBW6D7Q
.


Develop

The genbank parser issues diagnostic messages to stderr; their presence does not signal a failed transform. Standard practice is to catch a non-zero return code as the indicator of a failed transformation.
The python change here cause the transform to succeed as long as it gets a zero return from the parser.
The java change causes the parser to issue a nonzero exit code when it catches an exception during parse.
@realmarcin this touches your code as well.

Looks good, merging now.


Adding check that EditContext is supported before using it

Check EditContext is supported

CI failing, looking into it


submodule update failed

Hi, when I updated submodule, it said that:
fatal: clone of 'git@github.com:sean93park/freertos.git' into submodule path 'freertos' failed
Thanks

Same here, I could not update the submodules.


create separate stylesheet

@adithyapaib i wanted to create stylesheet to Index.html so that things are managed well.
Please assign it to me

@adithyapaib Please review my PR #226


Bug: Escrow Account from common is failing to filter the correct address

Describe the bug
Escrow Account eventual is using the indexer address as filter and the way graph-node works, everything is supposed to be lowercase

This is already lowercase:
https://github.com/graphprotocol/indexer-rs/blob/1966049e5552eab5aca84f6e49879d3fe1a8db98/common/src/escrow_accounts.rs#L170
Do you have more details about the issue?

Having trouble reproducing the issue, the gist is that Escrow query returned empty array (no accounts) when I expected at least one for the indexer.
I can file an issue if it pops up again.

Cannot reproduce for now


Wrap instructions are no longer removed from the configuration if the jar file matches #53

Alright, I will merge this PR and fix the problem I mentioned in the comment... should release this soon.


Head/foot/side

Added the asked features for the head, foot, and side. All of them are in separete files and tested the ng-includable with the main.html

Do you mind telling me that command for git

So where do you want me to move the files ?


Preview geometry faces not shown inside transparent geometry

this will be the same thing as "multiple transparent objects viewed through each other doesn't work"
also effects lines,

as far as i know this is unfixable,
(is possible in opengl but dont think the replacement of the fixed pipeline is possible in webgl)


Fixes HaveValue method when type is a class

Fixes #172
As == and .Equals() can bring some different results depending the code written and/or overrides, I added one extra null comparison step before the current checking.

Great thank you!


Cancellable handler

I had an idea this morning based on the changes in #546, so I thought I'd see how far I could get with it and submit a PR for discussion.
In the event that the issue that lead to #546 occurring and tasks to process messages back up, it's possible that a task to process a message may be trying to process a message that was received so long ago that the message visibility timeout has expired and it is now a potential duplicate waiting to be processed.
If the handler had a CancellationToken that cancels after the approximate message visibility timeout expires, JustSaying could enable two behaviours:

It could self-cancel trying to do anything with the message before getting to the handler and abandoning it (potentially just extending the visibility instead, but I've not done that here).
The handler, when called, could observe the cancellation token itself and make a decision about what to do with the message. It could return false to send it back to the queue (where it could have since been handled elsewhere anyway), or it could return true on the basis, if this has expired I'll just ignore it and pretend I've dealt with it.

This is implemented here by adding the ICancellableHandlerAsync<T> interface that derives from IHandlerAsync<T>, and then plumbing it in appropriately so it's used if implemented by the handler for a particular message and extending things like the exactly-once handler and stopwatch wrappers.
Replaces #549.

Just to add another option, it could renew the message visibility timeout: https://github.com/justeat/JustSaying/issues/291
This is what Rebus does, and kind of what I'd expect by default for this type of library.

To be honest I thought we already had that capability, so I've re-opened it. It's also something we'd probably want as opt-in?
However, that's not what I was trying to achieve here. This is more of a reaction to a backed-up local queue (see #546).
In the event of messages being sat on scheduled Tasks waiting to progress and not being processed, the chances are AWS has already considered the message "lost" and redelivered it somewhere else. By that point if the task does eventually run, it's probably dealing with what is now a duplicate, and a waste of processing. By observing the fact the timeout has probably elapsed, we can just not process the message at all and end the Task and release some resources back to the worker to try and make some headway through the queue.
In that scenario, renewing the message visibility timeout would probably make things worse as it would leave messages on a backed-up local queue even longer?

I would expect an "auto-renew" to be on by default, but you'd certainly want control. This is something that the PE team needed a long time back for their deployment tool, so we exposed the RecieptHandle on the messages so they could do it themselves.
I happen to have the opposite view to you on this 😄, I think it more directly solves the problem of local queues holding stale messages. Cancelling sounds more haphazard as a general pattern here. If one worker has the message, it has a duty to process it, and if it doesn't it will eventually become visible to others.
I could see that cancelling before a handler gets the message would solve your problem, but adding cancellation to handlers feels wrong from an event-driven architecture perspective. If a hander is still working as (or soon before) a message visibility times out, it should let others know it's still working on it. It's "at least once" message delivery after all, cancellation doesn't belong here.

But here, the cancellation is pre-handler. Once control is passed to the handler, it's just as it is today, except you have to opt-in to implementing the new interface, and then have to decide to observe the token to do something different in your handler implementation.
This is just trying to improve the situation where the internals get stuck in a never-progressing backlog (which is what we had in the issue that lead to #546 as the Task queue was backing up) by never calling the handler in the first place.
If we wanted to do something to allow renewing the message visibility, I think that's something else that would need to be a first-class concept somewhere in the handlers to give you the hook to decide to renew/extend the visibility after the handler has already seen the message to make a decision.
Maybe that could be morphed into a more detailed handler concept that did both separately, so for more advanced scenarios you'd get like this very-of-the-top-of-my-head thing:
public interface ISuperDuperHandler<in T>
{
    Task<bool> HandleAsync(HandlerContext<T> context);
}

public abstract class HandlerContext<T>
    where T : Message
{
    public CancellationToken CancellationToken { get; protected set; }

    public T Message { get; protected set; }

    public MessageContext MessageContext { get; protected set; }

    public abstract async Task ExtendVisibilityAsync(TimeSpan value);
}

internal sealed class SuperDuperHandlerContext<T> : HandlerContext<T>
    where T : Message
{
    private _client;

    public SuperDuperHandlerContext(
        T message,
        MessageContext messageContext,
        SomeClient client)
    {
        Message = message;
        MessageContext = messageContext;
        _client = client;
    }

    public override async Task ExtendVisibilityAsync(TimeSpan value)
    {
        await _client.ExtendTheVisbilityAsync(Message.Id, value, CancellationToken);
    }
}

Then you could do stuff like this:
public class MyHandler : ISuperDuperHandler<MyMessage>
{
    public async Task<bool> HandleAsync(HandlerContext<T> context)
    {
        if (context.CancellationToken.IsCancellationRequested)
        {
            // Too old or shutting down, decide to junk it and let someone else handle it
            return false;
        }

        if (context.Message.IsMessageHuge)
        {
            await context.ExtendVisibilityAsync(TimeSpan.FromHours(1));
        }

        await DoExpensiveStuffAsync(context.Message);

        return true;
    }
}

Also want to add, I'm not saying that by default the behaviour is that messages are continually renewed in terms of visibility, there would be a configurable policy of how long / how many renews before giving up.

Ah, I was (or maybe still am) confused 😄
So if I understand you, ICancellableHandlerAsync<T> lets us build a pipeline that's cancellable, before calling the user provider handler.
If we want to let the user optionally know if the message had timed out, the cancellation token could lead to a little confusion, as the signature would imply that the ct is live, and you'd be expected to constantly check it and flow it for cooperative cancellation.

No, the interface would be to allow a developer to opt-in to doing something different in the handler if the message is considered "stale" or if the message loop is shutting down.
To me, visibility locks is a different feature for people who need to process messages that may take a long time to handle in the handler.
I don't think they're a solution to a backed-up internal queue that is operating with no context that could be potentially having messages lying around in memory that are dozens of minutes old.
Effectively this makes this PR two different, related, things in one:

If a message has been waiting to be passed to a handler since receipt for longer than the visibility timeout, don't bother trying to process (effectively, abandon it as if the service had crashed).
Provides a separate opt-in mechanism that allows a handler to decide to do different logic if the message loop has been requested to stop or if the message visibility timeout has lapsed.

To me, visibility locks is a different feature for people who need to process messages that may take a long time to handle in the handler.

The way I see it, JustSaying grabs a handful of messages and will use the processing strategy to decide when to call the handlers, it's its duty to try to guarantee correctness (within reason), in this case by dropping the messages (FIFO as this change is), or with re-acquiring visibility locks. This wouldn't need much further complexity than what is done in this PR, there is still the same timer involved. (I sense I won't sell you in the short term)
I see though that dropping the messages is a good solution, and is the minimal change. I'd add a suggestion of being able to add (or subtract rather) a buffer to the timeout, if I'm 0.1 seconds away from someone else picking up the message, and the timeout is 30 seconds, I'd probably want to still drop it.
On the opt-in behaviour, the only thing I don't like is the way it's presented, when I look at the ICancellableHandlerAsync<T> type I see a message handler with cancellation, not as you describe. I'd like to see it be a little more unambiguous, but I haven't had much sleep, so I could just be not seeing things clearly 😄

For some more reading in favour of extending timeouts, here's the guidance on the matter:
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/working-with-messages.html#processing-messages-timely-manner
The thing with dropping messages is that the messages being dropped will be mostly random, so it's very easy for messages to be dropped multiple times, exceeding the max receive count and ending up in a dead letter queue. If you extend locks, you generally get a much more ordered processing of messages, which will leave messages in queues where they are nice and safe.

I think it's worth comparing a prototype of that guidance, when a message is received at the earlier occasion we create a heartbeat that renews the lock, it would be configurable and defaults to half the timeout, and extends by the timeout.
So if it's 30 seconds, schedule a task in 15 secs to renew by 30 (45s accumulative), then again 15 secs later forever pushing out the lock until some overall timeout. Once the handler has completed, any heartbeat task is cancelled via a cts.
Waddaya say? I can have a bash and we can compare notes?

I'd be happy to drop the ICancellableHandler<T> part (though I think it's a nice addition) and just keep the "this has been sat around internally for too long" part.
If you want to try a different tack and raise a PR I'll take a look.

Thanks, I'll start work in a different PR (likely not today but soon).
Sorry if this sounds negative (you know I love your work ❤), but now I've considered it some more I think this PR should be closed, as it's trading off one problem for another an not really solving the issue, I hope my points in the previous comments have persuaded you too.

I'll re-review when I get the chance and see what could be removed to make it simpler but still provide a mitigation for a runaway Task queue, as ultimately that issue would have brought down the worker due to a memory leak.
Also waiting for anyone else to chip in with their thoughts 😄

In other news, sometimes a repo name tells a story...

Oh god, I've just encountered the same issue, what gives? The fork upstream link is gone from GH repos for JustSaying 😞


Const

https://github.com/1Mayuko1/Euro_Diffusion/blob/ab960c6015d6733bcdc82b7bc5bc59ef48cdaa51/lab1.js#LL114C38-L114C45
Consider using const

and here https://github.com/1Mayuko1/Euro_Diffusion/blob/ab960c6015d6733bcdc82b7bc5bc59ef48cdaa51/lab1.js#L132

https://github.com/1Mayuko1/Euro_Diffusion/blob/ab960c6015d6733bcdc82b7bc5bc59ef48cdaa51/lab1.js#LL237C34-L237C40

The problem has been solved, thanks for the comment


Code reload not working

Hello, thank you for open sourcing this project it is quite interesting and I want to learn more about it. I am facing some issues regarding the code reload, as described below.
Every time I do a change in data db/src/sample_data/data.sql as a specified here the stack breaks down. I start getting the following errors
OpenResty
│./db/src/sample_data/data.sql changed                                                                                │
│Starting code reload ------------------------                                                                                │
│Ready ---------------------------------------                                                                                │
│sed: /docker-entrypoint-initdb.d/libs/pgjwt/pgjwt-0.0.1.sql: No such file or directory                                                                                │
│psql:/Users/steveazzopardi/Code/github.com/SteveAzz/khumbuicefall/db/src/libs/auth/schema.sql:27: ERROR:  function pgjwt.sign(json, text) does not exist                                                                                │
│LINE 2:     select pgjwt.sign($1, settings.get('jwt_secret'))

pg-amqp-bridge
│thread '<unnamed>' panicked at 'internal error: entered unreachable code', /home/travis/.cargo/registry/src/github.com-1ecc6299db9ec823/postgres-0.14.2/src/notification.rs:155:17                                                                                │
│note: Run with `RUST_BACKTRACE=1` for a backtrace.

curl
$ curl -H "Authorization: Bearer $JWT_TOKEN" "http://localhost:8080/rest/todos?select=id,todo"
{"hint":null,"details":null,"code":"42P01","message":"relation \"api.todos\" does not exist"}⏎

I am running on latest master. Macos, latest stable docker version

sorry for the late reply, is this happening on a clean/new clone or did you change something in the init.sql file

Hello, sorry for the late reply myself. Yes, it was.

it works for me, here is a complete list of things i did from a clean dir
~/tmp$ mkdir example-api
~/tmp$ cd example-api
~/tmp/example-api$ git init
Initialized empty Git repository in /Users/ruslantalpa/tmp/example-api/.git/
~/tmp/example-api$ git remote add upstream https://github.com/subzerocloud/postgrest-starter-kit.git
~/tmp/example-api$ git fetch upstream
remote: Counting objects: 470, done.
remote: Total 470 (delta 0), reused 0 (delta 0), pack-reused 470
Receiving objects: 100% (470/470), 1.10 MiB | 184.00 KiB/s, done.
Resolving deltas: 100% (183/183), done.
From https://github.com/subzerocloud/postgrest-starter-kit
 * [new branch]      master     -> upstream/master
~/tmp/example-api$ git merge upstream/master
~/tmp/example-api$ docker-compose up -d
WARNING: The MAX_ROWS variable is not set. Defaulting to a blank string.
WARNING: The PRE_REQUEST variable is not set. Defaulting to a blank string.
Creating postgreststarterkit_db_1 ...
Creating postgreststarterkit_rabbitmq_1 ...
Creating postgreststarterkit_rabbitmq_1
Creating postgreststarterkit_db_1 ... done
Creating postgreststarterkit_postgrest_1 ...
Creating postgreststarterkit_rabbitmq_1 ... done
Creating postgreststarterkit_pg_amqp_bridge_1 ...
Creating postgreststarterkit_postgrest_1 ... done
Creating postgreststarterkit_openresty_1 ...
Creating postgreststarterkit_openresty_1 ... done
~/tmp/example-api$ curl http://localhost:8080/rest/todos?select=id,todo
{"message":"Database connection lost, retrying the connection."}~/tmp/example-api$
~/tmp/example-api$ curl http://localhost:8080/rest/todos?select=id,todo
[{"id":1,"todo":"item_1"},{"id":3,"todo":"item_3"},{"id":6,"todo":"item_6"}]~/tmp/example-api$

#####
this is where in another terminal window i executed
subzero dashboard

then changed item_1 to item_1 update
saved the file, then saw this in subzero cli
./db/src/sample_data/data.sql changed                                                                                Starting code reload ------------------------                                                                                Ready ---------------------------------------
#####
after getting back to the first window, i reexecuted the call and got the correct response

~/tmp/example-api$ curl http://localhost:8080/rest/todos?select=id,todo
[{"id":1,"todo":"item_1_update"},{"id":3,"todo":"item_3"},{"id":6,"todo":"item_6"}]~/tmp/example-api$

make sure you have the latest subzero-cli https://github.com/subzerocloud/subzero-cli

The issue seems to be because of me forgetting to install sqitch I'm sorry for wasting your time.
Thank you so much for helping me and for the hard work you put into this project 💯


Release v0.8.1

[Feature] Add $Null builtin.
[Feature] Add minLength option to ArrayType.
[Fix] Fix TsEnumType name.
[Fix] Restore assumeStringKey option for MapType.

Codecov Report

Merging #66 into master will increase coverage by 0.2%.
The diff coverage is 84.84%.

@@           Coverage Diff            @@
##           master     #66     +/-   ##
========================================
+ Coverage    75.1%   75.3%   +0.2%
========================================
  Files          58      59      +1
  Lines        1663    1697     +34
========================================
+ Hits         1249    1278     +29
- Misses        414     419      +5

Impacted Files
Coverage Δ

src/lib/writers/structured.ts
90% <ø> (ø)
:arrow_up:

src/lib/errors/min-array-length.ts
83.33% <100%> (ø)

src/lib/types/ts-enum.ts
92.85% <100%> (ø)
:arrow_up:

src/lib/types/array.ts
84.61% <80%> (+0.1%)
:arrow_up:

src/lib/types/map.ts
76.53% <85.71%> (+2.5%)
:arrow_up:

Continue to review full report at Codecov.

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


chat.langchain.com is not working, it keeps loading, even the website we created on top of it also not working

When i visit chat-langchain website it will provide result quickly however not its working its keep loading refer below image

3 days back it worked fine, now not sure why it's not woking.
Expected behaviour: For given prompt it should load data quicker

It worked fine yesterday, I think it is because of the updates released on the dev day.

Should be working now. There were a couple incidents from llm and embedding provider outages


Fix Component Governance Issues

Fix Issues raised by Component Governance

API change check
API changes are not detected in this pull request.


No sound when using raspberry pi 3b+, 2 mic hat.

I tried everything i could think of. I get no sound output when running the 2mic hat on the raspberry pi 3b+.
Its specifically linked to pulseaudio and the enhanced wyoming service. When running the standard wyoming service without the snapcast client, sound output is fine from the hat.
Pulse audio gives this error, however i cannot figure out how to fix it.
`
Jul 07 00:15:04 wyomingsatelite pulseaudio[563]: Failed to find a working profile.
Jul 07 00:15:04 wyomingsatelite pulseaudio[563]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-3f902000.hdmi" card_name="alsa_card.platform-3f902000.hdmi" namereg_fail=false tsched=yes fixed_latency_r>
Jul 07 00:15:07 wyomingsatelite pulseaudio[563]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Jul 07 00:15:07 wyomingsatelite pulseaudio[563]: Most likely this is a bug in the ALSA driver 'snd_bcm2835'. Please report this issue to the ALSA developers.
Jul 07 00:15:07 wyomingsatelite pulseaudio[563]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Jul 07 00:15:10 wyomingsatelite pulseaudio[563]: Failed to find a working profile.
Jul 07 00:15:10 wyomingsatelite pulseaudio[563]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-3f902000.hdmi" card_name="alsa_card.platform-3f902000.hdmi" namereg_fail=false tsched=yes fixed_latency_r>
`
When I use paplay /usr/share/sounds/alsa/Front_Center.wav the sound outputs fine.

i have the same issue and i followed the guide as is, the service ran successfully. but no sound.
however it works if start manually by issuing a command snapclient -h 192.168.xx.xx --player pulse:property=media.role=music --sampleformat 44100:16:*
so im not sure whats wrong
Start the client, used only by the init.d script
START_SNAPCLIENT=true
Additional command line options that will be passed to snapclient
note that user/group should be configured in the init.d script or the systemd unit file
For a list of available options, invoke "snapclient --help"
SNAPCLIENT_OPTS="-h 192.168.xx.xx --player pulse:property=media.role=music --sampleformat 44100:16:*"


Added Event details and Event Registration page #359

I added Event details to the page. Once the viewEvent button is clicked based on the specific event it will redirect to the details of that specific event which has details like title, image, description date, time, location details and a register button to register for the event. The page is designed with a responsive layout that adjusts based on the screen size, ensuring a good user experience on both desktop and mobile devices. JavaScript is used to dynamically populate event details from URL parameters, ensuring that the correct information is displayed based on user selection.
Once the register button is clicked it will redirect to EventRegister form, which is a well-structured, with labeled input fields for user information (name, address, email, city, and state). This makes it easy for users to fill out.
The event name, date, and location fields are read-only, ensuring that users can see the details of the event they are registering for without the ability to edit them.A "Submit" button allows users to send their registration information.
A "Back" button lets users return to the previous page without losing their entered data.
The form includes HTML5 validation (e.g., required fields) to ensure that users provide necessary information before submission. A simulated email sending function is included, which logs the event details to the console and shows an alert indicating that an email has been sent, providing feedback to the user.
The form automatically populates with event details from the URL, improving user experience by pre-filling relevant information based on the event selected. Consistent styling across both pages ensures a professional look, while media queries make the registration form responsive, adjusting padding and font sizes for smaller screens.
A JavaScript function (redirectToEventDetails) is defined for redirecting users to the event details page with all the relevant data encoded as URL parameters, facilitating smooth navigation between pages.

Please see the conflicts highlighted. Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


Fix for broken link to contributor's guide.

Maybe even add a link to Free Code Camp's new to open source guide?
Example:
For a list of resources for people who are new to contributing to open source, check out how to contribute to open source.

@sbtn Thank you for your contribution!


[BUG] Make logo in the header clickable link to the home page

Description
The logo in the header is not clickable. It have to be a link and should redirect to the home page.
Actual Behavior
The logo in the header is not clickable.
Expected Behavior
Make it a clickable link which redirects to the home page

Please assign this issue to me under GSSOC'24


Inquiry: ARM Compatibility for Puppeteer

Hello team,
I hope this message finds you well. I'm reaching out to inquire about the compatibility of Puppeteer with ARM architecture.
I've scoured through the documentation but couldn't find any explicit mention regarding ARM compatibility. To verify this, I conducted some tests by running Puppeteer within an ARM environment, specifically in a Docker container with Ubuntu as the base image. Surprisingly, Puppeteer worked seamlessly in this setup.
However, before proceeding further, I wanted to confirm with the team if Puppeteer is officially supported on ARM architecture. It's crucial for our project's infrastructure planning and compatibility assurance.
Could someone please provide clarity on this matter? Any official documentation or insights regarding Puppeteer's compatibility with ARM architecture would be greatly appreciated.
Thank you for your attention to this matter.

macos arm64 is fully supported. As for linux arm64, Chrome does not officially support this platform so there are no arm64 binaries for linux https://github.com/puppeteer/puppeteer/issues/7740 It should be still possible to use third-party arm64 chromium builds or use some sort of emulation to be able to run x64 on arm64.


WIP: enable colored output on jupyter notebooks

this currently lacks automated tests and is entirely untested on windows
fixes #1185

the callout i started for this wrt windows was timed rather badly, i'll take a look at making a unix only fix soon

#1271 Applies specifically to Jupyter Lab (in case there's a difference in this case from the workings of Jupyter Notebook).
Also:
# Doing:
print(click.style(text, **styles), file=file)
# works (prints styled), while this doesn't (prints unstyled):
click.echo(click.style(text, **styles), file=file)


3/19/2019 Publish

OPS Build status updates of commit 3bab4df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fixes CupertinoFullscreenDialogTransition leaks

Part of #141198
FixesCupertinoFullscreenDialogTransition widget leaks
Pre-launch Checklist

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

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

cc: @polina-c this one reduces leaks by 330 :)

Looks good. Can you opt-in some test, to make bot stop complaining about test coverage?

@ValentinVignal Again, thanks for review :) i'll add fix things as per your suggestions

@polina-c Do we need test here? since it does not change outside behaviour, if so what kind of test would be good fit for this?

@polina-c Do we need test here? since it does not change outside behaviour, if so what kind of test would be good fit for this?

Since this PR fixes a leak, it would be great to opt-in a test to track this fixed leak.

@polina-c I have added test-case as discussed, let me know we are good go.
At first i tried to add opt-in into existing testcase but it seems all CupertinoPageRoute test are all paired with CupertinoApp which it self leaks CurvedAnimation so i had to create new testcase with MaterialApp would that be okay?
Also, added null assigned to curve after disposal

@polina-c framework_tests_impeller seems to be failing and from looking at logs editable_text_cursor_test.dart has something to do with this, i ran tests but except of leaks logs test-cases are passing.
does this has something to do with current changes in PR?

It seems they passed now.

@polina-c @ValentinVignal Added mentioned changes 👀

This is not addressed yet: https://github.com/flutter/flutter/pull/147168#discussion_r1580089692

@polina-c please check now


non-Sendable captures don't suggest the most common solution

Motivation
Here's the example I'm thinking of:
class MyClass {
}

func someFunction(_ block: @Sendable () -> Void) {
}

func useFunction() {
    let value = MyClass()

    someFunction {
        // ERROR: Capture of 'value' with non-sendable type 'MyClass' in a `@Sendable` closure
        // Info: Class 'MyClass' does not conform to the 'Sendable' protocol
        print(value)
    }
}

This code produces an error and a extra bit of info. One of the most common solutions to a problem like this is to use a global actor. But users need to known that's an option and that it will make the type Sendable. I think the compiler should offer that advice!
Proposed solution
How about something like:
// ERROR: Capture of 'value' with non-sendable type 'MyClass' in a `@Sendable` closure
// Info: Class 'MyClass' does not conform to the 'Sendable' protocol
// Info: Class 'MyClass' is not isolated to a global actor

Alternatives considered
No response
Additional information
No response

I don't understand your proposed amendment; MyClass is isolated to a global actor (@MainActor)…?
A better fix-it suggestion might be to replace the Sendable requirement with sending, as in this case specific example that's all that's needed to type check successfully in useFunction.
I'm also not sure that the global actor isolation is that relevant, anyway.  Irrespective of whether a type is isolated to a global actor, it can still be sent to other isolation domains (IIRC), it just can't be used from them.  The crux really is the sending aspect, and the ambiguity is the user's intent as to whether they actually want to send it or not.

Arg, I typo'ed. Yes, that @MainActor is not supposed to be there in the example. I've just removed it. And, yes once actor-isolated, that type is indeed Sendable. So adding that @MainActor make the above code valid.
I love the concept of mentioning sending here as well. I just don't know enough about it to suggest it with confidence. I can say, though, that often when faced with this kind of thing, the closure in question isn't under your control. I'm not sure if such a suggestion could be conditionalized on the definition being within the same module maybe?

Yeah, I'm not sure entirely what it would mean to say a closure is sending (I mean, literally it would mean that anything it captures must be carried with it, for isolation purposes, but the question is can that actually be implemented in the compiler and does it have any undesirable logical consequences).  Anyway, that's pretty tangential now that you've corrected your example.


Showing alt text resets zoom

I feel like this shouldn't happen.

Seems to be an issue with the PhotoView library. I've tried saving the current zoom with getScale() and restoring it by calling setScale() right after the alt text gets visible, but for some reason it doesn't do anything

There is now an alternative style for displaying the alt text that does not reset zoom anymore.


Segmentation fault on ./kinect2_bridge

On running the kinect2_bridge I get a segmentation fault. I'm not sure whether this is because my laptop is not detecting kinect2, or is there a bug in kinect2_bridge. I have connected kinect2 to USB 3.0 port on Ubuntu 12.04 using the latest kernel. Below is the output of "./kinect2_bridge" executable:
ashesh@ashesh-jain:~/catkin_ws/devel/lib/kinect2_bridge$ ./kinect2_bridge
parameter:
base_name: kinect2
sensor:
fps_limit: -1
calib_path: /home/ashesh/catkin_ws/src/iai_kinect2/kinect2_bridge/data/
use_png: false
jpeg_quality: 90
png_level: 1
depth_method: opengl
depth_device: -1
reg_method: default
reg_devive: -1
max_depth: 12
min_depth: 0.1
queue_size: 2
bilateral_filter: true
edge_aware_filter: true
publish_tf: false
base_name_tf: kinect2
worker_threads: 4
Segmentation fault (core dumped)

Upon running ./Protonect I get the following error:
ashesh@ashesh-jain:~/Downloads/libfreenect2/examples/protonect/bin$ gdb -ex r --args  ./Protonect
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
http://bugs.launchpad.net/gdb-linaro/...
Reading symbols from /home/ashesh/Downloads/libfreenect2/examples/protonect/bin/Protonect...done.
Starting program: /home/ashesh/Downloads/libfreenect2/examples/protonect/bin/Protonect
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeaf18700 (LWP 1215)]
[New Thread 0x7fffea717700 (LWP 1216)]
Program received signal SIGSEGV, Segmentation fault.
glfwGetWindowAttrib (handle=0x0, attrib=139266) at /home/ashesh/Downloads/libfreenect2/depends/glfw_src/src/window.c:560
560	            return window->glMajor;
(gdb) bt
#0  glfwGetWindowAttrib (handle=0x0, attrib=139266) at /home/ashesh/Downloads/libfreenect2/depends/glfw_src/src/window.c:560
#1  0x00007ffff7a17f78 in flextInit (window=0x0, bindings=0x6329b0) at /home/ashesh/Downloads/libfreenect2/examples/protonect/src/flextGL.c:20
#2  0x00007ffff7a1b8cb in libfreenect2::OpenGLDepthPacketProcessorImpl::initialize (this=0x63e630)
at /home/ashesh/Downloads/libfreenect2/examples/protonect/src/opengl_depth_packet_processor.cpp:469
#3  0x00007ffff7a19700 in libfreenect2::OpenGLDepthPacketProcessor::OpenGLDepthPacketProcessor (this=0x60e670, parent_opengl_context_ptr=, debug=false)
at /home/ashesh/Downloads/libfreenect2/examples/protonect/src/opengl_depth_packet_processor.cpp:783
#4  0x00007ffff7a06826 in libfreenect2::OpenGLPacketPipeline::createDepthPacketProcessor (this=0x622170)
at /home/ashesh/Downloads/libfreenect2/examples/protonect/src/packet_pipeline.cpp:109
#5  0x00007ffff7a06941 in libfreenect2::BasePacketPipeline::initialize (this=0x622170)
at /home/ashesh/Downloads/libfreenect2/examples/protonect/src/packet_pipeline.cpp:43
#6  0x00007ffff7a06b02 in libfreenect2::OpenGLPacketPipeline::OpenGLPacketPipeline (this=0x622170, parent_opengl_context=, debug=)
at /home/ashesh/Downloads/libfreenect2/examples/protonect/src/packet_pipeline.cpp:102
#7  0x00007ffff7a1137e in libfreenect2::createDefaultPacketPipeline () at /home/ashesh/Downloads/libfreenect2/examples/protonect/src/libfreenect2.cpp:631
#8  0x00007ffff7a140d8 in libfreenect2::Freenect2::openDevice (this=0x7fffffffdcf0, idx=0)
at /home/ashesh/Downloads/libfreenect2/examples/protonect/src/libfreenect2.cpp:669
#9  0x0000000000401b5d in main (argc=, argv=) at /home/ashesh/Downloads/libfreenect2/examples/protonect/Protonect.cpp:58
(gdb)
Is this problem because of OpenGL? I have the following OpenGL version:
"OpenGL version string: 3.0 Mesa 8.0.4"

Hi,
I think for the OpenGL processor you need at least OpenGL 3.3. Try out the OpenCL processor.

I used to have the segmentation error: "Segmentation fault (core dumped)" when I want to "$ rosrun kinect2_bridge kinect2" I found a solution for my case. Maybe it helps somebody:
$ sudo gedit /etc/default/grub
Here, be sure there is no modification about nomodeset. It should stay as its original default version:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
$ sudo update-grub
$ sudo reboot
In my case, I used to changed it to GRUB_CMDLINE_LINUX_DEFAULT="nomodeset" for some reason, therefore kinect2_bridge was not working.

I am able to run ./Protonect and can view color, ir and depth images with out any error.
When I am trying to run kinect2_bridge from the root, it asks for clients. If I provide kinect2/sd/image_color_rect, it produces the messages but if I provide other topics like kinect2/qhd/image_color, the following error genetares
root@tegra-ubuntu:~/catkin_ws/devel# rosrun kinect2_bridge kinect2_bridge
parameter:
base_name: kinect2
sensor:
fps_limit: -1
calib_path: /home/ubuntu/catkin_ws/src/iai_kinect2/kinect2_bridge/data/
use_png: false
jpeg_quality: 90
png_level: 1
depth_method: opengl
depth_device: -1
reg_method: default
reg_devive: -1
max_depth: 12
min_depth: 0.1
queue_size: 2
bilateral_filter: true
edge_aware_filter: true
publish_tf: false
base_name_tf: kinect2
worker_threads: 4
[Freenect2Impl] enumerating devices...
[Freenect2Impl] 10 usb devices connected
[Freenect2Impl] found valid Kinect v2 @2:5 with serial<PHONE_NUMBER>47
[Freenect2Impl] found 1 devices
Kinect2 devices found:
0:<PHONE_NUMBER>47 (selected)
[Freenect2DeviceImpl] opening...
[Freenect2DeviceImpl] opened
starting kinect2
[Freenect2DeviceImpl] starting...
[Freenect2DeviceImpl] ReadData0x14 response
92 bytes of raw data
0x0000: 00 00 12 00 00 00 00 00 01 00 00 00 43 c1 1f 41 ............C..A
0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x0020: 0a 21 33 55 c2 00 17 20 00 08 00 00 10 00 00 00 .!3U... ........
0x0030: 00 01 00 00 00 10 00 00 00 00 80 00 01 00 00 00 .......... .....
0x0040: 31 33 00 00 00 04 0a 0d 47 4d 42 30 31 33 2e 31 13......GMB013.1
0x0050: 58 00 00 00 00 00 00 00 07 00 00 00 X...........
[Freenect2DeviceImpl] ReadStatus0x090000 response
4 bytes of raw data
0x0000: 23 26 00 00 #&..
[Freenect2DeviceImpl] ReadStatus0x090000 response
4 bytes of raw data
0x0000: 23 26 00 00 #&..
[Freenect2DeviceImpl] enabling usb transfer submission...
[Freenect2DeviceImpl] submitting usb transfers...
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[Freenect2DeviceImpl] started
device serial:<PHONE_NUMBER>47
device firmware: 2.3.3913.0.7
[Freenect2DeviceImpl] stopping...
[Freenect2DeviceImpl] disabling usb transfer submission...
[Freenect2DeviceImpl] canceling usb transfers...
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[Freenect2DeviceImpl] stopped
default ir camera parameters:
fx 367.573, fy 367.573, cx 256.171, cy 209.483
k1 0.0850694, k2 -0.273469, p1 0, p2 0, k3 0.100644
default color camera parameters:
fx 1081.37, fy 1081.37, cx 959.5, cy 539.5
using sensor defaults for color intrinsic parameters.
using sensor defaults for ir intrinsic parameters.
using defaults for rotation and translation.
using defaults for depth shift.
camera parameters used:
camera matrix color:
[1081.3720703125, 0, 959.5;
0, 1081.3720703125, 539.5;
0, 0, 1]
distortion coefficients color:
[0, 0, 0, 0, 0]
camera matrix ir:
[367.572998046875, 0,<PHONE_NUMBER>617188;
0,<PHONE_NUMBER>46875,<PHONE_NUMBER>617188;
0, 0, 1]
distortion coefficients ir:
[0.08506941795349121, -0.2734693884849548, 0, 0, 0.1006444990634918]
camera matrix depth:
[367.572998046875, 0,<PHONE_NUMBER>617188;
0,<PHONE_NUMBER>46875,<PHONE_NUMBER>617188;
0, 0, 1]
distortion coefficients depth:
[0.08506941795349121, -0.2734693884849548, 0, 0, 0.1006444990634918]
rotation:
[1, 0, 0;
0, 1, 0;
0, 0, 1]
translation:
[0; 0; 0]
depth shift:
0
[DepthRegistration::New] Using CPU registration method!
[DepthRegistration::New] Using CPU registration method!
[kinect2_bridge] waiting for clients to connect
[kinect2_bridge] client connected. starting device...
[Freenect2DeviceImpl] starting...
[Freenect2DeviceImpl] ReadData0x14 response
92 bytes of raw data
0x0000: 00 00 12 00 00 00 00 00 01 00 00 00 43 c1 1f 41 ............C..A
0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x0020: 0a 21 33 55 c2 00 17 20 00 08 00 00 10 00 00 00 .!3U... ........
0x0030: 00 01 00 00 00 10 00 00 00 00 80 00 01 00 00 00 .......... .....
0x0040: 31 33 00 00 00 04 0a 0d 47 4d 42 30 31 33 2e 31 13......GMB013.1
0x0050: 58 00 00 00 00 00 00 00 07 00 00 00 X...........
[Freenect2DeviceImpl] ReadStatus0x090000 response
4 bytes of raw data
0x0000: 01 26 00 00 .&..
[Freenect2DeviceImpl] ReadStatus0x090000 response
4 bytes of raw data
0x0000: 03 26 00 00 .&..
[Freenect2DeviceImpl] enabling usb transfer submission...
[Freenect2DeviceImpl] submitting usb transfers...
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[Freenect2DeviceImpl] started
[RgbPacketStreamParser::handleNewData] packetsize or sequence doesn't match!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[kinect2_bridge] depth processing: ~nanHz (nanms) publishing rate: ~0Hz
[kinect2_bridge] color processing: ~-nanHz (-nanms) publishing rate: ~10.3149Hz
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[kinect2_bridge] depth processing: ~nanHz (nanms) publishing rate: ~0Hz
[kinect2_bridge] color processing: ~112.666Hz (8.87577ms) publishing rate: ~13.6632Hz
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[TurboJpegRgbPacketProcessor] avg. time: 58.6753ms -> ~17.043Hz
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[kinect2_bridge] depth processing: ~nanHz (nanms) publishing rate: ~0Hz
[kinect2_bridge] color processing: ~127.059Hz (7.87038ms) publishing rate: ~14.6242Hz
Segmentation fault
I am using Jetson TK1 board .
cpu ang gpu performance were altered with maximum efficiency
Why lots of "skipping rgb packet!" and " [TransferPool::submit] failed to submit transfer " ?
why not providing depth data?
[kinect2_bridge] depth processing: ~nanHz (nanms) publishing rate: ~0Hz
Why segmentation fault after producing one message to the topics?


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Codecov Report

Merging #12 (e2659d2) into develop (296d7d9) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             develop      #12   +/-   ##
==========================================
  Coverage      99.01%   99.01%
  Complexity        91       91
==========================================
  Files             14       14
  Lines            203      203
==========================================
  Hits             201      201
  Misses             2        2

Impacted Files
Coverage Δ

lib/Dmm/Helpers/DiscoverApi.php
88.23% <ø> (ø)

lib/Dmm/HttpClient/Api/AbstractApi.php
100.00% <ø> (ø)

lib/Dmm/HttpClient/Api/Addresses.php
100.00% <ø> (ø)

lib/Dmm/HttpClient/Api/ArtworkVersions.php
100.00% <ø> (ø)

lib/Dmm/HttpClient/Api/Artworks.php
100.00% <ø> (ø)

lib/Dmm/HttpClient/Api/CompanyAddresses.php
100.00% <ø> (ø)

lib/Dmm/HttpClient/Api/CustomFields.php
100.00% <ø> (ø)

lib/Dmm/HttpClient/Api/Letters.php
100.00% <ø> (ø)

lib/Dmm/HttpClient/Api/MailingLists.php
100.00% <ø> (ø)

lib/Dmm/HttpClient/Api/Postcards.php
100.00% <ø> (ø)

... and 3 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


feat: support for specifying AWS region

Description
Support for specifying AWS region.
Testing instructions

Set 'region' in settings.DJFS.
Test that uploads to a bucket not in the default region work.
Test that generated URLs contain the region name.

Other information
Private-ref: https://tasks.opencraft.com/browse/BB-8077

Thanks for the pull request, @ArturGaspar! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate.

Approved :+1:

[x] I tested this running on a sandbox with S3 region me-south-1
[x] I read through the code
[x] Includes documentation

This looks good code-wise, but I think if you want to use it, you're going to want to bump the version number.

@dianakhuang Done.

@ArturGaspar 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

@ArturGaspar great! I merged it and created a new release with your changes: https://github.com/openedx/django-pyfs/releases/tag/v3.5.0 Should be up on PyPI soon.


Fix spark test failures

Recently the _source endpoints have had their types removed. There are a few spots in the test code that uses these end points that really don't need to be using them in the first place. This PR removes them to get the tests passing again.

@jbaiera Please remember to add version labels to all PRs


deps: Bump build-image -> 41c5a05

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

this genuinely makes a lot of the mobile jobs timeout due to changed toolchain

/retest

/retest


Fix concurrency problem in Configs

Fix problems where Configs::getAccount would return an Account with
the wrong data due to either the private 'account' field not being
propogated to other threads, or because the updated Service in the
'generalConfig' field was not being propogated to other threads.

Still not holding up in testing...


Is it possible in some way to start screen capture on initial phone setup.

I trying to get screenshots from the initial configuration of a Samsung phone, but in this stage it's not possible to enable USB debugging yet.
Is there a way  to get this done with scrcpy?

Is there a way to get this done with scrcpy?

No, scrcpy requires adb, which requires USB debugging.

It;s not possible to enable USB debugging other than through the menu?