Too many open files OSError during initialisation

Describe the bug
For the Django project I work on, I would like to use reloadium with the python repl.
Usually to run the repl, I would type on the commandline python manage.py shell
But when using reloadium: reloadium run manage.py shell I get the following traceback
Traceback (most recent call last):
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/ll1l1lll1l1lll1lIl1l1.py", line 138, in l11l1llll1llll11Il1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1111l1l111ll1llIl1l1.py", line 326, in llllll1111llll11Il1l1
  File "<string>", line 4, in __init__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1111l1l111ll1llIl1l1.py", line 242, in __post_init__
  File "<string>", line 5, in __init__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1l1l1llll11lll1Il1l1.py", line 170, in __post_init__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1l1l1llll11lll1Il1l1.py", line 248, in l1lll1llllll11l1Il1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/lllllll111l1l1llIl1l1.py", line 389, in l11l1llll1lll111Il1l1
  File "<string>", line 12, in __init__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/lllllll111l1l1llIl1l1.py", line 332, in __post_init__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/watchdog/observers/api.py", line 291, in schedule
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/watchdog/observers/kqueue.py", line 450, in __init__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/watchdog/utils/dirsnapshot.py", line 251, in __init__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/watchdog/utils/dirsnapshot.py", line 283, in walk
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/watchdog/utils/dirsnapshot.py", line 283, in walk
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/watchdog/utils/dirsnapshot.py", line 283, in walk
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/watchdog/utils/dirsnapshot.py", line 259, in walk
OSError: [Errno 24] Too many open files: '/Users/me/Work/code/project/node_modules/queue-microtask'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/me/.virtualenvs/python/bin/reloadium", line 8, in <module>
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/__init__.py", line 20, in start
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1111l1l111ll1llIl1l1.py", line 612, in start
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1111l1l111ll1llIl1l1.py", line 596, in l1llll11ll11ll1lIl1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1111l1l111ll1llIl1l1.py", line 502, in l1l1lll11ll1ll1lIl1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1111l1l111ll1llIl1l1.py", line 325, in llllll1111llll11Il1l1
  File "/Users/me/.pyenv/versions/3.10.1/lib/python3.10/contextlib.py", line 153, in __exit__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/ll1l1lll1l1lll1lIl1l1.py", line 143, in l11l1llll1llll11Il1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/ll1l1lll1l1lll1lIl1l1.py", line 107, in l11ll1111lll11llIl1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1l1l111l1l111l1Il1l1.py", line 15, in l111ll11lll11l11Il1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1l1l111l1l111l1Il1l1.py", line 43, in ll1ll1l1111l1ll1Il1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1l1l111l1l111l1Il1l1.py", line 15, in l111ll11lll11l11Il1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/corium/l1l1l111l1l111l1Il1l1.py", line 24, in lll11ll1l1l111l1Il1l1
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/sentry_sdk/hub.py", line 105, in _init
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/sentry_sdk/client.py", line 85, in __init__
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/sentry_sdk/client.py", line 119, in _init_impl
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/sentry_sdk/integrations/__init__.py", line 93, in setup_integrations
  File "/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/sentry_sdk/integrations/__init__.py", line 41, in iter_default_integrations
  File "/Users/me/.pyenv/versions/3.10.1/lib/python3.10/importlib/__init__.py", line 126, in import_module
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1002, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 945, in _find_spec
  File "<frozen importlib._bootstrap_external>", line 1430, in find_spec
  File "<frozen importlib._bootstrap_external>", line 1402, in _get_spec
  File "<frozen importlib._bootstrap_external>", line 1539, in find_spec
  File "<frozen importlib._bootstrap_external>", line 1582, in _fill_cache
OSError: [Errno 24] Too many open files: '/Users/me/.virtualenvs/python/lib/python3.10/site-packages/reloadium/vendored/sentry_sdk/integrations'

Desktop (please complete the following information):

OS: MacOS
OS version: 12.6 (Monterey)
Reloadium package version: 0.9.4
PyCharm plugin version: None
Editor: commandline
Run mode: reloadium run

Additional context
It appears that reloadium (through watchdog) is not only scanning all my node_modules but opening the files too.
This is happening regardless if I set either the RELOADIUMPATH or RELOADIUMIGNORE environment variables.
I assumed I could configure it via reloadium_config.py since the Config object has ignored_paths and watched_paths but I think this scanning occurs prior to the config being loaded(?).
I believe this is more a problem with the vendored watchdog library, which also seems to also try limit you to 300 files in the pycharm plugin. This would be a problem for me since the django project I have as several thousand files.
Maybe you could use an alternate filesystem watcher like: https://pypi.org/project/watchfiles/

Maybe respecting .gitignore by default is also a good idea. I have some good experiences with gitignorefile.


Request to enable scrobbling for Saavn.com

Hi David,
Thanks for the great app. Is it possible to enable scrobbling for the music website Saavn.com?

Looks like not possible because Artist name not shown in player.

This could be done by querying song page and getting the artist name.
https://github.com/mayank127/web-scrobbler/blob/master/connectors/v2/saavn.js


Please Implement discovery.

Detect somehow if host is orangePI and install adapter automatically:
Find suitable example here

outdated


Add matchmaking servers

Partial implementation of matchmaking servers interface without server lists wrappers. The main principle is to create one structure with cpp virtual table and make another one structure which will be first element with callbacks inside, what matchmaking_servers_callback macro is doing. Main thing i don't like here is &CStr inside add_rule and add_player callbacks instead of &str. But there is no way to pass &str to callbacks with this macro because of lifetimes as far as i know. Also we can pass Cow<'_, str> from CStr::to_string_lossy() into them what seems to be a good solution

wow! just as I came to work on this, you've implemented it! will try this out later... <3

gonna create new pr without these first 9 commits


TypeScript Definition Files

Problem Description
Hi, it would be great to have TypeScript Definition Files as official oracle driver have that and it helps in rich experience in VSCode.
Thanks

Duplicate of #169 - this links to the TypeScript definitions..  When 1.12 is released to npm, I was going to nude @bigous to see if he can update them

Crap - wrong repo! Sorry @sagiegurari

In this repo, I don't think this will happen.
Too much maintenance because I got a lot of apis and I don't want to manage that.
You might want to look like @cjbj stated at oracle/node-oracledb#169 and see there, which basically an external contributor created that definition and submitted it to https://github.com/DefinitelyTyped/DefinitelyTyped
So you can do the same and I can reference your definitions file in my docs.


[INFRA] use tributors to list contributors and CITATION.cff for referencing

closes #66
relates to #627

Add new files to becomes the single, unambiguous, authoritative representation

the  .tributors file for the list of contributors, their info and their contribution type
the  CITATION.cff file for the bids spec version and potentially other metada of the repo to be used when releasing on zenodo
the .all-contributorsrc file for the required info to update the README contributors table

Add a script that uses tools/new_contributors.tsv as input and

update .tributors
uses .tributors to update .all-contributorsrc and CITATION.CFF

Add a script to update the contributors table in appendix based on .all-contributorsrc

Note that this table is now sorted alphabetically

The .all-contributorsrc is generated to make use all-contributors to generate a table of contributors in the README.

Changes little to the workflow for users to add themselves as contributors (or update their contributions): still done via the wiki, but they should now specify:

name:
contributions:
email (optional):
github (optional):
affiliation (optional):
orcid (optional):
bio (optional):
website (optional):

New contributors email should in any case be provided to the maintainers privately.

Before a new release, maintainers

manually update the tools/new_contributors.tsv'
run make update_contributors
a script updates:

.tributors
.all-contributorsrc (the tributors package handles this),
README.md contributor table (the all-contributors package handle this)
the authors field in CITATION.cff (can be scripted but may be refactored once tributors can handle this)

TODO

[x] identify github username of MANY contributors
[ ] add avatar in README for contributors that have no github account
[x] collect orcid numbers of contributors
[x] identify eventual duplicates
[x] ensure the final number of contributors matches the current list
[x] add worflow to validate CITATION.cff file
[x] update contributing and wiki to explain how to add oneself as a contributor / update contribution lists and for maintainers how to update those files
[ ] move institution that contributed to the acknowledgment section of the BIDS website, see also: https://github.com/bids-standard/bids-website/pull/279
[ ] figure out how PDFs will get released
[x] add caveat that contributors that do not add their email addresses may effectively exclude themselves from participating in elections

To discuss

[x] This will enforce an alphabetical order of contributors on zenodo. EDIT: Steering group approved of it

manually update the .tributors file with new contributors

FWIW, here is the workflow @vsoch (welcome to provide feedback here) prepared for datalad where we get a PR if tributors finds something needing updating (e.g. a new contributor, updated metadata etc): https://github.com/datalad/datalad/blob/master/.github/workflows/update-contributors.yml  So I guess similar setup could be done here.

identify github username of MANY contributors

FWIW, I don't think it is very reusable as-is but just an idea: here is the script I used to collate list of invitees for DataLad's JOSS paper https://github.com/datalad/datalad-git-bug-dumps/blob/master/tools/make-summaries .  The point was to invite also contributors to issues (not only code contributors), so we used  https://github.com/MichaelMure/git-bug (IIRC) to fetch all issues from datalad github repo (hence this large https://github.com/datalad/datalad-git-bug-dumps/blob/master/all-bugs.json ), and then populate list of invitees with aforementioned script.  I don't know if there are any contributors which aren't committers in BIDS though, so might not be worth the struggle.  But also it seems that git bug dump includes github logins (and names) so you could match a good portion of contributors... alternative -- just use github api to get list of all PRs and their owners, and names for those users.

I don't know if there are any contributors which aren't committers in BIDS though, so might not be worth the struggle.

In terms of issue openers that never commited I think we might have quite a few

But also it seems that git bug dump includes github logins (and names) so you could match a good portion of contributors... alternative -- just use github api to get list of all PRs and their owners, and names for those users.

Yup that should get me quite distance already. FLW

