Group cluster 0xfffc and TC_IDM_10_2 (CON-1333)

Hi All,
I am preparing a thermostat for the Matter 1.3 certification.
While I do the test harness I have an issue with the case TC_IDM_10_2.
The test harness log shows:
[MatterTest] 09-13 07:03:00.011 INFO
Problem: ProblemSeverity.ERROR
test_name: IDM-10.2
location:
Endpoint: 1,
Cluster:  4 (0x04) Groups,
Attribute:65532 (0xfffc)
problem: Unknown feature with mask 0x80
spec_location:
[MatterTest] 09-13 07:03:00.012 INFO
Problem: ProblemSeverity.ERROR
test_name: IDM-10.2
location:
Endpoint: 2,
Cluster:  4 (0x04) Groups,
Attribute:65532 (0xfffc)
problem: Unknown feature with mask 0x80
spec_location:
It said the groups cluster fail to pass the test and I don't know how to fix it.
In my program I didn't handle anything about the groups, just created two endpoints, one is thermostat another one is fan
the esp32c3 log shows:
I (1652) esp_matter_core: Dynamic endpoint 0 added
I (1652) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000003's Attribute 0x00000001 is 0 **********
I (1672) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000004's Attribute 0x00000000 is 128 **********
I (1682) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000004's Attribute 0x0000FFFC is <invalid type: 0> **********
I (1692) esp_matter_core: Dynamic endpoint 1 added
I (1702) esp_matter_attribute: ********** W : Endpoint 0x0002's Cluster 0x00000003's Attribute 0x00000001 is 0 **********
I (1712) esp_matter_attribute: ********** W : Endpoint 0x0002's Cluster 0x00000004's Attribute 0x00000000 is 128 **********
I (1722) esp_matter_attribute: ********** W : Endpoint 0x0002's Cluster 0x00000004's Attribute 0x0000FFFC is <invalid type: 0> **********
I (1732) esp_matter_core: Dynamic endpoint 2 added
How can I make the FFFC become valid and pass the test? Thanks a lot for your help!

@david0215 we need more information to debug this problem, can you help with the below template
Environment

ESP-Matter Commit Id:

ESP-IDF Commit Id:

SoC (eg: ESP32 or ESP32-C3):

Device Logs (Please attach the log file):

TH version or commit-id of the TH:

Commissioner's logs if present: <here, chip-tool logs, i.e. logs from TH will help>

Any additional details
...

Hi Shubamdp,
Thanks for your reply, here is the information:
ESP-IDF: a322e6bdad (HEAD, tag: v5.2.1) change(version): Update version to 5.2.1
ESP-Matter : 67dda26 (HEAD -> main, origin/main, origin/HEAD) Merge branch 'esp_matter/simplification_core_cpp' into 'main'
TH version : origin/v2.10.1+spring2024
SoC: ESP32-C3
esp32c3 log:
esp32c3_log.txt
TH log:
UI_Test_Run_2024_09_13_10_40_23.log

@david0215 thanks for reporting, can you please try applying this patch and see if it works https://github.com/shubhamdp/esp-matter/commit/50a40b9ac5695d6a2b3390df73897dd2373a3f05
curl https://github.com/shubhamdp/esp-matter/commit/50a40b9ac5695d6a2b3390df73897dd2373a3f05.patch | git am

It works! Thank you @shubhamdp !

It also help to pass the TC_IDM_10_2 test

@david0215 Thanks for the verification


Add support for parser schemas

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

Project coverage is 95.02%. Comparing base (b114822) to head (60017bf).
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1210      +/-   ##
==========================================
+ Coverage   95.00%   95.02%   +0.02%
==========================================
  Files         104      104
  Lines       12503    12570      +67
==========================================
+ Hits        11878    11945      +67
  Misses        475      475
  Partials      150      150

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Refactor connection options and features into attrs classes

Added ConnectionOptions and ConnectionFeatures attrs classes to allow reusing connection arguments in new Reader and Writer classes keeping type annotations as strict as possible.
This also simplifies the usage of those arguments in user-defined wrappers for these classes.

Tests fail because of from ansq import __version__ import in setup.py that triggers import attr whilst attrs package is not installed yet.

Tests fail because of from ansq import __version__ import in setup.py that triggers import attr whilst attrs package is not installed yet.

Fixed in #47

Codecov Report

Merging #45 (a499bc5) into master (a1fa4e5) will decrease coverage by 0.46%.
The diff coverage is 70.76%.

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
- Coverage   85.05%   84.59%   -0.47%
==========================================
  Files          32       32
  Lines        1653     1694      +41
  Branches      168      166       -2
==========================================
+ Hits         1406     1433      +27
- Misses        191      202      +11
- Partials       56       59       +3

Impacted Files
Coverage Δ

ansq/tcp/connection.py
63.75% <18.75%> (-1.75%)
:arrow_down:

ansq/tcp/reader.py
81.25% <75.00%> (ø)

ansq/tcp/types/connection.py
81.70% <86.84%> (+0.22%)
:arrow_up:

ansq/tcp/types/__init__.py
100.00% <100.00%> (ø)

ansq/tcp/types/client.py
76.47% <100.00%> (+0.71%)
:arrow_up:

ansq/tcp/writer.py
92.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Lint Error

The lint error that was in 5.5 is still here in 6.0
See: https://github.com/FIRST-Tech-Challenge/SkyStone/issues/262

To clarify, this isn't an issue with Travis CI; this is an issue that has to do with the lint gradle task. However, this comes up in Travis CI because it likely uses some form of ./gradlew build under the hood, which would invoke the lint gradle task. This also precludes using ./gradlew build from the command line in the FTC SDK.
Any call to the lint task will cause this error however (in this case caused by running ./gradlew lint:
> Task :FtcRobotController:lint FAILED
Ran lint on variant debug: 34 issues found
Ran lint on variant release: 34 issues found
Wrote HTML report to file:///home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/build/reports/lint-results.html
Wrote XML report to file:///home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/build/reports/lint-results.xml

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':FtcRobotController:lint'.
> Lint found errors in the project; aborting build.

  Fix the issues identified by lint, or add the following to your build script to proceed with errors:
  ...
  android {
      lintOptions {
          abortOnError false
      }
  }
  ...

  The first 3 errors (out of 5) were:
  /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:39: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
      android:showAsAction="never"
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:44: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
      android:showAsAction="never"
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:50: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
      android:showAsAction="never"
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Steps for reproduction:

cd into the sdk's directory from the command line
run ./gradlew lint (or ./gradlew build!)

Note: this was run on Fedora, however I doubt OS would matter here
Now of course, this isn't really an issue if you don't call ./gradlew lint, however this also occurs when you run ./gradlew build, which is the most convienient way to build from the command line and how CI would likely go about doing things.
This can either be fixed by fixing the actual lint errors, or by adding
android {
      lintOptions {
          abortOnError false
      }
  }

to the build.gradle of the affected modules.
Of course, actually fixing the lint errors would seem to be the preferred course of action.

adding
android {       lintOptions {           abortOnError false       }   }
still results in the same lint errors,
however, running ./gradlew build -x lint seemed to work for me

This error is still there in 7.0

Can confirm, still here in 7.0...

This will be fixed in the next release

Fixed in 7.1


Thrift.Protocol.TProtocolException: 'don't know what type: 13' Exception on read

Version: Parquet.Net v2.1.1
Expected behavior
Simple Parquet file created and then read back successfully.
Actual behavior
An error is encountered on line:
dsread = reader.Read()
The exception is
Thrift.Protocol.TProtocolException: 'don't know what type: 13'
Steps to reproduce the behavior
Run method below.
Code snippet reproducing the behavior

private void ParquetDemo()
{
    DataSet ds = new DataSet(new DataField<string>("City"), new DataField<Int32>("ID"));
    ds.Add("London", 1);
    ds.Add("Cochin", 2);
    using (Stream fileStream = File.OpenWrite("..\\..\\outputs\\Demo.txt"))
    {
        using (var writer = new ParquetWriter(fileStream))
        {
            writer.Write(ds);
        }
    }

    DataSet dsread;
    using (Stream fs = File.OpenRead("..\\..\\outputs\\Demo.txt"))
    {
        using (var reader = new ParquetReader(fs))
        {
            dsread = reader.Read();
        }
    }
}

Demo.txt

@GKallarackal exactly same code works for me, can you try absolute file path or just make sure that directory exists?

Hi
Thanks for the quick response. The file reading and writing is fine that is
not the problem.
Which version of the .Net Framework are you using? I realise I am using
4.5.2.
Regards
George
On 11 December 2017 at 16:18, Ivan Gavryliuk<EMAIL_ADDRESS>wrote:

@GKallarackal https://github.com/gkallarackal exactly same code works
for me, can you try absolute file path or just make sure that directory
exists?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastacloud/parquet-dotnet/issues/282#issuecomment-350773880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfniATHCw9JOxLCpaH0ryMSQNGd_KPVVks5s_VXngaJpZM4Q9nHb
.

Problem solved when I changed to 4.6.1.
Regards
George
On 11 December 2017 at 16:23, George Kallarackal<EMAIL_ADDRESS>wrote:

Hi
Thanks for the quick response. The file reading and writing is fine that
is not the problem.
Which version of the .Net Framework are you using? I realise I am using
4.5.2.
Regards
George
On 11 December 2017 at 16:18, Ivan Gavryliuk<EMAIL_ADDRESS>wrote:

@GKallarackal https://github.com/gkallarackal exactly same code works
for me, can you try absolute file path or just make sure that directory
exists?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastacloud/parquet-dotnet/issues/282#issuecomment-350773880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfniATHCw9JOxLCpaH0ryMSQNGd_KPVVks5s_VXngaJpZM4Q9nHb
.

@GKallarackal good point, we're running integration tests only under .NET Core 1.1 at the moment. Ideally should be running on several targets.

Actually, the use case I have is trying to create files for AWS Athena and
I am struggling to create examples that work in Athena with Double or
Decimal data types.
Should I change to .net core 1.1?
On 11 December 2017 at 16:39, Ivan Gavryliuk<EMAIL_ADDRESS>wrote:

@GKallarackal https://github.com/gkallarackal good point, we're running
integration tests only under .NET Core 1.1 at the moment. Ideally should be
running on several targets.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastacloud/parquet-dotnet/issues/282#issuecomment-350780675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfniAUGMU0N0QHhbPCcGyqe1z83fCzYHks5s_VregaJpZM4Q9nHb
.

@GKallarackal framework doesn't matter much, but there is a known issue with Athena and decimal types when it doesn't support decimals according to specs. You should  use DecimalDataField and set forceByteArrayEncoding to true to be readable by Athena/Impala.

Great thanks will give that a go.
George
On 11 December 2017 at 16:46, Ivan Gavryliuk<EMAIL_ADDRESS>wrote:

@GKallarackal https://github.com/gkallarackal framework doesn't matter
much, but there is a known issue with Athena and decimal types when it
doesn't support decimals according to specs. You should use
DecimalDataField and set forceByteArrayEncoding to true to be readable by
Athena/Impala.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastacloud/parquet-dotnet/issues/282#issuecomment-350782759,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfniAc-xL-nd2syXpE7nSetAaSDGMmtIks5s_VxZgaJpZM4Q9nHb
.

Is there a similar issue with Double?
On 11 December 2017 at 16:47, George Kallarackal<EMAIL_ADDRESS>wrote:

Great thanks will give that a go.
George
On 11 December 2017 at 16:46, Ivan Gavryliuk<EMAIL_ADDRESS>wrote:

@GKallarackal https://github.com/gkallarackal framework doesn't matter
much, but there is a known issue with Athena and decimal types when it
doesn't support decimals according to specs. You should use
DecimalDataField and set forceByteArrayEncoding to true to be readable
by Athena/Impala.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastacloud/parquet-dotnet/issues/282#issuecomment-350782759,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfniAc-xL-nd2syXpE7nSetAaSDGMmtIks5s_VxZgaJpZM4Q9nHb
.

No, decimals only ;)

