Parse IOS 16.1.1 Log failed

I got the logarchive from iPhone Device. and the logarchive  can be read via Mac OS log command.
E:\temp\logs>unifiedlog_parser.exe -i E:\temp\logs\CameraD3Y.logarchive -o E:\temp\logs\Camera.csv
Starting Unified Log parser...
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:00 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\00\._39384A699C34058A9D5E4E5CD780BF: Incomplete(Unknown)
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:00 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\04\._63432F754C379D94BB675E2C0A3F4D: Incomplete(Unknown)
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:00 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\09\._A4F4D99F2F341580AFC6CC2A99CC11: Incomplete(Unknown)
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:00 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\0B\._FFFF79EB0035E9A1613B6E2F20AC27: Incomplete(Unknown)
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:00 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\0D\._EB3248238C35229CE78FD92266346E: Incomplete(Unknown)
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:00 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\0E\._125B33B6BA3EFD917F9A01C95F5FA2: Incomplete(Unknown)
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:00 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\11\._295075F6B93D35935E1FB5B54650AA: Incomplete(Unknown)
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:00 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\12\._1BE04B7F5A35DDB9A7DF90E8DF0BBA: Incomplete(Unknown)
21:54:00 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
..............
21:54:02 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\FD\._67E91FC5F53BFEA8C8EBDCCE076F99: Incomplete(Unknown)
21:54:02 [ERROR] [macos-unifiedlogs] Incorrect UUIDText header signature. Expected<PHONE_NUMBER>. Got: 118883584
21:54:02 [ERROR] [macos-unifiedlogs] Failed to parse UUID file E:\temp\logs\CameraD3Y.logarchive\FD\._DE23A9719734379F402669D84F254D: Incomplete(Unknown)
Parsing: E:\temp\logs\CameraD3Y.logarchive\Persist\._000000000000000e.tracev3
21:54:02 [ERROR] [macos-unifiedlogs] Failed to parse the tracev3 file: Error(Error { input: [0, 5, 22, 7, 0, 2, 0, 0, 77, 97, 99, 32, 79, 83, 32, 88, 32, 32, 32, 32, 32, 32, 32, 32, 0, 2, 0, 0, 0, 9, 0, 0, 0, 50, 0, 0, 0, 146, 0, 0, 0, 2, 0, 0, 0, 196, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 65, 84, 84, 82, 0, 0, 0, 0, 0, 0, 0, 196, 0, 0, 0, 156, 0, 0, 0, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 156, 0, 0, 0, 40, 0, 0, 24, 99, 111, 109, 46, 97, 112, 112, 108, 101, 46, 108, 111, 103, 100, 46, 109, 101, 116, 97, 100, 97, 116, 97, 0, 0, 1, 0, 0, 0, 180, 90, 207, 42, 242, 15, 73, 151, 150, 255, 83, 84, 87, 101, 225, 124, 170, 170, 170, 170, 163, 204, 63, 9, 0, 0, 0, 0, 250, 20, 52, 155, 0, 0, 0, 0], code: Eof })
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Tracev3Parse', unifiedlog_parser\src\main.rs:141:39
stack backtrace:
   0:     0x7ff6c4ed834f - <unknown>
   1:     0x7ff6c4ef0dca - <unknown>
   2:     0x7ff6c4ed4679 - <unknown>
   3:     0x7ff6c4eda9eb - <unknown>
   4:     0x7ff6c4eda665 - <unknown>
   5:     0x7ff6c4edaf99 - <unknown>
   6:     0x7ff6c4edae9d - <unknown>
   7:     0x7ff6c4ed8cd7 - <unknown>
   8:     0x7ff6c4edab79 - <unknown>
   9:     0x7ff6c4f00255 - <unknown>
  10:     0x7ff6c4f003d3 - <unknown>
  11:     0x7ff6c4d899ce - <unknown>
  12:     0x7ff6c4d85fc8 - <unknown>
  13:     0x7ff6c4d8e1a6 - <unknown>
  14:     0x7ff6c4d92f3c - <unknown>
  15:     0x7ff6c4ece55b - <unknown>
  16:     0x7ff6c4d8d1b7 - <unknown>
  17:     0x7ff6c4ef8260 - <unknown>
  18:     0x7ffb2b6374b4 - BaseThreadInitThunk
  19:     0x7ffb2d6226a1 - RtlUserThreadStart

hi @zytzjx thanks for opening the issue.
It looks like AppleDouble files were created by the log (or maybe logd) command in addition to copying the log files.
I have not done alot of research into the files but they may have metadata about file attributes?
Ex: ._39384A699C34058A9D5E4E5CD780BF contains metadata related to attributes for the file 39384A699C34058A9D5E4E5CD780BF
If curious on how I arrived at AppleDouble files, I took the error output:
0, 5, 22, 7, 0, 2, 0, 0, 77, 97, 99, 32, 79, 83, 32, 88, 32, 32, 32, 32, 32, 32, 32, 32, 0, 2, 0, 0, 0, 9, 0, 0, 0, 50, 0, 0, 0, 146, 0, 0, 0, 2, 0, 0, 0, 196, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 65, 84, 84, 82, 0, 0, 0, 0, 0, 0, 0, 196, 0, 0, 0, 156, 0, 0, 0, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 156, 0, 0, 0, 40, 0, 0, 24, 99, 111, 109, 46, 97, 112, 112, 108, 101, 46, 108, 111, 103, 100, 46, 109, 101, 116, 97, 100, 97, 116, 97, 0, 0, 1, 0, 0, 0, 180, 90, 207, 42, 242, 15, 73, 151, 150, 255, 83, 84, 87, 101, 225, 124, 170, 170, 170, 170, 163, 204, 63, 9, 0, 0, 0, 0, 250, 20, 52, 155, 0, 0, 0, 0
And converted it from decimal using cyberchef and reviewed the raw binary
> file data.raw
data.raw: AppleDouble encoded Macintosh file

It looks like the dot_clean on a macOS system can merge the AppleDouble files back with the original file.  If a macOS system is not available you can simply delete or move the ._* files out of the logarchive.  The parser should then work
I can also probably push an update to the example files to skip files that start with ._ which seems to be the prefix for AppleDouble files
Let me know if there are still issues or questions with the parser.
Thanks.

Thanks. I have remove   ._*  files.  I can get csv file.
unifiedlog_parser.exe -i E:\temp\logs\Camerabak.logarchive -o E:\temp\logs\Camera.csv
Starting Unified Log parser...
Parsing: E:\temp\logs\Camerabak.logarchive\Persist\000000000000000e.tracev3
Parsing: E:\temp\logs\Camerabak.logarchive\Persist\000000000000000f.tracev3
Parsing: E:\temp\logs\Camerabak.logarchive\Persist\0000000000000010.tracev3
Parsing: E:\temp\logs\Camerabak.logarchive\Persist\0000000000000011.tracev3
Parsing: E:\temp\logs\Camerabak.logarchive\Special\000000000000000d.tracev3
22:44:24 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:24 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:24 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 1, error_len: Some(1) }
22:44:24 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 1, error_len: Some(1) }
22:44:24 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
Parsing: E:\temp\logs\Camerabak.logarchive\Special\000000000000000e.tracev3
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 1, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 1, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:25 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:26 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:26 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
Parsing: E:\temp\logs\Camerabak.logarchive\Special\000000000000000f.tracev3
22:44:27 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:27 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 3, error_len: Some(1) }
22:44:27 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:27 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 1, error_len: Some(1) }
22:44:27 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
Parsing: E:\temp\logs\Camerabak.logarchive\Special\0000000000000010.tracev3
Parsing: E:\temp\logs\Camerabak.logarchive\Special\0000000000000011.tracev3
Parsing: E:\temp\logs\Camerabak.logarchive\Special\0000000000000012.tracev3
22:44:29 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 1, error_len: Some(1) }
22:44:29 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:29 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 2, error_len: Some(1) }
22:44:29 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 3, error_len: Some(1) }
22:44:29 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:29 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
22:44:29 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 1, error_len: Some(1) }
22:44:29 [WARN] [macos-unifiedlogs] Failed to get string: Utf8Error { valid_up_to: 0, error_len: Some(1) }
Parsing: E:\temp\logs\Camerabak.logarchive\Signpost\0000000000000005.tracev3
Parsing: E:\temp\logs\Camerabak.logarchive\Signpost\0000000000000006.tracev3
Parsing: E:\temp\logs\Camerabak.logarchive\Signpost\0000000000000007.tracev3
Parsing: logdata.LiveData.tracev3
Parsed 1417312 log entries

Finished parsing Unified Log data. Saved results to: output.csv


Deprecation policy

Description
Readme update

Deprecation policy
Dynamo based instructions
Quickstart / quick installation
separated detailed installation + contribution guide

@peri044 can you help fill in the instructions for the export flow?

@laikhtewari Here's the example for export : https://github.com/pytorch/TensorRT/blob/main/docsrc/user_guide/saving_models.rst


The programmer called Zhendi posts a link to a github reporitory on reddit

The comments suggest this will go horribly wrong.

Went better than expected


Hide "Statistics" tab if there is not enough data

[x] Transform tabs into a computed property and adds a condition to render the tendencies tab

Resolves #189


remove target filtering tag

I manually checked the generated JSON for the affected powers to confirm the change. The definitions are defaulting to the game folder because I haven't used thus feature before now. I can correct it tomorrow night or Sunday to direct the definitions to the GitHub folder instead so that the change in definitions is captured


Organization API key expired

Yo @ReubenBond think i'm dealing with an expired organization API key for pushing to NuGet
    - name: Push to NuGet
      run: dotnet nuget push *.nupkg --skip-duplicate -s https://api.nuget.org/v3/index.json -k ${{secrets.NUGET_KEY}}

https://github.com/OrleansContrib/Orleans.SyncWork/actions/runs/7855264915/job/21436806519

@ReubenBond I assigned you as you took care of this last time, but let me know if there's someone else I should ping

Thanks for the ping, @Kritner! I've updated the key - let me know if you hit issues with it.

Awesome, thanks!  Was able to get nuget push through on the latest pipeline run


Short solution needed: "How to store time series" (redis-timeseries)

Please help us write most modern and shortest code solution for this issue:
How to store time series (technology: redis-timeseries)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to store time series


