TypeError: Cannot read property ‘secretExists’ of undefined

We’re using User API key generated by NR user account.
this is how our serverless.yml is configured.
custom:
  newRelic:
    accountId: ${self:custom.config.environment.NEW_RELIC_ACCOUNT_ID}
    apiKey: ${self:custom.config.environment.NEW_RELIC_USER_KEY}
    enableExtension: true
    enableIntegration: true
    logEnabled: true

  provider:
    environment:
      NEW_RELIC_ACCOUNT_ID: ${self:custom.config.environment.NEW_RELIC_ACCOUNT_ID}
      NEW_RELIC_USER_KEY: ${self:custom.config.environment.NEW_RELIC_USER_KEY}
  plugins:
    - serverless-newrelic-lambda-layers

and this is config.prod.yml
  NEW_RELIC_ACCOUNT_ID: <our production user key>
  NEW_RELIC_USER_KEY: ${ssm:/NEW_RELIC_USER_KEY~true}

Build is failing on production with following error:
  TypeError: Cannot read property 'secretExists' of undefined

      at NewRelicLambdaLayerPlugin.<anonymous> (/codebuild/output/src058836924/src/node_modules/serverless-newrelic-lambda-layers/dist/index.js:142:34)

      at Generator.next (<anonymous>)

      at fulfilled (/codebuild/output/src058836924/src/node_modules/serverless-newrelic-lambda-layers/dist/index.js:5:58)

      at runNextTicks (internal/process/task_queues.js:59:5)

      at processImmediate (internal/timers.js:412:9)

      at process.topLevelDomainCallback (domain.js:130:23)

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

@harrythedev Try plugin version 3.1.0, which we've just released--this condition should be fixed.

@harrythedev If you need to revert to v2, the last version of that was 2.4.1. v3 of the plugin requires serverless v3, which had several breaking changes from serverless v2.


Dictionary-based logging using Coresight STM frontend and ETR on nrf54h20

PR adds support for dictionary-based logging using Coresight STM and ETR (embedded trace router).
PR contains:

Preparation changes:

creating logging/frontends directory and moving there frontend related files
Fix Kconfig dependency in logging Kconfig when using dictionary-based logging and string stripping.

Adding Coresight STMESP frontend (log_frontend_stmesp) to logging/frontends. Frontend is not nrf54h20 specific but data formatting  requires decoding tool which is nordic specific (nrfutil trace stm). Frontend has additional API for tracepoints. Tracepoint is a super fast way of tracing (log_frontend_stmesp_tp(x), log_frontend_stmesp_tp_d32(x, d32)). It's less flexible than logging but much faster (tracepoint is <0.1us vs ~0.7us for logging).
Adding DT nodes in nrf54h20 for STMESP (STM extended stimulus port) and TBM (Trace Buffer Monitor).
Adding ETR RAM buffer in nrf54h20dk memory map (may change in the future).
Adding soc/nordic/common/coresight_etr_tbm.c module which dumps ETR data (generated by STMESP frontend) over UART. It is nordic specific because it is using nordic peripheral (Trace Buffer Monitor - TBM) to get busyness of the ETR buffer. It runs on cpuapp.
Adding nordic-log-stm-dict snippet for enabling dictionary-based logging using STMESP frontend
Adding a sample which demonstrates performance of the logging with Coresight STM. Sample is using sysbuild and runs on app and rad cores.

DNM since official SDFW and appropriate version of nrfutil trace stm are not yet ready.

#72476 contains all commits from this PR.


Add draft RFC for using Paketo stacks in CF Deployment

For easier viewing: https://github.com/cloudfoundry/community/blob/rfc_paketo_stacks/toc/rfc/rfc-draft-add-paketo-stacks.md
cc @robdimsdale, @dsabeti, @dsboulder, @sophiewigmore, @geofffranks

With the Remove Stacks & Mixins RFC as well as the work on Extensions close to being done - I wonder how long an integration of Cloud Native Buildpacks that separates stacks from droplets can carry us.
I agree with the Add Cloud Native Buildpacks RFC focusing on quick evaluation. Wrapping Cloud Native Buildpacks in a v2 API that produces droplets that can be run on top of a Cloud Foundry stack enables applications with minimal or no change in Cloud Foundry at all. This will enable our community to check the Paketo buildpacks for compatibility and will enable us to improve that to the point of getting feasible for applications to consider switching over.
I do believe that any step further should take into account how Cloud Native Buildpacks work and are packaged. The most feasible thing to deliver and control for a platform seems to be Cloud Native Builders - combining root file systems and buildpacks. Indeed, the new use cases enabled with Extensions will likely only be available when we take this into account.
Given that the cflinuxfs4 and Paketo Full Stack are likely very similar if not identical - I would hope that for the early phase of discovery we don't need a Paketo specific Cloud Foundry Stack. As I tried to picture above, I don't think that we should have a Paketo specific Cloud Foundry Stack for anything beyond.
FWIW Keeping the separation could lead to the Paketo project non being able to leverage the full potential of changes in the Cloud Native Buildpack ecosystem.

Given that the cflinuxfs4 and Paketo Full Stack are likely very similar if not identical - I would hope that for the early phase of discovery we don't need a Paketo specific Cloud Foundry Stack. As I tried to picture above, I don't think that we should have a Paketo specific Cloud Foundry Stack for anything beyond.

We explored this and unfortunately they're not identical. For example the CF stacks require a vcap user, but the Paketo stacks use cnb user. Either we provide both users in the Paketo stacks, or we make separate stacks.

FWIW Keeping the separation could lead to the Paketo project non being able to leverage the full potential of changes in the Cloud Native Buildpack ecosystem.

I assume this is meant to read:
Keeping the separation could lead to the Cloud Foundry project non being able to leverage the full potential of changes in the Cloud Native Buildpack ecosystem.

My reading of this is that if CF doesn't implement the CNB specification properly, then Paketo may get caught in a situation where they can't incorporate newer versions of the CNB specification without breaking CF.

My reading of this is that if CF doesn't implement the CNB specification properly, then Paketo may get caught in a situation where they can't incorporate newer versions of the CNB specification without breaking CF.

Exactly @Gerg.

Ah ok, thanks. I made a few assumptions that lead me to not consider much risk to Paketo:

We would have to maintain separate stacks (for the different users mentioned above)
We wouldn't maintain separate buildpacks, nor would we make CNB-incompatible changes to the buildpacks
The concept of a builder wouldn't exist in CF, because there is already a mechanism for bridging stacks and buildpacks

In this RFC we have some open questions and looks to me like we need to discuss those during a meeting. At leats this is my personal opinion. Looking into the schedule for working group updates for the TOC the ARI WG is scheduled at the moment for the 3rd of October. If you think that we need a live discussion would that be an option? Or are there any other suggestions?

I need to do a deeper reading of the CNB platform specification, which I haven't had a chance to yet. I'm going on vacation for a couple weeks, but I hope to re-engage with this RFC when I return.
At that point @ryanmoran may be back from leave as well, and he may have some to contribute.

The current scheduled for the ARI WG update during the TOC meeting is 26th of September. @Gerg I think it makes sense to add this RFC as discussion point for that meeting. Do you think it is a good idea? If yes, we can announce it here, so that who ever is interested can join the discussion.

I'm going to retract this RFC PR for now. I appreciate everyone who has contributed to it up to this point and provided sharp and thoughtful feedback. To move this effort forward, I think it will require a substantial re-working of the proposal, and this area unfortunately hasn't been a focus for me recently.
If anyone is interested in trying out Paketo stacks on CF, I believe there are sufficient hooks in place today to add a custom Paketo Stack, even if it isn't formally integrated into CF Deployment. If anyone is interested, I'd be happy to chat more about this on Slack.
If there is continued interest in this area, I hope to eventually submit a successor RFC that better integrates with the CNB specification, or at least justifies intentional non-integration with the spec.


Span & ReadOnlyMemory

Please concider using .net core Span<> and ReadOnlyMemory<> and avoiding using calls to C malloc, alloc and free where possible thus avoiding pointer and memory leak issues.

this would break the compatibility with netfx and interoperability with other ecosystems (e.g. python) -- ideally, a cell buffer allocated from .NET Core could be passed over to foreign runtimes.

@yatli For Span and Memory you just need to reference https://www.nuget.org/packages/System.Memory/ and you can keep netfx support btw.

Update: to clarify this, many raw pointers come from lower level C code directly and is not owned by the .NET runtime. We'd like to pass them freely between runtimes, and thus adopt commonly accessible routines for memory management.


all packs in Float at 54V, only BatteryAggregator is at 55.2V and dont reduce the CVL

To provide a debug log, use dbus-spy to change the D-Bus path /LogLevel for the BatteryAggregator to DEBUG. Log location is /var/log/BatteryAggregator/current.

