[pwm/base_vseq] fixes/changes implemented within base sequence

replaces some values within the base sequence to use parameters defined within env_pkg,
also added invert to monitor config and adjusted the lowpower function.

CI failure
2022-05-26T14:27:46.5017208Z VERBOSE: [Launcher] xmvlog: *E,EXPRPA (../src/lowrisc_dv_pwm_env_0.1/seq_lib/pwm_base_vseq.sv,32|27): expecting a right parenthesis (')') [4.3][9.7(IEEE)].
2022-05-26T14:27:46.5019405Z ERROR: [Scheduler] [00:01:52]: [build]: [status] [pwm:default: F]

As with the other similar PR, the private CI failure is caused by a build failure. Please fix and compile your code, then re-push.

compile error as @rswarbrick  mentioned.
2022-05-27T20:55:58.2054598Z VERBOSE: [Launcher] xmvlog: *E,EXPSMC (../src/lowrisc_dv_pwm_env_0.1/seq_lib/pwm_perf_vseq.sv,30|35): expecting a semicolon (';') [SystemVerilog constraint block item].
2022-05-27T20:55:58.2056340Z ERROR: [Scheduler] [00:00:10]: [build]: [status] [pwm:default: F]


Extension for help in localization.

This is not an issue i'm listing, it's a new feature proposal. I would like to see/add some extension which will help to handle localizing of UIKit's components designed through storyboard.
Recently i'm working on localizing an app. Xcode giving great support while localizing strings which are  defined in the storyboard design. Storyboard generates a string/storyboard file for each storyboard & languages i wanted to support, which is great.
But the problem i'm facing whenever i update the Base storyboard i have to manually update the other language's string or storyboard files. I tried sneaking for some shortcuts, but couldn't find a better way to resolve this.
Then i come with an idea. I created extension with @IBDesignable and @IBInspectable for each Widgets in UIKit. In example for UILabel i created following extension
@IBDesignable
extension UILabel {
    @IBInspectable var localizedText : String? {
        get {
            return text
        }
        set {
            text = NSLocalizedString(newValue ?? "", comment: "")
        }
    }
}

So in storyboard i set the text in localizedText property and defined the corresponding localized text in Localizable.strings file. This way i maintain single string file which is shared by multiple storyboards. This methodology brings me several benefit

Single localized text is being used by multiple storyboard.
In case i have to share the localized file with client (for validation), i have to share only the Localizable.strings file.
A central place where all equivalent localization is present, which reduces repeating myself.
I don't have to maintain multiple storyboard/string file for each storyboard, it also helped me update the storyboard later when the design is changed.

I would like to hear your opinion on this aspect.

Hey @ratulSharker, sorry for my late response here 😅
I like how you brought strings from Localizable.strings file to the storyboard!
however, I think this seems more like it is own project since it expects users to have the Localizable.strings and requires some explanation before using


Fix README links

Accidentally used the image references to the project from which I copied the badges.

Coverage remained the same at 99.492% when pulling b57a67e08458e3c7b129dc350e00458a2035668e on enkessler:patch-1 into 6fceaf9ff2d2dc4fdd6aa0f1f75c93186e2f3e88 on grange-insurance:dev.

Coverage remained the same at 99.492% when pulling b57a67e08458e3c7b129dc350e00458a2035668e on enkessler:patch-1 into 6fceaf9ff2d2dc4fdd6aa0f1f75c93186e2f3e88 on grange-insurance:dev.

Coverage remained the same at 99.492% when pulling b57a67e08458e3c7b129dc350e00458a2035668e on enkessler:patch-1 into 6fceaf9ff2d2dc4fdd6aa0f1f75c93186e2f3e88 on grange-insurance:dev.

This fix is now included in #11


dbeaver-corp/dbeaver-i18n#123

Added missing translation

Terminology has to be fix in russian - https://postgrespro.ru/docs/postgresql/9.6/sql-grant


workflows/auto-pr: be more forceful

WIP, still working on debugging the auto-pr workflow.

Successful run: https://github.com/Homebrew/brew-pip-audit/actions/runs/4091289431/jobs/7055271713
xref https://github.com/Homebrew/homebrew-core/pull/122291

Some other things we need to do here (H/T @chenrui333):

Bump the revision of each formulae
Provide a better summary of the update in the PR description (which formulae are being updated + which vulnerabilities are being patched by ID)

Bump the revision of each formulae

There's no existing API for this (only a dev-cmd), so I'll probably need to break one out.

