nb-black is outdated. wait and see if it is fixed

This issue https://github.com/dnanhkhoa/nb_black/issues/40 blocks nb-black from being installed.

Proposed solution: deprecate nb-black until issue is fixed (https://github.com/City-of-Helsinki/mlops-template/pull/54)

black now supports notebooks with black[jupyter] install option. Notebook reformatting is now a pre-commit action. Solved in pr https://github.com/City-of-Helsinki/mlops-template/pull/54


add java format style

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[ ] refactor
[x] others

Which issues of this PR fixes ：
Add java style in .clang-format to avoid format error when writing java code:

@ucasfl  How to use this feature? After this is merged, I can format java code by executing ./build-support/clang-format.sh?

@ucasfl How to use this feature? After this is merged, I can format java code by executing ./build-support/clang-format.sh?

I didn't notice this script, just my editor can format code automatically with this config and clang-format when writing code.

@ucasfl How to use this feature? After this is merged, I can format java code by executing ./build-support/clang-format.sh?

I didn't notice this script, just my editor can format code automatically with this config and clang-format when writing code.

What editor do you use?

@ucasfl How to use this feature? After this is merged, I can format java code by executing ./build-support/clang-format.sh?

I didn't notice this script, just my editor can format code automatically with this config and clang-format when writing code.

What editor do you use?

vim with releated plugin.


Add timestamp-based dependency system to build_clib

build_clib is sorely missing one thing in distutils - checking outdated dependencies when compiling. This makes it so that, when building a static c library, all objects are always all compiled.
The function to create the static library itself does implement something of this sort, but since all objects have been recompiled it has no practical effect (everything still runs every time).
This is a small patch designed to fix that, with a couple of qol improvements along the way. Two new keys were added to the build_info dictionary:

obj_deps - Allows specifying extra dependencies for each source so they can be recognized as being newer than the object being compiled. Example:

setup(
...
libraries=[(
    'examplelib',
    {'sources': 'example.c',
     'obj_deps': {'': 'global.h',  # use an empty string to define global (for all sources) dependencies
                  'example.c': 'example.h'}
    }
)]
...
)

cflags - This just allows the user to provide an extra set of flags to the compiler.

That is pretty much it, a simple (but important) quality of life improvement for those of us who need to compile static libs with python.
If the implementation is fine I can get started on documentation, just not sure where to put it.

This seems reasonable, and I appreciate the effort put into making this first request a complete and thorough one.
I welcome subsequent improvements to the documentation. I also encourage you to see this implementation made the default in distutils (stdlib) with setuptools providing forward compatibility but eventually delegating that role back to distutils. I won't stipulate that as a requirement, however.

I'll definitely look into that, time to start learning mercurial :) Thanks!


keybindings reset

Please use the search functionality before reporting an issue. Also take a look at the closed issues!
Issue description:
When i change the keybindings and restart the game, the keybindings reset to their default values. This happens with and without the controlling mod installed. Tested on my modpack "Tosers Spacecraft". I can change other keybindings without problems. They remain after restart as expected. Only mekanism keybindings are affected.
Steps to reproduce:

change some mekanism keybindings for example change armor mode to the "i" key
2.restart minecraft
3.options.txt changed the armor mode to the default key "g"

Version (make sure you are on the latest version before reporting):
Forge: <IP_ADDRESS>24
Mekanism: 1.12.2-<IP_ADDRESS>7
Other relevant version:
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
[gist/pastebin/etc link here]

Probably has to do with the spaces in the name of the keybinding lookup key. This probably will be fixed by #5389

@ToserBan are you using a non-english language for Minecraft?

I´m using german as language, but in older versions of mekanism i had never a problem to change the controls. Right now i´m testing out english(US).
Ok, ready: The problem occurs as well in english(US). Furthermore i detected another strange behaviour according to keybindings, but that does not necessarily have to do with mekanism. When i tried to type in the "i" key for mekanism armor mode switch, it showed "alt+i", it did it as well for other mod controls. I had not caps lock or something activated and after playing around with shift, alt and control key i was able to type in the normal "i", but after a minecraft start  i had the default value "g" for mekanism armor mode switch.

Update: I saved my options.txt, deleted the modpack and reinstalled it(technic launcher version). Then i copied back the options.txt and started the game. Now it works, i can change all keybindings including mekanism controls. Tested only in english(US) language. Maybe the above problem came from an inaccurate language translation. In the english version, i could use the default "g" key to change fly mode in the german version i couldnt, really strange.

The code in the current release of mekanism stores the keybinds with a translated 'description', where it should be using the translation key so that language doesn't matter - this is legacy code that will be resolved in the PR pupnewfster linked.
This is probably your issue, but we can't say for sure until I finish up that PR

When i change back to german, i have the old problem. Anyway, thanks for your work on this great mod.

9.7.5 should fix this issue (though you may have to view (or change) the keybindings and then restart MC once for it to properly sync if it starts in a broken state). If you could confirm that would be great


select and Custom child node

🐛 Bug report
Nested in api.positionerProps will report an error if opened by manual control ：
[@zag-js/dismissable] node is `null` or `undefined`

💥 Steps to reproduce

🧐 Expected behavior
Need to pull open in manual control, handle some special operations, report an error if api.positionerProps is empty or not api.contentProps, should not restrict the use of subcomponents.
🌍 System information

Software
Version(s)

Zag Version
0.10.2

Thanks for reporting this issue. However, you needed to provide more information for us to understand and reproduce the problem.
Please send a reproduction, as we cannot act on issues that lack important information.


How to improve the use of cpu

I run the dnc example and found that in 32-core machines, the CPU usage is not high. Is there any way to make the CPU work at full capacity and improve efficiency? Thank you

I would recommend data-parallelism versus model parallelism here, see https://www.tensorflow.org/deploy/distributed#replicated_training. The general idea is that you want to split your input training batch across multiple groups of CPUs and have several instantiations of the DNC train on these partitions, instead of hoping the model can parallelize very well over 32 machines for a single minibatch.


Uploaded Helene Lange Gymnasium Dortmund

I would like my school to be added here so us students can freely code in computer science class without all being required to buy a subscription plan just for studying.

@UniCode9696 The first verification stage is complete: the official domain for  Helene Lange Gymnasium Dortmund is www.hlg-do.de, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.hlg-do.de/digitalitaet/faq

@UniCode9696 The first verification stage is complete: the official domain for  Helene Lange Gymnasium Dortmund is www.hlg-do.de, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.hlg-do.de/digitalitaet/faq

@UniCode9696 Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


update Larb token Logo

Token Address
e.g: https://scan.tomochain.com/address/0x3a5F05396D310DCfBfF1B1bD7BC8746D727e384E
Token Symbol
LARB
Token Name
Larb
Token Logo
PNG 256px by 256px
Token Description
inLarb native asset backed utility token.
Website
https://inlarb.com.
Social links
Telegram - https://t.me/inlarbnetwork
Twitter - https;//twitter.com/inlarb
Instagram - https://instagram.com/inlarbnetwork
Youtube - https://www.youtube.com/channel/UCCDn7l-MXhfprWb44yXc4jw

Done https://github.com/tomochain/tokens/pull/67


support Deep type inference

Coverage remained the same at 86.42% when pulling 33cf29a03192653dfadd85e99d8be9fe6a89f6d2 on SalmaKhater:feature/#70-deep-type-inference into 3b7d21c82b73b461cf1c2d460578bc8f314631e0 on cassandra-scala:master.

Coverage increased (+1.8%) to 88.192% when pulling 007d0a186d6782ef0734cf75a179d174968c5410 on SalmaKhater:feature/#70-deep-type-inference into 3b7d21c82b73b461cf1c2d460578bc8f314631e0 on cassandra-scala:master.

@SalmaKhater: @Eman-Shaaban  is working on #40
Which might be useful for this PR?


Date formatting

Fixes the issue talked about at: http://stackoverflow.com/questions/7556591/javascript-date-object-always-one-day-off?noredirect=1&lq=1
When picking a date (as opposed to a date/time) almost no one will want 29 Jan to be converted to 28 Jan GMT-5.

This is probably too heavy handed, but something along these lines should be available to allow users to choose a date without having to be concerned by locales/time zones/etc.

In my opinion this case should not be handled directly in admin-on-rest. Indeed, it is recommended to always return a timezone with your dates in API to prevent these kinds of issues. If you don't, I would instead recommend to add an interceptor in your REST client to make these conversions.
Moreover, what about if you want to display date in local browser time? :)

All true. But in this case admin-on-rest is taking the raw data returned by REST and sending it through new Date(value), then displaying the result, potentially distorting the value. In the case where I came across this, my DB was returning a value 2017-01-30 which Date interpreted as 2017-01-29 19:00 GMT -5 which then got displayed by admin-rest as 2017-01-29, truncating the time. So each time you re-rendered the component, the date dropped by one day, obviously not correct.
Due to the quirk of how Date parses dates, it won't occur with 2017/01/30, so that's where my hacky solution came from. Would it be better for admin-on-rest to not even run the date through Date? Or is there some other way to enforce that a Date is "timezone-less" and thus should not be corrected for or interpreted as time-zone dependent? An example is a birthday. Most people interpret it as just a constant day, vice correcting for timezone with the true time of birth or international dateline, etc.

Your solution removes hours and seconds from Datetime, it it's not good. The DateField has a withTime param that you should take into account.
I think the problem isn't with the parsing of the date, it's with the rendering of the dates.
For the DateField, did you try passing { timeZone: 'America/New_York' } as options prop? This forces the timezone for the locale date conversion.
https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/Date/toLocaleString

@fzaninotto : Yes, I've tried timeZone and locale. I suspect a modified DateTimeFormat could probably do the trick.
I agree that my solution in this PR is not good for the general case. But I do think the datify function needs a modification. new Date is manipulating the input as a moment in time, then truncating the time for display.
Here's the note from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date regarding the use of new Date
Note: parsing of date strings with the Date constructor (and Date.parse, they are equivalent) is
 strongly discouraged due to browser differences and inconsistencies. Support for RFC 2822
 format strings is by convention only. Support for ISO 8601 formats differs in that