Hello,
i use v3.0.57. My System had 4x16 Cells with JKBMS in parallel.
Aggregator is always at 55.2V, all packs are now in float.
Sometimes after reboot one of the packs has no CVL in the parameters.
Thanks a lot and greetings
Kristian
Here is the log.
@40000000663df5290f073c94 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyUSB3: C4} now has values {'com.victronenergy.battery.ttyUSB4': 'C1', 'com.victronenergy.battery.ttyUSB5': None, 'com.victronenergy.battery.ttyUSB1': 'C5', dbus.String('com.victronenergy.battery.ttyUSB3'): 'C4'} with result C5
@40000000663df52934fa957c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB4 /Dc/0/Voltage 55.37
@40000000663df5293511f1f4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyUSB4: 55.37} now has values {'com.victronenergy.battery.ttyUSB4': 55.37, 'com.victronenergy.battery.ttyUSB5': 55.37, 'com.victronenergy.battery.ttyUSB1': 55.37, dbus.String('com.victronenergy.battery.ttyUSB3'): 55.36} with result 55.36749999999999
@40000000663df529353fe794 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB4 /Dc/0/Power 105.76
@40000000663df529354eef3c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyUSB4: 105.76} now has values {'com.victronenergy.battery.ttyUSB4': 105.76, 'com.victronenergy.battery.ttyUSB5': -89.7, 'com.victronenergy.battery.ttyUSB1': 105.76, dbus.String('com.victronenergy.battery.ttyUSB3'): 100.76} with result 222.58
@40000000663df52935747c84 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB4 /System/MinVoltageCellId C4
@40000000663df529357c0a1c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinVoltageCellId updated with {com.victronenergy.battery.ttyUSB4: C4} now has values {'com.victronenergy.battery.ttyUSB4': 'C4', 'com.victronenergy.battery.ttyUSB5': None, 'com.victronenergy.battery.ttyUSB1': 'C9', dbus.String('com.victronenergy.battery.ttyUSB3'): 'C6'} with result C4
@40000000663df52937289cf4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB1 /Dc/0/Current 2.13
@40000000663df529372c13ac DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyUSB1: 2.13} now has values {'com.victronenergy.battery.ttyUSB4': 1.91, 'com.victronenergy.battery.ttyUSB5': -1.62, 'com.victronenergy.battery.ttyUSB1': 2.13, dbus.String('com.victronenergy.battery.ttyUSB3'): 1.82} with result 4.24
@40000000663df52937498aa4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB1 /Dc/0/Power 117.94
@40000000663df5293752a2c4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyUSB1: 117.94} now has values {'com.victronenergy.battery.ttyUSB4': 105.76, 'com.victronenergy.battery.ttyUSB5': -89.7, 'com.victronenergy.battery.ttyUSB1': 117.94, dbus.String('com.victronenergy.battery.ttyUSB3'): 100.76} with result 234.76
@40000000663df5293793c2a4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB1 /System/MaxVoltageCellId C3
@40000000663df529379b486c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyUSB1: C3} now has values {'com.victronenergy.battery.ttyUSB4': 'C1', 'com.victronenergy.battery.ttyUSB5': None, 'com.victronenergy.battery.ttyUSB1': 'C3', dbus.String('com.victronenergy.battery.ttyUSB3'): 'C4'} with result C4
@40000000663df52937b767a4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB1 /System/MaxCellVoltage 3.464
@40000000663df52937c25c54 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyUSB1: 3.464} now has values {'com.victronenergy.battery.ttyUSB4': 3.461, 'com.victronenergy.battery.ttyUSB5': None, 'com.victronenergy.battery.ttyUSB1': 3.464, dbus.String('com.victronenergy.battery.ttyUSB3'): 3.462} with result 3.464
@40000000663df52a0db4339c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB3 /Dc/0/Current -1.82
@40000000663df52a0dd6ee3c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Current updated with {com.victronenergy.battery.ttyUSB3: -1.82} now has values {'com.victronenergy.battery.ttyUSB4': 1.91, 'com.victronenergy.battery.ttyUSB5': -1.62, 'com.victronenergy.battery.ttyUSB1': 2.13, dbus.String('com.victronenergy.battery.ttyUSB3'): -1.82} with result 0.5999999999999999
@40000000663df52a0e60c364 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB3 /Dc/0/Power -100.76
@40000000663df52a0e68aad4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyUSB3: -100.76} now has values {'com.victronenergy.battery.ttyUSB4': 105.76, 'com.victronenergy.battery.ttyUSB5': -89.7, 'com.victronenergy.battery.ttyUSB1': 117.94, dbus.String('com.victronenergy.battery.ttyUSB3'): -100.76} with result 33.239999999999995
@40000000663df52a0e9521a4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB3 /System/MaxVoltageCellId C7
@40000000663df52a0ecfd4fc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyUSB3: C7} now has values {'com.victronenergy.battery.ttyUSB4': 'C1', 'com.victronenergy.battery.ttyUSB5': None, 'com.victronenergy.battery.ttyUSB1': 'C3', dbus.String('com.victronenergy.battery.ttyUSB3'): 'C7'} with result C7
@40000000663df52a1695ab6c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB5 /Dc/0/Voltage 55.38
@40000000663df52a16ad3e94 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyUSB5: 55.38} now has values {'com.victronenergy.battery.ttyUSB4': 55.37, 'com.victronenergy.battery.ttyUSB5': 55.38, 'com.victronenergy.battery.ttyUSB1': 55.37, dbus.String('com.victronenergy.battery.ttyUSB3'): 55.36} with result 55.370000000000005
@40000000663df52a16bba614 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB5 /Dc/0/Power -89.72
@40000000663df52a16c2511c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyUSB5: -89.72} now has values {'com.victronenergy.battery.ttyUSB4': 105.76, 'com.victronenergy.battery.ttyUSB5': -89.72, 'com.victronenergy.battery.ttyUSB1': 117.94, dbus.String('com.victronenergy.battery.ttyUSB3'): -100.76} with result 33.22000000000001
@40000000663df52a3514ad2c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB4 /Dc/0/Voltage 55.36
@40000000663df52a3514cc6c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Voltage updated with {com.victronenergy.battery.ttyUSB4: 55.36} now has values {'com.victronenergy.battery.ttyUSB4': 55.36, 'com.victronenergy.battery.ttyUSB5': 55.38, 'com.victronenergy.battery.ttyUSB1': 55.37, dbus.String('com.victronenergy.battery.ttyUSB3'): 55.36} with result 55.36750000000001
@40000000663df52a35765cfc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB4 /Dc/0/Power 105.74
@40000000663df52a3576746c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /Dc/0/Power updated with {com.victronenergy.battery.ttyUSB4: 105.74} now has values {'com.victronenergy.battery.ttyUSB4': 105.74, 'com.victronenergy.battery.ttyUSB5': -89.72, 'com.victronenergy.battery.ttyUSB1': 117.94, dbus.String('com.victronenergy.battery.ttyUSB3'): -100.76} with result 33.199999999999974
@40000000663df52a359eff54 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB4 /System/MinVoltageCellId C3
@40000000663df52a35b20e3c DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MinVoltageCellId updated with {com.victronenergy.battery.ttyUSB4: C3} now has values {'com.victronenergy.battery.ttyUSB4': 'C3', 'com.victronenergy.battery.ttyUSB5': None, 'com.victronenergy.battery.ttyUSB1': 'C9', dbus.String('com.victronenergy.battery.ttyUSB3'): 'C6'} with result C3
@40000000663df52a35dbdd5c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB4 /System/MaxVoltageCellId C7
@40000000663df52a35edabf4 DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxVoltageCellId updated with {com.victronenergy.battery.ttyUSB4: C7} now has values {'com.victronenergy.battery.ttyUSB4': 'C7', 'com.victronenergy.battery.ttyUSB5': None, 'com.victronenergy.battery.ttyUSB1': 'C3', dbus.String('com.victronenergy.battery.ttyUSB3'): 'C7'} with result C7
@40000000663df52a36278c5c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB4 /System/MaxCellVoltage 3.462
@40000000663df52a363ba8cc DEBUG:com.victronenergy.battery.aggregator:Aggregator for /System/MaxCellVoltage updated with {com.victronenergy.battery.ttyUSB4: 3.462} now has values {'com.victronenergy.battery.ttyUSB4': 3.462, 'com.victronenergy.battery.ttyUSB5': None, 'com.victronenergy.battery.ttyUSB1': 3.464, dbus.String('com.victronenergy.battery.ttyUSB3'): 3.462} with result 3.464

Can you include some screen shots to show exactly what you mean, please.

Hello,
thanks for your answer.
Since downgrade to v3.0.52 all is perfect.
Also tested on a 12V Victron Setup, the same.
so i need actual no more help.
Thanks a lot and greetings
Kristian

Just to verify, are you saying v3.0.57 does not work, but v3.0.52 does? Somewhat ironically, v3.0.57 contains support for DVCC, but it seems to have caused you issues. I may look into adding a config option to disable DVCC support in BatteryAggregator then.


Don't show the play button when there is no preview_url

When there is no preview_url, e.g. it is null, don't show the play button.

Implemented


GIFs playing too fast on iOS

Describe the bug
The GIF plays at a much quicker speed than expected. React Native's Image seems to have fixed this and played the GIF at normal speed. RN-fast-image is able to preload and cache the GIF correctly, it is just played at ~3x speed.
To Reproduce
Steps to reproduce the behavior if possible, or a link to a reproduction repo:

Use React Native Fast Image to display a GIF via URL

Dependency versions

React Native version: 0.69.6
React version: 18.0.0
React Native Fast Image version: 8.6.1

Note: if these are not the latest versions of each I recommend updating as extra effort will not be taken to be backwards compatible, and updating might resolving your issue.

Issue confirmed, only happening with FastImage.
If you ever find a solution @jbernar3 can you share it here?
I will as well

The same issue on iOS. On some new devices, the animated webp plays too fast. However, it works normally on most devices. Any fixes on that?

lock SDWebImage version up to 5.15.5 at  file node_modules/react-native-fast-image/RNFastImage.podspec

Any updates? I have the same problem, I locked SDWebImage and it doesn't help

Still happening

issue still happening

still happening. please look into


Logging over several days

My test .NET console application stopped sending logs to elastic search at midnight. Is there any setting that has to be configured to be able to log over several days ? Is there any internal container limitation in elasticsearch that can be influenced over the elasticsearch sink parameters  (my test application sends a log to elasticsearch every 100 msec)? In the application no special parameters were set at configuring the elasticsearch sink:
.WriteTo.Elasticsearch(new ElasticsearchSinkOptions(new Uri("http://localhost:9200"))
{
    AutoRegisterTemplate = true
}

It should already send log data over multiple days, however, by default it will create a new index for this new day. So do you see a new index appear?

You are right, thanks! The indexes were available in the kibana "management" view, I just had to add the new index patterns for the missing days. It was not obvious to me, I am doing the first learning steps with elasticsearch/kibana,..
But nevertheless, is there any size limitation for logging with serilog to elasticsearch ? I have an use-case where hundreds of logs received as tcpip messages from an embedded system approx. every 50 milliseconds should be logged to elasticsearch. The requirement is to keep the logs for the last 30 days, that means a kind of serilog rolling files functionality, but with elasticsearch. What would be the right configuration/approach for such a scenario? Does the serilog elasticsearch sink support a "batch" functionality, to send several logs at once to elasticsearch?

There is no size limitation in the sink, there might be a limit in your ES setup. You have to be careful in setting up your shards and replicas for sure.
The sink will batch by default. So it will collect 50 logevents or wait 2 seconds before flushing. This is configurable. The batch operation is a single http call with all the operations to be performed against ES.
Keeping retention is something you need to handle yourself. Look for the elasticsearch curator tooling. As we store events per day in a separate index, it is very easy to remove days by simply deleting indexes or to search in only the last week (using an alias specifying the set of indexes).
If you want more resiliency, then write your events as quickly as possible to a queue instead and use for example logstash to turn those events into ES.
hope this helps

Thanks for the detailed answer. Is the functionality of rolling the elasticsearch indices (to keep the logs for lets say the last 10 days) implemented inside the serilog elasticsearch sink, or can be configured in elasticsearch? I mean the creation of a new index when a new day starts, the removal of the oldest index when the max.number of rolling indices is reached.

Cleaning up indexes is something you need to do outside the sink and ES. But basically, it is a matter of deleting the daily index based on a pattern. ES has a tool called Curator for this: https://www.elastic.co/guide/en/elasticsearch/client/curator/current/about.html
The creation of a new index happens due to the index name we use. So for each event we pass it through a function that returns the name based on the timestamp. By default it will use a daily pattern and as such create a new index the next day. You can alter this behaviour and return a name with only a year and month in it. But your index will be large and normally you will only want to find events for the last day or even shorter.

Thank you for the information. Is it possible to configure serilog in such a way that all daily indices are stored in the same shard? Or at least for a group of daily indices. The actual implementation allocates a new shard for each daily index.

Nothing in Serilog or the sink itself that can do that, but use tooling like Curator or simply the ES API to do so. Changing shard size is not a simple thing to do btw as you need to rewrite the index (an index consist of one or more shards). But you can configure ES to move older indices to slower storage for example.


Support autolinked references (issue, PR, commit shorthands)

They're all listed in the Github documentation here

Where do you want these to be supported (code editor, comments, review overview)?

All three! But it occurs to me that code editor support could produce false positives, so that should have a user setting

We used to support issues and PRs links in the editor, but it was to slow so we removed it.
Issue and PR links are already supported in the overview.

Do hovers still exist? I can't make them appear, see relevant settings, or find associated documentation 😓

Documentation is here: https://github.com/microsoft/vscode-pull-request-github/blob/main/documentation/IssueFeatures.md
It's a little out of date. I will try to update it soon!

Thanks for the reference 🙏🏼 From that list I don't get the code action to create an issue or completions or hovers for issues. I'm authenticated and working on my forked origin with issues disable and the upstream original repo properly configured. Am I missing something? Are you aware of a related issue already?

@texastoland those are all still working well for me. Can you please open a new issue for these and add some screenshots or gifs of things that you are not seeing work?

I can! A video of them ... not appearing? Should the file type (ex. F#) matter?

We pay attention to file type for some features, but it shouldn't matter for any of the features that you've listed.

microsoft/vscode-pull-request-github#1858
microsoft/vscode#99356

Sorry to spam this issue! I'd also like to propose a different default query for autocomplete. Otherwise it isn't discoverable in typical open source workflows where no one is ever assigned. Is that worth a separate ticket or already discussed and decided?

We now have more things linkified in comments.


[REQ] Bloxstrap Verified System

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
So, you see, there's this cool idea which is basically useless but would like for to be around, there's an FFlag that allows you to whitelist people as verified, and you see them as verified with the verified symbol from video stars, what if it sent a request to a github repo let's say before entering roblox and sets it in the clientsettings.json with all the ids from the github repo? (so that it's updated no matter what) and people can be verified with everyone using Bloxstrap seeing them as verified? I know this is useless but I wanted somewhere to put my idea in, I don't think this is a good idea and it would ruin the entire purpose of verifying, maybe if you added a few walls, like using it only for identifying people that are important in the community.
Anyways, enough yapping, this is the FFlag: "FStringWhitelistVerifiedUserId": "1",

no


YouTube fullscreen freezes flobro

Describe the bug
When you click the fullscreen icon of a YouTube video, Flobro freezes and becomes unusable.
Steps to reproduce
Steps to reproduce the behavior:

Enter YouTube embed URL in Flobro: https://www.youtube.com/embed/cgirVaJo42g?autoplay=1&cc_load_policy=3&iv_load_policy=3
While video is playing, click the fullscreen icon at the bottom right.

Expected behavior
Video playing in fullscreen
Please complete the following information:

OS: macOS Mojave 10.14.1
Version 0.1.2

Can't reproduce


Bug in sfm/utils/alignment.hpp - applyTransform - also control points must be transformed

The code is as follows:
  for(auto& view: sfmData.views)
  {
    geometry::Pose3& pose = sfmData.poses[view.second->id_pose];
    pose = pose.transformSRt(S, R, t);
  }

If the same pose is referenced by multiple views, it will be transformed multiple times, leading to incorrect end result.

not a bug, there is no shared poses

the real bug is that the control points are not transformed

The best would be to use openMVG::sfm::ApplySimilaritythat will do the job
https://github.com/openMVG/openMVG/blob/master/src/openMVG/sfm/sfm_data_transform.hpp#L23

great more duplicated code... :-)
And with the same bug... the control points should be transformed as well, shouldn't they?