Thought about that.
There are already some emails in the tributors file already that were caught  by the tributor package when it pinged the github API to get a first list of commiters.
Before adding more however, I would like to make sure that contributors are OK having their email listed on there. Would make it more convenient for us maintainers but I am not sure that all would be OK with this.

Question for fellow maintainers. @sappelhoff @effigies @ericearl @bendhouseart
Currently this is shaping into having most of the info regarding contributors centralissed into a .tributor file... Except for the list of their contributions which would be in the .allcontributors
Even if the .tributor file was not made for this I am tempted to "hijack" it to put the list of contributions in there as well, so that we have only one file to update.
Any veto?
Also pinging @yarikoptic who may be able to tell if this is just a bad idea regarding the use of tributors.

Also pinging @yarikoptic who may be able to tell if this is just a bad idea regarding the use of tributors.

Let's ask @vsoch for the most competent advice on this. I think it should be feasible/sensible to also centralize storing types of contributions to .tributors.

Sure what is your question? I use tributors in several of my projects if you need an example recipe.

Thanks @vsoch
In brief: it would be easier for maintainers (and for the adventurous contributors) to only have to modify one file to update info about a contributor. We are assuming here that we are not using the contributor bot to do those updates.
At the moment, if a old contributor wants to update their list of contributions, this should be done in the .allcontributors file.
If a new contributor must be added, their info should go in the .tributor file but their list of contributions should go in the .allcontributors file.
Ideally I would prefer to have a single file to modify, to make easier for everyone.
So I am planning to also put the contribution list in the .tributor file and have a script to update everything else (.allcontributors, citation.cff, README contributors section and contributors table in the specification).
Any reason why this workflow would be a bad idea?

@Remi-Gau tributors doesn't require any manual updates - the action handles that.

@Remi-Gau tributors doesn't require any manual updates - the action handles that.
The point is that .tributors serves as a source of truth, and updates the other files. There isn't support for CITATION.cff (yet) but it could easily be added.

I forgot to mention that we do have contributors that are not on github and for whom we may just have a name but may have contributed to documentations, ideas in other ways (google docs...): so at some point we need to do some manual edit of some files.
The idea would be to still track their info and list of contributions in some way but to also do in one central place: hence why using .tributors as source of truth made sense.
But if I understand you correctly when we have a new contributor, you would suggest: add their info in their citation.cff (assuming tributors handles it), and also add their contributions in allcontrib but make sure that name of the contributor in each actually match so that tributors can properly merge that info?
Sorry to be annoying, I may be missing something obvious about how tributor works.

I think you would add to .tributors and then it would update CITATION.cff, given there is support.

I think you would add to .tributors and then it would update CITATION.cff, given there is support.

okidoki
will start going down that route then, thanks. 😃

Note to self.

Use cff github action for validation of cff file.
try relying on cffconvert for cff writing

Hey @Remi-Gau are there any plans to move the functionality for the .cff generation to resolve https://github.com/con/tributors/issues/58? ;-) then it would become immediately available to other projects

Sort of.
I was waiting for BIDS 1.8 to be in and for the steering group elections to be over to finalize this PR.
Was planning to look into looking to see if I can use some of the code from cffconvert to avoid reinventing the wheel there.

@sappelhoff
added a TODO in this PR to only keep "individuals" in the contributors and move institutions to the BIDS website.
also FYI: will work on this after the BEP for motion is in.

@sappelhoff
looks like we should be able to use this even before the next release

@bids-standard/maintainers
for anyone who may get involved in the release of the specs, I can give you a tour of what this does if you are interested (also to increase our bus factor) 🚌 🚌 🚌

for anyone who may get involved in the release of the specs, I can give you a tour of what this does if you are interested (also to increase our bus factor) 🚌 🚌 🚌

maybe a short tour during our next biweekly meeting?

TODO:
take into account direct changes to the contribution list: https://github.com/bids-standard/bids-specification/pull/981/files/38f38f78a1dd06f7dc5faf5c2dcc9ceeb83d2dc5..03e6badb072a005a07734440b99e7c4c1bab07b0

Possibly to be done after merging

[ ] add new contributors from the new BEPS (also add them to our "internal" list of emails) to make sure they will be able to take part in coming elections

Just a note that on the "recent contributors" WIKI, where contributors are supposed to enter their details, it currently says:
- name:
- contributions:
- email (optional):
- github (optional):
- affiliation (optional):
- orcid (optional):
- bio (optional):
- website (optional):

If all details except the name is optional, we should maybe include the caveat that contributors that we don't have contact information of are effectively excluding themselves from participating in elections etc. -- and may not even be considered "active contributors" if we vote for a governance amendment that defines "active contributors" as those that:

have contributed AND
have not explicitly opted out AND
we have valid contact information of (email address)

see also:

#1521

Actually I think we need to make it clear in the wiki that if people do not want to share their contact info publicly then they can do it privately but if we do not have a valid contact info then we can't count them for the votes.

This is in the wiki: https://github.com/bids-standard/bids-specification/wiki/Recent-Contributors#adding-yourself-as-a-contributor

As a BIDS contributor you can get to vote during BIDS steering group elections, but the maintainers will need some contact information to reach you.
If you add your email below, it will then appear on the repository (in our .tributors and CITATION.CFF file). If you do not want your email to be made public, then you should communicate your email to the maintainers privately so they can contact you.

Let me know if you think we need more.
@sappelhoff

Let me know if you think we need more.

I added an email they should write to<EMAIL_ADDRESS>which gets redirected to anyone who has access to the account signs up for this particular "forward rule", currently only me). Other than that, it's good!

2. ry whether dumping a CITATION CFF (from this repo at release time) together with a pdf into the manually curated zenodo entry can automatically updated the zenodo metadata (i.e., update the info without going via the github webhook)

Not seen any info in the zenodo doc that this would work.

switch on zenodo for the bids-specification repo --> on release, an entry will be automatically created with correct metadata informed by the CITATION CFF from this PR ... in a next step, when manually uploading the PDF to the other zenodo entry (as before), copy the citation cff metadata and add it to the manually created zenodo entry

Are we sure that if we do that we will keep the same generic DOI?
Should we ask zenodo in advance to see if some DOI magic needs to be done?

try whether dumping a CITATION CFF (from this repo at release time) together with a pdf into the manually curated zenodo entry can automatically updated the zenodo metadata (i.e., update the info without going via the github webhook)

create a new repository under bids-specification "pdf-releases", hook it up to zenodo, and start putting the BIDS spec PDFs in there piece by piece, always releasing each version. For the most recent ones, start adding the CITATION CFFs (they were not available for the earlier versions, so think of a solution for that). Potentially contact zenodo on whether they can remove / redirect the old DOIs to the new ones.

Other possibility, github allows cutting release from any branch, so we could have a branch that we just use for realeases that has only the pdf and the citation.cff for the metadata?

Are we sure that if we do that we will keep the same generic DOI?
Should we ask zenodo in advance to see if some DOI magic needs to be done?

it will be a different "generic" DOI. With this solution, we'd have BIDS version PDFs <1.9 under one DOI and >= 1.9 under a different one (if one takes the "generic" DOI that zenodo creates for all versions of a particular project. each PDF will of course still have its own DOI).
But yes, perhaps we can discuss solutions with the Zenodo team, however I am afraid that most requests we could have would be rather invasive, like: "can we cancel this project and redirect all DOIs to the new one?"

Other possibility, github allows cutting release from any branch, so we could have a branch that we just use for realeases that has only the pdf and the citation.cff for the metadata?

I would prefer having a dedicated repo for this 🤔  it seems cleaner to me and we wouldn't have to be careful if we ever wanted to archive the actual bids_specification repo content on zenodo.

Overall, I am in favor of my option 3 from https://github.com/bids-standard/bids-specification/pull/1115#pullrequestreview-1491846653
and in a next step asking zenodo whether they'd kindly close the currently existing zenodo project (https://zenodo.org/record/7263306) and:

redirect the generic DOI of that project (https://doi.org/10.5281/zenodo.3686061) to our then newly created and GitHub-linked project
redirect the spec version specific DOIs of that project(v1.0.0 until v1.8.0) to the then newly released spec version specific DOIs (of the newly created and GitHub-linked project)

If zenodo won't cooperate on that (which would be totally understandable, as it's a huge request) -- I'd bite the bullet of having each BIDS spec PDF from version 1.0.0 until 1.8.0 accessible under two different DOIs, which is dirty ... but life is messy. In that latter, messy, case we could upload one last release to the old zenodo project which contains just a README that says: "please look at this project instead".

Ok most of that makes sense to me but let's see what the other maintainers have to say about this at our next meeting