I have used code below to create file.
private void CreateFilesTest2()
{
DataSet ds = new DataSet(new DecimalDataField("ElementID1", 38, 15,
true));
Random r = new Random;
ds.Add((decimal)1.23);
Directory.CreateDirectory("..\..\outputs\Test2\");
WriteFile("..\..\outputs\Test2\SimpleTest.parquet", ds);
ds.Clear();
}
Then run this on Athena
CREATE EXTERNAL TABLE IF NOT EXISTS default.PeerInsightTest2 (
ElementID DECIMAL (38, 15)
)
STORED AS PARQUET
LOCATION 's3://athenatestgk/Parquet/PeerInsightsTest2/';
followed by
MSCK REPAIR TABLE default.PeerInsightTest2;
But when I
select * from PeerInsightTest2
I get this error:
An error occurred when executing the SQL command:
select * from PeerInsightTest2
HIVE_CANNOT_OPEN_SPLIT: Error opening Hive split
s3://athenatestgk/Parquet/PeerInsightsTest2/SimpleTest.parquet (offset=0,
length=296): can not read class parquet.format.FileMetaData: don't know
what type: 14 [SQL State=FAILED]
1 statement failed.
On 11 December 2017 at 16:49, Ivan Gavryliuk<EMAIL_ADDRESS>wrote:

No, decimals only ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastacloud/parquet-dotnet/issues/282#issuecomment-350784050,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfniASSNiLDEgBcUyzr99Gvz0yxCeCvMks5s_V03gaJpZM4Q9nHb
.

I'm not sure to be honest. Well have a look. It may take some time as AWS Athena team is not very responsive)

@GKallarackal is this still an issue?

I was not able to resolve it so yes. I moved forward by storing data as
strings but that is far from ideal.
George
On Fri, 16 Feb 2018, 09:15 Ivan Gavryliuk<EMAIL_ADDRESS>wrote:

@GKallarackal https://github.com/gkallarackal is this still an issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastacloud/parquet-dotnet/issues/282#issuecomment-366181947,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfniAcxa1bQDnSgYZTxseEKAo17jEAwvks5tVUdEgaJpZM4Q9nHb
.

@GKallarackal sorry I've got a slight problem with AWS as I don't have a test environment for this. Unfortunately AWS doesn't always follow parquet standard, we've seen this many times, therefore these issues. I'll try to arrange something soon.

I got same problem - it's because AWS streams don't return all data, and ParquetReader always expectes that Stream.Read will return exactly number of bytes requested.
Here https://docs.microsoft.com/en-us/dotnet/api/system.io.stream.read?view=netframework-4.7.2 it says:
An implementation is free to return fewer bytes than requested even if the end of the stream has not been reached.
I encountered same error, had to write Stream wrapper that executes Read until count is reached

More precisely, it's because .Net HTTP treams (AWS being such case) return amount they currently read in their buffer.
I see that everywhere in the code Read is only called on streams once and returned number of bytes actually read is ignored.

Closing as not an issue. The fact parquet is not streamable format is well known. You have to have file available on the node.


An update is needed for example code of this library in PlatformIO extension of VS Code

I used your library today in VS Code, I verified the code on Arduino UNO board,
the IDE said: 'class Ultrasonic' has no member named 'read'
by the intellisense function, I knew it was "distanceRead()" rather than "read()", so maybe there need an update in your example code in PlatformIO extension for VS Code.

And, when I used it, it shown negative value sometimes, like "-277 cm", what did it mean ?

Hi @mianqi2016!
The "distanceRead ()" method has been replaced by "read ()". It should continue to work, but will issue a warning during compilation.
From what I saw in the example on Platformio.org, the available example is correct, just like the ones available here on GitHub.
Unfortunately, I am not responsible for updating the library within the PlatformIO platform, I believe they automatically take the code released here on GitHub. I checked the source code available there and it, like the examples, is the same as what is here on GitHub. Anyway, I can do some tests if you give me more details about your development environment and what Arduino Board you are using.
As for the negative reading value, this would not be possible due to the implementation of the library, since the value returned by the read method is unsigned int. So, I imagine two possible problems:

An incorrect conversion of data types;
Some problem with the circuit, especially with the wires connecting the trigger and the echo.

If you can share the code snippet where the value is read and displayed on the console, I can help.
In any case, thank you very much for using the library and for sharing your doubts. I hope I can help you.

Sometimes, it showed negative value, expecialy when I put a barrier nearer than 3cm, is it normal?

