Model nullability with Option

Right now any WinRT interface/class/delegate types (reference types) can store a null pointer value. We should change that so that a null pointer value is not a valid state and the developer has to use Option<T> to express that. While this is more syntactically verbose in some cases, at least when you hold a T you know it's valid and can use it directly with no runtime or syntactic overhead. WinRT class constructors (T::new() in Rust) will simply return Result<T> but all other return/out params of reference types will simply return Result<Option<T>> on the assumption that it could be null. This avoids the confusion around whether a given value may be used or whether the is_null check should be performed, which is not idiomatic in Rust.
Beyond constructors, we should be able to avoid the extra Option<T> for activatable factory interfaces since they are exclusively used to implement constructors.

For reference, in winrt-rust we also made the same change after a while: https://github.com/contextfree/winrt-rust/pull/54
It did make dealing with return values more cumbersome, because now you always have to "unwrap" twice ...
Probably, many methods never actually return null, but there's no way to know that. Maybe at some point additional metadata could be added, so the Option<> wrapper could be elided fer such methods ...? Just dreaming ;-)

By the way, in winrt-rust we also added an exception for the Windows.Foundation.IAsync... types because I guess it would really be a bug if such a method would return null. The user is expected to await it, and await doesn't work on null. The question remains what to do if it actually does happen (because some kind of safety check needs to be there) ... it probably would have to panic!.

Thanks Patrick, double unwrap is certainly a bit gross. Yes, .NET has the NotNull attribute. We could introduce such an attribute for WinRT, but the challenge is always getting any adoption for such an attribute on the many existing APIs.
I do like the idea of excluding certain common patterns, like constructors and async.

Here's the attribute proposal: https://github.com/microsoft/xlang/pull/708

Looks like the attribute may not be practical, but I think we can grow the number of return types that are, heuristically, not-null to the following:

Constructors
Functions that return async interfaces
Functions that return collection interfaces

#354 fixes this both in modeling nullability with Option<T> and avoiding the double unwrap by folding the degenerate case into the result's Err value so that WinRT APIs simply return Result<T> rather than Result<Option<T>>.


create discord bot

I know it's a very small PR but I think this is necessary to help us start get rolling again. There's only one thing I have to comment on right now regarding the bot. As you probably know from discord bots you can set the avatar.
How should we do this? We can either have the server owner specify an image url in the config or place an image file somewhere in the server directory and we use that. I'm more leaning towards using a url.

Discord bot profile pictures are set through the discord bots page. I do not think you can set the profile picture through JDA.

It actually is possibly to change profile pictures through the api.

DiscordBot.getInstance().getJda().getSelfUser().getManager().setAvatar(Icon.from(File avatar));

That would be how to do it with a file. Icon.from() also has an overloaded method to take an InputStream so we can use a url.
I know we can do it through the discord page but this way might be a bit easier on owners for changing bot settings as it'd be all in one place.

Alright I'm happy with this right now, anything needing to be changed before merge?

Looks reasonable to me, but my knowledge of JDA and Discrod bridges is shaky - so if one of the others could just confirm the logic is sound, we can merge and get things rolling again.

If it's working, looks good to me. Did you run a test case at all?

yep, I tested it with an inject into the AboutCommand class and giving the name of the bot.


fix deprecated new Buffer()

using new Buffer() is deprecated for a long time now
use Buffer.from() instead
also change the serialization format to base64 to produce shorter
binary strings

Awesome, thanks!


Add clang-tidy in CI

This PR adds clang-tidy and clang-format using cpplinter in github action.

Sounds good, reverted the changed in the files used for testing


Dice Throw Problem ( DP problem ) - See the problem statement below

Given n dice each with m faces, numbered from 1 to m, find the number of ways to get sum X. X is the summation of values on each face when all the dice are thrown.

Hi! I would like to work on this!!

Hi! I would like to work on this!!

Yes you are free to take up the issue!

Is this issue open can I pick this one?


[WIP] Account access restriction

See #192 and https://ethresear.ch/t/account-read-write-lists/285

I'll try it again...


Enable all except plugins by default. Add --enable-plugins flag

A code change to enable all except plugins by default. Now if plugins need to be collected the user will have to pass --enable-plugins flag. This flag will be ineffective when --disable-expensive-operations is passed.

Looks good, please proceed! Thanks.
On Sun, 24 Dec, 2023, 2:14 am Vivek Narang, @.***>
wrote:

@narangvivek10 https://github.com/narangvivek10 requested your review
on: #8 https://github.com/SearchScale/search-insights-collector/pull/8
Enable all except plugins by default. Add --enable-plugins flag.
—
Reply to this email directly, view it on GitHub
https://github.com/SearchScale/search-insights-collector/pull/8#event-11331469734,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDCR5FVIKCAMSLIDX2GTNDYK47CXAVCNFSM6AAAAABBBAUPVGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGMZTCNBWHE3TGNA
.
You are receiving this because your review was requested.Message ID:
<SearchScale/search-insights-collector/pull/8/issue_event/11331469734@
github.com>


Split webpack config into base, development and production

I found that it's very hard to read and change webpack config with this boilerplate.
It's clear that there are many differences between development and production environment config. And I found redux approach is pretty good. It has three webpack config files: base, development and production. and uses different files accordingly.

I'll look into that, sounds like an acceptable and clear solution, thanks for showing me that!

So I looked at the Redux repo, and that looks really clean. Would love a PR against the v3.0.0 branch!

Done with d614130, thanks for the suggestion @yjcxy12!


⚠ Bofrost.lu has degraded performance

In e90182f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1980 ms

Resolved: Bofrost.lu performance has improved in ac51a15 after 28 minutes.


Add run_always() for "install-type" actions that don't use pip.

See discussion in https://github.com/dhermes/bezier/issues/224.
I am filing this issue because I'll be implementing this feature today.

@theacodes I'm gonna set a calendar reminder to cut a release with this change in it. Last release was May 24, 2020. How long do you want to leave the window open for other changes in the next release? (I was thinking June 24 to make it a month, but up to you.)


BUG - Duplicate Contacts from Merged Contacts

Are you a current Fivetran customer?

Issue identified by Marion Pavillet
Describe the bug

Our integration to the datawarehouse is done with fivetran. Deletions are caught properly with a deleted flag that is correctly ignored by the package.
Everything runs smoothly except for some tests related to contacts being unique in the email_events aggregated table:
unique_hubspot__email_event_clicks_event_id.sql
unique_hubspot__email_event_delivered_event_id.sql
unique_hubspot__email_event_opens_event_id.sql
unique_hubspot__email_event_sent_event_id.sql
unique_hubspot__email_event_status_change_event_id.sql
unique_hubspot__email_sends_event_id.sql

I did some investigation and it is due to contacts being merged in Hubspot. These contacts are not flagged as either deleted or inactive. Thus, there are duplicates in the email address (which is used in a JOIN clause and leads to duplicates downstream - specifically this SQL hubspot__email_event_sent.sql).
with base as (
    select *
    from database.schema_stg_hubspot.stg_hubspot__email_event_sent
), events as (
    select *
    from database.schema_stg_hubspot.stg_hubspot__email_event
), contacts as (
    select *
    from database.schema_stg_hubspot.stg_hubspot__contact
), events_joined as (
    select
        base.*,
        events.created_timestamp,
        events.email_campaign_id,
        events.recipient_email_address,
        events.sent_timestamp as email_send_timestamp,
        events.sent_by_event_id as email_send_id
    from base
    left join events
        using (event_id)
), contacts_joined as (
    select
        events_joined.*,
        contacts.contact_id
    from events_joined
    left join contacts
        on events_joined.recipient_email_address = contacts.email ---THIS IS WHERE IT IS MESSED UP
)
select *
from contacts_joined

Expected behavior

The merged contact is the contact that is used in transformations and not the older contacts.

@fivetran-joemarkiewicz Hey. This makes sense. What's weird about the Hubspot data is that the information about the merge is on the contact that has been merged into, not on the contact that has been merged. There's a column called merged_vids which is an array of the contact IDs that have been merged into a given contact.
I think to filter these out we would need to grab the unique set of IDs stored in merged_vids and then filter any of those IDs out from the table. This could be done in the staging model, though we may want to leave the grain of that untouched? If that's the case, I think we could do it in an intermediate model in the transform package.

Thanks for looking into this @DylanBaker. I was not aware of the merged_vids column previously, but looking into it I see how it stores both the merged contact and contacts that have been merged into it.
My one curiosity is that on the dataset I have available it seems that the merged contacts no longer exist within the contact table? I wonder why the customer is still seeing these merged contacts within their dataset while I see no record of the merged contacts?
I do agree with you however, that this should be performed within an intermediate model in the transform package to leave the grain of the staging model untouched.

This feature has been integrated within the latest v0.4.1 release of the dbt_hubspot package. FYI the feature is disabled by default and you may enable the contact merge auditing by setting the hubspot_contact_merge_audit_enabled to true.


Merge nnbd

Codecov Report

Merging #4 (93675f6) into null_safety (90f8c7c) will decrease coverage by 7.26%.
The diff coverage is 84.70%.

@@               Coverage Diff               @@
##           null_safety       #4      +/-   ##
===============================================
- Coverage        95.26%   88.00%   -7.27%
===============================================
  Files                7        6       -1
  Lines              190      125      -65
===============================================
- Hits               181      110      -71
- Misses               9       15       +6

Impacted Files
Coverage Δ

lib/src/interface/rx_storage.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

lib/src/logger/logger_adapter.dart
100.00% <ø> (ø)

lib/src/model/key_and_value.dart
100.00% <ø> (ø)

lib/src/impl/real_storage.dart
86.31% <84.41%> (-7.26%)
:arrow_down:

lib/src/async_memoizer.dart
100.00% <100.00%> (ø)

lib/src/logger/default_logger.dart
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #4 (93675f6) into null_safety (90f8c7c) will decrease coverage by 7.26%.
The diff coverage is 84.70%.