@sappelhoff
most of the zenodo / pdf issues discovered via this PR are kinda independent, no?
so we could merge this PR and open an issue to start the discussion afresh (easier for other people's to follow).

so we could merge this PR and open an issue to start the discussion afresh (easier for other people's to follow).

Yes. After you left the call yesterday, we agreed that it made more sense to get this in and then test any plans in the Zenodo sandbox. I don't think anybody else has the energy to review this, and it's not spec-related, it just needs to work.

Make buttons turn green.

#LifeGoals


Test all operators are documentated

This blog post describes an interesting way of using tests to ensure documentation coverage. It would be good to have a crack at using it, to help ensure everything is documented.
As well as operators, it would be good to test for documentation of recipes and command line options.

This would be covered by documentation lints in ruff, so #211 would also resolve this.


Clarify Student Names vs. Usernames

Coverage remained the same at 56.629% when pulling 3fd7eaf00c4172068f0b5d380d6fbf6ccc744a10 on classroom-names-displays into 32cb41ef58a25ed82e7ed653d1cae121f0cda60d on master.

Coverage increased (+0.1%) to 56.771% when pulling 3a0c2e7bf1d959e134909fa3ce14c6eb63ec34f9 on classroom-names-displays into 32cb41ef58a25ed82e7ed653d1cae121f0cda60d on master.


Add abstraction for Callable

In order to use Signal connect, we need a Callable as argument. There is currently no way to make one.
I'm also not sure about the security aspects of creating one, but for now just go ahead with the API

Implemented in https://github.com/libriscv/godot-sandbox/pull/156


[Sluggable] [PHP7] Unable to find slug

I'm using StofDoctrineExtensionBundle for the sluggable behavior and KnpLabs Doctrine Behaviors for the translatable behavior.
I have an entity where the slug is generated from translated properties and is also translatable. When running the app with PHP 5.6, everything is fine. But with PHP 7 I get the error:
Unable to find slug [locale] as mapped property in entity.
Here is the entity:
<?php

namespace AppBundle\Entity;

use Doctrine\ORM\Mapping as ORM;
use Gedmo\Mapping\Annotation as Gedmo;
use Knp\DoctrineBehaviors\Model\Translatable\Translation;

/**
 * Class CenterTranslation
 * @package AppBundle\Entity
 * @ORM\Entity()
 * @ORM\Table(name="center__center_translation"))
 */
class CenterTranslation
{
    use Translation;

    /**
     * @var string
     * @ORM\Column(type="string", length=255, nullable=true)
     */
    protected $title;

    /**
     * @var string
     * @ORM\Column(type="string", length=255, nullable=true)
     * @Gedmo\Slug(fields={"title", "locale", "id"})
     */
    protected $slug;

    /**
     * @return string
     */
    public function getTitle()
    {
        return $this->title;
    }

    /**
     * @param string $title
     * @return CenterTranslation
     */
    public function setTitle($title)
    {
        $this->title = $title;

        return $this;
    }

    /**
     * @return string
     */
    public function getSlug()
    {
        return $this->slug;
    }

    /**
     * @param string $slug
     * @return CenterTranslation
     */
    public function setSlug($slug)
    {
        $this->slug = $slug;

        return $this;
    }
}

When I run app/console c:cl -e dev, the cache is cleared successfully.
When I run app/console c:cl -e prod, the exception is thrown.
[Gedmo\Exception\InvalidMappingException]
Unable to find slug [locale] as mapped property in entity - AppBundle\Entity\CenterTranslation

When I try to access a page where the entity is used, in production and in dev environment, the exception is thrown.

We found the reason why this exception was thrown. See my last comment in StofDoctrineExtensionsBundle issue.


Error after input PIN in GuestMode

I implemented and use chromecast almost OK.
But when I tried to cast on chrome cast 3 by Guest Mode, I acidently got this error.
[0]: -[GCKClientCertificate importPKCS12:withPassword:]
Failed to import the PKCS12 Identity
does any one know why and how to fix it ?

Hi, can you provide a full log that you are seeing and steps to reproduce? We are investigating the issue.


Asterisk 13 Support

Try to get 2.6.0 work with Asterisk 13, I can see all the AMI events passing through to Adhearsion in the logs, but none of the controllers works, my guess is the current adhearsion/punchblock do not support AMI 2 protocol.
Is there any plan to support Asterisk 13?

Support for Asterisk 12/13 is indeed missing. No-one has properly tested / reported the full set of bugs or worked on fixing them. Contributions, even if just of properly formatted bug reports (see http://adheres ion.com/docs/dealing-with-bugs), are welcome.

Cool, will get bug reports ready once I've restored the testing environment.

Basic Asterisk 13 support is provided in Punchblock 2.7.0. See https://github.com/adhearsion/punchblock/issues/245 for details. If anything remains broken, please report individually and in full, referencing that issue.


[stable/mysql] Incompatible with default install of Kubernetes 1.16

Describe the bug
The mysql chart can't be installed on Kubernetes 1.16 unless the deprecated extensions/v1beta1 API version is re-enabled. This version has been deprecated since Kubernetes 1.8 and was disabled by default in Kubernetes 1.16 per https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/
Version of Helm and Kubernetes:
Any version of Helm, Kubernetes 1.16+
Which chart:
mysql
What happened:
Following the setup instructions in the README on a default Kubernetes 1.16 cluster, you get the following error:
$ helm install --name mysql-test stable/mysql
Error: validation failed: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"

What you expected to happen:
I expected following the setup instructions on a default install of Kubernetes to result in a working MySQL pod.
How to reproduce it (as minimally and precisely as possible):
Run helm install stable/mysql against a stock Kubernetes 1.16 cluster.
The fastest way to reproduce from scratch is to do minikube start, helm init with the canary build of Helm 2 (per https://github.com/helm/helm/issues/6374#issuecomment-537185486 ), and then helm install stable/mysql. It's possible to wind up in this state as well if you helm init on Kubernetes <= 1.15 and then upgrade to 1.16, without needing to use any pre-release software.
Anything else we need to know:
Fixing this is probably going to be somewhat messy. This chart doesn't specify an explicit selector, and apiVersions before apps/v1beta2 defaulted that field to have all of the pod labels, including the chart version. Selectors became immutable in apps/v1beta2, but the chart version changes every release. Removing those selectors before the upgrade is tricky with Helm if you're on <= 1.15 and impossible (without re-enabling the deprecated API) if you've already upgraded to 1.16. See https://github.com/helm/charts/pull/17627 for some options I came up with when I submitted a PR to the memcache chart, which has the same issue.
I'm happy to send a PR here as well, but I wanted to start the discussion before heading down that path since there are several options and testing an implementation isn't a great use of time if the approach isn't acceptable in the first place :stuck_out_tongue:

(Looks like this is going to be fixed in #17642 )


Update surah_1.json

Started the verse count from 0

I don't agree with this PR, because in every quran, surah alfatihah is included with bismillah.
So the verse in surah alfatihah is correct, must be start from 1, not zero.

Hello @SafwanAd-Dardak, I understand that you consider the verse to be an array of elements from a developer's perspective. However, I suggest that it be kept as a list of verses for ease of data consumption. From my perspective, it would be better if it remains unchanged.


// test //

🤐

@morenoh149 sorry about that, we were just testing GitHub PR reviewing! Locking the thread.


Need possibility to award an item without auction

player is targeted
go to inventory or dead boss
click BIND button
little window appears:
https://cdn.discordapp.com/attachments/908748099948793896/909429188660957204/unknown.png

What does step 2 mean exactly? Afaik looting or opening the loot window changes your target?

Yes, looting a boss changes your target. So it would only work this way form your inventory.
Are you aware that the option to award without auction is present, though not in a gui.
Target player -> /clm award [itemLink]/[value]

@dmitrysvito does the answer above solve your problem?

No user response. Assuming @Peleccotur response is enough


Unable to remove black borders for cutscenes in ultrawide

There's a injection by Helifax using d3d11.dll to do texture overrides for removing the black borders that appears in cutscenes during ultrawide gameplay. Unfortunately these two mods are incompatible together as you can't chain them.
Helifax's fix is available from here (RESIDENT_EVIL_2_UI.7z):
https://community.pcgamingwiki.com/files/file/1703-resident-evil-2-2019-fov-vignette-fix/

I believe his mod is based on 3Dmigoto:
https://github.com/bo3b/3Dmigoto/releases

I second this. I also created an issue on 3DMigoto....can one of you please look into it?


Interlinear glossed text

Cross-linguistic datasets often contain examples as interlinear glossed text (IGT) according to the Leipzig Glossing Rules (LGR). While this kind of data clearly can be modelled as tabular data, thus would fit into csv files, this format would probably go against the idea of having formats that can be easily edited by hand. To satisfy this requirement, a format that groups examples as blocks of aligned IGT constituents might be better suited. One candidate for such a format is the Toolbox variant exported by ELAN:
\utterance_id ...
\ELANBegin 5.708
\ELANEnd 8.974
\ELANParticipant
\utterance <text in source language>
\gramm_units <morphemes split by whitespace>
\rp_gloss <glosses split by whitespace>
\ft <translation>
\comment

The ODIN project came up with a custom XML format to store IGT:
<igt id="i840">
  <metadata type="xigt-meta">
    <meta type="language" name="czech" iso-639-3="ces" tiers="phrases words morphemes"/>
    <meta type="language" name="English" iso-639-3="eng" tiers="translations"/>
    <meta type="odin-source" doc-id="2990" line-range="3297-3299" line-types="L+DB G+DB T+DB"/>
  </metadata>
  <tier id="o" type="odin-raw">
    <item id="o1" line="3297" tag="L+DB">  (52) Pjdu        tam [já a ty]                                                    NP2 saw Bill , Alice VP, Alice V Bill , Alice saw NP, Alice saw</item>
    <item id="o2" line="3298" tag="G+DB">       will.go-1 SG there I and you                                                 Bill }                                          (Goodall 1987:2.21)</item>
    <item id="o3" line="3299" tag="T+DB">      'You and I wil l go there.'</item>
  </tier>
  <tier id="c" type="odin-clean">
    <item id="c1" line="3297" tag="L+DB">Pjdu        tam [já a ty]                                                    NP2 saw Bill , Alice VP, Alice V Bill , Alice saw NP, Alice saw</item>
    <item id="c2" line="3298" tag="G+DB">will.go-1 SG there I and you                                                 Bill }                                          (Goodall 1987:2.21)</item>
    <item id="c3" line="3299" tag="T+DB">You and I wil l go there.</item>
  </tier>
  <tier id="p" type="phrases" content="c">
    <item id="p0" content="c1[0:140]"/>
  </tier>
  <tier id="g" type="glosses" content="c">
    <item id="g0" content="c2[0:144]" alignment="p1"/>
  </tier>
  <tier id="t" type="translations" content="c">
    <item id="t0" content="c3[0:25]" alignment="p1"/>
  </tier>
</igt>

I think we clearly do not want to deal with any document-specific ordering/numbering/grouping of examples (which seems to account for much of the variation within the ODIN corpus).

One may argue that for alignments we have a similar situation, since we can annotated it in csv, but for manual editing, the most convenient way is to use tab-separated formats, unless one uses a specific tool to edit alignments. So we have for alignments the way to handle it in CSV, and the other formats that we did not really discuss so far, but which have been used, for example, in the alignment benchmark.

Btw. are there any standard packages for Python, R, etc. to read and write Toolbox files? The one I came up with is here: https://github.com/clld/clldutils/blob/master/clldutils/sfm.py

@LinguList I'd argue that one difference to the situation for alignments is that IGT are typically written by hand, whereas alignments are often(?) created automatically and consumed by programs.

Guillaume Jacques has hired some programmers (Céline Buret has done the main part) to convert from Toolbox to LaTeX and the like, they have one library here: https://pypi.python.org/pypi/pylmflib/1.0
Here's the github: https://github.com/buret/pylmflib
I have started to work on a toolbox-LingPy converter, without knowing of the work by Guillaume, since people told me it would be useful to have one:
https://github.com/dighl/lift

There is also some prior work (and data) here: https://github.com/langsci/lsp-xml
XML though, so not for manual editing.

@xrotwang I wouldn't be completely sure about that: if classical linguists make alignments, they will do them in excel spreadsheets. But I agree that we should encourage people to make alignments in the tools that we are developing for them, since otherwise it get's messy anyway.

The code from pylmflib seems to be pretty much tied to MDF dictionaries, i.e. makes assumptions about the semantics of markers. I don't know enough about MDF to tell whether it has standard markers for all the layers/tiers/lines we would want to have for IGTs.

There are some pecularities with how Toolbox counts (combining) characters for aligment when reading/writing UTF-8-encoded files (AFAIR, ELANs import/export might even differ in some cases). Hand-editing in a normal text-editor is an issue there. So one might want to define a strict subset (or rather a sane variant?) of the syntax (or rather use something else?).
Here is an R-Package that loads Toolbox-Files: http://bitbucket.org/tzakharko/toolboxsearch/

@xflr6 My first idea would have been csv, with a column MORPHEMES_AND_GLOSS, storing analyzed text and gloss as two lines of \t-separated chunks. But at least looking at such a file in LibreOffice, it didn't seem like a good idea. How does Excel fare with multiline cell values?

Excel doesn't handle multiline cell values at all. On import it treats a newline within a cell as an end of record, even if the cell is delimited with quotes.

@stevepepper oops. Good call. I guess this a showstopper.

JSON may be another good option, primarily because it

supports lists natively, so no need to markup morpheme boundaries with some custom markers,
lends itself to editing via JavaScript tools, which could easily be hosted online.

The format could look like this
{
  "iso_code": "nmn",
  "sentences": [
    {
      "gloss": [
        "3SG",
          "dry-PFV/STAT"
      ],
      "morph": [
          "ha",
          "\u01c1oo-a"
      ],
      "text": "Ha \u01c1ooa.",
      "trans": "It is dry."
    }
  ]
}

Does IGT really lend itself to being "modelled as tabular data"? A single instance might consist of:

(ID?, language?, source?, utterance?, segmented, glossed, translation?)

This could be represented as seven columns, but not intuitively (since they would be displayed horizontally, whereas they are typically presented vertically). In theory, the elements of the segmented utterance could be represented one per column with the gloss below them, but then you'd either need two rows, or line breaks within cells, which would be screwed up by Excel.
I think the ELAN representation is the better starting point, but I personally would prefer to see a minimalistic form of XML tagging rather than Latex-style commands:

Pjdu tam [já a ty]
Pjdu tam [já a ty]
will.go-1SG there I and you
You and I will go there.

In  and  morphemes are delimited by white-space. In this example,  is superfluous because there are no morpheme breaks inside words. The whole example could then be represented as JSON_DATA in a CSV file, could it not?

If you handle IGT with whitespace as delimiter in the columns as specified by @stevepepper , all you have to do is to define how whitespace inside a gloss will be distinguished from whitespace as delimiter. Than you have basically the same format we have for alignments and multitiered sequence representation in phonetic entries, where we also may have multiple values virtually aligned but put in different columns, like the word "th o ch t e r", it's simplified version in sound classes "T O X T E R", etc. Seems to be straightforward like that, given that we need to allow for one delimiter inside the cells anyway (at least I assume we will do so for the phonetic alignments).

AFAICT the Leipzig Glossing Rules do not allow whitespace in the gloss, other than to indicate word boundaries (morpheme boundaries are to be expressed as hyphens). So I guess, in terms of the data model, basically all alternatives are expressive enough. What remains is the problem of "manipulating by hand with a text editor".
Coming back to my use case: Currently, I have the following workflow in mind for submissions to dictionaria:

Author submits files.
Technical editor assesses technical correctness of files, including

linked multimedia files are available,
correctness of IGTs, i.e. number of morphemes in gloss and segmented text is the same,
etc.

Author fixes technical problems.

In many dictionaries the same examples are used for multiple entries. The typical toolbox way of dealing with this seems to be to copy&paste. So if we want authors to fix examples, they either have to do this for all instances of the same example, or we could offer a file with unique examples, extracted from their toolbox file. That's my favourite variant, in particular, because it would also work for submission formats other than toolbox; and that's my motiviation for requiring this format to be editable "with bare hands".

I start to think that JSON is the way to go. Another advantage over Toolbox (and XML as well) is that JSON requires a unicode file encoding, which will make some classes of errors when handling encodings impossible.

Maybe a good idea to include a version field in the format so the exact schema can be evolving.

@xrotwang -- For the specific use case of Authors-Fixing-Examples, a spreadsheet is almost certainly the best tool, with one morpheme per column, as here:

A
B
C
D
E
F

meta
53; ces; Forkel (2015:311)

utterance
Pjdu tam [já a ty]

segmented
Pjdu
tam
já
a
ty

glossed
will.go.1SG
there
I
and
you

translation
You and I will go there.

The first column is a label corresponding to the element type in the XML that I proposed above (or the style name in a Word or Writer document). This example would display better in MS Excel and OpenOffice Calc than it does here, because cell content that exceeds the cell boundary is visible when the following cell is empty. (In other words, column B would not have to be wider than the other columns, as it is here.)
Most importantly: One must distinguish between the underlying data model and the way it is represented for any particular purpose. The latter can vary: JSON lists in a database, CSV for simple editing (as above), specific styles in word processing documents, XML for some forms of interchange, etc. I believe we should define an abstract format (most easily expressed as XML, in my opinion) and mappings from it to multiple application-specific representations.
P.S. XML also requires Unicode.
P.P.S. Should we not also consider other use cases?

@stevepepper I think in this case the underlying data model is fairly well-defined by the LGR and what I'm after is the best representation for authoring/editing such data, where "best" is measured by

how well known the necessary tools may be to the average user/linguist,
how much validation could be off-loaded to existing tools,
etc.

@xrotwang I would like to see a formal definition of the data model, both to be sure that it really is well-defined and to establish common terminology. Don't you think that would be useful?
As for the average user/linguist, we can assume that (s)he knows Word and Excel, period. Many (but not all) field linguists will know Toolbox, so we should definitely cater for it, but it's is a legacy tool, so shouldn't build solutions around it. I would not want to have to explain to an average user how to edit JSON directly.
Most validation probably has to come from providing good visual feedback, but some could be implemented using relatively simple Excel macros with the model I proposed above.

I think the full data model is exemplified by this, using terminology of the LGR document as keys:
    {
      "segmented_words": [
          ["ha"],
          ["\u01c1oo", "a"]
      ],
      "glosses": [
          ["3SG"],
          ["dry", "PFV/STAT"]
      ],
      "text": "Ha \u01c1ooa.",
      "translation": "It is dry."
    }

Thanks. You may be right, but it's impossible to tell unless you provide the interpretation for this example as well. Can you show how it would be formatted in a grammar or dictionary? And what is the meaning of the slash in "PFV/STAT". I don't find the slash as a delimiter in LGR... Also, what kind of thing is "ha", and what is the relationship between X and Y in (a) [X], [Y] and (b) [X, Y]? We need names for these things.
In addition, one example is not enough. The definition of the model should take the form of a schema of some kind, against which we can test multiple examples.
I'm not trying to be difficult :-) I'm just worried that some important details might get overlooked if we don't have a formal description. I'll be happy once we have a schema AND a demonstration that every example in the LGR document can be represented in every detail...

@stevepepper I'm not too worried that important details might get overlooked, as long as I don't overlook essentials of my use case. The worst case then would be that I come up with a file format which is not as widely applicable as it could be, but I don't risk ending up - after a long time - with a format that is too big to be applicable in practice anywhere. So I'm aiming only slightly higher than "ad-hoc" and "de facto" :)

So, your goal is not to be able to represent every detail. That's fair enough, and it's probably the right decision. But it is an assumption that needs to be stated explicitly, if you want outsiders (like me) to contribute. That's where a formal model helps.

But isn't glossing always a sloppy business where nothing is really defined apart from the fact that one has at least two lines one which shows the original langauge and one which shows the target language, and things are aligned using whatever people can think of, especially in word?
Judging from known usecases, however, @xrotwang's example should leave at least for a second line of glosses, ideally for as many as one wants, since people may want to gloss more than two languages, as for example in those cases, where one has a specific writing system and a transliteration.

Slightly besides the point, I am aware, I just wanted to say that my ever-favourite glossed text collection is this one and it seems like it was also good fit for the less-techy people who were using it
http://www.univie.ac.at/negation/sprachen/annot-en.html

It is also my impression that although some things in glossing have
well-defined rules, not even those are seriously adhered to. I remember
Nordhoff giving the figure 40% for the IGT examples in a modern grammar
(Teiwa by Klamer) that actually follow the specification claimed.
Apparently many deviations were bracketed extra information of various
kinds. Maybe worth anticipating such a need in the format. all the best, H
2015-11-23 18:00 GMT+01:00 Johann-Mattis List<EMAIL_ADDRESS>
But isn't glossing always a sloppy business where nothing is really
defined apart from the fact that one has at least two lines one which shows
the original langauge and one which shows the target language, and things
are aligned using whatever people can think of, especially in word?
Judging from known usecases, however, @xrotwang
https://github.com/xrotwang's example should leave at least for a
second line of glosses, ideally for as many as one wants, since people may
want to gloss more than two languages, as for example in those cases, where
one has a specific writing system and a transliteration.
—
Reply to this email directly or view it on GitHub
https://github.com/glottobank/cldf/issues/10#issuecomment-158996082.

Another potentially superfluous observation, but if you haven't already take a look at some of the articles in this volume: http://nflrc.hawaii.edu/ldc/?p=263
to get a grasp of what the end-users think about. I bet most in this thread already has read everything there, but just in case. i've recently discovered that many people haven't seen those articles.
Btw, personally, I like gb4e
https://www.ctan.org/tex-archive/macros/latex/contrib/gb4e

My impression of language typology is being challenged hard these days. I was innocently assuming that all these things like glossing, describing the features of a language, and the like were nicely resolved, and thinking badly about the aberrancies of phonetic transcription and the dark sides of IPA, concept translation in Swadesh lists, but now it turns out this is a repeating patterns in all aspects of linguistics. The question is, however, should I feel some kind of evil Schadenfreude as a historical linguist, or should I just be sad about typology and historical linguistics?
@HedvigS, thanks for posting gb4e, I was trying to remember the whole day which package I used for glossing in LaTex...

Well, if you want to get all philosophical @LinguList I've also been thinking about this a lot (with less experience behind me of course) and I got to the conclusion that maybe diversity in methods and tools is not necessarily a bad thing - it might even be good. Diversity in analysis, as long as accessible and sufficiently motivated, keeps us from getting locked in into one perspective..
but perhaps let's save that discussion for another thread :)

yes, another thread, since this can become an endless discussion, but I think, too much freedom is at the core of all evil, although I hate to say this, since it contradicts all my political convictions...
But for another thread: we should think of following up on diversity (due to encoder variability) problems we encounter in typology but also in lexicostatistics (we have all similar problems there but people tend to ignore them). Maybe this could become an interesting investigation in the context of GlottoBank.

@LinguList  Agreed!
I vaguely rambled about similar things here: http://humans-who-read-grammars.blogspot.nl/p/help-linguistics-is-hard.html

@d97hah The WALS experience certainly supports the Nordhoff figure of (at most) 40% regular IGTs. That's why the clld db table for sentences has an xhtml column - that's where you stick all the weird things, paradigm tables, etc. I also think it's important to cater to this need, if only to make sure people don't have to sneak stuff into the more regulated fields. But again, JSON seems to have the easiest extensibility story of the alternatives considered so far.

Hi,
Sorry to be late to the discussion. I am keen to build an online set of IGT
with media, and developed EOPAS.org for that purpose. The specifications
are here:
http://www.eopas.org/help
It currently simply imports a particular Toolbox XML output or Elan .eaf
(using a given template). I will extend it to allow for FlexText format.
Given that this is how most linguists are creating their IGT it is easiest
to allow that to be imported.
Nick
On 24 November 2015 at 06:50, Robert Forkel<EMAIL_ADDRESS>wrote:

@d97hah https://github.com/d97hah The WALS experience certainly
supports the Nordhoff figure of (at most) 40% regular IGTs. That's why the
clld db table for sentences has an xhtml column
https://github.com/clld/clld/blob/master/clld/db/models/sentence.py#L57

that's where you stick all the weird things, paradigm tables, etc. I also
think it's important to cater to this need, if only to make sure people
don't have to sneak stuff into the more regulated fields. But again, JSON
seems to have the easiest extensibility story of the alternatives
considered so far.

—
Reply to this email directly or view it on GitHub
https://github.com/glottobank/cldf/issues/10#issuecomment-159043432.

@xrotwang Do you really expect authors to edit JSON text like the [example you gave above] (https://github.com/glottobank/cldf/issues/10#issuecomment-158898419)? Seriously?

@stevepepper No. JSON would be the best option when we have to provide
tooling ourselves.
Am 25.11.2015 08:46 schrieb "stevepepper"<EMAIL_ADDRESS>
@xrotwang https://github.com/xrotwang Do you really expect authors to
edit JSON text like the example you gave above
https://github.com/glottobank/cldf/issues/10#issuecomment-158898419?
Seriously?
—
Reply to this email directly or view it on GitHub
https://github.com/glottobank/cldf/issues/10#issuecomment-159526701.

@xrotwang OK. I'm relieved to hear that :-)  I guess I was confused by what you wrote earlier:

what I'm after is the best representation for authoring/editing such data, where "best" is measured by

how well known the necessary tools may be to the average user/linguist,
how much validation could be off-loaded to existing tools,
etc.

So the question of the best representation for authoring/editing IGT data remains to be answered, yes?
I made [a proposal a few days ago] (https://github.com/glottobank/cldf/issues/10#issuecomment-158932744) for how one might do this in Excel but no-one has so far commented on it. I have since shown it to a field linguist working on a dictionary for Dictionaria here at the University of Oslo and he confirmed that he would be comfortable working with such a format. Are there alternative proposals?

@stevepepper I do think your proposed spreadsheet format is a good representation for authoring and editing. It's just a bit inconvenient to process for tools, because of the variable number of columns.

@xrotwang I've always felt that 3 or 4 more lines of code is a small price to pay for a format that is maximally convenient and intuitive for dozens, if not hundreds, of users... :-)

@stevepepper I would guess "maximally convenient" for most users means "whatever they used before". So this why ELAN/Toolbox/Flex importable and exportable formats are on this list. With a couple lines of code it may also be possible, to fine-tune a JSON editor enough to be usable.

@nthieberger Thank you for the info on EOPAS - I think any format that already has applications supporting it should be prioritized. One question though: I'm told the Tolbox default markers for the tiers of IGT are \tx, \mb, \gl, and \ft. Why does EOPAS only understand \tx, \mr, \mg, \fg?

Indeed! These were just the fieldmarkers that I was using at the time it was developed (over 10 years ago for the first version). But of course this can be changed if there were an accepted standard for fieldmarkers, and there is going to also be an import routine for flextext files sometime soon.

More on this. From the perspective of an archive holding all kinds of material, each with its own way of being presented, a filetype for IGT would allow an EOPAS-style presentation of the text and media, while providing persistence and citability at whatever level of granularity was given in the text. In 2016 PARADISEC will experiment with a new filetype (.ixt) that will call a viewer (to be built) that knows how to present IGT and linked media. The .ixt format will be XML, based roughly on a Toolbox XML as follows (but open to discussion). We will write converters from Flextext to this format. We will also include manuscript images of text as time-aligned objects with the text (see e.g. http://<IP_ADDRESS>/transcripts/2). As this is only just starting development, input of good ideas is welcome!
<phrase endTime='1395.22' id='o_37' startTime='1388.22'>
<transcription>Go kiplake pa, kiplake pan, ranru matur. </transcription>
<wordlist>
<word>
<text>Go</text>
<morphemelist>
<morpheme>
<text kind='morpheme'>go</text>
<text kind='gloss'>and</text>
</morpheme>
</morphemelist>
</word>
<word>
<text>kiplake</text>
<morphemelist>
<morpheme>
<text kind='morpheme'>ki=</text>
<text kind='gloss'>3S.PS=</text>
</morpheme>
<morpheme>
<text kind='morpheme'>plak</text>
<text kind='gloss'>with</text>
</morpheme>
<morpheme>
<text kind='morpheme'>-e</text>
<text kind='gloss'>-TS</text>
</morpheme>
<morpheme>
<text kind='morpheme'>-ø</text>
<text kind='gloss'>-3S.O</text>
</morpheme>
</morphemelist>
</word>
[...]
</wordlist>
<translation>He took her and went, they slept until she became that man's wife.</translation>
</phrase>

@nthieberger Would startTime and endTime be attributes available on word elements as well? In general it seems that synchronization with an audio recording may be better off as content of a separate resource? If so, the question would be which parts of an IGT resource should be addressable via IDs from other resources.

Yes, time is currently at the level of the chunk (sentence, IU ..), but in EOPAS morphemes are citable (http://www.eopas.org/transcripts/212#!/p2/w5 cites a word) but within the chunk which is also citable (http://www.eopas.org/transcripts/212#t=19.44,22.24). I think that IGT must cite timecodes and be immediately playable in order to provide verifiability of the primary material.

Hi, I stumbled upon this page looking for something else, but since I see you mentioned the Xigt format we're using in the ODIN project, I thought I'd chip in. In case I repeat something already mentioned, I apologize for not reading every reply here carefully.
First, IGT data is vaguely tabular, in that it's intended to be read in aligned columns, but the annotation structure is actually more like a tree. One phrase is made up of many words, and each word can be several morphemes, and each morpheme may have several glosses. A translation usually follows the glosses, but it's better thought of as an annotation of the phrase than of words or morphemes. You can probably model an IGT with CSV/TSV files, but I think it would be difficult to do so accurately while keeping the general look of an IGT. Therefore, I think using spreadsheet software like Excel would be terribly limiting for producers of IGT. Toolbox is nice because of it's automatic "parsing" (i.e. morphological analysis) functionality. Other tools focus more on, say, aligning text to audio/video, or managing dictionaries, etc. Linguists will often use several tools in the process of creating IGT.
Second, the Leipzig Glossing Rules, despite the name, is a set of conventions for linguists to follow. Linguists often deviate from these "rules", so you can't expect any given IGT to fully comply with the LGR. You can't even reliably expect there to be the same number of space-separated tokens on the morpheme and gloss lines, or the same number of hyphens. Such as assumption will get you pretty far, but you'll have to abandon it if you want to cover many sources of data.
The purpose of the Xigt format is to better enable NLP tasks using IGT as the data source, so it might not be best for, e.g., an archival format. But if you're interested I'd be happy to explain how it could be used. It is canonically an XML format, but we also have a JSON format, on top of which we are building a REST+JSONP server for IGT corpora, and some other tools.
If you want to use Toolbox SFM files, the NLTK project has a Toolbox reader. I also created a Toolbox reader for the Xigt/ODIN stuff, with some functions to help return the proper annotation structure when the author didn't follow the LGR strictly.
This comment is getting long so I'll stop, but let me know if you have any questions.

@goodmami Thanks for the pointers, especially the one to sleipnir. A format (xigtjson) that already has tool support is certainly a good candidate for an interchange format.

I looked through the replies a bit more, and I should add that we haven't yet done anything in particular for audio data. Xigt is very free in what and how it annotates things, so there's nothing stopping someone from describing audio data, but we have so far only been concerned with text data and have not implemented audio (or video) playback or annotation in our applications. It would, however, be straightforward to port audio annotations from some other format into Xigt.
Also, @nthieberger, it's nice to see you here. I was inspired by your '09 paper titled "Culture clash – Humanities research and computing: a case study of Interlinear Glossed Text (IGT)" when we were creating Xigt.

I would be very interested in a module for interlinear glossed texts. I'm not sure it would be useful for editing, but it will most certainly be useful for quantitative analyses. Are you planning to include such a module in a future version? I have worked on a tool (an R package) for turning IGT (Emeld or toolbox) into a set of tables, with a relational data model. It also include a function for turning LIFT dictionaries into a set of tables in the line of the Dictionary module.
Best,
Sylvain

@sylvainloiseau There is a CLDF component for IGT. It exploits the fact that the CSVW spec provides a mechanism to specify secondary delimiters in CSV files, e.g. a separator for words in an IGT line. While this probably isn't enough to specify IGT exhaustively, it serves the purpose you mention: Making it simpler for tools like R to access (well understood) IGT corpora.


Firefox tests fail to run document.write calls

In order to introduce Firefox support in #53 I had to not execute tests on Firefox that include document.write calls because Firefox rejects those as Security Errors only when running as automated browser for a reason I don't understand.
Solving this at some point will be great.

From f2258c79d102441254d7cc1c2ed56c317c5e5805 such tests are skipped, but still need to be solved!

document.write is not so relevant anymore thanks to #118


Add getUsernameForFid helper function

Change Summary
Add a function to easily retrieve the username for any given FID. Works similarly to getAddressForFid.
Merge Checklist

[x] PR has a Changeset
[ ] PR includes documentation if necessary
[ ] PR updates the boilerplates if necessary

Thank you for this PR, it would definitely be a great addition to the library! Seeing as the endpoint returns all user data, I propose we parse and return it all. Please see my comments below

Yeah good idea, will update it to default to all options, and an option flag to return specific info

@turbowizardry no need to update the options to return specific info, the user can destructure the result and use what they need

We've rolled this change up into https://github.com/framesjs/frames.js/pull/24

Your contribution is appreciated @turbowizardry


A torch-like CrossEntropyLoss

Initially found a small mathematical error from the cross entropy loss calculation in CIFAR where
out.mul(Y).mean()
should be
out.mul(Y).sum(axis=1).mean()
Since this is probably the most frequently used loss function, I implemented a class inside tinygrad.nn that matches torch as well as tests.

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/nn/__init__.py                    9               0
------------------------------------------------------------
lines added in the tinygrad folder: 9

This should not be a class, it has no state.

I agree with no need to write as a class. I think when you first wrote CIFAR, you used sparse_categorical_crossentropy from extra/training.py And the difference is just resulting in a smaller loss value during training that I wouldn't able to catch if not crunching the last 1%.

I moved it in tensor.py as a function, under other functional nn ops but don't know if they should stay there.

Hmm, idk if we should put this in tensor.py either, probably just fix this in cifar for now.


Add bool methods

For #358

Codecov Report

Merging #909 into master will increase coverage by 0.08%.
The diff coverage is 86.2%.

@@            Coverage Diff             @@
##           master     #909      +/-   ##
==========================================
+ Coverage   63.93%   64.02%   +0.08%
==========================================
  Files          88       88
  Lines       14922    14974      +52
  Branches     3335     3345      +10
==========================================
+ Hits         9541     9587      +46
+ Misses       3175     3174       -1
- Partials     2206     2213       +7

Impacted Files
Coverage Δ

vm/src/obj/objint.rs
86.28% <100%> (+0.57%)
:arrow_up:

vm/src/obj/objbool.rs
77.88% <85.18%> (+7.88%)
:arrow_up:

Continue to review full report at Codecov.

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

@sapir thank you for contributing to this project. This is appreciated! I left one remark in your change.


msglist: Find web's dark-theme color for typing-indicator text; add to MessageListTheme

@PIG208, would you be able to do this, as a followup to your PR #790 which was merged? Here's the color that should be updated:
    return Padding(
      padding: const EdgeInsetsDirectional.only(start: 16, top: 2),
      child: Text(text,
        style: const TextStyle(
          color: HslColor(0, 0, 53), fontStyle: FontStyle.italic)));

Cross-linking: this forms part of #95.

I'll go ahead and take this; it should be quick, and I'd like to get it done today if I can. 🙂


fix: enqueue a single request for all resources

What this PR does / why we need it:
The current behavior of the controller is to run Reconcile for each resource that is updated. This gets quite expensive when you have 100s-1000s of resources.
This change allows for multiple resource updates to result in a single run of Reconcile.
This greatly reduces the cpu/memory consumption at startup and during periodic re-syncs of all resources.
Which issue(s) this PR fixes:

Fixes #1797

this is a neat idea, thanks for implementing this @dboslee, trying to understand this better, by using EnqueueRequestsFromMapFunc we've managed to create a specific Reconcile request with the same name for all Watch cases, which get coalesced / rate limited by the controller (since the name is same ) so we end up getting 1 reconcile request within a specific duration ?

this is a neat idea, thanks for implementing this @dboslee, trying to understand this better, by using EnqueueRequestsFromMapFunc we've managed to create a specific Reconcile request with the same name for all Watch cases, which get coalesced / rate limited by the controller (since the name is same ) so we end up getting 1 reconcile request within a specific duration ?

I think you've got it more or less. There isn't a specific duration here other than the rate limiting provided by the controller. Here are a few examples of describing the behavior.
At startup a single call to reconcile is executed since the controller will wait for all caches to initialized and events are coalesced.
In general, during a re-sync of many resources, any events that are processed before Reconcile is called are coalesced. If additional resource events arrive while the call to Reconcile is still running they will be coalesced in the next call to Reconcile.
The time in between calls to Reconcile is enforced by the rate limiters but its pretty quick by default.

this is a neat idea, thanks for implementing this @dboslee, trying to understand this better, by using EnqueueRequestsFromMapFunc we've managed to create a specific Reconcile request with the same name for all Watch cases, which get coalesced / rate limited by the controller (since the name is same ) so we end up getting 1 reconcile request within a specific duration ?

I think you've got it more or less. There isn't a specific duration here other than the rate limiting provided by the controller. Here are a few examples describing the behavior.
At startup a single call to reconcile is executed since the controller will wait for all caches to initialized and events are coalesced.
In general, during a re-sync of many resources, any events that are processed before Reconcile is called are coalesced. If additional resource events arrive while the call to Reconcile is still running they will be coalesced in the next call to Reconcile.
The time in between calls to Reconcile is enforced by the rate limiters but its pretty quick by default if not immediate when events occur.

ah makes sense, thanks for the explanation !


Set "noImplicitAny" to true per default?

Actually this is a question to all of you who are using this template.
In my experience it always made sense to set noImplicitAny to true, even though TypeScript doesn't do that per default.
What do you think?

As of version 2.0.0 this is now enabled by default.


Make readonly on the input fields overrideable

Here: https://github.com/airbnb/react-dates/blob/master/src/components/DateInput.jsx#L130
We found a little problem with this today. A colleague has a newer Dell laptop with .... a touch screen! And for him the input field does not accept any inputs.
Now I can totally understand why you added this feature but it would be really great if I had an option to disable it somehow or to override this...
Thanks a lot for your awesome component by the way!

I think this is fixed now! X_x If readOnly is explicitly set to false, then that will override the default isTouch fallback --- https://github.com/airbnb/react-dates/blob/master/src/components/DateInput.jsx#L194


Clicking vertical scrollbar for suggestions in IE closes menu

If the suggestions menu has a vertical scrollbar, e.g. has a max-width set, clicking the scrollbar closes the typeahead menu in Internet Explorer. The scroll bar works fine in Firefox and Chrome.
Affects at least IE8, IE11 (probably IE9 and IE10 as well).
IE8: Clicking scroll up/down icons works fine, but dragging the "scroll element" does not.
IE11: Clicking anywhere on the scrollbar closes the menu.
Tested using typeahead.js 0.10.1
Example fiddle: http://jsfiddle.net/r2a2G/

still happening

I'm not too sure why this is closed as I still experience this issue? Is there a fix for this? It even happens on the main examples page for the Scrollable Dropdown Menu.

Hi guys, just to let you know it looks like a bug in the latest IE11.0.47, which has reintroduced this bug.

In case anyone needs a solution, I basically made a version of _hacks() that relies on a focus flag set using mouseenter, mouseleave events on the menu. Seems to do the trick.

That's what I did too:
https://github.com/corejavascript/typeahead.js/issues/166

mouseenter/leave didn't occur to me until I saw this on a similar problem.
https://stackoverflow.com/questions/2284541/form-input-loses-focus-on-scroll-bar-click-in-ie


Remove the binary netCDF files from the repo.

Remove the binary netCDF files from the repo.
Partially fixes #379

Change Description
Removes the binary netCDF files from the repository.
The files
init_rect20x30.nc
init_rect30x30.nc

can be recreated using their respective scripts
make_init_rect20x30.py
make_init.py

These and all netCDF files that depend on the ERA5 and TOPAZ4 reanalyses can be found at ftp://ftp.nersc.no/nextsim/netCDF. These include the atmosphere and ocean boundary files used in the year-long reference run described by config_june23.cfg.
init_25km_NH.nc
init_rect20x30.nc
init_rect30x30.nc
init_topaz128x128.nc
25km_NH.ERA5_2010-01-01_2011-01-01.nc
25km_NH.TOPAZ4_2010-01-01_2011-01-01.nc
ERA5_2010-01-01_2011-01-01.nc
TOPAZ4_2010-01-01_2011-01-01.nc

It makes sense to remove these, as long as we have the info in the docs/readme how to create them.

See issue #379 and branch issue379_ncgenerator.

Perfect. Thanks Tim :tada:
What do we mean by partially fixes #379 ? this looks like a complete fix to me or am I missing something.

What do we mean by partially fixes #379 ? this looks like a complete fix to me or am I missing something.

I want to add scripting to the CMakeLists to regenerate the netCDF files that don't depend on external data.
Also, I rather thought that one of the tests depended on one of the deleted files. Apparently not.


Deploy SAP HANA as a Service

Tutorial URL: https://developers.sap.com/tutorials/haas-dm-deploying-haas.html
Step2 "Services -> Service Marketplace. Click on SAP HANA Service" - SAP HANA Service is not available as shown in the screenshot, just "SAP HANA Schemas & HDI Containers (Trial) ", and this one doesn't have "Enterprise" service plan as shown in the subsequent step when creating an instance.  Thanks for checking this.

You probably don't have the license for SAP HANA Service then. As the tutorial states:
This tutorial cannot currently be completed with a trial account.
Requires Customer/Partner License
You have a productive account with entitlement to the SAP HANA Service in Cloud Foundry

That explains it, thanks for the feedback.

We do have a trial offering coming soon. You can sign up to be notified once its available here: https://info.sapdigital.com/sap-hana-cloud.html


Need a test that verifies that mapping faults are 2MiB or 1GiB, and not 4KiB

The famfs kernel RFC v1 has fault counters that can be enabled via /sys/fs/famfs/...  These were implemented because we had a bug in the kernel module at one point that resulted in 4K mapping faults rather than 2M, and it killed performance for many concurrent computational processes hammering on the same data frame(s) in memory.
Famfs files are constrained to multiples of 2MiB, and mmap addresses are constrained to 2MiB alignment - both for this reason. But we need a good way to catch a regression.
However, the counters proved controversial (see thread [1]) so they will probably be dropped from the next version of the patch set. Dan Williams pointed out a user space test that ndctl uses to verify something similar [2], but I'm hoping we can do better. The first place to look is the rest of the thread at [1] to see of a prescription becomes clear.
[1] https://lore.kernel.org/linux-fsdevel/3jwluwrqj6rwsxdsksfvdeo5uccgmnkh7rgefaeyxf2gu75344@ybhwncywkftx/T/#m69d2b66e54f9657c38e6e0a0da94ab4b3eca7586
[2] https://github.com/pmem/ndctl/blob/main/test/dax.sh#L31

Note our smoke tests access the fault counters, so they will need to adapt to the new method (whatever that ends up being)


Suggestion: Less picky quarantine

What is your Test Scenario?
I am testing a large Angular application and there are some flakes. Testcafé does its best to prevent them but it is not always possible. Sometimes you have a test like:
await t
  .click(foo)
  .expect(somethingHappenedAfterClick);

Nothing too special, but sometimes for reasons I have yet to understand, Angular receives the click but decides not to do anything with that, just swallow it. I would have to click it again to make the expectation.
In short, a flaky test
What are you suggesting?
I discovered the quarantine mode today and it is INCREDIBLE. I have many many many tests and some of them fails (I have them identified).
From 10-12 flaky tests, with quarantine I am down to 2 unstable.
Are they really unstable? Not in terms of Fowler, it is a different thing in my opinion.
I have for example a dropdown with a sign out button and sometimes clicking the dropdown shows it and sometime doesn't. Maybe in 5 runs, fails 2. But the important thing here is that they only fail within testcafé. In the real app it works 100/100.
I would love for quarantine mode to have an option for unstable tests to not mark them as failures. Just a warning that says "Hey, this test need attention" but not to fail the test itself since it did pass at least once".
I understand that this is not its purpose, but it will make the life way way better for flaky tests that are outside your reach to fix.
What alternatives have you considered?
I considered other frameworks to see if they weren't having this issue. I have many tests (in different applications) that for some reason swallow clicks. It is like testcafé trying to do its job before Angular finishes rendering. I know there is an angular plugin but I didn't see a difference.
Additional context
Maybe this is not the PROPER solution for this, maybe there is a bug in testcafé with Angular, but in the meantime, this quarantine made my day.

Hi @Foxandxss,
Thank you for the suggestion, we will discuss it with the team. At the moment, a flaky test counts as failed if it fails more often than it passes (e.g. 3 times of 5 attempts).
As for the plugin, yes, we have the testcafe-angular-selectors plugin. Did you try calling the waitForAngular function before every test (please see the Examples section of the plugin's README)? This should prevent TestCafe from interacting with a page before Angular rendering is completed.

Hello @alexey-lin
I would like to group E2E tests like this:
a) Tests that always work as intended
b) Tests that normally pass but depends on something third party that could make them fail
c) Automated tool not behaving like it should
d) CI machine is not as fast as yours.
a and d are the easier ones. You can always tweak your tests so it is not speed dependant. You can always bump some timeout and you're good to go.
Quarantine is very nice with b because you will normally get a green result and if you start getting too many unstable then you know you need to work in it.
The problem lies with c. I have been doing E2E for over 5 years as a full time job but only with Angular and I have seen some strange patterns in different projects and I am yet unable to pinpoint a cause.
I have for example a page where after clicking a button and doing a process, it automatically redirects to a new one. For unknown reasons while executing this process within TestCafé the new page gets half loaded and I have to trigger a .click so it keeps loading. That is an easy solution, never flakes.
Then I have a case where I have a custom radio button that gets an active css class when selected. I have a test where I assert that this class applied (and that the other button would get it removed) and also some validation errors would appear. For unknown reasons there are some times where the active css class is not removed when toggling the radio buttons. Ok, here you can say that my code is wrong somehow, but you can toggle them 1.000 times on the real app and it would never ever do that but then in testcafé I can see visually how the two buttons gets the same CSS class when toggling.
It is like Angular behaves differently when Testcafé is driving it.
So this test kind of flakes on me.
Then I have many many cases (in separate projects even with different UI libraries and stuff) where I click a link or button that would trigger something (new page, section appears, etc) and Angular will just swallow the click and do nothing. Again this would never ever happen when using the app for real, but it does happen inside testcafé.
This tests flakes on mes as well.
I did try testcafe-angular-selectors but I didn't get anything different so I guess the problem comes from somewhere else.
I don't know if Angular is doing it wrong or Testcafé has a strange bug when using Angular.
Now is when we come to Quarantine. I can say that 90% of this flaky tests will happen once or twice every 10 executions so with quarantine mode I get way better results.
Am I misusing quarantine? I may, but when you get say 10 out of 200 tests that may fail or not and there is nothing you can do to fix them, it gets problematic.
My solution was to skip them with a comment saying "This is a flaky test". That is bad. I am losing value in there.
Now we get to the 10% that even quarantine doesn't set them straight. Right now I am putting the "This is a flaky test" comment on them. Better to get it on 1 every 200 tests. Those are still tests out of my control, that testcafé is making my application behave differently and sometimes I can hack through it and sometimes I can't.
So I would like a way to know when a test is unstable so I can do something about it or even a way to say "hey, run it up to 3-5 times, if it pass at least once, just tell me it wasn't that stable but move on".
To finish, let me share a hack I use. After creating an account I am presented with two choices, when I click one (it is a button) I get some extra options to continue. Sometimes when testcafé clicks the button it does nothing, even a second click does nothing and then maybe the third click goes in and everything moves forward. Since I do this process many times, I had to write this:
await t.click(sut.firstOption);

 for (let i = 0; i < 5; i++) {
    // Click didn't go through?
    const isVisible = await sut.wizard.visible;

    if (!isVisible) {
      await t.wait(1000).click(sut.firstOption);
      continue;
    }

    break;
  }

Basically it says click the button. If what should appear after it is not there (click was swallowed) try it again up to 5 times.
Sorry for the long answer, but I believe it was worth the insight.

@Foxandxss,
Thank you for your detailed explanation. As far as I understand, you have issues with event processing with Angular + TestCafe, and so your tests are flaky ( i.e. Angular "swallows" click? radio button does not get "active" class and so on).
In this case I think it's better to fix the cause of the issue but not to hide it with quarantine mode. Please share your project with us (or create a sample project) and we will try to find the cause of the issue and fix it if it's on our side.

I will try to reproduce it in a new project since this is a client work. But yes, I am with you here, if this is an issue with testcafe, we should be able to fix it.

@Foxandxss, Thank you for your collaboration. Feel free to create a separate issue if you reproduce this behavior.


Django 3+, Wagtail 2.8+

Thanks, but please have a look to the other pending pull requests at first: Django 3.0 support is already on the way with #63.

Thanks, sorry ))

Closing in favor of having merged #63. Thanks for both of your work on this.


Feature/merge time series schemas

Description

[x] Merge two core schemata used to specify time series data in a flex model, namely QuantityOrSensor and TimeSeriesOrSensor.
[x] Named new schema VariableQuantityField.
[x] Backward compatibility: deprecate old schemas, but keep them functioning for now (while logging a deprecation warning).
[x] Allow setting a SoC unit directly in some fields (formerly Float fields, and now Quantity fields), while still falling back on the contents of the soc-unit field, for backwards compatibility:

soc-at-start
soc-min
soc-max

[x] Allow setting a unit directly in fields that already supported passing a time series:

soc-maxima
soc-minima
soc-targets

[x] Allow passing a time series in fields that formerly only accepted passing a fixed quantity or a sensor reference:

power-capacity
consumption-capacity
production-capacity
charging-efficiency
discharging-efficiency
storage-efficiency
soc-gain
soc-usage

[x] Revise docs in flex-model-v2g.rst with regards to passing dynamic power constraints as part of the flex-model
[x] Remove all but one mention of the soc-unit field from the docs (still works under the hood)

Look & Feel
Synchronizes support for specifying time series data in a flex model in three distinct ways:

As a constant quantity, such as:"10 kW"

As a time series, such as (NB the below example assumes the unit is specified via a separate field):[
    {
        "value": 51,
        "start": "2024-02-04T10:35:00+01:00",
        "end": "2024-02-05T04:25:00+01:00"
    }
]

As a sensor, such as:{
    "sensor": 101
}

How to test
Work in progress.
Further Improvements

[ ] Add test cases for passing a time series to the new schema

Related Items
Aims at closing #1109.

In #1128 we also mentioned that:

we'd close #386
we'd add examples (of scheduling non-MW sensors) to the documentation

If this PR is the successor, then it should also take those promises over. They might be rather meaningful for users.

we'd add examples (of scheduling non-MW sensors) to the documentation

Moved to #1139


user_groups: Show deactivation error in modal itself.

Previously, the error was shown besides the group name after the modal was closed, but it did not look good for long error messages like the one we get when the group being deactivated is being used for a setting.
Updated the code to use dialog_widget.submit_api_request since it takes care of showing the error inside the modal and also added code to show loading spinner as the modal is not closed immediately to show the error.
Discussion

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @sahil839! I'm not entirely what mechanism closes the modal on a successful request.

It is just that instead of adding code to success_continuation function in the channel.post call, I changed it to use submit_api_request which already calls dialog_widget.close() in  success_continuation.


feat: adding Edgeware EdgeEVM Mainnet support

I have read the CLA Document and I hereby sign the CLA

recheck


Add connecting lines between bars

Connects the edges of the waterfall bars using the parameter connect_lines:

I really like this addition of hlines. I added a connect_lines_color option in the code


Delay creation of Flux that emits buffer based on fixed sized string and byte[].

Enables re-subscription on body so it is replayable for fixed size data (string, byte[]), no performance penality. Without this first consumption of body releases the memory and it's not replayable anymore, this will be an issue when user implements their own retry policy which does re-subscription on each retry.

Build output:

dist/com.azure/azure-common-1.0.0-SNAPSHOT.jar
dist/com.azure/azure-common-1.0.0-SNAPSHOT-javadoc.jar
dist/com.azure/azure-common-1.0.0-SNAPSHOT.pom
dist/com.azure/azure-common-1.0.0-SNAPSHOT-sources.jar


Added webcam status capability

Suggested PR which adds in webcam monitor capability if Teams is in a call, will check registry key to see if Teams is using the webcam. If it is, it will reflect "In a call - camera on". Otherwise, "In a call - camera off".
Likely needs testing and possibly a check on whether registry key is present or not to prevent errors.

Nice find :) What is your use case to distinguish between camera on or off?