发件人: Erick Sim?es<EMAIL_ADDRESS>发送时间: 2020年8月20日 20:14
收件人: ErickSimoes/Ultrasonic<EMAIL_ADDRESS>抄送: Mian Qi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>主题: Re: [ErickSimoes/Ultrasonic] An update is needed for example code of this library in PlatformIO extension of VS Code (#52)
Hi @mianqi2016https://github.com/mianqi2016!
The "distanceRead ()" method has been replaced by "read ()". It should continue to work, but will issue a warning during compilation.
From what I saw in the example on Platformio.orghttps://platformio.org/lib/show/1507/Ultrasonic/examples, the available example is correct, just like the ones available here on GitHub.
Unfortunately, I am not responsible for updating the library within the PlatformIO platform, I believe they automatically take the code released here on GitHub. I checked the source code available there and it, like the examples, is the same as what is here on GitHub. Anyway, I can do some tests if you give me more details about your development environment and what Arduino Board you are using.
As for the negative reading value, this would not be possible due to the implementation of the library, since the value returned by the read method is unsigned int. So, I imagine two possible problems:

An incorrect conversion of data types;
Some problem with the circuit, especially with the wires connecting the trigger and the echo.

If you can share the code snippet where the value is read and displayed on the console, I can help.
In any case, thank you very much for using the library and for sharing your doubts. I hope I can help you.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/ErickSimoes/Ultrasonic/issues/52#issuecomment-677880363, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFPCOAX6GATVQGR6NN4BIZLSBV73TANCNFSM4PPU4UVQ.


Migrate from dartsim to dartsim-cpp

Since https://github.com/conda-forge/dartsim-feedstock/pull/75 dartsim contains both C++ and Python libraries, in Gazebo we just need the C++ library. Furthermore, this rebuilds gazebo against a version of dartsim that is built against fmt 11.
Similar to https://github.com/conda-forge/gazebo-feedstock/pull/227 .
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

fyi @jslee02 @fabiobergonti


New tests fail with the current implementation

I added tests for some special case in the branch https://github.com/axel-op/feature_discovery/tree/testing
I noticed that markStepComplete doesn't work properly with these tests because the tests can't find the next overlay after it has been called (it's like it's not displayed at all).
However on a device this seems to work fine.

I would suggest that you just merge your implementation if you plan on working on the plugin further. That would get rid of a lot of difficulties.

Closed because #20 has been merged


FULL White preview

Describe the bug
When i generate something nevermind what the preview always shows me a full white page and when i downloaded it, it comes to every files etc, etc, but i just see an only white page, its happened from one day to the next

Photo in link: https://kephost.net/p/MTYxMzI4OA.png
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-qupyamdm
Validations

[X] Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.

Steps to reproduce
IDK, i guess it's an opera gx bug? mybee.. but i dont think soo, cuz when i try it in brave showed me nothing again, just a white page
Expected behavior
it has always shown the page
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 OPR/<IP_ADDRESS>
performance.memory = {
  "totalJSHeapSize": 52230776,
  "usedJSHeapSize": 49014340,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = KaV3R
Chat ID = a7329187840a

Additional context
No response

Same issue here, been struggling for the last week trying to sort this out. Now the code seem to be in a loop and the page crashes


[fix][doc] Fix 404 in security-tls-transport.md

Fixes #16877,  fixes #16844
Motivation
There is a 404 link in the doc of security > Transport Encryption.
wget https://raw.githubusercontent.com/apache/pulsar/master/site2/website/static/examples/openssl.cnf

Modifications

Fix the link

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[ ] doc-not-needed
(Please explain why)

[x] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

FYI @urfreespace

I am getting this again
wget https://raw.githubusercontent.com/apache/pulsar-site/main/site2/website/static/examples/openssl.cnf
--2022-11-19 14:09:57--  https://raw.githubusercontent.com/apache/pulsar-site/main/site2/website/static/examples/openssl.cnf
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8000::154, 2606:50c0:8003::154, 2606:50c0:8002::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8000::154|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-11-19 14:09:57 ERROR 404: Not Found.

The issue is still there.

File structure is changed. And we should use url based on pulsar.apache.org instead of github.
I'll push a fix in hours.
cc @delgemoon @JohnTangZX

@JohnTangZX @delgemoon The link is updated to https://pulsar.apache.org/examples/openssl.cnf, and the latest doc is changed also.
If you still encounter the issue, please share what page (url) you see the link, as well as a screenshot.


Update to 2.2.0

Fixes #3 and #4. Removed supporters/golden key features from the original plugin as appeared that such things may not pass Apple's app review.

@parkeyparker Hey Aaaron, could you give an update as soon as this extension passes App Review? Really helpfull! Ty

@dbektas will do, however currently in discussions with the creator of the extension itself as I need to get their permission before I can actually release it.

@dbektas It's passed App Review and the original creator is happy with me release it so you can now find it here: https://apps.apple.com/gb/app/aws-extend-switch-roles/id1592710340 (available for MacOS and iOS which is super handy when quickly trying to do something on an iPad for example)


Upgrade Solhint version to catch new rules

I'm using Solhint 3.6.2, which provides a rule immutable-vars-naming to use SNAKE_CASE for immutable state, there was also a PR on Solhint repo to fix the var-name-mixedcase rule to disregard immutable variables, which was added in Solhint 3.5.1.
This extension is using Solhint 3.4.0 though, so it's making VS Code to give false positive errors:

Is there a way to configure the extension to use a higher Solhint version, or rather would it be ok to upgrade Solhint version on this extension? I'm keen on opening a PR for this if this is desirable.
Thanks for such a great extension!!!

+1

@AlissonRS it is now integrated in the latest versions


Optimize staging

Optimize the performance of staging (zipping) for large file sizes. Consider using Java 7 nio.
Make sure that if we zip with Java zip streams, we can still unzip correctly with TrueZip, write JUnit tests for this.
Upgrade from TrueZip to TrueVFS.
Create performance tests which will be executed at will. What is the best framework for at-will test that don't run every time you do mvn clean install?

Done


Hide Animation Frames section when there are no animations

Fixes #74372
When there are no animations, a message is shown, similar to other parts of the engine, like the Animation Player, and TileMap editor :

The message goes away when at least one animation is added :

Thanks!

Cherry-picked for 4.0.4.


Fixing KMSFactory and CryptoServiceFacotry's constructor

Fix KeyManagementServiceFactory and CryptoServiceFactory to take in MetricRegistry for the purpose of metrics.
SLA: 5 mins
Reviewers: Casey

Codecov Report

Merging #770 into master will decrease coverage by 0.08%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #770      +/-   ##
============================================
- Coverage     65.67%   65.58%   -0.09%
+ Complexity     3904     3901       -3
============================================
  Files           342      342
  Lines         25909    25909
  Branches       3233     3233
============================================
- Hits          17015    16993      -22
- Misses         7997     8012      +15
- Partials        897      904       +7

Impacted Files
Coverage Δ
Complexity Δ

...mbry.router/SingleKeyManagementServiceFactory.java
100% <100%> (ø)
2 <1> (ø)
:arrow_down:

...m.github.ambry.router/GCMCryptoServiceFactory.java
100% <100%> (ø)
2 <1> (ø)
:arrow_down:

...c/main/java/com.github.ambry.network/Selector.java
78.48% <0%> (-3.59%)
44% <0%> (-1%)

...b.ambry.network/BlockingChannelConnectionPool.java
64.03% <0%> (-2.2%)
8% <0%> (ø)

.../java/com.github.ambry.router/DeleteOperation.java
91.72% <0%> (-1.51%)
43% <0%> (-1%)

.../com.github.ambry.router/GetBlobInfoOperation.java
79.86% <0%> (-1.39%)
30% <0%> (-1%)

...java/com.github.ambry.store/CompactionManager.java
91.04% <0%> (-0.75%)
17% <0%> (ø)

...in/java/com.github.ambry.store/BlobStoreStats.java
84.44% <0%> (-0.72%)
92% <0%> (ø)

...in/java/com.github.ambry.network/SocketServer.java
82.78% <0%> (-0.41%)
13% <0%> (ø)

...java/com.github.ambry.router/GetBlobOperation.java
88.32% <0%> (-0.27%)
30% <0%> (-1%)

... and 2 more

Continue to review full report at Codecov.

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


Add credits to UW SnowEx Hackweek account

Context
In https://2i2c.freshdesk.com/a/tickets/146, Scott forwarded some AWS credits for the UW SnowEx Hackweeks Hub. We should add these to the appropriate account.
Proposal
No response
Updates and actions
No response

@yuvipanda I know you're off today and generally travelling, but I hope it's ok that I assigned this to you!

@sgibson91 yep, I'll pick this up tomorrow!

Done!


Added focus state to .btn-link

Closes #29891
Preview: https://deploy-preview-30036--twbs-bootstrap.netlify.com/docs/4.3/components/buttons/#examples

Moving this to v5. @patrickhlauke please have a look :) Also, @ysds @MartijnCuppens

isn't the point of .btn-link that it's a button, but will look like a link? which is does by showing the underline?


#2489 Sticky header broken at Series Fix

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #2489
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address:
Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

perfect! )
pay 100 usd

😍 Perfect, I’ve sent the payout
💵 $100 @ 120.95 USD/KSM ~ 0.827 $KSM
🧗 EzGc4s9PgCPx1YnF3fqzhLzVHpHMTL4LWPScwpDrR8JKgSU
🔗 0x15b0d0e0f2d8197d485999d366e80d593d83d7389e73ece75917343e8075f16d
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Field not working when wrapping another component

I am just trying out react-redux-form, so I might be doing it wrong here. When I use it the way recommended, it seems to work. However, if I wrap the Field component around my own component (which implements input fields), it doesn't seem to be working. It looks like this:
import { Field } from 'react-redux-form';
import Input from '../components/Input';

function Form (props) {
    return (
        <form>
            <Field model="user.name">
                <Input label="Name" type="text"/>
            </Field>
        </form>
    );
}

Input just wraps the native input or select field with some label and container elements, so my fields can be more consistent.
Am I doing this wrong?

You need to add custom field with name Input so it will be able to recognize it. It will behave the same way.

@Faulik is right. See the React Native & Custom Components doc for more information.
In version 1, this will become much easier, I promise :) It will look something like this:
// Warning: future syntax!
import { Control } from 'react-redux-form';

// render()
<Control model="user.name" component={Input} label="Name" type="text" />

Thanks @Faulik and @davidkpiano . I am not sure what you mean by adding the custom field with key?
The doc seems to suggest that I need to implement a custom change event handler on my Input element, and have it dispatch an actions.change event. Is that right?

Yes, that is correct. Alternatively you can use createFieldClass to create a custom <Field> class that recognizes your custom <Input>. But you have to make sure that Input.displayName = 'Input'.
Let me know if the custom component solution outlined in the docs works for you!

So I really liked the approach of using createFieldClass with the default controls, instead of declaring each props individually. However, my custom Input field is used generically for all text, textarea, checkbox etc. fields. So does that mean I'd have to create a new field of each of those input types?

So does that mean I'd have to create a new field of each of those input types?

Not necessarily.
Assuming your custom Input has a type="..." attribute, you can do something like this:
const CustomField = createFieldClass({
  Input: (props) => {
    switch (props.type) {
      case 'text': // return ...
      case 'radio': // return ...
      default: // return ...
    }
  }
});

where each different type would return their own prop mappings. Again, <Control> will make this a little bit easier. But this approach will work.

That is nifty, and yes, Input has a type attribute. Could I even do something like
const CustomField = createFieldClass({
  Input: (props) => {
    return controls[props.type]();
  }
});

Yep, absolutely! The mapping function simply returns the mapping given props. So you can do anything in that function.

Just to update this ticket after talking with David on Discord:
When trying to createFieldClass route, I'm getting an error because the custom component Input that I'm using include a non-input element (label). The error is Uncaught TypeError: Cannot read property 'length' of undefined on this line https://github.com/davidkpiano/react-redux-form/blob/b192a92/src/components/field-component.js#L133

^ I'll have a patch for that soon. Thanks!

@davidkpiano I just updated my app to the latest version to try this again. This time, I get this error instead. Have you seen it before?
invariant.js:39 Uncaught Invariant Violation: onlyChild must be passed a children with exactly one child.
invariant	@	invariant.js:39
onlyChild	@	onlyChild.js:29
render	@	field-component.js:208

@tnguyen14 Can you show me your full code?

@davidkpiano sure I just pushed a temporary branch here https://github.com/tnguyen14/ledge/tree/react-redux-form

Hey @tnguyen14 this was just a usage issue - createFieldClass creates a new custom Field that can recognize your custom components. Here's the working NewTransaction.js class:
import React, { PropTypes } from 'react';
import { Button } from 'react-bootstrap';
import Input from '../components/Input';
import InputTypeahead from '../components/InputTypeahead';
import config from 'config';
import { connect } from 'react-redux';
import { Field, Form, createFieldClass, controls } from 'react-redux-form';
import { saveTransaction } from '../actions';

function isNotNull (str) {
	return typeof str === 'string' && str.length !== 0;
}

// make react-redux-form work with custom component
// https://github.com/davidkpiano/react-redux-form/issues/167
// this could change in react-redux-form 1.0
const CustomField = createFieldClass({
	Input: (props) => {
		let type = props.type;
		switch (props.type) {
		case 'date':
		case 'time':
		case 'number':
			type = 'text';
		}
		return controls[type](props);
	},
	InputTypeahead: controls.text
});

function NewTransaction (props) {
	const statuses = [{
		slug: 'POSTED',
		value: 'POSTED'
	}];

	const { transaction } = props;
	const submitText = props.editing ? 'Update' : 'Add';
	const submittingText = props.editing ? 'Updating...' : 'Adding...';

	return (
		<Form className="new-transaction" model="transaction" onSubmit={saveTransaction}>

Add a new transaction

			<CustomField model="transaction.amount"
				validators={{
					required: isNotNull
				}}>
				<Input label="Amount" type="number" min="0" step="any" />
			</CustomField>
			<CustomField model="transaction.merchant"
				validators={{
					required: isNotNull
				}}>
				<InputTypeahead source={props.merchants} label="Merchant" />
			</CustomField>
			<CustomField model="transaction.date"
				validators={{
					required: isNotNull
				}}>
				<Input label="Date" type="date" />
			</CustomField>
			<CustomField model="transaction.time"
				validators={{
					required: isNotNull
				}}>
				<Input label="Time" type="time" />
			</CustomField>
			<CustomField model="transaction.category"
				validators={{
					required: isNotNull
				}}>
				<Input label="Category" type="select" options={config.categories} placeholder="Select a category" />
			</CustomField>
			<CustomField model="transaction.source"
				validators={{
					required: isNotNull
				}}>
				<Input label="Source" type="select" options={config.sources} placeholder="Select a source" />
			</CustomField>
			<CustomField model="transaction.description">
				<Input label="Description" type="textarea" />
			</CustomField>
			<CustomField model="transaction.status"
				validators={{
					required: isNotNull
				}}>
				<Input label="Status" type="select" options={statuses} />
			</CustomField>
			<CustomField model="transaction.id">
				<input type="hidden" />
			</CustomField>
			<Button bsStyle="primary" className="pull-right" type="submit" disabled={transaction.submitting}>{transaction.submitting ? submittingText : submitText}</Button>
		</Form>
	);
}