fix: do not allow reserved context keys in ServerContext or UserContext

Do not allow reserved context keys in UserContext and ServerContext if they don't match
For example, you cannot have request as a key in UserContext or ServerContext unless it is Request like below;
// @ts-expect-error Not allowed
createYoga<{
    request: FastifyRequest
}>(/* ... */);

// But allowed
createYoga<{
    req: FastifyRequest
}>(/* ... */);

// Also allowed
createYoga<{
    request: Request // From Fetch API
}>(/* ... */);

Great idea ! You need help to actually finalize it ?

It'd be great @EmrysMyrddin
There are still issues with TS stuff.

I will take a look :-)


Updated remoting Port to work with Wildfly 10.0.0.CR4

I wasn't able to shutdown a Wildfly running as Windows Service created using the Service-Package from contrib directory. The reason was using the old remoting port which has been changed from 9990 to 9999.

Can one of the admins verify this patch?

this is ok to test

obsolete due to wrong configuration in standalone.xml


Migrate Cypress integration tests from volto-slate-project and make them work

[x] migrate the rest of the tests from volto-slate-project
[ ] make the PR pass the Cypress tests

@tiberiuichim @valentinab25 @avoinea
At the moment of this writing, this is the latest version of the reset-fixture.js fixture in Volto's Cypress tests.
I tried to move tests from the old Volto Slate Project into Volto Slate in this PR, and the relevant file is this (the same role as the above file).
It is almost the same code, but it does not work when called with the teardown parameter.
I get the following error when running $ node cypress/support/reset-fixture.js teardown:
Error: connect ECONNREFUSED <IP_ADDRESS>:55001
      at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
    errno: 'ECONNREFUSED',
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '<IP_ADDRESS>',
    port: 55001
  }

and no output and no error when running $ node cypress/support/reset-fixture.js.
But the teardown version of the command is required to reset the DB on each test run by Cypress.
So does it seem that the following XMLRPC facility was removed from Plone?
client.methodCall(
  'run_keyword',
  [
    'remote_zodb_teardown',
    ['plone.app.robotframework.testing.PLONE_ROBOT_TESTING'],
  ],
  (error, value) => {
      ...
  },
);

When running $ docker pull plone:
Using default tag: latest
latest: Pulling from library/plone
Digest: sha256:6af6a9bbf8f09ca4ef29fed607a30fb2eee46aea792a6b181573d579ba74f523
Status: Image is up to date for plone:latest
docker.io/library/plone:latest

The above output looks to me like the plone image is up-to-date on my computer.
So this is the story of the issue that I get errors like this one from the second test on, in CI.
What is the next step in making this PR pass the Cypress tests in your opinion? Thanks.

@tiberiuichim @valentinab25 @avoinea
At the moment of this writing, this is the latest version of the reset-fixture.js fixture in Volto's Cypress tests.
I tried to move tests from the old Volto Slate Project into Volto Slate in this PR, and the relevant file is this (the same role as the above file).
It is almost the same code, but it does not work when called with the teardown parameter.
I get the following error when running $ node cypress/support/reset-fixture.js teardown:
Error: connect ECONNREFUSED <IP_ADDRESS>:55001
      at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
    errno: 'ECONNREFUSED',
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '<IP_ADDRESS>',
    port: 55001
  }

and no output and no error when running $ node cypress/support/reset-fixture.js.
But the teardown version of the command is required to reset the DB on each test run by Cypress.
So does it seem that the following XMLRPC facility was removed from Plone?
client.methodCall(
  'run_keyword',
  [
    'remote_zodb_teardown',
    ['plone.app.robotframework.testing.PLONE_ROBOT_TESTING'],
  ],
  (error, value) => {
      ...
  },
);

When running $ docker pull plone:
Using default tag: latest
latest: Pulling from library/plone
Digest: sha256:6af6a9bbf8f09ca4ef29fed607a30fb2eee46aea792a6b181573d579ba74f523
Status: Image is up to date for plone:latest
docker.io/library/plone:latest

The above output looks to me like the plone image is up-to-date on my computer.
So this is the story of the issue that I get errors like this one from the second test on, in CI.
What is the next step in making this PR pass the Cypress tests in your opinion? Thanks.

FYI I used the following command to start the backend:
$ docker run -d --name plone -p 8080:55001 -e SITE=Plone -e PROFILES="profile-plone.restapi:blocks" plone

FYI I used the following command to start the backend:
$ docker run -d --name plone -p 8080:55001 -e SITE=Plone -e PROFILES="profile-plone.restapi:blocks" plone


Microsoft.Bot.Connector.Place incorrectly stored in Bot Conversation Data (JObjectBotData)

Pre-flight checklist

[ ] I posted a question about this issue on Stack Overflow using the tag #botframework.
[x] I have searched the existing issues before logging a new one.

System Information