If camera is on, door status light is red. If camera is off but teams is busy/in a meeting, status light yellow. Otherwise, green.
Let's family come in when green and ask questions. Come in but don't make noise when yellow. Don't come in when red since they'll be on camera.

If there's interest from others, I'm happy to add it to the master branch.

This would be great!  I'd use mine to turn my color coded light off (the one in the office) and turn it to white so I don't look red on camera :)
Great work & a big THANK YOU - I use this ALL DAY!

Any idea when / if this will be merged?

Any idea when / if this will be merged?

@tuffelh - not sure when @EBOOZ might decide to. Meanwhile, at least back from March, you could manually modify following these instructions: https://community.home-assistant.io/t/microsoft-teams-status/202388/61?u=dcnoren

I'll investigate what's possible in https://github.com/EBOOZ/TeamsStatus/issues/51


MiAIRR table for v1.2 release (stable) is broken!!!

Hi All,
I just noticed that the link to the table on this page:
https://docs.airr-community.org/en/stable/miairr/introduction_miairr.html
is broken. As a result, I don't think there is a way to get to the table of AIRR terms in the current spec on the stable docs branch... Not sure how long this has been broken!

I notice that the table is linked to the TSV file on master branch - which no longer exists... I thought the stable branch was linked to the 1.2.1 tag (the most recent numerical tag). Not sure how these things get pushed to docs site - so not sure what the right fix is.