NewTransaction.propTypes = {
	editing: PropTypes.bool.isRequired
};

function mapStateToProps (state) {
	let merchants = [];
	if (state.account.merchants_count) {
		merchants = Object.keys(state.account.merchants_count).reduce(function (merchants, merchant) {
			return merchants.concat(state.account.merchants_count[merchant].values);
		}, []);
	}
	return {
		transaction: state.transaction,
		editing: !!state.transaction.id,
		merchants: merchants
	};
}

export default connect(mapStateToProps)(NewTransaction);

Yup, that fixed it! Makes sense. Thanks @davidkpiano for all the incredible and timely help!

 Sorry if the documentation is confusing around this. <Control> in v1.0 will make this easier.


fix: 避免忽略本地allow any云上deny any安全组规则同步

这个 PR 实现什么功能/修复什么问题:
避免忽略本地allow any云上deny any安全组规则同步
是否需要 backport 到之前的 release 分支:

release/2.13

/area region
/cc @zexi

Codecov Report

Merging #6511 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6511   +/-   ##
=======================================
  Coverage    7.17%    7.17%
=======================================
  Files         647      647
  Lines      108977   108977
=======================================
  Hits         7819     7819
  Misses     100558   100558
  Partials      600      600

Flag
Coverage Δ

#aFlag
7.17% <ø> (ø)

Continue to review full report at Codecov.

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


[BUG] On Clicking enter while filling the form, entire website is getting re-loaded.

Describe the bug
On Clicking enter while filling the form the page is getting re-loaded.
Product Flavor

[ ] Managed (https://rxresu.me)

To Reproduce

Open any form to enter data. Let's say interests form.
Type the name of interest
Press enter
Entire page will be reloaded.

Expected behavior
After pressing enter post filling the form, the data should be submitted, instead the page is getting reloaded.

Hi there, I just fixed the Interest Form locally, I will submit pull request soon. Thanks for the info


Check for missing optional modules at runtime

Just made the bugC1523 test work in the language module project, by removing the optional module in JS (previously I would only remove it in JVM), and it fails for JS, because you don't check the return of `module optional` at run-time like we do in JVM. You should check it and throw an assertion error if it's missing.

Oh I just fixed this :)


[terra-navigation-side-menu] selection color change

Summary

What was changed:
Changed styles for selected item background color styles.
Why it was changed:
Testing

This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[x] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[x] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-XXXX

Thank you for contributing to Terra.
@cerner/terra

Summary
What was changed:
Changed styles for selected item background color styles.
Why it was changed:
Testing
This change was tested using:

[ ]  WDIO
[ ]  Jest
[ ]  Visual testing (please attach a screenshot or recording)
[ ]  Other (please describe below)
[x]  No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[x]  UX review
[ ]  Accessibility review
[ ]  Functional review

Additional Details
This PR resolves:
UXPLATFORM-XXXX
Thank you for contributing to Terra. @cerner/terra

No Jira Key for this Changes ?

Summary
What was changed:
Changed styles for selected item background color styles.
Why it was changed:
Testing
This change was tested using:

[ ]   WDIO
[ ]   Jest
[ ]   Visual testing (please attach a screenshot or recording)
[ ]   Other (please describe below)
[x]   No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[x]   UX review
[ ]   Accessibility review
[ ]   Functional review

Additional Details
This PR resolves:
UXPLATFORM-XXXX
Thank you for contributing to Terra. @cerner/terra

No Jira Key for this Changes ?

Summary
What was changed:
Changed styles for selected item background color styles.
Why it was changed:
Testing
This change was tested using:

[ ]   WDIO
[ ]   Jest
[ ]   Visual testing (please attach a screenshot or recording)
[ ]   Other (please describe below)
[x]   No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[x]   UX review
[ ]   Accessibility review
[ ]   Functional review

Additional Details
This PR resolves:
UXPLATFORM-XXXX
Thank you for contributing to Terra. @cerner/terra

No Jira Key for this Changes ?

-- No JIRA for this @supreethmr . This was raised in the demo call.

Can you add more details on PR description about the changes. Previous screenshots seems to have selectedItem in bold and blue left border. https://github.com/cerner/terra-framework/pull/2155/files#diff-83d99d284c785bf351e17f3df0297049e247a1686c0b785141df5b63c41b6912
I think the existing styles of selected item (except background color)  looks more appropriate then the new selectedItem styles being added on this PR.
Curious to know, Has UX team reviewed the new style changes for selectedItem

Discussion is to change the background color for the selected item in the menu. I made the change to keep the existing styles and just updated the background color.
UX team has not reviewed the new style changes for selectedItem.
Thanks

Discussion is to change the background color for the selected item in the menu. I made the change to keep the existing styles and just updated the background color. UX team has not reviewed the new style changes for selectedItem.
Thanks

Can you check again it looks like the selected styles are still missing in this screenshot https://github.com/cerner/terra-framework/pull/2155/files#diff-83d99d284c785bf351e17f3df0297049e247a1686c0b785141df5b63c41b6912

Can you check again it looks like the selected styles are still missing in this screenshot https://github.com/cerner/terra-framework/pull/2155/files#diff-83d99d284c785bf351e17f3df0297049e247a1686c0b785141df5b63c41b6912

@supreethmr The change here is when the menu item has submenu(chevron icon) even if it selected we will not apply the selected css styles.

+1


design and doc MASP integration

Start with a exploration/design doc for MASP integration

Does this depend on having more crypto in the VP prelude, or should it be all native?

If we can compile the MASP to WASM then it might be best to do that as it should not be a bottleneck, but we will need to add more crypto the prelude. We'll discuss this more in-detail in a session with crypto team

we should have full crypto in the VP prelude anyway


[auto] convert to swift 3

Convert to Swift 3 via Xcode, builds without errors.
There aren't any tests, so I can't be 100% sure this actually works, but maybe you've got some use in this PR

Can confirm it does not work. It loads all images into the first frame


fix for PR #25903 - spec file support for Windows plugin discovery

