Added AboutPage

I was not sure about what content you wanted in the About Page, so currently it's pretty much the same as the Support section in Options Page.
The page has a link to repo issues.

This is perfect;) I'll merge asap (travelling now:))
Thanks a lot


update installation in README and sphinx

Documentation updates!

@bmcfee, for your approval.

@bmcfee, fixed the last to_wav stuff.


White border on right hand edge

When I export screens, some of them have a white border on the right edge. There seems to be no reason for it. I have even tried it on a blank artboard with background colour and still getting it.
Maybe I am using the wrong settings. Designing in 375*812
Puzzling.

need more info

Sorry. I managed to resolve it but forgot to post back here. The error was at my end. Cheer.


Attribute Transition: Initial Implementation

New attribute API (transition flag)
New base layer API (transition prop with the following parameters: duration, easing, onStart, onEnd, onInterrupt)
Enable transition on applicable attributes of instanced core-layers
Add example app

TODO:

Check WebGL2 support
Update layer documentations
GridLayer and HexagonLayer need to map transition key names @heshan0131

@ibgreen @1chandu @shaojingli  If there're no more comments, I'd like to get this PR approved. As discussed, I will not merge it before the 4.2 release.


Add a cmd to create collections in production mode

Production mode does not create collections automatically, so need a way to do it in cmdline. Something like:
$ horizon create-collections

Or add it to schema apply command?

$ horizon schema apply already support it :)


not working?

looks like the service has been down for quite some time?

I confirm it's not working


Concurrency bug when calling an SDK function with multiple thread

When calling an SDK function with multiple threads which use a shared SDK instance, one of the following exceptions occurs:

 /home/pi/.local/lib/python3.9/site-packages/_pytest/unraisableexception.py:78: PytestUnraisableExceptionWarning: Exception ignored in: <function SPI.__del__ at 0x7fb30ab8b0>

  Traceback (most recent call last):
    File "/home/pi/.local/lib/python3.9/site-packages/periphery/spi.py", line 209, in close
      os.close(self._fd)
  OSError: [Errno 9] Bad file descriptor

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/home/pi/.local/lib/python3.9/site-packages/periphery/spi.py", line 78, in __del__
      self.close()
    File "/home/pi/.local/lib/python3.9/site-packages/periphery/spi.py", line 211, in close
      raise SPIError(e.errno, "Closing SPI device: " + e.strerror)
  periphery.spi.SPIError: [Errno 9] Closing SPI device: Bad file descriptor

 /home/pi/.local/lib/python3.9/site-packages/_pytest/unraisableexception.py:78: PytestUnraisableExceptionWarning: Exception ignored in: <function I2C.__del__ at 0x7fb30b2670>

  Traceback (most recent call last):
    File "/home/pi/.local/lib/python3.9/site-packages/periphery/i2c.py", line 162, in close
      os.close(self._fd)
  OSError: [Errno 9] Bad file descriptor

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/home/pi/.local/lib/python3.9/site-packages/periphery/i2c.py", line 61, in __del__
      self.close()
    File "/home/pi/.local/lib/python3.9/site-packages/periphery/i2c.py", line 164, in close
      raise I2CError(e.errno, "Closing I2C device: " + e.strerror)
  periphery.i2c.I2CError: [Errno 9] Closing I2C device: Bad file descriptor

    warnings.warn(pytest.PytestUnraisableExceptionWarning(msg))

This specific stack trace arises from calling set_rtd in the ADC Service with multiple threads using a shared SDK instance, but other functions called also cause the same exceptions to be raised. The bug seems to arise when multiple SDK instances use a shared hardware resource -- in this case I2C and SPI devices.
When testing for this exception, I found that when the threads each have their own instance of the SDK the tests pass. The tests fail if the threads share an SDK instance, with the rate of failure increasing with more threads. Additionally, the tests pass if each thread has its own SDK instance but the function call is protected with a lock.

@josiah-tesfu include your test code please for both shared sdk and protected.

@sj608 this is a reproducible issue now. @josiah-tesfu has test codes (which should be added to this ticket soon) that can produce the error consistently.

Non-shared instances (all tests pass)
regarding this test, I just want to add that I think the reason that it is passing is not because the sdk is non-shared but because sdk init is slow the threads do not have a good chance to overlap

@sjpark608 to make all tests fail just increase number of threads from 5 to 30 here:
    threads = [PropagatingThread(target=set_rtd_client) for _ in range(5)]

This comment is to sum up our brief discussion about thread safety of SDK

The root cause of the issue here is from the thread safety of character devices of spi and i2c being limited to file level. What could be happening during the shared sdk test is that one thread may have already closed the device after a transaction while another thread is trying to start the transfer. This throws a bad file descriptor error which indicates accessing of a file that's closed.
We've discussed implementing the thread-safe mutex on the SDK level, I will be investigating the feasibility and possible overheads before implementation.


Added contributors page

Solved issue #372

[ ] Unchecked box

[ x] I have tested the changes locally

[ x] Changes are backward-compatible

https://github.com/VaibhavArora314/StyleShare/assets/154724111/bdc73e38-35d4-416f-b2f9-fd74c2294355

@VaibhavArora314 Pls review this PR!!!

@VaibhavArora314 Made the changes

@akbatra567  kindly review this

@akbatra567 Review this pls


feat: improve let directive type

Related to #394
This PR improves assigning the correct let directive type when the component type is available.
However, since @typescript-eslint/parser cannot be used to retrieve component types, users should use the experimental parser typescript-eslint-parser-for-extra-files instead. .
If the user is using @typescript-eslint/parser it will be the same as before.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