I guess this will be less important when we release v1.3, but we should probably still fix?

Duplicate of #393.
I'm working on it. Didn't have time during the week to finalize the fixes. It builds in the docs-tables branch though.

I guess we could restore this link by putting the old TSV back into master temporarily, but yuck.

Probably not worth fixing for 1.2 and just fix through the v1.3 release???


C++ APIView: Flag items in the namespace _detail {.  i.e. anything that isn't under Azure:: but is within _detail

    We should flag items in the `namespcae _detail {`.  i.e. anything that isn't under `Azure::` but is within `_detail`

Originally posted by @RickWinter in https://github.com/Azure/azure-sdk-tools/pull/4809#discussion_r1038627946

@LarryOsterman, assigning this to you since I believe you're the one working on this.  If this was intended to go to one of the ApiView devs, please reassign.


运行cgc提示invalid verification-code  , verification-code  需要设置多少。看Reame里面没有提到要设置多少。

设置为UMUTech 提示  wensocket was gracefully closed at both endpoints

-u UMU   verification-code 123456


{default.repository.root} variable in mongo.yml

Hi,
Using the repository.root variable in mongo.yml throws an exception. It would be practical to use this variable in all configuration files.
config line: client_jar_url: ! '{default.repository.root}/mongodb/2.13.3/mongo-java-driver-2.13.3.jar'
Failing with:
Installing archive ... (1.0s)
E, 2016-04-17T14:51:14.849569 #14 ERROR – /tmp/buildpacks/5ff2ca7f7e3f4422b1d4e131cbc34544/lib/liberty_buildpack/buildpack.rb:50:in `rescue in drive_buildpack_with_logger': Compile failed with exception #<URI::InvalidURIError: bad URI(is not URI?
):
{default.repository.root}/mongodb/2.13.3/mongo-java-driver-2.13.3.jar>
bad URI(is not URI?): {default.repository.root}
/mongodb/2.13.3/mongo-java-driver-2.13.3.jar
Failed to compile droplet
-----> Retrieving and installing client jar(s) from mongo-java-driver-2.13.3.jar Exit status 223