- What I did
Fixed typo in pkg/plugins/discovery_windows.go (from #25903)
And added build tag for pkg/plugins/discovery_unix.go (unix is not a GOOS so file suffix is not enough)
- How I did it
It's just a small fix. Without it docker on windows is still using "/etc/docker/plugins", "/usr/lib/docker/plugins"
- How to verify it
Run a plugin. I used https://github.com/Azure/azurefile-dockervolumedriver (with small changes to run it on windows). Check if address from .spec file is used by docker.
- A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: Michal Wieczorek<EMAIL_ADDRESS>

LGTM

LGTM, thanks!


pip install --user xyolo 安装失败

Collecting xyolo
Using cached xyolo-0.1.6-py3-none-any.whl (118 kB)
Collecting tensorflow>=2.2 (from xyolo)
Obtaining dependency information for tensorflow>=2.2 from https://files.pythonhosted.org/packages/93/21/9b035a4f823d6aee2917c75415be9a95861ff3d73a0a65e48edbf210cec1/tensorflow-2.15.0-cp311-cp311-win_amd64.whl.metadata
Using cached tensorflow-2.15.0-cp311-cp311-win_amd64.whl.metadata (3.6 kB)
Collecting numpy<1.19.0,>=1.18.1 (from xyolo)
Using cached numpy-1.18.5.zip (5.4 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [92 lines of output]
Running from numpy source directory.
:461: UserWarning: Unrecognized setuptools command, proceeding with generating Cython sources and expanding templates
C:\Users\AppData\Local\Temp\pip-install-yj7yjewh\numpy_5b63143e6a264d4ebafcf8f996655cdd\tools\cythonize.py:75: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
required_version = LooseVersion('0.29.14')
C:\Users\AppData\Local\Temp\pip-install-yj7yjewh\numpy_5b63143e6a264d4ebafcf8f996655cdd\tools\cythonize.py:77: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
if LooseVersion(cython_version) < required_version:

碰到了相同的问题，xyolo无法安装成功

我也是


README.adoc: update AppVeyor CI badge

The URL for AppVeyor CI badge is not scoped to master branch builds.
This means that all AppVeyor CI builds (including Pull Requests) can
affect the current AppVeyor build status reflected on the README.adoc.
Let's fix the erroneous URL for the AppVeyor CI badge to scope it to
master branch builds only.

Coverage remained the same at 93.754% when pulling 32074beec24c012a723d82cead282572ff38714c on Creastery:update-readme-ci-badges into 8b912cc12f333c4c266b30d3342244384a811182 on cs2113-ay1819s2-t09-1:master.


kubeadm init failed.

下载脚本
wget https://ghproxy.com/https://raw.githubusercontent.com/lework/kainstall/master/kainstall-ubuntu.sh
报下面的错误，帮忙看看是什么原因?
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/kainstall/kube-apiserver:v1.25.0: output: E0831 09:51:30.930600   27372 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = NotFound desc = failed to pull and unpack image \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-apiserver:v1.25.0\": registry.cn-hangzhou.aliyuncs.com/kainstall/kube-apiserver:v1.25.0: not found" image="registry.cn-hangzhou.aliyuncs.com/kainstall/kube-apiserver:v1.25.0"
time="2022-08-31T09:51:30+08:00" level=fatal msg="pulling image: rpc error: code = NotFound desc = failed to pull and unpack image \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-apiserver:v1.25.0\": registry.cn-hangzhou.aliyuncs.com/kainstall/kube-apiserver:v1.25.0: not found"
, error: exit status 1
        [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/kainstall/kube-controller-manager:v1.25.0: output: E0831 09:51:32.328803   27397 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = NotFound desc = failed to pull and unpack image \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-controller-manager:v1.25.0\": failed to resolve reference \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-controller-manager:v1.25.0\": registry.cn-hangzhou.aliyuncs.com/kainstall/kube-controller-manager:v1.25.0: not found" image="registry.cn-hangzhou.aliyuncs.com/kainstall/kube-controller-manager:v1.25.0"
time="2022-08-31T09:51:32+08:00" level=fatal msg="pulling image: rpc error: code = NotFound desc = failed to pull and unpack image \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-controller-manager:v1.25.0\": failed to resolve reference \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-controller-manager:v1.25.0\": registry.cn-hangzhou.aliyuncs.com/kainstall/kube-controller-manager:v1.25.0: not found"
, error: exit status 1
        [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/kainstall/kube-scheduler:v1.25.0: output: E0831 09:51:33.818145   27422 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = NotFound desc = failed to pull and unpack image \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-scheduler:v1.25.0\": failed to resolve reference \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-scheduler:v1.25.0\": registry.cn-hangzhou.aliyuncs.com/kainstall/kube-scheduler:v1.25.0: not found" image="registry.cn-hangzhou.aliyuncs.com/kainstall/kube-scheduler:v1.25.0"
time="2022-08-31T09:51:33+08:00" level=fatal msg="pulling image: rpc error: code = NotFound desc = failed to pull and unpack image \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-scheduler:v1.25.0\": failed to resolve reference \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-scheduler:v1.25.0\": registry.cn-hangzhou.aliyuncs.com/kainstall/kube-scheduler:v1.25.0: not found"
, error: exit status 1
        [ERROR ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/kainstall/kube-proxy:v1.25.0: output: E0831 09:51:35.166799   27447 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = NotFound desc = failed to pull and unpack image \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-proxy:v1.25.0\": failed to resolve reference \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-proxy:v1.25.0\": registry.cn-hangzhou.aliyuncs.com/kainstall/kube-proxy:v1.25.0: not found" image="registry.cn-hangzhou.aliyuncs.com/kainstall/kube-proxy:v1.25.0"
time="2022-08-31T09:51:35+08:00" level=fatal msg="pulling image: rpc error: code = NotFound desc = failed to pull and unpack image \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-proxy:v1.25.0\": failed to resolve reference \"registry.cn-hangzhou.aliyuncs.com/kainstall/kube-proxy:v1.25.0\": registry.cn-hangzhou.aliyuncs.com/kainstall/kube-proxy:v1.25.0: not found"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

相同错误

离线版本也出现了这个错误

新版本的镜像地址改了，https://github.com/kubernetes/kubernetes/pull/109938

现在可以下载了。我同步到阿里云了


PhoneGap Build / Android apk size increase (phonegap-plugin-push vs. phonegap-build/PushPlugin)

Hi,
I just migrated from deprecated plugin phonegap-build/PushPlugin to this plugin.
My apk got bigger : It has increased by ~1Mo (1171ko vs. 2104ko)
I looked at the plugin source and I don't understand where this increase comes from.
I presume it may be linked with google-play-services-gcm but on my local android sdk file : the size of play-services-gcm-*.aar is 60ko maximum...
Do you have you any idea ?
Thanks
--
David

@davidbarre It's probably a combination of the Android Support Library and GCM Play Services.

@macdonst I believe this is a recent development. In our case, the APK ballooned from 6MB to 23MB due to this plugin!
Any chance we can reduce this? The situation is worse when we have to add crosswalk on top of this!


I got in dev a failing test from master, how to properly setup?

Running tests from master branch, latest commit #a30327a I got a failing test:
Failures:

  1) DashTestDefaultProc to_json behaves correctly with default proc
     Failure/Error: to_hash.to_json(*args)

     NoMethodError:
       undefined method `to_json' for {:fields=>[]}:Hash
       Did you mean?  to_s
     # ./lib/hashie/hash.rb:43:in `to_json'
     # ./spec/hashie/dash_spec.rb:61:in `block (2 levels) in <top (required)>'

Finished in 0.18124 seconds (files took 0.31668 seconds to load)
673 examples, 1 failure

Failed examples:

rspec ./spec/hashie/dash_spec.rb:59 # DashTestDefaultProc to_json behaves correctly with default proc

same for ruby 2.5, 2.6 and 2.7.

But at Travis it is OK -- build passing . How I do configure my env to properly works? I should be using a specific ruby version?

This doesn't seem right. Looks like the json gem is not properly required, this would happen if we were missing require 'json'. We don't actually do that anywhere explicitly.
I assume you ran bundle install first and it got everything, including json, which is a dependency.
~/source/hashie/dblock (master)$ bundle | grep json
Using json 2.2.0

Next, what's bundle show json
~/source/hashie/dblock (master)$ bundle info json
  * json (2.2.0)
	Summary: JSON Implementation for Ruby
	Homepage: http://flori.github.com/json
	Path: /Users/dblock/.rvm/gems/ruby-2.7.1/gems/json-2.2.0

Finally, any difference running bundle exec rspec spec vs. rspec spec?

Yes, I did run bundle through ./bin/setup, using fresh and clean gemsets.
ruby 2.5.7
JSON installed, but version 2.3.1
➜  hashie git:(master) bundle info json
  * json (2.3.1)
	Summary: JSON Implementation for Ruby
	Homepage: http://flori.github.com/json
	Path<EMAIL_ADDRESS>
there is no diff between bundle exec rspec spec and rspec spec
ruby 2.6.5
  * json (2.3.1)
	Summary: JSON Implementation for Ruby
	Homepage: http://flori.github.com/json
	Path<EMAIL_ADDRESS>
there is no diff between bundle exec rspec spec and rspec spec
ruby 2.7.1
  * json (2.3.1)
	Summary: JSON Implementation for Ruby
	Homepage: http://flori.github.com/json
	Path<EMAIL_ADDRESS>
there is no diff between bundle exec rspec spec and rspec spec
Now forcing json to 2.2.0
ruby 2.5.7
➜  hashie git:(master) ✗ bundle info json
  * json (2.2.0)

same result as above
ruby 2.6.5
➜  hashie git:(master) ✗ bundle info json
  * json (2.2.0)

same result as above
ruby 2.7.1
➜  hashie git:(master) ✗ bundle info json
  * json (2.2.0)

same result as above

Add require 'json' into spec_helper.rb. Works?

it works.
I'm still curious to know why CI works and my env doesn't -- going to investigate later.

I bet this is actually a bug and all of the rest of us have a globally available json gem or something and it doesn't work with a clean gemset. Also what's your OS @gnomex?


The same CubeId with different hashCodes

What went wrong?
The same cube created using two different methods can have different bitMask's. This leads to different hashCodes, making CubeId an unreliable candidate as Map keys.
How to reproduce?
val level65 =
      CubeId(2, "wQwwwQwwQwwQwwwwwQwQwwwQQwwwwQQwQwwwQwwQwwQwwwwwQwwQQQQQQQQQQQQQQ")

// cubes from level 64
val cubeThroughParentMethod = level65.parent.get
val cubeThroughConstructor =
      CubeId(2, "wQwwwQwwQwwQwwwwwQwQwwwQQwwwwQQwQwwwQwwQwwQwwwwwQwwQQQQQQQQQQQQQ")

println(cubeThroughParentMethod.bitMask) // Array(-1441504016541484037, -6148914603906580738, 0, 0)
println(cubeThroughConstructor.bitMask) // Array(-1441504016541484037, -6148914603906580738)

2. Branch and commit id:
main, 880203a
5. How are you running Spark?
Local

Good catch, please do not forget to fix equals as well. Thank you.


Refinement is not a type?

Hey @gcanti ,
I have code like this:

const password = t.struct({
  password: t.maybe(t.Str) // it is refinement for t.maybe(t.Str) in real world but it isn't important here
});

const passwordRequired = t.refinement(password, (v) => !!v.password, 'PasswordRequired');

const signInForm = t.struct({
  email: t.Str // it it refinement too in app
}).extend([passwordRequired], 'signInForm');

it gives me an error [tcomb] Invalid argument mixins supplied to extend(mixins, name), expected an array of objects or types. If I change code to
const signInForm = t.struct({
  email: t.Str // it it refinement too in app
}).extend([password], 'signInForm');

where [password] isn't a refinement anymore but pure struct, it works fine.
Is it supposed to work like this? Can I extend refinements?
Thanks

Hi @Firfi
Extending refinements is not supported at the moment, the error message is misleading, should be expected an array of objects or structs, I'll fix that.

Supporting refinements makes sense for me. Maybe I am doing it wrong?
I.e. I have two forms in two different parts of application that 'mixin' some behavior like addressBehavior. addressBehavior is a struct with zip (zip code), address, country and state. country is a enum of every country codes. If country code is not US, I want to leave zip and state as t.maybe(t.Str), however, if country is US, I want to do additional check for zip and state presence.
As I see currently, this check should be implemented as a refinement over struct, but I cannot extend it or extend with it to mixin in my two forms then.
Maybe I understand refinement objective wrong? Also, maybe there is some workarounds?

Supporting refinements makes sense for me

I agree, it's just not supported at the moment. We need to draft a spec though, I'll open an issue for this.

Also, maybe there is some workarounds?

Maybe. If acceptable, the simplest one would be to assign the addressBehavior refinement to a address field instead of mix it in the main type.

@Firfi FYI tcomb v3.1.0 now supports extending refinements


Update Website Images

ref #621

1.12.0 submitted to App Store! Will update the website w/:

New gradient background
1.12.0 feature screenshots

done!

1.14 right? And nice ad campaign? 😜
Sent with GitHawk


Add more robust fpu test

This improves the FPU testing.

By popular demand, it makes it faster.
It now more correctly generates 387 code (this is the point of the out and wrapper functions)
It checks that the FPU and MMX registers are persisted across syscalls and forks.

unfortunately, the test currently fails due to an unknown bug (either in the test or the kernel). Strangely, commenting out the "int" lines (so as to not perform the fork) does NOT fail.


[FEATURE REQ] Add support for Browser (Web Push)

Is your feature request related to a problem? Please describe.
Browser (Web Push) is now supported in Azure notification hubs. This should be supported in the client as well.
Describe the solution you'd like
Add SendBrowserNotificationAsync etc to the client.
Describe alternatives you've considered
N/A
Additional context
N/A
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Description Added
[x] Expected solution specified

Thank you Eddy - I now understand why I am having bother.

I'm also interested in this functionality.

I'm also interested in this functionality.   Am I correct in thinking that we will have to wait on  a newer  SDK release of Microsoft.Azure.Notificationhubs because   there is currently no  CreateOrUpdateInstallationAsync   method that will allow us for Web Push that will allow us to send the below?
                                                                                var browserPushSubscription = new BrowserPushSubscription
        {
            Endpoint = "",
            P256DH = "",
            Auth = "",
        };

MS REF URL :  https://learn.microsoft.com/en-us/azure/notification-hubs/browser-push#create-browser-installations-sdk

Any ETA on this? Currently waiting for this feature to be available in the SDK :)

When would this task be finished and released in nuget? We really need this functionality badly


Application crashes after opening

ARC after the update this morning crashes after opening every time.  Using it doesn't seem to affect this, (no using ARC until it crashes or preforming 'GET' requests)
steps to recreate:

open ARC in windows 7 SP1 (using it outside of the browser)
wait < 5 minutes
popup pops up saying that ARC has crashed and needs to be restarted.

I can guess that it may be related to #830 where the arc is trying to process a lot of data. But in this case it is trying to process history data (not the same as on the history list). I'm fixing it right now.

So, I fixed it by limiting number of history records that the app can process during a request recall. It should not cause crashes.


Remove Blocks additions that are in BlocksKit

https://github.com/zwaldowski/BlocksKit is way more awesome than our half baked copy of it. (For which IIRC I was responsible. Mea culpa.)
I suggest we either vendor BlocksKit or just strongly suggest that people use it.

I assume it's safe to delete the block additions as nobody responds, right? @MSch shall we remove all of them or did you add some that are not present in BlocksKit?


Subprocess-error related to numpy while installing via pip

The following error comes up while trying to install "simcse" via pip:
"
error: legacy-install-failure
Encountered error while trying to install package.
numpy
note: This is an issue with the package mentioned above, not pip.
"

Hi,
It seems that you have some problem installing numpy? Maybe try pip install numpy. If this does not solve the problem, you can also just clone the project and install it by python setup.py install.

Hi,
I encountered the same error while trying to install the package in a Python 3.10 environment with both methods (pip install and python setup.py). The issue at this line which specifies numpy<1.20 which is very old.
So the solution for me was to remove this constraint (replace the above line with numpy>=1.19.5) and then install using python setup.py install. And that worked for me.
Hope this helps.


Add Snowflake database data provider with example DAGs

Description
What is the current behavior?

Add DataProvider for Snowflake
Add non-native transfer implementation for s3 to Snowflake
Add non-native transfer implementation for gs to Snowflake
Add example DAG

closes: #1547
What is the new behavior?

Add DataProvider for Snowflake
Add non-native transfer implementation for s3 to Snowflake
Add non-native transfer implementation for gs to Snowflake
Add example DAG

Note: Please merge this PR before merging this.
Does this introduce a breaking change?
No
Checklist

[x] Created tests which fail without the change (if possible)
[x] Extended the README / documentation, if necessary

screenshot of DAGs working
Following is the recording of example DAG running: https://astronomer.slack.com/archives/C03868KGF2Q/p1676662728169199


API to manage Models

Is your feature request related to a problem? Please describe.
There is currently no API to just add, delete or update models in a granular way.
Describe the solution you'd like
LUIS Allowed so much more granularity in it's API with being able to manipulate intents, utterances, patterns etc. CLU - Language offers none of this API.
https://learn.microsoft.com/en-us/rest/api/cognitiveservices-luis/authoringv2.0/model/add-intent?tabs=HTTP
Compared to
https://learn.microsoft.com/en-us/rest/api/language/2022-10-01-preview/conversational-analysis-authoring
Additional context
This would be great for anyone wanting to build more abstractions over CLU - Language.

@zhouwangzw @mahilleb-msft Do you know who could best comment on this?

Hello @alt95 ,
While LUIS authoring APIs were designed with a CRUD paradigm in mind, the CLU authoring APIs were designed to handle changes to the schema and training data through importing and exporting the project.
This made it easier for users to manipulate snapshots of their projects while they were being authored, whether through version control or manual versioning.
We have the CRUD APIs support in our backlogs, but it's not one of the features we're currently working on. So it may be a little ways down the road before they're made available.
Thank you.


Remark: Memory demand (min. 8 GB it seems)

Hi! This is less of an issue and rather a remark.
I've been doing some guesswork lately as OpenSlides 3.0 would build at all on a VM, crashing with a rather weird npm related error that I could not reproduce on my machine at home.
As it turns out, it seems that 4 GB of RAM simply is not enough for the build process (server/build.sh) when it goes through npm run build (I think) in the Dockerfile.
With 8 GB, however, it worked flawlessly.
Just wanted to leave this here for other lost souls ^^

I had this problem with 2 GB, but 4 GB worked for me.

That's due to the angular client. Building the client in production mode requires (at least) 4GB of Memory
https://github.com/OpenSlides/OpenSlides/blob/master/client/package.json#L13

I see. I suspected that.
Wouldn't it make sense to throw a warning when less is available?
Or note it somewhere in the docs?

We'll I ran into this issue twice, though in edge cases:

Building on a RaspberryPi (nice and mobile for events with only a few clients)
Building on a rented cloud node where I initially selected only 4GB RAM because that's usually enough.

I would've appreciated a note. Mostly because the error thrown was rather cryptic and not pointing directly to a lack of RAM.
12 Mar 2020 19:11:16 Sean<EMAIL_ADDRESS>

Wouldn't it make sense to throw a warning when less is available?

no, since trying to build the client (in production mode) without the ng-high-memory command (and thus at least 4GB of memory) will fail. We might want to throw an error directly and stop building.

Or note it somewhere in the docs?

I don't consider 4GB of memory to be an exceptional amount that should be worth mentioning in build instructions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [https://github.com/OpenSlides/openslides-docker-compose/issues/1#issuecomment-598342799] , or unsubscribe [https://github.com/notifications/unsubscribe-auth/ADT5B5RWDKXH4GFL25AUQBLRHEQT5ANCNFSM4I5AUT2A] . [https://github.com/notifications/beacon/ADT5B5SEWVO7AHDEKIBNDKTRHEQT5A5CNFSM4I5AUT2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOU7ZDY.gif]

Thank you for your comments.  I have added the requirement to the README file (c.f. fe895e06924a53bb532dfd6d91f2faf7b9b72958).

@gsiv the client now requires less RAM to for a prod-build since the angular9 update.

Thanks for the info! :-)


Fix error in laravel 6.X

Currently octobercms 1.1.x supports since laravel 6.x LTS. However, since barryvdh/laravel-ide-helper 2.8.x only supports laravel 8.x upwards, causing an error to appear when executing php artisan ide-helper:generate under laravel 6.x.
The update setting ~2.7.0 will ensure that laravel-ide-helper runs from laravel 6.x up to 8.x without any problems.

I'm assuming this will break October in the same way your other PR broke Winter?


Update damping values for jolt rigid bodies on mode switch at runtime

Hi there 👋
Here's a fix for an issue where linear_damp and angular_damp are not updated when either linear_damp_mode or angular_damp_mode is changed at runtime.
Previously, linear_damp and angular_damp were computed once using their initial damping mode and not updated whenever a mode was changed.
It's likely that we want to split that update operation for each damping type.

I've made a short demo, cube A and B are the same but they change their linear damping mode when they collide with a floor surface, the red one changes the mode to REPLACE while the blue one changes the mode to COMBINE.
The initial mode is COMBINE for both and they have the same initial velocity in opposite directions.
The default linear damping value is .5.
https://github.com/user-attachments/assets/c937b559-04fa-489d-a275-21bf57dde1bc
Here's the same demo without the fix (which means damping is not updated when cube A damping mode is changed when it first collides with the red surface)
https://github.com/user-attachments/assets/18184434-2767-4543-a7b1-f3a237188a7e

Also, since it'll probably get brought up eventually, note that Godot's contribution workflow (seen here) specifies that pull requests should ideally be a single commit, so you'll need to squash (and force push) your commits yourself before the PR can be merged.

But there's no need to squash yet only when it's actually approved and ready to merge

Thanks! Congratulations on your first merged contribution! 🎉


more examples on how to use this crate?

like how to use those public apis.
how to optimize the parameters.

Where to add the examples?

Where to add the examples?

add an example/ folder and run it in ci, link it in the readme.

#[test] may be used in test private functions, but examples are for normal users to read.

Add an example:

#244

TODO:

[ ] optimization
[ ] migration


Nested table syntax for data table?

My original question:  Are we keeping the nested table syntax for the data table?  No existing tools will write files out this way (except perhaps for our Excel Template tool) because while it does parse, it isn't really standard YAML syntax. This is the whole – I want to open my YODA file in Excel discussion.  Looks like using PyYAML they parse to exactly the same thing.
Anthony's response:  Regarding the "I want to open my YODA file in Excel" discussion, I'm a firm believer that we should support this by recommending a convention for writing out each line the data table like this:
"2015-01-01 00:30:00",-7.0,-9.56,-9.31,-9.87,],[
rather than like this:
- ["2015-01-01 00:30:00",-7.0,-9.56,-9.31,-9.87]
As Jeff points out, PyYAML parses both identically, so why not recommend the former to also ease the use of Excel? The only reason I can think of is that we may have a hard time writing out the former from PyYAML, and for those use cases, I think we should allow for both (but recommend the former, and set up the Excel Templates to output the former).

The new Time Series template adopts the following syntax for each line of data:

[ "2015-01-01 00:30:00", -7.0, -9.56, -9.31, -9.87 ]

This is clean, it doesn't break across lines in the file, it doesn't require an open bracket at the end of the line, it parses in a standard way, and because it has both spaces and commas, it can easily be broken into columns in Excel using "text-to-columns" functionality with commas and spaces as delimiters.


Chris/add anno property maps

#234 - Add annotation maps. I added to p4info.proto and updated the P4Runtime spec with an example. I generated the example P4Info by using the proposed enhanced p4info.proto, reading in actual xxx.p4info.txt from current p4c, parsing the P4info using python, adding parsed annotations to the P4info "DOM" (with generated p4info_pb2.py libs from the new p4info.proto) then emitting it.
If acceptable, hopefully p4c can be enhanced to do the adding parsed annotations to the P4info "DOM" task

Hey peeps, any time to review this? Thanks!

Hi Chris. I’m on vacation which is why I haven’t reviewed this yet. I should be able to take a look at it in the upcoming days.

@antoninbas I appreciate all  the great feedback, it resulted in a much better PR. If this is acceptable, perhaps we can review at the next WG meeting.

One change is that with AnnotationMap, we lose the order of annotations. I can't say I have a super clear use-case for why preserving that odering is important, but I'm generally skeptical when we parse some language and just forget about the ordering of elements, even if the order should not matter.
Questions:

Can we think of reasons that would rely on ordering?  Would we ever want to "deparse" our representation and expect to get the same as the original program?
Is there an easy way to add ordering back in?  What do would we lose if we don't use a map, but instead a repeated list?

In addition, we also lose the order for KV lists, which again does not seem great, even if I can't actually think of a example where it matters necessarily.

@stefanheule Re: maintaining the ordering or being able to regenerate the original code so to speak - it's a good point, but one could say the same thing for most P4 constructs: once parsed, something is lost. If this is important, we could retain the original annotations and remove the deprecation.
Here's an alternative along the lines of your comment:
// One parsed element within an annotation's body
message AnnotationElement {
  message AnnotationProperty {
    string key = 1;
    string value = 2;
  }
  oneof element {
    string expression = 1;
    AnnotationProperty property = 2;
  }
}

// An ordered list of annotations identified by the tag
message ParsedAnnotation {
  string annotation_tag = 1;
  repeated AnnotationElement elements = 2;
}

Then, instead of the original proposal, replace all occurrences of
  AnnotationMap annotation_map = ...;

with
 repeated ParsedAnnotation parsed_annotations = ...;

Note AnnotationProperty is a like a one-element map; since there's  only ever one pair it is not worth using a map field type.
The benefits to this alternative are, ordering of everything is preserved exactly, and you could presumably regenerate the original source code, subject to some normalization. The drawback is  more work in any application consuming these. For example, one want to put all the properties into a map and all  the expressions into their own list, mimicking the original proposal. With this approach, it remains a choice whether to coalesce annotations with duplicate tags. If we do, we lose reversibility.  If we don't, we have to accumulate kv-pairs (and expressions) in the application.
This also points out my original proposal should have specified that expressions get coalesced just like kv-pairs.  I'll comment my own PR as a reminder.

I'm fine with the second proposal as well. It is still better than what we have currently, since the application does not have to actually parse the raw annotations anymore. With the new proposal we can support duplicates and preserve the order, but deny the application the convenience of an associative container. It is probably good not to make assumptions about the semantics of user-defined annotations. By preserving order and duplicates, we enable the consumer to choose: accumulate duplicates or override, and that can be defined on a per-annotation basis. So I'm leaning towards the second one at this time. Let's make a final decision at the next meeting.
On a side note @chrispsommers I realized that this change has impacts on other parts of the spec (e.g. the description of the Preamble message, you can search the spec for "annotation"). These will need to be updated as part of this PR. I suggest you wait until we reach an agreement, or you may need to update the same paragraphs multiple times...

Thanks for working on this, Chris, I really appreciate it.  I agree that we probably won't be able to have parse-deparse be the identity (there's whitespace, too, for example), so that was a bad example and should not be a goal.
I have a few more thoughts:

Besides order that I think is important to preserve, there are two more points I'd like us to consider: repetition of keys and repetition of the same annotation.  Unlike what Antonin says, it looks like the consumer is not free to choose override vs duplication, as the P4 spec says what the semantics are:

Multiple annotations of either form may be used and are cumulative, i.e. the list of k-v pairs will accumulate. If a given key appears more than once, then the latest value will replace all earlier ones.

Since this is in the spec, we should probably also do that.

I would like to propose that we treat KV lists and expression lists more uniform, since the two can be mixed (at least through accumulation, though the P4 spec seems to forbid mixing in a single annotation).  We can treat expression lists as a KV list where they key is just empty.

The P4 spec says annotation names starting with a lowercase character are reserved, so at the very least we should not use that in our examples.

Here's my proposal (I also change annotation_tag to name, since that's what the P4 spec uses):
// One parsed element within an annotation's body.
message AnnotationElement {
  // key can be empty, in which case the annotation was just an expression
  string key = 1;
  string value = 2;
}