@@               Coverage Diff               @@
##           null_safety       #4      +/-   ##
===============================================
- Coverage        95.26%   88.00%   -7.27%
===============================================
  Files                7        6       -1
  Lines              190      125      -65
===============================================
- Hits               181      110      -71
- Misses               9       15       +6

Impacted Files
Coverage Δ

lib/src/interface/rx_storage.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

lib/src/logger/logger_adapter.dart
100.00% <ø> (ø)

lib/src/model/key_and_value.dart
100.00% <ø> (ø)

lib/src/impl/real_storage.dart
86.31% <84.41%> (-7.26%)
:arrow_down:

lib/src/async_memoizer.dart
100.00% <100.00%> (ø)

lib/src/logger/default_logger.dart
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Implement TRIO105 for anyio (library function must be awaited)

From https://github.com/Zac-HD/flake8-trio/pull/120#discussion_r1094980781

Some of trio_async_funcs don't exist in anyio, and vice-versa; we should probably make a second list (well, tuple) for anyio and check them separately.

I can probably compile it without too much issue, but let's have a separate issue & PR for it.

nursery calls have also been implemented in this since #56, that should probably be rewritten to use the new type-tracking functionality (Do we also want name-based tracking on top of that?), and anyio's version of that is Task Groups and https://anyio.readthedocs.io/en/stable/api.html#anyio.create_task_group

nursery calls have also been implemented in this since https://github.com/Zac-HD/flake8-trio/issues/56, that should probably be rewritten to use the new type-tracking functionality (Do we also want name-based tracking on top of that?)

Skimming through that issue, we only used name-based tracking at all because we thought type-based tracking wasn't worth the trouble.  Since we have the latter now let's add that; but keep name-based checks for nursery because there are a few patterns where you pass that around as an argument.
For TaskGroup, it looks like the conventional names are covered by tg|task_?group.

because there are a few patterns where you pass that around as an argument.

This only matters if they're not typing the parameter list, if they do it's covered.
While giving false positives on non-nursery objects named tg isn't too bad since it's an awful name, it almost surely will give false positives.

Hmm, we currently only match .*nursery\.start; I think (tg|.*(nursery|task_?group)\.start wouldn't have too many false alarms?  Important that we're looking at a method call not just the variable name though.

Ah yes, I was assuming I'll import over the type-tracking functionality used in 2xx

Searching github, I get >7k code results for "task_group", and 18k for "taskgroup" in python code - and skimming the first few pages I find that e.g. Apache AirFlow has something called task groups, and bunch of random people implementing whatever they call task groups. Searching for task_group.start() wasn't very fruitful though as github doesn't care for punctuation, so I get a lot of hits for task_group_start and stuff.
So it's definitely a relatively common name for Stuff:tm:, so it ends up becoming a tradeoff between false positives vs checking untyped code where task groups are sent around as parameters or other complicated stuff.

OK, let's just check based on types and the name "tg" then.  Thanks for investigating!

Related documentation things: we should have a tiny section listing deprecated anyio stuff that we don't lint for, including

anyio.open_cancel_scope() - let's also leave a comment on the cancel_scope_names constant that it's deliberately omitted
anyio.abc.TaskGroup.spawn(), which is deprecated in favor or .start_soon()
...actually there are nine of these, maybe we should have a lint rule for use of deprecated functionality?  ctrl-f "Deprecated since" on this page

Note also that handle = await anyio.open_process(...) is a separate function, where Trio would use handle = await nursery.start(trio.run_process, ...)

...actually there are nine of these, maybe we should have a lint rule for use of deprecated functionality? ctrl-f "Deprecated since" on this page

We do have TRIO117 for the deprecated MultiError, but that's a special case so a generic error code for deprecated library functions sounds good.

Went through the anyio API:
awaitable functions
I note that this is more comprehensive than we have for trio, where no submodule functions are checked.
    aclose_forcefully
    connect_tcp
    connect_unix
    create_connected_udp_socket
    create_tcp_listener
    create_udp_socket
    create_unix_listener
    getaddrinfo
    maybe_async
    open_file
    open_process
    run_process
    run_sync_in_worker_thread
    sleep
    sleep_forever
    sleep_until
    wait_all_tasks_blocked
    to_thread.run_sync
    to_thread.run_sync_in_worker_thread
    to_process.checkpoint_if_cancelled
    to_process.open_process
    to_process.run_sync
    lowlevel.cancel_shielded_checkpoint
    lowlevel.checkpoint
    lowlevel.checkpoint_if_cancelled

awaitable methods
Are just way too many and messy to list manually, so would either runtime generate these - or write some fancy thing to generate a hard-coded list. Or a lot of them aren't useful, and relevant ones can be hand-picked. But checking for them would be somewhat doable with the type-tracking, and not just do taskgroup.start
    anyio.abc.TaskGroup.spawn
    anyio.abc.BlockingPortal.sleep_until_stopped
    anyio.abc.BlockingPortal.stop
    anyio.AsyncFile.aclose
    anyio.abc.UnreliableObjectReceiveStream.receive
    anyio.abc.UnreliableObjectSendStream.send
    anyio.abc.ObjectStream.send_eof
    anyio.abc.ByteReceiveStream.receive
    anyio.abc.ByteSendStream.send
    anyio.abc.ByteStream.send_eof
    anyio.abc.Listener.serve
    # and many many more

deprecated functions
    abc.BlockingPortal.spawn_task
    abc.TaskGroup.spawn
    create_capacity_limiter
    create_condition
    create_event
    create_lock
    create_semaphore
    from_thread.create_blocking_bortal
    open_cancel_scope

stuff that shouldn't be awaited
https://github.com/agronholm/anyio/blob/5d9a476d6e3e6b6d7b1876fa18e70cd910d2e7e7/docs/migration.rst
With AnyIO 3 they made a bunch of previously async stuff sync, some most of which return resources that can be awaited - but will give deprecationwarning.
The transition from AnyIO 2 to 3 seems to have been ~1.5 years ago, but shouldn't be much effort to also check these.
functions
    current_time
    current_effective_deadline
    get_current_task
    get_running_tasks
    open_signal_receiver

methods
    anyio.abc.CancelScope.cancel
    CapacityLimiter.acquire_nowait
    CapacityLimiter.acquire_on_behalf_of_nowait
    Condition.release
    Event.set
    Lock.release
    Semaphore.release
    MemoryObjectReceiveStream.receive_nowait  # <.streams.memory.MemoryObjectReceiveStream.receive_nowait>`
    MemoryObjectSendStream.send_nowait  # <.streams.memory.MemoryObjectSendStream.send_nowait>`

context managers
    fail_after
    move_on_after
    open_cancel_scope # is deprecated

I'm inclined to leave out awaitable methods (except tg.start) as not high enough priority to be worth the trouble at the moment, and leave deprecated don't-await-this to the runtime system since they'll go away at some point without us.

Sounds good, I'll leave those out for the time being and can consider revisiting them later. Any code for awaitable methods would of course be reusable for Trio methods, and don't-await-this could also be extended to check all non-async functions in trio/anyio.
I'm a bit vary of matching the variable name of tg as well - I find at least two instances of tg.start() where tg is short for Telegram, but mostly because I think most/all instances will be caught by type tracking on anyio.create_task_group(). And I think the plugin could also be extended to handle stuff like from anyio import create_task_group without much effort in future PRs thanks to the shared state/variable stuff. So I think the only additional thing it will catch is a function taking a task group as a parameter, untyped, named tg.

Ah, awaiting non-awaitable functions/methods is picked up by type checkers - which makes it somewhat redundant, though requires strict typing of return values.

Let's leave this to typecheckers; illegal-await is also an immediate error at runtime and thus easier to debug than missing-await errors.

Ooh, mypy 1.0.0 does give me

tests/eval_files/trio113.py:12: error: Value of type "Coroutine[Any, Any, object]" must be used  [unused-coroutine]
tests/eval_files/trio113.py:12: note: Are you missing an await?

now when I write
async with anyio.create_task_group() as bar:
    bar.start(my_callable)  # TRIO113: 8, anyio.TaskGroup.start

And it catches all the awaitable library functions as well ... so there's maybe a decent case for skipping TRIO105 for anyio and just tell people to use mypy? (pyright does not give the warning, did not check other ones)
I tried installing trio.typing and enabling it's plugin to see if it would catch the trio one as well - but it didn't. So should maybe spend some time figuring out what part of trio's magic breaks that check.

Yeah, let's stick with the status quo then.
Low priority, I'd like to work out why pyright doesn't do this and get mypy working for Trio, but that's definitely lower-priority than e.g. LibCST.

Coolies. I will push a PR with some modifications to type tracking and nurseries I implemented before I realized this, but otherwise revert most modifications.
Oh nvm, pyright does have support for it - but since eval_files are in the exclude list it didn't say anything even when explicitly passed the file :sweat_smile:
So this falls under "static typing improvements for Trio" in the TODO, I might do some more testing/looking around and then maybe open an issue / comment on some existing typing issue in trio.


Minimal Tokens Exercise

Implement a solution for the Minimal Tokens Exercise.

Submitted to Base Goerli: https://goerli.basescan.org/address/0xF0bd02c87f42F920d498d964ee87311DBCc0eFeC#code


Support CVSSS3 scoring on results

safety version:Lastest
Python version:3
Operating System:Linux

Description
When its possible, Its can be good idea to put CVSS3 metric inside output results for better understanding.

We do offer this, actually. But only for enterprise account…


feat(lane_change): add text display for candidate path sampling metrics

Description
Display candidate path sampling metrics for prepare phase and lane changing phase on rviz to help with debugging.

Related links
None.

How was this PR tested?

PSIM

Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

I was thinking to add "Accepted" and "Rejected" path for indication. How do you think about it?


MUI 5 is not supporting MUI 4 Implementation, syntax, please add reverse comparability

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
please ensure reverse compatibility for upcoming updates
Examples 🌈
No response
Motivation 🔦
No response

Can you provide more details? otherwise, there is nothing that we can follow up.


Audit log GraphQL API

Background
This pull request introduces new modules titled Audit Log. The audit logs comprehensively document all user activities and system events, organized by each organization.
Description

A new GraphQL schema has been established, along with the creation of an interface named AuditLog.
Audit log cases have been implemented by developing a new type that adheres to the AuditLog interface.
A new provider, named AuditLogManager, has been created with Clickhouse to facilitate database updates. This provider offers three primary functions:

createLogAuditEvent: Utilized for inserting new log/event data.
getPaginatedAuditLogs: Employed for retrieving all data from the database.
getAuditLogsCount: Used to count the total number of records in the database.

The provider oversees the event/record type through a new type called AuditLogEvent, with each case accompanied by a zod schema to enhance type safety.
Currently, I have included a single example of a case that records user activity - you can see it here, and I welcome feedback on the next steps.

@kamilkisiela @dotansimha @n1ru4l
I would appreciate your thoughts on this and any suggestions for modifications

Please add integration tests for:

creation: create org, do some actions, check the DB for logs, check the GraphQL layer, and verify response matches.
access control: create org, invite a new user, do some actions, and make sure only the owner can access and query the audit logs
data correction: query GraphQL and check response makes sense and is valid


[BUG][Android][Plugfest #4] Crash CHIPTool when read invalid String attribute

Reproduction steps

Commissioning device using Android CHIPTool
Read attributes string type.
Crash when parsing String hex.

08-14 09:30:05.986 F 15822    15927    e.chip.chiptoo:                                                                     java_vm_ext.cc:577] JNI DETECTED ERROR IN APPLICATION: input is not valid Modified UTF-8: illegal continuation byte 0
08-14 09:30:05.986 F 15822    15927    e.chip.chiptoo:                                                                     java_vm_ext.cc:577]     string: tfm_bas�
08-14 09:30:05.986 F 15822    15927    e.chip.chiptoo:                                                                     java_vm_ext.cc:577]     input: 0x74 0x66 0x6d 0x5f 0x62 0x61 0x73 0xd5
08-14 09:30:05.986 F 15822    15927    e.chip.chiptoo:                                                                     java_vm_ext.cc:577]     in call to NewStringUTF
Bug prevalence
read attribute with specific device.
GitHub hash of the SDK that was being used
ce0ddc035143117d9193eb5b59647a7dd957aea0
Platform
android
Platform Version(s)
master
Anything else?
During testing in Plugfest 4, while analyzing the issue, the same crash occurs in Android CHIPTool, so an issue is registered.