We don't need to bump revisions, that's no longer done I was told.

We don't need to bump revisions, that's no longer done I was told.

I thought so as well, but @p-linnane told me that we still need revision bumping -- without it these changes will only affect future installers of the same version of a formula, whereas with a revision bump it'll be correctly handled by auto-upgrades, etc.
Ref: https://docs.brew.sh/Formula-Cookbook#formulae-revisions

If you want to make changes to a formula that users will receive when running brew upgrade, but aren't incrementing the version, you will need a revision. The most common case for this is rebuilding dependents against an updated library.

Then we do want to bump version. Maybe we should get this working end-to-end (and automatically) and then cycle back to revision, since we'll probably want to add that into the existing library.

Maybe we should get this working end-to-end (and automatically) and then cycle back to revision, since we'll probably want to add that into the existing library.

Agreed; I'll shore this up and get it merged.

Got a little further, but now we explode if a bump doesn't happen to produce any changes (I would expect this to never happen, so I need to debug it):
Updating resources for termtosvg
Switched to a new branch 'bump-python-resources-termtosvg'
On branch bump-python-resources-termtosvg
nothing to commit, working tree clean
/usr/local/Homebrew/Library/Homebrew/utils.rb:324:in `safe_system': Failure while executing; `git commit --no-edit --verbose --message=termtosvg:\ bump\ python\ resources -- /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/termtosvg.rb` exited with 1. (ErrorDuringExecution)
	from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:607:in `block in create_bump_pr'
	from /usr/local/Homebrew/Library/Homebrew/extend/pathname.rb:303:in `block in cd'
	from /usr/local/Homebrew/Library/Homebrew/extend/pathname.rb:303:in `chdir'
	from /usr/local/Homebrew/Library/Homebrew/extend/pathname.rb:303:in `cd'
	from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:564:in `create_bump_pr'
	from generate-prs.rb:41:in `block in <main>'
	from generate-prs.rb:7:in `each'
	from generate-prs.rb:7:in `<main>'

Some more context:
Updating resources for termtosvg
Switched to a new branch 'bump-python-resources-termtosvg'
M	Formula/detect-secrets.rb
M	Formula/fdroidserver.rb
M	Formula/onlykey-agent.rb
On branch bump-python-resources-termtosvg
Changes not staged for commit:
	modified:   detect-secrets.rb
	modified:   fdroidserver.rb
	modified:   onlykey-agent.rb

no changes added to commit
/usr/local/Homebrew/Library/Homebrew/utils.rb:324:in `safe_system': Failure while executing; `git commit --no-edit --verbose --message=termtosvg:\ bump\ python\ resources -- /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/termtosvg.rb` exited with 1. (ErrorDuringExecution)

...so, separately, we should probably do some additional cleanup to ensure each branch is clean before bumping.

Feedback:

We should skip deprecated and disabled formulae (thanks @iMichka)
It looks like sometimes we downgrade versions (e.g., https://github.com/Homebrew/homebrew-core/pull/122410/files), probably because someone manually upgraded them only in Homebrew (which they shouldn't have)

65552ae skips deprecated/disabled formulae.

Another thing: it looks like we're not updating Python resources on HEAD. I'll look into it.

And another: we should think about only updating the listed vulnerable subdependencies, not all out-of-date subdependencies. This would make the diffs smaller and more topical, and would avoid any unnecessary breakage.

Another nice to have: the PR message body should probably include a URL back to the CI job, for rapid debugging.

This is mostly working, so I'm pulling the trigger on it.


Not possible to cancell armor equipment via rightclicking

I am currently running...

SpongeVanilla version:  1.12-7.0.0-BETA-289
Java version: 8
Operating System:

[x ] Linux (Ubuntu, Debian, Fedora, etc)
[ ] macOS
[x ] Windows

When a player has no armor and rightlicks with an armor in the main hand the armor is then put into armor section of player's inventory.
Depending on the  player actions ingame  before the item is moved from hotbar to armor inventory one of the following events is fired

InteractEntityEvent.Secondary
InteractBlockEvent.Secondary  - this one is surprisingly fired even if a player righclicks into the air.

I think it would be very helpful if cancelling such events would restrict players from equiping armor via rightclicks, however this is not the case right now. Even if the event is cancelled the amor still gets equiped.

ChangeEntityEquipmentEvent is not fired yet.
see https://github.com/SpongePowered/SpongeCommon/issues/1402

I'll look at this once https://github.com/SpongePowered/Mixin/issues/193 is fixed (which is currently preventing SpongeVanilla from running in my development environment).

Try listening to InteractItemEvent instead. That should work.

InteractItemEvent works


How to get django-tenants-celery-beat

Hi! I am a little newer to Celery and Celery Beat and this documentation doesn't fully explain this (or I just don't know), but I already have tenant_schemas_celery running in my project:
import os