// An ordered list of annotations identified by the name
message ParsedAnnotation {
  string name = 1;
  repeated AnnotationElement elements = 2;
}

// to be used as:

repeated ParsedAnnotation parsed_annotations = ...;

The following invariants hold:

For any P4 entity with annotations, there are no two parsed_annotations that have the same name.
Within a ParsedAnnotation, there are no two AnnotationElements that have the same key, except for the empty key, which can appear any number of times.

Here's an example of how this would be used (showing accumulation and shadowing and mixing):
@MyAnno1()
@MyAnno2("Some random content: for i in range(10)")
@MyAnno3(1+1, "Hello", 1 << 3)
@MyAnno4(a=b,c=d)
@MyAnno4(e=f)
@MyAnno5(a=1,a=2)
@MyAnno6(e=f)
@MyAnno6(1)
table test1 {
    key = { hdrs.data.f1 : ternary; }
    actions = {
        setb1;
        noop;
    }
    default_action = noop;
}

tables {
  preamble {
    id: 33619894
    name: "ingress.test1"
    alias: "test1"
    annotations: "@MyAnno1()"
    annotations: "@MyAnno2("Some random content: for i in range(10)")"
    annotations: "@MyAnno3(1+1, "Hello", 1 << 3)"
    annotations: "@MyAnno4(a=b,c=d)"
    annotations: "@MyAnno4(e=f)"
    annotations: "@MyAnno5(a=1,a=2)"
    annotations: "@MyAnno6(a=b)"
    annotations: "@MyAnno6(1)"
    parsed_annotations {
      name: "MyAnno1"
    }
    parsed_annotations {
      name: "MyAnno2"
      elements {
        value: "\"Some random content: for i in range(10)\""
      }
    }
    parsed_annotations {
      name: "MyAnno3"
      elements {
        value: "1+1"
      }
      elements {
        value: "\"Hello\""
      }
      elements {
        value: "1 << 3"
      }
    }
    parsed_annotations {
      name: "MyAnno4"
      elements {
        key: "a"
        value: "b"
      }
      elements {
        key: "c"
        value: "d"
      }
      elements {
        key: "e"
        value: "f"
      }
    }
    parsed_annotations {
      name: "MyAnno5"
      elements {
        key: "a"
        value: "2"
      }
    }
    parsed_annotations {
      name: "MyAnno6"
      elements {
        key: "a"
        value: "b"
      }
      elements {
        value: "1"
      }
    }
  }
}