Best regards,
Murat

This should be addressed by https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack/commit/cf6b3ec41ede38c7727fa38f6d588b8695869e84.


Uid gid changes

Opening PR on behalf of @bgruening as his solution is better than #34

groupadd: Permission denied.
groupadd: cannot lock /etc/group; try again later.

This is incompatible with -u.

Tested, working.

Eh, don't bother deleting the user, just sed /etc/passwd|shadow.
But yes, agreed, should be same user each and every time.

@jmchilton The only reason I left this code in is to make the start of IPython inside of galaxy-docker faster. I guess for simplicity on our side we can remove this code path.


fix(setup-wallet): dialogs and link

Related to:

YOMO-1304
YOMO-1306
YOMO-1307

@banklesss conflicts, any feedback from Product?

any feedback from Product?

yes im applying a little change. Will be done in a minute

done @stackchain


Dark mode feature added

Dark mode feature is enabled along with local storage functionality so that users' theme preferences will be saved in their local browser.
Additionally, modified the colour of the Introduction text to enhance its visibility in dark mode.

Resolves https://github.com/priyankarpal/Portfolio/issues/10

Looks Good 🎉

Yes Right : ))


Edit profile / password

While testing #365 I noticed that we ask the user to enter a password when updating their profile. When they do, I got an error saying that 'current password' is required but there is no field for it in the form. However, the profile fields I had changed were updated. :man_shrugging:
Anyways, I think we should have a separate password change action that requires the current password to be entered. The general profile form should not include anything related to the password at all.