from celery.schedules import crontab
from tenant_schemas_celery.app import CeleryApp as TenantAwareCeleryApp

from config import settings

os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'config.settings')

app = TenantAwareCeleryApp()
app.config_from_object('django.conf:settings')
app.autodiscover_tasks(lambda: settings.INSTALLED_APPS)

In a apps.periodic_testing.tasks.py file I have:
from celery.schedules import crontab
from celery.utils.log import get_task_logger
from django_tenants_celery_beat.utils import generate_beat_schedule

from config.celery import app

logger = get_task_logger(__name__)

@app.task
def add(x, y):
    z = x + y
    print(z)

app.conf.beat_schedule = generate_beat_schedule(
    {
        "tenant_task": {
            "task": "app.tasks.add",
            "schedule": crontab(minute=0-59),
            "tenancy_options": {
                "public": False,
                "all_tenants": True,
                "use_tenant_timezone": True,
            }
        },
        "hourly_tenant_task": {
            "task": "app.tasks.add",
            "schedule": crontab(minute=0-59),
            "tenancy_options": {
                "public": False,
                "all_tenants": True,
                "use_tenant_timezone": False,
            }
        },
    }
)

But I can't seem to get the scheduler working. Any idea of what I could be doing wrong?

And when I try to add a job through the admin panel I get:

DoesNotExist at /admin/django_celery_beat/periodictask/add/
Company matching query does not exist.


Failing patch request

Hi, I was trying to convert my scala tests in java ones. When I arrived to a PATCH request, it continues failing without any reasons at first sight and my logs gave me a 405 error saying POST method is not supported like following:
WARN  o.z.p.spring.common.AdviceTraits - Method Not Allowed: Request method 'POST' not supported
With help I finally looked it up in the Http.class from io.gatling.javaapi.http package  and it appears that for a simple patch request that is a post that is called (cf. line 54) instead of a patch.
@Nonnull
    public HttpRequestActionBuilder patch(@Nonnull String var1) {
        return new HttpRequestActionBuilder((new io.gatling.http.request.builder.Http(this.name)).post(Expressions.toStringExpression(var1)));
    }

Minor bug but confusing for beginners like me :)
Thanks for all what you've done anyway!!

Doh! Do you want to contribute a fix?

Sure what should i do?

Please fork the repository, send a Pull Request and sign our CLA.


feat: split cookie headers

feat: handler cookie headers for Response
chore: flag unhandled cookies

🔗 Linked issue
Related https://github.com/unjs/nitro/pull/989
Fix #988

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Continuing the work done by @oleghalin and applying it more generally to every presets that needs it.
Note that the culprit for this would be unenv, but fixing this in Nitro allows us to not add any dependency to unenv.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks. I think we can add fix to a wrapper of localFetch util directly so that entries using it already have fix

Thanks. I think we can add fix to a wrapper of localFetch util directly so that entries using it already have fix

We can do it like this  :
  function normalizedHeaders(fetch: typeof globalThis.fetch) {
    return async (...args: Parameters<typeof fetch>) => {
      const r = await fetch(...args);
      return new Response(r.body, {
        headers: normalizeOutgoingHeaders(r.headers),
        status: r.status,
        statusText: r.statusText,
      });
    };
  }

  // Create local fetch callers
  const localCall = createCall(toNodeListener(h3App) as any);
  const localFetch = normalizedHeaders(
    createLocalFetch(localCall, globalThis.fetch)
  );

I'm worried about the possible impact of changing $fetch for Nuxt, or something else besides the preset runtimes.
If the goal is to DRY we can add a localNormalizedHeadersFetch and call this in the presets.
I think I'll let you decide.

Yes, i still think wrapper method would be better idea.

Is there any reason why cloudflare, lagon, denos, netlify-edge, service worker and vercel-edge presets are using localCall ? They are all returning a Response.

Is there any reason why cloudflare, lagon, denos, netlify-edge, service worker and vercel-edge presets are using localCall ? They are all returning a Response.