Thoughts?

@antoninbas and @stefanheule Great input, I like Stefan's revised proposal, thanks for the improvements and providing a well-worked-out example. It's a good compromise on all the issues so far raised - fewest assumptions,  mostly-reversible transformations, reasonably convenient. It would take just a few lines of e.g. Python code to build a consolidated dict, for example. I would like to see feedback from @konne-google if possible, since he was strongly in favor of the need for something like this, based on actual use-cases.
I'll wait for this to simmer awhile, then submit a new PR prior to the next WG meeting. @antoninbas thanks for the reminder to comb the spec for affected areas.

@stefanheule

Thinking about this some more, this is at least my interpretation of what the P4 spec says. However, we may want to ask if that's correct, and why there is this inconsistency between accumulating expression lists and KV lists, but not allowing mixing of them directly.

I added kv-pairs to the language spec in https://github.com/p4lang/p4-spec/commit/ede4c872875ad2b878c2b434a5551482fad0e40e. I didn't think of these other cases at the time. If we do approve this PR, I'll bring suggestions to the LDWG to enhance the grammar accordingly.

Another thing we might want to check is if the compiler currently accumulates/overwrites as is described in the P4 spec. If it does not, we should ask why. If it does, a P4RT implementation could reuse that when creating the proto.

p4c does the kv-pair accumulation correctly (I believe there are even test cases for it), but no expression accumulation.

Ah great, I didn't know you also did this in the P4 spec! :)  For p4c, maybe we should open a bug then to track that it doesn't implement the accumulation for expressions.  Does it shadow KVs correctly?  That is, does @A(a=1,a=2) become @A(a=2) like the spec says?

@stefanheule The spec currently only covers the accumulated kv-pairs and p4c already handles it. The PR was quite some time ago. If we approve this change to P4RT, I'll open issues for enhancing the language and compiler.

I'm not sure I understand what you are saying, I think the spec does explicitly also cover shadowing: "If a given key appears more than once, then the latest value will replace all earlier ones.".  We should make sure the compiler implements this, or if not, open a bug.  But in any case, sounds like we are all in agreement, thanks for the explanations and all your work!

Thanks guys for the very thorough work here, looks very good to me!
One minor nitpick, the comment:
// key can be empty, in which case the annotation was just an expression
was hard for me to understand, because annotations aren't expressions.
Maybe:
// Key is empty, if and only if no key was specified

@konne-google Actually annotations are expression lists or kv-lists. From https://p4.org/p4-spec/docs/P4-16-v1.1.0-spec.html#sec-annotations:
annotation
    : '@' name
    | '@' name '(' expressionList ')'
    | '@' name '(' keyValueList ')'
    ;

We'll probably want to enhance the grammar to allow arbitrary mixtures of expressions and kv-pairs.