Yes ControlPoints was not transformed, since they are often linked to a static SRS (Spatial Reference System).As discussed in another thread, an option will come in a future update to make the control point transformed or not.

ok i added the boolean.
I think we added the same function at almost the same time :-)


Clean up activity code and get 100% coverage.

ec8baa70aee2f64923446f4c2bf50a703a64dc90 LGTM
d19059970e9de7b07c82e8ad3fc690908c880d06 LGTM
4af280a83e93df106769382c164ee3c7788c68e9 LGTM
b16a77de8beb462bdcd0431709890f37291269ef LGTM
I'm not 100% sure of cd9b57721cff87001c661224a9b813bc4e0a4b44.

This looks great, merged, thanks @showell!  For reference, the comment removed in the first commit was meant to apply to the inititialize function (aka the line above), not the line below, so was more in the wrong place than inaccurate :)

Cool, that make sense re:the comment.  I should eventually document in a more general way how we sometimes expose methods in the JS code to help make code more testable.


mgDiagSettingsAll module sample PowerShell script structure is inconsistent with others

What happened? Provide a clear and concise description of the bug, including deployment details.
Other PowerShell scripts define an InputObject and then call the deployment cmdlet with that single InputObject as a parameter. This module puts the cmdlet's parameters inline.
Please provide the correlation id associated with your error or bug.
No response
What was the expected outcome?
No response
Relevant log output
No response
Check previous GitHub issues

[X] I have searched the issues for this item and found no duplicate

Code of Conduct

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

Hey @SvenAelterman, I'm working on a PR to align this with the rest of the modules. Thanks for the callout.


Cow: Watch restoredharvest.com

Cow requests the watch of the watch_keyword restoredharvest\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

restoredharvest\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


fix: update pyhton dependencies

:tada: This PR is included in version 2.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add link to Data is Plural newsletter, somewhere

Hey there!
Love this resource.
I think it would be great to add a link to @jsvine's Data is Plural newsletter (and archives). It was recently posted to DataTau. But I'm opening an Issue rather than a PR, because I'm not sure where to put it. Maybe you have an idea, @caesar0301 ?

Thanks, @hangtwenty :^)


[WIP] CI: Check formatting

This adds a CI check to verify the formatting is correct, and adds an esy format command to run refmt against all the files in the repo.

Thanks for the idea @jchavarri ! husky would be a nice way to enforce this - either as a precommit/prepush hook - would save some time across the board 😄
Unfortunately it looks like there are issues integrating husky with esy at the moment: https://github.com/esy/esy/issues/623

Ah, cool didn't know. Thanks @bryphe for pointing me to that issue! 🙂


Segmentation fault when using h5py

📚 Installation
The install of the packages seem fine. But I get a Segmentation fault with no additional information when doing:
import h5py; from torch_geometric.data import Dataset
Importing h5py on its own or Dataset on its own works fine, only in combination I get a SegFault.
Environment

OS: CentOS 7.6.1810
Python version: 3.8.3
PyTorch version: 1.6.0
CUDA/cuDNN version: 10.2
GCC version: 8.3.0
How did you try to install PyTorch Geometric and its extensions (wheel, source): source
Any other relevant information:

Checklist

[x ] I followed the installation guide.
[x ] I cannot find my error message in the FAQ.
[ x] I set up CUDA correctly and can compile CUDA code via nvcc.
[ ] I do have multiple CUDA versions on my machine.

Which version of h5py are you using? Maybe you can downgrade it and see if the error disappears.

I am using 2.10.0 and tried downgrading to 2.7.x, but without success. I just discovered however that explicitly including
import sklearn
anywhere in the code (e.g. at the top of the executable) fixes the Segmentation fault.


netopeer doesn't support server private keys besides "rsa" and "secp"

Hello!
When trying to connect via TLS to server which has x25519 private key, in logs I see Unknown private key algorithm "x25519"
In netopeer2 sources (https://github.com/CESNET/netopeer2/blob/master/src/netconf_server.c#L53):
    /* set algorithm */
    if (!strncmp(alg->value.ident->name, "rsa", 3)) {
        *privkey_type = NC_SSH_KEY_RSA;
    } else if (!strncmp(alg->value.ident->name, "secp", 4)) {
        *privkey_type = NC_SSH_KEY_ECDSA;
    } else {
        ERR("Unknown private key algorithm \"%s\".", lyd_get_value(&alg->node));
        return -1;
    }

So, netopeer doesn't support server private keys besides "rsa" and "secp".
But x25519 and x448 algorithms are presented in ietf-crypto-types.yang:
        enum "x25519" {
          value 12;
          description
            "The asymmetric algorithm using a x.25519 Curve.";
          reference
            "RFC 7748:
               Elliptic Curves for Security.";
        }
        enum "x448" {
          value 13;
          description
            "The asymmetric algorithm using a x.448 Curve.";
          reference
            "RFC 7748:
               Elliptic Curves for Security.";
        })

And as I tested - sysrepocfg accept them without errors when I change <algorithm> in ietf-keystore module
Is it a bug?
--
Regards,
Alexander

Ok, thank you!
Btw, could you tell me if secp192r1, secp224r1, secp256r1 algorithms are supported?
At least I tried secp224r1 - it doesn't connect, handshake failure; in logs:
netopeer2-server: [ERR]: LN: SSL_accept failed (no shared cipher)
But I tried secp384r1 and secp521r1 algorithms - they work well (connection is established)

Btw, could you tell me if secp192r1, secp224r1, secp256r1 algorithms are supported?

I do not know many details, it is left up to OpenSSL. The error seems to indicate that the server/client does not accept the shorter key variants because of security, probably. Our server nor the CLI do not support explicit configuration of the accepted key algorithms, which is probably what would be required for the keys to be accepted.

Ok
I'd also like to know about an error netopeer2-server: [ERR]: LN: SSL_accept timeout. when using rsa15360 server private key.
It connects really long time when using it.
Is it also because of openssl?

Probably, I have never used such a long key and it is all handled internally by OpenSSL anyway, so I cannot tell you anything more about this.

ok, thank you


iosevka-comfy: 1.0.0 -> 1.1.1

Description of changes
https://github.com/protesilaos/iosevka-comfy/releases/tag/1.1.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 197496 run on x86_64-linux 1

9 packages built:

iosevka-comfy.comfy
iosevka-comfy.comfy-duo
iosevka-comfy.comfy-fixed
iosevka-comfy.comfy-motion
iosevka-comfy.comfy-motion-duo
iosevka-comfy.comfy-motion-fixed
iosevka-comfy.comfy-wide
iosevka-comfy.comfy-wide-duo
iosevka-comfy.comfy-wide-fixed

LGTM

No reason. Merging. Thank you for your review @romildo.


Downloading 'bridge' Dataset using tfds-nightly