SDK language (C#)
SDK version 3.5.6-alpha
Development environment - localhost

Issue Description
I am trying to store an instance of Microsoft.Bot.Connector.Place into the bot's PrivateConversationData.
It is stored incorrectly because apparently the internal dynamic types are stored a JObjects and cannot be converted back to GeoCoordinate and PostalAddress later on.
Example Code
Save the place by:
context.PrivateConversationData.SetValue<Place>("UserLastSeenPosition", place);

and retrieve it like:
var place = context.PrivateConversationData.Get<Place>("UserLastSeenPosition");
var coordinates = place.GetGeoCoordinates()

Expected Behavior
Place can be deserialized correctly without additional work from the consumer.
Actual Results
The call to place.GetGeoCoordinates() will throw: Exception: Cannot convert type 'Newtonsoft.Json.Linq.JObject' to 'Microsoft.Bot.Connector.GeoCoordinates'
Analysis
I suspect this is because the serializer will use reflection to get the type of nested objects to deserialize them to a specific type. By being declared as dynamic, there is no type information associated with the member, so the deserializer fallback to a JObject type.
My workaround is to append this after retrieving the value from the store:
                if (place != null)
                {
                    var geo = place.Geo;
                    if (geo is JObject)
                    {
                        place.Geo = ((JObject)geo).ToObject<GeoCoordinates>();
                    }
                }

Do you think it is possible to convert the dynamic types to a strong type in the Place class? Would you accept a pull request doing so?
Thank you.

@andreesteve are you still experiencing the issue after upgrading to BotBuilder v3.8.1?


Turn Auth Tests On

We turned off auth tests in #683 until datproject.org is a bit more stable and we are starting to use it.

These were added back in #799.


🐛 [OFFICIAL] Generated Issue: ConnectionTimeoutException

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The API has returned an error:
MongoDB\Driver\Exception\ConnectionTimeoutException
Status code: 13053
Message: No suitable servers found (`serverSelectionTryOnce` set): [connection timeout calling hello on '<IP_ADDRESS>:27017']
Trace: /var/www/jikan-rest/vendor/mongodb/mongodb/src/functions.php on line 487
Expected Behavior
The API should have returned a successful response with data.
Steps To Reproduce
Http Request: `GET /v4/anime/11617/full
Environment
No response
Anything else?
No response

Duplicate https://github.com/jikan-me/jikan-rest/issues/501


Use address derivation from cardano-addresses

Context

We have separate cardano-addresses repo that contains implementation of mnemonics and address derivation interface along with byron, icarus, jomrungandr and shelley implementations
Decision

We want to use address-derivation's interfaces and impl inside cardano-wallet, and replace it with current ones
Acceptance Criteria

HardDerivation, SoftDerivation, StakingDerivation, PaymentAddress and DelegationAddress
Use crypto primitives from cardano-addresses
Use Depth, Index, DerivationType, AccountStyle` from cardano-addresses
Styles and corresponding unit tests are removed
The rest codebase is adjusted

Development

QA

Tracked in JIRA as: https://jira.iohk.io/browse/ADP-438


[Fix #11800] Mark Style/InvertibleUnlessCondition as unsafe

Fixes #11800.
This PR marks Style/InvertibleUnlessCondition as unsafe. @safety is already documented:
https://github.com/rubocop/rubocop/blob/v1.50.1/lib/rubocop/cop/style/invertible_unless_condition.rb#L20-L23

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


Ignored glob pattern with v0.41.0

Hi, I find a behavior change about glob between v0.40.0 and v0.41.0.
I'm not sure this change is a breaking change within the v0.41.0 release note, but it seems a bug to me. 🤔
If my reported change is the breaking change, feel free to close this issue.
Expected Behavior
ktlint 'src/**/*.kt' should analyze src/App.kt.
Observed Behavior
ktlint 'src/**/*.kt' ignores src/App.kt.
Steps to Reproduce

Prepare src/App.kt.
Run ktlint 'src/**/*.kt'.

Success without output.

On the other hand, ktlint 0.40.0 analyzes src/App.kt expectedly. See below for details:
$ tree -a
.
├── ktlint
├── ktlint-0.40.0
└── src
    └── App.kt

1 directory, 3 files

$ cat src/App.kt
fun main(args: Array<String>) {
  println("Hello");
}

$ ./ktlint 'src/**/*.kt'
(no output)

$ ./ktlint-0.40.0 'src/**/*.kt'
/private/tmp/foo/src/App.kt:2:1: Unexpected indentation (2) (should be 4)
/private/tmp/foo/src/App.kt:2:19: Unnecessary semicolon

$ ./ktlint --version && ./ktlint-0.40.0 --version
0.41.0
0.40.0

Your Environment

Version of ktlint used: 0.41.0
Name and version (or code for custom task) of integration used (Gradle plugin, Maven plugin, command line, custom Gradle task): Not used
Version of Gradle used (if applicable): Not used
Operating System and version: Mac OS X 10.15.7 (19H15)
Link to your project (if it's a public repository): None

Should be resolved with 0.43.0, please re-open otherwise


[StableHLO] Error compiling model with StableHLO

What happened?
(iree.venv) mariewhite@marie:~/github/iree$ iree-compile --iree-hal-target-backends=cuda --iree-input-type=stablehlo_experimental --iree-hal-cuda-llvm-target-arch=sm_80 /tmp/hlo.mlirbc -o /tmp/hlo.vmfb
/tmp/hlo.mlirbc:1:1: error: one or more illegal operations were found in the compiler input (are you missing an --iree-input-type= flag, or did you mean to pre-process through an IREE importer frontend?)
module {
^
/tmp/hlo.mlirbc:660:12: note: failed to legalize operation 'stablehlo.batch_norm_inference' that was explicitly marked illegal
    %337 = "stablehlo.batch_norm_inference"(%336, %17, %16, %15, %14) {epsilon = 1.001000e-05 : f32, feature_index = 3 : i64} : (tensor<128x112x112x64xf32>, tensor<64xf32>, tensor<64xf32>, tensor<64xf32>, tensor<64xf32>) -> tensor<128x112x112x64xf32

Steps to reproduce your issue

Download MLIR at https://storage.googleapis.com/iree-model-artifacts/tensorflow/tf_models_2.12.0_1683544084/RESNET50/batch_128/hlo.mlirbc

Compile:

iree-compile --iree-hal-target-backends=cuda --iree-input-type=stablehlo_experimental --iree-hal-cuda-llvm-target-arch=sm_80 /tmp/hlo.mlirbc -o /tmp/hlo.vmfb

Changing stablehlo_experimental to mhlo works.
What component(s) does this issue relate to?
Compiler
Version information
iree-compiler version 20230503.508
Additional context
No response

Thanks for reporting, @mariecwhite. This works for me on https://github.com/openxla/iree/commit/8cd5dd93e6764cd3c8f0ec4c376e7705758aa23e and compiles without any errors.
Please reopen if this still happens to you on a newer build.


Check if __registry actually exists on the current class, not a parent

Fixes #2455

@manolakis what do you think?


[CHANGE ME] Re-generated to pick up changes from self.

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/34aeb7fd-5547-45d8-a2a8-87cf6880ed3d/targets

[ ] To automatically regenerate this PR, check this box.

Superseded by #1206.


SQLSTATE[HY000]: General error: 8 attempt to write a readonly database

When trying to write to a sqlite database I get the following error: SQLSTATE[HY000]: General error: 8 attempt to write a readonly database

Fix: The folder the database resides in must have write permissions, as well as the actual database file.
On windows make sure your IIS_Users and Users have write permissions under security.


missing mypy detail when annotate_only=true

as briefly mentioned in: https://github.com/mikepenz/action-junit-report/issues/699#issuecomment-1983734072
basically when you have annotate_only=false (the default) you see something like this (similar to the repo README images):
and when you click "Raw Output" button you see the mypy error:

but with annotate_only=true you don't have the "Raw Output" button and therefore can't see the erorr

Upon a closer look, this is unfortunately a limitation from GitHub. There is a difference if a check is created, or if a normal annotation is built.
For the annotate_only a annotation property can be provided, and these don't allow for any additional information.

https://github.com/mikepenz/action-junit-report/blob/main/src/annotator.ts#L39-L53
https://github.com/actions/toolkit/blob/ef77c9d60bdb03700d7758b0d04b88446e72a896/packages/core/src/core.ts#L40

While check do allow an additional raw_details to bo be provided

https://docs.github.com/en/rest/checks/runs?apiVersion=2022-11-28#list-check-run-annotations

The only "alternative" I could think of would be to add the stacktrace as part of the message for the annotation, however not everyone may like that as it is quite verbose and there is no collapsing for it

Closing as we won't be able to have the same output for annotation_only.


NIFI-13088 Populate missing parameter context ids in MiNiFi flows.json.raw

Summary
NIFI-13088
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks for the fix. Merging.


Create Docs “react/react-study-guide/index”

Automatically generated by Netlify CMS

Browser metadata
Path:      /blog/
Browser:   Chrome 101.0.4951.67 on Windows 10
Viewport:  2560 x 1238 @0.75x
Language:  en-US
Cookies:   Enabled

Open in BrowserStack

Open Deploy Preview · Mark as Resolved


svc_interface.sysl does not handle untyped return ok response

given an endpoint like this:
foo:
    /orders:
        POST:
            return error <: Error
            return ok

the svc_client.sysl transform will create a func PostOrders(ctx context.Context, req *PostOrdersRequest) (*http.Header, error) however the svc_interface.sysl does not handle the untyped ok and it generates PostOrders(ctx context.Context, req *PostOrdersRequest) error instead. This ends up causing a compile time failure trying to initialisae the service interface.

@anz-gordonj7 "return ok" should work now, it generates the following code.
GetEmptyokList            func(ctx context.Context, req *GetEmptyokListRequest, client GetEmptyokListClient) error
The code also compiles, there are working examples in simple.sysl.

@springwiz I must not have been clear enough, sorry.
svc_client.sysl generates the func (in the service interface) -> PostOrders(ctx context.Context, req *PostOrdersRequest) (*http.Header, error)
svc_serviceinterface.sysl generates the func -> PostOrders(ctx context.Context, req *PostOrdersRequest) error
Notice how the 2 signatures are different? They must be the same or else the generated code wont compile.

@springwiz the testcase for simple.sysl is an endpoint that calls another endpoint which returns ok


[SWITCHYARD-2744] - Added facility to override SSL hotname verifier and stores

https://issues.jboss.org/browse/SWITCHYARD-2744

Can one of the admins verify this patch?

ok to test

Processed by Jenkins.


Create gort role info command

The gort role info command should exist (for parity with cogctl)
(From docker run -it operable/cogctl:alpine-1.0.1 cogctl role info --help)
cogctl role info --help
Usage: cogctl role info [OPTIONS] ROLE

  Show role details

Options:
  --help  Show this message and exit.

Closing as a duplicate of https://github.com/getgort/gort/issues/42.


Adds coverage calculation by individual file feature.

@ptashman I squashed and rebased, plus ghost wrote an extra sentence into the README.
If you're happy with this, I'll hit merge as soon as travis confirms green.

Sounds good to me. Thanks!

Very cool, thanks!


Add Probabilistic to GPUStreamlines

Done:
-> Adds model agnostic probabilistic option
-> Adds first draft of a model agnostic PTT option
-> Handle c vs fortran order for all inputs, not just dataf
-> Moves all the run*.py files into one so I only had to make changes in one place (If there is a reason this was in four files, I can put it back)

Hey @36000 : any reason not to merge this now?

I will merge

Should we merge to master?
On Wed, Oct 30, 2024 at 5:49 PM John Kruper @.***>
wrote:

Merged #17 https://github.com/dipy/GPUStreamlines/pull/17 into
csaodf_debug_2.
—
Reply to this email directly, view it on GitHub
https://github.com/dipy/GPUStreamlines/pull/17#event-15022011890, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA46NX6YWH5EHSW2G3KTJ3Z6F5B7AVCNFSM6AAAAABKAYHZJOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGAZDEMBRGE4DSMA
.
You are receiving this because you commented.Message ID:
@.***>

I created #18 to advance merging this into the master branch.


Cloning Handing

Hello,
I am just trying to set up my first project in PHPCI.
When I go to build It stops on cloning.

Any pointers to where to look?

Well I am not sure what I did but I have reached my next error
fatal: ambiguous argument 'Manual^!': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]

See this https://github.com/Block8/PHPCI/issues/1051#issuecomment-141104748

Thanks @zippy1981  I am going to close this now as i just swapped versions and that fixed it :)


V2.17.0 skip CI

tensorflow 2.17.0
Destination channel: main
Links

https://github.com/tensorflow/tensorflow/tree/v2.17.0
Relevant dependency PRs:

https://github.com/AnacondaRecipes/python-flatbuffers-feedstock/pull/1
https://github.com/AnacondaRecipes/flatbuffers-feedstock/pull/4
https://github.com/AnacondaRecipes/tensorboard-feedstock/pull/1
https://github.com/AnacondaRecipes/ml_dtypes-feedstock/pull/3
https://github.com/AnacondaRecipes/libml_dtypes-headers-feedstock/pull/1
https://github.com/AnacondaRecipes/rsync-feedstock/pull/2 (for complex file copies in build.sh)
https://github.com/AnacondaRecipes/snappy-feedstock/pull/5 (with rtti enabled, for linux builds)
https://github.com/AnacondaRecipes/keras-feedstock/pull/4 (keras >=3.2)
https://github.com/AnacondaRecipes/bazel-feedstock/pull/19

Explanation of changes:

Moving back recipe from tensorflow_recipes to here.
Sync with CF.
abs.yaml configured to not build cuda on CI
Building with XNN option xnn_enable_avx512fp16=false as GCC 11.8 does not support avx512fp16
Building with jpeg, not libturbo_jpeg
Updated keras required.
Snappy with rtti required on linux.
Updated bazel to 6.5
Updated bazel toolchain scripts based on bazel-toolchain 0.2.0 (See https://github.com/AnacondaRecipes/bazel-toolchain-feedstock/pull/2)
Make python handling less hermetic - packages are still downloaded from pypi at build time, but our packages are used at run time. This results in a number of overdepending warnings.

Platforms working

[x] linux-64
[x] linux-64 cuda
[x] linux-aarch64
[x] osx-64
[x] osx-arm64
[ ] win-64 - to be done on subsequent PR.

The cuda packages are built, can provide them when ready to upload rest of stuff.

Would it be possible to split up the conda-forge sync from the rest of the changes? It would make the whole review a lot easier.

Would it be possible to split up the conda-forge sync from the rest of the changes? It would make the whole review a lot easier.

Sure, here is a PR with the sync changes only: https://github.com/AnacondaRecipes/tensorflow-feedstock/pull/2

Linter check found the following problems:
Traceback (most recent call last):
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/percy/parser/recipe_parser.py", line 117, in _parse_yaml
    output = cast(JsonType, yaml.safe_load(s))
                            ^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/__init__.py", line 125, in safe_load
    return load(stream, SafeLoader)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/__init__.py", line 81, in load
    return loader.get_single_data()
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/constructor.py", line 49, in get_single_data
    node = self.get_single_node()
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/composer.py", line 35, in get_single_node
    if not self.check_event(StreamEndEvent):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/parser.py", line 98, in check_event
    self.current_event = self.state()
                         ^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/parser.py", line 142, in parse_implicit_document_start
    if not self.check_token(DirectiveToken, DocumentStartToken,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/scanner.py", line 116, in check_token
    self.fetch_more_tokens()
  File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/scanner.py", line 258, in fetch_more_tokens
    raise ScannerError("while scanning for the next token", None,
yaml.scanner.ScannerError: while scanning for the next token
found character '%' that cannot start any token
  in "", line 1, column 2:
    {% set tensorflow_cpu_gpu = "tens ...
     ^
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/conda/envs/linter/lib/python3.12/site-packages/anaconda_linter/run.py", line 208, in main
return_code, report = execute_linter(
^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/anaconda_linter/run.py", line 180, in execute_linter
result = linter.lint(recipes, subdir, variant_config_files, exclusive_config_files, fix_flag)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/anaconda_linter/lint/init.py", line 728, in lint
msgs = self.lint_file(
^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/anaconda_linter/lint/init.py", line 834, in lint_file
self.lint_recipe(
File "/opt/conda/envs/linter/lib/python3.12/site-packages/anaconda_linter/lint/init.py", line 894, in lint_recipe
res = self.check_instances[check].run(recipe, fix)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/anaconda_linter/lint/init.py", line 294, in run
self.check_recipe(recipe)
File "/opt/conda/envs/linter/lib/python3.12/site-packages/anaconda_linter/lint/check_syntax.py", line 35, in check_recipe
ro_parser: Final[RecipeParser] = recipe.get_read_only_parser()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/percy/render/recipe.py", line 675, in get_read_only_parser
return RecipeParser("\n".join(self.meta_yaml))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/percy/parser/recipe_parser.py", line 328, in init
new_node = RecipeParser._parse_line_node(clean_line)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/percy/parser/recipe_parser.py", line 147, in _parse_line_node
output = RecipeParser._parse_yaml(s)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/percy/parser/recipe_parser.py", line 126, in _parse_yaml
cast(JsonType, yaml.safe_load(s)), lambda d: substitute_markers(d, sub_list)
^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/init.py", line 125, in safe_load
return load(stream, SafeLoader)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/init.py", line 81, in load
return loader.get_single_data()
^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/constructor.py", line 49, in get_single_data
node = self.get_single_node()
^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/composer.py", line 35, in get_single_node
if not self.check_event(StreamEndEvent):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/parser.py", line 98, in check_event
self.current_event = self.state()
^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/parser.py", line 142, in parse_implicit_document_start
if not self.check_token(DirectiveToken, DocumentStartToken,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/scanner.py", line 116, in check_token
self.fetch_more_tokens()
File "/opt/conda/envs/linter/lib/python3.12/site-packages/yaml/scanner.py", line 258, in fetch_more_tokens
raise ScannerError("while scanning for the next token", None,
yaml.scanner.ScannerError: while scanning for the next token
found character '%' that cannot start any token
in "", line 1, column 2:
{% set tensorflow_cpu_gpu = "tens ...
^
ERROR conda.cli.main_run:execute(125): conda run conda-lint /tmp/abs_64h1h801od/clone failed. (See above for error)

It would be nice to move the other tensorflow repos to the deprecated repo

Will do once this is merged in.

This isn't a fork of conda-forge's recipe, which we can't change now, but maybe we could add something in the README to that effect, i.e. something to tell whoever works on this next that they should pull conda-forge's changes with changes made in this PR made again on top of that.

Added comment to README.

We also had sporadic xcode-related failures on osx-64 and osx-arm64:
10/02/24 10:38:16  INFO   Analyzing: 3 targets (646 packages loaded, 25696 targets configured)
                   INFO   ERROR: /private/var/tmp/_bazel_builder/3d27507a171c46891a410d16c736a180/external/local_config_apple_cc/BUILD:61:23: in
                          apple_cc_toolchain rule @local_config_apple_cc//:cc-compiler-darwin_arm64: Xcode version must be specified to use an Apple CROSSTOOL.
                          If your Xcode version has changed recently, verify that "xcode-select -p" is correct and then try: "bazel shutdown" to re-run Xcode
                          configuration
                   INFO   ERROR: /private/var/tmp/_bazel_builder/3d27507a171c46891a410d16c736a180/external/local_config_apple_cc/BUILD:61:23: Analysis of target
                          '@local_config_apple_cc//:cc-compiler-darwin_arm64' failed
                   INFO   ERROR: /private/var/tmp/_bazel_builder/3d27507a171c46891a410d16c736a180/external/bazel_tools/src/tools/launcher/BUILD:9:14: errors
                          encountered resolving toolchains for @bazel_tools//src/tools/launcher:launcher
                   INFO   ERROR:
                          /private/var/folders/k1/30mswbxs7r1g6zwn8y4fyt500000gp/T/abs_fdl1h7az42/croot/tensorflow-split_1727883363694/work/tensorflow/tools/bu…
                          errors encountered resolving toolchains for //tensorflow/tools/build_info:gen_build_info

however restarting the build solves it. It could have been differences in configuration of our (physical) osx builders.


Bug: incorrect/spurious transformation être → êtree.

Describe the Bug
When a text contains "être", this word is transformed into "êtree", which is incorrect (in French).
How to Reproduce
Steps to reproduce the behavior:

Make sure that "Auto-correct common misspellings" is On in the Linter settings.
Type "être" in a note.
Launch the linter.

Expected Behavior
The word "être" should instead not be touched.
Device

[X] Desktop
Mobile not tested

Hey @lebigot , is there a reason not to add that value to the ignore list? English is the only language that the auto fix is really designed for. So for French words that may be the case, but when used in English it may not be the same (assuming that is even a thing). However if that is a French word and the English usage is spelled as you suggest, that should probably be bubbled up to the codespell maintainers to get it fixed there as well.

I have not heard anything about this. in about 2 weeks. If I do not hear anything else by Sunday, I will close this issue since I am not able to validate the claim here on my own with the information provided.

There is a reason to not add "être" to the ignore list: there is no valid reason for it to be transformed into "êtree" anyway, be it in French or English, where "êtree" doesn't exist, and fixing at the source is more useful for everybody.
Now, codespell 2.2.4 (the latest version) doesn't run into this problem.
Maybe the bug comes from a previous version of codespell? Maybe it is somewhere in linter? Maybe it's a while guess, but maybe linter somehow doesn't recognize the "ê" and codespell applies its rule "tre" → "tree", resulting in "être" being transformed into "êtree", which is not correct?

This may be a bug in the Linter where that rule you suggested may be getting applied. Let me see if it gets modified in a UT and move forward from there. The possibility you suggested could be the case. I wonder if python has a different default set for regex which could cause the issue in question.

Looks like I have a fix for this. Thanks for taking a look at codespell and verifying it was not in the list @lebigot !

The change should go out with the next release.

Great, thanks!


Update ndm to 1.0.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

back to v1.0.0 comment


Service creation issue

[x] Decimal issue in sales price

Steps

disable sales information
Then enable sales information
click save button

issue fixed !


Question abou the triplet loss you use?

Hi, I have question about the triplet loss in your paper.
Here you said that the margin you use is infinite value, and you write the formulation as follow:

I wonder whether the value of this loss can be negative? That means ap_{i,j} < an_{i, j} (or the distance between the anchor to positive sample is smaller the that between negative sample, and this seems easy to reach?) What does it mean when loss  is less than zero? how can it be optimized?

Hi @DanilHu ,
sorry for delay! See the answers below.

I wonder whether the value of this loss can be negative?

Yes, it definitely can, and if you run  sample training it will get negative very quickly.

What does it mean when loss is less than zero? how can it be optimized?

It means exactly what you wrote, so the positive sample is more similar to the anchor than the negative sample and this is what we want. For the optimizer it doesn't matter if it's positive or negative, as soon as the loss landscape is smooth.
Best,
Daniel

Closing, feel free to reopen if you have any other questions.


React 15.2 seriously breaks formsy

[06:19:50.068] "Warning: Unknown props `layout`, `validatePristine`, `validations`, `validationError`, `validationErrors`, `addonBefore`, `addonAfter`, `buttonBefore`, `buttonAfter` on <input> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in input (created by Input)
    in div (created by Row)
    in Row (created by Input)
    in Input (created by _form)
    in fieldset (created by _form)
    in form (created by Formsy)
    in Formsy (created by _form)
    in _form (created by Container(_form))
    in Container(_form) (created by UseDeps(Container(_form)))
    in UseDeps(Container(_form)) (created by _class)
    in div (created by _class)
    in div (created by _class)
    in div (created by _class)
    in div (created by _class)
    in _class (created by _class)
    in div (created by _class)
    in div (created by _class)
    in _class (created by WithDeps(_class))
    in WithDeps(_class)"

Please have a look at :
 React 15.2 Unkown Prop Warning #517

Looks like problem in formsy-react-components. Please open issue in that repo

Is this is a warning in both production and development mode? Does it still work on production mode? I'll look into this, of course, but apart from the warning is anything actually "seriously broken" in production mode?

I have no prior experience with formsy and only a little bit of experience with the app that uses it.  The bug is certainly a complete show stopper, but that may simply be due to poor exception handling, I do not know.
Facebook has changed the rules about passing properties to React components.  When I saw that, and saw formsy's dependence on passing non-React properties into form components, I did not investigate further.
The failure is in the v0.2.1 branch of this repo if you want to see it "in-the-wild".  (Installation instructions are at the bottom of the README)

Hi @martinhbramwell, thanks for the detail. It's pretty easy to reproduce. I've added an issue over here. This should be okay to close here, I think.

Ok.  As far as I'm concerned I am trapped at React 15.1.  If I try to upgrade to 15.2 then formsy seems to kill my app.  Possibly Facebook's changes are killing some other thing that fails to throw a visible exception.
I don't know, I haven't been able to determine what's really going on.

Why is that closed if is not fixed yet? (I stilll have the issue by the way, but i've settled for 15.1 for now)

@albertotorresfoltyn just update formsy-react-components


Added ssl_versions parameter

This commit adds the ssl_versions parameter. This allows users to
choose which versions of SSL that RabbitMQ should accept.

Looks great! One small docs request.

I've amended the README -- let me know how it reads.

Looks great, thanks!

Hi, this feature has an issue in that the functionally added is ignored by RabbitMQ (or Erlang?).
Tested with:
$openssl s_client -connect localhost:5671 -ssl3
$openssl s_client -connect localhost:5671 -tls1
$openssl s_client -connect localhost:5671 -tls1_1
$openssl s_client -connect localhost:5671 -tls1_2
(note the output line "Protocol  :")
The actual result is that tls1, tls1.1 and tls1.2 are still enabled, even when specifying only [ 'tls1.1', 'tls1.2'].
The syntax of the rabbitmq.config file in the change should actually add a line to ssl_options ",{versions, ['tlsv1.1', 'tlsv1.2']}". Compare syntax with https://www.rabbitmq.com/ssl.html#disabling-tls-versions
I suggest it does the same to ssl_opts of the rabbitmq_management block also.
I've also noted that the line "{ssl, [{versions, ['tlsv1.1', 'tlsv1.2']}]}" (which is outside the rabbit config block in the docs) doesn't have any effect on ssl protocol support.
Though this is included in the docs(https://www.rabbitmq.com/ssl.html), and does no harm being there.
Perhaps it is my versions of erlang(1:17.4) or rabbitmq-server (3.4.3-1), can you confirm the above tests work for you with the current patch?

I have seen the same result regarding tlsv1 still being enabled even though it is not specified in the config. I saw this while I was working on this patch. There's some prior discussion in #291 which was a rough draft of this patch.
I'm not exactly sure how to disable tlsv1 entirely given I've followed everything in the RabbitMQ docs and haven't looked into this further yet. Suggestions are definitely welcome.

Thanks for confirming, I'd not read all of #291. I've got this working and disabling tls1.0 with the above noted changes to your patch.
I'll be looking to submit these for review tomorrow (GMT).

Created pull request #301 with these changes.


fix fullwidth ！

the ! in != should use halfwidth form instead of fullwidth,  otherwise it will cause trouble in K8s.
More about halfwidth and fullwidth in Chinese
Signed-off-by: Hollow Man<EMAIL_ADDRESS>

/lgtm

/assign @xichengliudui


OB 2 Lolicode Color

Can we “” change colors in Lolicode view like in OB1?
<test>
OB1 this “” is yellow so it’s easy to see them.
OB1
https://prnt.sc/1skejlz
OB2
https://prnt.sc/1skegls

Colored with the last update.
thank you for your interest @Ruri

It's working in some cases and in others not.
Example:
POST request content: ✔
Custom headers: ❌
Is this intentional?

It's working in some cases and in others not.
Example:
POST request content: ✔
Custom headers: ❌
Is this intentional? @openbullet

@nero-0 This happens because the current pattern does not account for variables inside lists and dictionaries, and honestly it might be pretty hard to implement (especially in the native client) since the $ symbol is at the start of the line and not before each string. If you want you can reopen this but I see it as low prio.

I can't reopen, but it's something I'd like to see in OB2 at some point in the future.


Playing around with dynamic specifications from wkt2 strings

Went with urllib to keep everything in the standard library for pulling the input WKT2.

weird, so my fix apparently broke the tests because sometimes a None is returned for the authority. I am digging into it now but it looks like converting to a dict first will always resolve the id
for example the CRS for Steins (2015) - Sphere / Ocentric has a valid authority of {'authority': 'IAU', 'code': 200286700, 'version': 2015}, but for Toutatis (2015) - Sphere / Ocentric, I get a None for the authority, but when converted to a dict first I get {'authority': 'IAU', 'code': 200417900, 'version': 2015} which seems fine

Messing with this a bit more this morning. Here are a few things that I noticed:

Validating these through morecantile+pydantic fails because they lack, naturally, EPSG codes. Code below to reproduce.  I am not sure who maintains opengis.net to see about adding the IAU codes. Maybe an OGC working group?

    import morecantile
    tms = morecantile.TileMatrixSet.parse_file('Moon_2000_tms.json')

Copying one of these custom TMS *.json files into the morecantile data area, which seems to be one method to register them causes the same error as above.

Option 1: Hack the CRSes in the JSON files.
In the short term, it might be most elegant to perform this hack (replace None with 4326 since these are all GCS. It would be significantly better to figure out who maintains opengis.net and try to get the IAU authorities added.
If one hacks the supportedCRS and and boundingBox:crs it is the validator works. The resulting TMS looks like:
{
    "type": "TileMatrixSetType",
    "title": "Sun (2015) - Sphere / Ocentric",
    "identifier": "IAU_1000_2015",
    "supportedCRS": "http://www.opengis.net/def/crs/EPSG/0/4326",
    "boundingBox": {
        "type": "BoundingBoxType",
        "crs": "http://www.opengis.net/def/crs/EPSG/0/4326",
        "lowerCorner": [
            -90.0,
            -180.0
        ],
        "upperCorner": [
            90.0,
            180.0
        ]
    },

Option 2: Register a custom TMS to morecantile

It is also possible to use the following to properly create a custom TMS (note that this is showing examples with the ESRI authority and the IAU authorities):

from pyproj import CRS

mars_crs = CRS.from_authority("ESRI", 104971)
ESRI104971 = morecantile.TileMatrixSet.custom(
    crs=mars_crs,
    identifier="Mars_2000_Sphere_ESRI",
    extent=mars_crs.area_of_use.bounds,
    matrix_scale=[1, 1],
)

iau_mars_crs = CRS.from_authority("IAU", "49900")
IAU49900 = morecantile.TileMatrixSet.custom(
    crs=iau_mars_crs,
    identifier="Mars_2000_Sphere_IAU",
    extent=mars_crs.area_of_use.bounds,
    matrix_scale=[1, 1],
)

I played around with parsing the WKT into custom TMSes for morecantile. This seems to be working to get these registered.

import urllib
with urllib.request.urlopen('https://raw.githubusercontent.com/pdssp/planet_crs_registry/main/data/result.wkts') as response:
    resp = response.read().decode(response.headers.get_content_charset())

import os
geocrss = []
for wkt_str in resp.split(os.linesep + os.linesep):
    if 'GEOGCRS' in wkt_str[:7] and 'TRIAXIAL' not in wkt_str:  # insanely hacky
        geocrss.append(wkt_str)

for crs in geocrss:
    crs_obj = CRS(crs)
    title = crs_obj.name
    auth = crs_obj.to_authority(min_confidence=25)
    if auth is not None:
        authority_version, code = auth
        authority, version = authority_version.split('_')
        identifier = f'{authority}_{code}_{version}'

        if crs_obj.area_of_use:
            bounds =  crs_obj.area_of_use.bounds  # Not sure that this is working?
        else:
            bounds = [-180, -90, 180, 90]
        custom_tms = morecantile.TileMatrixSet.custom(
                                                    crs=crs_obj,
                                                    identifier=identifier,
                                                    extent=bounds,
                                                    matrix_scale=[1, 1])

        # Strange append because morecantile.tms is a custom object
        morecantile.tms = morecantile.tms.register(custom_tms)
morecantile.tms.list()

Results in (truncated):
['LINZAntarticaMapTilegrid',
 'EuropeanETRS89_LAEAQuad',
 'CanadianNAD83_LCC',
 'UPSArcticWGS84Quad',
 'NZTM2000',
 'NZTM2000Quad',
 'UTM31WGS84Quad',
 'UPSAntarcticWGS84Quad',
 'WorldMercatorWGS84Quad',
 'WGS1984Quad',
 'WorldCRS84Quad',
 'WebMercatorQuad',
 'IAU_1000_2015',
 'IAU_19900_2015',
 'IAU_19901_2015',
 'IAU_29900_2015',
 'IAU_30100_2015',
 'IAU_39900_2015',
 'IAU_39901_2015',
 'IAU_40100_2015',
 'IAU_40200_2015',
 'IAU_49900_2015',
...

All of this is to say: How are we anticipating one use these custom TMS?

@jlaura That is a lot of great detective work and I can't respond to it all now, but a few things I can say:

Registering the custom TMSs is already a part of planetcantile https://github.com/AndrewAnnex/planetcantile/blob/5ea2577f5dc4a3bc91b0443ef0633a5f89b15e03/planetcantile/defaults.py#L1-L16
Which was the initial intent of this repo to both generate correct TMS specs as json files and to register them in python for those using python. I hope there are also other projects (JS frontends?) to contribute the json files elsewhere so that other non-python frameworks can use them or we could also make additional libraries to distribute these files. Section Annex D of the TMS 2.0 spec (https://docs.opengeospatial.org/is/17-083r4/17-083r4.html#toc48) lists some common ones for Earth so I can imagine maybe a similar list being published for planetary bodies along with the json files.. My hope is that these custom TMS become standardized and just as easy to access/use as 4326.

That's really interesting about the opengis.net, since it is the OGC definitions server we should do some work to identify what changes they need to support IAU better and see how quickly that can happen. I think I identified another specification (well known scale sets) that need to be adjusted to each planetary body and I think those are also defined at opengis.net (see https://defs.opengis.net/vocprez/object?uri=http%3A//www.opengis.net/def/wkss). The alternative would be to do the 4326 hack, but let's see how far we can go without it.

I planned to add some steps to the github action to add any changes to the json files made in a PR as a commit to the PR also so the generate.py file is only really used by the ci service to support continuous delivery of these specs.

@jlaura this looks relevant to our discussion https://github.com/opengeospatial/NamingAuthority/issues/212

Good find! This is what Trent has been talking about. I did not realize the timeline and that it would be linking through opengis.net. That solves the problem on our side as far as I can tell!
We'll have to check morecantile/proj to ensure that they are encoding the URL properly, e.g., that they didn't hard code the /0/ where we need the IAU year /2015/ and IAU vs EPSG. That should get the identifiers straightened out and the code up and running. 🚀

as an update to point 2 I made above, I made this PR for morecantile to support generating more-correct scaleDenominators by using the CRS ellipsoid's semi major axis rather than hard-coding the earth radius (https://github.com/developmentseed/morecantile/pull/92). Looking into it the WKSS part may be partially deprecated in TMS 2.0 so we may not need to define additional wkss's
I totally agree about figuring out a way to remove NAIF Ids from the names of the bodies, but I am unsure what the right solution would be for that at the moment if the NAIF id is used is the code and if the code must be an integer?
for the urls encodings in morecantile this looks like the relevant bit of code:
https://github.com/developmentseed/morecantile/blob/689cad98914033e746f7eca78719c6e751f843a4/morecantile/models.py#L72-L75

I'll make a pr for that also as it could use the same logic I added to this pr to grab the code/version/authority

😆 I was just logging on to get that pushed in. 👍 Glad to see the PRs opened.
With a hopeful update to opengis, I think that these will be all set to deploy without a bunch of hackiness. Once that is the case, I am happy to host these as a lambda at a USGS URL as a community service.

👋 this is a great conversation 😄
Let me know if I can help with anything. I've seen mentioned to the TMS spec 2.0, just to be clear right now morecantile creates TMS of version 1.0, if it can be helpful to you I can start working of switching to 2.0 🤷♂

@vincentsarago thanks so much for that info, good to know about the TMS spec, I had assumed wrongly about TMS 2.0 already being implemented. We don't have an immediate need for 2.0 in morecantile but likely that would be of interest eventually. I am still very much learning about the TMS spec in general, so it would be very helpful to get your guidance on what else needs to be done to support these IAU CRSs better in morecantile and also in projects downstream of it.

@jlaura looks like Vincent merged in the first of the two PRs earlier today, there was a bit more work to do with the 2nd one but I think we're now at a much better spot with it and hope it can be merged in soon. Time to come up with more tasks!

one thing that could be good is to think about the maxzoom parameter a bit. I could imagine that for low res data sets like MOLA we could tune that to lower numbers but we'd want TMS specs usable for HiRISE images also. Maybe it's best to assume a higher zoom level always for each body and assume clients would do the right thing and not attempt to render tiles much finer than the best resolution available.

@AndrewAnnex 🎉 That's great news!
I think we need to support a really wide range zoom range and then assume that the client or user will do the correct thing. For example, if we have a TMS MOLA base (resolutions is like 463m or so?) and someone wants to tile a long CTX string (50x lines at 6mpp), I think we want them to be able to use the same TMS endpoints.
Next steps on the TMS:

Wait for the opengis.net update to happen.
Test deploy the TMSes to the endpoint.
Test registering the endpoint to stac browser at stac.astrogeology.usgs.gov/browser-dev. That has Europa, Moon, and Mars example.

Are you thinking of other next steps for TMS or in general? I am not super fluent in the topography encoding, but you seemed pretty excited about that. Can I assist there? I've been starting to look at vector tiles and SLD symbology definitions as well. I have a pygeoapi deploy as an AWS lambda that I am trying to use to learn about the vector side of things. COG and STAC standards / best practices are probably right up there too. For example, we have WKT2 codes, but they will not properly encode out of GDAL without some coaxing. 😆 So, lots of areas!

@jlaura sounds good regarding the wide zoom ranges, I'll do some thinking to come up with a reasonable limit (possibly 24 or 25; for earth zoom level 24 is 0.009m GSD at the equator assuming an equirectangular projection, so smaller bodies would be even finer scale resolution than that, 24 may be more sensible as that would ensure tiles indexes remain within 24bits if that even matters... some things to think about anyways)
Next steps sound good. Once the morecantile prs are merged in (and maybe a new version is released) the changes in this PR can be merged.
I sent you an email before I saw this and had some thoughts about the topography encoding which for now I think are somewhat independent from this until the opengis update happens. My biggest unknown is what else needs to happen to js frontends assuming we get these parts working. I also haven't thought much about the vector side yet, interested to hear why the wkt2 codes wouldn't work with ogr/gdal...
We may need to move the discussion elsewhere on github, maybe as issues on this repo?

Different file in the repository (planetcantile/defaults.py) , no longer broken due to recent pushes I made to fix- Dr. Andrew AnnexOn Dec 13, 2022, at 2:07 PM, Vincent Sarago @.***> wrote:
@vincentsarago commented on this pull request.
In planetcantile/data/generate.py:

for tmsp in crss:
# create the tms object
tms = morecantile.TileMatrixSet.custom(**asdict(tmsp))
_d = json.loads(tms.json(exclude_none=True))  # get to pretty printed json

with open(f'./{tmsp.crs.name}_tms.json', 'w') as dst:

with open(f'./{tmsp.identifier}_tms.json', 'w') as dst:
# dump to json
json.dump(_d, dst, indent=4, ensure_ascii=False)
print(f'wrote {dst.name}')

err "like" it but not exactly it, also not working currently
what is not working?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

I am going to try to merge this PR and clean up things a bit to ensure that the work is captured. I've saved a PDF of the page saving all of the discussions above just in case but will leave the pr up to allow the conversation to continue a bit here until it needs to move on to other prs/issues


Adds FeatureTable[PresenceAbsence] as input for taxa filter-table

closes #161

I'd say to add a test, but it's not interesting because it would be identical to a FeatureTable[Frequency] but with only 1s and 0s. Merging


feat: seat based pricing in plans

Features can be configured with behavior: per_seat while creating to make the plan charge org based on number of users at the end of the subscription billing cycle.

https://github.com/raystack/proton/pull/328

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 42.372%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
5896

Relevant Lines:
13915

💛  - Coveralls


ModbusTcpClient(redacted:1502): Connection unexpectedly closed

Basically there two, connected, error messages (copies from Log)

2022-08-20 23:08:40.007 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Error fetching SolarEdge Coordinator data: Failed to update devices: Modbus Error: [Connection] ModbusTcpClient(.......:1502): Connection unexpectedly closed 0.000131 seconds into read of 8 bytes without response from unit before it closed connection

2022-08-21 05:54:43.009 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Error fetching SolarEdge Coordinator data: Failed to update devices: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
2022-08-21 05:55:46.007 ERROR (SyncWorker_5) [pymodbus.client.sync] Connection to (......., 1502) failed: timed out
2022-08-21 05:56:49.006 ERROR (SyncWorker_0) [pymodbus.client.sync] Connection to (......., 1502) failed: timed out
....... continuing...
Solaredge thru modbus is unreachable. No data is coming into HA. Solaredge entities are: not available.
Getting control back by either by resetting or reinstall of the integration Solaredge.
Reconfigured the WiFI connection with my LAN brought no solution.
Every time within a few hours after a restart, both errors appear.
Solaredge Support updated my Solaredge and stated that the transformer is operating ok.
Home Assistant (please complete the following information):

Home Assistant Core Version: 2022.8.6 and .5
solaredge-modbus-multi Version:  2.1.2 also 2.1.1. The integration is standard configured.

Please, do you have  a solution?

First try turning on the "Keep Modbus Connection Open" option.

Thanks for the reply.
Turned Keep .... open on.
Will report tomorrow after 24 hrs.

If that doesn't help, I've also created a pre-release for the latest pymodbus dev version: v2.1.2-pymodbusdev.1
If you are using HACS you will need to turn on "show beta versions" for the integration in HACS (you can do this by choosing "redownload")

@WillCodeForCats. Will keep your suggestion in mind.
A Status update.
Applied Keep ..connection open.
In the last hour Solaredge status is alternating per 300 sec (call freq.) between status: 4 (production) and status: not available and per 10 minutes an error:
Error fetching SolarEdge Coordinator data: Failed to update devices: Modbus Error: [Connection] ModbusTcpClient(<IP_ADDRESS>:1502): Connection unexpectedly closed 0.000475 seconds into read of 8 bytes without response from unit before it closed connection

We can randomly try things but if the inverter is dropping the connection during the read there's probably no actual fix I can come up with.
I don't use wifi so if there's a network problem related to wifi anywhere in the communication path I probably won't see the issue personally.

Did you try the pymodbusdev.1 pre release version?

@WillCodeForCats.
Not yet. Will do that tomorrow.
I am also contemplating how to connect Solaredge with a cable instead of WiFi.

I've created Release v2.1.3-pre.1 which adds disconnect calls on modbus read errors. The idea is that if there is an error it will make sure the connection is closed and re-opened on the next attempt.

@WillCodeForCats.
Tomorrow is this evening. Installed V2.1.2-pymodbusdev.1 pre.
20 min Solaredge status: in production, after that, alternation of status started again: 5 min in production and 5 min not available. No improvement.
Just saw your 2.1.3-pre.1. Will try it.

Just to be clear, read errors can't be prevented by the integration. I can only change how the integration handles errors.

@WillCodeForCats
Applied  2.1.3-pre.1. It looks good so far. No alternation of statuses seen.
Let see what the performance will be the coming 24 hrs.
Support for your focus on error handling.

@WillCodeForCats
In status "production", last night started at 20:39 and continued in sleeping mode at 21:14 56 error messages were recorded until 5:49:

Deze fout is ontstaan door een aangepaste integratie.
Logger: custom_components.solaredge_modbus_multi
Source: custom_components/solaredge_modbus_multi/hub.py:347
Integration: SolarEdge Modbus Multi Device (documentation, issues)
First occurred: 21 augustus 2022 20:39:31 (56 occurrences)
Last logged: 05:49:31
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(...:1502): Connection unexpectedly closed 0.000135 seconds into read of 8 bytes without response from unit before it closed connection
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(..:1502): Connection unexpectedly closed 0.000132 seconds into read of 8 bytes without response from unit before it closed connection
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(..:1502): Connection unexpectedly closed 0.000136 seconds into read of 8 bytes without response from unit before it closed connection
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(...:1502): Connection unexpectedly closed 0.000138 seconds into read of 8 bytes without response from unit before it closed connection
Unexpected error fetching SolarEdge Coordinator data: Modbus Error: [Connection] ModbusTcpClient(1....:1502): Connection unexpectedly closed 0.000164 seconds into read of 8 bytes without response from unit before it closed connection
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/solaredge_modbus_multi/init.py", line 121, in _async_update_data
return await self._hub.async_refresh_modbus_data()
File "/config/custom_components/solaredge_modbus_multi/hub.py", line 291, in async_refresh_modbus_data
await self._hass.async_add_executor_job(inverter.read_modbus_data)
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/solaredge_modbus_multi/hub.py", line 447, in read_modbus_data
inverter_data = self.hub.read_holding_registers(
File "/config/custom_components/solaredge_modbus_multi/hub.py", line 347, in read_holding_registers
return self._client.read_holding_registers(address, count, **kwargs)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/common.py", line 114, in read_holding_registers
return self.execute(request)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 109, in execute
return self.transaction.execute(request)
File "/usr/local/lib/python3.10/site-packages/pymodbus/transaction.py", line 174, in execute
response, last_exception = self._transact(
File "/usr/local/lib/python3.10/site-packages/pymodbus/transaction.py", line 294, in _transact
result = self._recv(response_length, full)
File "/usr/local/lib/python3.10/site-packages/pymodbus/transaction.py", line 326, in _recv
read_min = self.client.framer.recvPacket(min_size)
File "/usr/local/lib/python3.10/site-packages/pymodbus/framer/init.py", line 49, in recvPacket
return self.client.recv(size)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 89, in recv
return self._recv(size)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 297, in _recv
return self._handle_abrupt_socket_close(
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 342, in _handle_abrupt_socket_close
raise ConnectionException(msg)
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] ModbusTcpClient(.....:1502): Connection unexpectedly closed 0.000101 seconds into read of 8 bytes without response from unit before it closed connection
At 5.49 sleeping mode changed into a non recoverable "not available" generating per 5 min. error messages:

2022-08-22 05:54:34.007 ERROR (SyncWorker_4) [pymodbus.client.sync] Connection to (.., 1502) failed: timed out
2022-08-22 05:59:37.009 ERROR (SyncWorker_2) [pymodbus.client.sync] Connection to (.., 1502) failed: timed out
2022-08-22 06:04:40.007 ERROR (SyncWorker_2) [pymodbus.client.sync] Connection to (.... 1502) failed: timed out
.........
At 8:30 I made a total hardware restart and in HA, Solaredge status is showing "production"......

Added connection exception in Release v2.1.3-pre.2

@WillCodeForCats
Implemented -pre.2

@WillCodeForCats.
Update freq. set to 120 sec.
Results -pre.2.
Happy with the results of work; it works; thanks for far. However,
With status 2 (sleeping) for the second night a non recoverable error meaning in the morning status not changed from 2 to 4. A restart of HA was necessary.
In sleeping mode, is an automatic recovery possible after experiencing an error just like in production mode?
It will prevent a restart every morning and I would be grateful!
error message:
Logger: pymodbus.client.sync
Source: /usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py:218
First occurred: 01:04:49 (209 occurrences)
Last logged: 08:11:13
Connection to (<IP_ADDRESS>, 1502) failed: timed out

Instead of restarting HA can you try reloading only the integration?

@WillCodeForCats.

Reload. Will do the next time. Thanks!
-pre.3 successful updated thru standard update procedure. Tomorrow night I will report.

Release v2.1.3-pre.4
Discovered a potential shutdown or reload bug during my testing.

@WillCodeForCats.
Thanks for informing.
With release V2.13-pre3.
This afternoon a non-recoverable error. Status production changed into 'unknown" but no return into 'production'.
Reload and restart had no effect. A Host restart did the trick.
error message:
2022-08-24 13:03:23.010 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Error fetching SolarEdge Coordinator data: Update failed: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
2022-08-24 13:05:26.017 ERROR (SyncWorker_3) [pymodbus.client.sync] Connection to (....., 1502) failed: timed out
2022-08-24 13:07:29.005 ERROR (SyncWorker_3) [pymodbus.client.sync] Connection to (......, 1502) failed: timed out
etc. etc. etc. ....
May this error message be helpful with discovery of a potential shutdown.
Release 2.2.0-pre.1 installed and continued monitoring.

@WillCodeForCats
Yes I am using WiFI. I contemplating to implement a cable backbone. But it is not a spare afternoon job. Some planning and cable pulling have to be done.
Appreciate your efforts for which I am very thankful. Hopefully some help is offered.

@bakboord4
Some extensive testing done and conclusion is that this issue, for me, can be closed.
Changed in My Fritz modem/router from Autochannel to fixed. Remains a more than 2 min. WiFi not available (Mesh reorganization?) per night which causes about 30 min not available status of Solaredge but Release 2.2.1 recovers that after 30 min. or so. A reboot automation will be fired for the situation that it takes more than 30 min. Perhaps not the best solution. This integration needs sometimes some help.
A cable connection for Solaredge in my home is not easy to be done.
Seth, many thanks for all the effort you put in to create solutions.

Thanks for your help testing.
Once the pymodbus library has a 3.0.0 release I will make a pre-release for that.

Perfect.

pymodbus has released v3.0.0
I have updated the pymodbus-dev branch to support the latest release version. You can download the branch to try it manually: https://github.com/WillCodeForCats/solaredge-modbus-multi/archive/refs/heads/pymodbus-dev.zip

@WillCodeForCats. Thanks, will implement it and report back

@WillCodeForCats. Tested. pymodbus functioned uninterrupted or recovered automatic from WiFi issues.

That's great to hear it's recovering properly with the latest pymodbus. I will plan to merge PR #132 and make a pre-release with the dependency change to pymodbus==3.0.0.


Feature: Shareable public wishlist view

Is your feature request related to a problem? Please describe.
Currently there's no way to share a wishlist with someone without them also having an account. Sharing a Christmas list with family, for instance, requires all family members to register first just to see the items.
Describe the solution you'd like
Having a public URL for a list would enable linking to it in view-only mode (or perhaps even allowing for claiming an item). Most registry and gift list websites allow for this without requiring gift givers to also register.
Describe alternatives you've considered
An alternative would be a password protected public view so that the page isn't completely exposed.
Additional context
Love the app! Amazing work, would love this feature added 🙏

Hi! Thanks for the request and feedback. This feature actually already is available as of a few versions ago. It's under the group settings called "Wishlist Mode", you can set this value to be "Registry" and it will act as you described.
The limitations with this is that there is only a single list and you cannot switch your group if it already has multiple users in it.
Let me know if this is what you're after!

Awesome! Yes this is the exact functionality I was looking for 🎉  Apologies, I didn't see anything when going through my instance/readme.
Thanks so much for the great app!


Convert security-secrets-setup to use common bootstrap package

Major refactor.
Fixes: https://github.com/edgexfoundry/edgex-go/issues/2104

Codecov Report

Merging #2142 into master will decrease coverage by 0.6%.
The diff coverage is 66.55%.

@@            Coverage Diff             @@
##           master    #2142      +/-   ##
==========================================
- Coverage    41.1%   40.49%   -0.61%
==========================================
  Files         182      181       -1
  Lines       12386    12291      -95
==========================================
- Hits         5091     4977     -114
- Misses       6998     7045      +47
+ Partials      297      269      -28

Impacted Files
Coverage Δ

...ernal/security/secrets/command/generate/flagset.go
100% <100%> (ø)

...nternal/security/secrets/certificates/interface.go
100% <100%> (ø)
:arrow_up:

internal/security/secrets/seed/seed.go
94.73% <100%> (ø)

internal/security/secrets/certificates/tls.go
78.66% <100%> (ø)
:arrow_up:

internal/security/secrets/command/cache/flagset.go
100% <100%> (ø)

internal/security/secrets/certificates/root.go
74.6% <100%> (ø)
:arrow_up:

internal/security/secrets/certificates/crypto.go
100% <100%> (ø)
:arrow_up:

...nternal/security/secrets/command/import/flagset.go
100% <100%> (ø)

internal/security/secrets/helper/helper.go
27.77% <50%> (ø)

...rnal/security/secrets/command/generate/generate.go
52% <52%> (ø)

... and 10 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 3fb26d3...219a1ed. Read the comment docs.

This draft PR represents a significant refactoring of the security-secrets-setup service in order to enable it to use the common bootstrap package.  I removed at least two layers of abstraction, separated individual command implementations (based on GoF command pattern), and rewrote the tests.  While I believe I've maintained the functionality and spirit of the prior implementation, I'll let you be the judge.
I'm not able to test this service in situ.  When I built a local image, substituted it into the latest developer-scripts docker-compose file, and brought the system up, it looks to me as if the service crashes.  Please don't blame me.  I have the exact same experience when I use the code from the tip of master.
Tingyu reached out to me earlier today asking about broken tests for this service during make test on his local machines (he apparently tried both Windows and Linux).  While I'm not sure what that's all about, I can say it's not my code (since it hasn't been merged).  It also begets the question -- how did changes that cause failing tests get past the build system?
In any case, I'd be grateful if you can expedite a review of these changes.  Happy to answer any questions.  Changes to this service on master to correct the existing issue would likely create much grief for this effort.  Open to someone working interactively with me to help solve the outstanding issues with the master version of this service by making changes to my working branch.
@tsconn23 @bnevis-i @tingyuz @jim-wang-intel

The failure of test cases I had yesterday was related to configuration of zMQ. Once I configured them correctly all the test cases passed.
If the build on top of the tip of the master crashes I think it is better to find out the root cause and fix it before pushing more into the branch which will make debugging more difficult.

The failure of test cases I had yesterday was related to configuration of zMQ. Once I configured them correctly all the test cases passed.

I think it's safe to say your test failure experience is unrelated to the problem with the master version of this service crashing.

If the build on top of the tip of the master crashes I think it is better to find out the root cause and fix it before pushing more into the branch which will make debugging more difficult.

I'm fine with this as long as the changes to actual code in master for this service are very limited.  If they're not, we need to have a conversation on how best to proceed/reconcile.

For what is worth, I am observing no crashes of security-secrets-setup in either unit tests nor a full-built container with the nightly docker-compose.   Proceeding to review code.

Remove draft status to enable review.  If this is accepted, my intent is to squash everything into a single commit and force-push to keep master commit history clean.

@michaelestrin I need more time to review this..please hold on the merging.

@jim-wang-intel -- I will wait for your review approval.

Verified and confirmed the master build has no crash and it works well currently so what Michael saw could be the local testing environment issue.

Update based on requested changes forthcoming.

Rebased.  Addressed comments.  If/when approved, will use GitHub tool to squash and merge (closing #2150)


plocate

Project description
plocate is a locate(1) based on posting lists, completely replacing mlocate with a much faster (and smaller) index.
Metadata

homepage URL: https://plocate.sesse.net/
source URL: https://git.sesse.net/?p=plocate
license: gpl2+
platforms: linux, bsd, ...

I actually have it locally - both package and module. I'll open a PR today or tomorrow.

So we already have a locate module in nixos - when I built my own module, I completely disregarded that and just made one for plocate. So it has to be incorporated properly which I'm not likely to get done within the near future. I'll open 2 PRs. One for the package and one for the draft module to serve as inspiration in case somebody chooses to run with it.


[bug]: no Phantom and cannot connect to Solana from other wallets

Description
When the modal opens there is no Phantom wallet even though I have added the id to the attribute explorerRecommendedWalletIds.
What's more, in order to switch to Solana, I tried two ways of setting the chain of the provider, the first one is to provider.setDefaultChain('Solana:mainnetBeta')
The second is to fill the sessionParams:
const  sessionParams = {
  namespaces: {
    solana: {
      methods: [],
      chains: ['solana:mainnetBeta'],
      events: [],
      rpcMap: {},
    },
  },
};

However, the first one won't work and for the second one I have tested on Spot wallet and it prompts that the network is unsupported.
WalletConnect Modal SDK version
"@walletconnect/modal-react-native": "^1.0.0-rc.6",
Output of npx react-native info
System:
OS: Windows 10 10.0.22621
CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
Memory: 2.15 GB / 15.63 GB
Binaries:
Node:
version: 16.16.0
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 1.22.15
path: C:\Program Files\nodejs\yarn.CMD
npm:
version: 8.11.0
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-212.5712.43.2112.8609683
Visual Studio: Not Found
Languages:
Java: 17.0.5
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.3
wanted: ^0.72.3
react-native-windows: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Expo Version (if applies)
"expo": "^49.0.0"
Steps to reproduce
Try to connect with solana network.
Snack, code example, screenshot, or link to a repository
None

Hi, Phantom wallet does not support WalletConnect protocol


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1002 ms

Resolved: Bofrost.de performance has improved in 6b529f1 after 10 minutes.


The memory leak bug about powershell that fixed last release appeared again

VSCode Version:
OS Version:

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

Is this an issue with the Powershell extension?
For integrated powershell please create an issue against the extension repo https://github.com/PowerShell/vscode-powershell


Missing "required" labels in the InfluxDB OSS API docs

There are missing required labels in the InfluxDB OSS API docs.
status is required to add a new check
orgID is required to add a new notification endpoint
every is required to add a new notification rule
orgID and bucketID are required to create a new scraper target
orgID si required to create a source
orgID or/and org is required to create a task - it might be worth noting that it only works like this for the OSS InfluxDB version. When it comes to the cloud InfluxDB there is no need for either orgID or org. I believe the Create a Task orgID and org should be described as they are for deleting data.
orgID is required to create a Telegraf configuration
orgID is required to create a new stack
orgID is required to apply or dry-run a template
orgID within orgIDs is required to export a new template
There is also one excessive "required" in create a dashboard where the name IS NOT a required parameter to create a new dashboard.

@k3yi0 I agree - this belongs in openapi. Thanks for the nudge!


fixes: #343 Calendar looks more like wireframes

fixes #343
Please provide enough information so that others can review your pull request:
I've styled the calendar so the text is white and the background is a gradient darkblue => blue
Explain the details for making this change. What existing problem does the pull request solve?
The way I did this was by importing the react-calendar module main CSS file called Calendar.css and make the changes there. This CSS file is now located in /client/src/css/Calendar.css
Test plan (required)
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
Screenshot attached

Final Checklist

[ x] Have you bumped the version in package.json?

Second decimal for major change, third decimal for minor change. This can go past 10 i.e. 1.0.9 !=> 1.1.0, 1.0.9 => 1.0.10
Read here for more info

[ ] Have you added any new tests necessary?
[x ] Is your PR rebased off the most current master?
[ x] Have you squashed all commits, or if you will merge will you squash all commits?
[x ] Did you use yarn, not npm?
[x ] Did you use Material-UI wherever possible?
[x ] Did you format according to Prettier?
[x ] Did you run all of your most recent changes locally to make sure everything is working?

It looks great! I bet it took some time so thank you!

I believe all the yarn.locks are gone, is there a reason why it wasn't caught by .gitignore?

Well, I am not sure, to be honest 😅 I think it got to be with the git past comment maybe, it was not added and when you rebase something goes wrong. Git is wired sometimes
Look at this you may find something regarding it

Looks like we deleted the correct yarn.lock in the client directory and created one in the root directory (shouldn’t be there). Not a big deal, I can make a quick HOTFIX when I get home later today.
Just for future reference, we want to keep the yarn.lock from within the /client directory - if a yarn.lock shows up in the root directory, that probably means at one point you ran yarn install in the root directory, not the client directory 👍

Changes look great though!

@SomeMoosery yeah I didn't notice it is not inside /client 😅 Sorry about it

ah, i understand, i yarn installed in the wrong directory! my bad.


[google_maps_flutter] Poor performance rendering polylines

Details

Target Platform: Android
Target OS version/browser: Platform 29
Devices: OnePlus 6
flutter doctor -v

[√] Flutter (Channel master, v1.14.7-pre.58, on Microsoft Windows [Version 10.0.18362.592], locale en-NZ)
    • Flutter version 1.14.7-pre.58 at C:\tools\flutter
    • Framework revision 83d4d63a71 (19 hours ago), 2020-01-30 18:10:36 -0800
    • Engine revision e5209202fb
    • Dart version 2.8.0 (build 2.8.0-dev.6.0 162d6c5634)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\Zac\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)
    • All Android licenses accepted.

[√] Android Studio (version 3.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 28.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

[√] VS Code, 64-bit edition (version 1.41.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.7.1
[√] Connected device (1 available)
    • ONEPLUS A6000 • a21aff4f • android-arm64 • Android 10 (API 29)

• No issues found!

Polylines (and other shapes) have to be serialized to json while rendering. This is done per-point and  can be extremely slow.
Profile build:

As you can see a huge amount of time is taken up in _toJson.
I wrote a simple patch that caches the json representation of Polylines based on their ID using a singleton map. This reduced the frametime back to reasonable levels:

Patch

diff --cc packages/google_maps_flutter/lib/src/polyline.dart
index 0d7684fb,0d7684fb..6f0b3d14
--- a/packages/google_maps_flutter/lib/src/polyline.dart
+++ b/packages/google_maps_flutter/lib/src/polyline.dart
@@@ -251,11 -251,11 +251,34 @@@ Map<PolylineId, Polyline> _keyByPolylin
            polyline.polylineId, polyline.clone())));
  }

++class _PolylineCache {
++  _PolylineCache._internal();
++
++  static final _PolylineCache _singleton = _PolylineCache._internal();
++  static final Map<PolylineId, dynamic> _map = Map();
++
++  factory _PolylineCache() {
++    return _singleton;
++  }
++
++  dynamic operator [](PolylineId id) => _map[id];
++  void operator []=(PolylineId id, dynamic v) => _map[id] = v;
++
++  bool containsKey(PolylineId id) => _map.containsKey(id);
++}
++
  List<Map<String, dynamic>> _serializePolylineSet(Set<Polyline> polylines) {
    if (polylines == null) {
      return null;
    }
++  final cache = new _PolylineCache();
++
    return polylines
--      .map<Map<String, dynamic>>((Polyline p) => p._toJson())
++      .map<Map<String, dynamic>>((Polyline p) {
++        if (!cache.containsKey(p.polylineId)) {
++          cache[p.polylineId] = p._toJson();
++        }
++        return cache[p.polylineId];
++      })
        .toList();
  }

This will need to be edited to store the cache per GoogleMap instance as PolylineId is only unique per map. My implementation also has no upper size bound.
It may also be worth using a third party cache library, of which there are a few available.
It's also almost certainly worth doing this for polygons.

Hi @zacps
if you wish to submit a pr please take a look to this docs
thank you

It's unlikely I'll have the time to refine this into a good state for the foreseeable future.

How many points did you render before it started having poor performance?

I was rendering a large number of points, I don't have a precise number at the moment. Regardless this should ideally be fixed by switching to a binary serializer for points/polylines/... as json serialization is incredibly slow in flutter.

@zacps
from your last message seems that you solved the issue, is this the case?
tagging @TahaTesser for visibility

I ended up removing the view that drew large numbers of poly-lines. The patch I provided does work as a workaround, but again the optimal solution is to move away from JSON serialization in the render loop entirely.

@zacps
Since this issue is more than a year old and the plugin has gone through lot of updates, I suggest to try your use case using latest plugin version and see if you still get similar performance or that has improved.

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


Power Shell automation

Description

Checklist

[ ] This pull request was tested on both of:

[ ] PowerShell 5.1 (Windows)
[ ] PowerShell 6.x
[ ] PowerShell 7.x (Latest PowerShell)

[ ] Scripts do not contain static passwords or other secret tokens.
[ ] All Azure resource identifiers which must be universally unique are guaranteed to be so.

Testing information

Platform and PowerShell version: [pscustomobject]$PSVersionTable | Select-Object OS, BuildVersion, PSVersion
Az version: (Get-InstalledModule -Name Az).Version

#sign-off

@mikefrobbins to approve and merge.

Powershell spelled with no space between Power and Shell for folder name


Replace async arrow with function

Intern isn't happy with async arrows, we should follow up with a lint rule like we did with coalescent.

What's intern?


Post-Processing to Exclude Existing Text from Suggestions

Problem
Sometimes the model will return a completion that includes existing text. For example, asking for a suggestion in the middle of a sentence may return a completion with the first part of the sentence along with the suggestion.
Problem examples
User's prefix text is returned.

User's suffix text is returned, including <mask/>.

Solution
If existing text is returned, it should be removed before showing the suggestion to the user. While we could also give more robust instructions to the LLM, implementing this as a post-processing step will ensure it's caught every time, as it will not rely on the model's behaviour during generation and whether the LLM is following instructions properly.
Further Ideas
If a significant portion or the entirety of the suggestion consists of existing text (such as in the second example image), we could automatically trigger a retry and generate a new suggestion. This could be a clean, blind retry where the model has no knowledge of its mistake, or we could resend the previous prompt and the models completion, this time with an additional system message stating the problem with the first attempt. This would need some testing - we wouldn't want the model to apologise in the middle of its next suggestion!

This is indeed a throne in my sight. I indeed want this fix. However, the overlap detection remains rather tricky since there are often minimalistic differences that cause the naive overlap post processor not to work. I have some ideas I want to try out that might solve some issues. I should have some time for it next week.
I first want to try a more heuristic approach to avoid making too many API calls. However, we could do a similarity check to decide that a new generation is needed. However, that will be a last resort if the additional heuristic approaches don't work.
If you have a list of failure examples, please share them here so that I already have some test cases.


data/build: support MNIST, CIFAR10, and CIFAR-100

As well as the zipped variant for MNIST
original commit

PR has been created by mistake.
Those changes aren't mine. The original changes are from this commit


Fix typo in OMP_NESTED default value description

It previously referred to OMP_DYNAMIC

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