@joonhaengHeo what property did you try to set to 0x74 0x66 0x6d 0x5f 0x62 0x61 0x73 0xd5 ? It seems this tries to assign a non-utf8 string to a string.
I am trying to figure out if matter spec require UTF8 or not but cannot see any obvious text where the data type string is defined ... but utf8 seems often reasonable when a separate "octet string" exists.

Trying to figure out if the fix should be instead an exception rather than allowing invalid utf8.

@andy31415
As explained above, this issue is from Plugfest.
When trying to read a specific attribute, it was confirmed that 0x74 0x66 0x6d 0x5f 0x62 0x61 0x73 0xd5 values were read, and a crash occurred due to this value.
(0x34 - Software Diagnostics, 0x00 - ThreadMetrics)
Detailed log
08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 		  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 		AttributeReportIB =  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 		{  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 			AttributeDataIB =  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 			{  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 				DataVersion = 0x43495aa5,  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 				AttributePathIB =  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 				{  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					Endpoint = 0x0,  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					Cluster = 0x34,  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					Attribute = 0x0000_0000,  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					ListIndex = Null,  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 				}  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 				Data =   08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 				{  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					0x0 = 11,   08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					0x1 = "tfm_bas�" (8 chars),   08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					0x3 = 879,   08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 					0x4 = 16777344,   08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 				},  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 			},  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 			  08-14 09:30:05.977 D 15822    15927    DMG                                                                                : 		},

My goal is also not to crash.
However, since this value is also read normally in chip-tool, I modified it in a way that can be read.
Do you think it is right to generate an error in your opinion?


fix capitalization on some files

Codecov Report

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

@@           Coverage Diff           @@
##           master      #42   +/-   ##
=======================================
  Coverage   83.63%   83.63%
=======================================
  Files          21       21
  Lines        2255     2255
=======================================
  Hits         1886     1886
  Misses        369      369

Impacted Files
Coverage Δ

src/CI.jl
88.86% <ø> (ø)

src/ClinicalTrialUtilities.jl
100.00% <ø> (ø)

src/Export.jl
92.98% <ø> (ø)

src/PK.jl
86.57% <ø> (ø)

src/SIM.jl
87.09% <ø> (ø)

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 127dfcb...4e4bb56. Read the comment docs.

Hi!
It's my fault - I have made wrong commit to master branch and changed file names. Thank you for pull request! This was very helpful. I renamed files back and bumped new minor release with some fixes and coverage. Best regards!


Add Vertex Slitherlink and Touch Slitherlink

Adds vslither and tslither as extensions to slither. Should have all of the necessary error checking, fail codes, rules, and test puzzles

Need to fix formatting


Retry if a github call temporarily fails

I don't know what is the best approach to overcome this, but in the last weeks it happens more and more often that our internal publisher pipeline fails, because workflow runs cannot be retrieved (temporarily). See for instance this pipeline.
What we see in the logs is, e.g.:
$ 'git ls-remote https://github.com/ITISFoundation/ML-TensorFlow-application refs/heads/main -q'
==================================================
GENERATED PIPELINE
==================================================
stages:
    - info
no-further-action-required:
    image: $CI_SERVICE_INTEGRATION_LIBRARY
    tags:
    stage: info
    tags:
        - DOCKER
        - XSERVER
        - GPU
        - LINUX
    script:
        - echo "Nothing required updates. No builds scheduled."
==================================================
Traceback (most recent call last):
  File "/.pyenv/versions/3.10.10/bin/dpos", line 33, in <module>
    sys.exit(load_entry_point('docker-publisher-osparc-services==0.0.1', 'console_scripts', 'dpos')())
  File "/.pyenv/versions/3.10.10/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/.pyenv/versions/3.10.10/lib/python3.10/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/.pyenv/versions/3.10.10/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/.pyenv/versions/3.10.10/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/.pyenv/versions/3.10.10/lib/python3.10/site-packages/docker_publisher_osparc_services/cli.py", line 129, in main
    asyncio.get_event_loop().run_until_complete(run_command(config))
  File "/.pyenv/versions/3.10.10/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/.pyenv/versions/3.10.10/lib/python3.10/site-packages/docker_publisher_osparc_services/cli.py", line 35, in run_command
    if not await did_ci_pass(repo_model, branch_hash):
  File "/.pyenv/versions/3.10.10/lib/python3.10/site-packages/docker_publisher_osparc_services/operations.py", line 47, in did_ci_pass
    return await github_did_last_repo_run_pass(repo_model, branch_hash)
  File "/.pyenv/versions/3.10.10/lib/python3.10/site-packages/docker_publisher_osparc_services/http_interface.py", line 28, in github_did_last_repo_run_pass
    for run in runs["workflow_runs"]:
KeyError: 'workflow_runs'

This is blocking me atm. Do we know by chance why this happens? Are we hitting some github api limits or so?

I saw that unauthenticated github API request are limited to 60/hour:
https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28
That could be it?
Maybe we should consider creating a github account for these request?

This could be it, since we are sharing it with a big pool of users.
I can add the authentication options to aid you wit this.

Yeah, that would be great. I assume the 5000/hour would be enough, especially if we make dedicated users for each CI plan.

added release v2.0.0 which should take care of this

👍🏻 thx!

Pipeline was also updated and works with the new GitHub Token.

Works perfectly 🥇


Is It possible to get browser version?

Hello,
Is it possible to get the version of browser ?
I do This
const cluster = await Cluster.launch({
    concurrency: Cluster.CONCURRENCY_CONTEXT,
    maxConcurrency: 2,
    monitor: true,
    retryLimit: 0,
    timeout: 180000,
    }
  });

await cluster.queue('www.example.com', main);

// Display browser version
// console.log(cluster.browser.version()) ?

const main = async ({ page, data: url }) => {
    await page.goto(url);
    const results = await page.evaluate(async () => {
    debugger;
      let title = document.title;
      return title;
    }).then((data) => {
      console.log(data);
    });
  };

Right now you cannot access the browser directly. What you can do is require puppeteer yourself and check the version there.

Actually, I was wrong. You can do it like this: const version = await page.browser().version();


store-<IP_ADDRESS> test fail: Data.Store, Manually listed polymorphic store instances, Roundtrips

In Stackage Nightly build for stackage-curator:
Failures:

  test/Data/StoreSpec.hs:287:
  1) Data.Store, Manually listed polymorphic store instances, Roundtrips (GHC.Real.Ratio GHC.Int.Int8)
       uncaught exception: ArithException (arithmetic overflow)

  test/Data/StoreSpec.hs:287:
  2) Data.Store, Manually listed polymorphic store instances, Roundtrips (GHC.Real.Ratio GHC.Int.Int64)
       uncaught exception: ArithException (arithmetic overflow)

The tests passed on stackage just now, so afaik this can be closed.


Update microlp, adding integer variables

This is the only one i was able to find, the one in mipgap is not available for microlp


Helm chart - rbac objects should iterate over SE_K8S__deployment__namespaces

The namespaced rbac resources should be decoupled from the deployment namespace of the streams-explorer.
For example, in our cluster, we deploy streams-explorer in infra and plan to discover stream apps in data and app.
I feel this is a valid use case and should be supported by the helm chart:
Proposal:

Role becomes a ClusterRole
a RoleBinding from CR to SA is created on a per namespace basis.
this effectively binds the CR to the target namespaces.
this can be made optional by introducing

rbac:
  enabled: true
  clusterScope:
     enabled: true
     namespaces: ["apps", "data"]

Hi @twiechert, thank you for the proposal. We think it's a good idea and I'll take a look into it as soon as I find the time


[GLUTEN-7291][DELTA] fix: push down input_file_name expression to transformer scan in delta