They need to be upgraded feel free to include fix in same PR (basically i made that refactor back in time for other presets to prepare for this unified fix :D)

@danielroe tagging you for the Azure changes

Added some refactors and tests. While making tests discovered some issues. Netlify is fixed but we have Node (https://github.com/unjs/nitro/issues/1462) and Bun (https://github.com/unjs/nitro/issues/1461) to be fixed.
Probably on nitro-deploys with edge channel we can E2E test better on tests to.


Clean up main app UI code

Routing code used in PoC https://github.com/ruinernin/foxylists/blob/master/plugin.video.foxylists/resources/lib/router.py seems like a good candidate for cleaning up here.
Need to ensure backwards compatibility with current OpenMeta player.

Chunks of this have been cleaned up remaining is

[ ] root dir
[ ] scraping
[ ] providing
[ ] player


Bump golangci-lint to v1.47.2 to support Go 1.18

We're bumping test-runner to Go 1.18.3, and golangci-lint v1.42.0 doesn't work right with Go 1.18+, so let's bump the version here.
/kind misc
Signed-off-by: Andrew Bayer<EMAIL_ADDRESS>

cc @tektoncd/resolution-maintainers

/approve
/lgtm


issue adding objects in objdb

18:48:06.742-|ASTROM| ***************************************************************************
18:48:06.762-|ASTROM| Updating pending-list online database
18:48:06.784-**|ASTROM| ***************************************************************************
18:48:09.454-  |ASTROM| Adding OBJECT=TOI1442 to dataframe
18:48:09.475-!!|ASTROM| E[01-010-00001]: Unhandled error has occurred: Error <class 'AttributeError'>
18:48:09.475-!!|ASTROM|
18:48:09.475-!!|ASTROM| Traceback (most recent call last):
18:48:09.476-!!|ASTROM|  File "/apero/apero-drs/apero/core/utils/drs_startup.py", line 432, in run
18:48:09.476-!!|ASTROM|    llmain = func(recipe, params)
18:48:09.476-!!|ASTROM|  File "/apero/apero-drs/tools/bin/apero_astrometrics.py", line 195, in __main__
18:48:09.476-!!|ASTROM|    drs_astrometrics.add_obj_to_sheet(params, add_objs)
18:48:09.477-!!|ASTROM|  File "/apero/apero-drs/apero/tools/module/database/drs_astrometrics.py", line 1155, in add_obj_to_sheet
18:48:09.477-!!|ASTROM|    dataframe = dataframe.append(astro_obj.to_dataframe())
18:48:09.477-!!|ASTROM|  File "/conda/miniconda3/envs/apero-env/lib/python3.9/site-packages/pandas/core/generic.py", line 5989, in __getattr__
18:48:09.477-!!|ASTROM|    return object.__getattribute__(self, name)
18:48:09.477-!!|ASTROM| AttributeError: 'DataFrame' object has no attribute 'append'
18:48:09.478-!!|ASTROM|
18:48:09.696-**|ASTROM| ***************************************************************************
18:48:09.721-@!|ASTROM| W[40-003-00005]: Recipe apero_astrometrics has NOT been successfully completed
18:48:09.744-**|ASTROM| ***************************************************************************

offline Wed Aug 16 08:48:10 spdrs@apikipiha: /data/spirou4/apero-data/offline/runs

I've tried killing my screen and re-launching the python env for the DRS, but it didn't help.

Hi Luc,
Sorry about this, this is due to an update with pandas, I already fixed this in v0.7.287 but you can't use that version yet.
I'll add this update to the v0.7.286-stable-test.

Do a git pull now and it should work.


New features

Hi,
Here are the changes that I made.

Added one more endpoint ('/get-all')
Enabled filtering by song or album
Updated the database so that all names of albums or songs are in title case
Updated index.html so that it has the new endpoints

The new endpoint allows getting all the lyrics in the database that match the filters. For example, https://taylorswiftapi.herokuapp.com/get-all?album=reputation or https://taylorswiftapi.herokuapp.com/get-all?song=Call%20it%20what%20you%20want
The same filtering options are available for the '/get' endpoint.
If there's something you want me to change, just tell me!
Thank you for letting me participate!

The end points are amazing. I will cross-check once before merging.


Add support for making columns optional from Pydantic model

Sometimes, when I use sqlalchemy_to_pydantic to create pydantic model, I want to make some columns and all columns to be optional for a patch requst.

Thanks for the interest! And thanks for the patience with my reply. :sweat_smile:
I deprecated this library a while ago in favor of SQLModel which would solve all the same use cases in a much better way, and I'm directing all the effort in that direction, so sadly I wouldn't be able to take new features here (that would also need maintaining them).
Given that, I'll close this one, but thanks for the effort! :coffee:


Generic Multicast 0 TLA specification

This spec verify the first generic multicast algorithm, that works in a
failure free environment. This is just a toy algorithm and we started
from here, so we can later just increase the needed steps from one
algorithm to another.
Just in this specification we already had some interesting results, that
could cause the protocol to no satisfy some properties. The first one is
on step assignSeqNumber, if the decided timestamp is greater than the
process local clock, we leap to the decided value. This could lead to
some inconsistency, when messages contains the same timestamp they are
sorted by the unique identifier, but if messages are too delayed and
they are supposed to delay with the message already delivered, both
messages will contain the same final timestamp but could be delivered
out of order. To solve this problem we also verify if the process clock
needs to be incremented on this step, if there is a message that
conflict with the current message, the clock will leap and increase, if
there is no conflicting message, the clock only leap.
Another change is on the doDeliver step. The definition presented on
the pseudo-code has some details that can lead to delivering messages
out of order. If there two messages with both timestamps, the unique
identifier will be used to break the tie, but if the message with the
smallest identifier is not on the Delivering set, the message with
higher identifier will be delivered first. When explaining how the
deliver method will work, the identifier is not used to break ties. To
solve this problem, instead of using a different function to verify the
messages ready to deliver, we use only a single expression that is able
to verify if the message is the smallest amongst all sets, already
verifying both timestamp, conflict relation and the unique identifier.
When ready to delivered, the commuting messages are also added to the
set to be delivered, so the generic property remains working.
In the step computeSeqNumber, the received messages and timestamps are
implicitly stored somewhere, so the coordinator can decide later which
is the highest received timestamp. The pseudo-code abstract this, but
when writing the specification a structure called Votes is added, this
does not change the protocol itself, the only difference is that now is
explicit the need to keep track of the received timestamps before
deciding the final timestamp.
The last change was adding one more property to the protocol. Using only
the Partial Order we want that the protocol sort messages in a certain
way, but we never tell the algorithm that it should sort messages.
With only the Partial Order definition, messages delivered at the same
instant are accepted, but we know that if messages conflict they should
be delivered in different instant. To avoid this situation, another
property is added to tell the protocol it must sort conflicting
messages.
This property is called Collision (perhaps is an overloaded term?). If
a process p deliver both messages m and n, if m and n are
different, p is both in m.d and n.d and m conflicts with n,
then p delivered m in a different instant than when p delivered
n. Using this property, now the protocol knows that messages that
conflict are supposed to be sorted.
Those are the major findings when validating the protocol with TLA+.
With this result we are able to see that only reasoning about a protocol
and possible states is something really hard, since so many edge cases
can be created. Specially the need for another property, when only
reading the properties, that conflicting messages can be delivered
after another by a process if, and only if other process also delivered
the message after. Only reading this statement is not easy to see that
the protocol need one more property to secure the ordering of messages.

Since not everything is happiness, there are some tradeoffs in this
specification. The most notable is the network abstraction, the protocol
definition is a genuine protocol, thus only processes involved in the
destination and source need to process the message so the protocol can
proceed. In the specification we are using all processes when exchaning
messages between processes, in this approach the number of generated
stated will be smaller. To strictly specify the protocol, when
exchanging messages only the processes on the destination of the message
is needed, but since TLC will verify every state, if we used a SUBSET of
the available Processes all valid subsets will be verified, leading to a
huge number of states. When reasoning about, using all Processes or
using only a subset should not affect the protocol behaviour nor fail
when verifying the properties, but then again, the problems we found
were only found because we verified with TLC and when only reasoning
about the protocol, it did not seem to have any problems.

Updated the spec, now we support to handle only a subset of processes. But since always something happen, there is a peculiarity about the destination. All messages that will be exchanged in the protocol are created in the beginning, using:
ChooseSubset == CHOOSE x \in SUBSET Processes: Cardinality(x) > 0
ToSend == { [ id |-> id, d |-> {2}, ts |-> 0, s |-> ChooseProcess ] : id \in Messages }

Using this approach, all possible states are verified? Since this structure is defined at start and never changes. Manually defining the destination for the combinations {1}, {2} and {1, 2}, the protocol works as expected, but when using the SUBSET the execution time is too fast to be verifying all possible states.
Also, unfortunately I did not found a way to express the message exchange for subset without using the IF/ELSE, specially in the AssignTimestamp step, where the protocol removes the message from itself and sends a message to the coordinator. At the moment the specification is doing this, but is too verbose (weird).


Missing dependency on XlsxWriter

Works great for me! And the template functions very well in LibreOffice Calc (7.4) too. The only difference from Excel is that invalid value alerts do not show the constraint possibilities.
Please add XlsxWriter to your README or dependencies:
pip install xlsxwriter
(And of course, in the future it would be nice to also support OpenDocument e.g. via odfpy)

Thanks @loleg, it is configured as an extra since I plan to also bring in Google Sheets support from existing code. I've updated the installation instructions accordingly:
pip install "tablecloth[excel] @ git+https://github.com/ezwelty/tablecloth"

Thanks, good tip!


Better keymap config

I will be adding "mapping" key that introduces a new style of config for keymaps, similar to how it's done in nvim-cmp.
Rather than having the actions as keys and key sequence as value, we will have the other way around. this makes it easier to disable keymaps as well as letting user customize keymaps to use their own functions
The existing keymap will be supported due to the major breaking change if it were otherwise. the config module will handle converting keymaps table to new mappings table, if the user provided them
mappings = {
  ["<tab>"] = "fold toggle"
}

Not sure on the specifics of what should be used on the RHS. Maybe if rhs is a string, it is considered a default action. rhs could also be a function.

I hope this will add the ability to use nowait = true on my spacebar, which I cannot bind now, because it's the prefix key for many things.

Hi @Ajaymamtora, it says on in the docs that you can set to {} to disable. Please do try again, and open a separate issue if it still doesn't work.
https://github.com/hedyhli/outline.nvim?tab=readme-ov-file#default-options


add scroll search

Hi, I added scroll search api to this client.
Paginate search results | Elasticsearch Reference [7.9] | Elastic
https://www.elastic.co/guide/en/elasticsearch/reference/current/paginate-search-results.html#scroll-search-results
Scroll API | Elasticsearch Reference [7.9] | Elastic
https://www.elastic.co/guide/en/elasticsearch/reference/current/scroll-api.html
Clear scroll API | Elasticsearch Reference [7.9] | Elastic
https://www.elastic.co/guide/en/elasticsearch/reference/current/clear-scroll-api.html
Here is the example code. This code print all document id by scroll search api.
import 'package:elastic_client/console_http_transport.dart' as elastic;
import 'package:elastic_client/elastic_client.dart' as elastic;

Future<void> main() async {
  final transport =
      elastic.ConsoleHttpTransport(Uri.parse('http://localhost:9201'));
  final elasticClient = elastic.Client(transport);

  final index = 'test_index';
  final scroll = Duration(minutes: 3);
  final searchResult = await elasticClient.search(
    index,
    '_doc',
    elastic.Query.matchAll(),
    scroll: scroll,
  );
  for (final i in searchResult.hits) {
    print(i.id);
  }
  while (true) {
    final scrollResult =
        await elasticClient.scroll(searchResult.scrollId, scroll);
    for (final i in scrollResult.hits) {
      print(i.id);
    }
    if (scrollResult.hits.isEmpty) {
      final clearScrollResult =
          await elasticClient.clearScroll([scrollResult.scrollId]);
      print(clearScrollResult.toMap());
      break;
    }
  }
  await transport.close();
}

Published as 0.1.14. Thanks!

I'm glad it was merged. Thank you for your review.


concat with the same video multiple time

Hi
I'd like to build videos with transitions.
Like :
Intro - Clip1 - Transition - Clip2 - Transition - Clip3 - Outro
The transition video is always the same one.
But when I put twice the same video in ffmpeg.concat(), the generated ffmpeg command hangs, it doesn't work.
This code :
infiles = []

ffmpeg_transition_clip = ffmpeg.input('/tmp/resized_transition.mp4')
transition_v = ffmpeg_transition_clip['v']
transition_a = ffmpeg_transition_clip['a']
infiles.append(transition_v)
infiles.append(transition_a)
infiles.append(transition_v)
infiles.append(transition_a)

concatened = ffmpeg.concat(*infiles, n=len(infiles)/2, v=1, a=1).node
v = concatened[0]
a = concatened[1]
output = ffmpeg.output(v, f'output/test.mp4', threads=4).overwrite_output()

Generates this command :
ffmpeg -i /tmp/resized_transition.mp4 -filter_complex [0:v][0:a][0:v][0:a]concat=a=1:n=2:v=1[s0] -map [s0] -threads 4 output/test.mp4 -y
Which hangs as well.
Changing it to this :
ffmpeg -i /tmp/resized_transition.mp4 -i /tmp/resized_transition.mp4 -filter_complex [0:v][0:a][1:v][1:a]concat=a=1:n=2:v=1[s0] -map [s0] -threads 4 output/test.mp4 -y
It works.
How can I do that using ffmpeg-python ?
Thank you !

Hey, old issue but I faced the same problem. By analyzing the sources, I found that ffmpeg-python is hashing the filename string to create the stream. So I was able to find a workaround: you simply just have to put a different filename each time you call ffmpeg.input.
Example: Let say you have 4 videos that you want to concat with a transition video. This won't work because it will just create twice the same transition stream (will only input transition.mp4 once).
# Won't work
import ffmpeg
videos = [
    '/path/to/v1.mp4',
    '/path/to/transition.mp4',
    '/path/to/v2.mp4',
    '/path/to/transition.mp4',
    '/path/to/v4.mp4',
    '/path/to/transition.mp4',
    '/path/to/v3.mp4'
]

for video in videos:
    ffmpeg.input(video)

[...]

The workaround use the fact that // translate to / in a path: /path/to//transition.mp4 = /path/to/transition.mp4. Thus, you can simply add a / the filepath of the transition video. You can use as many as you want. You can also use /./.
# Will Work
import ffmpeg
videos = [
    '/path/to/v1.mp4',
    '/path/to/transition.mp4',
    '/path/to/v2.mp4',
    '/path/to//transition.mp4',
    '/path/to/v4.mp4',
    '/path/to///transition.mp4',
    '/path/to/v3.mp4'
]

for video in videos:
    ffmpeg.input(video)

[...]

@Guisch I'm late to the party but thank you so much for figuring this out!
I spent 30mn debugging my code without knowing what to do.


Fix Remove Collection Number

Removing a Collection Number from an Observation currently throws an error. (And one user has complained.)
Started GET "/collection_numbers/11072/remove_observation?observation_id=512701&q=1oAhh" for <IP_ADDRESS> at 2023-01-11 23:55:58 +0000
ActionController::RoutingError (No route matches [GET] "/collection_numbers/11072/remove_observation")

This PR:

Adds a test that provokes the bug;
Fixes the bug by replacing the Collection Numbers Remove link with a PATCH button.
Delivers Pivotal #184210741

Manual Test

Create an Observation, checking the Specimen Available box, and adding a Collector's Number
Remove the Collection Number

@nimmolo Thanks for the review.
I am re-running the tests because the Check display is weird:

codeclimate/diff-coverage Pending — Waiting for coverage results to be reported
codeclimate/total-coverage Pending — Waiting for coverage results to be reported
codeclimate — All good!
I will merge and deploy this as soon as that's fixed.

@JoeCohen - Forgot to say yesterday, I'm out of town visiting my aunt this weekend... i'll have a phone but no computer until Monday.
The diff-coverage and total-coverage are new, right? I feel like they were still "pending" when i reviewed last night, but not sure.

Thanks for the response.
I think you're right that the pending lines were there when you reviewed it.
Don't worry about the issue; I'll take care of it. Worst case is that I
just ignore it.
Have a great visit with your aunt.
On Thu, Jan 12, 2023 at 8:19 AM andrew nimmo @.***>
wrote:

@JoeCohen https://github.com/JoeCohen - Forgot to say yesterday, I'm
out of town visiting my aunt this weekend... i'll have a phone but no
computer until Monday.
The diff-coverage and total-coverage are new, right? I feel like they were
still "pending" when i reviewed last night, but not sure.
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1280#issuecomment-1380662036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALDFC6WD6UCVH2JQ4R3P3WSAVKXANCNFSM6AAAAAATYZIS34
.
You are receiving this because you were mentioned.Message ID:
@.***>

Coverage: 92.721%. Remained the same when pulling 57c714e6fbf79900d44959ba4f606c36479af994 on jdc-remove-collection-number into de552896b4afff58a3f337093c7538632376282d on master.


Add white space in the Nav

I think having a white space between the "About DEI Badging"  in the Navigation

I want to work on this issue. @Anita-ihuman


bug: debugger does not start

Did you check docs and existing issues?

[X] I have read the documentation.
[X] I have searched the existing issues.

Neovim version (nvim -v)
0.10.0
Operating system/version
macOS 14.5
Describe the bug
neotest-golang runs a single test, but cannot start debugger for the same test.
Note: neotest-go starts the debugger (though it runs for all tests in the module 😢 ), but neotest-golang fails with an error:
neotest-golang: ...vchenko/.local/share/nvim/lazy/nvim-nio/lua/nio/init.lua:119: The coroutine failed with this message:
...nvim/lazy/neotest/lua/neotest/client/strategies/init.lua:57: attempt to index local 'instance' (a nil value)
stack traceback:
	...nvim/lazy/neotest/lua/neotest/client/strategies/init.lua: in function 'run'
	...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:130: in function '_run_spec'
	...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:89: in function <...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:88>
stack traceback:
	...ocal/share/nvim/lazy/neotest/lua/neotest/client/init.lua:89: in function <...ocal/share/nvim/lazy/neotest/lua/neotest/client/init.lua:88>
	[C]: in function 'error'
	...vchenko/.local/share/nvim/lazy/nvim-nio/lua/nio/init.lua:119: in function 'gather'
	...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:94: in function '_run_tree'
	...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:65: in function <...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:22>
	[C]: in function 'xpcall'
	...ocal/share/nvim/lazy/neotest/lua/neotest/client/init.lua:84: in function 'run_tree'
	...al/share/nvim/lazy/neotest/lua/neotest/consumers/run.lua:85: in function 'func'
	...chenko/.local/share/nvim/lazy/nvim-nio/lua/nio/tasks.lua:173: in function <...chenko/.local/share/nvim/lazy/nvim-nio/lua/nio/tasks.lua:172>

Steps To Reproduce

Start a debugger for a test case
An error occurs

Expected Behavior
Should run the debugger
Your Lua setup
Using LazyVim I configure:

return {
  "nvim-neotest/neotest",
  opts = {
    adapters = {
      -- "neotest-go",
      "neotest-golang",
    },
  },
  dependencies = {
    {
      -- {
      --   "nvim-neotest/neotest-go",
      --   extra_args = { "-vet=off" }
      -- },
      {
        "fredrikaverpil/neotest-golang",
        args = { "-vet=off" }
      },
    },
  },
}

Please provide a minimal reproducible Go test example.

Check out https://github.com/golang-jwt/jwt , run go build ./... to make sure it builds, then run neovim in the dir and execute a debug test.

I cloned down the repo, found a test at random and tried to both run it and then debug it. Works on my machine 😄

It feels like this could be a configuration issue on your end...?
Since LazyVim is already using neotest-golang, I could quite easily try it out here too, and it works for me:

Could it be that you haven't enabled debugging in your neotest-golang config with dap_go_enabled = true?


Cosmetic/UX improvements on the PyQt viewer for centerline manual labeling

After #3175, the following (minor) improvements are suggested:

Fix text overlapping on the image: this sometimes happen depending on the resizing of the figure or the zoom on the image.
Increase the font of the message on top (easy to miss!).
Red arrow (fig below): remove the white area corresponding to the layout (e.g. make they the same color as the window: grey)
Blue arrow (fig below): add an editable text field so users can modify the interval for the AUTO mode.

 Large figure hidden, click to show

EDIT by @joshuacwnewton: I wrote https://github.com/neuropoly/spinalcordtoolbox/pull/3175#pullrequestreview-570084154 which suggested a number of code style improvements. @jcohenadad has suggested to save these changes for this issue #3178, to allow v5.1.0 to be released more quickly. In summary:

Small cosmetic bug where "# of points selected" doesn't refresh when Ctrl+D shortcut is used.
Allow self.START_SLICE to be set directly using an int, rather than string-int key-value pairs.
Clean up outdated param.starting_slice code.
Make CMD_KEY a global constant for the GUI module.
Address this: # TODO: try the setShortcut attribute
Clean up recursive function call for on_toggle_mode.

Fix text overlapping on the image: this sometimes happen depending on the resizing of the figure or the zoom on the image.

To show an example of this:

Fix text overlapping on the image: this sometimes happen depending on the resizing of the figure or the zoom on the image.

To show an example of this:

thank you for identifying these additional improvements @joshuacwnewton 🙏

thank you for identifying these additional improvements @joshuacwnewton 🙏