date-only strings (e.g. "1970-01-01") are treated as UTC, not local.

Some other libraries solve the problem by internally replacing - by /. This also works for your library, (it was a previous attempt at a PR, not sure if you'd find that acceptable).
https://github.com/danvk/dygraphs/blob/3f675fe524eece31f39fb68601d2d2d7d5720941/dygraph-utils.js#L510

Replacing - by / looks like a better idea in this case. Yet, we would need to test this method on several timezones and browsers (especially Safari, which has some troubles with dates if I remember correctly. @Kmaschta or @ThieryMichel, can you confirm?).

@tomberek Any update on this PR?

@leesei - No.
I am still personally interested, but my project has moved on to a different solution.

I see. I'll be using <DateInput> in my project.
Would you mind me creating a PR based on code in this PR if I see any problem?

go ahead

On second thought <DateInput> is not wrong in returning Date object of UTC time, which is the internal representation of all times in JavaScript VM.
If the issue is transforming the date string "YYYY-MM-DD" (presumed local time) to Date object, do refer to dateFormatter in #555:
const dateFormatter = v => {
  // v is a string of "YYYY-MM-DD" format
  const match = /(\d{4})-(\d{2})-(\d{2})/.exec(v);
  if (match === null) return;
  const d = new Date(match[1], parseInt(match[2])-1, match[3]);
  if (isNaN(d)) return;
  return d;
};

Agreed, closing.

Just hit this, and had to use the following to get DateField rendering correctly:
<DateField source="birthDate" options={{ timeZone: "UTC" }} />


Cannot Ignore Properties on Multiple Derived Types and Base Class Simultaneously

Describe the bug
This is related to: https://github.com/riok/mapperly/issues/694
To Reproduce
Have ignores set up on separate derive types + the base class for a given mapping structure.
Results in RMG021: IgnoredSourceMember was not found
There is currently no way to Ignore base mappings due to the inability to apply the MapDerivedType logic to an existing mapping.
Expected behavior
A clear and concise description of what you expected to happen.
I would expect the ability to separately ignore members at the base class level, and at each of the derived types without introducing errors or suppressions.
Code snippets
public class SourceBase
{
    public int BaseId { get; set; }
}

public class Source : SourceBase
{
    public int Id { get; set; }
}

public class AnotherSource: SourceBase
{
    public int NewProp { get; set; }
}

public class TargetBase // missing ID
{ }

public class Target : TargetBase
{ }

public class AnotherTarget : TargetBase
{}

[Mapper]
internal static partial class TestMapper
{
    [MapDerivedType<Source, Target>]
    [MapDerivedType<AnotherSource, AnotherTarget>]
    [MapperIgnoreSource(nameof(SourceBase.BaseId))]
    [MapperIgnoreSource(nameof(Source.Id))]
    [MapperIgnoreSource(nameof(AnotherSource.NewProp))]
    public static partial TargetBase ToTarget(this SourceBase source);
}

Environment (please complete the following information):

Mapperly Version: e.g. 3.2.0
.NET Version: e.g. .NET 7.0.*
Target Framework:  .net7.0
IDE: Visual Studio v17.8
OS: Windows 10

This would be a great enhancement. Would be happy to accept a PR, let me know if you want to contribute and need any hints 😊

The problem I see here is how to decide which configurations apply to which type mappings. Should all applied to all? Even if there is a specific mapping method for a given type pair?

Could it follow the existing precedence conventions / behaviors that already exist?

What conventions are you referring to?

Closing in favor of the new MapperIgnoreAttribute that allows ignoring properties at source.


Implement Set Union iterator

Note that this should be distinguished from producing a new prolly set. The goal here is to simply produce an iterator which returns the union of two sets values.

Let's call these UnionIterator and not just Union to make this clear.
Having Union that does not return a Set would be confusing.
On Fri, Aug 5, 2016, 21:43 Rafael Weinstein<EMAIL_ADDRESS>wrote:

Note that this should be distinguished from producing a new prolly set.
The goal here is to simply produce an iterator which returns the union of
two sets values.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/issues/2294#issuecomment-238005611,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACzFauY9QdYMJNPzHqXLArLqxg-erbbks5qdBDYgaJpZM4JeGfF
.

Fixed by PR #2383


[Feature Request] Kill Sounds?

It's a simple feature, just plays a sound after you killed someone

it's easy to add mate, look at how hitsounds work and then look at the kill message feature put the two together and boom.

not sure if you mean through the mic like P2Cs

it's easy to add mate, look at how hitsounds work and then look at the kill message feature put the two together and boom.

big brain, if this was reddit... i would give you a gold medals

it's easy to add mate, look at how hitsounds work and then look at the kill message feature put the two together and boom.

big brain, if this was reddit... i would give you a gold medals

ikr

https://wiki.alliedmods.net/Counter-Strike:_Global_Offensive_Events
player_death is the event you want.
player_hurt already contains hitsound code.

this feature is added to Osiris, please close this issue


Can't get 3080 GPU working...

I've tried the 'pip [...] --index-url https://download.pytorch.org/whl/cu117' instruction but it causes numba to have the wrong dependency version for numpy. Any ideas?

Try pip check and Can you show me the results?


Update Version Checks

This PR implements a required change for Trtl Anti-Entropy: Update checks if the version being updated is still later than the local version. I've also added a WithForce() option that bypasses checks if the user wants to force put an object to the database, overriding the namespace and version checks.
This is related to https://github.com/trisacrypto/directory/pull/299
Note this is related to sc-2703 but is not a complete implementation; this PR only does enough to fix sc-2694.

I know we haven't gone through sc-2694 yet @bbengfort @pdeziel, but I think this makes sense to me. I gather that part of the replication bug we've been experiencing in trtl relates to the need for this subsequent check that object updates sent by the remote are still the latest from the perspective of the local replica? And it looks like you've added the force option so that we can still make manual repairs to an object, even if it means regressing its version?

Yes, this is related to the need to handle Put and Update concurrency correctly while CHECK messages are being sent between replicas. Adding guards like this makes me a little worried sometimes though because it means if things get out of whack, it's tougher to repair - so I'm hoping the force option allows us to do dangerous things when we just need the database to get back to a correct state.
Based on your review of SC-2694, I think we should add one more thing to Update - a return of the UpdateType, e.g. was it a stomp, a skip, a linear version, etc. I'd like to open that in a new PR so that it can be added to SC-2694 to unblock the prometheus metrics.


[ENG-4195] Hide anonymized fields

Ticket: ENG-4195
Feature flag: n/a

Purpose

Hide registration fields that will no longer be serialized in AVOL views

Summary of Changes

Hide DOI in registration AVOL view
Hide affiliated institutions in registration AVOL view

Screenshot(s)
Metadata sidebar will no longer show DOI's and affiliated institution after this update

Side Effects

No, not really?

QA Notes

The DOI and affiliated institutions will still be visible in the API even in AVOL view until the backend piece is merged
Pending code changes here: https://github.com/CenterForOpenScience/osf.io/compare/develop...jwalz:osf.io:avols_take_2#

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.815%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5567

Relevant Lines:
7532

💛  - Coveralls


"error from TR_TADIR_INTERFACE" when pulling

using latest abapGit
analyzing problem...

AVAS object has wrong filename, opening PR

merged, fixed, closing


Add schema based parsing of UWSGI metrics

First stab at schema based parsing of UWSGI metrics now that we're adding service level dimensions. Ideally this would be driven more by configuration files or some other pluggable schema parser, but for now I think it's a suitable simple alternative.
@gnufied let me know what you think.

It looks good and +1 to not having to parse same json twice for dropwizard format and stuff.

+1


Support for Symfony 5

We'd actually only need a new tag since composer.json already allows Symfony 5
#SymfonyHackday

Here is the new tag:
https://github.com/SymfonyTest/SymfonyDependencyInjectionTest/releases/tag/4.1.0

Thank you @Nyholm !


Problems after upgrade from 0.2.0 to 0.2.2

Open Interpreter broken in Termux after upgrade:
’’’zsh
❯ i
Traceback (most recent call last):
File "/data/data/com.termux/files/usr/bin/i", line 5, in
from interpreter.terminal_interface.start_terminal_interface import main
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/interpreter/terminal_interface/start_terminal_interface.py", line 9, in
from .profiles.profiles import open_profile_dir, profile, reset_profile
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/interpreter/terminal_interface/profiles/profiles.py", line 13, in
import send2trash
ModuleNotFoundError: No module named 'send2trash'
❯ interpreter --version
Traceback (most recent call last):
File "/data/data/com.termux/files/usr/bin/interpreter", line 5, in
from interpreter.terminal_interface.start_terminal_interface import main
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/interpreter/terminal_interface/start_terminal_interface.py", line 9, in
from .profiles.profiles import open_profile_dir, profile, reset_profile
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/interpreter/terminal_interface/profiles/profiles.py", line 13, in
import send2trash
ModuleNotFoundError: No module named 'send2trash'
❯ pip install --upgrade open-interpreter --no-cache-dir --no-deps
Requirement already satisfied: open-interpreter in /data/data/com.termux/files/usr/lib/python3.11/site-packages (0.2.2)
❯ pip install --upgrade open-interpreter
Requirement already satisfied: open-interpreter in /data/data/com.termux/files/usr/lib/python3.11/site-packages (0.2.2)
Collecting aifs<0.0.10,>=0.0.9 (from open-interpreter)
Using cached aifs-0.0.9-py3-none-any.whl.metadata (3.2 kB)
Requirement already satisfied: astor<0.9.0,>=0.8.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (0.8.1)
Requirement already satisfied: fastapi<0.111.0,>=0.110.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (0.110.0)
Requirement already satisfied: git-python<2.0.0,>=1.0.3 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (1.0.3)
Requirement already satisfied: html2image<<IP_ADDRESS>,>=<IP_ADDRESS> in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (<IP_ADDRESS>)
Requirement already satisfied: inquirer<4.0.0,>=3.1.3 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (3.2.1)
Requirement already satisfied: ipykernel<7.0.0,>=6.26.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (6.28.0)
Requirement already satisfied: jupyter-client<9.0.0,>=8.6.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (8.6.0)
Requirement already satisfied: litellm<2.0.0,>=1.18.4 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (1.23.5)
Requirement already satisfied: matplotlib<4.0.0,>=3.8.2 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (3.8.3)
Collecting nltk<4.0.0,>=3.8.1 (from open-interpreter)
Using cached nltk-3.8.1-py3-none-any.whl.metadata (2.8 kB)
Collecting platformdirs<5.0.0,>=4.2.0 (from open-interpreter)
Using cached platformdirs-4.2.0-py3-none-any.whl.metadata (11 kB)
Requirement already satisfied: posthog<4.0.0,>=3.1.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (3.3.1)
Requirement already satisfied: prompt-toolkit<4.0.0,>=3.0.43 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (3.0.43)
Requirement already satisfied: psutil<6.0.0,>=5.9.6 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (5.9.7)
Requirement already satisfied: pyyaml<7.0.0,>=6.0.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (6.0.1)
Requirement already satisfied: rich<14.0.0,>=13.4.2 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (13.7.0)
Collecting send2trash<2.0.0,>=1.8.2 (from open-interpreter)
Using cached Send2Trash-1.8.2-py3-none-any.whl.metadata (4.0 kB)
Requirement already satisfied: six<2.0.0,>=1.16.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (1.16.0)
Collecting tiktoken<0.6.0,>=0.5.2 (from open-interpreter)
Using cached tiktoken-0.5.2-cp311-cp311-linux_aarch64.whl
Requirement already satisfied: tokentrim<0.2.0,>=0.1.13 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (0.1.13)
Requirement already satisfied: toml<0.11.0,>=0.10.2 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (0.10.2)
Requirement already satisfied: uvicorn<0.28.0,>=0.27.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (0.27.1)
Requirement already satisfied: wget<4.0,>=3.2 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from open-interpreter) (3.2)
Collecting chromadb<0.5.0,>=0.4.22 (from aifs<0.0.10,>=0.0.9->open-interpreter)
Using cached chromadb-0.4.24-py3-none-any.whl.metadata (7.3 kB)
Collecting unstructured<0.13.0,>=0.12.0 (from aifs<0.0.10,>=0.0.9->open-interpreter)
Using cached unstructured-0.12.6-py3-none-any.whl.metadata (83 kB)
Requirement already satisfied: pydantic!=1.8,!=1.8.1,!=2.0.0,!=2.0.1,!=2.1.0,<3.0.0,>=1.7.4 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from fastapi<0.111.0,>=0.110.0->open-interpreter) (2.5.3)
Requirement already satisfied: starlette<0.37.0,>=0.36.3 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from fastapi<0.111.0,>=0.110.0->open-interpreter) (0.36.3)
Requirement already satisfied: typing-extensions>=4.8.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from fastapi<0.111.0,>=0.110.0->open-interpreter) (4.9.0)
Requirement already satisfied: gitpython in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from git-python<2.0.0,>=1.0.3->open-interpreter) (3.1.41)
Requirement already satisfied: requests in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from html2image<<IP_ADDRESS>,>=<IP_ADDRESS>->open-interpreter) (2.31.0)
Requirement already satisfied: websocket-client<2.0.0,>=1.0.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from html2image<<IP_ADDRESS>,>=<IP_ADDRESS>->open-interpreter) (1.7.0)
Requirement already satisfied: blessed>=1.19.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from inquirer<4.0.0,>=3.1.3->open-interpreter) (1.20.0)
Requirement already satisfied: editor>=1.6.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from inquirer<4.0.0,>=3.1.3->open-interpreter) (1.6.5)
Requirement already satisfied: readchar>=3.0.6 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from inquirer<4.0.0,>=3.1.3->open-interpreter) (4.0.5)
Requirement already satisfied: comm>=0.1.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (0.2.1)
Requirement already satisfied: debugpy>=1.6.5 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (1.8.0)
Requirement already satisfied: ipython>=7.23.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (8.20.0)
Requirement already satisfied: jupyter-core!=5.0.*,>=4.12 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (5.7.1)
Requirement already satisfied: matplotlib-inline>=0.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (0.1.6)
Requirement already satisfied: nest-asyncio in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (1.5.8)
Requirement already satisfied: packaging in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (23.2)
Requirement already satisfied: pyzmq>=24 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (25.1.2)
Requirement already satisfied: tornado>=6.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (6.4)
Requirement already satisfied: traitlets>=5.4.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from ipykernel<7.0.0,>=6.26.0->open-interpreter) (5.14.1)
Requirement already satisfied: python-dateutil>=2.8.2 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from jupyter-client<9.0.0,>=8.6.0->open-interpreter) (2.8.2)
Requirement already satisfied: aiohttp in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from litellm<2.0.0,>=1.18.4->open-interpreter) (3.9.1)
Requirement already satisfied: click in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from litellm<2.0.0,>=1.18.4->open-interpreter) (8.1.7)
Requirement already satisfied: importlib-metadata>=6.8.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from litellm<2.0.0,>=1.18.4->open-interpreter) (7.0.1)
Requirement already satisfied: jinja2<4.0.0,>=3.1.2 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from litellm<2.0.0,>=1.18.4->open-interpreter) (3.1.3)
Requirement already satisfied: openai>=1.0.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from litellm<2.0.0,>=1.18.4->open-interpreter) (1.7.1)
Requirement already satisfied: python-dotenv>=0.2.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from litellm<2.0.0,>=1.18.4->open-interpreter) (1.0.0)
Requirement already satisfied: tokenizers in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from litellm<2.0.0,>=1.18.4->open-interpreter) (0.15.0)
Requirement already satisfied: contourpy>=1.0.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from matplotlib<4.0.0,>=3.8.2->open-interpreter) (1.2.0)
Requirement already satisfied: cycler>=0.10 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from matplotlib<4.0.0,>=3.8.2->open-interpreter) (0.12.1)
Requirement already satisfied: fonttools>=4.22.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from matplotlib<4.0.0,>=3.8.2->open-interpreter) (4.47.2)
Requirement already satisfied: kiwisolver>=1.3.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from matplotlib<4.0.0,>=3.8.2->open-interpreter) (1.4.5)
Requirement already satisfied: numpy<2,>=1.21 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from matplotlib<4.0.0,>=3.8.2->open-interpreter) (1.26.4)
Requirement already satisfied: pillow>=8 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from matplotlib<4.0.0,>=3.8.2->open-interpreter) (10.2.0)
Requirement already satisfied: pyparsing>=2.3.1 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from matplotlib<4.0.0,>=3.8.2->open-interpreter) (3.0.9)
Collecting joblib (from nltk<4.0.0,>=3.8.1->open-interpreter)
Using cached joblib-1.3.2-py3-none-any.whl.metadata (5.4 kB)
Requirement already satisfied: regex>=2021.8.3 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from nltk<4.0.0,>=3.8.1->open-interpreter) (2023.12.25)
Requirement already satisfied: tqdm in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from nltk<4.0.0,>=3.8.1->open-interpreter) (4.66.1)
Requirement already satisfied: monotonic>=1.5 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from posthog<4.0.0,>=3.1.0->open-interpreter) (1.6)
Requirement already satisfied: backoff>=1.10.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from posthog<4.0.0,>=3.1.0->open-interpreter) (2.2.1)
Requirement already satisfied: wcwidth in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from prompt-toolkit<4.0.0,>=3.0.43->open-interpreter) (0.2.12)
Requirement already satisfied: markdown-it-py>=2.2.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from rich<14.0.0,>=13.4.2->open-interpreter) (3.0.0)
Requirement already satisfied: pygments<3.0.0,>=2.13.0 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from rich<14.0.0,>=13.4.2->open-interpreter) (2.17.2)
Requirement already satisfied: h11>=0.8 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from uvicorn<0.28.0,>=0.27.0->open-interpreter) (0.14.0)
Requirement already satisfied: build>=1.0.3 in /data/data/com.termux/files/usr/lib/python3.11/site-packages (from chromadb<0.5.0,>=0.4.22->aifs<0.0.10,>=0.0.9->open-interpreter) (1.0.3)
Collecting chroma-hnswlib==0.7.3 (from chromadb<0.5.0,>=0.4.22->aifs<0.0.10,>=0.0.9->open-interpreter)
Using cached chroma-hnswlib-0.7.3.tar.gz (31 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [65 lines of output]
Traceback (most recent call last):
File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/core/init.py", line 24, in
from . import multiarray
File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/core/multiarray.py", line 10, in
from . import overrides
File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/core/overrides.py", line 8, in
from numpy.core._multiarray_umath import (
ImportError: dlopen failed: cannot locate symbol "PyExc_ValueError" referenced by "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311.so"...
  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/__init__.py", line 130, in <module>
      from numpy.__config__ import show as show_config
    File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/__config__.py", line 4, in <module>
      from numpy.core._multiarray_umath import (
    File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/core/__init__.py", line 50, in <module>
      raise ImportError(msg)
  ImportError:

  IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!

  Importing the numpy C-extensions failed. This error can happen for
  many reasons, often due to issues with your setup or how NumPy was
  installed.

  We have compiled some common reasons and troubleshooting tips at:

      https://numpy.org/devdocs/user/troubleshooting-importerror.html

  Please note and check the following:

    * The Python version is: Python3.11 from "/data/data/com.termux/files/usr/bin/python3.11"
    * The NumPy version is: "1.26.4"

  and make sure that they are the versions you expect.
  Please carefully study the documentation linked above for further help.

  Original error was: dlopen failed: cannot locate symbol "PyExc_ValueError" referenced by "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311.so"...

  The above exception was the direct cause of the following exception:

  Traceback (most recent call last):
    File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
      main()
    File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
      return hook(config_settings)
             ^^^^^^^^^^^^^^^^^^^^^
    File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
      return self._get_build_requires(config_settings, requirements=['wheel'])
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
      self.run_setup()
    File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 311, in run_setup
      exec(code, locals())
    File "<string>", line 5, in <module>
    File "/data/data/com.termux/files/usr/tmp/pip-build-env-5l9uibmd/overlay/lib/python3.11/site-packages/numpy/__init__.py", line 135, in <module>
      raise ImportError(msg) from e
  ImportError: Error importing numpy: you should not try to import numpy from
          its source directory; please exit the numpy source tree, and relaunch
          your python interpreter from there.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
’’’

Thanks for raising this @b9Joker108! Too bad that we're back to dealing with dependency issues. Have you had the chance to try any fixes?

I am sorry, I don't know what to do, or how to manage it. All I managed to do, was install the new version successfully without dependencies, and am unsure how to individually, manually install dependencies.

All good! I appreciate you bringing this to my attention. We've been so busy with the 01 project that I haven't tested termux with the new OI releases

I got approximately the same message. As well as one that stops me from installing patchelf pkg. I have 0 coding experience so am hoping to find that someone has solved these problems for me as i dont understand a thing lol

All good! I appreciate you bringing this to my attention. We've been so busy with the 01 project that I haven't tested termux with the new OI releases

Mike
Look, I am patient. I have a few other digital spotfires to put out at the moment. I am integrating two dotfiles management frameworks and ecosystems, at present, in my host Termux environment. That, and researching and writing the book on shell scripting, is keeping me busy. I don't really need OT right at the moment, I just use it periodically, and work its answers to my shell, system and coding questions, into my book.
I would just appreciate your help resolving the OT issues, when you have the time, and wish to do it.
Oh, by the way, I noticed OT was off-the-air on X/Twitter, for a bit. But, I see the OT X account, is visible again, which is good.
Thanks for your code.
Cheers
Beauford

I got approximately the same message. As well as one that stops me from installing patchelf pkg. I have 0 coding experience so am hoping to find that someone has solved these problems for me as i dont understand a thing lol

Just keep at it. There are always new problems. And, there are always new solutions. It is a constant dance. Just be patient, the issue will resolve in time, when Mike, gets around to it. Mike, is just busy, with the main non-Termux Open Interpreter gig.

Numpy import issues have been involved in all my error messages lately both for installing pkgs and for installing apt, so i wonder if its perhaps the source of the problem. Im not sure how well termux supports numpy, and i did hear mentioned that numpies compatability is heavily dependant on python version, i think python versions are hard to change so we are stuck with 3.11 and im not sure if numpy versions can work with that in termux? i tried numpy 1.24 i think and 1.25, but still got the same error. Thats all ive found so far but as i mentioned i am new to this i only got termux yesterday

Oh, i am actually trying to install open interpreter on my android with termux. But there is something called shell integration that may potentially get in the way so may have to find another way despite being so close.

Thanks, I had the same issue.but this seems to have worked so far

I have it loaded with a config error, is this going to be a problem. I am not sure what to do.
Pretty sure I uninstalled the original pkg
~ $ interpreter
/data/data/com.termux/files/usr/lib/python3.11/site-packages/pydantic/_internal/fields.py:151: UserWarning: Field "model_id" has conflict with protected namespace "model".
You may be able to resolve this warning by setting model_config['protected_namespaces'] = ().
warnings.warn(
/data/data/com.termux/files/usr/lib/python3.11/site-packages/pydantic/_internal/fields.py:151: UserWarning: Field "model_name" has conflict with protected namespace "model".
You may be able to resolve this warning by setting model_config['protected_namespaces'] = ().
warnings.warn(
/data/data/com.termux/files/usr/lib/python3.11/site-packages/pydantic/_internal/fields.py:151: UserWarning: Field "model_info" has conflict with protected namespace "model".
You may be able to resolve this warning by setting model_config['protected_namespaces'] = ().
warnings.warn(
▌ A new version of Open Interpreter is available.
▌ Please run: pip install --upgrade open-interpreter
──────────────────────────────────────────────────────────────────────────────────────────────────────────
▌ Model set to gpt-4
Open Interpreter will require approval before running code.
Use interpreter -y to bypass this.
Press CTRL-C to exit.

Its been a while, havnt been able to find any fixes anywhere else either.
I did have the idea though as a non-coder that if we could get oi installed we could then maybe use it to create a new environment and build and debug interpreter to get it to an os version on android and just share what it did. It might not be good enough to do that but might be worth a try

I even tried to install OI in a Python Virtual Environment and even that didn't help:
https://docs.python.org/3.11/library/venv.html

I only had it working with 0.2.0


Reference search shows matches in the same file under different paths

open https://github.dev/python/cpython/pull/29581
open Include/internal/pycore_ast.h
do a reference search for the enum FunctionDef_kind

-> the same match is reported twice in different files, but there is only a single pycore_ash.t in this repository

Looks like there is two variants of this file: one is the actual file (vscode-vfs-scheme) and another one seems to be from the review-scheme. I assume the later is from GHPR extension and should be filtered

Instead of having the static filter-list we should probably have an allow list which is all schemas file-search found - plus some special scheme, like notebooks


TOMEE-2316 Convert Markdown files to Asciidoc in the docs folder - 9

Part 9
[TOMEE-2316]

Approved. Looks good!


Assembly output not working

Something seems to be broken with assembly output. I get this:
   Compiling playground v0.0.1 (/playground)
warning: due to multiple output types requested, the explicitly specified output file name will be adapted for each output type

warning: ignoring --out-dir flag due to -o flag

    Finished release [optimized] target(s) in 0.35s

I tried poking around the source but it was just complicated enough that I couldn't figure out how it was invoking rustc.

Works fine:

When reporting bugs, please consider providing steps to reproduce them.

Sorry, this was a terrible bug report, I apologize! It turns out that the problem was that I didn't have a main function defined so presumably the compiler just optimized all my code away?
Here's the code I was using that was confusing me:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=0f71298048ce3bfb1cf579450f57a934
Changing fn foo to fn main makes it produce actual output (which makes sense in hindsight):
https://play.rust-lang.org/?version=stable&mode=release&edition=2018&gist=d5aef485ff6d3c2b3a9444771bc9ae2c

I didn't have a main function defined so presumably the compiler just optimized all my code away?

Yes, or make it pub fn foo.


Primitives V2 MVP2

URL, if applicable
No response
Describe the new content you are requesting.
Primitives V2 MVP2 is scheduled to release on April 1. This release will including the following enhancements:

Support dynamic circuits (without DD) in SamplerV2
Support measurement level 1 in SamplerV2
Support twirling in SamplerV2
Deprecation of primitives V1
Deprecation of backend.run

We'll need corresponding docs
[ ] Migration guide to go from backend.run to SamplerV2. This will include dynamic circuits & measurement level 1 that are currently supported by backend.run
[ ] Update existing V1->V2 migration guide to include twirling in SamplerV2
[ ] Some examples of using dynamic circuits / meas level 1 in https://docs.quantum.ibm.com/run/primitives-examples
[ ] Probably need to update / clean up the whole "Migrate to Qiskit Runtime" section
If this new content request is accepted, do you want to write the content?
I can help the team by providing enough information to write the material

I think the name of the current migration guide file will be confusing (qiskit-runtime-from-provider).  So I could rename it to something like qiskit-runtime-from-backend-run.  Thoughts, @jyu00 @ElePT ?


Update appveyor.yml

:white_check_mark: Build bitcointrade-sdk-dotnet 1.0.185 completed (commit https://github.com/guibranco/bitcointrade-sdk-dotnet/commit/b3aecf5348 by @guibranco)


Combination of $Exact and $Keys doesn't work

Link: https://flow.org/try/#0PTAEAEDMBsHsHcBQiAuBPADgU1AFQKIDKuoAvKAN6KigDkGATrAFZYDGKAzrQFyicoGASwB2AcwA01OgBMsnIWJHc+A4eKk16TVhwC0clAEMh0Xv0GjJ02g3ZYRKaGj2xsIrDPNqrUgL7I6NigAIJklKAA2gDWWGh8ACQA0nGcADwExAB8ALp8IgCuALYARlgMoAGIbLDKKKDwsAzRnHxh5FRajCzsXOYAjJqy8orKA0PaPfqGJmZ8gzZ2bA5OLm4OnuOIVUE4AELhCfgAHkYcaRRRsfGgyakZRLi5+cVlFX5Z0tW1AqAisCgAOpNaJWPgHDo2bq6PrzCZyBRKFSgBZdHS9AxYYymLZaJYrZyudybOHbL40RBAA
Should type B in the example above work or am I using it wrong?

The problem with {[key: $Keys<TEST>]: number} is that you cannot really enforce that you want to exhaust all possible values for key. You can use $ObjMap<T, F>:
type B = $ObjMap<TEST, () => number>;

const kindaWorking: B = {
  'projects': 1,
  'designs': 1,
  'project-detail': 1,
  'recently-opened': 'a', // still works :(
}

unfortunately, for some reason, B accepts string properties as well. i was able to fix this, but it's a bit ugly:
type B =$ObjMap<TEST, () => number>;

const uglyButWorks: B = {
  'projects': 1,
  'designs': 1,
  'project-detail': 1,
  'recently-opened': ('a': $PropertyType<B, 'recently-opened'>), // throws!
}

You can now use mapped type for this purpose


SOLR-17151 backport to 9x

https://issues.apache.org/jira/browse/SOLR-17151

again the pull request build failing with:This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.


Add Fine-tune SVM example notebook

Adds a notebook that trains a SVM that predicts species based on image embeddings created by BioCLIP. The SVM logic is based on https://github.com/samuelstevens/biobench by @samuelstevens.
Part of issue #76.

The docs COLAB link is for once this merges. So right now https://colab.research.google.com/github/Imageomics/pybioclip/blob/fine-tune-svm/examples/FineTuneSVM.ipynb can be used.


Skip duplicate EH clauses

Update RyuJIT to pick up the actual fix
Remove TODO and add assert to verify there are no duplicate clauses

Fixes issue #2262

The CI will fail until the jit package with the matching fix gets published.

@dotnet-bot test this please


WIP: Fix overlap between subplot titles and x-axis tick labels in viz.plot_*_psd()

This was brought up by @larsoner in https://github.com/mne-tools/mne-python/pull/9842#discussion_r729014409
MWE:
# %%
from pathlib import Path
import mne

sample_dir = Path(mne.datasets.sample.data_path())
sample_fname = sample_dir / 'MEG' / 'sample' / 'sample_audvis_raw.fif'

raw = mne.io.read_raw_fif(sample_fname)
raw.crop(tmax=60)

events = mne.find_events(raw, stim_channel='STI 014')
event_id = {'auditory/left': 1, 'auditory/right': 2, 'visual/left': 3,
            'visual/right': 4, 'face': 5, 'buttonpress': 32}

epochs = mne.Epochs(raw, events=events, event_id=event_id,
                    tmin=-0.2, tmax=0.5, baseline=(None, 0),
                    preload=True)

fig = epochs.plot_psd()

On main:

This PR:

@drammock
With the tight_layout() all, the figure looks better.
But I get this good old warning:
E   UserWarning: This figure includes Axes that are not compatible with tight_layout, so results might be incorrect.
3175

Is there a way to avoid (or just swallow) it? Is it safe to ignore it?

Thanks @agramfort!
But I'm also wondering if maybe I should simply make mne.viz.tight_layout() simply consume and hide this warning…

IMO it's useful for us to know when we're using tight layout on axes that don't respect it. So I would not swallow the warning. ( I also agree that subplots_adjust is preferable here)

Alright, thank you!

Seems to render fine:
https://36071-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/intro/10_overview.html#loading-data
https://36071-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/epochs/20_visualize_epochs.html#plotting-the-power-spectrum-of-epochs


Add Profile: rajdeepchakraborty-rc

A pull request should be created from this issue if not kindly ping @dinxsh ⚠
Profile link: https://github.com/rajdeepchakraborty-rc

@dinxsh Since no PR was created, I pinged you.

we're working on fixing the bot and will add your profile once its done, until then please wait, thanks!

Sure. Thanks for the reply.

@dinxsh just wanted to follow up on the status of the bot fix. Is it resolved?


Can't press down arrow in search results dropdown on https://mxnet.incubator.apache.org/

It would improve UX to be able to press the down arrow in the dropdown that appears when we search https://mxnet.incubator.apache.org/

@aaronmarkham

@ys2843 has this been taken care of?

@aaronmarkham @marcoabreu  Global search now supports keyboard control (up/down arrow select). This issue can be closed.

Thanks for adding the functionality Yang!
Can you point to which PR added keyboard control? Was it different from the one I mentioned above?

@ChaiBapchya I assume it is the dropdown of the search feature on the top navigation bar that need keyboard control. v1.6+ website has new global search feature #18288 which support navigating through results by pressing up/down arrow key.


P10 Pipette Function: Opt-In Modal

As a robot user, I would like to be proactively notified when the new P10 pipette function is available, so that I can decide whether to use it or not.
Acceptance Criteria

[ ] Modal pops up first time a user connects to a robot and P10 function is toggled off
[ ] Modal informs user of availability of new P10 pipette function (see copy, below)
[ ] User able to opt in or out of using the new function, setting the feature flag
[ ] User informed that this setting can be changed in 'Advanced Settings' at any time
Note we do not need a 'don't show again' checkbox

Copy
Title: "Important: Updated P10 Pipette Calibration"
Body:
"This release includes a refinement to the aspiration function of the P10 single-channel pipette based on an expanded data set.
Note this is a small but material change to the P10's pipetting performance, in particular decreasing the low-volume µl-to-mm conversion factor to address under-aspiration issues.
We recommend accepting this change, unless you are an advanced user who has manually modified your P10S pipette's µl-to-mm conversion factor
To use the updated calibration, click "Update P10 Pipette Function".
To temporarily continue using your current calibration, click "Not Now".
Please note you can change your selection in the 'Advanced Settings' menu. As always, please reach out to our team with any questions."
Buttons [ "Not Now" ] ["Update P10S Pipette Function"]

fyi @mcous -- don't think you've started, but I made a minor copy edit (1pm on 12/10)


Remove version: WinSCP.WinSCP.RC version 5.18.5-

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/winscp/files/WinSCP/5.18.5 RC/WinSCP-5.18.5.RC-Setup.exe/download
OK
(Automated message - build 923)

Close with reason: Package still available.;


Sample Data

Hello,
I am interested in working on the project, but I do not have any sample data.
Is there a good source for sample data?

I used http://www.rawastrodata.com. Specifically, I've been testing using the M42 and Bode's datasets.

Thank you


Deleting a User Account

Corresponding to Shay's comment on Rony's PR on the file: [house/models.py]
I think it could be an option in Mine Page, when he is logged in to his user, to have a button where it says: Delete Account
or something like that
There could also be a page of making sure the user wants to the delete his account
So we'll need an html file to the page consisting a django form or a simple html file consisting two buttons: Yes & No
connecting it to the Mine Page, and if he chooses to delete his account it could direct him to the login page
we could add it to the house urls or the account urls
What do you guys think?
@ronyyosef @shlior7 @ShellyGolden

It's a good feature but also not that necessary depends on our other more crucial features and our timeline. If we do want to implement this, I think there is no need for a Django form if you meant that, but an alert for the yes or no. And I'm pretty sure Django auth gives the option to delete accounts pretty easily

I agree with @shlior7 , we can discuss this in our next meeting

Our next meeting should be focused on building the presentation to the Demo
@ronyyosef
The Demo is in two weeks


fix(recs): modify the interfaces for contracts and implement with warp and remote service

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use it.

Hi, i have difficult to understand how can i use it?
Can you show me an example?
Thanks

Ok, i just solved.
Thanks.


proposal for additional data source -- full real-time BGP table

Hi,
Not sure if this is the right place to propose this, but I'd like to propose an additional source of data for asmap -- the full internet routing table.
This can be done by running FRR or BIRD in a container or a VM (cloud, etc), getting an eBGP peer with a provider that's willing to provide the full table, and then extracting the data into a format that can be used with asmap.   Multiple people/orgs can run these, and the table can be received from multiple networks.  The BGP peer for the table doesn't have to be part of any data plane, it can be just for sending the table, no routes accepted, etc.  It can also be remote (not ttl 1).
Would this be useful to this project and bitcoin core?
I can do this work and provide code and steps, just want to see if it's worthwhile first.

Hey @joe-bp thanks for the idea. If I understand correctly, this BGP peer would be limited to its provider's announcements, even if they are "global". We use a few sources which do a lot of this work for us, namely get route information from many BGP peers and collate it into one data source. We use multiple sources (and want to add more) to be able to compare them against each other and not rely/trust a single provider's view of the routing table.
That being said, more data could be good if we take the time to validate that it gives us something RPKI/IRR/Routeviews doesn't, and why. We can definitely do more here so thanks for the input!

Hi @jurraca thanks for the reply.
This sounded like a yes to the usefulness question, so I started the work.
Couple of points I'd like to make:

In my opinion, the RIPE RIS data is the most useful (for reasons below), however using it relies on a centralized data source that could change access or even manipulate data at will.  Using direct BGP routing table data from BGP itself is a means of obtaining that same kind of data but without having to rely on a single upstream organization (particularly not one under a hostile jurisdiction)
IRR and RADB records are often stale, incomplete, sometimes completely incorrect, and occasionally even malicious.  Also, many times these databases may say one thing, but what ends up being used by routing policies on carrier and edge networks can be completely different, particularly the further down from tier1/2 networks you go.  Pulling and using subnet+origin ASN from the actual routing tables provides the clearest and most accurate view on what's really going on
A couple people have asked/mentioned things like "but who's routing table?", and it's a very good point/question.  What I'm hoping to provide is a means for anyone interested in bitcoin infrastructure to be able to run this and pull their own BGP table data from multiple networks.  There are possibly thousands of tier2/3 network operators that will provide this kind of route feed ebgp peer, remotely, for a small fee monthly.  Just have to know what is being asked.

So, with all that, the first step was to grab the data in a useful format with some python.  Overall takes about 4 seconds to run on a small VM that has all ~1m internet routes:

ewr1-asdata1:~# time vtysh -c "show ip bgp" > bgp_table.txt; time python3 ./asmap_input_generate.py

real	0m1.500s
user	0m0.134s
sys	0m0.303s
Generated asmap_input.txt with prefix to ASN mappings.

real	0m2.424s
user	0m2.179s
sys	0m0.241s

I've attached that data file, just has subnet and origin/announced by ASN (routes that were accepted into the global routing table by carriers and ISPs)
asmap_input.txt
Next step is to get it into asmap
I'll be heading to tabconf next week -- is there anyone around that might want to meet and discuss this there?

Also, here's what a full bgp table looks like from FRR, and the python script to convert it into subnet/asn text file.  (subnet and announcing ASN are primarily what matters -- announcing ASN is the last one in the as path field)
bgp_table.txt.gz
asmap_input_generate.py.gz

@joe-bp Very cool, thanks for your interest in asmap and going with this alternative data sourcing approach. It's definitely interesting and it goes a bit along the lines of what I was thinking of when I wrote the "Using your own source" bit here: https://github.com/asmap/kartograf/issues/11 Though I had the few people in mind that already have the necessary BGP infrastructure running anyway, so their overhead would be minimal. Still, the general idea is similar I think.
A few comments/questions to make sure we are on the same page:

In my opinion, the RIPE RIS data is the most useful (for reasons below)

You probably mean most useful in terms of data completeness (getting all BGP announcements), in which case I would agree. That's both good and bad though, aside from the single data source issue the declared goal of RIPE RIS is to collect data for research so if there is a huge leak/hijack going on they really want to have it in their data set for researching it later which goes completely against our goals of course. FWIW, did you see our write-up on data sources? https://asmap.org/sourcing-data/ I am not sure what you mean by the reasons below though. You only speak about IRR and RADB being suboptimal but that's not what we are using.

IRR and RADB

We are not using RADB for the same reasons you laid out and in terms of other IRRs we only use the IRRs which are run by the RIRs. The reasoning is that they know their customer base (KYC FTW ;) ) and what each of them controls and they can filter the entries based on that, so the risk of wrong/outdated entries is minimized. Our primary source, however, is RPKI and we are getting less and less data from the IRRs as RPKI network adoption grows steadily. I am somewhat hopeful that we can kick out IRRs altogether as a source in the near future. (The last time I checked we got about 10% of the asmap entries out of IRRs. When I started the work on asmap I think it was more like 20%.) We are then using preprocessed data from Routeviews to backfill everything we don't have yet. Routeviews uses the same approach as RIPE RIS to collect their data so I see them as equivalent and due to the trust issues you mentioned yourself we believe there is no upside to processing the data ourself.

What I'm hoping to provide is a means for anyone interested in bitcoin infrastructure to be able to run this and pull their own BGP table data from multiple networks. There are possibly thousands of tier2/3 network operators that will provide this kind of route feed ebgp peer, remotely, for a small fee monthly. Just have to know what is being asked.

That would be cool and I don't want to discourage you from trying this but I have to say that I am sceptical that this will get high numbers of adoption. Paying a small fee to several network operators is probably not a small fee anymore? I also would suspect that paying them implies some business relationship between the node runner and the network operator which would require some version of doxxing yourself and your setup without significant additional anonymity-preserving effort. If this infrastructure is run continuously (to achieve real-time) it would probably require a separate server from the node as well. Can you say a bit about how this relationship would work in practice: Would you maintain a public contact list of network operators that provide this service to node runners for a pre-negotiated price or something like that? How many network operators would you recommend for a normal node runner and how would you discourage people from connecting to only one and possibly all the same one (the cheapest/most convenient)?
I would also recommend that the user runs an RPKI validator and checks the routes they are receiving for their validity status before including them in the asmap. This is really the single best thing to do for data quality. I am curious how you plan to reconcile the differences in the table data received from multiple network operators? Do you configure a preference sequence or something?
And, just to clarify, this means you don't see a point in comparing hashes of the final asmap with other peers because everyone will have a different result anyway right? (different network operator sources, different starting times etc.)

I'll be heading to tabconf next week -- is there anyone around that might want to meet and discuss this there?

I can't make it this time, unfortunately.

Not sure if this is the right place to propose this

Neither am I for what it's worth but I think here is a bit better than kartograf because I think this would best be implemented as a separate project because so far it sounds like the requirements could be quite different (continuously running etc.) and we could pull out parts of kartograf that are shared between the projects.

Thanks for the reply
I did review the write-up and your other comments -- think we're definitely on the same track on this.

A few comments/questions to make sure we are on the same page:

In my opinion, the RIPE RIS data is the most useful (for reasons below)

You probably mean most useful in terms of data completeness (getting all BGP announcements), in which case I would agree. That's both good and bad though, aside from the single data source issue the declared goal of RIPE RIS is to collect data for research so if there is a huge leak/hijack going on they really want to have it in their data set for researching it later which goes completely against our goals of course. FWIW, did you see our write-up on data sources? https://asmap.org/sourcing-data/ I am not sure what you mean by the reasons below though. You only speak about IRR and RADB being suboptimal but that's not what we are using.

I think this is the key area where my initial thoughts/approach to this are a bit different.  I'm coming from a background in carrier networking and routing -- forgive me if I'm saying things that everyone already knows or if I'm missing something key about asmap.
If the intent of asmap is to influence inter-node communications to be effectively much more decentralized and distributed in general (as opposed to just relying on /16 boundaries), then I think using IRR and RPKI data is perfect enough for that.  If the intent is -also- to prevent or protect against eclipse or sybil attack (by way of route hijacking), then I think the best data to use is the actual routing table, even when it conflicts with IRR and RPKI.
This is because RPKI and IRR data are also intended to help prevent hijacking and provide some level of BGP route AAA, making the data itself intent focused vs what can end up in the tables.  If I had to come up with an analogy -- IRR and RPKI data are like reading the laws that are on the books, but the routing table is like talking to the local police/authorities about what is happening in their jurisdictions.

IRR and RADB

We are not using RADB for the same reasons you laid out and in terms of other IRRs we only use the IRRs which are run by the RIRs. The reasoning is that they know their customer base (KYC FTW ;) ) and what each of them controls and they can filter the entries based on that, so the risk of wrong/outdated entries is minimized. Our primary source, however, is RPKI and we are getting less and less data from the IRRs as RPKI network adoption grows steadily. I am somewhat hopeful that we can kick out IRRs altogether as a source in the near future. (The last time I checked we got about 10% of the asmap entries out of IRRs. When I started the work on asmap I think it was more like 20%.) We are then using preprocessed data from Routeviews to backfill everything we don't have yet. Routeviews uses the same approach as RIPE RIS to collect their data so I see them as equivalent and due to the trust issues you mentioned yourself we believe there is no upside to processing the data ourself.

Both interesting and cool that so much of the asmap data is able to be derived from RPKI data.
The concern I have about RPKI, similar to above, is that the further down the network tiers you go (and further out to 2nd world and 3rd world regions), the less RPKI is used for actually validating route advertisements.  Particularly with the significant rise in peering points everywhere.  Every network geek in the world wants to run their own peering point (and many of them are) and those are free-flows of traffic between networks that usually won't turn on RPKI validation until they're forced to.
Side note: A concern I have with the bitcoin network today is that I believe (and working on proving) that it is highly susceptible to eclipse and sybil, particularly further away from tier1/2 networks.  I believe the two easiest way of reducing this risk is getting BGP table data into asmap, and increasing the default outbound connection counts from 8-12 to 48-64.

What I'm hoping to provide is a means for anyone interested in bitcoin infrastructure to be able to run this and pull their own BGP table data from multiple networks. There are possibly thousands of tier2/3 network operators that will provide this kind of route feed ebgp peer, remotely, for a small fee monthly. Just have to know what is being asked.

That would be cool and I don't want to discourage you from trying this but I have to say that I am sceptical that this will get high numbers of adoption. Paying a small fee to several network operators is probably not a small fee anymore? I also would suspect that paying them implies some business relationship between the node runner and the network operator which would require some version of doxxing yourself and your setup without significant additional anonymity-preserving effort. If this infrastructure is run continuously (to achieve real-time) it would probably require a separate server from the node as well.

Yep you're absolutely right, running this is not going to get high levels of adoptions from node runners, BGP and bitcoin core might as well be on different planets.
What I might envision is ~5-10 organizations in different regions that run this setup and provide access to the routing data specifically for asmap by way of http (and things like github).  Those organizations would be publicly known.  They could be bitcoin related organizations, or they could just be infrastucture or network operators properly motivated to provide this data.
Rough flow:
BGP table (view from X/Y/Z network) -> eBGP peer -> route collector and extractor (FRR and python on a VM/container) -> asmap-friendly data files -> public object storage (http, gh, etc) -> nodes-who-care
Couple of ways this could be implemented:

Org runs VMs/Containers on cloud and gets BGP table from cloud provider (ex: Vultr, Hertzner, AWS, OCI, etc).  Generally all of these costs are self contained in a cloud provider relationship, and can be done for about $20 per month.
Org runs VMs/Containers on their own infra and gets BGP table remotely (multihop eBGP neighbor) from paid relationships with a few networks.  This has split costs between running instances (low), and then the cost of eBGP peers to grab this data.  There are thousands of potential networks to get this data from, with a cost range of $1 to $100 per month.  There are also options like bgp-bmp.
Org runs VMs/Containers on their own infra and gets BGP table from their own network infrastructure.  If an org already has this infrastructure, the costs to run this are around the same as # 1.

I have scenario # 1 mocked up today (using Vultr), and will have # 3 mocked up in a few weeks.

Can you say a bit about how this relationship would work in practice: Would you maintain a public contact list of network operators that provide this service to node runners for a pre-negotiated price or something like that? How many network operators would you recommend for a normal node runner and how would you discourage people from connecting to only one and possibly all the same one (the cheapest/most convenient)?

Good questions.  I think if we're talking about the scenario of ~10+ orgs doing this work (if that's a feasible scenario, kind of like the orgs/nodes hosting the node seed data), all of that would need some basic initial coordination in order to get the most diverse data.  Getting a list of networks that would provide data could be as easy as asking for networks willing to via network operators mailing lists and orgs, like nanog.

I would also recommend that the user runs an RPKI validator and checks the routes they are receiving for their validity status before including them in the asmap. This is really the single best thing to do for data quality. I am curious how you plan to reconcile the differences in the table data received from multiple network operators? Do you configure a preference sequence or something?

Generally, the subnet:origin-ASN pairs in the global routing table will be consistent regardless of where you are or what networks you connect to.  What differs is the AS path (ASN hops in between) and other metrics to influence routing decisions, but that data probably isn't very relevant for asmap.  You will have larger blocks being advertised by carriers and provider ASNs, and then smaller subnets part of the larger blocks being advertised by other ASNs, but generally when an ASN is advertising a subnet, that pair -should- be the same everywhere.
Some exceptions:

An org is doing an ASN migration, in which case the same subnet could be advertised by multiple ASNs.
A misconfiguration between a carrier and a customer of the carrier
An actual route hijack

I think key point is -- seeing the exceptions is very useful

And, just to clarify, this means you don't see a point in comparing hashes of the final asmap with other peers because everyone will have a different result anyway right? (different network operator sources, different starting times etc.)

I would take the opposite approach, I would specifically compare all of the routing table data from as many sources as possible, and when an exception has occurred (differences in subnet:origin-ASN pair), reduce the trust of nodes in that subnet.  If there's a "default" hash or bucket where unmatched subnets currently fall, that would be a good place for the exception networks to fall.

Super interesting, thanks for the insight @joe-bp .

If the intent of asmap is to influence inter-node communications to be effectively much more decentralized and distributed in general (as opposed to just relying on /16 boundaries), then I think using IRR and RPKI data is perfect enough for that.

yes, that's the idea. Glad to hear it :)

If the intent is -also- to prevent or protect against eclipse or sybil attack (by way of route hijacking), then I think the best data to use is the actual routing table, even when it conflicts with IRR and RPKI.

I would say it's not an explicit (or immediate) goal of the project, but i've thought about it. The main difference is level of threat like you said, but also operational intent. Your idea would require detecting "live" anomalies to be useful, and I think most high-sensibility nodes would certainly be interested, but other more casual users wouldn't necessarily.

The concern I have about RPKI, similar to above, is that the further down the network tiers you go (and further out to 2nd world and 3rd world regions), the less RPKI is used for actually validating route advertisements. Particularly with the significant rise in peering points everywhere.

yea we need to be looking at this. Once we've got the ASmap generation a little more performant, I intend to look at the data more closely.

I think key point is -- seeing the exceptions is very useful

100%. I think we could learn a lot from this data. Like you said it's kind of the opposite of the current work, which is "get the best IP-to-AS map to users", but I would love to see the project grow to watch the routing table and provide infra for others to do the same.
Have you looked at real-time BGP stuff like Cloudflare Radar, or pybgpstream?

Thanks, leaving some further comments but either way you have my support to explore this project. I am mostly curious if we can learn from you about some weaknesses in our current approach that we could address independently of your approach.

If the intent of asmap is to influence inter-node communications to be effectively much more decentralized and distributed in general (as opposed to just relying on /16 boundaries), then I think using IRR and RPKI data is perfect enough for that. If the intent is -also- to prevent or protect against eclipse or sybil attack (by way of route hijacking), then I think the best data to use is the actual routing table, even when it conflicts with IRR and RPKI.
This is because RPKI and IRR data are also intended to help prevent hijacking and provide some level of BGP route AAA, making the data itself intent focused vs what can end up in the tables. If I had to come up with an analogy -- IRR and RPKI data are like reading the laws that are on the books, but the routing table is like talking to the local police/authorities about what is happening in their jurisdictions.

I am curious how you will know that the actual routing table data is better for us than RPKI data when they conflict. I would suspect that that's a route leak or hijack more often than not when that is the case and that's also what my take-away was from speaking with people at RIPE meetups. Would you just always take the route table over RPKI or do you have some further validation in mind that makes sure the differing route table data is legit? Is this happening for BGP peers that have RPKI implemented or do you now speak about those without RPKI? Would be great if you have some documentation or statistics on that because I think it's the first time I am hearing it if this means peers that have RPKI implemented still put entries in their routing table that conflict with RPKI data.

The concern I have about RPKI, similar to above, is that the further down the network tiers you go (and further out to 2nd world and 3rd world regions), the less RPKI is used for actually validating route advertisements. Particularly with the significant rise in peering points everywhere. Every network geek in the world wants to run their own peering point (and many of them are) and those are free-flows of traffic between networks that usually won't turn on RPKI validation until they're forced to.

It's not a big deal for them afaik. They don't have to do the validation themselves. They just have to sign once every few years that they control their IP block with their ASN and load it up to a RPKI repository. They don't have to run any software, just them signing and keeping that up-to-date would be enough for us on the asmap side when using RPKI as a data source. So there really isn't a barrier to adoption but sure, many still won't do it because YOLO. But if you run bitcoin nodes I am really not sure why you wouldn't invest 30 minutes to increase your security against BGP hijacks (assuming their provider has adopted RPKI and provides them with some kind of interface to sign/configure, something like myafrinic provides but honestly I don't know how this shapes up with the rest of the world, see https://afrinic.net/support/rpki/create-add-rpki-roa).

Side note: A concern I have with the bitcoin network today is that I believe (and working on proving) that it is highly susceptible to eclipse and sybil, particularly further away from tier1/2 networks. I believe the two easiest way of reducing this risk is getting BGP table data into asmap, and increasing the default outbound connection counts from 8-12 to 48-64.

How big do you expect the differences to be between the routing table and the routeviews collected data we use now? Do you see a weakness in how routeviews collects data that would lead to it missing significant parts of the routing table?

I would take the opposite approach, I would specifically compare all of the routing table data from as many sources as possible, and when an exception has occurred (differences in subnet:origin-ASN pair), reduce the trust of nodes in that subnet. If there's a "default" hash or bucket where unmatched subnets currently fall, that would be a good place for the exception networks to fall.

The unmatched nodes are in a separate bucket, so to leverage that behavior the table entries where there is disagreement would have to be excluded from the resulting asmap file entirely. If they are to be included with "reduced trust" that concept would need to be implemented in the bitcoin node software peer management and I guess the asmap file format would also need to change in order to be able to hold such information.


docs: add library schema docs

Closes #4
Adds documentation for how to add library and asset metadata files. Additional properties will be added in #6.
Changed

Simplified the response of the image optimization
Will update the prototype to use thumbnailPath instead of thumbnail

Review
Here's the markdown documentation.
https://github.com/carbon-design-system/carbon-platform/blob/b2e37d07d901f8e3f084c71a80ee484e9ca7f031/docs/resource-schemas.md

@andreancardona can you review this? In this first round of applying the schema to known libraries/assets, I'm thinking we'll just include the properties that I've documented in this PR: https://github.com/carbon-design-system/carbon-platform/blob/6607ad44c42b0b4b4f76152acff4a57e6e62bedf/docs/resource-schemas.md
Then after this feels good, via #6 we can add more properties to the schema, to the metadata files, then in the prototype.

@mattrosno Should we add a card to the backlog to turn the schemas into json/yaml schema files? If we have those on GitHub, they could be referenced by other projects to get code completion and property validation in real-time as they're being edited.

@jdharvey-ibm I don't follow your question. The application of the schema will take place in various repos in yml metadata files like this example: https://github.com/mattrosno/carbon-next/blob/e2f8bff6883f69a01feeb134b4b8a66414b5b07e/packages/react/src/components/Accordion/carbon-asset.yml
Our prototype is currently reading that YML data and parsing it into JSON.

@jdharvey-ibm bottom two issues in this epic will apply the schema for prototyping purposes.
https://github.com/carbon-design-system/carbon-platform/issues/2

@mattrosno Ah sorry, I'll try to clarify. I mean an actual formal json schema file that defines all possible fields that can exist in a carbon-asset.yml file or other file governed by a formal schema. This would be something like a carbon-asset.schema.json file that defines what fields are valid, what types they are, and where they can be used in one of the carbon-asset.yml files that an end user would place in their repo.
To use a schema, you include a line in your file to reference it, and from there, you get validation and auto-completion. Here's some pictures demoing me pulling in the example schema over at json-schema.org

@jdharvey-ibm got it - I'll document as a separate issue for schema tooling.
@andreancardona I added more documentation to describe value values: https://github.com/carbon-design-system/carbon-platform/blob/cdb912fa70c3cbe6dce4ddbef76bd7bb425e1b53/docs/resource-schemas.md

Markdown file has been updated: https://github.com/carbon-design-system/carbon-platform/blob/b2e37d07d901f8e3f084c71a80ee484e9ca7f031/docs/resource-schemas.md


Long press counter

Minor comments. lgtm otherwise. Excellent! Good job. 👍

I would make all text bold (in storyboard - font - type - bold)
And figure out Reset button left constraint (it should be closer to the edge of the screen)

lgtm


feat: optimistic concurrency control loop for IAM

Adds functions to DatabaseAdminClient and InstanceAdminClient that run a
optimistic concurrency control (OCC) loop for IAM updates. That makes
the customer code a bit easier to write and less error prone. This is
analogous to the Commit() loops for the spanner::Client.

This change is

Codecov Report

Merging #1162 into master will decrease coverage by 0.3%.
The diff coverage is 77.06%.

@@            Coverage Diff             @@
##           master    #1162      +/-   ##
==========================================
- Coverage   95.76%   95.46%   -0.31%
==========================================
  Files         170      170
  Lines       13159    13255      +96
==========================================
+ Hits        12602    12654      +52
- Misses        557      601      +44

Impacted Files
Coverage Δ

google/cloud/spanner/instance_admin_client.h
100% <ø> (ø)
:arrow_up:

google/cloud/spanner/database_admin_client.h
100% <ø> (ø)
:arrow_up:

google/cloud/spanner/instance_admin_client_test.cc
95.29% <100%> (+0.05%)
:arrow_up:

google/cloud/spanner/database_admin_client_test.cc
98.14% <100%> (ø)
:arrow_up:

...tegration_tests/instance_admin_integration_test.cc
86.36% <100%> (+0.15%)
:arrow_up:

google/cloud/spanner/samples/samples.cc
86.18% <72.72%> (-0.2%)
:arrow_down:

...tegration_tests/database_admin_integration_test.cc
54.41% <75%> (-38.09%)
:arrow_down:

google/cloud/spanner/instance_admin_client.cc
85.41% <75%> (-14.59%)
:arrow_down:

google/cloud/spanner/database_admin_client.cc
89.58% <82.14%> (-10.42%)
:arrow_down:

... and 6 more

Continue to review full report at Codecov.

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


Add a variable to control suffix text in the modeline

This should address Issue #7

I like this feature, but we should combine it with the implementation of #1 (since one might want a different suffix text for NN.NN years and AA.AA/BB years. @alraban thoughts?

Also another possible format XX.XX years left.

For me #1 would be difficult to implement while this was something I could attempt myself. It is also something I want more than the acturial death date feature.
Regarding getting the acturial table data into this package,

Is it going to be kept in this repo? I am not good enough with elisp data structures to attempt something like that.
Or will the package have to go online every time it updates the age calculation? I would not be too happy with a package that accesses the internet every day to maintain full functionality.

I should clarify that I am not against the acturial date feature, if someone implements it I would mostly use it myself.
I'm just of the opinion that there is no need to put this feature on hold until that feature implemented.

For me #1 would be difficult to implement while this was something I could attempt myself. It is also something I want more than the acturial death date feature.

I respect that and agree. We can write the code as a group effort.

Regarding getting the acturial table data into this package,
* Is it going to be kept in this repo? I am not good enough with elisp data structures to attempt something like that.

I would be in favor of not including any tables / formulas in this package because:

It's not clear which tables to use (they vary per country and based on many factors).
I personally think relying on average outcomes is not wise. To have the best chance against future regrets, it's wiser to assume a bad outcome.
Life is not about its length but the sum of your experiences; for most people it's better to have a bit of urgency and get to those experiences sooner. To people who have too many experiences, their body eventually sends a strong signal to rest; to people who have too few, the body doesn't send enough signals and life hacks such as this package are the main reminder.

* Or will the package have to go online every time it updates the age calculation? I would not be too happy with a package that accesses the internet every day to maintain full functionality.

I agree. I wouldn't put in any internet access.

I should clarify that I am not against the acturial date feature, if someone implements it I would mostly use it myself.

Would it work that people who want to use the tables can look them up on the internet? If there are some standard tables, we can link to them from the readme so people can find them easily.

I'm just of the opinion that there is no need to put this feature on hold until that feature implemented.

I agree that actuarial tables would be complex to implement. But if we just give users the ability to enter an arbitrary end date or age, that's quite simple and we can get it done soon.

I agree that actuarial tables would be complex to implement. But if we just give users the ability to enter an arbitrary end date or age, that's quite simple and we can get it done soon.

I agree with everything you said and this sounds reasonable. I can try and implement something like that. Should I do it in a new pull request?

Thanks for volunteering! Doesn't matter which pull request is used - whichever way you prefer to do it :) Before we start, it would be nice to get a third opinion from @alraban on how to do things since he requested #1.

With respect to this pull request, I think creating a variable to allow the user to choose their own string as a suffix is a good solution, as that offers the most flexibility in describing what is displayed, regardless of what is ultimately displayed, if that makes sense.

@alraban Do you have time / elisp skills to work on this? I'm very busy with the Scheme programming language and other stuff right now so elisp time is quite limited.

I have very limited elisp skills unfortunately, but I can take a hack.  That said, this pull request looks like a good solution to the suffix issue already; did you mean to suggest I take a hack at a pull for #1 ?

@lassik let's get this in now! I see #1 as orthogonal to this. Thoughts?

Yes, I don't think there is a reason not to merge this.

Thank you @aksharvarma for this contribution!  I have updated how it works, however, and I think this is now obsolete.  You can customize memento-mori-mementos with any message(s) that you want, so basically a prefix and/or suffix.
I'm going to go ahead and close this, but please feel free to open a new PR (or issue) if there is something else you would like to see changed!  I really do appreciate your work on this.


Use balena-semver insteat of the custom osVersionRCompare

Resolves: #681
Change-type: minor
Signed-off-by: Thodoris Greasidis<EMAIL_ADDRESS>
Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

That's on top of https://github.com/balena-io/balena-sdk/pull/682 .
I will rebase and mark as ready for review once the other PR is merged.

See: https://github.com/balena-io/balena-sdk/issues/686


Update spotlight

Updates pom to most recent spotlight version (29.1).

No longer targets pulibrary fork of spotlight.
Points to new pomegranate branch on pulibrary/spotlight-resources-iiif.
Created a new issue for the rails 5 upgrade: #116.

@eliotjordan Do you want to squash, or do you want to keep these commits to keep track of changes/version?

I was thinking to keep them as a record of the version changes. I already squashed commits where nothing changed outside of Gemfile and Gemfile.lock.

👏


Updated fallback lookup

Details
Updated mitre_enrichment.csv based on the release of ATT&CK 16.0
Now that we build against the local version of mitre/cti, we should probably assess cleaning this up.
Checklist

[ ] Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
[ ] CI/CD jobs passed ✔
[ ] Validated SPL logic.
[ ] Validated tags, description, and how to implement.
[ ] Verified references match analytic.
[ ] Confirm updates to lookups are handled properly.

Notes For Submitters and Reviewers

If you're submitting a PR from a fork, ensuring the box to allow updates from maintainers is checked will help speed up the process of getting it merged.
Checking the output of the build CI job when it fails will likely show an error about what is failing. You may have a very descriptive error of the specific field(s) in the specific file(s) that is causing an issue. In some cases, its also possible there is an issue with the YAML. Many of these can be caught with the pre-commit hooks if you set them up. These errors will be less descriptive as to what exactly is wrong, but will give you a column and row position in a specific file where the YAML processing breaks. If you're having trouble with this, feel free to add a comment to your PR tagging one of the maintainers and we'll be happy to help troubleshoot it.
Updates to existing lookup files can be tricky, because of how Splunk handles application updates and the differences between existing lookup files being updated vs new lookups. You can read more here but the short version is that any changes to lookup files need to bump the datestamp in the lookup CSV filename, and the reference to it in the YAML needs to be updated.

Neat update!


Automated Package Upgrade

:tada: This PR is included in version 5.0.516 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


DCC Official: Initial Release

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[ ] The pull request makes changes to files in only one sub-folder.
[ ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Dungeon Crawl Classics
This is the official Dungeon Crawl Classics character sheet. The sheet is fully integrated with the DCC compendium.
The sheet provides several automations and quality of life features.
Rolls
The sheet fully supports modifying your roll at the time you roll it through a modal pop up in the sheet that allows you to modify what dice you are rolling and what modifiers are being applied.
Additionally, you can roll misfire and corruption from the sheet.
Compendium Integration features
Drag and Drop
Spells, equipment, armor, weapons, NPCs and even rollable tables can all be drag and dropped onto the character sheet.When a rollable table is dragged onto an open sheet you will roll on that table and the result will be output to chat.
NPCs can be dropped directly to the virtual tabletop to create a character for them complete with token.
When you drag and drop a spell onto the character sheet, the mercurial effect of the spell will be randomly determined from the Mercurial effects rollable table. Note that if the result results in a reroll, you will need to manually reroll and apply the result.
Character mancer
If your game has the DCC compendium enabled, the sheet's character mancer will guide you through all the steps of creating and leveling up your character. This includes randomly generating your level 0 character and class selection at level 1.

Character Sheet Info Roll20 Internal Use only.

Hey @Kurohyou!
Everything looks great as always here, just one quick confirmation I need before we can go ahead and merge: Do you want this to be named "Dungeon Crawl Classics by Goodman Games" or "DCC by Goodman Games?" I'll keep an eye on this thread and merge this in as soon as we get an answer.
Best
Nora

Rudy let me know what to enter, so we're good to go!


Cop small refactors

Several small refactors to reduce the number of Metrics/AbcSize offenses.

rubocop should report 6 fewer Metrics/AbcSize offense.
All code changes should have coverage.
All tests should pass.

Coverage increased (+0.01%) to 91.291% when pulling 0e8940c38be9446207b5aa496f1a6b96395d8b3d on cop-small-refactors into a84ebc9cbd69121b8a37b92b95fb307d3382bcf7 on master.


Remove unecessary progress bar

A progress bar (shown below) is shown when opening the node sync info overlay. It is not necessary to have this and the bottom sync bar - just adds visual clutter. The sync bars are also styled completely different which doesn't look consistent.

Tested on Windows 10

Tested it on MacOS 11.1 and seems unnecessary..


Fix utils usage

While ImportError has already been fixed by https://github.com/openshift/aos-cd-jobs/pull/3031,  there are still a few leftovers from imports being removed from pyartcd/util.

/lgtm


Update AdminServlet.java

⛔ Snyk has found 1 issues.

Icon
Severity
Issues

Critical
0

High
1

Medium
0

Low
0

⛔ code/snyk check is completed. Snyk found 1 issues. (View Details)


Implement local cert provider

Today,  to configure notary verifier to read cert from local Path  customer will specify path in the verificationCert property . It will be cleaner to implement a local path cert provider in the k8 scenario notary verification.

As discussed offline with @susanshi, I feel we don't need to implement it since we already have inline cert provider.

Closing per Binbin's comment.


Issue with Modal

Describe the bug
Modal renders and behaves incorrectly in production mode (npm run build/npm start) works fine in dev mode. See attached screen shots.
Code example
The code is available from https://github.com/tomhornyak/modaltest.git
To Reproduce
Comment out line 12 in page.tsx to see the issue in production mode.

I'm seeing somewhat related issues the don't have "useSearchParams()" however I'm still working on try to make an example for debugging.

Styles are not being applied to Semcore buttons in production mode until the page is reloaded.
Drop downs " don't close when item is selected in production mode - works after a page reload. This happens on multiple pages.
To address these issues, I added location.reload() to hide the problem.
Once I can reproduce it in a small example outside our application, I'll log the issues,

No hurry, I replaced Semcore with PrimeReact and it solved all the problems I was having,