What changes were proposed in this pull request?
This PR aims to push down input_file_name expression to transformer scan in delta.
(Fixes: #7291)
How was this patch tested?
Add new unit test.

@yma11 could you please have a review? thanks


Clean up JNI and improve freeing native memory (CBL-130)

Used only public API except for RefCounted

Use FLSlice instead of slice.
Use FLSliceResult instead of AllocSlice.
Use FLEncoder instead of Encoder and fix some bugs in FLEncoder.

Instead of freeing FLSliceResult in finalize(), make sure the consumer codes call free() method. This will match the way FLSliceResult is used natively.
Instead of freeing FLEncoder in finalize(), make sure the customer codes call free() method. This will match the way FLSliceResult is used natively.
Ensured to reset the shared FLEncoder after using it.
Fixed bug in jstringSlice C++ class when the string is null. This seems to cause a lot of memory issue (bad_alloc) when changing to use FLSlice instead of slice.

I fixed error reported by checkstyle and findbugs and did force-push.


add more and clear Trim function support

add more and clear Trim function support

Codecov Report

Merging #63 into master will decrease coverage by 0.40%.
The diff coverage is 94.87%.

@@            Coverage Diff             @@
##           master      #63      +/-   ##
==========================================
- Coverage   92.83%   92.43%   -0.41%
==========================================
  Files          10       11       +1
  Lines         810      820      +10
==========================================
+ Hits          752      758       +6
- Misses         39       41       +2
- Partials       19       21       +2

Impacted Files
Coverage Δ

gse.go
93.22% <ø> (-3.64%)
:arrow_down:

trim.go
94.87% <94.87%> (ø)

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 bcd06f9...8b4ea84. Read the comment docs.


Failure on tests/posix/common/ due to uninitialized memory access

Randomly, the test crashes with an assert. The cause would seem to be the one detected by valgrind (see log below)
Steps to reproduce
On ae8649c5ec59b483615c0348ebcb8da6e346a1ce
cmake ../tests/posix/common/ -DBOARD=native_posix -GNinja
ninja
valgrind zephyr/zephyr.exe

Log
***** Booting Zephyr OS v1.9.0-8074-gae8649c5ec *****
Running test suite posix_apis
===================================================================
starting test - test_posix_pthread_execution
==17094== Thread 2:
==17094== Conditional jump or move depends on uninitialised value(s)
==17094==    at 0x10D74C: zap_pthread_attr_setschedparam (pthread.c:89)
==17094==    by 0x10A97E: test_posix_pthread_execution (pthread.c:249)
==17094==    by 0x110800: run_test_functions (ztest.c:58)
==17094==    by 0x110800: test_cb (ztest.c:195)
==17094==    by 0x10C17E: _thread_entry (thread_entry.c:29)
==17094==    by 0x10CE61: posix_thread_starter (posix_core.c:301)
==17094==    by 0x495D3BC: start_thread (pthread_create.c:463)
==17094==    by 0x4A6EE15: clone (clone.S:108)
==17094==
==17094== Conditional jump or move depends on uninitialised value(s)
==17094==    at 0x10DDE6: valid_posix_policy (pthread_sched.c:12)
==17094==    by 0x10DDE6: zap_sched_get_priority_min (pthread_sched.c:26)
==17094==    by 0x10D75E: is_posix_prio_valid (pthread.c:42)
==17094==    by 0x10D75E: zap_pthread_attr_setschedparam (pthread.c:90)
==17094==    by 0x10A97E: test_posix_pthread_execution (pthread.c:249)
==17094==    by 0x110800: run_test_functions (ztest.c:58)
==17094==    by 0x110800: test_cb (ztest.c:195)
==17094==    by 0x10C17E: _thread_entry (thread_entry.c:29)
==17094==    by 0x10CE61: posix_thread_starter (posix_core.c:301)
==17094==    by 0x495D3BC: start_thread (pthread_create.c:463)
==17094==    by 0x4A6EE15: clone (clone.S:108)
==17094==
==17094== Conditional jump or move depends on uninitialised value(s)
==17094==    at 0x10DE07: valid_posix_policy (pthread_sched.c:12)
==17094==    by 0x10DE07: zap_sched_get_priority_max (pthread_sched.c:54)
==17094==    by 0x10D76E: is_posix_prio_valid (pthread.c:43)
==17094==    by 0x10D76E: zap_pthread_attr_setschedparam (pthread.c:90)
==17094==    by 0x10A97E: test_posix_pthread_execution (pthread.c:249)
==17094==    by 0x110800: run_test_functions (ztest.c:58)
==17094==    by 0x110800: test_cb (ztest.c:195)
==17094==    by 0x10C17E: _thread_entry (thread_entry.c:29)
==17094==    by 0x10CE61: posix_thread_starter (posix_core.c:301)
==17094==    by 0x495D3BC: start_thread (pthread_create.c:463)
==17094==    by 0x4A6EE15: clone (clone.S:108)
==17094==

    Assertion failed at /home/alpi/aescolar-ot/tests/posix/common/src/pthread.c:250: test_posix_pthread_execution: (ret not equal to EINVAL)
uninitialized attr set!
FAIL - test_posix_pthread_execution
[...]

@nashif : Please reassign to whoever is maintaining this area.

#10508 also reports the same issue. Possibly any one of the issues can be closed.

Correct, feel free to close this one.


[examples] Failing examples, overview of the current state

Ref : ubuntu, with mechanisms (oce, pythonocc and bullet)
https://cdash-tripop.inrialpes.fr/viewTest.php?onlyfailed&buildid=2242

Todo for each failing example : fix or move to .sandbox (in siconos-tutorials)
Remark : same build for release 4.2.0 leads to :
https://cdash-tripop.inrialpes.fr/viewTest.php?onlyfailed&buildid=2245

Most of python examples are working (eg BouncingBall and many others),
only those depending on bullet and oce where not included in the examples/test process.
There was a bug in SICONOS_HAS_BULLET/OCE setting.
Moreover, examples to be processed must be explicitly set in examples/CMakeLists.txt, which was
not the case for mechanic/GeometricPrimitives mechanic/GranularMaterial
I think (hope) the last commits in siconos and siconos-tutorials fix this.
We'll see that on cdash.


NG0204: Token InjectionToken X is missing a ɵprov definition after Angular 15 upgrade

After updating to Angular 15, components with the following setup fail with NG0204: Token InjectionToken X is missing a ɵprov definition.
import {
  ChangeDetectionStrategy,
  Component,
  InjectionToken,
  Input,
} from '@angular/core';
import { UntilDestroy } from '@ngneat/until-destroy';

export const FAB_ITEM = new InjectionToken<any>('FAB_ITEM');

@UntilDestroy()
@Component({
  selector: 'aw-fab-item',
  templateUrl: 'fab-item.component.html',
  changeDetection: ChangeDetectionStrategy.OnPush,
  providers: [{ provide: FAB_ITEM, useExisting: FabItemComponent }],
})
export class FabItemComponent {
  @Input() disabled = false;
}

The error dissapears and the component works after removing the UntilDestroy decorator.

Could you please provide a minimal reproducible example?

Closing as not reproducible. We have an integration app in this repository which is running with Angular 15.
Feel free to re-open the issue once you're able to provide a reproducible example.

Got the same issue after migration to angular 15.

I saw that the repo was upgradet to angular 15. Could we get a new release? Maybe this fix the issue.

Well, I could’ve published a new version but I’d want to double check to ensure this is related to a new version. Because that might be an unnecessary publish. I need a reproducible example gentlemen.

Could you publish a dev version so that I can check against my project?

I'm using Angular v15, and I don't have an issue. It'll be helpful if you can reproduce it.

I have had something similar since the upgrade to Angular 15.
We have a use case where we want to get a MatFormFieldControl from a ControlValueAccessor component implementing the MatFormFieldControl that is injected using the Content Projection.
  @ContentChild(MatFormFieldControl, { static: true })
  private formFieldControl!: MatFormFieldControl<unknown>;

  ngOnInit(): void {
    this.matFormField._control = this.formFieldControl;

For MatFormFieldControl components that have the UntilDestroy() decorator, the this.formFieldControl is empty
When you remove the decorator, it works well again.
I'll try to provide a reproducible case today

I was not able to reproduce our issue on a clean project TBH.
We are still investigating why it is failing by removing all codes around.
Even if I remove the code within the decorator it is failing.
Just the fact that we set the decorator has an impact on our @ContentChild reaction.
I think this is related to https://github.com/angular/angular/issues/48276 but no idea what is the reason.

Even trying that approach it fails:
function UntilDestroy(options = {}) {
  return (type: unknown) => {};
}

@UntilDestroy()
@Component({
...

So at least, this is not related to this library ;)

To be honest I have issues in other libraries as well related to decorators. But it’s usually not a library issue but something related to the application.
Since I’ve seen already some issues related to decorators this means there actually has been some change in the TS compiler or Angular compiler that might affect it.

this typescript issue seems to be related

Yeah, I haven't got my hands yet to going through the Angular 15 release completely. In other libraries this is being solved by playing around with useDefineForClassFields.

Have to re-open the issue because I also experience it in one of my apps (haven't met it earlier):
Error: NG0204: Token InjectionToken NgValueAccessor is missing a ɵprov definition.

@jogelin I have experienced this issue with a control value accessor too. I have fixed it with the forwardRef.
Before:
provide: NG_VALUE_ACCESSOR,
useExisting: CosAutocompleteComponent

After:
provide: NG_VALUE_ACCESSOR,
useExisting: forwardRef(() => CosAutocompleteComponent),

Your thoughts?
P.S. I know it wasn't necessary to use forwardRef since Ivy has been released (because component definition appeared after the class itself, thus there has been no reason to "capture" the class reference).

Ok, I just doubled checked my app and the issue wasn’t related to this library. Sorry for pinging anyone who’s subscribed to this issue.

@jogelin I have experienced this issue with a control value accessor too. I have fixed it with the forwardRef.
Before:
provide: NG_VALUE_ACCESSOR,
useExisting: CosAutocompleteComponent

After:
provide: NG_VALUE_ACCESSOR,
useExisting: forwardRef(() => CosAutocompleteComponent),

Your thoughts?
P.S. I know it wasn't necessary to use forwardRef since Ivy has been released (because component definition appeared after the class itself, thus there has been no reason to "capture" the class reference).

Seems to work too :)


Added "Humidity_Transport" in sensor.py

Added "Humidity_Transport" to show "Feuchtetransport" in HA
ABS_HUM_MEASURES = [
"abs_Humidity_In",
"abs_Humidity_Out",
"Humidity_Transport",
]

Hi @MaxiKingXXL
I appreciate the request to improve this package! It looks like you created this change through the WebUI of Github - which makes me believe you did not test this change locally to ensure that it will work properly.
Please try this change out in your local home-assistant installation first and report back with the results in your UI and the reported success.
For creating this patch you have already created a fork of the project, which you should be able to add in HACS as custom repository and load/try the changes in your own setup. Note it might be you need to merge your patch branch (patch-1) into master in your own fork before the changes take effect.

Hi @nielstron
I have tested this change on my local HA environment already and the correct "Feuchtetransport" value show up properly.
But you are right that the unit is not matching which I overlooked. :)  The Humidity_Transport is in g/24h.
Maybe just GRAMS = "g" as unit would fit better here.
The is my first change request in github ever and I'm also new in Python. I would be grateful is you could help to with this change.

That's good to know! To change the unit type, it would be easiest to introduce a new sensor list/map for this class - you see the two lists for abs and rel humidity sensors are grouped together since they share the unit type.
Grams seems unlikely to be the right unit - is it grams/s or grams/24h or something like that? grams would imply it is the accumulated total

Hi @MaxiKingXXL
I adjusted your PR so that humidity transport should now have the correct unit. Can you please check if it behaves as expected?

@nielstron Thanks, for making this change. But for it doesn't show up. Might it be possible that you have nit check in the latest change in sensor.py?

I did not test it yet. I'll try to setup homeassistant with a mock server, then merge into master


extensions: support disabling the grpc http1 reverse bridge filter per-route

Support disabling the filter per route in the grpc http1 reverse bridge filter.
Risk Level: low (adds per-filter config)
Testing: unit tests added
Docs: inline
Release Notes: updated
Fixes: #8052
Signed-off-by: Manuel Jurado<EMAIL_ADDRESS>

@zuercher code review fixed.
Thank you very much for your review.

@htuch and/or @mattklein123 this is ready for API review

Please merge master and fix format to pick up the next free field annotations.
/wait

Please merge master and fix format to pick up the next free field annotations.

@mattklein123 done /cc @zuercher @snowp @htuch
Thx!

Please merge master and fix format to pick up the next free field annotations.

@mattklein123 done /cc @htuch @zuercher @snowp
thx!

Thank you @mattklein123


@export-ing a const preload() crashes Godot.

Godot version
v4.0.beta4.mono.official [e6751549c]
System information
Linux Mint 21.1
Issue description
When in the Godot code editor, the entire program will instantly crash when writing a const foo = preload("res://someScript.gd"), followed by an @export statement for a variable of the just preloaded type.
Steps to reproduce

Create a new Godot project.
Create foo.gd like this:

extends Node

Create another script like this:

extends Node

const Foo = preload("res://foo.gd")

@export
var foo: Foo

Godot should have become unresponsive, then closed itself on step 3.

Minimal reproduction project
Note: This project is missing the second o in Foo in exporter.gd since, as soon as I type it, the engine crashes without saving.
GodotBug#71078.zip

@Psychpsyo Please test on the latest beta to see if the issue is still present before creating an issue.
Just tested on master (fcba87e) and I couldn't reproduce.

I confirm the crash on beta 4, but we're at beta 10 already, and it's already fixed.
@akien-mga We can close this issue.


fork ufo2fdk?

Currently ufo2ft shows up in github as "forked" from typesupply/ufo2fdk.
However, given the drastic changes to the api, I don't think the intention is to fold ufo2ft back in ufo2fdk repo.
If that is the case, then @jamesgk could delete the current ufo2ft repo, create a new Github repo called again "ufo2ft" and push his local copy to the new remote.
This way, Github will see it as an independent repository, instead of a fork of someone else's repo. The commit history will be kept intact however.
This would allow others to fork directly from James' "ufo2ft". At the moment, in fact, if one tries to fork from ufo2ft, Github will not allow it if the user has already forked ufo2fdk.
I had to resort to special "ufo2ft-*" branch names on my "hybrid" anthrotype/ufo2fdk fork, in order to be able to track both typesupply/ufo2fdk and jamesgk/ufo2ft...

You can also ask support to switch the repository to a distinct one.

You can unlink the repos without deleting anything. Just email
<EMAIL_ADDRESS>

well, even better then. Whatever works for you.

OK, ufo2ft has been extracted from ufo2fdk. This means that we adopted ufo2fdk's ufo3 branch, which frankly I want to get rid of asap. I don't want to worry about maintaining two separate branches -- for now I just want to incorporate ufo3 support as long as it's compatible with ufo2.

As I told you before, the difference is mainly kerning prefixes. The ufo3 branch of ufo2fdk also drops heuristic to extract kerning groups from any group since in ufo3 kerning groups have a well-defined prefix.
I don't think that there is much difference besides that.

ufo2ft is now distinct, and the ufo3 branch is deleted. I'm gonna close this.


Refactor Cppcheck output folder creation

The root folder creation might be redundant. In #3680  @whisperity suggested a new approach to do it:

Remove root folder creation
"Use os.makedirs instead, so it creates the parent directories, and then the other call might truly be redundant."
This is a follow up issue to #3680 .

In general, if there are problems with how Cppcheck behaves, we should investigate the versions that need to be supported and how those versions behave, and create a hard version requirement before releasing the feature. Cppcheck is being added as a new feature, this is the time where the contract can be pulled tight.


bingoArry entries with faulty errors

Issue:

User1 submits "100"
User2 submits "1" or "10" and it states the number exists in the array, even when the only number in the array is 100.

Due to the following line.
code:
if jsonPlayRecord["number"] in jsonArry["number"]:                     print(colored('number present in array, aborting','red'))                     await cmd.reply('Number selected by another user, try again!')                     print('==============================================================')                     break
Changed the logic and testing fix now

Issue fixed with latest push


Is there any way to avoid the user icon rotation?

How can I avoid the rotation of the user marker when is tracking it's location?
It rotates and does not make too much sense how is showing, I prefer an static horizontal image.
BR.

Thanks so much @liodali, your reply is appreciated.

check new version 0.53.0
we added attribute disableUserMarkerRotation in enableTracking set it to true
to disable the rotation


omnisharp-roslyn: drop .NET 7 test, refactor

Description of changes

omnisharp-roslyn: format
omnisharp-roslyn: move to pkgs/by-name
omnisharp-roslyn: drop test for .NET 7 - https://github.com/NixOS/nixpkgs/issues/326335
omnisharp-roslyn: set passthru.updateScript
omnisharp-roslyn: ignore beta releases for update script
omnisharp-roslyn: add maintainer gepbird

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 343690

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 343690

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 343690


sound-based records erroneously getting annotated as 'Photograph' in the voucher type column

iNat records with only sound recordings (eg https://www.inaturalist.org/observations/175522145) that are in the ALA (https://biocache.ala.org.au/occurrences/86488ecf-b65a-4c02-bdc6-8280bc14277e) are getting pulled in by the app. This is good and working as expected. However, they are getting annotated as 'Photograph' in our voucher type column, which is not desirable given it's misleading.
How can we annotate these records correctly in the voucher type column? The 'record type' field in the ALA does not differentiate between photos and sounds (they all get called 'human observation')

cc_occurrences <-
galah_call() |>
galah_identify("Cicadoidea") |>
galah_filter(year == 2022) |>
galah_select(group = c("basic"), sounds,imageID, basisOfRecord) |>
atlas_occurrences()
Better case_when using sounds, imageID and basisOfRecord when creating Voucher type

this is done on the alalink branch, but not ready to merge yet

done


Update Github actions

@clintonb Thanks for the review. All tests are passing, it's ready to merge.


Missing referenced script

Hello,
In the documentation, you talk about "Maintain a service catalog of your Azure fully qualified domain name (FQDN) endpoints and the application owners. To build your service catalog, run the following Azure Resource Graph query script". Where is this script?
Thank you

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 647e9a22-fedf-a3d6-5bb3-54b635bdfba4
Version Independent ID: a35040bc-5e45-0514-fd49-e4b97813ed98
Content: Prevent subdomain takeovers with Azure DNS alias records and Azure App Service's custom domain verification
Content Source: articles/security/fundamentals/subdomain-takeover.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @memildin
Microsoft Alias: memildin

@bertrandpons  Thanks for the feedback. We will engage the content development team for further investigation, they will verify and perform necessary changes in the document as needed.
@memildin Can you have a look at this ?

Hi @bertrandpons, thanks for the feedback and for taking the time to help us improve the docs.
The script is referenced in the "Run the script" section of the page. That section talks about Azure Resource Graph and "running the query". In a future version we'll try to make it even clearer.
I'm going to close this issue, but feel free to comment again here or open a new one if you have additional requests.
#please-close


Helm Not Accessible in Rancher after helm init

Rancher versions:
rancher/server or rancher/rancher: 2.0.6
rancher/agent or rancher/rancher-agent: 2.0.6
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable): 1.10.5
Docker version: (docker version,docker info preferred) 17.03.2-ce
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
NAME="RancherOS"
VERSION=v1.4.0
ID=rancheros
ID_LIKE=
VERSION_ID=v1.4.0
PRETTY_NAME="RancherOS v1.4.0"
HOME_URL="http://rancher.com/rancher-os/"
SUPPORT_URL="https://forums.rancher.com/c/rancher-os"
BUG_REPORT_URL="https://github.com/rancher/os/issues"
BUILD_ID=

Helm Version:
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO): AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB): Single Node, HA-Kubernetes Cluster
Environment Template: (Cattle/Kubernetes/Swarm/Mesos): Kubernetes
Steps to Reproduce:

Spin up Kubernetes cluster with AWS cloud provider
Grab the KubeConfig from the Rancher UI
Create tiller service account
Instantiate Helm using helm init --service-account tiller

Results:
Any Helm command (helm ls, helm install, helm upgrade) returns the error:
error: error upgrading connection: Upgrade request required

I believe it has to do with how Rancher is proxying requests into the Kubernetes cluster.   Exposing tiller on host networking or by exposing a node port seems to be working.   I found this related issue:  https://github.com/rancher/rancher/issues/7303  in which the reporting user indicates that their issue was resolved by exporting a nodeport as the $HELM_HOST variable.  However, I think this should work by default.
Please see this corresponding Gist with more verbose details:   https://gist.github.com/aric49/091cad31e6cfd429c715e14d4fb546ea
Any assistance is greatly appreciated!  Thank you in advance.

After debugging, I discovered that this issue seems to be related to the Amazon Application LoadBalancer I configured in front of our Rancher server.  I discovered during this time that commands such as kubectl exec, kubectl logs, and kubectl port-forward all seem to fail with the same error message.   I tried experimenting with using an ELB instead of an ALB and the same issue persists.
Eventually, I was able to work around this issue by bypassing the load balancer all together and issue requests directly to the Rancher server.   It appears as though Amazon load balancers are filtering out some traffic that Kubernetes expects.
I found in the Rancher 1.6 docs a disclaimer about using an ELB as opposed to an ALB, and directing traffic to port 8080 but I believe this is deprecated since it appears that the rancher/rancher docker image does not listen on port 8080:     https://rancher.com/docs/rancher/v1.6/en/installing-rancher/installing-server/basic-ssl-config/#enabling-proxy-protocol
Any futher help with this issue is greatly appreciated.   I am somewhat satisfied with the workaround I discovered, but would ultimately like to be able to use some type of load balancer for kubectl traffic as opposed to just WebUI management.