Hello,
I am encountering an issue while trying to download the bridge dataset using TensorFlow Datasets (TFDS). I am currently using tfds-nightly version 4.9.3.dev202311230044.
Issue Description
When I attempt to load the 'bridge' dataset with the following code:
import tensorflow_datasets as tfds
tfds.load('bridge', data_dir="mypath/“)

I receive an error indicating that the dataset cannot be downloaded.
In addition to the issue described above, I am considering the possibility of manually downloading the dataset from the following URL:
https://rail.eecs.berkeley.edu/datasets/bridge_release/data/tfds/bridge_dataset/1.0.0/
Before I proceed with this approach, I have a few questions:

Is manually downloading the dataset from this URL a recommended solution to the problem I am experiencing?

Will manually downloaded data integrate seamlessly with the TensorFlow Datasets API, or are there additional steps required to ensure compatibility?

Any guidance or suggestions regarding manual downloading would be greatly appreciated.
Thank you!

Raise the issue to tfds team here https://github.com/tensorflow/datasets/issues/5170

Hi @kpertsch , thank you for your suggestion. I would like to confirm, if I use the command gsutil -m cp -r gs://gresearch/robotics/bridge/0.1.0 /mypath/, does it download the latest bridge v2 data?

Perfect, the Bridge v2 dataset is exactly what I need. Additionally, could you please explain what is meant by "lacks the additional camera streams"? Does this refer to a lack of image or video data?

Thank you for your patient response! I look forward to your updates, and for now, I will start with a single camera stream.


Use internal path for plugins

Changed the way default plugins are referred in kitchenSink to match JSPM way.  (optional).

Great idea.


Unexpected behaviour with poll and tickless scheduler

Hello,
I'm using poll in conjunction with timerfds and the POLLIN event to schedule actions at different rates. I'm finding that when  CONFIG_SCHED_TICKLESS is used, poll is returning with only a subset of my file descriptors in revents field, even though I'm specifying the timeout to occur at the same time.
Here's a working example which demonstrates the issue, in which I:

Setup 8 timer file descriptors to have their first expiry after 3 seconds, and then expire at a 1 second rate.
Poll continuously for POLLIN events.
Report the expired events and print which fds expired as a hex value.

#include <stdio.h>
#include <errno.h>
#include <stdlib.h>
#include <poll.h>
#include <sys/timerfd.h>
#include <stdint.h>
#include <unistd.h>

#define TIMERFD_COUNT 8

static int fds[TIMERFD_COUNT] = {-1};

int create_timers(void)
{
  struct itimerspec its;

  clock_gettime(CLOCK_MONOTONIC, &its.it_value);

  // Set initial alarm for 3 seconds in the future
  its.it_value.tv_sec += 3;
  its.it_value.tv_nsec = 0;

  // Set interval to 1 second
  its.it_interval.tv_sec = 1;
  its.it_interval.tv_nsec = 0;

  for(int i = 0; i < TIMERFD_COUNT; i++)
  {
    fds[i] = timerfd_create(CLOCK_MONOTONIC, TFD_CLOEXEC);
    if(fds[i] < 0)
    {
      return fds[i];
    }

    if (timerfd_settime(fds[i], TFD_TIMER_ABSTIME, &its, NULL) < 0)
    {
      return errno;
    }
  }

  return 0;
}

void cleanup(void)
{
  for(int i = 0; i < TIMERFD_COUNT; i++)
  {
    if(fds[i] > 0)
    {
      close(fds[i]);
    }
  }
}

void timer_read(int fd)
{
  uint64_t expirations;
  read(fd, &expirations, sizeof(expirations));
}

size_t wait(void)
{
  struct pollfd pfds[TIMERFD_COUNT];
  const int timeout_ms = 10000;
  int ret;
  size_t mask = 0;

  for(int i = 0; i < TIMERFD_COUNT; i++)
  {
    pfds[i].fd = fds[i];
    pfds[i].events = POLLIN;
  }

  ret = poll(pfds, TIMERFD_COUNT, timeout_ms);
  if(ret < 0)
  {
    exit(EXIT_FAILURE);
  }

  for (int i = 0; i < TIMERFD_COUNT; i++)
  {
    if (pfds[i].revents == POLLIN)
    {
      mask |= (1 << i);
      timer_read(pfds[i].fd);
    }
  }
  return mask;
}

int main(int argc, char *argv[])
{
  size_t mask;
  int ret = create_timers();
  atexit(cleanup);

  if(ret < 0)
  {
    printf("Cannot create timers: %d\n", ret);
    exit(EXIT_FAILURE);
  }

  printf("Start poll\n");
  while(1)
  {
    mask = wait();
    printf("mask 0x%zX\n", mask);
  }

  exit(EXIT_SUCCESS);
}

Expected output.
I've tried the following example on the following platforms:

Linux: with gcc poll_test_main.c -o poll_test && ./poll_test
sim:nsh with CONFIG_TIMER_FD added.
qemu-rv:knsh32
arty_a7:knsh

In each case I get:
nsh> poll
Start poll
mask 0xFF
mask 0xFF
mask 0xFF
mask 0xFF
mask 0xFF
mask 0xFF
mask 0xFF

Which is what I am expecting.
However, when I use a tickless scheduler, such as:

qemu-armv8a:nsh_smp_tickless
arty_a7:knsh-tickless

I get the following:
nsh> poll
Start poll
mask 0x80
mask 0x70
mask 0xF
mask 0x80
mask 0x70
mask 0xF
mask 0x80
mask 0x70
mask 0xF
mask 0x80
mask 0x78
mask 0x7

In this case poll needs to be called 2-3 times for all expiry events to be returned. It doesn't seem to miss any events, they just are not all returned at the same time.
I haven't looked into this too much yet, but I feel like the underlying cause may also be what is causing the issue in #9840.
If there's any interest, I can add this example program, as well as any additions needed to the mentioned default configurations in our NuttX fork, to ease testing.
I would appreciate and feedback or suggestions.

I was able to test this out on the ESP32-C3 devkitc, same issue:
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x1 (POWERON),boot:0xc (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd5820,len:0x16c0
load:0x403cc710,len:0x87c
load:0x403ce710,len:0x2f54
entry 0x403cc710
I (30) boot: ESP-IDF v5.1-dev-3972-g1559b6309f 2nd stage bootloader
I (30) boot: compile time Mar 15 2023 12:14:06
I (31) boot: chip revision: v0.3
I (35) boot.esp32c3: SPI Speed      : 80MHz
I (40) boot.esp32c3: SPI Mode       : DIO
I (44) boot.esp32c3: SPI Flash Size : 4MB
I (49) boot: Enabling RNG early entropy source...
I (54) boot: Partition Table:
I (58) boot: ## Label            Usage          Type ST Offset   Length
I (65) boot:  0 factory          factory app      00 00 00010000 00100000
I (73) boot: End of partition table
I (77) esp_image: segment 0: paddr=00010020 vaddr=3c020020 size=0a41ch ( 42012) map
I (92) esp_image: segment 1: paddr=0001a444 vaddr=3fc83630 size=001c0h (   448) load
I (94) esp_image: segment 2: paddr=0001a60c vaddr=40380000 size=01a84h (  6788) load
I (103) esp_image: segment 3: paddr=0001c098 vaddr=00000000 size=04060h ( 16480)
I (113) esp_image: segment 4: paddr=00020100 vaddr=42000100 size=1bb98h (113560) map
I (137) boot: Loaded app from partition at offset 0x10000
I (137) boot: Disabling RNG early entropy source...

 Subsequent calls return less events.

@g2gps are you using Tickless mode with RR ?
Try to use CONFIG_RR_INTERVAL=200 for example and see if it improves the results. I think that in tickless mode each event itself is forcing the context switch and you are getting the preliminary mask instead of the complete bitmap set mask.

Thanks acassis, I just tried this out with the esp32c3-devkit:tickles configuration with,

CONFIG_RR_INTERVAL=0 (The default for this configuration)
CONFIG_RR_INTERVAL=20
CONFIG_RR_INTERVAL=200

In each case, I get a similar result.
I was having a look at vfs/fs_timerfd.c in timerfd_settime:
int timerfd_settime(int fd, int flags,
                    FAR const struct itimerspec *new_value,
                    FAR struct itimerspec *old_value)
{
  FAR struct timerfd_priv_s *dev;
  FAR struct file *filep;
  irqstate_t intflags;
  sclock_t delay;
  int ret;

  /* Some sanity checks */

  if (!new_value)
    {
      ret = -EFAULT;
      goto errout;
    }

  if ((flags & ~TFD_TIMER_ABSTIME) != 0)
    {
      ret = -EINVAL;
      goto errout;
    }

  /* Get file pointer by file descriptor */

  ret = fs_getfilep(fd, &filep);
  if (ret < 0)
    {
      goto errout;
    }

  /* Check fd come from us */

  if (!filep->f_inode || filep->f_inode->u.i_ops != &g_timerfd_fops)
    {
      ret = -EINVAL;
      goto errout;
    }

  dev = (FAR struct timerfd_priv_s *)filep->f_priv;

  /* Disable interrupts here to ensure that expiration counter is accessed
   * atomicaly.
   */

  intflags = enter_critical_section();

  if (old_value)
    {
      /* Get the number of ticks before the underlying watchdog expires */

      delay = wd_gettime(&dev->wdog);

      /* Convert that to a struct timespec and return it */

      clock_ticks2time(delay, &old_value->it_value);
      clock_ticks2time(dev->delay, &old_value->it_interval);
    }

  /* Disarm the timer (in case the timer was already armed when
   * timerfd_settime() is called).
   */

  wd_cancel(&dev->wdog);

  /* Clear expiration counter */

  dev->counter = 0;

  /* If the it_value member of value is zero, the timer will not be
   * re-armed
   */

  if (new_value->it_value.tv_sec <= 0 && new_value->it_value.tv_nsec <= 0)
    {
      leave_critical_section(intflags);
      return OK;
    }

  /* Setup up any repetitive timer */

  clock_time2ticks(&new_value->it_interval, &delay);
  dev->delay = delay;

  /* We need to disable timer interrupts through the following section so
   * that the system timer is stable.
   */

  /* Check if abstime is selected */

  if ((flags & TFD_TIMER_ABSTIME) != 0)
    {
      /* Calculate a delay corresponding to the absolute time in 'value' */

      clock_abstime2ticks(dev->clock, &new_value->it_value, &delay);
    }
  else
    {
      /* Calculate a delay assuming that 'value' holds the relative time
       * to wait.  We have internal knowledge that clock_time2ticks always
       * returns success.
       */

      clock_time2ticks(&new_value->it_value, &delay);
    }

  /* If the time is in the past or now, then set up the next interval
   * instead (assuming a repetitive timer).
   */

  if (delay <= 0)
    {
      delay = dev->delay;
    }

  /* Then start the watchdog */

  ret = wd_start(&dev->wdog, delay, timerfd_timeout, (wdparm_t)dev);
  if (ret < 0)
    {
      leave_critical_section(intflags);
      goto errout;
    }

  leave_critical_section(intflags);
  return OK;

errout:
  set_errno(-ret);
  return ERROR;
}

There would be finite time between when the number of ticks for the absolute time expiry is calculated, and when it's added to the list of activate watchdogs, in wd_start. Given that in tickless mode, the underlying timebase is till running, could this not cause the watchdog timeout tick to be sqewed?

Hi @g2gps, @acassis
I was able to get my hands on an stm32f4discovery and test it on that platform. Same issue. See below:
nsh> poll
Start poll
mask 0xE0
mask 0x1F
mask 0xE0
mask 0x1F
mask 0xE0
mask 0x1F
mask 0xE0
mask 0x1F
mask 0xE0
mask 0x1F

Thanks acassis, I just tried this out with the esp32c3-devkit:tickles configuration with,
* CONFIG_RR_INTERVAL=0 (The default for this configuration)

* CONFIG_RR_INTERVAL=20

* CONFIG_RR_INTERVAL=200

In each case, I get a similar result.
I was having a look at vfs/fs_timerfd.c in timerfd_settime:
int timerfd_settime(int fd, int flags,
                    FAR const struct itimerspec *new_value,
                    FAR struct itimerspec *old_value)
{
  FAR struct timerfd_priv_s *dev;
  FAR struct file *filep;
  irqstate_t intflags;
  sclock_t delay;
  int ret;

  /* Some sanity checks */

  if (!new_value)
    {
      ret = -EFAULT;
      goto errout;
    }

  if ((flags & ~TFD_TIMER_ABSTIME) != 0)
    {
      ret = -EINVAL;
      goto errout;
    }

  /* Get file pointer by file descriptor */

  ret = fs_getfilep(fd, &filep);
  if (ret < 0)
    {
      goto errout;
    }

  /* Check fd come from us */

  if (!filep->f_inode || filep->f_inode->u.i_ops != &g_timerfd_fops)
    {
      ret = -EINVAL;
      goto errout;
    }

  dev = (FAR struct timerfd_priv_s *)filep->f_priv;

  /* Disable interrupts here to ensure that expiration counter is accessed
   * atomicaly.
   */

  intflags = enter_critical_section();

  if (old_value)
    {
      /* Get the number of ticks before the underlying watchdog expires */

      delay = wd_gettime(&dev->wdog);

      /* Convert that to a struct timespec and return it */

      clock_ticks2time(delay, &old_value->it_value);
      clock_ticks2time(dev->delay, &old_value->it_interval);
    }

  /* Disarm the timer (in case the timer was already armed when
   * timerfd_settime() is called).
   */

  wd_cancel(&dev->wdog);

  /* Clear expiration counter */

  dev->counter = 0;

  /* If the it_value member of value is zero, the timer will not be
   * re-armed
   */

  if (new_value->it_value.tv_sec <= 0 && new_value->it_value.tv_nsec <= 0)
    {
      leave_critical_section(intflags);
      return OK;
    }

  /* Setup up any repetitive timer */

  clock_time2ticks(&new_value->it_interval, &delay);
  dev->delay = delay;

  /* We need to disable timer interrupts through the following section so
   * that the system timer is stable.
   */

  /* Check if abstime is selected */

  if ((flags & TFD_TIMER_ABSTIME) != 0)
    {
      /* Calculate a delay corresponding to the absolute time in 'value' */

      clock_abstime2ticks(dev->clock, &new_value->it_value, &delay);
    }
  else
    {
      /* Calculate a delay assuming that 'value' holds the relative time
       * to wait.  We have internal knowledge that clock_time2ticks always
       * returns success.
       */

      clock_time2ticks(&new_value->it_value, &delay);
    }

  /* If the time is in the past or now, then set up the next interval
   * instead (assuming a repetitive timer).
   */

  if (delay <= 0)
    {
      delay = dev->delay;
    }

  /* Then start the watchdog */

  ret = wd_start(&dev->wdog, delay, timerfd_timeout, (wdparm_t)dev);
  if (ret < 0)
    {
      leave_critical_section(intflags);
      goto errout;
    }

  leave_critical_section(intflags);
  return OK;

errout:
  set_errno(-ret);
  return ERROR;
}

There would be finite time between when the number of ticks for the absolute time expiry is calculated, and when it's added to the list of activate watchdogs, in wd_start. Given that in tickless mode, the underlying timebase is till running, could this not cause the watchdog timeout tick to be sqewed?

Yes, I think it could be the root cause!
@xiaoxiang781216 @patacongo @phfbertoleti any idea or suggestions how to fix it?

Hi @g2gps, @acassis
I was able to get my hands on an stm32f4discovery and test it on that platform. Same issue. See below:
nsh> poll
Start poll
mask 0xE0
mask 0x1F
mask 0xE0
mask 0x1F
mask 0xE0
mask 0x1F
mask 0xE0
mask 0x1F
mask 0xE0
mask 0x1F

@rtucker85 thank you for confirming!

@g2gps Have you tested this issue on latest master? I can't reproduce on qemu-armv8a:nsh_smp_tickless

I retested this today with NuttX main.
The issue is not present with qemu-armv8a:nsh_smp_tickless.  Although I still have the same failed result with the esp32c3-devkit:tickless and Litex based configuration.
If I checkout NuttX at 533ccb184736587b0915f928e2de79ccaf82d223, which was the current revision when this issue was reported, the test fails on qemu-armv8a:nsh_smp_tickless as well.
I'm going to have a quick look through to see if I can find any obvious changes specific to the arm64 port, which may have resolved this.  Perhaps someone else has some background here?

I've added a branch to our fork of nuttx-apps (https://github.com/motec-research/nuttx-apps/tree/issues/11189) and nuttx (https://github.com/motec-research/incubator-nuttx/tree/issues/11189). With the example program and configuration added. Hopefully it makes trying this out a bit easier.

I've found the cause of the issue. Both esp32c3 and the Litex port use the simple interval timer for tickless events. If I change the tickless implementation to support CONFIG_SCHED_TICKLESS_ALARM, poll works as expected.
I can push a PR for the Litex port once I get the implementation tidied up. However, I assume that this issue would still exist for other ports.


For a 0.1.8 release

#31

Codecov Report

Merging #32 (403ef67) into master (db5b4d6) will increase coverage by 0.06%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
+ Coverage   91.77%   91.84%   +0.06%
==========================================
  Files           7        7
  Lines         377      380       +3
==========================================
+ Hits          346      349       +3
  Misses         31       31

Impacted Files
Coverage Δ

src/methods.jl
80.76% <ø> (ø)

src/types.jl
96.29% <83.33%> (+0.10%)
:arrow_up:

Continue to review full report at Codecov.

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


Improve node scaling default

I see the issue.
Would you mind replacing{1.f,1.f,1.f} with Ogre::Vector3::UNIT_SCALE? It makes it more obvious that it is the default scale applied to the node (it's the same value; it just makes for cleaner code for the humans :wink: )

Since you left the edit opened for me, I pushed a commit to your branch. Once CI has ran and confirmed plugin still builds, I'll merge that.
Thanks a lot! :+1:


To-Do: Update Generated HTML

Update HTML template to utilize semantic html

The objective of this issue has been met


Need help with my card build, almost there but not quite.

I have built two cards and they both seem to have the same issue. I am not sure what is wrong. I have gone over them a few times. Reprogrammed the PAL and added the preload before adding the vga firmware. Both show similar screens via vga output. See screen shots. What am I missing?

Try and mash the reset key sequence a few times.  Normally on the 3rd try it will come up

I tried a couple times. I guess I should try more. You think thats all it is? Will this happen every time or just for the first initial boot?

Everytime from my experience. Using the older firmware I did not have any issues

Really? Thats not good at all. if thats the case I would be happy to try the older firmware. Which have you had the best luck with?

Try 20230406 version.  Had graphics issues in hires mode but seemed to boot first try.
Also if that don't work remove the PAL and jumper the board to just rule that out

20230406.zip
Here you go

Thank you mamejay! I will try this tomorrow. Can I just drop the new firmware on the cards or should I do the preload first?

I would do the pre-load first.  Always do just in case

Understood. Thank you again. Will post results tomorrow.

IF the old firmware mamejay doesnt have an affect I will try the nopal option next to see if the issues are the PAL's. Also I have been using the 4ns LC-VGA firmware (no wireless).

Ok I have an update. I tried what Mamejay said about mashing the restart buttons and it didnt do anything for one card it seems but the other gave me colored blocks.

Also this same card gave a different color line pattern if I did onboard diags check.

I ran the preload on both cards and then the old firmware and this is what I get on both cards now.

So what does this mean? My PAL's are not working? I can try the no pal next if you guys think that is the correct move.
Also here is a copy of the JED file I got as an output of WINCUPL, can you verify its correct?
PicoPal.zip
Also just want to note, I was using the 4ns LC VGA firmware initially when testing these cards.

The PAL and nopal jumper aren't needed for VGA only functionality. they enable the card to detect the slot-specific I/O accesses, but it will still see all writes regardless of the PAL or jumper being used. Usually when a card doesn't see bus activity it indicates the right most level shifter is installed wrong or bad. if it sees activity but it's corrupt or blank, that indicates one of the other shifters is the problem. Check that the dot on the chips indicating pin one is aligned with the longer white stripe on the silkscreen. The next versions of the card have clearer silkscreen markings for pin 1. Also check that there are no shorts between adjacent pins, or legs lifted preventing connection.

Thanks I did check and found no shorts. But I can check again.

I have just swapped out the lcx16245 ics. The one that works has toshiba TC74LCX16245 but I bought a roll of motorolla lcx16245 ics. I can not get the card to see bus activity and I am sure the ics are connected properly. Have you heard of this? I suppose I should buy more Toshiba TC74LCX16245 IC's.

Anyone have any ideas on this?

74LCX16245 is not the part used on my version of the board, and is a single-supply chip. If the board was designed for the dual-rail 74LVC16T245, it may be part of the problem.  The 74LCX16245 chips should only be supplied with 3.3V on all of the VCC inputs.  It would help to know which PCB you have.  Even without the PAL chip or jumper, the PHI signal and all address and data lines are passed to the PICO and you should get video. The cardselect lines are only needed for Z80 mode, and interacting with the config utility.

My apologies. I am using Hans Huebners fork. https://github.com/hanshuebner/AppleII-VGA

I would also suggest trying Mark's 1.0.0 firmware release, see if it makes any difference. He has backported some of the changes I and others have made, and some folks have had better results running his firmware.  https://github.com/markadev/AppleII-VGA/releases/tag/v1.0.0   I don't know what all features he has implemented beyond the IIe modes, so the config util and multiple fonts are almost certainly off the table.

Thank you. I will give this a try.

I realize I never updated this. All set closing the issue.


Testcases 1057 and 1129 fail when built against HDF5 1.10 configured with --with-default-api-version=v18

Hi,
In the process of preparing the HDF5 1.10 transition in Debian, i've tried a build of Matio 1.5.8 against the HDF5 1.10 packages currently in Debian experimental. Matio builds fine but the test suite reports 2 failures :

1057: Delete variables                                FAILED (mat73_readwrite.at:40)
1129: Delete variables                                FAILED (mat73_compressed_readwrite.at:42)
Please find attached an archive of the resulting testsuite.dir.

Note: this instance of HDF5 1.10 was configured with --with-default-api-version=v18.
Thanks.
testsuite-dir.tar.gz

Thanks for reporting and providing the files. Need to check and update (Travis) CI to also build against HDF5 1.10. Unfortunately I'll be offline for the next week, hence it will take some more week to fix the issue (if possible).

Can you please reproduce the problem with HDF5 v1.10.0-patch1 and current HEAD of matio? https://drone.io/github.com/tbeu/matio/547 gives different test failure (of same two tests though).

Same failure as https://drone.io/github.com/tbeu/matio/547. New testsuite.dir attached.
testsuite-dir.tar.gz

I can reproduce on CentOS and investigated the issue. It looks like a problem of the new HDF5 1.10 lib, hence I asked the HDF Group for support by mail.

Hi,
Has the HDF Group replied with a HDFFV issue number?
Thanks.

They did and wanted to investigate. Need to ask them about progress or update.

The HDF5 group asked for a stand-alone test case merely depending on the HDF5 library. This was my reply from today:

Hi,
thank you for your feedback.
I created a stand-alone application test41 that just simply uses the HDF5 library. Please copy https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4 to a source file test41.c and build it with
$ gcc -DHAVE_HDF5=1 test41.c -o test41 -lm -lhdf5
You probably need to specify include and lib pathes for the HDF5 library.
Now copy matio_test_cases_hdf_le.mat from https://sourceforge.net/p/matio/matio_test_datasets/ci/master/tree/ to your test41 directory and run
$ ./test41 matio_test_cases_hdf_le.mat var2
to first copy matio_test_cases_hdf_le.mat to test_mat_copy.mat and then delete variable var2 from the copied file.
You can inspect the resulting MAT file test_mat_copy.mat by a debug tool like h5dump and you will see that using HDF5 1.8.17 results in a valid MAT file test_mat_copy_18.mat (http://tbeu.de/test_mat_copy_18.mat) and using HDF5 1.10.0 results in an invalid MAT file test_mat_copy_110.mat (http://tbeu.de/test_mat_copy_110.mat).
HDF5 1.8.17 was configured with
$ ./configure --quiet --enable-shared --enable-production --enable-debug=no --disable-deprecated-symbols --disable-hl --with-pic --with-default-api-version=v18 CFLAGS="-w"
and HDF5 1.10.0 was configured with
$ ./configure --quiet --enable-shared --enable-build-mode=production --enable-deprecated-symbols=yes --disable-hl --with-pic --with-default-api-version=v110 CFLAGS="-w"
If you need some more details just let me know.
By the way, running test41 on Windows using the pre-built libraries from https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.10/hdf5-1.10.0-patch1/bin/windows/extra/ and using Visual Studio 2015 also gives errors, but different ones. Thus I believe there is some new issue apparent in HDF5 1.10.0.
Thank you for caring.
Best regards,
tbeu

And this is the command to build test41 using Visual Studio 2015 x86 command prompt

cl /MD /DHAVE_HDF5=1 /DH5_BUILT_AS_DYNAMIC_LIB /I"c:\Program Files (x86)\HDF_Group\HDF5\1.10.0\include" test41.c /link /DEFAULTLIB:"c:\Program Files (x86)\HDF_Group\HDF5\1.10.0\lib\hdf5.lib"

One more answer

Hi,
I know that there a many additional calls beside the HDF5 API calls. I already spent several hours on this problem an can give you the following clues again.

Calling Mat_VarDelete is the only test that fails. Hence it is not likely that the modified data types of HDF 1.10 are the error.
There is no problem with writing a HDF5 file since the intermediate HDF5 file after line https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4#file-test41-c-L9078 is all fine.
It is also all working fine until line https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4#file-test41-c-L9109 where the content of the mat_t data straucture (https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4#file-test41-c-L701-L713) is copied from the newly opened file to the already existing data structure (living outside Mat_VarDelete). This structure includes the HDF5 file identifier (https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4#file-test41-c-L8544 or https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4#file-test41-c-L8546) of the newly opened HDF5 file in https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4#file-test41-c-L9101.
Afterwards only Mat_Close (https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4#file-test41-c-L21873) is called which basically calls H5Fclose (https://gist.github.com/tbeu/b31c50fa11587a21675c211571116ca4#file-test41-c-L8581) on this file identifier.
This results in the invalid/truncated HDF5 file using HDF5 1.10.

Now I am out of any more ideas on do hope that you will have another look on this case.
Best regards,
tbeu

HDFFV-9983 is the (non-public) bug number.

I've pinged the HDF Group support desk. No news, but they promised to have a look as soon as they can.

Yes, I did the same in the last weeks. So far nobody did investigate it.

Hi Thomas,
What is the status of this ticket? Have you find a worlkround using h5repack(), as suggested by the HDF Group support desk? I'm worried because the transition freeze for Debian Stretch is very soon now: 5th November 2016.
Thx.

I wondered why I could no longer reproduce the issue (neither on CentOS nor on Win) until I figured out that 38f50fdb78c48162c99d66365bc7d81542d50090 for #44 also resolves this issue.

That's very good news indeed :)
Will you release a new version soon?
Thanks.

Hope so (before your deadline). But need to work on two more other issues before making the new release.

My deadline is somewhat reached already: I have a lot of work to do before requesting a transition slot from Debian Release Team, and ideally this request should be made very soon, in the next few days.
What do you think about cherry-picking 38f50fd for the current Matio release in Debian unstable? It might be the best option I have...
Thanks.

So what is your exact deadline for matio. There is more than this critical commit.

I don't know exactly. The transition freeze is the 5th of november. But if I submit my request the 4th, it is very likely it will be dismissed, so close of the deadline. HDF5 has 65+ reverse dependencies. The sooner I submit, the more chance I have the request will be accepted.
If I start rebuilding all the reverse depends this evening, I can be done by Sunday. Would you have something by then?
Thinking about it, a patch against the current matio release in Debian is the best option: a new matio release would have to transition before hdf5.

Ok, I hurry up such that you have some new release v1.5.9 the next 2 or 3 days. (Just fixed cc032717345cf630a36909d1beedd663e3e68386 and only #40 left open for read-write mode.)
By the way, previously I was on contact with @sebastien-villemot for some Debian related lib maintenance - basically only when it failed.

@pini-gh I am indeed the maintainer of libmatio in Debian. Feel free to open a bug against the package with the patch, I'll try to handle it quickly. Or even better, don't hesitate to do a team upload directly if you're member of the Debian Science Team.

From the NEWS:
Changes in 1.5.9 (xx October 2016)

Fixed resource leak when reading character data from HDF5 MAT file
Fixed bug writing struct to HDF5 MAT file (Mat_VarWrite never returned 0 on success)
Fixed bug writing sparse logical array to HDF5 MAT file
Fixed bug calculating array sizes of structs, cells, complex and sparse arrays in Mat_VarGetSize
Fixed bug duplicating sparse array with empty data in Mat_VarDuplicate
Fixed segmentation fault when reading compressed v5 MAT file with opaque class
Updated support of HDF5 v1.10.x (no longer depend on deprecated v1.8.x symbols)

If you cannot wait I would at least patch 7. (e387271d20f902d4f65fa1352898f12a789b1161) beside 1. (38f50fdb78c48162c99d66365bc7d81542d50090).

FYI: I plan to release v1.5.9 tonight.

Thanks Thomas!

v1.5.9 is now (that GitHub and Travis CI are back to stable) released.

@pini-gh I have uploaded version 1.5.9 to Debian. However the package is not yet accepted, because of the ongoing maintenance operation on ftp-master.

@sebastien-villemot Make sure it is the latest v1.5.9 (needed to re-tag about 20 min ago).

@tbeu Oh no… Here is the one I uploaded:
$ md5sum matio-1.5.9.tar.gz 6cdb2f1ff549129068182d09ea5bb2c4  matio-1.5.9.tar.gz

I'm trying to cancel my upload, maybe it's not too late. Otherwise I'll have to upload the new 1.5.9 tarball under a different version number (like <IP_ADDRESS> or 1.5.9+real or something like this).

Sorry for that.

Fortunately, thanks to the temporary disruption of Debian services, I was able to cancel my previous upload.
The right libmatio 1.5.9 has now been uploaded and accepted in Debian.

Thanks for letting me know.

Thanks Sébastien.

The transition freeze is the 5th of november.

@pini-gh Being curious, did you manage to submit your hdf5 1.10 update?

@tbeu It's on good track. I've got an ACK from the release team and they told me I should have a GO in a few days. They want to finalize some other ongoing transitions first.

Sound good! Fingers crossed!

@tbeu: hdf5 1.10 has landed into Debian unstable yesterday. The transition ongoing.

I was told that new hdf5 1.10 release is expected for Feb.

The HDF Group told me 1.10.1 will be released in January. But this will be too late for Debian Stretch.

Updated hdf5 1.10.1 seems to be delayed to any time later.

Indeed. They now say "by the end of March".

FYI: hdf5 v1.10.1 was released today.

As far as I know, files created with hdf5 v1.10 are not backward compatible to 1.8. See:
https://support.hdfgroup.org/HDF5/docNewFeatures/
Due to the requirements of some of the new features, the format of a 1.10.x HDF5 file is
likely to be different from that of a 1.8.x HDF5 file. This means that tools and applications
built to read 1.10.x files will be able to read a 1.8.x file, but tools built to read 1.8.x files
may not be able to read a 1.10.x file.

I think that Matlab until now used 1.8, so I think matio should reject hdf5 1.10 for the time being?


Renew pdc client doc

Correct build pdc client package from source with tito instead of
make rpm.
JIRA: PDC-1134

looks good to me

Looks good to me

looks good

:+1:


s1 metric heatmaps have trouble with NaNs

When calculating the heatmaps for the s1 metric there is a problem when NaNs are encountered.  It handles the NaNs well during calculation, but then wants to print a warning on the screen that NaNs are encountered - and that's where it stops with an error.

Error message:
File ~/anaconda3/envs/ai2es-sharpness/lib/python3.8/site-packages/sharpness-0.1.0-py3.8.egg/sharpness/heatmap.py:106, in Heatmap(img1, img2, metric, block_size, pad_len, pad_mode, block_stride, bivariate)
104 if np.any(np.isnan(res)):
105     if type(res) is list:
--> 106         print(f'NaNs encountered in {metric.name}:\n'
107               f'{np.sum(np.isnan(res[0]))} NaNs out of {np.prod(res[0].shape)} total blocks in image 0\n'
108               f'{np.sum(np.isnan(res[1]))} NaNs out of {np.prod(res[1].shape)} total blocks in image 1')
109     else:
110         print(f'NaNs encountered in {metric.name}: {np.sum(np.isnan(res))} NaNs out of {np.prod(res.shape)} total blocks')
AttributeError: 'functools.partial' object has no attribute 'name'

I added a line in "metric_list.py" that sets the __name__ attribute for s1 manually to work around this, and pushed this fix in commit 4c646d0a1def175fd7a301f38f0d0c74acdb2f4d, so these errors should no longer occur.


api: Run just check-api

Some wombat queued 100 PRs up and is constantly breaking the api text files.

ACK 7cd6778
Should we make the API check non-blocking in github until we have 1.0? Maybe just warn for now

Either that or maybe toggle GitHub's Merge Queue

Re-based and re-ran because more changes to the api files have gone in.

Can you put this one when you get a chance please @apoelstra, I'll keep an eye open and rebase everything else I have open then so we can get back to a clean slate.


Fix more tick size bidding errors

Fixes several remaining tick size related bugs
Improves quality and accuracy of error messages. For example:

When there is a tick size, the minimum bid amount now shows the prior bid + the tick size
Numbers in error messages are now limited to two decimal places, same as the allowed # of decimal places in the bid input box

Now accurately accounts for the following auction states:

First bid
Not first bid / has tick size
Not first bid / no tick size

Looks good. When its in dev post in engineering and a few of us can do tick size testing.


Bug: Number Circle missing before "Collaborate" Heading

Description
Currently, the website's sections include "Collaborate," "Connect," and "Build."
And, there is a number circle before each one of them, except for "Collaborate" . This inconsistency can be improved for a more cohesive design.
Proposed Solution
To maintain design consistency across sections, we propose adding a number circle element before the "Collaborate" heading. This will enhance the visual appeal and user experience.
Screenshots
The Collaborate section does not have number circle:

Rest of the sections have that:

Browser 🥦
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no).

Heyy @tamalCodes , I will love to solve this bug, this only needs a number inside the circle with the same css as the other sections are having, can you please assign this issue to me? I will love to contribute.

Hi thanks for raising this issue however we would like to fix a lot of design flaws in total. We have the work ongoing in #1119 would you like to collaborate in that ?

Yes, i will love to contribute, and there i can fix the major ui flaws, right?

Hi @tamalCodes , can I work on this issue?

Hi , @sahilrohera10 @harsh31dangi ping up there in the issue.
@varundhand , you can just copy-paste what you want to remove (whatever you mentioned here) in that issue itself. and we can proceed further. That issue has a https://github.com/MilanCommunity/Milan/labels/multi-asignees tag, meaning more than 1 person can collaborate and make PRs for the same issue.
To avoid confusion I'll close this issue and let's continue there !

Sure thing @tamalCodes!


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 3f5e262:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-11-08-06-54-48 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-11-08-06-54-48

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


switchToWindow doesn't allow you to resize or maximize new window

What is your Test Scenario?
Testing a site registration process.
What is the Current behavior?
Navigate to a site.
Click on the register link which opens a new window (smaller window then the main)
Use the switchToWindow action to access that window
If I attempt to resize the new window or maximize the new window and it doesn't alter the new window.
What is the Expected behavior?
switchToWindow followed by the resize or maximizeWindow Action should resize the new window
What is your web application and your TestCafe test code?
It's not a public site.
Tired:
   await t.switchToWindow(w => w.url.pathname === '/account/register');
   await t.maximizeWindow();

Tired:
  await t.switchToWindow(w => w.url.pathname === '/account/register').maximizeWindow();

Tired:
   await t.switchToWindow(w => w.url.pathname === '/account/register').resizeWindow(600,600);

Tried:
   await t.switchToWindow(w => w.url.pathname === '/account/register');
   await.resizeWindow(600,600);

Steps to Reproduce:
Navigate to a site.
Click on the register link which opens a new window (smaller window then the main)
Use the switchToWindow() or maximizeWindow() action to access that window
If I attempt to resize the new window or maximize the new window and it doesn't alter the new window.
Your Environment details:

testcafe version:                   1.9.0
browser name and version: Chrome 86
platform and version:          Windows 10

The resizing functionality for multiple windows will be available in Chrome-based browsers in v1.10.0. You can test this functionality in the release candidate (v1.10.0-rc.2).
Currently, this feature is not implemented in Firefox. Please track the https://github.com/DevExpress/testcafe/issues/5700 issue to see the progress.


f1 score precision, recall added

@PranitAbhinav Have you tested the methods?

Yes , I have tested it and compared to sklearn metrics it showed same
results.
On Mon, Apr 12, 2021, 14:02 Kailash Ahirwar @.***>
wrote:

@PranitAbhinav https://github.com/PranitAbhinav Have you tested the
methods?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ravenprotocol/ravml/pull/6#issuecomment-817606507,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBGIGVHGK2KFUFLFH5JQVLTIKV2NANCNFSM42YXOWGA
.


json utf8 messy code

I created a controller and return utf8 string;
using CMAKE and drogon source code;
jsoncpp's  emitUTF8 has set to true
void login_controller::login(const HttpRequestPtr& req, std::function<void(const HttpResponsePtr&)>&& callback)
{
auto json = req.get()->getJsonObject();
string name = (*json)["UserName"].asString();
string psw= (*json)["UserPsw"].asString();
Json::Value ret;
if (!name.empty() && !psw.empty())
{
ret["Msg"] = "登录成功";
ret["Result"] = true;
}
else
{
ret["Msg"] = "登录失败,无效用户名或密码";
ret["Result"] = false;
}
auto resp = HttpResponse::newHttpJsonResponse(ret);
cout << ret << endl;
callback(resp);
}
and this is the result
console->{
"Msg" : "登录成功",
"Result" : true
}
this is ok;
but in browser,I got those->
{"Msg":"��¼�ɹ�","Result":true}
Is there any set in drogon? or other works to dealing with this.
I am a fresher ,sorry to bother you twice in one day;

Usually, this is due to the character set of your source code, especially in the windows dev environment. I'm not sure, but if you build the application by MSVC, please set the source file on UTF8(with BOM)

finally I got this->https://blog.csdn.net/Michael_fchou/article/details/104349977
but jsoncpp data will still transform utf-8 to unicode;
set jsoncpp's emitUTF8=true will really dealing with this;and it's also works in Linux complie
console->{
"Msg" : "登录成功",
"Result" : true
}
browser->{"Msg":"登录成功","Result":true}
thanks again for help


error：string index out of range

Hello,
I use SISTR in local and run your example usage
I get the following error messages:
Traceback (most recent call last):
  File "/usr/local/bin/sistr", line 11, in <module>
    load_entry_point('sistr-cmd==1.0.2', 'console_scripts', 'sistr')()
  File "/usr/local/lib/python3.5/dist-packages/sistr/sistr_cmd.py", line 324, in main
    outputs = [sistr_predict(input_fasta, genome_name, tmp_dir, keep_tmp, args) for input_fasta, genome_name in zip(input_fastas, genome_names)]
  File "/usr/local/lib/python3.5/dist-packages/sistr/sistr_cmd.py", line 324, in <listcomp>
    outputs = [sistr_predict(input_fasta, genome_name, tmp_dir, keep_tmp, args) for input_fasta, genome_name in zip(input_fastas, genome_names)]
  File "/usr/local/lib/python3.5/dist-packages/sistr/sistr_cmd.py", line 194, in sistr_predict
    cgmlst_prediction, cgmlst_results = run_cgmlst(blast_runner, full=args.use_full_cgmlst_db)
  File "/usr/local/lib/python3.5/dist-packages/sistr/src/cgmlst/__init__.py", line 342, in run_cgmlst
    full=full)
  File "/usr/local/lib/python3.5/dist-packages/sistr/src/cgmlst/__init__.py", line 134, in get_allele_sequences
    msa_ref, msa_novel = msa_ref_vs_novel(ref_seq, allele_seq)
  File "/usr/local/lib/python3.5/dist-packages/sistr/src/cgmlst/msa.py", line 58, in msa_ref_vs_novel
    msa_out_dict = msa_mafft(input_fasta)
  File "/usr/local/lib/python3.5/dist-packages/sistr/src/cgmlst/msa.py", line 41, in msa_mafft
    if stdout[0] == '>':
IndexError: string index out of range

I don't know why？
Do you have any idea？

Hi, thanks for using sistr_cmd! I think the issue could be due to not having mafft installed.
Do you have mafft (https://mafft.cbrc.jp/alignment/software/) installed on your system and accessible in your $PATH? sistr_cmd needs mafft to do some checks when running cgMLST against your input genomes.
Hope that helps!

The problem is indeed in mafft.
sistr_cmd works now.
Thanks your help.


is there a safe method you recommend for storing a browser-generated PKCE code_verifier?

is there a safe method you recommend for storing a browser-generated PKCE code_verifier, so that it can be used in a redirected page instance to complete an authorization flow?

hello, you could put it in session storage.


Query Languages as features

For our discussion: This is what it would look like to turn SQL into a feature. Could be done similarly for other query languages. Mid-term, a larger refactoring, turning query languages into modules, would be preferable.

now serialization works again, now we can merge


[FEATURE] Terraform Provider should support EFI boot

Is your feature request related to a problem? Please describe.
The Terraform provider does not make provisions for enabling EFI boots which prevents using some VM images (notably Rocky9)
Describe the solution you'd like
Add a configuration parameter to the harvester_vm resource that allows me to enable EFI boot mode.
Describe alternatives you've considered
Someone has forked your provider github repo and made the change themselves. This is not a supportable solution so I need something we can take to customers

@bcdurden supported in terraform-provider-harvester v0.5.2


New Release version with the latest closed PR`s

Hi guys, i saw that master has closed pr`s that were not released under a new minor version.
Because of that we need to use this "dev-master#3f7a284906ce3e402bcb101938270842fdad71fa".
Can we add a new release ? with the latest stuff in dev-master?

I don't think we release new version of v1.

Yes but you have closed pr`s after the latest release.... TO get those in we need to add propel in composer with hash... not with version that is silly .


Update Laserposition in Jog-Pane

I think we had partially opted against this because it had an issue that you'd lose the laser-goto location.


FasterTransformer offloading integration

This adds two Q schemes, q4f16_ft and q8f16_ft, for quantizing weights in the format as expected by the FT fp16 A - int B kernel. The resulting decode -> matmul sequences are offloaded to the FT kernel via CUTLASS BYOC.
The new Q scheme is a simple symmetric one where each column of (K, N) matrix is scaled by the corresponding element from a scale vector of shape (N,). Each scale is calculated over the K axis. For int4, the weight matrix needs to be packed into int8 storage with shape (K, N / 2).
The quantized weight is further preprocessed by relax cutlass.ft_preprocess_weight packed call, which is made possible by the recent improvement https://github.com/mlc-ai/mlc-llm/pull/622. Moreover, based on the attributes of the consumer matmul or weight shape, we may need to fallback to other Q scheme. I use GroupQuantizationSpec when the FT Q is not applicable. This fallback mechanism is made possible by another recent improvement, https://github.com/mlc-ai/mlc-llm/pull/657. Thanks @MasterJH5574 for your help in making these improvements.
@tqchen @sunggg @junrushao @yzh119

This is a shiny piece of code I don’t actually fully understand! Please feel free to get it in and I will try to comprehend later


Update Netty to version 4.1.31.FINAL

This update was performed, because a Netty 4 dependency was added in graylog-server version 2.5 for backport of the DNS Lookup adapter (see https://github.com/Graylog2/graylog2-server/pull/5274).
@bernd and I will review together in Houston

Coverage remained the same at 82.581% when pulling 96fcf9db20a389385ce961c06e5f87bb7fa604d7 on update-netty into a9715ff3f6ae7d926f9ed35be29c2353815ea4cd on master.


Update fred integration

I recently found out the endpoint that gets series within a category is limited at 1k. we should iterate over all pages.
ratelimit.exception.RateLimitException: too many calls should be handled

Fixed the category limit issue, RateLimitException will be handled in a different issue


Get unexpected results from demo

Results form demo(test image is from GOPRO):

Environment:
Windows 10 with Anaconda3,
python 3.7.13, pytorch 1.7.0, cudnn 8.2.1, cudatoolkit 11.0.221,
(Because RTX3060 in my machine do not surpport cuda<=10,
and pytorch 1.6 do not surpport cuda>=11, I cannot use pytorch 1.6.0)
tqdm 4.64.0, imageio 2.9.0, scikit-image 0.18.3, numpy 1.19.2, matplotlib 3.5.1, pyreadline 2.1
Test Command:
python main.py --save_dir GOPRO_L1 --demo true --demo_input_dir GOPRO_Large/MyTest --demo_output_dir GOPRO_Large/MyResult
I modified utils.py as this issue, and changed nothing else.
I want to know why I got this result and what should I do to get correct result.

Hi @XCR16729438,
Did you download the pretrained model weights?
Please refer to #1. Your case seems to be the same one.


FIXED: don't remove / from labels

this should handle cases where / is contained in labels

Thanks for the submission, but a few questions/comments:

What exactly are you trying to "fix"?  There's nothing broken, per se.  There's a reason why the range of characters that constitute labels is limited -- it has to meet criteria for HTML, LaTeX, ODF, and other possible future formats.  Do you have a real-life example where this causes problems?  Have you tested this in other output formats?

I realize that the whitespace in the code is not always 100% consistent (my settings in Xcode aren't always customized, and sometimes that would create changes.)  That said, a pull request with 64 lines of changes that really only changes a single line is difficult to check.  It's much easier if the pull request only changes the minimum number of lines -- it took me several passes just to find the actual content of this request.  It's fine for you to disagree with the existing whitespace, but leave it alone in this circumstance.  ;)

Last, but not least, check out this page.  If you want to make your case for this change for MMD-6 over there, feel free.  I'm open to considering changes.  But this won't be changed in MMD-5 since a new version is almost finished.

i'm trying to unbreak semantic labels in latex like when i use crossreferences as explained here https://en.wikibooks.org/wiki/LaTeX/Labels_and_Cross-referencing

This example:
## Something 1 [ch:som1]
### Something 2 [sub:som1/som2]

[](#sub:som1/som2)

is broken actually.

Sorry for the whitespaces. My vim editor is configured to trim all of them on save https://github.com/thypon/dotconfig/blob/master/.vimrc#L82

I know there will be another release in the near future but a stable working version isn't a bad idea for now.

It's not broken, you're doing it wrong.  ;)  You're confusing HTML anchors (the [](#foo) syntax) and MMD cross-references (the [][foo] syntax).  The two are different things.  Your example "accidentally" works correctly some of the time because you can generally anticipate what a heading id attribute will look like, but sometimes you can't.   There are two ways to fix it.  You can use a correctly anticipated HTML anchor:
 ## Something 1 [ch:som1]
 ### Something 2 [sub:som1/som2]

 [](#sub:som1som2)

or you can use the expected MMD syntax (and it figures out the correct anchor for you):
 ## Something 1 [ch:som1]
 ### Something 2 [sub:som1/som2]

 [][sub:som1/som2]

No worries.

MMD 5 is a stable working version.  ;)  That's not to say it's 100% bug free, but it's very close for most users.


FEATURE: A simplification of the creation of  load_combination_items

Is your feature request related to a problem? Please describe.
A simplification of the creation of  load_combination_items, because it is annoying to mark all the specified fields as true, if the fields are marked as false the items are not accepted by rstab9.
Describe the solution you'd like
A constructor that sets every "...Specified field to true for me.
Describe alternatives you've considered
Currently, for each "..Specified" I call the field and toggle t

he value to true
Additional context
Without setting the fields, the combination_item will not be accepted by Rstab and the last_combination will remain empty

Later I realized that the specification fields are also in the load_combinations. Maybe I can declare them in general as true as default or if I set an attribute which is "more specified" I can change the boolean value.
e.g:
load_combination combination = new load_combination();
combination .imperfection_case = 23;
=> no function
combination .imperfection_case = 23;
combination .imperfection_caseSpecified = true;
=> desired function
Translated with www.DeepL.com/Translator (free version)

Later I realized that the specification fields are also in the load_combinations. Maybe I can declare them in general as true as default or if I set an attribute which is "more specified" I can change the boolean value.
e.g:
load_combination combination = new load_combination();
combination .imperfection_case = 23;
=> no function
combination .imperfection_case = 23;
combination .imperfection_caseSpecified = true;
=> desired function

We are using SOAP technology for our WebService. C# library is automatically generated with the help of WSDL. Every SOAP request has its own method in the library. Every SOAP type has its own class. Class contains all properties with "default" values.  Class could have dozens of properties and you might use just a few of them.  Here it comes ...Specified into the game.  With the help of ...Specified we create request which contains properties which only you set. That way, we limit the size of request.
So if you want to assign imperfection case 23 to combination you need to use rows
combination .imperfection_case = 23;
combination .imperfection_caseSpecified = true;

Then SOAP request set_load_combination contains
<imperfection_case>23</imperfection_case>

We are using SOAP technology for our WebService. C# library is automatically generated with the help of WSDL. Every SOAP request has its own method in the library. Every SOAP type has its own class. Class contains all properties with "default" values.  Class could have dozens of properties and you might use just a few of them.  Here it comes ...Specified into the game.  With the help of ...Specified we create request which contains properties which only you set. That way, we limit the size of request.
So if you want to assign imperfection case 23 to combination you need to use rows
combination .imperfection_case = 23;
combination .imperfection_caseSpecified = true;

Then SOAP request set_load_combination contains
<imperfection_case>23</imperfection_case>


merge package template from arlac77/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template

Codecov Report

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

@@           Coverage Diff           @@
##           master     #348   +/-   ##
=======================================
  Coverage   69.45%   69.45%
=======================================
  Files           4        4
  Lines         203      203
=======================================
  Hits          141      141
  Misses         62       62

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 fb0b630...c2d33b6. Read the comment docs.

Coverage remained the same at 64.49% when pulling c2d33b69cdd268f37d7ee6f597a7e57c13c08ef9 on template-sync-1 into fb0b63043247243935d74913a60c8b6499dfdfbb on master.


Why not make it distro-agnostic?

Why not make this icon theme distro-agnostic and not specifically market it towards Ubuntu? Has anyone tried this under Solus?

this is not an icon theme.

This is distro agnostic, however, this is tested and fulyl supported only for Unity.

This is distro agnostic, however, (...) fully supported only for Unity.

This sounds contradictory to me. Why not add another desktop environment to make it "more" agnostic? I like your theme but I don't understand the fascination and exclusive focus on Unity, that's all.

It requires time and effort to create and maintain it for different DE's.


some more grouping on ontology pages

Yesterday we discussed whether there were any other ways that terms should be grouped together.
I think we are OK for now on the gene pages, but on the ontology pages, it might be better for process terms if regulation terms were listed immediately underneath the regulated process.
See:

mitotic spindle assembly
regulation  of mitotic spindle assembly
positive regulation  of mitotic spindle assembly
mitotic spindle elongation
regulation of mitotic spindle elongation
positive regulation of mitotic spindle elongation
negative regulation of mitotic spindle elongation
much easier to consume ....

This is in no way critical but do others think it would be useful?

assess if it would be better to order terms so more specific terms first
Kim suggested this. It might work for function, not sure about process.
Need to add some page examples, and discuss pros & cons
(transferred from  https://github.com/pombase/website/issues/229)
will discuss term age display again later

also  consider with this one
https://github.com/pombase/website/issues/235

A small improvement might be to always have the term in question at the top...
MAybe we discussed this and decided against it...
I'm thinking
Term...
Descendants...
Sometimes its a bit odd that the term referred to can get a bit buried...
But there may be disadvantages to doing this?

Action:
Put the  'term page' term at the top.

Action:
Put the 'term page' term at the top.

I've made that change.  I'll close the issue after checking on Tuesday morning.

Action:
Put the 'term page' term at the top.

Done and now on the main site.


How to play sound

How to play sound, and please place it in example section

I believe you're looking for the "airhorn" example :)
https://github.com/bwmarrin/discordgo/tree/master/examples/airhorn

FYI: the mentioned repo to dca-rs seems to be removed.
Is there any known working alternative or fork?

https://github.com/bwmarrin/dca
That's the link to the dca project. There's a couple implementations listed there that you can use.
We need to update the readme on the airhorn example though to not refer to dca-rs anymore.


The main bugs found on PROD

[ ] The user name is not visible at all
(https://app.birdeatsbug.com/sessions/IkExTJ5vPJxdRaa0_WTpq)

[ ] There are no user names displays in the feed transactions card (https://app.birdeatsbug.com/sessions/jA4PNpOdYy9EO_tRj2_xT)

[ ] There is no feed transactions card displayed after creating the transaction via the "Receive via wallet link" (https://app.birdeatsbug.com/sessions/BCG_TAwGWa4KQiKrU-I4X?)

[ ] There is no possibility to delete avatar
(https://app.birdeatsbug.com/sessions/Ln4TBwrzXozPm9_rz9k67)

Avatar issue is RealmDB-related. It caused by 'update not permitted' error.
As other fields (e.g. fullname) could be changed and avatar could be cropped and saved that means we have again the issue with setting realm fields to null. Need to applied schema changes we did on QA / Dev to support null values
@sirpy could you please do it or provide creds from Realm dashboard to my GD email account ?

"About The user name is not visible at all" i think it can be related, to signup method?
I tested it on new account and i have my full Name visible.

@vldkh the avatars issue has been resolved

@johnsmith-gooddollar
The avatar issue is not reproduced now.
https://app.birdeatsbug.com/sessions/rit3HiU3_uP75NhiEK_t4

@vldkh
Regarding 'There are no user names displays in the feed transactions card' - that's ok because we loading profiles from RealmDB during feed events formatting. So for the profiles haven't been migrated we'll display Unknown and no avatar.
I've checked with two profiles have been filled and stored to Realm - everything is working fine.
After the counterparties will open wallet and migrate to Realm, we will be able to load their profiles and display avatars/names. To update feed items were cached we're re-requesting counter party profiles each 24hrs until got name/avatar (see #3380 for more details)

@lukasz-kilaszewski @johnsmith-gooddollar
The feed transactions cards are not displayed after creating the transaction on the recipient side via:

Request specific amount
Receive via wallet link
Receive via QR-code

From the sender's part -  everything is good.
Attachments:
https://www.screencast.com/t/mRp0cknQgUQ

@vldkh @sirpy
Regarding 'no feed transactions card' issue.
It happens because production realmdb instance doesn't have inboxes collection for tx outbox feature.
Need to migrate this schema from dev/qa. I tried to do it but it seems i have no such permissions:

Also there's a strange error ' Error: ENS is not supported on network private' looks related to the web3.
@sirpy could you please look on this ?

@vldkh added the missing inbox

@johnsmith-gooddollar
There is no possibility to upload the avatar. The error popup "we could not capture all your beauty. please try again" is shown. The same issue on QA and DEV envs.
Environment:
DEV 1.31.1-1
QA 1.31.1-1
Devices:
Windows 10 // Google Chrome v93
Attachments:
https://app.birdeatsbug.com/sessions/VvV2q15OLAaZlytwIpqHN?

@sirpy need to buy some extended tier on Pinata:
{“error”:{“reason”:“FREE_TIER_EXCEEDED”,“details”:“You have exceeded the free tier data limit! Please add a credit card to your profile to continue pinning content with Pinata.“}}

@vldkh avatar should be saved now

@johnsmith-gooddollar
There is no possibility to enter the invite code on the invite page. The field is unclickable with new accounts.
Environment:
PROD 1.31.12
Devices:
Windows 10 // Google Chrome v93
Attachments:
https://app.birdeatsbug.com/sessions/DmtpXLGQ6vooC3MyHRs_C?

@johnsmith-gooddollar
All of these issues are not reproduce on PROD 1.32.1. Main functions work properly.
Environment:
PROD 1.32.1
Devices:
Windows 10 // Google Chrome v93