29 of 33 (87.88%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 90.517%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/converts/attr.ts
25
29
86.21%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
2213

Relevant Lines:
2361

💛  - Coveralls


HDDS-4562. Old bucket needs to be accessible after the cluster was upgraded to the Quota version.

What changes were proposed in this pull request?
long quotaInBytes are new fields in the bucketArgs, this field will go to 0 by default in the old bucket when the old cluster is upgraded. At this point, the data writes are rejected.
This is similar to creating a bucket without specifying quotaInBytes, where quotaInBytes is set to -1 by default via getQuotaValue. We can use 0 as a special term.

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4562
How was this patch tested?
ut added

Not related to this PR, can you also provide info on how the clear space quota works and it's usage.
Because I see when bucket clear space quota comes, we reset to -1, but what will happen to volume quota (Will it reclaim bucket quota? or any information on clear space quota usage and how it works also can you share some info.

@captainzmc see #1691 for acceptance test with two lines that are currently disabled to verify this fix.  If you could review that PR, then uncommenting them in this PR would improve test coverage.

Hi @captainzmc
Few questions:

Can we make use of proto default value to -1 for quotaInBytes value in proto.
So on old buckets, we cannot set quota, as we don't have any info of bytesUsed/namespace count, or if it can be set how this will be handled?
And how upgrades are handled for quota feature overall, like for older volumes and buckets under it?

Thanks for @bharatviswa504’s advices.

For now, we use getQuotaValue(long quota) to handle the default case in RpcClient. And setting the default in proto is also a good way, I'll change that later.
After adding usedByets, the original keys of the old bucket cannot be counted, so we can only count the newly written keys. Therefore, we temporarily did not recommend old buckets to enable Quota (because their usedByets were inaccurate).
For old buckets we do not recommend that quota be enabled, but in order not to affect the write, I handle the default at checkBucketQuotaInBytes in this PR.

reclaim
Yes, I have submitted the use of the latest quota in Doc. Can be seen here:
https://ci-hadoop.apache.org/view/Hadoop Ozone/job/ozone-doc-master/lastSuccessfulBuild/artifact/hadoop-hdds/docs/public/feature/quota.html

Not related to this PR, can you also provide info on how the clear space quota works and it's usage.
Because I see when bucket clear space quota comes, we reset to -1, but what will happen to volume quota (Will it reclaim bucket quota? or any information on clear space quota usage and how it works also can you share some info.

Yes, I have submitted the use of the latest quota in Doc. Can be seen here:
https://ci-hadoop.apache.org/view/Hadoop Ozone/job/ozone-doc-master/lastSuccessfulBuild/artifact/hadoop-hdds/docs/public/feature/quota.html

@captainzmc see #1691 for acceptance test with two lines that are currently disabled to verify this fix. If you could review that PR, then uncommenting them in this PR would improve test coverage.

Thanks for @adoroszlai 's suggestion, I will deal with the acceptance test here.

https://ci-hadoop.apache.org/view/Hadoop Ozone/job/ozone-doc-master/lastSuccessfulBuild/artifact/hadoop-hdds/docs/public/feature/quota.html

When clear volume quota(Assuming volume quota was set before), it is just like setting the quota on the volume to -1, when clear volume quota is called?
When volume quota is set, bucket clear quota, it is like just setting the quota for that bucket to -1, and it will allow new buckets can be created if volume quota is still available(As previous bucket quota cleared quota)

When volume quota is not set and bucket quota is set, it is just reset quota of the bucket to -1. when clear bucket quota operation is performed
Is my understanding correct here?
Example:
V1 - 100 MB
V1/B1 - 50MB
V1/B2- 50MB
Now clear quota on V1/B2 we set quota of V1/B2 to -1, and now a new bucket can be still created in this volume?
New Bucket created with quota 50MB. (V1/B3)
So, in this volume there are 3 buckets, only 2 are considered in to count, as clearQuota is run(on V1/B2), and we are not considering this bucket in quota calculations, so this bucket will not be counted under quota, but for volume we have crossed the quota of that volume. (As user has run clear quota on V1/B2)
So, here clear quota means resetting the quota to -1? Or what is the real purpose of this clearQuota usage on clusters, in what scenarios this will be useful on the cluster?

For old buckets, we do not recommend that quota be enabled, but in order not to affect the write, I handle the default at >checkBucketQuotaInBytes in this PR.

But I don't see any guards in the cluster to not allow this for older buckets.

Currently, Unsigned field can't have negative default value in proto. If we set [default = -1], an error will be compiled.
For now, we use getQuotaValue(long quota) to handle the default case in RpcClient..
Might be use int64, but protobuf document said it is inefficient for negative numbers, not sure it is good idea. Just thought of bringing this up here?

int64
Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint64 instead.
int64
long
int/long[3]
*int64

I think it will also help if we plan to support quota on older buckets.
The default will be -2, all older buckets will have -2, new buckets created after this feature will have -1. So, if one some sets quota on older buckets in this way, we can figure it out.

Might be use int64, but protobuf document said it is inefficient for negative numbers, not sure it is good idea. Just thought of bringing this up here?

I'll change the type to sint64, which is both negative by default and more efficient than int64.

Example:
V1 - 100 MB
V1/B1 - 50MB
V1/B2- 50MB
Now clear quota on V1/B2 we set quota of V1/B2 to -1, and now a new bucket can be still created in this volume?
New Bucket created with quota 50MB. (V1/B3)
So, in this volume there are 3 buckets, only 2 are considered in to count, as clearQuota is run(on V1/B2), and we are not considering this bucket in quota calculations, so this bucket will not be counted under quota, but for volume we have crossed the quota of that volume. (As user has run clear quota on V1/B2)
So, here clear quota means resetting the quota to -1? Or what is the real purpose of this clearQuota usage on clusters, in what scenarios this will be useful on the cluster?

Thanks to @bharatviswa504‘s advice, you found a very important point.
Before HDDS-4308, we had usedBytes in volume, so before writing the key, we checked both bucket quota and volume quota. Setting bucket quota to -1 alone at this point does not matter, since we are able to ensure that usedBytes do not exceed volume quota.
But we can't do that now because volume doesn't have usedBytes. I created a new JIRA HDDS-4588 to fix this problem. If volume's quota is enabled then bucket's quota cannot be cleared. We need to prompt the user to clear volume quota first.

But I don't see any guards in the cluster to not allow quota operations for older buckets/volumes.
And also do you think, we need to document this in our docs?
I’ll  refine the docs to make it clear that older volumes/buckets are not recommended to use quota.

When the acceptance test upgrade, namespace will also have the problem that old volumes cannot create buckets. This also fixed in this PR.  R: @amaliujia @linyiqun

Updated PR and fixed review issues.

Example:
V1 - 100 MB
V1/B1 - 50MB
V1/B2- 50MB
Now clear quota on V1/B2 we set quota of V1/B2 to -1, and now a new bucket can be still created in this volume?
New Bucket created with quota 50MB. (V1/B3)
So, in this volume there are 3 buckets, only 2 are considered in to count, as clearQuota is run(on V1/B2), and we are not considering this bucket in quota calculations, so this bucket will not be counted under quota, but for volume we have crossed the quota of that volume. (As user has run clear quota on V1/B2)
So, here clear quota means resetting the quota to -1? Or what is the real purpose of this clearQuota usage on clusters, in what scenarios this will be useful on the cluster?

Thanks to @bharatviswa504‘s advice, you found a very important point.
Before HDDS-4308, we had usedBytes in volume, so before writing the key, we checked both bucket quota and volume quota. Setting bucket quota to -1 alone at this point does not matter, since we are able to ensure that usedBytes do not exceed volume quota.
But we can't do that now because volume doesn't have usedBytes. I created a new JIRA HDDS-4588 to fix this problem. If volume's quota is enabled then bucket's quota cannot be cleared. We need to prompt the user to clear volume quota first.

But I don't see any guards in the cluster to not allow quota operations for older buckets/volumes.
And also do you think, we need to document this in our docs?

I’ll refine the docs to make it clear that older volumes/buckets are not recommended to use quota.

So, now if the volume quota is not set, the bucket Clearspace quota is just disabling quota on the buckets.
And also just setting quota at volume level will not be counted, until bucket level quotas are set.
For my understanding so volume quota is set, and bucket quota is set, clearing volume quota is just set to -1, so that now quota is tracked at bucket level. And now when bucket quota is cleared, when volume quota is set, we disallow the operation.
This will be the behavior of clear space quota, let me know if i am missing something.

But we can't do that now because volume doesn't have usedBytes. I created a new JIRA [HDDS-4588
(https://issues.apache.org/jira/browse/HDDS-4588) to fix this problem. If volume's quota is enabled then bucket's quota >cannot be cleared. We need to prompt the user to clear volume quota first.

Now the example mentioned scenarios will not happen. Thanks for opening this Jira and tracking this issue.

The default will be -2, all older buckets will have -2, new buckets created after this feature will have -1. So, if some one sets >quota on older buckets in this way, we can figure it out, just an idea saying here.

If we want to disallow the quota support for older buckets, one idea to do at code level.

@captainzmc
Can we use 0 to indicate that a quota is not set? Will this better handle the cluster upgrade issue that some buckets by default has 0 quota?
If a case is really set "0" quota to a bucket thus lock the bucket from creating, then users can choose to use a negative value.

O, actually from the code seems that setting default value as -1 is solved in proto. If so please ignore my previous comment (which assumed that proto cannot set -1 as default value for quota)

The default will be -2, all older buckets will have -2, new buckets created after this feature will have -1. So, if some one sets >quota on older buckets in this way, we can figure it out, just an idea saying here.

If we want to disallow the quota support for older buckets, one idea to do at code level.

Is it feasible that we provide a option of calculating the bytesInUsed for each bucket during 1.0.0 -> 1.1. upgrade to user?  @adoroszlai

So, now if the volume quota is not set, the bucket Clearspace quota is just disabling quota on the buckets.
And also just setting quota at volume level will not be counted, until bucket level quotas are set.
For my understanding so volume quota is set, and bucket quota is set, clearing volume quota is just set to -1, so that now quota is tracked at bucket level. And now when bucket quota is cleared, when volume quota is set, we disallow the operation.
This will be the behavior of clear space quota, let me know if i am missing something.

Yes.
And, the problem of clear quota will be fixed in HDDS-4588.

The default will be -2, all older buckets will have -2, new buckets created after this feature will have -1. So, if some one sets >quota on older buckets in this way, we can figure it out, just an idea saying here.

If we want to disallow the quota support for older buckets, one idea to do at code level.

User using old Ozone version may still has the desire to use the new Quota feature. It's better not shut the door completely.
@adoroszlai , I'm not sure if it's feasible that we provide a option of calculating the bytesInUsed for each bucket during 1.0.0 -> 1.1. upgrade to user? So that user has the choice either tolerate the inaccurate bytesInUsed or a relative longer upgrade time to get accurate bytesInUsed of buckets.

Hi @ChenSammi, I think it's dangerous recalculating usedBytes in upgrade . If the amount of data is too large, it will greatly increase the time, and if the processing is not good, it will cause the upgrade to fail.
If we want use Quota in old buckets, we can add a command to recalculate bucket usedBytes to minimize the impact.

The default will be -2, all older buckets will have -2, new buckets created after this feature will have -1. So, if some one sets >quota on older buckets in this way, we can figure it out, just an idea saying here.

If we want to disallow the quota support for older buckets, one idea to do at code level.

User using old Ozone version may still has the desire to use the new Quota feature. It's better not shut the door completely.
@adoroszlai , I'm not sure if it's feasible that we provide a option of calculating the bytesInUsed for each bucket during 1.0.0 -> 1.1. upgrade to user? So that user has the choice either tolerate the inaccurate bytesInUsed or a relative longer upgrade time to get accurate bytesInUsed of buckets.

@ChenSammi Above idea is to detect older buckets/volumes in the Ozone cluster, from discussion as it is said not recommended, said we can fail the operation But, if we want to support, when they setQuota, we can know this is an old bucket, we can say a warning message to the user, older keys are not considered.

The default will be -2, all older buckets will have -2, new buckets created after this feature will have -1. So, if some one sets >quota on older buckets in this way, we can figure it out, just an idea saying here.

If we want to disallow the quota support for older buckets, one idea to do at code level.

User using old Ozone version may still has the desire to use the new Quota feature. It's better not shut the door completely.
@adoroszlai , I'm not sure if it's feasible that we provide a option of calculating the bytesInUsed for each bucket during 1.0.0 -> 1.1. upgrade to user? So that user has the choice either tolerate the inaccurate bytesInUsed or a relative longer upgrade time to get accurate bytesInUsed of buckets.

Hi @ChenSammi, I think it's dangerous recalculating usedBytes in upgrade . If the amount of data is too large, it will greatly increase the time, and if the processing is not good, it will cause the upgrade to fail.
If we want use Quota in old buckets, we can add a command to recalculate bucket usedBytes to minimize the impact. User can decide for himself which buckets to recalculate.

Yes during upgrade might not be a feasible idea, it will take a long time for an upgrade if there are many buckets/keys in the cluster.

If we want use Quota in old buckets, we can add a command to recalculate bucket usedBytes to minimize the impact. User can decide for himself which buckets to recalculate.
Even this will be a costly operation, during that operation we should acquire bucket read lock and do the calculation, so all writes will be stalled in the system. (As during this operation, we should not allow new writes to get accurate bytesused).

Updated PR, set default to -2.  No matter whether or not we support old volume/bucket setting quota, we need to distinguish which volumes and buckets are old. So Here I take @bharatviswa504's advice.

If no more comments, I will commit this by tomorrow.

Thank you @captainzmc for the contribution and everyone for the review.


Fix formatting + check content for Compression

I've looked over this chapter, fixed formatting, refactored run length encoding section, and made a bunch of issues/ suggestions. Overall, it is in a pretty good state compared to some of the other chapters.


sorting 4 numbers

Description
Help me to sort the 4 numbers from smallest to biggest
Domain
Competitive Programming
Type of Contribution
Others
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of LearnCPP.

/assign


Fix Tinkerbell preflights to account for bundles changes

Description of changes:
The bundle changes trigger a rolling upgrades but Tinkerbell currently doesn't account for them during preflights which causes the upgrade to fail if a bundle change happened alongside a scaling operation.
This PR adds a preflight to detect bundle changes and marks those also as a trigger for rolling upgrades.
So if a scaling operation happens along with bundle changes, the CLI will fail out early in preflights.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/cherry-pick release-0.17


I2S: PCM Short Framesync, Clock (WS) inverted, Data Out starts too early

Environment

Development Kit: SparkFun ESP32 Thing
IDF version: v4.0-dev-71-g5beb2802e

Problem Description
When configured for PCM Short Framesync in master mode, the Clock polarity is active-low instead of active-high, each sample is sent twice, and the data output starts one bit to early.
Expected Behavior
I expect to see PCM Short Framesync on logic analyzer, similar to ESP32 Tech Ref Manual, Figure 53. WS is high-active, data starts after WS goes low.

Actual Behavior

Clock (WS) is active-low
sample is output twice,
output starts one bit to early

Steps to repropduce
Configure I2S for PCM Short, send data
Code to reproduce this issue
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "driver/i2s.h"

#define NUM_SAMPLES 60
#define I2S_NUM         (0)
#define I2S_BCK_IO      (GPIO_NUM_26)
#define I2S_WS_IO       (GPIO_NUM_25)
#define I2S_DO_IO       (GPIO_NUM_22)
#define I2S_DI_IO       (-1)

void app_main()
{
    i2s_config_t i2s_config = {
        .mode = I2S_MODE_MASTER | I2S_MODE_TX,                                  // Only TX
        .sample_rate = 8000,
        .bits_per_sample = 16,
        .channel_format = I2S_CHANNEL_FMT_ONLY_LEFT,
        .communication_format = I2S_COMM_FORMAT_PCM | I2S_COMM_FORMAT_PCM_SHORT,
        .dma_buf_count = 6,
        .dma_buf_len = 60,
        .use_apll = false,
        .intr_alloc_flags = ESP_INTR_FLAG_LEVEL1                                //Interrupt level 1
    };
    i2s_pin_config_t pin_config = {
        .bck_io_num = I2S_BCK_IO,
        .ws_io_num = I2S_WS_IO,
        .data_out_num = I2S_DO_IO,
        .data_in_num = I2S_DI_IO
    };
    i2s_driver_install(I2S_NUM, &i2s_config, 0, NULL);
    i2s_set_pin(I2S_NUM, &pin_config);
    i2s_set_clk(I2S_NUM, 8000, 16, I2S_CHANNEL_MONO);

    while (1) {
        uint16_t sample_data[NUM_SAMPLES];
        int i;
        for (i=0;i<NUM_SAMPLES/2;i++){
            sample_data[i*2]   = 0x5001;
            sample_data[i*2+1] = 0x5002;
        }
        size_t i2s_bytes_write;
        i2s_write(I2S_NUM, sample_data, 60 * 2, &i2s_bytes_write, portMAX_DELAY);
    }
}

Hi,@mringwal
The data out put  is not 1-bit early, but the WS signal is inverted. the WS  output signal can be reversed in gpio_matrix. You can try to modify i2s.c as follows:

My output signal:

thanks !!


new sarama use pierrec/lz4  , V 1.18.0 use which pierrec/lz4?

Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Sarama Version:
Kafka Version:
Go Version:
Configuration
What configuration values are you using for Sarama and Kafka?
Logs
When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set sarama.Logger to a log.Logger to capture Sarama debug
output.
Problem Description

Can you please elaborate more?

@h00401342 not sure if the thing you're trying to mention is that we are using a non versioned dependency to the lz4 lib?
as currently go.mod is referencing a commit for lz4:
github.com/pierrec/lz4 v0.0.0-20190327172049-315a67e90e41

I think we could add a reference to a released version, however the lz4 repo doesn't use go mod, but at least, it's tagging the releases.
Something like:
github.com/pierrec/lz4 v2.2.6+incompatible


Simple fix to unicode

Caolan,
Simple request: in two places in the default.js reporter, the actual character is used in the code, for the checkmark (passed) and the xmark (failed) for an individual test.
To make it more cross-platform and unicode (and IDE) friendly, can it be replaced by the actual unicode?
line 81: replace the checkmark with '\u2714' (that is backslash character followed by u2714)
line 84: replace the xmark with '\u2716' (that is backslash character followed by u2716)

\u2714

@deitch sorry this took so long. I think this has been resolved via https://github.com/caolan/nodeunit/commit/19998595d21e6ac7eb24978b6960a03a70f330b8
if not, we can re-open.

Actually, I don't think that one resolves it. The change you linked to only changes test-cli.js.
It looks like it was consolidated as pass_indicator and fail_indicator here https://github.com/caolan/nodeunit/blob/master/lib/reporters/default.js#L54 and https://github.com/caolan/nodeunit/blob/master/lib/reporters/default.js#L55 , but it still uses the actual checkmarks if not on windows. Why not just use the unicode everywhere?

ah ok, I'll re-open it then.

Why not just use the unicode everywhere?

I dunno, I'm just the project maintainer, I wasn't around when this was originally written. I know this is one of the oldest node unit testing packages; probably was created when windows support was spotty/non-existent. :) Pull request welcome! 👍

Hmm, it wasn't on Windows. At least I think it wasn't. I don't recall the circumstances. Any reason not to change it?
I don't mind a PR, but it would be changing the following line:
// from
var pass_indicator = process.platform === 'win32' ? '\u221A' : '✔';

// to
var pass_indicator = '\u221A';


Screen Wake Lock doesn't work on iOS 16.

Screen Wake Lock works on Google Chrome onWindows, but doesn't work on Safari on iOS 16.

According to Can I Use..., Screen Wake Lock API just doesn't work on web app mode, and it's a bug, so it can't be helped for now.

On iOS does not work in web app (aka PWA) mode, only works in actual browser


nodes is forbidden

When attempting to call kubectl get nodes, an error is received:
Error from server (Forbidden): nodes is forbidden: User<EMAIL_ADDRESS>cannot list resource "nodes" in API group "" at the cluster scope
Also, during the AD setup the following command generates this error message:
export AADOBJECTID_USER_CLUSTERADMIN=$(az ad user create --display-name=${AADOBJECTNAME_USER_CLUSTERADMIN} --user-principal-name ${AADOBJECTNAME_USER_CLUSTERADMIN}@${TENANTDOMAIN_K8SRBAC} --force-change-password-next-login --password ChangeMebu0001a0008AdminChangeMe --query objectId -o tsv)
ERROR: Insufficient privileges to complete the operation.

Hi @rovin-ms

First error is because of second error that you have mentioned.
Your AD is not configured appropriately with AKS because you don't have sufficient rights to perform write rights over AD

You can follow below article to make those things work
https://docs.microsoft.com/en-us/azure/aks/managed-aad

Hey there @rovin-ms -- as @shubhammicrosoft1 mentioned, you'll want to ensure that the user you created, it also assigned to a group that has been granted k8s RBAC permissions to perform that action.  The simplist being a ClusterRoleBinding of ClusterAdmin.  This is the purpose of the group + tenant ID that is passed into the ARM template.  Feel free to reach out to me for any additional troubleshooting necessary (here or on Teams, whatever works for you).

Thanks @ckittel and @shubhammicrosoft1. I created my own AD group after I posted here and everything worked. I just thought this should be documented for others that come across this issue when going through the steps. Your work is much appreciated!

Glad it works for you.  If you have any more questions @rovin-ms, don't hesitate to ask. Cheers.


No username/password dialog

Hi guys.
Im trying to use sateliizer with facebook, and it works like a charm..
But the thing is, when I open the browser in incognito mode and trying to log a popup shows and it says:
"Not Logged In: You are not logged in. Please login and try again."
Isn't that need to open a dialog where the user enters his facebook credentials(username/password) and then return to my application? am i missing something?

I Had a problem with how i define the application on facebook :)
was missing the "Aoo Domains" section
You can close that Thanks !!


add prop types to most components

@MikeLockz this adds propTypes without coupling it with the functional component changes so we don't have to remove propTypes because fo the issue with functional components.


libraw: 0.19.2 -> 0.19.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libraw/versions.
meta.description for libraw is: '"Library for reading RAW files obtained from digital photo cameras (CRW/CR2, NEF, RAF, DNG, and others)"'.
meta.homepage for libraw is: '"https://www.libraw.org/"

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.19.3 with grep in /nix/store/zagjf5h5bjphx0d8smsxm9dvqjlkp8pc-libraw-0.19.3
directory tree listing: https://gist.github.com/1e2a96e4f365624f4624ceabcfa1ac6b
du listing: https://gist.github.com/ef6a44fdf5b6b030260ba938cc7aba38

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

145 total rebuild path(s)
52 package rebuild(s)
52 x86_64-linux rebuild(s)
41 i686-linux rebuild(s)
12 x86_64-darwin rebuild(s)
40 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
deepin.deepin-image-viewer
enlightenment.econnman
enlightenment.efl
enlightenment.enlightenment
enlightenment.ephoto
enlightenment.rage
enlightenment.terminology
gegl_0_3
gegl_0_4
gimp
gimp-with-plugins
gimpPlugins.exposureBlend
gimpPlugins.focusblur
gimpPlugins.fourier
gimpPlugins.gap
gimpPlugins.gimplensfun
gimpPlugins.gmic
gimpPlugins.lightning
gimpPlugins.lqrPlugin
gimpPlugins.resynthesizer
gimpPlugins.resynthesizer2
gimpPlugins.texturize
gimpPlugins.ufraw
gimpPlugins.waveletSharpen
gmic
gmic_krita_qt
gnome3.gegl_0_4
gnome3.gnome-photos
gnome3.shotwell
gthumb
gwenview
kdeApplications.gwenview
kdeApplications.kdegraphics-thumbnailers
kdeApplications.libkdcraw
krita
libraw
libsForQt5.libkdcraw
libsForQt511.libkdcraw
libsForQt512.libkdcraw
luminanceHDR
megasync
nomacs
pantheon.elementary-photos
photoflow
photoqt
python27Packages.pythonefl
python27Packages.rawkit
python37Packages.pythonefl
python37Packages.rawkit
rapid-photo-downloader

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zagjf5h5bjphx0d8smsxm9dvqjlkp8pc-libraw-0.19.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A libraw https://github.com/r-ryantm/nixpkgs/archive/542f3d77e23c68cae7fcaa06b93ed2dbef1624f8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zagjf5h5bjphx0d8smsxm9dvqjlkp8pc-libraw-0.19.3
ls -la /nix/store/zagjf5h5bjphx0d8smsxm9dvqjlkp8pc-libraw-0.19.3/bin

Release notes: https://www.libraw.org/news/libraw-0-19-3-release
ABI/API Tracker: https://abi-laboratory.pro/index.php?view=compat_report&l=libraw&v1=0.19.2&v2=0.19.3&obj=26246&kind=abi
The issue mentioned there was in the release notes

Note: ABI slightly changed, new variable added at end of class LibRaw Generally, all old code should run w/o recompile, but you're warned...


⚠ Bofrost.de has degraded performance

In 4b54f24, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1075 ms

Resolved: Bofrost.de performance has improved in 02fb004 after 22 minutes.


QS never finds applications

For some reason somtimes QS just never finds applications, I type the name of the application and seems to just find some random item with the same letters in it, not in order or anything, just random, its weird

Quicksilver was designed so you would’t have to type entire names. The letters have to be in order, but they don’t have to be consecutive. For example, to launch “PhotoShop”, you can just type “ps” (or “p” or “o” for that matter). Save yourself some time and type less.
The thing you want might not be the first result (but Quicksilver will learn over time and move the things you use up higher). Do you see the application you’re looking for if you hit ↓ a few times? In the preferences, under Catalog, do you have Applications checked?

don't get me wrong, this is seriously a bug, i type in photoshop after i quit and restart qs and it works just fine, i've used qs for a few years, i can tell this not by no means normal behavior, its very straight

i type in photoshop after i quit and restart qs and it works just fine

Do you only see this problem when Quicksilver starts on login (as reported in #741)? And restarting manually fixes it?

it could be related to this issue with the other issue of mine which you closed

That’s what I was thinking, but you got a date which is not what I expected to see, so there could be another similar problem. A potential fix will be in B66, so let’s revisit this after its released. (Or you could test it now if you feel comfortable building Quicksilver from the latest source.)

i'm comfortable with running around with my pants on my head proclaiming the wonders of quicksilver for efficiency, i am honored to beta test :]

I am having problems with this.
Quicksilver 2.4.0 (4039).
Ctrl+Space ... Type "ME" "MESS" or "MESSAGES" ... it does NOT find /Applications/Messages!
Instead, I get garbage results for files I don't care to have catalogued.  ~/dmesg-phi-inst.txt, /Library/Application Support/iStat Menus Support/iStat Menus 6/iStat Menus Status.app, /System/Library/PrivateFrameworks... ....   NONE of the results contain /Applications/Messages.app.
If I drill down, there is no listing for /Applications/Messages.app.  I want Quicksilver to find files in /Applications/ and ~/Applications/.   I NEVER want it to go into /Library/Application Support/; I NEVER want it to go into /System/Library/.... and I don't want files -- the only 'file-like' access I desire is for things like ~/Downloads if I go ctrl+space 'Do' or 'Dow' or 'Down' ... and I get other results like '/System/Volumes/Preboot/*' ... which I absolutely DO NOT WANT.
In the past, I could pull down the list of matches and set the priority or scoring for a match to 100 or default.  The problem is that ... these applications in /Applications/ are not being included in the catalogue.  I have tried restarting Quicksilver.  I have tried telling Quicksilver to rescan its catalogue.  Neither of these work.
Underneath Quicksilver Preferences => Catalog => Applications, I have 'Sources' listed.  The selected options are 'Applications' and 'Applications (User)' -- which I interpret to mean as -- Quicksilver will look in /Applications/* (recursively), and ~/Applications/* (recursively).  But it does not find these files.  It produces 30 results, none of which are relevant!   The only enabled plugin is the 'Calculator Plugin' ...
This has also occurred with /Applications/Firefox.app ... after restarting Quicksilver a few times, it sometimes will 'find' the /Applications/Firefox.app.  But this is hit-or-miss.

Is there no way to (with the restricted settings, where I have specified ONLY the { /Applications, ~/Applications, and ~/Downloads } folders + Calculator plugin, for these erroneous results to be disabled?
Why doesn't Quicksilver find the files in the folders I have specifically instructed/configured it to look in?

It's so frustrating, I've actually started to use Spotlight for search!  I'd rather have Quicksilver work, as I've used it for 20-ish years -- but it keeps giving me these incorrect results.  30 results for things I haven't asked it to index, and NO results for the things I have instructed it to index -- despite restarting it, despite doing a catalogue rescan.   :(

Can you confirm with the latest release? 2.4.2 has been out for a while.

Ok.  I just downloaded 2.4.2.  I closed and erased 2.4.0.  I put 2.4.2 in /Applications.  I started it.  The behaviour is identical.

What can I do to further troubleshoot this?

Another side-bug; if I have Quicksilver up, I can't do Shift-Cmd-3 or Shift-Cmd-4 to capture what it considers "matches."   If I dismiss the Quicksilver UI, S+C+3 and S+C+4 work as advertised.  If I have the Quicksilver UI up, these shortcuts are broken.

Machine+OS -- 2018 Intel Mac Mini running Sonoma 14.5.

Meta-bug -- on the Quicksilver website, if I load https://qsapp.com/support.php ... and I select "FAQ
See the FAQ Page in the Quicksilver Wiki for a list of Frequently Asked Questions." ...
https://qsapp.com/wiki/FAQ displays:

Following the instructions on https://qsapp.com/manual/Troubleshooting/ ; I opened Console.  Troubleshooting states, "Start Console.app and you’ll see the console.log displayed, most applications write their information to this log. If there isn’t a left hand pane in the window click the Logs button in the toolbar to make it appear (or use the Show Log List command from the View menu). Make sure the console.log is selected, that’s where Quicksilver writes all its information."
The LHS doesn't list 'Console.log' ... If I select the computer, 'start streaming (may impact system performance)' and filter 'Quicksilver' -- zero results.

Should I move my report/comments to a new bug (since this one is closed)?

Yes please -- new issue, and a separate issue for each bug.
For the screenshots of the catalog -- please also expand the right hand sidebar that shows the individual items being indexed. It sure looks like your applications are in there.


IE8 compatibility

When calling PrioritizedSubPub, IE8 will throw errors Function expected and when you log PrioritizedSubPub directly, such as in the console, it is referenced in IE8 as nothing more than:
[object] { }

Ah I found. In the form of:
var  PrioritizedSubPub = PrioritizedSubPub || {};
When doing so, IE8 seems to destroy the variable and set it to {}. Nice quirk.

That's a weird one.
I think a safer check would look like
window.PrioritizedSubPub = window.PrioritizedSubPub || function () {};

Since window is better than using an assumed global that could be undefined. Also, it's a function with static properties.
BTW, I am thinking of renaming this to something catchy. If you have a suggestion, feel free.

Yoke JS?
put a yoke on (a pair of animals); couple or attach with or to a yoke.
I started one a while but can donate the name to you:
https://github.com/camsjams/yokejs

I also saw this definition
>: something that causes people to be treated cruelly and unfairly especially by taking away their freedom
It reminds me of yokel


feat(request, response): change context type to a subclass of dict

ref https://github.com/falconry/falcon/issues/1120
Work in progress:

[x] Make Request / Response use context_type subclassing dict
[x] Update unit tests
[x] Update FAQ
[x] Update benchmark code
[x] Update examples in README.rst and elsewhere
[x] Resolve Hug tests (Hug is relying on dict context) :arrow_left: not any longer an issue with dict subclass approach

@nZac I think I found a semi-elegant way to do that, but I think that would bog down users with warnings being spammed upon every request provided they use dict context. So I think it is best to go forward with this now and give users some breathing space to adapt to the new changes, and start emitting these warnings in a later release.


[bug] connectivity browser cannot select different data source

to reproduce:
use dev (b13cb82)
0/ go to / , select multilevel human atlas, select region, select connectivity
1/ try to select a different data source
expected behaviour:
data source can be selected
click on region results in navigation to the region
actual behaviour:
no new datasource available
click on region does not result in navigation in region
error in console

data source can be selected - You mean that on connected region click, selected region should be changed automatically? if so it is more feature request I guess.
click on region does not result in navigation in region - this issue was valid for first region only and it should be resolved now.

data source can be selected - You mean that on connected region click, selected region should be changed automatically? if so it is more feature request I guess.

No, there are only 1 data data source, namely Average streamline counts from diffusion imaging, 1000BRAINS cohort
On attempt to select another, there is a error logged in console.
it probably is an issue with siibra-api, but it should be:

filed with siibra-api, and tracked here
handled graciously, preferably show the data sources that are not malformed.

Do see multiple sources on Julich brain 2.9 or 1.18?

for v1.18, all are working as intended.
for v2.9, on attempt to change data source, only 1 source is available.
Additionally, after attempt to change data source, single click to navigate to region no longer works
for dev build: https://siibra-explorer.apps-dev.hbp.eu/dev/

fixed by #993


test: add cases for debezium json test

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

introduced testcontainers (mysql and postgres) to test debezium cdc connectors
added test cases for the debezium json parser
added conversion from int to date/time in the json parser

Checklist For Contributors

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[ ] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

10K+ additions lol. Most of them comes from connector_node/risingwave-source-test/src/test/resources/orders.tbl and this file cannot be reviewed easily throught GitHub. I guess it is the test data. Can we generate the data on the fly or download it on-demand during testing?
Btw, are these unit tests or integrations tests? When will the tests be run?

10K+ additions lol. Most of them comes from connector_node/risingwave-source-test/src/test/resources/orders.tbl and this file cannot be reviewed easily throught GitHub. I guess it is the test data. Can we generate the data on the fly or download it on-demand during testing?
Btw, are these unit tests or integrations tests? When will the tests be run?

Yes we are thinking about generating the data on the fly instead of using this big file...Shouldnt be a problem :)
These are unit tests I believe...We will first use testcontainers to start a mysql/postgres instance, insert data into the database and check if the connector successfully captures the changes (number of lines match). We also check if the response json from debezium can be correctly parsed by risingwave and that the datatypes are correct :)


Empty title for demoTNormform.php

The <title> tag is empty thus the page does not validate.

Fixed earlier. Issue outdated. Closing.


Minor tweaks to CI

Some very minor touches to the CI scripts

Looks fine to me. Made a minor suggestion above.

@jakirkham changed as requested

Thanks @crusaderky :)


Some AVIFs cannot be opened in Firefox

Hi,
I got some images which fails with warnings in Compliance Warden. These cannot open in Firefox but work in Chrome and Paint.NET.
I made the initial report at the forum which contains a sample and sob story:
https://forums.getpaint.net/topic/124627-some-avifs-cannot-be-opened-in-firefox/
I am unsure if this is a plug-in issue or upstream. So now I am at least notifying you.
Kind Regards
Claus

If I understood Rick's upvote I should sing my song here instead. Here goes:
Version

Windows 10
paint.net 5.0.12 (Stable 5.12.8735.38135)
Google Chrome Version 121.0.6167.140 (Officiel version) (64-bit)
Firefox 122.0 (64-bit)
AvifFileType v<IP_ADDRESS>
AOM v3.7.1-664-g94fe92f0ed

Bug
paint.net will at times generate avif images which does not conform to the standard. I have not been able to track down when/why. Saving a series of 10 avif files in different resolutions caused problems with 4.
The images can be reopened with paint.net and displayed in Chrome but fails in Firefox.
Firefox has previously been reluctant to address avif issues if they where non-conforming:
https://bugzilla.mozilla.org/show_bug.cgi?id=1700723
The check is done using:
https://gpac.github.io/ComplianceWarden-wasm/index.html
The 4 offending images has no direct errors but they all give multiple warnings on rule #38.
[miaf][Rule #38] Warning: Tile widths should be a multiple of 64. Found XXX

Specification description: MIAF (Multi-Image Application Format)
MPEG-A part 22 - ISO/IEC 23000-22 - w18260 FDIS - Jan 2019

[miaf][Rule #38] Section <IP_ADDRESS>.2
Any grid image in a MIAF file shall also conform to the following constraints:
- The tile_width shall be greater than or equal to 64, and should be a multiple
of 64.
- The tile_height shall be greater than or equal to 64, and should be a multiple
of 64.

The offending images are downscaled versions of the same source image. When saving "Preserve Exisiting Tile Size" was enabled.
It is worth noting that these are warnings and not errors. It might be worth pursuing a bug with Firefox as well but I think it is important to get your stance on this. This might be a more general aom issue or for 0xC0000054 but I have no clue. It is part of the default install so now I start here.
I am unsure if it is a tile issue or that is just a red herring. One offender is attached radio1920x908.avif and I have more samples available at request. This file will fail in Firefox but work in Chrome and Paint.NET.
The sob story
I made a HTML file with this image stack:
<img src="img/radio1920x908.png"
     alt=""
     srcset="img/radio5604x2650.avif 5604w,
             img/radio5120x2421.avif 5120w,
             img/radio4096x1937.avif 4096w,
             img/radio3840x1816.avif 3840w,
             img/radio2560x1211.avif 2560w,
             img/radio2048x968.avif  2048w,
             img/radio1920x908.avif  1920w,
             img/radio1920x908.png   1920w,
             img/radio1280x605.avif  1280w,
             img/radio1280x605.png   1280w,
             img/radio640x303.avif    640w,
             img/radio640x303.png     640w,
             img/radio320x151.avif    320w,
             img/radio320x151.png     320w"
     sizes="100vw">

It worked as expected in Chrome. But in Firefox it blanked out for 1920w, 2048w, 3840w and 5604w. In developer tools it looked like the correct versions downloaded properly. The remaining images in the srcset was picked up and displayed properly. The images opened nicely in Paint.NET which I use for images (duh!). Many (many!!!!) hours of trials, debugging and troubleshooting later I finally tried to open the offending images directly in Firefox (right-click open with) and got the error:

The image [image] cannot be displayed because it contains errors.

The weird thing is that 5604w is an offender as that was the base image and the rest are simply resized versions of that (tiles preserved!). It started as a JPEG and I trimmed the size and removed the background. Then I did the monkey work of resize -> save as avif -> save as png -> repeat x9.
The avif settings was the same each time:
Quality: 43
[ ] Lossless
[X] Lossless Alpha Compression
Encoder preset: Medium
Chroma 4:2:0
[X] Preserve Exisiting Tile Size
[X] Premultiplied Alpha

I do not have steps to reproduce as such. But I suspect if I save enough images then some will fail in Firefox. If need be I will take the time to do that.
Let me know if I am missing something obvious? Anything else you want me to do etc.?
Thank you for your time!
Kind Regards
Claus Andersen

NOTE: I now see there is a later version than the one bundled with Paint.NET. I have not tried that yet as I have no surefire way of reproducing.

Yay! I can reproduce!
I updated the plugin with the latest release.
In the save as dialog in confirms as version 1.1.30 AOM 3.8.1
I did a resize to 1920x908 and could not open in Firefox
I did a resize to 1280x605 and could open in Firefox.
The 1280 was clean in Compliance Warden and the 1920 has warnings:
[miaf][Rule #38] Warning: Tile heights should be a multiple of 64. Found 908
[miaf][Rule #38] Warning: Tile heights should be a multiple of 64. Found 908
[miaf][Rule #38] Warning: Tile heights should be a multiple of 64. Found 908
[miaf][Rule #38] Warning: Tile heights should be a multiple of 64. Found 908

So it would seem that there is some sort of correlation to size.

It gets better:

Open Paint.NET with a blank canvas
Resize to 1920x908
Save as avif

Fails to open in Firefox.
Compliance Warden warns:
[miaf][Rule #38] Warning: Tile heights should be a multiple of 64. Found 908
[miaf][Rule #38] Warning: Tile heights should be a multiple of 64. Found 908

Details:
Version 1.1.30 AOM 3.8.1
Quality: 43
[ ] Lossless
[X] Lossless Alpha Compression
Encoder preset: Medium
Chroma 4:2:0
[X] Preserve Exisiting Tile Size
[X] Premultiplied Alpha

This is a duplicate of issue #23.
The problem is that Firefox does not support tiled images. See https://bugzilla.mozilla.org/show_bug.cgi?id=1696090.
The Compliance Warden warnings are related to a recommendation in the MAIF standard that the individual images in a tiled image should have a width and height that is a multiple of 64, but few (if any) AVIF encoders bother to follow that.
The library that chrome uses for AVIF decoding (libavif), also ignores that recommendation:
// The priority could be to use a cell size that is a multiple of 64, but there is not always a valid one,
// even though it is recommended by MIAF. Just use ceil(numPixels/numCells) for simplicity and to avoid
// as much padding in the right-most and bottom-most cells as possible.

 I only searched the open issues. Sorry!!!
I am a little puzzled as 1280x605 is not a mutipla of 64 either but that works?
So this leaves us between a rock and a hard place. You (more precisely aom) does not want to follow the spec to the letter and Firefox will only care if you are strict.
I will try to complain to Firefox and see if they at least can change the horrible UX so the images are not dropped silently. At least they could log it in the console.

I am a little puzzled as 1280x605 is not a mutipla of 64 either but that works?

If you are saving on the Medium, Slow or Very Slow presets, the plugin will not use tiles for that image.
The Fast, Medium and Slow presets use progressively larger tile sizes. Very Slow does not use tiles at all, but it can take ages to save because of that.

So this leaves us between a rock and a hard place. You (more precisely aom) does not want to follow the spec to the letter and Firefox will only care if you are strict.

It is Firefox that is not following the spec, by their AVIF decoder not supporting tiled/grid images. As I mentioned above the MAIF recommendation that tile/grid images should be a multiple of 64 is effectively ignored by most AVIF decoders and encoders.
Here are 3 tiled/grid images from the official AVIF test suite: Summer_in_Tomsk_720p_5x4_grid.avif, animals_00_multilayer_grid_a1lx.avif and animals_00_multilayer_grid_lsel.avif..
Summer_in_Tomsk_720p_5x4_grid.avif uses tiles that are not multiple of 64, but the other two images do. Firefox can't open any of them.

A workaround to be sure my images works in Firefox would then be to always spend the time and save using the "Very slow" preset if

All images I have put through sqoosh.app does not suffer from this problem. But the workflow will be easier without going that route.

Another option would be to use libavif's avifenc command line app,

Do you happen to know if there are any other known major pitfalls with the Firefox decoder?

The grid issue is the main bug I am aware of. Firefox's general tracking issue for AVIF support is: https://bugzilla.mozilla.org/show_bug.cgi?id=1443863

Brilliant, thanks!


parameter settings different with paper reported.

@ildoonet , I refer to the paper.

At the search stage, #epochs =90. while in your code is 270. If we set the #epochs=90, how to set the lr policy?
At the search stage, #training samples=6000. while in your code, for reduced_imagenet, the #training samples seems almost 50000.

Can you explain this? And which one should I follow?
Many thanks.

@snownus Thanks for the report.

You need to provide --epoch 90 argument, when you run the search.py file. Learning rate scheduler will be adapted accordingly: https://github.com/kakaobrain/fast-autoaugment/blob/master/FastAutoAugment/lr_scheduler.py#L12

I will fix the parameter soon. The paper's parameters should be used. Since we conducted ablation studies internally after submitting the paper, some parameters are incorrect but it is not intentional.

Thanks.

@ildoonet thanks for your instant reply.


python: grpc.secure_channel "Creates an insecure Channel to a server."

Documentation for the secure_channel method is incorrect

Thank you for the report! This was also reported in issue 7791 and has been fixed.


Implement town::update_monthly

This still needs some cleanup, but I wanted to get some feedback wrt. variable naming / general feedback, since I am not too familiar with the code base yet.

Looks good, I will see if I can find out what history represents and any of the other unknown fields. Some of the array logic can also be changed to use std::begin, std::end, std::array, std::fill, std::copy etc.

@ceeac Do you have time to continue work on this, or would you like one of us to take over?

I'll try to finish it this week, I just forgot about it. :) Sorry for the delay.

Good to hear from you! No worries!

History values still differ from vanilla. I've pushed some code to help us investigate.


add compilation guide

this should help those newer to plugin development

I feel that if ‘Right Clicking’ previously linked into ‘Publishing’ then this new page should also lead there when done

Wdym right clicking?

pages/Developer-Guide-(4a-Right-Clicks).md Sorry. Used to link to Publishing now to Compilation. So I feel compilation should link to Publishing now in lieu :)


Ability to use refs/pull/# instead of tag

I have a repo where the Releases themselves are tagged upon creation but no tags are used before hand.
Can we have a feature implmented that can look at refs/pull/n-1 to refs/pull/n and gather the same data?
Run mikepenz/release-changelog-builder-action@v1
  with:
    ignorePreReleases: false
    failOnError: false
    commitMode: false
  env:
    APP_NAME: XXX
    JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/11.0.14-101/x64
    VERSIONNAME: [2](https://github.com/ThePieMonster/XXX/runs/5470140862?check_suite_focus=true#step:8:2).0.[4](https://github.com/ThePieMonster/XXX/runs/5470140862?check_suite_focus=true#step:8:4)
    GITHUB_TOKEN: ***

📘 Reading input values
  /usr/bin/git rev-list --tags --skip=0 --max-count=1
  /usr/bin/git describe --abbrev=0 --tags
  fatal: No names found, cannot describe anything.
  Error: The process '/usr/bin/git' failed with exit code 12[8](https://github.com/ThePieMonster/XXX/runs/5470140862?check_suite_focus=true#step:8:8)

@ThePieMonster instead of the tag you can also use the SHA1 git hash, which should serve as a more flexible solution compared to the refs/pull/.

@mikepenz Included the below code in the Checkout code step which got me a little further.
    - name: Checkout code
      uses: actions/checkout@v2
      with:
        fetch-depth: 0

The last submitted tag that was created upon Release was 2.0.3 in this case. The current build is 2.0.4. I can manually pass this new number as a parameter but the mikepenz/release-changelog-builder-action@v1 still thinks 2.0.3 is the latest it seems.

@mikepenz Got the "create tag" GitHub script to create a tag and pass it through. The build is running as part of a PR (check before a merge) but shows that no PRs are found. Any idea as to why?

The action allows to specify from and to tag as either the git tag or the SHA-1 git hash. There is currently no direct plan to allow it take branches instead.
You can have build steps before this action to retrieve the SHA-1 for a branch if your usecase requires this.
Please also note that generally this action is meant to get release notes for releases (and the respectively merged PRs) which should have specific assigned states.


Possible to adjust image with VCOM value?

I have VSMP running with a 7in5_V2 screen; fantastic project!
Is it possible to adjust the VCOM value in order to try and fine tune the image?  I cannot see where this value is set for the particular screen.

I don't know if you ever found an answer to this, but that would be something to ask on Waveshare's repo.


Update verifiable-credentials-configure-tenant.md

Added link for video-walkthrough

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

#label:"aq-pr-triaged"

#sign-off

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


Playground releases

There are at least two external tutorials for PlutusTx now, and some of the code in those tutorials will stop working soon due to changes such as https://github.com/input-output-hk/plutus/pull/474 (renaming PendingTx' to PendingTx).
The API is not finalised yet and further changes are unavoidable. To prevent a situation where a lot of the documentation is outdated before Plutus is even available on the blockchain we should

Show the current version in the Playground (commit ref + date would be enough)
Record all changes in the changelog
Link from Playground to the deployed version on Github

I think this is in a good place now.


auth: remove unused address scope from openid connect

Signed-off-by: Nandor Kracser<EMAIL_ADDRESS>Summary
I just set up Portus with OpenID Connect authentication using Dex which doesn't support the address scope. I just checked through the code and data returned from that scope is not used at all, so I have removed it from the OAuth request.

@mssola could you please check this?

Spam bot no. bad boy.

bump


Remove arenas, move operations.

In GitLab by @perarnau on Mar 25, 2019, 08:46
New, simpler area implementation. Arena abstraction is removed but can be re-insterted later as an area allocator. The main reason for that change is the simplification of the abstraction that most users will see first: area. The linux implementation in particular was too complex, with too much inner details leaking out.
This merge request also remove dma move operations from the library, to allow us to focus on what works: copies & transforms, while simplifying the overall API. The reality is that move can never be really performant, and including it makes the rest of the library more complex.
Major side-effects of this merge request:

jemalloc not needed at all, and might be reintroduced as an external dependency later if needed.
dma/scratch loose some generic API calls.
most of area API redesigned.

Fixes #23, #20.
Closes #15, #5, #7, #12 (not longer valid).

In GitLab by @perarnau on Mar 25, 2019, 09:43
Missing updates in src/*
By Swann Perarnau on 2019-03-25T14:43:07 (imported from GitLab project)

In GitLab by @perarnau on Mar 27, 2019, 09:05
Another version, with more incremental diffs is on the way.
By Swann Perarnau on 2019-03-27T14:05:43 (imported from GitLab project)

In GitLab by @perarnau on Mar 25, 2019, 11:14
changed the description
By Swann Perarnau on 2019-03-25T16:14:29 (imported from GitLab project)

In GitLab by @perarnau on Mar 25, 2019, 11:21
changed title from {-Noarena-} to {+Remove arenas, move operations.+}
By Swann Perarnau on 2019-03-25T16:21:45 (imported from GitLab project)

In GitLab by @perarnau on Mar 25, 2019, 11:21
changed the description
By Swann Perarnau on 2019-03-25T16:21:46 (imported from GitLab project)

In GitLab by @perarnau on Mar 25, 2019, 15:29
changed this line in version 2 of the diff
By Nicolas Denoyelle on 2019-03-25T20:29:10 (imported from GitLab project)

In GitLab by @perarnau on Mar 25, 2019, 09:06
install-recursive can go away too.
By Swann Perarnau on 2019-03-25T14:06:36 (imported from GitLab project)

In GitLab by @perarnau on Mar 25, 2019, 15:29
added 6 commits
1eec5894 - remove unused autogen options283bf442 - add error handling utils560b2afe - area redesigna7a5e0fc - area redesignaf083cd5 - remove obsolete ruleb45b43c7 - fix error
Compare with previous version
By Nicolas Denoyelle on 2019-03-25T20:29:12 (imported from GitLab project)

In GitLab by @perarnau on Mar 27, 2019, 09:05
closed
By Swann Perarnau on 2019-03-27T14:05:01 (imported from GitLab project)

In GitLab by @perarnau on Mar 25, 2019, 09:22
I think users would expect any function called malloc to behave like a regular malloc, and returning the new pointer instead. That does make it more complicated to deal with error codes, but we can work out an errno-like later.
By Swann Perarnau on 2019-03-25T14:22:55 (imported from GitLab project)

In GitLab by @perarnau on Mar 25, 2019, 09:07
check if autoreconf -rfi would be enough for the entire autogen now
By Swann Perarnau on 2019-03-25T14:07:34 (imported from GitLab project)


Allow specifying supplier for maven dependencies

It looks like createMavenModulePackage is always setting the supplier of the dependency to "NOASSERTION"
It could be nice to have a way to specify the supplier of this maven dependency

It seems that the ntia-conformance-checker is saying that suppliers must be specified for dependencies.
An example sbom generated by this plugin for which the ntia-conformance-checker outputs a warning about missing suppliers:
Components missing an supplier: androidx.annotation:annotation:1.1.0,com.google.protobuf:protobuf-javalite:3.21.8

Maybe we could specify this information by having the plugin allow the build to pass in a service that decides what the supplier should be for a specific dependency.
Maybe this would be similar to the usage of the mapRepoUri

Another option would be to automatically compute the supplier based on some other information; see https://github.com/spdx/spdx-gradle-plugin/pull/29

Resolved via https://github.com/spdx/spdx-gradle-plugin/pull/29 . Thanks!


Test 10'000 votes

Here some bugs which still exist while testing 10'000 votes on a production system:

[x] make sure the votes actually work - my current script sends invalid votes
[x]  don't lose votes, not sure which one is faster of - see also dedis/d-voting#345 dedis/d-voting#346

[ ] adding a queue in the backend to only send one vote every 2 seconds
[x] find the bug and fix

[x] check that we can do 2'000 votes

voting: 100ms-120ms for every ballot
shuffling: 5 minutes
decryption: 2 minutes
error while sending the combination: wrong nonce (2107 < 2110)
cycling nodes
combining: 2 minutes
results seem OK

[x] check that we can do 10'000 votes

closing: 80s
shuffling: failed
changed GetProof to GetRead
shuffling: 9m
decryption: 5m
combining: 1m - frontend shows timeout
results seem OK

[x] check that we can do 10'000 votes - new version w/o GetProof

closing: 7s
shuffling: times out - reloading shows that shuffling is available
shuffling: 11m
decryption: 1m - 1st failed, restarted blocks, restarted decryption
combining: 1m
results seem OK

[x] when getting the list of the forms in the frontend, it loads all votes, just to show the list - the slowdown was in the backend
[x] fixed

[x] #126
[x] check what happens if the nodes restart before/during setup
[x] sometimes the viewchange fails, and I'm not sure if it works with restarting the nodes
[x] sometimes one of the nodes is not available for the initialization step, and then everything fails
[x] look for more Heisenbugs

To be done later:

[ ] #130
[ ] #128
[ ] #127
[ ] #129
[ ] #143

Updated it and closed it. There are a couple of heisenbugs which seem to be fixable by restarting the nodes.


Notebook links for C# 101 open VS Code, for ML.Net they open VS 2022

Just noticed a small inconsistency, not sure if it's intentional.
When I click on C# 101 notebook links, they open .net interactive in vs code (with python set ast the kernel). When I click the ML.NET notebooks they open in visual studio 2022.

What are your thoughts on all links actually opening in GitHub but then at top of Notebook there are links to open in Visual Studio or Visual Studio Code.

That would probably be my preference and I think it would be more familiar to people used to browsing python machine learning notebooks. When casually browsing github links, most of the time I just want to see the code in my browser.
That said, once I've seen the code and decided that I want to try it out, your "click a button to open in visual studio version X" experience is really nice. The F# ecosystem added a related feature to the top of documentation pages built with FSharp.Formatting (see DiffSharp example here) and it is really easy for newcomers to use.

I'll leave this open to track it! Thanks @nhirschey


[Feature][Agent] Support CloudEvents

Description
Support CloudEvents in Agent.
Use case
No response
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@xuesongxs please add more description about this issue, why do we need to support CloudEvents in the agent? do we have a specific use case?

duplicate with https://github.com/apache/inlong/issues/4987, so close it.


Create BaseRecord model to support schema and relations (no active stuff)

Think about has one relation which connects two models using save and update methods. I might need to modify it to support active and non active models

Related to #14


wuff with eclipse-neon -  SWT parts not available at compile time

Hello, I am a little bit stuck on a problem - maybe you can help:
Info
I am developing a eclipse integration for eclipse called egradle (https://github.com/de-jcup/egradle) and I want to execute my testcases in complete eclipse environment so I can test eclipse parts too (currently I don't so many parts are not tested). To eat my own dog food I decided to do the test execution also with gradle so I started to use wuff...
Changes made to get wuff on eclipse-neon running
My target platform is eclipse-neon, I setup the wuff-depencies in
https://github.com/de-jcup/egradle/blob/feature-84-make-eclipse-projects-built-by-gradle/build.gradle
to work with eclipse-neon (3.6.1)
Download + Installation fine
The downloads and the installation to ./wuff are working, all fine.
Build failes on compileJava
at
https://travis-ci.org/de-jcup/egradle/builds/167167495
(or as raw log in https://api.travis-ci.org/jobs/167167496/log.txt?deansi=true)
you can see I am full missing all kind of org.eclipse.swt imports:
e.g.
/home/travis/build/de-jcup/egradle/egradle-plugin-main/src/main/java-eclipse/de/jcup/egradle/eclipse/Activator.java:24: error: package org.eclipse.swt.custom does not exist
but when I execute
./gradlew :egradle-plugin-main:dependencies
at the ouptut, I see the org.eclipse.swt plugin apearing
Question
All I want to do is currently a simple compile and execute all test cases.
So what goes wrong?

I suggest you examine the history of recent responses to issues in this project.
Is there some reason Buildship isn't sufficient for you?

recent responses to issues:
I found nothing about eclipse-neon, so I started to configure for 3.6
Also I found nothing about missing SWT as well - so I started this issue.
buildship:
Hmm.. I tried it (and Gradle IDE) and it felt not good
What I want is simply

execute gradle,
easy synch mechansim (e.g. import all existing gradle build test files to eclipse - egradle does 4500 test imports in less than 3 seconds at my work...)
execute junit tests inside ui on a fast way (e.g. simply click on test method and execute as junit test...)
use eclipse and console parallel without any conflicts
have access to root project parts without duplicated parts etc.
lightweight integration. no special imports necessary, a simple "cleanEclipse eclipse"+ "import existing projects" is all. Means: always working...
no conflicts on importing projects in my eclipse workplace at work
and it was not fulfilled sorry. So I decided to write my own integration and I am happy with it any my collegues too...
(see also https://github.com/de-jcup/egradle/wiki/FAQ)


sccache causes flowistry-driver to fail

When trying to use flowistry for the first time, I get this error message:
Flowistry could not run because your project failed to build with error:
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `sccache /Users/domenukk/.cargo/bin/flowistry-driver rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit status: 2)
  --- stderr
  sccache: error: failed to execute compile
  sccache: caused by: Compiler not supported: "error: expected one of `!` or `[`, found keyword `if`\n --> /var/folders/9b/2lxhyc8567g980pxjn_t3qy40000gn/T/sccachewzZPue/testfile.c:1:2\n  |\n1 | #if defined(__NVCC__)\n  |  ^^ expected one of `!` or `[`\n\nerror: aborting due to previous error\n\n"

Could this be realted to sccache somehow? I'll try without next, but in any case it would be good to find another solution.

Thanks for the bug report @domenukk! It's almost certainly related to sccache. I've never tested with it. I'm not 100% sure if it it's even possible to integrate with sccache, because Flowistry uses a similar mechanism (RUSTC_WORKSPACE_WRAPPER) to integrate with rustc.
I noticed that Clippy also has an open issue on integrating with sccache: https://github.com/rust-lang/rust-clippy/issues/3840
I'll play with this, but I wouldn't expect a fix unless Cargo gets patched to support this. Sorry!

I encountered same problem.

But isn't there a way to bypass sccache and call rustc directly? I'd like to use Flowistry without having to lose the setting that enables sccache system-wide.

Had the same problem with cg_clif: https://github.com/bjorn3/rustc_codegen_cranelift/issues/1091 The problem is indeed sccache. It detects whether it wraps rustc or a C compiler based on the executable name. This means that only "rustc" will be considered a rust compiler accepting the same arguments as rustc. If the executable is named anything different it will assume that is is gcc or clang and attempt to compile some C code using it to detect which C compiler is is exactly. I opened an issue about this a long time ago: https://github.com/mozilla/sccache/issues/861 On cg_clif's side I worked around it by checking if RUSTC_WRAPPER is set to sccache and unsetting it if this is the case.


license of this project

Hi, what's the license of this project? Especially of LibraryLoader.java? I want port that class to my project.

It's MIT - just added the LICENSE file


M5 crash seen while reporting was setup abort() was called at PC 0x40126635 on core 1

Problem
M5 crash seen while reporting was setup abort() was called at PC 0x40126635 on core 1
SHA: d86a7d49e050f6d9eec438934ea205aa93ce77fd
Steps to reproduce:

Pair M5 with chip tool and setup reporting with Min 1s, Max 2s, delta: 1 C
Verify reporting is working fine by changing temp values on M5 board
Exit the temp sensor screen on chip tool and come back into temp sensor screen again
Seems like within ~1-2 mins of step 3, saw M5 crash with below logs on M5:

abort() was called at PC 0x40126635 on core 1
0x40126635: chip::Inet::UDPEndPointImplLwIP::LwIPReceiveUDPMessage(void*, udp_pcb*, pbuf*, ip_addr const*, unsigned short) at /Users/vganji/MATTER-iOS/connectedhomeip/examples/all-clusters-app/esp32/build/esp-idf/chip/../../../../../../config/esp32/third_party/connectedhomeip/src/lib/support/CodeUtils.h:489
(inlined by) chip::ReferenceCounted<chip::Inet::UDPEndPoint, chip::Inet::EndPointDeletorchip::Inet::UDPEndPoint, 1>::Retain() at /Users/vganji/MATTER-iOS/connectedhomeip/examples/all-clusters-app/esp32/build/esp-idf/chip/../../../../../../config/esp32/third_party/connectedhomeip/src/lib/core/ReferenceCounted.h:55
(inlined by) chip::Inet::UDPEndPointImplLwIP::LwIPReceiveUDPMessage(void*, udp_pcb*, pbuf*, ip_addr const*, unsigned short) at /Users/vganji/MATTER-iOS/connectedhomeip/examples/all-clusters-app/esp32/build/esp-idf/chip/../../../../../../config/esp32/third_party/connectedhomeip/src/inet/UDPEndPointImplLwIP.cpp:374
chiptool-logs-M5-crash-seen-during-reporting.txt
M5-logs-M5-crash-seen-during-reporting.txt

@kean-apple Do you still see this with the latest codebase?


Synchronize the GCS bucket with RouteViews archives

ping on this

(to make sure I didn't miss something I mean :) )


Better error handling for authentication exceptions

Right now we just abort without passing on any info.  Also, the abort arguments are in the wrong order.
https://github.com/voryx/Thruway/blob/master/src/Thruway/Authentication/AuthenticationManager.php#L316

This was fixed here: https://github.com/voryx/Thruway/commit/442b2b8e66c5c8b60e413594ec893256cc495b0d


ChromeDebugException: Unexpected error from chrome devtools

flutter_02.log
content:
command
flutter run -d chrome

exception
ChromeDebugException: Unexpected error from chrome devtools:
text: Uncaught
exception:
  description: ReferenceError: require is not defined
    at <anonymous>:1:1
  type: object
  value: null
attempted JS eval: `require('dart_sdk').developer._extensions.keys.toList();`

#0      handleErrorIfPresent (package:dwds/src/services/chrome_proxy_service.dart:569:5)
#1      AppInspector._getExtensionRpcs (package:dwds/src/debugging/inspector.dart:505:5)
<asynchronous suspension>
#2      AppInspector._initialize (package:dwds/src/debugging/inspector.dart:78:40)
<asynchronous suspension>
#3      AppInspector.initialize (package:dwds/src/debugging/inspector.dart:108:21)
#4      _AsyncAwaitCompleter.start (dart:async-patch/async_patch.dart:43:6)
#5      AppInspector.initialize (package:dwds/src/debugging/inspector.dart:84:41)
#6      ChromeProxyService.createIsolate (package:dwds/src/services/chrome_proxy_service.dart:112:37)
#7      _AsyncAwaitCompleter.start (dart:async-patch/async_patch.dart:43:6)
#8      ChromeProxyService.createIsolate (package:dwds/src/services/chrome_proxy_service.dart:106:29)
#9      ChromeProxyService.create (package:dwds/src/services/chrome_proxy_service.dart:86:19)
#10     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#11     _rootRunUnary (dart:async/zone.dart:1132:38)
#12     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#13     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#14     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#15     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#16     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#17     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#18     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#19     ChromeProxyService._initialize (package:dwds/src/services/chrome_proxy_service.dart)
#20     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#21     _rootRunUnary (dart:async/zone.dart:1132:38)
#22     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#23     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#24     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#25     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#26     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#27     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#28     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#29     Debugger.create (package:dwds/src/debugging/debugger.dart)
#30     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#31     _rootRunUnary (dart:async/zone.dart:1132:38)
#32     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#33     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#34     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#35     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#36     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#37     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#38     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#39     Debugger._initialize (package:dwds/src/debugging/debugger.dart)
#40     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#41     _rootRunUnary (dart:async/zone.dart:1132:38)
#42     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#43     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#44     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#45     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#46     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#47     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
#48     _rootRun (dart:async/zone.dart:1124:13)
#49     _CustomZone.run (dart:async/zone.dart:1021:19)
#50     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#51     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#52     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#53     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#54     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#55     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

flutter doctor
[✓] Flutter (Channel master, v1.10.5-pre.23, on Mac OS X 10.13.6 17G8030, locale zh-Hans-CN)
    • Flutter version 1.10.5-pre.23 at /Users/evanzhengli/Documents/flu/flutter
    • Framework revision e026bd3d33 (44 分钟前), 2019-09-19 07:29:41 -0400
    • Engine revision 1cada0a6dc
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 ea969c358e)

[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/evanzhengli/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/evanzhengli/Library/Android/sdk
    • Java binary at: /Library/Java/JavaVirtualMachines/jdk-12.0.2.jdk/Contents/Home/bin/java
    • Java version Java(TM) SE Runtime Environment (build 12.0.2+10)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.dev/setup/#android-setup for detailed instructions.

[✗] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install:
        sudo gem install cocoapods
        pod setup

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

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/setup/#android-setup for detailed instructions).

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

[✓] Proxy Configuration
    • HTTP_PROXY is set
    • NO_PROXY is .oa.com,localhost,<IP_ADDRESS>
    • NO_PROXY contains <IP_ADDRESS>
    • NO_PROXY contains localhost

[✓] Connected device (2 available)
    • Chrome • chrome • web-javascript • Google Chrome 76.0.3809.132
    • Server • web    • web-javascript • Flutter Tools

! Doctor found issues in 3 categories.

Does this happen with any App that you try?
If not, can you share this apps code?

I think this should be fixed with https://github.com/flutter/flutter/pull/40766

Windows7 x64
command
flutter run -d chrome
exception
ChromeDebugException: Unexpected error from chrome devtools:
text: Uncaught
exception:
description: ReferenceError: require is not defined
at :1:1
type: object
value: null
attempted JS eval: require('dart_sdk').dart.getLibraries();
#0      handleErrorIfPresent (package:dwds/src/services/chrome_proxy_service.dart:569:5)
#1      AppInspector._getLibraryRefs (package:dwds/src/debugging/inspector.dart:489:5)
<asynchronous suspension>
#2      AppInspector._initialize (package:dwds/src/debugging/inspector.dart:72:36)
<asynchronous suspension>
#3      AppInspector.initialize (package:dwds/src/debugging/inspector.dart:108:21)
#4      _AsyncAwaitCompleter.start (dart:async-patch/async_patch.dart:43:6)
#5      AppInspector.initialize (package:dwds/src/debugging/inspector.dart:84:41)
#6      ChromeProxyService.createIsolate (package:dwds/src/services/chrome_proxy_service.dart:112:37)
#7      _AsyncAwaitCompleter.start (dart:async-patch/async_patch.dart:43:6)
#8      ChromeProxyService.createIsolate (package:dwds/src/services/chrome_proxy_service.dart:106:29)
#9      ChromeProxyService.create (package:dwds/src/services/chrome_proxy_service.dart:86:19)
#10     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#11     _rootRunUnary (dart:async/zone.dart:1132:38)
#12     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#13     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#14     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#15     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#16     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#17     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#18     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#19     ChromeProxyService._initialize (package:dwds/src/services/chrome_proxy_service.dart)
#20     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#21     _rootRunUnary (dart:async/zone.dart:1132:38)
#22     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#23     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#24     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#25     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#26     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#27     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#28     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#29     Debugger.create (package:dwds/src/debugging/debugger.dart)
#30     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#31     _rootRunUnary (dart:async/zone.dart:1132:38)
#32     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#33     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#34     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#35     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#36     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#37     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#38     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#39     Debugger._initialize (package:dwds/src/debugging/debugger.dart)
#40     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#41     _rootRunUnary (dart:async/zone.dart:1132:38)
#42     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#43     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#44     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#45     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#46     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#47     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
#48     _rootRun (dart:async/zone.dart:1124:13)
#49     _CustomZone.run (dart:async/zone.dart:1021:19)
#50     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#51     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#52     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#53     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#54     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#55     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

flutter doctor
[✓] Flutter (Channel master, v1.10.6-pre.29, on Microsoft Windows [Version
    6.1.7601], locale zh-CN)
    • Flutter version 1.10.6-pre.29 at D:\flutter
    • Framework revision 919cc97f6a (2 days ago), 2019-09-20 14:57:05 -0700
    • Engine revision 99092a0436
    • Dart version 2.6.0 (build 2.6.0-dev.1.0 7c1821c4aa)

[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\undcover\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: D:\AndroidStudio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    ✗ Android licenses not accepted.  To resolve this, run: flutter doctor
      --android-licenses

[✓] Chrome - develop for the web
    • Chrome at
      C:\Users\undcover\AppData\Local\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 3.2)
    • Android Studio at D:\AndroidStudio
    • Flutter plugin version 31.3.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[!] IntelliJ IDEA Ultimate Edition (version 2018.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2018.2.5
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[✓] Connected device (2 available)
    • Chrome • chrome • web-javascript • Google Chrome 73.0.3683.75
    • Server • web    • web-javascript • Flutter Tools

! Doctor found issues in 2 categories.

@jonahwilliams Looks as if its not fixed in the current master. Is the PR not yet published?

Hi @asmallkite
this pr should have solved the issue;
if  you are still experiencing this issue with the latest version of Flutter?
If the issue persist please provide your updated
flutter doctor -v and flutter run --verbose
together with a minimal code sample to reproduce the problem
thank you

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.


Adding E2E CI

Description
What's new?

Added the CI and some E2E tests. #1780

What kind of change does this PR introduce?

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

Closing it a duplicate to #1898


Caching Device Allocator fails with debug output enabled

Bryan F
Jun 1
Visual Studio 2013, CUDA 7.5, CUB 1.5.2
Error in util_allocator.cuh@Line 414: map/set iterator not dereferencable
This issue is caused by erase being called on the block iterator before the debug output is printed.
cached_blocks.erase(block_itr);
cached_bytes[device].free -= search_key.bytes;
cached_bytes[device].live += search_key.bytes;
if (debug) _CubLog("\tDevice %d reused cached block at %p (%lld bytes) for stream %lld (previously associated with stream %lld).\n",
device, search_key.d_ptr, (long long)search_key.bytes, (long long)search_key.associated_stream, (long long)block_itr->associated_stream);
Fixed:
cached_bytes[device].free -= search_key.bytes;
cached_bytes[device].live += search_key.bytes;
if (debug) _CubLog("\tDevice %d reused cached block at %p (%lld bytes) for stream %lld (previously associated with stream %lld).\n",
device, search_key.d_ptr, (long long)search_key.bytes, (long long)search_key.associated_stream, (long long)block_itr->associated_stream);
cached_blocks.erase(block_itr);
The same error should occur at several locations where block_itr is used in the debug output.

Should this issue be closed?

Adding James.
Bryan
On Thu, Nov 17, 2016 at 8:24 AM, Daniel Trebbien<EMAIL_ADDRESS>wrote:

Should this issue be closed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NVlabs/cub/issues/45#issuecomment-261293949, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACdv4FQNBdUr_xowhpfk73y8qcc1P3pMks5q_H_GgaJpZM4I1nR3
.

Fixed in the above commit for v1.5.5


Placeholder text returning to default

I have a small issue with the placeholder text being reset t0o the default NMessenger after dismissing the keyboard
I set the default placeholder text with
inputBarView.textInputView.text = "Enter a message..."
When loading the view this displays fine, but if you click into the text field then dismiss the keyboard it reverts to "NMessenger"

Not sure but I might have fixed that in https://github.com/eBay/NMessenger/pull/123


docs: Rename steelthreads to agriculture-gov-au

Updated all references of steelthreads to agriculture-gov-au
View preview
Checklist
Preflight

[x] Prefix the PR title with the slug of the package or component - e.g. accordion: Updated padding or docs: Updated header links
[x] Describe the changes clearly in the PR description
[x] Read and check your code before tagging someone for review
[x] Create a changeset file by running yarn changeset. Learn more about change management.

Documentation

[x] Create or update documentation on the website
[ ] Create or update stories for Storybook
[ ] Create or update stories for Playroom snippets

Approving for now, but let's not merged until the DNS is updated.


Is links: {} valid?

This response currently validates against the schema:
"relationships": {
  "posts": {
    "links": {}
  }
}

The documentation on links is a little unclear here - is the above actually valid, or should one of self/href/meta be present?

I don't see any issue, in the spec or conceptually, with links being an empty object.

👍 thanks for the clarification!