thanks for the Q&A, close it now as LB config cloud be a separate thread for the helm init topic, thanks.


Update (initialization) helpers

Adds helper function to initialize GPIOs, this avoids having to configure and initialize GPIOs in the drivers init function.
Closes #128
Any suggestions with the name of the function are welcome. Same with lvgl_driver_init, now it only initializes the SPI/I2C peripheral.

Is it related to the new architecture?

Kind of, I'm removing the GPIO initialization from the display drivers to a more generic way.
So at the end there would not be any GPIO specific code in the display driver init function.

I think it's a great direction. I was also thinking about it, and concluded that GPIOs can be handled in the display_send, indev_read functions too along with the  SPI/I2C peripheries.

DC pin also can be managed in the SPI driver.

Isn't it? :smile:
E.g. a send_cmd can handle the DC pin too. Or have I missed something?


Shader split

In this PR the experimental/shader-split branch will be merged manually. These are the steps:

[x] BufferHandler und Buffer
[x] Pass, Pipeline
[x] PushConstant(s)
[x] Initializers
[x] Fence (move from VulkanEngine) (Called newFence until old Fence is gone)
[x] New shaders
[ ] Merge the rest (sadly this cannot be divided further)
[ ] PushConstant(s) cleanup
[ ] Pipeline cleanup
[ ] Buffer cleanup

Put on ice for now until we decide to have enough time to do Vulkan optimizations.


Fix array creation for ndarray list of arrays of different dtypes

Fix #3576.

Jenkins, test this please

Jenkins CI test (for commit b6dac744bf159b64ae1b1509c558b714db763131, target branch master) succeeded!

@emcastillo This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?


ISPN-6323 Cluster startup hangs indefinitely in client-server mode

avoid creation of remote query components for internal caches because the starting of __protobuf_metadata cache may lead to deadlock

Jira: https://issues.jboss.org/browse/ISPN-6323

Pushed, thanks


1596 introduce links to header flag popovers

Delivers #1596.
This required a bit of fussing about and resulted in the creation a new panel to represent the header flag popover content.  It takes the form of HeaderFlagPopoverPanel.