You are right Chris that annotations can use expressions in their element list (whether it's a KV list or just expressions without a key), but annotations themselves are not expressions.  That's why Konstantin thinks my sentence is confusing, and I agree that his proposal is better.  Let's use that (minus the stray comma).
// Key is empty if and only if no key was specified

As a heads-up, there are some changes to P4 annotations coming down the pipe. With the next version of the spec, annotation bodies will be largely unstructured: https://github.com/p4lang/p4-spec/blob/c357d17bd8db3f3f3c3a71f6611062d2ae461ff4/p4-16/spec/P4-16-spec.mdk#L6954-L6979
annotation
    : '@' name
    | '@' name '(' annotationBody ')'
    ;
~ End P4Grammar

## Bodies of annotations

The flexibility of P4 annotations comes from the minimal structure mandated by
the P4 grammar: annotation bodies may contain any sequence of terminals, so
long as parentheses are balanced. In the following grammar fragment, the
`annotationToken` non-terminal represents any terminal produced by the lexer,
including keywords, identifiers, string and integer literals, and symbols, but
excluding parentheses.

~ Begin P4Grammar
annotationBody
    : /* empty */
    | annotationBody '(' annotationBody ')'
    | annotationBody annotationToken
~ End P4Grammar

Annotations may impose additional structure on their bodies, and are not
confined to the P4 language. For example, the P4Runtime specification defines a
`@pkginfo` annotation that takes key-value pairs, which are not found in the
main P4 language.

@liujed Thanks for flagging this. I do recall  you making proposals in the past towards this end. The intent of this PR is to make it easy to consume typical annotations like KV-pairs and expressions. I'm wondering how we can still accomplish this PR's intent without tripping on unstructured annotations. Do folks think there should be a new choice in the message below, e.g. unstructured for anything which doesn't match expression or property grammar?
    string expression = 1;
    AnnotationProperty property = 2;
  }

OK folks, I updated p4types.proto, p4info.proto and the spec, to align with the very latest suggestions, just prior to @liujed 's https://github.com/p4lang/p4runtime/pull/238#issuecomment-536092720. I realize this is evolving but I wanted to consolidate it so we have a  clear view of where we are. I reexamined the history of the P4 spec and p4c commits in this regard, you might refer to https://github.com/p4lang/p4-spec/pull/724 and https://github.com/p4lang/p4c/pull/1614. I think this PR will work with free-form annotations as developed by Jed. Note, in the latest commit I added @MyAnno7(...) borrowed from Jed's example in https://github.com/p4lang/p4c/pull/1614/files#diff-8e279f4569ce347a6bf5278b97c851bc (file: testdata/p4_16_samples_outputs/free-form-annotation-first.p4)
@liujed I see you've made quite a few additional commits to p4c to handle various annotation body use-cases. I'm wondering if P4Info needs to accommodate these cases, e.g. via enhancements to the proposed ParsedAnnotation message. Are we missing something?

The proposed ParsedAnnotation looks mostly there, but I have a couple of concerns.
First, it appears to be missing the ability to distinguish between annotations that are recognized by the compiler, and ones that are not. I don't know if this is important in this context, but p4c has different internal representations for @MyAnno3("Hello", 1 << 3, 1 + 1), depending on whether it recognizes (and parses) MyAnno3 annotations, analogous to the difference between
    parsed_annotations {
      name: "@MyAnno3"
      elements {
        value: "\"Hello\""
      }
      elements {
        value: "1 << 3"
      }
      elements {
        value: "1 + 1"
      }
    }

and
    parsed_annotations {
      name: "@MyAnno3"
      elements {
        value: "\"Hello\", 1 << 3, 1 + 1"
      }
    }

In the former case, the annotation body is parsed into a list of expressions; in the latter case, the body is just an uninterpreted sequence of tokens. With the current proposal in this PR, these two cases are indistinguishable for an annotation like @AmIInterpreted(1 + 1). Both cases would result in
    parsed_annotations {
      name: "@AmIInterpreted"
      elements {
        value: "1 + 1"
      }
    }

I can imagine a few ways of addressing this, if this is indeed a concern. My suggestion would be to not deprecate the annotations element; only annotations that are recognized and parsed by the compiler would have a corresponding entry in parsed_annotations. This is the smallest and cleanest change I can think of.
A second, perhaps lesser concern, is that I'd be careful to preserve whitespace in uninterpreted annotations. The annotation in the example appears as follows:
@MyAnno7(
- What do you get if you multiply six by nine?
- Six by nine. Forty two.
- That's it. That's all there is.
- I always thought there was something fundamentally wrong with the
  universe.
0xdeadbeef
)

I would expect the following result (perhaps with \n instead of actual new-lines):
    annotations: "@MyAnno7(
- What do you get if you multiply six by nine?
- Six by nine. Forty two.
- That\'s it. That\'s all there is.
- I always thought there was something fundamentally wrong with the
  universe.
0xdeadbeef
")

and
    parsed_annotations {
      name: "@MyAnno7"
      elements {
        value: "
- What do you get if you multiply six by nine?
- Six by nine. Forty two.
- That\'s it. That\'s all there is.
- I always thought there was something fundamentally wrong with the
  universe.
0xdeadbeef
"
      }
    }

@liujed Thanks for the detailed feedback. I agree with your second point - preserve whitespace. And in my example, I substituted hard linebreaks for \n for readability, perhaps I should put in '\n' before the typographical linebreaks for clarity.
I also now feel that we should not deprecate the old-style annotations. As yourself and @stefanheule  both pointed out in different ways, we should avoid "lossy" transformations and making too many assumptions about how annotations will be used.
You wrote:

My suggestion would be to not deprecate the annotations element; only annotations that are recognized and parsed by the compiler would have a corresponding entry in parsed_annotations.

When I first read this I interpreted "recognized and parsed by the compiler" to mean "has a well-known/reserved name," from the list of p4c reserved annotations in the P4-spec Section 18 (ex. : "@name"), or from the list of P4info reserved annotations, Table A.1 in the P4Runtime spec (ex.: "@brief").
Then I realized you probalby were paraphrasing my language in https://github.com/p4lang/p4runtime/pull/238#issuecomment-536104501:

If an unstructured annotation doesn't contain a conforming AnnotationElement then it won't generate any.

This brings up a point. I believe p4c already suppresses outputting recognized annotations from either reserved list into the annotations fields. However, I'm not sure where this is documented. If so, can someone point me to it? I think it deserves mention in the P4Runtime spec. In any case, the language describing the generation of parsed_annotations need some clarification.
To summarize, I propose that I do the following:

Remove deprecations on old annotations - too many gotchas
Clarify that only non-reserved annotations generate annotations and parsed_annotations
Stipulate the preservation of whitespace and linebreaks
Clarify that P4Info doesn't emit reserved annotations in annotations or parsed_annotations

When I last commented I wasn't aware that P4 changed the grammar for annotations.  I think the new unstructured P4 annotations are a big step backwards, but it looks like it was already decided to go with that new proposal.
If we have to live with these new unstructured annotations, though, I don't think this PR makes much sense any more.  At most we can parse the name and the completely unstructured list of tokens, but I don't know how much value there is in that.  If we think there is, we can do it, but otherwise it might be easiest to just not do anything.

@stefanheule My understanding is there can still be parsing of expressions and kv-pairs for purposes of generating P4Info. The language spec is simply removing any grammar requirements for the body of  an annotation, i.e. anything inside the matching () is legal. The P4Runtime spec, not the P4-16 Language spec, controls the generation of P4Info and thus can declare, for a certain annotation format, it will indeed be parsed as stated in the PR. p4c strives to accommodate both the language requirements and P4Info generation. Anyone agree/disagree?

@chrispsommers I'm assuming we can close this old PR now?

@antoninbas yes, this is obsolete. Thanks.


Prepare for custom URL parser

We need a custom URL parser to support relative file URLs. It is not ready but we need to release 0.1.0 asap, so this PR merges the compatibility-breaking changes, so that the new URL parser can land in a minor release.

bors merge


Filter runs locally instead of via API query param

The Github API is currently returning stale results when the event query param is supplied. They appear to be about 24 hours old. It seems likely that filtered results are eventually consistent and there's some sort of indexing delay on Github's side.
Removing the event filter from the API request returns up-to-date results. The results are filtered with jq instead.

Reopened the PR from my personal account: https://github.com/felixp8/dispatch-and-wait/pull/8


NavLink always active if href="/"

If you use the NavLink component in a blazor application and point to the base url href="/" it will always be marked as active.
We have a navigation item called Home that points to "/". This navigation item will always have the class active on it even if you navigate to a different page.

Okay found the solution by adding the Match=NavLinkMatch.All attribute on the NavLink element.
So now it looks like this:
<NavLink href="/" Match=NavLinkMatch.All>Home</NavLink>


prediction boxes is wrong.

First Image is CornerNet-Saccade result and second Image is CornerNet-squeeze result.

Is there a problem in NMS process?

CornerNet-Saccade estimates object locations via attention maps and detects object in a small region around each location. If the predicted attention maps are not sufficiently good, CornerNet-Saccade may miss an object or only see part of it. It seems to me that CornerNet-Saccade is not able to generate sufficiently good attention maps for this image.
More details about how the quality of the attention maps affects the performance of CornerNet-Saccade can be found in the experiment section of our paper.

Get it! Thank you very much! Good job!


Filter for projects

Hi, very good workflow, ty.
Are you planning to add a filter for projects? This would help companies with a lot of repositories. For example, the company has 100 repositories, but the user works only with 5 projects. In this case, the user sees a lot of unnecessary information.

Thanks! Could you please explain this in more detail? From my point of view, there is already a project filter in the workflow. Just type bitbucket and then you can choose Search for projects. Or are you looking for a way to filter the list of repositories by project?


adjusted the size of the calculator

The calculator was way too big previously and we had to scroll down to see the full calculator.
i have adjusted the height of the calculator and now we don't have to scroll down to see the full calculator

ps- add hacktoberfest label to this PR

this fixes the issue #16

Thanks 🙌


Add SqlUtils.dropTrigger that takes a DatabaseWrapper

To use during migrations. Otherwise one has to resort back to raw SQL
queries to using the migration's DatabaseWrapper instance.
Improve related JavaDoc comments too.

BTW. you could set "develop" as the default project branch so that pull requests go against it automatically :-)

ping

@agrosner Sorry to bug you about it again...

Rebased once more


Improved Tag UI by Adding Spacing, Clickable Chips, and Search and Clear Functionality

I have made these changes:

Enabled tag click functionality: Clicking on a tag now automatically fills the search box with the corresponding tag value and triggers the search.
Added a clear button to reset the search box and remove any selected tags, allowing users to easily start a new search.
Increased spacing between tags for better readability and distinctiveness.
Updated tag styling to resemble clickable chips, providing a clearer indication of interactivity.
Added hover effects that change the background color and add subtle shadows to give visual feedback when users interact with the tags.

All changes have been tested to ensure proper functionality and usability. Please review the enhancements and provide feedback.

You have made an incredible change to our website, and it looks really great! If you think of any other enhancements that could make the user experience more interesting, feel free to go for it. Thank you for your valuable contributions!