This problem is actually caused by the old seed data. I fixed it in https://github.com/OfficeMomsandDads/scheduler/pull/358. If you re-plant your seed data, your default admin account should be set up properly to avoid this issue.

Which problem specifically? Doesn't the profile edit form still include a password field that is required?

Yes, the current password is required, and we could see about changing that. The problem solved by that PR is that the admin user didn't have it marked that they had accepted the invitation, and that's why the current password field wasn't showing up, so it was impossible to edit the profile of the default account.

Oh, I see! Great, thanks for fixin' that part (already!)


Maintenance: Release version 1.7.1

Summary
Fix release 1.7.0

Revert aspect injector to version 2.8.1
add tests

test 2.8.1 is present
test examples in pipeline

Revert metrics in examples

Why is this needed?
There is an issue with AspectInjector 2.8.2, and in release 1.7.0 AspectInjector was updated to that version by mistake. This would make the decorator not work, making all utilities have issues and metrics to throw null reference exception
Which area does this relate to?
No response
Solution
Revert AspectInjector to 2.8.1
Acknowledgment

[X] This request meets Powertools for AWS Lambda (.NET) Tenets

aws-lambda-dotnet blueprints - https://github.com/aws/aws-lambda-dotnet/pull/1587
sam cli templates - https://github.com/aws/aws-sam-cli-app-templates/pull/450
examples - https://github.com/aws-powertools/powertools-lambda-dotnet/pull/486

https://github.com/aws-powertools/powertools-lambda-dotnet/releases/tag/1.7.1


[Automation] Generate Fluent Lite from Swagger managednetworkfabric#package-2023-06-15

[Automation] Generate Fluent Lite from Swagger managednetworkfabric#package-2023-06-15

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-managednetworkfabric

/azp run java - managednetworkfabric - mgmt - tests

Breaking change approved in: https://github.com/Azure/azure-rest-api-specs/pull/25618
This API was never published to customer before.


⚠ Minecraft has degraded performance

In 8e11ae2, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1221 ms

Resolved: Minecraft performance has improved in bd40ec4.


[Themes] Fix empty files in host themes during app dev

WHY are these changes introduced?
https://github.com/Shopify/cli/issues/4793
When using app dev, host themes were getting overwritten due to a race condition between the minimum asset upload and the core job that handles theme installation when the src param`, causing potential issues during development.
WHAT is this pull request doing?
Prevents the upload of of minimum theme assets when a source URL is provided during theme creation.
How to test your changes?

Run app dev with a theme extension
Verify that the host theme is created with proper content
Ensure no empty files are present in the theme

Measuring impact

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

/snapit