Looks good @payten, though conflicts :(

Thanks @steveswinsburg. Rebased and happy.


Window title = Gnuplot (window id: 0)

Hi,
When I use the lib on Ubuntu, a popup is titled Gnuplot (window id: 0)
It's ugly. How can I change it?

http://stackoverflow.com/questions/18643489/changing-gnuplot-graph-window-name


Unable to use kubeless installed in any namespace other than 'kubeless'

You can see here the default namespace to look for the config-map is 'kubeless':
https://github.com/serverless/serverless-kubeless/blob/master/lib/config.js#L25
And you can see here that the Config object is constructed with no other options given:
https://github.com/serverless/serverless-kubeless/blob/master/deploy/kubelessDeploy.js#L84
Thus the config-map is only ever able to be fetched from the 'kubeless' namespace.

Yes, that's correct. Would you able to send a PR to fix that? The easiest solution would be to read an env var at that point. The kubeless CLI uses KUBELESS_NAMESPACE for that.

Sure I'll give it a go.


Problem between two slider

Hi NightCatSama. I am using two sliders at same time. If I move the first slider, the second slider have to change the value but the second slider value don´t support a function. How can I fix it? Are there any possibility?.
Thanks in advance

like that? demo5

Not exactly, in demo5 use the same value. My project it´s like money conversor. I choose a value in "$" in the first slider and with a function I calculate the value in "€" for set in the second slider.

I wrote an example, I wonder if it can solve your problem.
https://jsfiddle.net/2xy72dod/169/


Add TravisCI build status badge

What about to add build status badge just to make it easier to notice when tests are failed in master?

I prefer to not add this. First, because Travis alerts us when test don't pass, so we don't merge those PRs. Second, even if we ignore Travis, the proprietary tool we use to merge things displays a big red warning message when any GitHub requirement don't pass (e.g. Travis tests).
Besides, I don't think any of the active contributors of this repository sees the README of the project, so we won't see the warning. Finally, tests pass almost always on this repo ... so I don't think it's OK to show "tests failing" during the short periods of time that tests don't pass. Also, that may make some people think that this project is not a high quality one, which wouldn't be fair or true.
Thanks for understanding!

Thank you for explaining your point of view


WinAppDriver - Unable to get the parent of the element using xpath

Hi, I am doing a proof of concept to automate WPF application using WinAppDriver. I have situation where a button does not have a unique id, name or classname (or any other properties that can be identified uniquely). However, there is a child element available to this button that has a text that is unique.
So I am trying to locate the child element (which I can) and then attempting to click on a parent (which is a button I want to click on) using below code but I am getting "An element could not be located on the page using the given search parameters." error.
It looks like the xpath does not work the same way as it works with web applications using selenium. Can someone please help with this ? Below is what I tried.

var eleRace = ele.FindElementByXPath(".//Text[@Name='LocatorName']/..");

var eleRace = ele.FindElementByXPath(".//Text[@Name='LocatorName']/parent::*");

    var ele = driver.FindElementByAccessibilityId("MainUserControl");
    var eleOne = ele.FindElementByXPath(".//Text[@Name='LocatorName']");
    var eleTwo = eleOne .FindElement(By.XPath("./.."));

use the below code:
driver.findelementsbytagname("Button").findelementsbyxpath("/")
findelementsbyxpath this will give all the child elements and check for the child element and using the index click on the button click the button
and the driver.findelementsbytagname("Button")[index].click():
Please note that this will be slow and finding element by xpath is slow and a known issue.

Thanks @anunay1. Tried the solution you suggested. driver.findelementsbytagname("Button")..findelementsbyxpath("/") is not returning the child elements. I am getting timeout errors.

try this driver.findelementsbytagname("Button").findelementsbyxpath("/")

yeah that's what I tried. Sorry there was an extra . in my previous comment.

What happens if you directly try driver.findelemenbybyname("Races")

I am getting "element is not a pointer - or keyboard interactable" error

What happens if you directly try driver.findelemenbybyname("Races")

Would something like this work?.FindElementsByClassName("Button").First(elm elm.FindElementsByName("Races").Any());

@Could you try next code:
var container = driver.FindElementByAccessibilityId("MainUserControl");
var elemToClick = container.FindElementByXPath(".//Text[@Name='Races']/ancestor::Button[1]");
elemToClick .Click();

If it does not work maybe Inspector.exe is not showing a real page source. Coul you save Pages source and post screen with particular elements here.


atomicMax for signed long long is missing

This is strictly speaking not a bug as the HIP documentation correctly lists what is supported, but if the goal is to match the CUDA API, then I am missing a function with this prototype:
long long int atomicMax(long long int* address, long long int val);

That is, a 64-bit signed atomic maximum.  HIP currently defines only the unsigned long long int version.

I'm not sure which version of ROCm you're running, but the support for signed long long is checked in.  It should be present in the next release if not already in the latest.

I think I am running the latest release, or at least close to it. Looking forward to the next one now!

I don't know if the implementation is supposed to reside in this repository (I cannot find it), but the documentation should probably be updated with the signed long long atomicMax.


Tracking Issue: support IBC integration in Astria

Astria is using the Penumbra stack to build their sequencer. They'd like to be IBC-enabled, and last Thursday we had a meeting (cc @noot) about what would be required for them to integrate our IBC stack. We'd like to support them in this, but there will be some work required on both sides. This issue tracks that work.
Currently, our IBC stack has two parts:

ibc-types, which just does common modeling for IBC data types and messages;
penumbra-ibc, which implements IBC on top of the state model provided by penumbra-storage and the component system provided by penumbra-component.

Since moving to our own IBC stack as part of #2379, we've hoped to generalize Penumbra's IBC implementation, with the long-term goal of separating the IBC logic from the state access.  We've held off on doing it until there's a concrete user, to avoid building the wrong generalization.
However, supporting Astria doesn't require that all of that work, because Astria already uses (some of) the Penumbra stack, in particular penumbra-storage and (a tweaked version of) the Component trait in penumbra-component. Instead, we just need to break the dependency of penumbra-ibc on other Penumbra components and generalize it for Astria's use case:

[ ] #3129
[ ] #3126
[ ] #3127
[ ] #3128
[ ] #3130

Beyond the state machine implementation, there's also relaying support. Much of the work we did on the Penumbra side to support Penumbra integration into Hermes will be directly reusable: the bulk of the work was implementing GRPC queries, and those query implementations are part of the IBC component now, so they can be directly used by Astria.
Astria will need to write their own ChainEndpoint implementation, but other work we're planning to push on in order to support Penumbra integration into Hermes may be useful to Astria:

https://github.com/informalsystems/hermes/issues/3636#issue-1909618028 allows Hermes backends to have backend-specific configuration data
https://github.com/informalsystems/hermes/issues/3641 may be relevant, depending on Astria's account / signing model.

The Astria team indicated they were hoping to get token transfers working by the end of October (4 weeks from now), so we should coordinate closely to make sure we're not blocking their work.

We've spoken with Astria out of band, and we have a few more weeks to get the necessary functionality in place. Related work such as #3131 is not shipping in Testnet 62 (#3123), but we plan to return to it soon.


wego version should also return the flux version being used

Short description
As a wego user, I would like to know the underlying flux version for potential troubleshooting or documentation selection.
Given a wego binary
When I run wego version
Then The underlying version of flux should be displayed with the other information

checkpoint has the wego version, so we go there to look for it.


Updated, supports Docker Mac, many fixes, latest Jenkins, wow!

This Pull request includes:

Compatibility for Docker for Mac/Windows
Configures Jenkins to talk to Docker through a Proxy container to work around TLS Certs (DO NOT USE IN PRODUCTION INSTANCES)
Simplified startup, sync source, make build, make run... GTG!
Updates to latest Jenkins 2.58
Updates to latest plugin versions
Has default test image/jenkins job to test and make sure everything works
Utility scripts to help export job/jenkins configuration and reuse it if you lose your data container
Utility scripts to help export Secrets/Credentials (USE CAUTION: Do not check in protected creds!)

I've maintained the tutorial repo's so the blog is consistent. I will probably update the blog series to just use this methodology in the future. Thank you everyone for your patience and feedback!

İ have many questıons now, for example, why use docker-proxy :D
So, im waıtıng for the new tutorıal.

@maxfields2000 I think you forgot update the README file correctly: the new version still use Yet Another Docker Plugin or use JNLP instead.


Use native string repeat instead of custom

Hi!
What about native str.repeat?
I think we can use it (https://caniuse.com/mdn-javascript_builtins_string_repeat).

Thanks for your PR, @Armanio!
While I certainly appreciate the upgrade here, it gave me an even better idea: use String#padStart and String#padEnd to achieve this. I added this in 8a30eaff82f47495cd5fb781d2e008ccd7491861, and will therefore be closing this PR.
Thanks again for the inspiration here!

Glad I helped 👍


exceptions.py tests failing on >= 3.7 because repr changed

CPython 3.7 changed exception’s repr implementation to get rid of a trailing comma:

repr for BaseException has changed to not include the trailing comma. Most exceptions are affected by this change. (Contributed by Serhiy Storchaka in bpo-30399.)

This makes the test case from exceptions.py fail on CPython 3.7 and later.
Should we get rid of the tests for repr, or perhaps just test substrings (that repr string contains both the type and the message)?

Should we aim for python3.7 compatibility? I think removing the trailing comma is good.
We could test for python version number in the test, but this might not be a good thing to start with. It feels like a rabbit hole.

I don’t think this behaviour is well documented anywhere in the official docs (or that built-in exceptions repr is documented at all, at least I cannot find it easily), so perhaps aiming at exact reproduction of any CPython’s behaviour isn’t necessary?
I’d myself restrict the tests to checking some minimal requirements that any sane Python3 (including both CPython 3.6 and CPython 3.7) meet. Eg. that the repr string contains the exception type first and then later it contains the message – but disregard punctuation entirely. Or just check that the message is enclosed in parentheses.
Since this is a detail that CPython changed from version to version, the client code shouldn’t rely on it anyway.

Or since repr should give a proper working Python representation – perhaps doing a round-trip test: checking whether eval() on the repr(exception) gives the same exception would be a good solution that all good Python implementation should pass?

That sounds fair. Then we can add an additional function:
def round_trip(ex):
    assert exceptions_eq(ex, eval(repr(ex)))


Add a rule for generating tables from our pdf-archive

In case anyone wants to reproduce our work exactly (or skip the scraping step).

added in 4cf65fc73e5f43fde7b5b7d1525600058826507b, nice werk @jeancochrane!


Docker 1.12.1 hanging at build step "Setting up ca-certificates-java"

OS:
Operating System: Ubuntu 14.04.4 LTS
Kernel: Linux 4.2.0-27-generic
Architecture: x86_64
Dockerfile:
FROM phusion/baseimage:0.9.19
ENV BAMBOO_HOME /home/bamboo/bamboo-agent-home
ENV BAMBOO_SERVER http://<IP_ADDRESS>:8085
RUN apt-get -y install software**-properties-common &&
add-apt-repository -y ppa:openjdk-r/ppa &&
apt-get update &&
apt-get -y install openjdk-8-jdk
COPY bamboo-agent-*.jar ${BAMBOO_HOME}/bin/
COPY run /etc/service/bamboo_agent/
RUN useradd bamboo:bamboo &&
chmod a+x /etc/service/bamboo_agent/run &&
chown -R bamboo:bamboo /home/bamboo
VOLUME $BAMBOO_HOME/xml-data/build-dir
isuue:
image building stuck in  "Setting up ca-certificates-java" , tried several times.
Setting up openjdk-8-jdk:amd64 (8u91-b14-3ubuntu1~16.04.1) ...
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer to provide /usr/bin/appletviewer (appletviewer) in auto mode
update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to provide /usr/bin/jconsole (jconsole) in auto mode
Setting up ca-certificates-java (20160321) ...

I guess this is a duplicate of https://github.com/docker/docker/issues/18180#issuecomment-193708192 , and it would be fixed by upgrading the kernel to 4.2.0-30.35 or later (Ubuntu 15.10?)

thanks, you are right


AspNetCoreModuleV2  HTTP Error 500.21 with Hosting Bundle 2.2.5 Bundle Installed

Describe the bug
Receiving a 500.21 error when attempting to access ASP.NET Core 2.2 application configured to use In-Process hosting.
Expected behavior
If ASP.NET Core 2.2 Hosting Bundle is installed, should be able to host using IIS in-process.
Screenshots
I have screenshots showing the bundle is installed , but my corporate Netskope is blocking me from uploading images, lol.
Additional context
Host (useful for support):
Version: 2.2.5
Commit:  0a3c9209c0
.NET Core SDKs installed:
No SDKs were found.
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

This error usually occurs when the global applicationhost.config file doesn't contain the correct global modules. Can you check and see if the global module AspNetCoreModuleV2 is listed in your applicationhost.config file in C:\Windows\System32\inetsrv?
Also, can you send the steps you took to repro this? Did you have other hosting bundles already installed on your machine? We have heard issues of this happening to customers but from what I can tell, we never received a great repro.

@jkotalik Appreciate the quick response. This is the issue.
We use a shared configuration file. We removed the share, installed the hosting bundle on both, and then reestablished the share.
I'm assuming in this instance we forgot to look at changes made by the installer in the local configuration files and get those into the shared file. I'll close this if that turns out to be the case.
Thanks again!

We use a shared configuration file. We removed the share, installed the hosting bundle on both, and then reestablished the share.

That's most likely the issue. The installer probably does not have permissions to write to the shared configuration. Are you redirecting the applicationhost.config via the redirection.config file?

That's most likely the issue. The installer probably does not have permissions to write to the shared configuration. Are you redirecting the applicationhost.config via the redirection.config file?

I don't know. Let me ask IT. Is this a best practice all things being equal?

@jkotalik This indeed was the issue. Perhaps the installer team could warn the user that the local applicationhost.config will be changed and these changes need to be placed in the shared config if it is being used..
I didn't get an intelligible answer as far as the redirect.config. Do you think this makes a difference?

The ANCM installer sometimes can't write to an applicationhost.config that is redirected. AFAIK, the redirection.config file is the main way to enable a shared configuration.'
I would need to recheck the logic for how ANCM handles redirected config. Glad you figured out the issue though!


[Linenoise 2] multi-console support & support for replacing stdin/stdout (IDFGH-8546)

Related Issue: https://github.com/espressif/esp-idf/issues/9986
This is definitely an optional PR. Linenoise is already an easy dependency for users to replace if they want to add this functionality. Still, I wanted to share these changes in hopes that Espressif or others may find them useful.
Note: this PR also incorporates the same EWOULDBLOCK linenoise changes from this other PR: https://github.com/espressif/esp-idf/pull/9983
Features:

support multiple instances of Linenoise, in order to support multiple consoles
backwards compatible, no code changes required for linenoise1 users
optional Linenoise2 API to support linenoise handles, and replacing stdin/stdout
in commands.c, support calling esp_console_run() on multiple independent threads.

Tested:

on ESP32-S3
both smart & dumb linenoise modes
both stdin/stdout, and /dev/usbserjtag

You can simply assign your task's stdin and stdout to whichever FILE* streams you want.

Yes. I wish I new that earlier 😅. For ease of discovery, I agree explicit api is much more clear.

That is, use IDF naming conventions

Hmm. I think it would be confusing for linenoise2 to have different naming convention than linenoise1, despite having all the same functions that do all the same things, in the same file.

but I'll discuss this with the team and come back with more concrete suggestions!

Please do!

got it. I'll implement your style suggestions.

I also wonder if we can make the future maintenance easier by developing this as a standalone component,

I just want to add my vote to keeping console in the main ESP-IDF repo. Opening a console is more important that wifi or bluetooth. It would be crazy to me to have wifi and bluetooth, but no console support in the main repo.

Created new PR with Ivans suggestions: https://github.com/espressif/esp-idf/pull/10526
I think it's quite a nice new API, that should make it into v5.1


Add Gist Support

Also, not a  huge thing, but if some day you got the chance to integrate gists into this addon, it would make a perfect single solution.
I am currently using https://github.com/linjunpop/obsidian-gist and it's a great plugin, but having everything wrapped into one would be the icing on the cake. Also sort of irritating that the gist plugin has no support for dark themes. So I have this dark Obsidian theme and then when I scroll to a gist, I get blasted with white.
Not a deal breaker, but just a thought.

Originally posted by @Aetherinox in https://github.com/MrGVSV/obsidian-github-embeds/issues/5#issuecomment-1791869691

A side note just in case you need the info.
What makes Github gists so great is that you can view the gist by going to either

https://gist.github.com/Aetherinox/e349cd6b200215b1f8d408bf9edc491b
https://gist.github.com/Aetherinox/e349cd6b200215b1f8d408bf9edc491b.json

By appending .json on the end, you get a json structure of your gist.
The other Gist addon calls stylesheet and div and places that code within Obsidian to show the gist. It's a great idea, but the downside is that he only applied the white theme.

In the Plugin settings in Obsidian, he provided a CSS Override field, and I've tried every which way to override the CSS to change the background, but nothing seems to work

Nice. It's no rush, but it would definitely be a welcomed feature. I've been trying to tweak the other Gist plugin, and it's not exactly user-friendly and have had to do some really hacky stuff to semi get dark themes in place.
I'm waiting on the developer for the program "OpenGist", who is implementing a feature similar to what GIsts have with json being called and being able to integrate a Opengist snippet.


advanced seed for community in progress - request for assistance

I am working on a relatively advanced angular2-seed which will feature {N} integration:
https://github.com/NathanWalker/angular2-seed-advanced
I'm running into an issue. Curious if someone could be so kind to take a look by following the instructions here to get setup and trying to help:
https://github.com/NathanWalker/angular2-seed-advanced/blob/development/NATIVESCRIPT_SUPPORT.md

JS ERROR ReferenceError: Can't find variable: __metadata
You get this one if you don't have reflect-metadata imported, or your compiler isn't emitting helpers or decorator metadata.
Out of curiosity, why do users need to edit tns-core-modules.d.ts? What is the original issue, and can we do anything about it?

tns-core-modules.d.ts includes references to:
/// <reference path="declarations.d.ts" />
/// <reference path="es-collections.d.ts" />
/// <reference path="es6-promise.d.ts" />
/// <reference path="es6.d.ts" />
/// <reference path="weakmap.d.ts" />

Those cause problems when paired with other build setups that already include those typings.
We should probably get NativeScript typings on the typings registry here since tsd is deprecated.
Instead of including those global typings in tns-core-modules.d.ts, it could be instructed for end user's to setup their typings.json to contain the typings that are needed.
This way tns-core-modules.d.ts would only cover typings for NativeScript libraries.

I am importing reflect-metadata here:
https://github.com/NathanWalker/angular2-seed-advanced/blob/development/src/app/app.ts
Maybe it needs to be imported in other files as well?
Maybe something incorrect here:
https://github.com/NathanWalker/angular2-seed-advanced/blob/development/src/tsconfig.json
Thank you for your help @hdeshev

I was able to get past it by removing both of these options in tsconfig.json:
"noEmitHelpers": true,
        "noEmitOnError": true,

:+1:  It's close to working now... just a few things left to work with Http and ng2-translate

Ok @hdeshev I've gotten much further with your help (thank you!) and I updated the {N} instructions here:
https://github.com/NathanWalker/angular2-seed-advanced/blob/development/NATIVESCRIPT_SUPPORT.md
But I am now running into this:
CONSOLE ERROR file:///app/tns_modules/angular2/src/platform/server/parse5_adapter.js:53:75: ORIGINAL EXCEPTION: TypeError: this.http.get(this.sfLoaderParams.prefix + "/" + lang + this.sfLoaderParams.suffix)
	            .map is not a function. (In 'this.http.get(this.sfLoaderParams.prefix + "/" + lang + this.sfLoaderParams.suffix)
	            .map(function (res) { return res.json(); })', 'this.http.get(this.sfLoaderParams.prefix + "/" + lang + this.sfLoaderParams.suffix)
	            .map' is undefined)

This is coming from the internals of ng2-translate (https://github.com/ocombe/ng2-translate/blob/master/src/translate.service.ts#L40-L41).
I have of course imported the .map operator here:
https://github.com/NathanWalker/angular2-seed-advanced/blob/development/src/app/app.ts#L7
I have also seen your Http sample here:
https://github.com/NativeScript/sample-ng-http
But I don't see anything I'm missing. Any idea what this last error is and why it's not importing the .map operator correctly?

Apparently this same question was asked on stackoverflow a couple weeks ago with no answer:
http://stackoverflow.com/questions/34899835/using-map-in-nativescript-with-angular2
I am experiencing the same trouble.

Hey @NathanWalker,
The issue looks like this one https://github.com/NativeScript/nativescript-angular/issues/38 which has already been fixed in the iOS runtime. You can try downloading the latest iOS runtime bits from here and use them. As those builds are not verified I'm not sure what will be their stability.

@ligaz Thank you! I will try this! ..crossing fingers..

Hmm unfortunately I now get this error setting up all the latest nightly's as that nativescript.rocks site mentions:
ld: warning: directory not found for option '-F/Users/nathan/Documents/github/NathanWalker/angular2-seed-advanced/src/platforms/ios/../../lib/iOS'
ld: can't open -sectcreate file: /Users/nathan/Documents/github/NathanWalker/angular2-seed-advanced/src/platforms/ios/build/emulator/metadata-i386.bin
clang: error: linker command failed with exit code 1 (use -v to see invocation)

The typings problem is related to NativeScript/NativeScript#1457. I started working on it today, and it will probably land in master tomorrow. The idea is for Angular apps to reference a different dts file for the nativescript components. I'm not sure tns-core-modules.es6.d.ts will suffice yet -- I may have to come up with another :-/
Anyway, solving this problem would get rid of the ugly build hook that regex-replaces stuff in the angular d.ts files to delete certain references that cause compile-time type conflicts.

Ok that makes sense. Thank you for this insight and let me know if I can help in anyway to move that forward. Give me a task, seriously. I'm quite anxious to get this working :)

@ligaz  - The builds on NativeScript.rocks are straight from source every afternoon my time.   (The majority of the NS core team is deeply sleeping midday my time; so it is the safest time to make sure I capture everyone's work on master for the day).
The actual status:

Android runtimes have my liveedit & encryption patches automatically applied.
iOS runtimes, no patches yet -- but eventually will have the same patches as above.
TNS Core Master - totally unchanged, just TS -> JS'd.

These are all build from Master, including the required sub-projects (widgets, metadata, v8).
v8 is only built when a new v8 is setup in master; as their is no point rebuilding the same code everyday --- so right now my masters are actually running on the new 4.7.80.  :grinning:
I do occasionally have to kick the android build as occasionally the NS team breaks my patches by adding new code around one of the diff locations and diff's won't apply cleanly, but otherwise it is a totally automated process; so if it doesn't work; it is because the master is broken.  :grinning:

I ran into this today as well so I thought I’d just add two things:

HTTP calls work for me on Android but not iOS, which tends to suggest that the problem is indeed the iOS runtime bug that @ligaz suggests.

Oddly, I had to do a JSON.parse() step to actually get my data in JSON format. See https://github.com/NativeScript/sample-Groceries/blob/bcb03dc54e8c4575b17fb99a6a22e8857b184a5c/app/shared/user/user.service.ts#L26. Anybody know what might be up there?

The good news: other than that one line of code, I’m using the exact same service to drive my web app and my native app, and that’s pretty freakin’ awesome 😀

Thanks for this additional insight @tjvantoll ... def exciting to be able to reuse services across different platforms! Congrats on getting it working in your setup and yes, hopefully iOS Http will work soon here!

I'll update the advanced seed to latest soon as it looks like most of these issues have been solved. I'll open different issue of anything else is found.


Dev.to MongoDB hackathon.

Hey @philipwaluisachi , MongoDB is having a hackathon and they just need project submissions that have utilised MongoDB. I think you should consider submitting this application and see how that goes. checkout dev.to, the deadline is in 2 days. Let me know if you need my assistance.

Okay lemme check @kibuikaCodes

@kibuikaCodes How do I change license  to apache 2

I am not really sure.


Names in .md need to sync with misc_names.toml

any progress on this??

This deals with https://github.com/jyotisham/adyatithi/blob/master/period_names/ - feel free to contribute a simple Python script if interested. Will fix it in time..


Support log to file

export OPENSHIFT_PYTHON_WRAPPER_LOG_FILE=
Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

/verified

/verifed

/verified

/verified


Add Exp to system functions

Add Exp to system functions so it is properly translated to the ELM Exp operator rather than a user-function.
v12 branch needs the same fix applied, but wasn't sure how you prefer it done (separate PR, merge from master to v12, etc).

I've been rebasing the v12 branch onto master as changes are made, so I'll merge this then do that there. Thanks Chris!


Add Prometheus to platform for dashboard data collection

Description

We want to collect and publish data on our infrastructure and application.
Specifics

[ ] configure Prometheus resources for our cluster
[ ] scrape cluster metadata

[ ] individual node status

[ ] build trade package under libraries/rust

[ ] write Client class

[ ] include new constructor with Alpaca configurations as parameters
[ ] add "get account balance" method returning integer value
[ ] add "get account positions" method returning list of tickers

[ ] add unit test coverage on all methods
[ ] add performancereporter directory under platform
[ ] build Dockerfile with basic Rust image
[ ] write required "entrypoint" logic/resources

[ ] build API endpoint

[ ] calls trade package "account" methods
[ ] returns payload with "account" information

[ ] emit "successful performance report" event

[ ] build and run resources locally for manual tests
[ ] include required Mise build/run/push commands
[ ] configure Prometheus to scrape performancereporter API endpoint
[ ] update Grafana with all metrics

Closing as low-priority.