URL Suggestion List Stays and Covers Up Screen Even After Focus Out

Expected Behavior
URL suggestion list seems to come up when one focuses on the url field (probably along with hitting send?). Then, it should disappear once we click elsewhere, but it stays stuck.
Actual Behavior
URL suggestion list seems to come up when one focuses on the url field (probably along with hitting send?) It should disappear once we click elsewhere, but it stays stuck. (See the list with the 'c' icons)

Reproduction Steps
Not fully sure...

Should have a 4-5 requests in collections (I have hundreds BTW).
Open a request, focus on the URL field, change something. Hit send.
Open another request and focus on the URL field. Hit send.
Repeat 2-3. At some point this issue will probably turn up.

Then the only way to remove the list is to select a suggestion (which will be unnecessary from actual usage perspective; hence you'd need to go to the URL field and clean it up)
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
Version: Insomnia 2021.7.2
Release date: 12/10/2021
OS: Windows_NT x64 10.0.18363
Electron: 11.2.3
Node: 12.18.3
V8: <IP_ADDRESS>-electron.0
Architecture: x64
node-libcurl: libcurl/7.73.0-DEV OpenSSL/1.1.1g zlib/1.2.11 brotli/1.0.9 WinIDN libssh2/1.9.0_DEV nghttp2/1.41.0
Insomnia Version
2021.7.2
What operating system are you using?
Windows
Operating System Version
Windows 10 v1909 (Windows_NT x64 10.0.18363)
Installation method
Downloaded frim insomnia.rest
Last Known Working Insomnia version
Not sure

I think this issue is already being tracked here: https://github.com/Kong/insomnia/issues/4531

The issue reproduces multiple times daily. Sometimes it goes away with a click, here or there, other times relaunching Insomnia is required.
Version: Insomnia 2022.4.2
Build date: 6/22/2022
OS: Darwin x64 21.6.0
Electron: 18.1.0
Node: 16.13.2
V8: <IP_ADDRESS>-electron.0
Architecture: x64

Configured are ~27 environments, each with a configuration looking something like:
{
  "endpoint": "https://...",
  "username": "user...",
  "password": "pass...",
  "api_key": {
    "id": "some_id",
    "name": "api_key_name",
    "expiration":<PHONE_NUMBER>828,
    "api_key": "ek..snipped..GcA",
    "authorization": "ApiKey dTlV..snippped...Q=="
  }
}

I would ❤ to see this fixed and would be happy to provide any info needed that might help.

Any possibility this bug could be verified?

Hi folks, this should have been fixed recently, please let us know if you can still reproduce this in tomorrow's beta.4 release.


Adding Quick sort

Quicksort is a sorting algorithm based on the divide and conquer approach where

An array is divided into subarrays by selecting a pivot element (element selected from the array).

While dividing the array, the pivot element should be positioned in such a way that elements less than pivot are kept on the left side and elements greater than pivot are on the right side of the pivot.

The left and right subarrays are also divided using the same approach. This process continues until each subarray contains a single element.
At this point, elements are already sorted. Finally, elements are combined to form a sorted array.

I want to add code for Quicksort in C++ for hacktoberfest 2022. Please assign this issue to me.

Hi please assign this issue to me. I want to contribute to hacktoberfest 2022

Hi there 👋
I'm excited to contribute to Hacktoberfest 2023, and I'd like to work on this issue. It looks like a great opportunity to learn and contribute to the project.
Please assign this issue to me, and I'll start working on it right away. If you have any specific instructions or guidelines, please let me know, and I'll make sure to follow them.
Thanks a lot for considering my request!
Best regards,
Prateek Sethi

hello sir this is my first hactoberfest and started my journey as a open source contributor can u pls assign this issue it will boost my spirit for open source thankyou

I wish to contribute. Kindly assign this to me.

Please assign this issue to me.


Refactor Kueue module

Issue link

Closes: RHOAIENG-13331

[x] #695

What changes have been made

Refactored the Kueue module to fit the design doc
Verification steps

E2E and Unit tests should be sufficient
Checks

[x] I've made sure the tests are passing.
Testing Strategy

[x] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

/lgtm


I try to use sweebee/filament-char-counter in my app and no effect ?

I added sweebee/filament-char-counter ^1.1.1 to my  filamenphp 2.17.17 app and adding HasCharacterLimit trait
I created custom CustomTextInput class :
    use App\Filament\Custom\CustomTextInput;
    //use Filament\Forms\Components\TextInput;
    use App\Models\BannerCategory;

    use Filament\Tables\Columns\TextColumn;
    ...
    class BannerCategoryResource extends Resource
    {
        ...
        public static function form(Form $form): Form
        {
            return $form
                ->schema([
                    Forms\Components\Group::make()
                        ->schema([
                            Forms\Components\Card::make()
                                ->schema([
                                    CustomTextInput::make('name')
                                        ->reactive()
                                        ->required()
                                        ->minLength(2)
                                        ->maxLength(255)
                                        ->characterLimit(255)
                                        ->unique(table: BannerCategory::class)
                                        ->afterStateUpdated(function (Closure $set, $state) {
                                            $set('slug', Str::slug($state));
                                        })->autofocus()
                                        ->unique(ignoreRecord: true)
                                        ->placeholder('Enter name of banner category'),
                                    CustomTextInput::make('slug')
                                        ->maxLength(255)
                                        ->characterLimit(255),

But no any char counters are visible. I found file vendor/wiebenieuwenhuis/filament-char-counter/src/FilamentCharCounterProvider.php with content :
<?php

    namespace Wiebenieuwenhuis\FilamentCharCounter;

    use Filament\PluginServiceProvider;
    use Spatie\LaravelPackageTools\Package;

    class FilamentCharCounterProvider extends PluginServiceProvider
    {
        protected array $styles = [
            'filament-char-counter' =>
                __DIR__ . '/../resources/dist/css/char-counter.css',
        ];

        public function configurePackage(Package $package): void
        {
            $package
                ->hasAssets()
                ->name('filament-char-counter')
                ->hasViews();
        }
    }

Opening file vendor/wiebenieuwenhuis/filament-char-counter/resources/dist/css/char-counter.css I see a lot of css code - looks like it must implement
char counters functionality but how to  assign it to the project?
In file config/app.php I added :
    'providers' => [

        /*
         * Laravel Framework Service Providers...
         */
         ...
        Wiebenieuwenhuis\FilamentCharCounter\FilamentCharCounterProvider::class,

and cleared cache.
Also I have
   npm run dev
command running...
But still no char counters functionality visible : https://prnt.sc/WlIvJe17fuGN
What I see in browser : prnt.sc/nrIx9blrWlLy not sure looks like this php
code is not loaded and css is not applied. Does filament/laravel packages has
some common way of loading package styles ?

Same here

You’re not using the textinput from this package, you should import it from this package not from filament itself.

Thank you ! After I upgrated wiebenieuwenhuis/filament-char-counterm to ^1.1.3 it works. Can you please make similar functionality for Filament\Forms\Components\RichEditor class ?


Create 0x3D0AfE41c7806159Ac52E370C0Db2361826cc1f7

Duplicate, but this one is more correct than your previous. still requires fixing
(Folder name needs to be named with the token address)
-Please name it logo.png

closing due to no fix


Fix container for PHP 8 union types

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues
#18624

👍


Document integrations with various CI environments

Covering how to integrate QUnit with various CI environments:

Jenkins, Travis, CircleCI
BrowserStack, Sauce Labs, testling
TestSwarm
PhantomJS
testem, testacular
Karma
Grunt
Gulp

But also other environments:

[ ] getting files with bower or npm (#40)
[ ] using directly or with AMD (#50)

Perhaps also a minimal example running via Headless Chromium (possibly via Puppeteer).

Grunt / Headless Chrome:
https://github.com/gruntjs/grunt-contrib-qunit/issues/171

DevExpress: https://github.com/DevExpress/testcafe

https://github.com/qunitjs/qunitjs.com/commit/30f316fdf0c57722b8393de70ae094ca639e015e


fix(strategySheet): 隐藏列兼容趋势分析表衍生指标场景

👀 PR includes

🐛 Bugfix

[x] Solve the issue and close #0

📝 Description
由于趋势分析表列头是魔改的一个单元格显示多组数据, 隐藏列头也需要兼容这种场景, 不然会错误的隐藏所有列, 新增 EXTRA_COLUMN_FIELD 字段

🖼 Screenshot

Before
After

🔗 Related issue link

🔍 Self Check before Merge

[ ] Add or update relevant Docs.
[ ] Add or update relevant Demos.
[ ] Add or update relevant TypeScript definitions.

:tada: This PR is included in version @antv/s2-v1.16.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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


Add zip_safe flag to setup.py

Why is this relevant for SoundFile? It seems to me that a single source file would not benefit from being zipped.

Having only one source file doesn't make it any less zip_safe.
Also, this is what happens by default if no package_data is specified and if __file__ and stuff are not used in the code.
I didn't make any performance tests, but I still think it's the natural thing to do.

Could you explain to me why it is zip-safe if it only contains source code, but zip-unsafe if it contains binaries?

Sure.
It is definitely zip-safe if the only access to any (potentially zipped) files happens via import statements.
That's the situation when we don't have any _soundfile_data.
It's hard to find reliable information about if it is theoretically zip-unsafe in the other case. But that would (in our case) be the default anyway, so I'm not changing anything here. I'm just enabling the zip-safe mode in the first case.
See http://setuptools.readthedocs.io/en/latest/setuptools.html#setting-the-zip-safe-flag.
The easiest way to actually find out if it is zip-unsafe is to just try it, which I did. It produces this error:
OSError: cannot load library /Users/me/myvenv/lib/python3.6/site-packages/SoundFile-0.8.1-py3.6.egg/_soundfile_data/libsndfile.dylib: dlopen(/Users/me/myvenv/lib/python3.6/site-packages/SoundFile-0.8.1-py3.6.egg/_soundfile_data/libsndfile.dylib, 2): no suitable image found.  Did find:
	/Users/me/myvenv/lib/python3.6/site-packages/SoundFile-0.8.1-py3.6.egg/_soundfile_data/libsndfile.dylib: stat() failed with errno=20

An errno of 20 means "Not a directory", which totally makes sense, since a zip file is not a directory.
I guess it would be possible to make it zip-safe anyway by using pkg_resources, but I don't like the idea of adding another runtime dependency.

Thank you for the elaboration.

No problem, thanks for merging!


Readme: Add info about split up cache steps

I think the basic explanation of how actions/cache works, is not needed here.
The split up step is super helpful when any error during link checking occurs and the cache would not be saved at all because of the failing job.

Good idea. I'll add it the website as well. Thanks!

Done. See here.

Looking good 👍


Added unit tests for AdminX API hooks

refs https://github.com/TryGhost/Product/issues/3831

🤖 Generated by Copilot at b39e813
This pull request refactors the createMutation and mutate hooks in the admin-x-settings app to simplify the mutation options and fetch logic. It also adds the @testing-library/react dependency and unit tests for the custom hooks and the query cache update functions. The goal of these changes is to improve the code quality and test coverage of the app.

Can't figure out the specs here, will try again when we separate this package (smaller surface area to debug then)


Change from trailing edge to leading edge

starting numb-counter from leading edge, not trailing edge.

Solved in boggyver commit.


Add Pharo 11 to the build matrix

Codecov Report

Merging #10 (42eeb9e) into master (e2fb73f) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   89.41%   89.41%
=======================================
  Files           4        4
  Lines         510      510
=======================================
  Hits          456      456
  Misses         54       54

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thank you for adding this in


updateCache is not working about datasets in several locations

I'm using your LSP server with nvim-lsp environment (see my article written in japanese).
I'm trying to use bq/updateCache with my BigQuery projects, but sometime it's not work.
I think it is caused by location of the dataset, because there are no problem with datasets located US.
A query about INFORMATION_SCHEMA.SCHEMATA might respond only about location where the job runs.
Instead of the query, for example, we can use bq command with following parameters.
bq ls -d --project_id=<project_id> --format=json

Thanks, for great product.

Thank you for your bug report.
週末にでもゆっくり確認させていただきますね。

Instead of the query, for example, we can use bq command with following parameters.

That's a good idea.
I have just published new version (0.0.17).
If it does not work fine, please feel free to reopen the issue.

Thank you for the response.
As you can imagine, I have some datasets in US and asia-northeast1.
And it (0.0.17) is works great in my environment.
早々のご対応ありがとうございました。しかも、cache のスキーマ変更まで。
上手く動作しており、ますますクエリがはかどりそうです。


Remove Emoticomix

… because it was not working any more for long.  Edit: See also issue #124.

Superseded by PR #131.


Set node count can throw AttributeError

http://jenkins.cgcloud.info/job/toil-pull-request-integration-tests/987/testReport/junit/src.toil.test.provisioners.aws.awsProvisionerTest/AWSAutoscaleTest/testSpotAutoScale/

That doesn't mean it isn't still a bug.
Cricket Alicia Sloan<EMAIL_ADDRESS>writes:

this ticket is 1 year stale
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.*

Agreed that it could still be a bug.  But given that large chunks of the code are rewritten, it would need to be reproduced. Do you have evidence that it still exists?

I don't necessary disagree with closing, only the justification
that it is a year stale from someone who is gone.
I don't know if the related code has been modified or not.
Suggest just ask Lon if he suspects the code has been change and
the problem would have been fixed.
Given there is no test case with the bug, `appears to be no
longer a problem' is great by me!  If it is a bug, it will come
back.
Cricket Alicia Sloan<EMAIL_ADDRESS>writes:

Agreed that it could still be a bug. But given that large chunks of the code
are rewritten, it would need to be reproduced. Do you have evidence that it
still exists?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.*


action.error cannot be set when Error object returned in payloadCreator

The behaviour has been changed by below commit
https://github.com/acdlite/redux-actions/commit/b9d5eb7daec5e29cb02c34dfb855c51183051f71
But we do depend on the original behaviour so that some basic validation can be done in our payloadCreator and set "error" for invalid cases.
Should we revert above commit back?

Can you do the validation outside the payload creator, passing in an Error object only when validation fails?
Also, would https://github.com/acdlite/redux-actions/pull/136 fix this for you?

Yes, I believe #136 should fix the issue since it will check the return value of payloadCreator.
I put basic validation in my action creator since I don't write another wrapper.


Feature: Resource tracking global view

The resource tracking feature is in progress.
We have so far:

CRUD on resource group
CRUD on resource pool

We need to add a view that give a visual map of resource group with link on attributes of a resource pool.
The idea is to generate a page with graphviz.
Example of code with dot language (can be tested in the online editor here)
digraph {
  node [shape=plaintext]
    rg1 [label=
    <

          Resource Group

          Name
          Server

          Resource
          34

          Attributes

        Name
        Total

        vCPU
        60

        Memory
        34

    >
    ];

  node [shape=plaintext]
    rp1 [label=
    <

          Resource Pool

          Name
          vCenter

          Attributes

        name
        Produced
        Consumed
        Available

        vCPU
        40
        30
        10

        Memory
        100
        20
        80

    >
    ];

    rg2 [label=
    <

          Resource Group

          Name
          VM

          Resource
          34

          Attributes

        Name
        Total

        vCPU
        60

        Memory
        34

    >
    ];

    node [shape=plaintext]
    rg3 [label=
    <

          Resource Group

          Name
          Resources
          vCPU
          Memory

        vCenter
        23
        30
        45

    >
    ];

    rg1:rg1_vCPU -> rp1:rp1_vCPU [color = green]
    rg1:rg1_memory -> rp1:rp1_memory [color = green]

   rp1:rp1_vCPU  -> rg2:rg2_vCPU [color = red]
   rp1:rp1_memory -> rg2:rg2_memory [color = red]

}

Here is the result:

Todo:

[ ] New link from the sidebar that point to this new page
[ ] Method that generate the view from current data in the DB
[ ] Color on attribute links (red when consumer, green when producer)
[ ] On resource group: Link on the number of resource that point to resource_group_resource_list view
[ ] On resource pool: Link on producer that point to resource_pool_attribute_producer_list
[ ] On resource pool: Link on consumer that point to resource_pool_attribute_consumer_list
[ ] Add background color on TD element with same color as our bootstrap framework

New minimalist version POC

Done and merged in dev


[FEATURE] Top N Queries API should be able to get historical data from index

Is your feature request related to a problem?
Currently we can export historical top n queries data into local index, and to view the historical data we have to manually search the index. It would be convenient if we can provide the functionality to specify time ranges in the top n queries API, and the API handles the logic to search in local index.
What alternatives have you considered?
We keep the current logic, but it would not be convenient for the user and also make the dashboard logic complex when getting historical top n queries.
Do you have any additional context?
Add any other context or screenshots about the feature request here.

[Catch All Triage - 1, 2, 3, 4]


Allocating drivers and vehicles in ODS

In reviewing the ODS spec, it appears that there is an absence of guidance regarding the allocation of blocks to operational vehicles, as well as the assignment of duties to drivers with their matching operated dates
As this crucial information is expected to be sourced from the dispatching software, can you provide clarification or additional details on how the ODS spec addresses the extraction of data related to block allocation, driver duties, and associated dates from the dispatching software for communication to the AVL provider?
Thanks

Matching operators to their duties on each day is something that I would use, and if it's not in ODS, I'd have to represent the data in a non-standard adjacent data feed. I'm currently using a CSV with 3 columns for this purpose: date, run_id, operator.
But it's also kind of separate from the schedules ODS does represent. For example, assigning operators to runs is done well after the rest of the schedule is finalized.
I think I remember this coming up in discussions a while ago and I think it was just cut for scope. It'd be easy to add as a backwards-compatible extension once the rest of the format is finalized.

Thanks for your answer @skyqrose. The concept I aim for is pretty much the same - having a new file assignments.txt file that includes also the assignment per drivers and vehicles
block_id,vehicle_id,run_id,driver_id,operational_date

I think I remember this coming up in discussions a while ago and I think it was just cut for scope. It'd be easy to add as a backwards-compatible extension once the rest of the format is finalized.

Yes, this was discussed and cut for scope and also because there seemed to be less consensus on the topic of representing driver/staff-identifying information, at least at that time. I remain in favor of bringing this information into ODS, however.

For example, assigning operators to runs is done well after the rest of the schedule is finalized.

Can we be clear about what the intended use case is here? I want to make sure I understand who is producing these assignments and who the consumer will be. If the run assignments are done via the same producer after the schedule is finalized but before it would be sent to the schedule consumer, that wouldn't seem like it would impact our decision to include those assignments in the ODS-represented schedule. But I want to be sure that's an accurate read of what you both have said.

At MBTA, the use case is to export data from HASTUS and distribute it to multiple internal apps using a standard format, instead of the status quo of each app getting a custom export in a custom format. (This data would probably also make it outside of MBTA to Swiftly, but that's not my side of the house so I'm not sure.)
So far, exporting the trip schedules and exporting the operators' schedules have been completely separate processes, and exporting operators' schedules for each season typically happens a couple weeks after the trips.
If we didn't have this proposal, we would keep doing the separate operator export alongside ODS.
If we did, then I think we would publish an internal ODS feed without operator schedules as soon as the trips are scheduled, and then re-publish an updated ODS feed with operator schedules once those become available.
Does that answer the question?

Depending on how the issues with non-unique run_ids go (see #12), it's possible that the drivers file would need to have a 4th column for the service_id. If runs are unique among all the services effective on a date (but not unique among all services), it wouldn't be necessary, but could still make looking up the run easier.
MBTA hasn't run into this specific uniqueness problem yet with our current use cases, but I expect we would if this file was standardized and we used it in more places.
I'm not sure if our block_ids are unique, but I guess the same problem could happen in principle to the vehicles file.

Can we be clear about what the intended use case is here? I want to make sure I understand who is producing these assignments and who the consumer will be. If the run assignments are done via the same producer after the schedule is finalized but before it would be sent to the schedule consumer, that wouldn't seem like it would impact our decision to include those assignments in the ODS-represented schedule. But I want to be sure that's an accurate read of what you both have said.

Adding on top of @skyqrose's answer. The dispatching software and the AVL vendor might be different. This creates a scenario where we are unable to communicate through the same format and are required to build per each vendor's specifications, which sometimes isn't possible. From the customer's end, if they're using two different systems in place, they are required to manually do the allocations in both the dispatching and the AVL software, which can be inefficient. If we don't include the actual assignments in the ODS format, we would be able to convey information about the runs/blocks but not the dispatching portion. Extending ODS for including assignments, creates a clear path for clear communication between two different software providers

Question re: proposed driver_assignment.txt file
Would it be reasonable to say this same use applies to personnel more broadly (that is to say, not just to drivers/vehicle operators)? Does the job performed need to be identified in the new field? Or will it (always) be self-evident from the operator id what job they are performing?
Trying to get at whether we need to make our language more job-agnostic and how we can either support other roles or at least bake in some extensibility for that support in future

As proposed, would we be imposing a limitation that a driver's run assignment would always be for the full run. Is that desirable? Would it make sense to include the piece information in the file as well?

Some questions on proposed vehicle_assignment.txt:

are there different types of assignment we need to account for?
how do we account for the same vehicle being assigned to multiple blocks on a given date? or the same block assigned to multiple vehicles?
is there a case where a block might be assigned no vehicle within the schedule, and instead only assigned on the day of operations?
do we need a master list of vehicles that vehicle_id can pull from? [we also have #30, which currently doesn't have a vehicle_id field but should.]

one more q for driver_assignment.txt

would it make sense for this assignment to be made between an operator and a bid instead to individual runs? with the bid representing a package of runs/pieces during a specific window of time?

I think that this file could apply to other jobs, if they have run ids, which seems very possible.
You can't determine job based on operator id, since some employees might do different jobs on different days. But you can determine the job based on run id. And if you want a run_id to job_id mapping, then that'd be better to do in runs.txt than in driver_assignment.txt. So I don't think it should go here, but we should consider it there.

Yes, this would limit assignments to a full run. I think by the definition of a run, that's okay. If you plan to assign multiple operators to different pieces of the same run, then those are really two separate runs.
If you don't plan to assign multiple operators, but end up having to because you're filling absences or if an operator has a half-day conflict or something, then that's not necessarily going to align to piece boundaries, and it'd require a way to specify assignments per trip, which is way more detail than ODS should have and is a step away from schedule data towards realtime data so is out of scope anyway.

(no comment on vehicles)
I don't think we should associate operators to bids instead of runs+dates. If we did, we'd need a separate way to map bids to runs to runs+dates, and every lookup would have to go through that level of indirection. It'd also make it impossible to reassign people on individual days, for example if vacation dates are chosen after bidding. The important operational detail we want to capture is which employees are working, and the bidding process is just an administrative detail to get there that doesn't matter if we have the end result.

Would it be reasonable to say this same use applies to personnel more broadly (that is to say, not just to drivers/vehicle operators)? Does the job performed need to be identified in the new field? Or will it (always) be self-evident from the operator id what job they are performing?
Trying to get at whether we need to make our language more job-agnostic and how we can either support other roles or at least bake in some extensibility for that support in future

It could be extended, but what is the use case for associating another personnel that is not performing a run?

As proposed, would we be imposing a limitation that a driver's run assignment would always be for the full run. Is that desirable? Would it make sense to include the piece information in the file as well?

It is fair to say that a duty/run can be "cut" and split between different drivers. In that case, we would need to have some unique identifier on how many pieces the duty is split between drivers and on what date (which we have already). Since a duty might repeat itself every day but on a different date. For instance - 1/3, 2/3, 3/3).

Some questions on proposed vehicle_assignment.txt:

are there different types of assignments we need to account for?
how do we account for the same vehicle being assigned to multiple blocks on a given date? or the same block assigned to multiple vehicles?
is there a case where a block might be assigned no vehicle within the schedule, and instead only assigned on the day of operations?
do we need a master list of vehicles that vehicle_id can pull from? [we also have add Vehicles.txt  #30, which currently doesn't have a vehicle_id field but should.]

one more q for driver_assignment.txt

would it make sense for this assignment to be made between an operator and a bid instead to individual runs? with the bid representing a package of runs/pieces during a specific window of time?

I don't think we should have additional assignments for vehicles, but it depends also on the receiving end  (the AVL) to elaborate on whether there is another use case from their side.
We can add a unique identifier to the number of pieces a block is worked on by different vehicles (same as proposed for the duties).
I assume no vehicle assigned is possible, due to maintenance and such. In that case, we would need a real-time aspect to inform the AVL of the change in allocation (this goes a bit further)
I proposed the vehicles.txt as an option for the AVL provider to be in sync with the information the dispatching software has. The advantage of using this file is to have a complete sync between the list of vehicles the dispatching software holds and the AVL provider. How often is a vehicle being added or removed from the fleet? on the same note, perhaps a drivers.txt file would also be valuable

Separating out the different discussion threads here:

[x] Driver vs job-agnostic personnel assignments
** Rows in this file could be applicable to any personnel that has a run assignment. This will often, but not always, be an operator.
** @skyqrose has provided examples of multi-personnel trips/runs in #54
** Proposal in that issue is to designate job performed within runs.txt rather than in driver_assignment.txt
** Further discussion on this can go to #54

[ ] Will a driver always be assigned during scheduling to a full run?
** Difference of opinion here:
*** @skyqrose says yes, scheduled runs should be assigned to 0 to 1 personnel
*** @hodb says it is possible that a run would be cut in such a way that we need to allow for 0, 1 or many personnel assignments
*** ultimately I believe this is a question of how we approach the normative power of a data standard. We can (1) normatively state that a single run is assigned to at most one person and that agencies using ODS will have to adhere to that, even if it means changing a run nomenclature they have used in the past, or (2) seek to be able to represent a wider array of use cases that exist in practice, even if they do not adhere to the typical definition of a run
** Sky brings up the case of having to make post-scheduling adjustments that result in more than one operator on a run. I agree that this case is out of scope for ODS and doesn't need further consideration
** This question should perhaps go out to the full working group

[ ] Will a vehicle always be assigned during scheduling to a full block?
** Much the same applies here; we seem to have the same options as to whether we allow or disallow the blocks to have multiple vehicle assignments or vice versa
** Hod proposes similar approach as for above

[x] Assignment types for vehicles
** Sort of fishing but also a genuine question: might a schedule assign a revenue vehicle to something other than revenue service (be it, idk, standby, relief, or what have you)? Could that or should that be able to be represented as a block?
** Hod says he doesn't think this is necessary; I'm inclined to agree at this stage unless we receive other feedback

[ ] Block with zero vehicles assigned
** The important point here is whether we end up in a situation where we have a complete list of blocks in the scheduling system, but only a subset of those blocks is captured in ODS, leaving the consumer app with an incomplete list or description of blocks
** Is there a case where this would happen? How would agencies handle this if they were scheduling during an operator shortage, for example? Is it possible that a defined block would not be assigned a vehicle until, perhaps, day-of (and thus not in ODS)?

[x] Personnel link to bids instead of to jobs?
** Sky argues against this as it would obfuscate the information that the consumer actually cares about: the specific work being performed by the operator
** this seems like a convincing argument to me, unless we receive other feedback

Going back to comment on vehicles:

On MBTA Green Line, vehicles are assigned day of. I just wouldn't use vehicle_assignment.txt, or would leave Green Line blocks out of the file. Consumers should be able to handle blocks without scheduled vehicles (and also runs without assigned employees, which also concretely happens in our data).
Having an inventory of all vehicles would be useful. Caveat: For trains that are made of multiple cars, what I really want is an inventory of cars, which doesn't directly correspond to a vehicle in the realtime data which is a full train. (This doesn't apply to bus.)

Ok, that makes sense. As it stands in GTFS and ODS, blocks are defined in trips.block_id and/or deadheads.block_id, so even if a block doesn't have a assignment in vehicle_assignments.txt, we still can have a full definition of what that block's contents are. I'll mark Block with zero vehicles assigned above as resolved

For the train use case, wouldn't we then also need multiple vehicles assigned per block (analogously to the multiple employees per run)?
It also could include a new (optional) field order_in_driving_direction so that the order of cars becomes clear if the provinding system knows it.
We can also ignore this for now, but I think the specification needs to make some statement on
assignments of multiple vehicles to a single block, because technically, users will be able to do that in the proposed format. We should clarify expectations here (explicitly allow or disallow).

As mentioned in another issue, driver_assignments.txt is likely to end up containing more than drivers. staff_assignments.txt would be more generic.

If we want to allow multiple operators on the same run / multiple vehicles on the same block, maybe it's as simple as not enforcing any uniqueness guarantees on these files?
The order_in_driving_direction couldn't apply in this file, because a operator/vehicle is likely to be in a different order on different trips (like if a train turns around and the first car becomes the last). But maybe it could work in runs.txt?

@safrazier17 @skyqrose This issue is currently marked as "Included" in ODS 2.0 here, but I don't see a final proposal of how to add the new files.
Also, the discussion about driver allocations was split off from this issue above, but there it states that the driver assignments should be in the new run_events.txt file - I cannot spot any reference to drivers or staff there. So it seems to me, that we still need to discuss both driver and vehicle assignments as part of this issue?

It's been a while, but this issue has come under discussion again for the rostering working group for TODS 2.1 this quarter. Lots of things have happened in this thread and in the rest of TODS, so here's a recap of where we are, with some new ideas and personal opinions mixed in:
Here's what I think this proposal is:
These two files record which vehicle/person is scheduled to do each block/run. They don't have to cover adjustments made after the schedule is made. They don't describe what's included in those blocks/runs (that's already in trips.txt and run_events.txt).
vehicle_assignments.txt:

Column Name
Required?
Description

date
Required

block_id
Required
Corresponds to trips.txt:block_id

vehicle
Required
Might refer to a vehicle, a train, or a type of vehicle, depending on what happens with the vehicle-related proposals this quarter? Maybe we'd have separate vehicle_type and vehicle_id fields, where you must fill at least one of the columns? We'll need to sort out the details but how to refer to vehicles isn't the hard part of this proposal.

Uniqueness:

A vehicle can do more than one block on a day.
A vehicle type can definitely do more than one block on a day.
As mentioned by timon-k, we need to make some statement about whether to allow multiple vehicles on the same block+date. I lean towards not recommended but allowed (potential use cases: trains with multiple cars; vehicles are scheduled to tag-team a block; or a block could be run with either type of vehicle), and consumers can ignore blocks with multiple assignment if they don't understand it.
Not every block+date combo mentioned in GTFS needs to appear in this file. If it's missing, then we just don't know what vehicle is doing that block, same as if this file doesn't exist at all.

employee_assignments.txt

Column Name
Required?
Description

date
Required

service_id
Optional
In run_events.txt, the unique ID for a run is (service_id, run_id), so this is recommended to make it clear which run the row refers to. It's may not be needed, because you might be able to look up a service_id via the calendar, or your run_ids might be unique even between days. But including it could help prevent errors. Probably needs more discussion.

run_id
Required
refers to run_events.txt. (Will require some discussion to resolve how this interacts with #76)

employee_id
Optional
Who's doing this run on this day? (If blank, then nobody's scheduled to do it.)

Not included: The type of job being performed is described in run_events.txt, not this file. There was also discussion of order_in_driving_direction, but that could change throughout a run, and if we need that, it'd be better to add it to run_events.
Uniqueness:

A person could do multiple runs on the same date (a double shift?) It's probably rare and not recommended, but it makes perfect sense.
A run probably can't be scheduled to be done by multiple people on the same date. (here's my explanation for that, in the middle section) See more discussion on this point below.
If a run is in run_events.txt but not this file, then we just don't know which employee is doing it.

There was some discussion (comment by hodb) about "cutting" a run between different employees. If this was about scheduling an employee to a run on some dates but not every date, then that's already handled because this file would assign employees on one date at a time. If this was about scheduling multiple people to the same run on the same date, then what I've written above wouldn't work, and it'd need to change. @hodb, which case were you describing?
If we do need it, here are some other ideas for how to handle scheduling an employee to only part of a run on a day:

Include an optional piece_id column. If it's filled, then the employee is only assigned to the portion of the run on that piece (as described by the piece_id column in run_events.txt).
For more granularity, include an optional event_sequence field. If it's filled, the employee is only assigned to the one trip/event on that run. (An employee assigned to half a run would probably have many rows in this file to assign them to each of the events they do that day.) This would be the most granular but also the most verbose and complex.
Allow assigning multiple people to the same run, without specifying which portion of the run they're doing. This would be easiest, but not describe exactly how the run is split between them.

Comparison to #45
#45 is another proposal about assigning people to runs. There are two main differences:
First, instead of employee ids, it gives a roster ids. The roster groups together runs that one person would do across multiple days, but doesn't say which person it's assigned to.
In the working group, we'll need to decide whether we want to include specific employees (as in this issue), the bid/roster (as in 45), or both. I lean towards employees being the right level of abstraction to include (I justify that here, in the 3rd section), but it depends on what uses people have for TODS.
Second, instead of working date-by-date, #45 works week-by-week, giving a monday schedule, a tuesday schedule, etc. This is similar to the difference between calendar.txt and calendard_dates.txt. We could work with either approach alone, or both together.
This file would require a lot of rows (one per run per day), and doing it week by week would be more compact. But this file also makes it easier to deal with vacations and irregular schedules, which I think is valuable given that employee's schedules are less likely to be regular than the service schedules in public GTFS.
We don't have to do only #28 or only #45. We could do both, or recombine the two in new ways, according to what information people want represented in TODS.
Summary
In summary, this issue is moving again, but there are still some major decisions to be made about which information and use cases are important. We'll discuss some of it in the working group meetings, but a lot of things are a lot easier to bring up in writing, so leave comments!

@skyqrose Thanks for wrapping up the current state so thoroughly. The draft in this ticket looks good to me already, I just wanted to leave feedback on selected points:

I'm strongly in favor of distinguishing between vehicle_type and actual vehicle in vehicle_assignments.txt. It sounds most useful to allow both columns and require at least one of them to be filled.
I'm fine with ignoring order_in_driving_direction for now, but I don't think we can use the runs to model it. Imagine a train consisting of three coupled cars who never change their order during the day (the train stays coupled). If this is published as three vehicles being assigned to a single block, operated by a single run, then the only place to document the order of the cars would be in vehicle_assignments.txt.
Strongly agree with you that we should keep the tuple of (service_id, run_id) as the run key in employee_assignments.txt
I also agree with you that there should be no need to assign a single run to multiple people on the same date. The run should be split in this case and the runs resulting from this split can be assigned to different people.
https://github.com/cal-itp/operational-data-standard/issues/45 seems orthogonal to our discussion here: It describes rostering information, which as you write is on the boundary between scheduling information and operational information. This should probably happen in different files and be treated separately from the assignments of concrete employees and vehicles.

Thanks for the detailed analysis @skyqrose! the use case I was referring to is the fact that a driver doesn't complete his scheduled run, and another driver would need to take care of it. Dispatchers may deal with unexpected situations during the day that can disrupt a trip or the driver’s day, malfunctioning vehicle, a driver getting sick during the work day, a bus breaking down in the middle of a trip, removing the workload of a driver, and such. We're not talking about multi-assignment but the ability to have modification to the runs and blocks and some reference. It is fair to say that a duty/run can be "cut" and split between different drivers. In that case, we are creating a subset of the original duty performed by different drivers -
For instance, the original duty - 123 was planned for driver A, but ended up being split between A and B. Having the cut means we may need a reference to the run_events.txt file to indicate this duty is done by different drivers

Two reasons to include service_id, given that runs are not unique on different services:

It makes it easier to look up the run in run_events.txt. If the service isn't listed here, you have to look up in the calendar which services are active, and then find an entry in run_events.txt that matches the run_id and also happens on any one of those services.
It could help prevent errors from mixing up runs on different days with the same id. I've had bugs in the past due to calendar exceptions not being applied correctly (holidays, track work, storm schedules), which led to looking at the wrong schedule (Weekday run 100 instead of Holiday run 100), and nonsense data. Always referring to a run as it's full (service_id, run_id) pair prevents those bugs.

Makes sense, but then let's include the service_id in both assignment files?

I drafted something that covers vehicle assignments, here:
https://github.com/antrim/operational-data-standard/blob/vehicle_assignments/docs/spec/index.md
This is based on what @skyqrose outlined in August: https://github.com/cal-itp/operational-data-standard/issues/28#issuecomment-2292345857
Notes:

vehicles.txt and vehicle_categories.txt crib liberally from http://bit.ly/gtfs-vehicles. That proposal aligned with platform descriptions for GTFS-Pathways. I don't know the current status of that proposal. I included a baseline of fields; perhaps more should be included in this proposal.
I considered whether to relate vehicle assignments to run_events.txt, but since mid-run events would never involve the change of a vehicle, this would have created more complexity.
vehicle_assignments.txt can map to trip_id or block_id. This is for cases where block_id is not universally supplied, perhaps because a GTFS feed follows the original usage of block_id - indicating allowed in-seat transfers.

In vehicle_categories.txt, how about adding a bike_capacity or bicycle_capacity field that works in a similar way to the other capacity fields?


Core admin-side TaskGroup attributes

The most user-facing new task attributes are defined in #1828, but TaskV2s or TaskGroupV2s should also include additional metadata that may replace the way we use task.source. That is, the first block of the source (all fields which are shared by tasks of the same package) should be transformed into a set of TaskGroupV2 attributes, so that the only task-specific part is the task name.
Note: for tasks that are added directly (without using task collection), several of the new attributes will be empty - mirroring the fact that their source is currently unstructured. Defining anti-duplication rules for this kind of tasks will require different rules.

Based on these new attributes, we'll then be able to build some logic to handle a few specific cases in endpoints.
Some are existing features which will just become smoother:

I collect a task and I try to collect it again. The endpoint immediately responds appropriately (e.g. a package with the same metadata already exists). This would be the same behavior as in current main, but without the need to check for the existence of a folder (which is quite useful e.g. in a SSH context).
I want collect two independent tasks that have a matching package name (e.g. because they are not canonically normalized). The second API call responds appropriately (e.g. "error: this task collection would use the same folder as another one")

Other are new features related to task-package duplication within the new access-control scheme:
3. I want to collect package X=1.2.3, but the same package&version is already available to me -> the endpoint responds "error: please use the existing package" - ref upcoming issue
4. Consequence of previous point: if I collected package X=1.2.3 privately, then I cannot also collect it a second time and associate it to a usergroup. What I can do is to change the visibility of the existing taskgroup.
5. If I collected package X=1.2.3 privately and then someone else collected it and associated it to a usergroup, then I cannot later make my version "public" - ref upcoming issue.

This was now defined in #1831. Copying from there:
TaskGroupV2 attributes
The first plan is to introduce the list of attributes listed below, for task groups. Note that many of those attributes are not specifically relevant for the current issue, but it's good to start to have them clear.

user_id: int: ID of the user who created this task group (by POST-ing a single-task, or via any kind of task collection). This is the user who "owns" the task group, i.e. who can patch or delete it.
user_group_id: Optional[int] = None: ID of the group of users who can access any task-group task (i.e. see it, insert it into a workflow, and run it).

If set, this user group should include the user_id user - upon creation.
TBD: Do we need to enforce this constraint forever? That is, is is allowed for an admin to remove the user from the usergroup even if this would mean that task-group owner does not belong to task-group usergroup?

origin: Literal["pypi", "wheel", "custom-collection", "single-task"] - the specific names/options are TBD, but this is a useful information to track
pkg_name: str

for pypi/wheel origins, this is a canonically-normalized package name
for custom task collection, this is either inferred or provided by the user
for custom single tasks, this is equal to task.name

version: Optional[str] = None: optional, but always present for pypi/wheel origins
python_version: Optional[str] = None: optional, but always present for pypi/wheel origins
venv_path: Optional[str] = None: optional, but always present for pypi/wheel origins
pip_extras: Optional[str] = None: only relevant for pypi/wheel
active: bool, always True upon creation - can be edited later
timestamp_created (required)

Additional fields may become useful for further lifecycle work, but are TBD for the moment:

timestamp_last_used (updated upon every successful call to submit endpoint)
managed: bool: similar to origin, this determines whether we can remove and recreate the venv.
pip_freeze: Optional[str]: Information needed to recreate a venv.
lifecycle_activity_log: list[str]: this could look like ["{timestamp1} TaskGroup created", "{timestamp2} TaskGroup deactivated", "{timestamp3} TaskGroup reactivated", ..]

origin:
* other for single-task POST or custom task collection
* Either pypi or wheel-file for standard task collection - @tcompa

pkg_name:

normalized package for task collections - @tcompa
task name for single-task POST
TBD for custom task collection


Basic changes to make QAOA and VQE work with Python 3

PR #57 is actually a more extensive set of changes that addresses other parts of Grove too.


Notifications of TOS changes

┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.8
┆Issue Number: DOCK-744
┆Epic: Terms of Service

possible duplicate, needs description if reopened


Outdated cask: tv-browser

Outdated cask: tv-browser.
Info:

version: 3.4.4.
appcast url: https://sourceforge.net/projects/tvbrowser/rss.

Please do not run find_outdated_appcasts unless you are a maintainer.


publish<EMAIL_ADDRESS>

Requested by: @chadwhitacre
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Targets

[x] docker[release]
[x] docker[latest]
[x] pypi
[ ] github

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

I fixed up the changelog manually now to make progress.

Socket error during GH artifact upload. Going around one last time before uploading manually.


Fix parameter type in Python example description

@veyu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

thanks, @veyu!
#sign-off


Full-screen mode on Sierra is broken

Full-screen mode on Sierra is broken. Only current cursor character (in files) or lines (in NerdTree) are visible - everything else is black. Entering full-screen mode is ok, but when you move cursor - it gets black as on screenshot below

Sorry, checked settings one more time and just selected Prefer native full-screen support checkbox in Advanced tab in preferences - and it works.

Also see #312.


Remove nonexistent recipe from yaml

What's changed?

Removes nonexistent recipe from yaml recipe list.
What's your motivation?

Fixes #127.
Anyone you would like to review specifically?

@jkschneider created commit 894f757b9e23eb0e0a50444cd13ed2874017409e and might know best.
Have you considered any alternatives or workarounds?

Instead of removing the line, we could have changed it to the new recipe that was introduced within the same commit. But for me that recipe doesn't fit the Owasp category description.
It would be good to have a more general fix that actually verifies that all yaml recipes contain only valid references to existing recipes in the same jar. I think there was a previous issue where the Owasp list also contained a broken reference.

Agreed. It would be good if the build would verify all META-INF/rewrite/*.yml files in the jar file of recipe libraries.

Was fixed independently in 8eec567cb7a420f54843d294fe82b0c7c037d033


Refs #30593 -- Improve extract check constraints in mariadb get_constraints().

Continue to https://github.com/django/django/pull/11566.

@felixxm I added the _parse_constraint_columns function and also some tests in tests/backends/mysql/test_introspection.py.
I created the example table in mariadb check constraint and added the check_clause from  information_schema.check_constraints table to tests. if you have something else please let me know.
Also, I just check tokens with type tokens.Name because here we just want to extract columns from check constraint but in SQLite we extract them from whole constraints. also, the SQL expression is different in SQLite.

@hramezani Can I push my edits? I added few more tests.

@hramezani OK, I could :smile: We should split changes into two commits:

1st: "Refs #30593 - Added _parse_table_constraints() hook to introspection on MariaDB" (with a new hook and tests that work without any changes in the logic),
2nd: "Refs #30593 -- Fixed introspection of check constraints columns on MariaDB." (with fix and extra tests).

@felixxm yes, you can :smile:
I will do the split.

@hramezani Thanks!


Content width is too narrow

It would be nice if we could have less margin and more usable space for content and code snippets to display.

I expanded the width with the latest implementation of the global style sheet from http://github.com/phonegap/phonegap.github.io


Top bar medium styles possible misconfigured?

Hey guys,
What is the story with the medium sizes for the top bar? By default they look like this:
(added black background for emphasis)

Why is this? Shouldn't it look like this?

Closing styling issues


[Feature] Add Bouncing Text

Description
I want to add Bouncing text animation under Text-Animations
Screenshots
https://github.com/Rakesh9100/Beautiify/assets/131646799/1edee1dd-eb55-4c61-bed6-cda59a49959f
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

@Rakesh9100 new text animation

Go ahead @VaishnaviMankala19


[Maint] update pyside6_experimental to be >6.7

References and relevant issues
Closes: https://github.com/napari/napari/issues/5657
Closes: https://github.com/napari/napari/issues/5644
Description
Permits only pyside6 >6.7, so currently 6.7.1 which appears to resolve the test failures -- at least locally for me.

@napari-bot update constraints

@napari-bot update constraints

@napari-bot update constraints

Bah, different segfault:
https://github.com/napari/napari/actions/runs/9246067031/job/25433325095?pr=6936#step:13:116
This one does pass for me locally though (unlike the viewer one where it segfaulted locally and on ci)

Just in case, PySide 6.7.2 just got released https://pypi.org/project/PySide6/6.7.2/

@napari-bot update constraints

@napari-bot update constraints

@napari-bot update constraints

@napari-bot update constraints

@napari-bot update constraints


Add "ip link show" based modprobe tricks

See https://twitter.com/lucabruno/status/902934379835662336
Closes #86

I've been using this successfully in tianon/docker-tianon, and find that it works pretty darn well. :smile:


Either HTTP or HTTPS is mandatory, but not both

Is your feature request related to a problem? Please describe.
Edgee currently requires HTTP AND HTTPS configurations.
Instead, a user must be able to configure Edgee to receive traffic only in HTTP, only in HTTPS, or both.
Describe the solution you'd like
Change the configuration to allow it
Change the entrypoint::start() method to launch either web::start() and/or websecure::start()

Picked up this issue and working on it. As as first impression of the codebase what I understand is that the
src/entrypoint/web.rs corresponds to HTTP and src/entrypoint/websecure.rs corresponds to HTTPS.
Please correct me if I am wrong and also I believe the change needs to made here in src/main.rs
tokio::select! {
   Err(err) = monitor::start() => error!(?err, "Monitor failed"),
   Err(err) = entrypoint::start() => error!(?err, "Entrypoint failed"),
}

Picked up this issue and working on it. As a first impression of the codebase what I understand is that the src/entrypoint/web.rs corresponds to HTTP and src/entrypoint/websecure.rs corresponds to HTTPS.
Please correct me if I am wrong.

Yeah, you're right!


Fix documentation of Xpub::identifier

:^)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

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

Totals

Change from base Build<PHONE_NUMBER>4:
0.0%

Covered Lines:
20020

Relevant Lines:
24245

💛  - Coveralls


eventPropGetter / slotPropGetter should accept more props

Hey,
slotPropGetter and eventPropGetter currently support className / style, but wouldn't it be nice if we could hand them more props like onMouseEnter or onContextMenu to do all sorts of exciting stuff on slots and events?
I'd like to commit a PR if you're willing to accept such, are you open for that?

I think a PR would be worth it! I would be interested to see what you could come up with.


Block deepcrawl bot

I'd prefer to slow this bot down rather than blocking it completely but documentation for the bot doesn't indicate that it supports the crawl-delay property.
They describe themselves as a:

site architecture analysis tool used by SEOs and web developers

Users won't be using this to find GOV.UK, so we can safely block it at the moment.

Seems sane to me! :+1:


"Windows Product ID" can be blanc?

According to documentation one need following three columns in a CSV:

It says nothing about any of the columns being null/ empty.
Looking at the references PowerShell script/ module, Get-WindowsAutoPilotInfo from PowerShellGallery, the part that gets out "Windows Product ID" is returning an empty string.
From Get-WindowsAutoPilotInfo.ps1 version 3.5

Questions that is not answered in current documentation IMO:

Can "Windows Product ID" be empty in the CSV one upload to Intune?

https://devicemanagement.portal.azure.com/#blade/Microsoft_Intune_DeviceSettings/DevicesWindowsMenu/windowsEnrollment

What is "Windows Product ID"; the product key used for activating installed version of OS edition, or OEM key from BIOS?

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

ID: 74814ff4-77e8-71eb-e78a-fa90cdc37c2c
Version Independent ID: 55e188f7-4368-6d6a-c567-41347098d66b
Content: Use the step-by-step guide to add Autopilot devices and profile - Microsoft 365 Business
Content Source: microsoft-365/business/add-autopilot-devices-and-profile.md
Service: o365-administration
GitHub Login: @Sirkkuw
Microsoft Alias: sirkkuw

@o-l-a-v Thank you for your feedback.

You are correct, This script uses WMI to retrieve properties needed for a customer to register a device with Windows Autopilot. Note that it is normal for the resulting CSV file to not collect a Windows Product ID (PKID) value since this is not required to register a device. Only the serial number and hardware hash will be populated.

I have added this as a note via  PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4013

ProductKey:  This is the Windows product ID, a.k.a. PKID, a 13-digit number that corresponds to the Windows product key that was inserted into the firmware of the device at manufacturing time. OEM's have started to put this value on the box itself, as a bar code

Hope this helps!
Thanks
Sri

@o-l-a-v Thank you for your feedback.

You are correct, This script uses WMI to retrieve properties needed for a customer to register a device with Windows Autopilot. Note that it is normal for the resulting CSV file to not collect a Windows Product ID (PKID) value since this is not required to register a device. Only the serial number and hardware hash will be populated.

I have added this as a note via  PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4013

ProductKey:  This is the Windows product ID, a.k.a. PKID, a 13-digit number that corresponds to the Windows product key that was inserted into the firmware of the device at manufacturing time. OEM's have started to put this value on the box itself, as a bar code

Hope this helps!
Thanks
Sri

@o-l-a-v Thank you for your feedback.

You are correct, This script uses WMI to retrieve properties needed for a customer to register a device with Windows Autopilot. Note that it is normal for the resulting CSV file to not collect a Windows Product ID (PKID) value since this is not required to register a device. Only the serial number and hardware hash will be populated.

I have added this as a note via  PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4013

ProductKey:  This is the Windows product ID, a.k.a. PKID, a 13-digit number that corresponds to the Windows product key that was inserted into the firmware of the device at manufacturing time. OEM's have started to put this value on the box itself, as a bar code

Hope this helps!
Thanks
Sri

Thanks. Please also add to the documentation that PKID being NULL in the output CSV is totally fine.

@o-l-a-v Thank you for your feedback.

You are correct, This script uses WMI to retrieve properties needed for a customer to register a device with Windows Autopilot. Note that it is normal for the resulting CSV file to not collect a Windows Product ID (PKID) value since this is not required to register a device. Only the serial number and hardware hash will be populated.

I have added this as a note via  PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4013

ProductKey:  This is the Windows product ID, a.k.a. PKID, a 13-digit number that corresponds to the Windows product key that was inserted into the firmware of the device at manufacturing time. OEM's have started to put this value on the box itself, as a bar code

Hope this helps!
Thanks
Sri

Thanks. Please also add to the documentation that PKID being NULL in the output CSV is totally fine.

@o-l-a-v Thank you. That is added to the note as well.

@o-l-a-v Thank you. That is added to the note as well.

@msbemba Thank you very much for the contribution and updating the documentation with PR. @o-l-a-v Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Recursive modules now detected

Fixes issue #132 , catches direct and indirect recursion
Recursive modules tests now work
Add a println for multiple errors accumulated during a test

You should try to keep the first line of your commit messages under 50 characters or at least 80 so that github doesn't do this weird "..." stuff

I got an intermittent error during a test run and it occurred in code below in line with FIRRTLStringLitHandler, which does inherit from a object with an member
    val byteArray = raw.getBytes(java.nio.charset.StandardCharsets.UTF_8)
    StringLit(unescape(byteArray, Array()))

I wonder if there could be some race condition intializing this thing
  property(s"Invalid escape characters should fail") {
    forAll(validCharSeq, invalidEsc, validCharSeq) {
      (head: Seq[Char], badEsc: Char, tail: Seq[Char]) =>
        val str = (head ++ Seq('\\', badEsc) ++ tail).mkString
        intercept[InvalidEscapeCharException] {
          firrtl.FIRRTLStringLitHandler.unescape(str)
        }
    }
  }

I believe the problem is actually in
  // Generators for random testing
  val validChar = for (c <- Gen.choose(0x20.toChar, 0x7e.toChar) if c != '\\') yield c
  val validCharSeq = Gen.containerOf[Seq, Char](validChar)
  val invalidChar = Gen.oneOf(Gen.choose(0x00.toChar, 0x1f.toChar),
                             Gen.choose(0x7f.toChar, 0xff.toChar))
  val invalidEsc = for (
    c <- Gen.choose(0x00.toChar, 0xff.toChar
  ) if (!validEsc.contains(c))) yield c

Everywhere you see an if in a scalacheck Gen, this means that it will generate a value then if it fails the if condition it will try again. If it fails more than a set number of times, scalacheck gives up and marks the test as a failure. This problem could be fixed by either increasing the number of times it tries to get a valid random value, or by fixing these generators to not use conditions like that.

retest this please

For Travis you have to rerun it through the web interface

@azidar @jackkoenig ,This appears to be failing running Chisel3 tests here.  Any idea what is going on here.  I think it unlikely that my changes are causing this problem
- /tmp/FailingAssertTester3792273207556073012/FailingAssertTester.v:55: Second verilog $finish, exiting
Assertion failed
    at Assert.scala:11 assert(Bool(false))
1
Assertion failed
    at Assert.scala:11 assert(Bool(false))
1

It looks like travis is complaining about "Instance loops a -> b -> a" is failing? I know that some of the Chisel tests are supposed to fail, so although verilator prints it fails, it actually succeeds.

Too far behind, resubmitting in another branch


Add Wyrmspy and Dragonegg IoCs

This PR adds IoCs for Wyrmspy and Dragonegg. Source is the investigation by lookout:
https://www.lookout.com/threat-intelligence/article/wyrmspy-dragonegg-surveillanceware-apt41

Awesome, thanks!


Invalid vectormath objects can be created using view

This fails, as it should:
vec = vectormath.Vector3([ 1.,  2.,  3.,  4.,  5.])

But this creates an invalid Vector3:
arr = np.array([1., 2., 3., 4., 5.])
vec = arr.view(vectormath.Vector3)

Ideally the latter case should fail as well. This should be possible but may take some work in __new__ and __array_finalize__. See here: https://docs.scipy.org/doc/numpy-1.13.0/user/basics.subclassing.html

@lheagy - I attempted to address this with https://github.com/aranzgeo/vectormath/pull/27
It seems a bit messy, but maybe works. Ideally, what I think would be best is check at __array_finalize__ and if the array is the wrong shape, simply use ndarray view, rather than vector class view. Unfortunately, __array_finalize__ can only mutate the existing array object; therefore, the view class cannot be changed.
As a next best alternative, I mucked around with both __array_wrap__ and __array_finalize__:

__array_wrap__ is called at the end of numpy ufuncs and does allow us to return an array of a different class. So here, I check if the shape is a valid vector shape, and if not just return the ndarray view. This resolves your kron issue (https://github.com/aranzgeo/properties/issues/197).

__array_finalize__ is called a few different ways - (1) after normal constructor, (2) after slicing, (3) view casting. We do nothing here on 1 and 2 (for 1, array is definitely valid; for 2, __getitem__ deals with class). For 3, if the array we are casting to a vector class is the wrong shape, it simply errors. This resolves my problem in this issue.

All this seems risky and possibly very fragile. I'd really appreciate if you had any comments, suggestions, or other cases we could test.

Another funny thing we could do is in __array_wrap__, if the output is a different vector shape (eg, input is Vector3 output is (*, 3), we could return the alternative vector view (eg Vector3Array in this case). But I'm hesitant to do this because we have no way of knowing if the output is actually a Vector3Array or if it just happens to be that shape...

Thanks @fwkoch, sorry for my delay (I am travelling and falling way behind on emails / github!). This works for the workflow / use case I am considering.
Another thought... I am wondering if we want an option to cast a Vector3 to a Vector3Array. For the example I am working with (and this will follow for quite a number of physics examples in geoana) I need to take a dot product between a Vector3 describing the orientation of a dipole and the location of each measurement point, which is a Vector3Array. So I expand the Vector3 to the right size using an outer product or kron and then compute the dot product. In a lot of ways, it would be nice if the output remained a Vector3Array (for validation etc). What about having an option in the Vector3 (allowVector3Array or cast2Array or something along those lines) that then casts it to a Vector3Array when operations are computed on it?

Hey @lheagy, sorry to let this stagnate. Casting between vector3 and vector3array would be nice - I could see that being part of properties especially, when we know the meaning of the vector properties so we can prescribe more specific behaviour.
However, I'm still hung up on my attempt at fixing the original problem in this issue. There are still things that do not work, for example flatten. This seems to do something... complicated under the hood and my naive fixes are insufficient (currently, flatten on a Vector Array causes an error; with minor tweaks it does not error, but the resulting flat array remains the same now-invalid class). I think in order to move ahead with these Vector classes, more detailed thought needs to go into the ndarray subclassing...


Virtual network

Are all the steps mentioned on this page pre-requisites ? Especially is the creation of virtual network a must ? If so, could you provide more detailed steps ?

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

ID: 4b745d67-f3a8-3a4a-5b89-c0e5851ef5e0
Version Independent ID: 82cdad50-be4d-fdb1-7daf-ac686298dd97
Content: Before you deploy App Service on Azure Stack
Content Source: articles/azure-stack/azure-stack-app-service-before-you-get-started.md
Service: azure-stack
GitHub Login: @apwestgarth
Microsoft Alias: anwestg

@cenkersoy Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

Thanks for the feedback, will be modifying the document to make this more explicit as this section is optional.  This phrasing will be reworked - Azure App Service on Azure Stack lets you deploy the resource provider to an existing virtual network or lets you create a virtual network as part of the deployment.

#please-close documentation was updated and published to this effect in November 2018 https://github.com/MicrosoftDocs/azure-docs-pr/commit/281c7c3c1fa6469ee5600e32e5864112df2f9995#diff-7c374a5efa6d13335ec7cb9c7849c840


Y24-097 Asset renaming - Barcode model - code references

Describe the Housekeeping
A Barcode has a Labware, as shown in the following code in the Barcode model:
belongs_to :asset, optional: false, class_name: 'Labware'

The name of this relationship is asset despite the table and model being called Labware.
This story is to add an alias to allow use of the more appropriate relationship name, and update all code references to use the alias.
A future story will be made to rename the database column.
Tasks

[x] Add aliases to the Barcode model to allow use of the relationship name labware. Suggested aliases as follows:

alias_attribute :labware_id, :asset_id
alias_attribute :labware, :asset

[x] Find all code references to this relationship and alter them to use the above aliases.
[ ] A possible test to see if they have all been found is to rename the asset_id column on barcodes locally and remove the alias, and run tests to see what errors.
[ ] Write up any learnings as you go, to help with future stories on different models.

Additional context
This story came out of the following research story. This has more detail and results of investigations that could be useful to read:

https://github.com/sanger/sequencescape/issues/4072

Hi @KatyTaylor, I've added an alias with alias_association, which adds a getter and a setter, similar to what happens when we use alias_attribute. We could have used alias_attribute, but I came to know that it was designed for aliasing attributes. So, with the changes I've made, it should be possible to address asset and labware relations synonymously in Rails web entities (models, controllers) when it comes to the semantics.
Regarding the third task listed in the description: I've tried doing this, but I think it is not possible to come to a working state by just renaming the column and removing the alias. In terms of alias_attribute, it's giving the programmer flexibility to refer to a certain table column with a different name. For instance, it gives the ability for us to refer the column asset_id as labware_id within our business logic. However, I think that it will violate the validations if we just rename the column (I've tried doing this, and validations do fail), as we then would be trying to rename columns that are part of foreign key constraints. I think the way to do this is through a migration. I think it might be something like:
class RenameOldColumnNameToNewColumnName < ActiveRecord::Migration[6.1]
  def change
    # Remove the foreign key constraint
    remove_foreign_key :barcodes, :labware

    # Rename the column
    rename_column :barcodes, :asset_id, :labware_id

    # Re-add the foreign key constraint
    add_foreign_key :barcodes, :labware, column: :labware_id
  end
end

It is my opinion that this migration needs to be part of https://github.com/sanger/sequencescape/issues/4123, as it involves the schema changes. I do not think that there will be a lot of changes required further (in case I haven't missed stuff) in our business logic in terms of the association name, but I do suspect that we would likely to get prompts in test factories for some changes after we add the migration.

Hi @dasunpubudumal
Good find, I hadn't seen that article about misuse of alias_attribute. If you've found another way that makes it "possible to address asset and labware relations synonymously in Rails web entities", then that's great, that's what I was after.
Renaming the field - when I wrote that acceptance criteria, I was trying to think of ways we could be sure we'd found all the code references to the 'old' name. It sounds like it's not as quick a task as I thought to make the schema change locally, temporarily, to smoke out hidden references. If you think it makes more sense to wait until the next story, and accept we may have some further code changes as part of that, then that's fine - it doesn't really matter which story it's done as part of.
Thanks for looking into this so thoroughly, looks like you're making good discoveries that will help with the next model too.


Refresh CI cookie

That didn't work..

That didn't work.. Any help? Current problem is that with (cat test-out.txt && exit 1), the cat output is not actually printed, I think because it's being passed to exit? How would I run both commands and still make cat output to the console?

Not quite sure what you're looking for here. Everything seems to work as intended.
If and only if we fail test cases will we end up running (cat test-out.txt && exit 1), and from what I can tell this will cat the entire test-out.txt file. See Check test status under: https://github.com/Elttob/Fusion/runs/4627907999?check_suite_focus=true
If you're looking to output the full test-out.txt file when we pass all the test cases we need to have grep be quiet using -q and then combine it with && cat test-out.txt:
(cat test-out.txt | grep -q "0 failed, 0 skipped" && cat test-out.txt) || (cat test-out.txt && exit 1)

If I'm misunderstanding something, and you're looking for something else please let me know!

If and only if we fail test cases will we end up running (cat test-out.txt && exit 1), and from what I checked, it does cat the entire test-out.txt file. See Check test status under: https://github.com/Elttob/Fusion/runs/4627907999?check_suite_focus=true

That's exactly what I was trying to achieve.. I looked at a few fail runs and never saw that output. Guess it was a fluke. No changes necessary then.

See now, there, there's no output:

Run cat test-out.txt | grep "0 failed, 0 skipped" || (cat test-out.txt && exit 1)
Error: Process completed with exit code 1.

I think the issue is there literally is no output, because run-in-roblox fails get posted to stderr. Is there any way to combine the stdout and stderr into a single file (test-out.txt) so it gets printed as well?

I think the issue is there literally is no output, because run-in-roblox fails get posted to stderr. Is there any way to combine the stdout and stderr into a single file (test-out.txt) so it gets printed as well?

You can change > into &> to have both stdout and stderr go to the same file:
run: run-in-roblox --place test.rbxl --script test-runner/Run.client.lua &> test-out.txt

You can see this in a test workflow I did (see Check test status):
https://github.com/nottirb/Fusion/runs/4989268886?check_suite_focus=true

That's it! Thanks for the help.

Thanks for the help guys! I'm not super experienced with this stuff so it's good you guys are willing to help out :)
Should I merge this now?

We might need to refresh that cookie again before merging this, since run-in-roblox is failing atm. Might also be worth looking into https://github.com/rojo-rbx/run-in-roblox/issues/21

Resolved by #170


Content update - broken link & grammar

Quick update to fix a broken link, inconsistent use of versions (e.g. v.1.1) and a few other bits and pieces.

Hello @Nerdwood,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Documentation for Connect4 Game

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
I have successfully added the Documentation (README file) for Connect4 game.
Fixes #2363

Mark the task you have completed ✅

[ ✅] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[✅ ] I have performed a self-review of my own code or work.
[✅ ] I have commented my code, particularly in hard-to-understand areas.
[✅ ] My changes generates no new warnings.
[✅ ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[✅ ] I have added screenshot for website preview in assets/images
[✅ ] I have added entries for my game in main README.md
[✅ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[✅ ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

@kunjgit Kindly, review this.

@kunjgit  Kindly, review this please.

Thank you  @SnigdhaP2022 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


[Templates] Add template for Spring Boot service

Feature Suggestion
It should be possible to scaffold a new Spring Boot backend service through Backstage.

Possible Implementation
Add a new "template" and load it from the server.

Context
Demo of this is available at https://www.youtube.com/watch?v=U1iwe3L5pzc

Should this template be in the milestone @stefanalund?

@benjdlambert nah, not really needed I think. But since we are targeting micro service management as the first end-2-end use-case, it does still makes sense add a "service" template.

Done!


DumpOperation is not adjointable or controllable

Describe the bug
DumpOperation (an extremely useful tool!) cannot be called from an operation that asks for all its operations to be adjointable or controllable (for example, an operation specified as is Adj+Ctl). This seems rather odd, since the docs say that it doesn't have an effect observable from Q#, so it would make sense to it behave like DumpMachine which can be called from any Q# code.
To Reproduce
Steps to reproduce the behavior:
I ran the following snippet from Q# Jupyter Notebook:
open Microsoft.Quantum.Diagnostics;

operation DumpCnot() : Unit is Adj+Ctl {
    DumpOperation(2, ApplyToFirstTwoQubitsCA(CNOT, _));
}

I got the following error:
c:\snippet_.qs(4,5): error QS6312: The called operation does not support the necessary functor(s) for the requested auto-generation of a specialization. Missing support for functor(s) Adjoint, Controlled.
Expected behavior
Operation compiled successfully and subsequent %simulate DumpCnot offer me a dump of CNOT.
System information

IQ# version 0.12.20092803

Good catch, thanks for pointing that out, @tcNickolas. We should definitely modify that to be adjointable and controllable, matching the behavior of other Dump* instructions.

@cgranade I had a go at this, and I have the fix for it ready. Can I go ahead and create a pull request if nobody has picked it up yet?

@Pallavi-mp: I'm not aware of anyone else picking this up yet, please go on and open a PR. Thank you for your contribution!


Default to TCP even when no servers are specified

Since this plugin defaults to TCP but dnsjava's DNS Lookup defaults to UDP, setTCP(true) must be called explicitly.
This supersedes my messier previous attempt (closes #12).
/cc @grantr

Nice, thanks for tracking this down.


Please provide an APK

Could you please make an APK file available for download? Most projects attach it to the corresponding release (at releases/), which would be very fine. Thanks a lot in advance!

Sure, I've added one to v1.1.

Thanks a lot! Promotion starts tomorrow around 6 pm UTC here and a little later here :smiley: Will give it a try myself as well. At least one of my devices has camera and flashlight close enough together (the other has them 4cm apart which will make it a bit hard)…
Ah, if you then wish to point to the first location, here's a badge for that. I also gladly assist should you want your app listed at F-Droid.org directly.
Until then: All the best, and thanks again!
Oh, PS: future releases will be picked up automatically within 24h of your attaching an APK to a new tag. Description and screenshots are taken along from Fastlane. Users will then automatically be informed that an update is available (if they use my repo with one of the F-Droid clients available). No tracking, no account needed.

:rofl: Looks like I missed your MR at F-Droid when asking for the APK – I could just have processed that instead. Done now, so your app will not only show up in my repo tomorrow, but at F-Droid a couple of days later as well. Seeing a new build cycle is just about to start, that could even happen only a day later (see: How long does it take for my app to show up on website and client?)
So apologies for the confusion!

Thank you so much!

Gladly done! And we really made it into the current build cycle (APK was built already and should be published within the next few days – with some luck tomorrow night, or shortly thereafter).


:book: Add cloud-config.json for v1.6.0-rc1

Adding manually because job failed to do automatically :P see https://github.com/kairos-io/kairos/actions/runs/4270835378

Codecov Report

Merging #967 (3ed38cd) into master (efc3980) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master     #967   +/-   ##
=======================================
  Coverage   22.79%   22.79%
=======================================
  Files          22       22
  Lines        1610     1610
=======================================
  Hits          367      367
  Misses       1179     1179
  Partials       64       64

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Should never have newobj = this

A newobj is created when a term is used as a variable, or part of a variable, while newobj = this is used for constants.
Instead we should throw exceptions.
In the longer run, being used as a variable should require a typeclass.

Ideally, we should have a variable type class that includes symbolic objects, with newobj a method only on this.

Exception is thrown instead.


Simple "./schema.graphql" not loaded

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

[x] 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox
GitHub: https://github.com/llllvvuu/graphql-eslint-repro
CodeSandbox: https://codesandbox.io/p/github/llllvvuu/graphql-eslint-repro

[ ] 2. A failing test has been provided

[ ] 3. A local solution has been provided

[ ] 4. A pull request is pending review

Describe the bug
yarn lint results in:
Error while loading rule '@graphql-eslint/no-unreachable-types': Rule `no-unreachable-types` requires `parserOptions.schema` to be set and loaded. See https://bit.ly/graphql-eslint-schema for more info
Occurred while linting<EMAIL_ADDRESS>
To Reproduce Steps to reproduce the behavior:
GitHub: https://github.com/llllvvuu/graphql-eslint-repro
CodeSandbox: https://codesandbox.io/p/github/llllvvuu/graphql-eslint-repro
How I made the repro:

create-next-app
make this commit which just adds Apollo's tutorial schema.graphql and graphql-eslint's tutorial .eslintrc.json

Expected behavior
There should be no lint issues
Environment:

OS: MacOS Ventura 13.1 (22C65)
@graphql-eslint/eslint-plugin: 3.19.1
Node.js: v18.16.0

Additional context

I figured it out, you can only put rules in the *.graphql override block, not in the *.ts override block or in the global config. Rules added to the *.graphql override block will still apply to *.ts files.


Horizontal Scroll Emulation for Desktop OS.

The Problem I have:
I want a standard implementation which is easy to enable (like two lines of code) to emulate horizontal scrolling with a modifier key.
My Solution:
I've forked this project and modified the kivy/inputs/providers/mouses.py file to make this work. The code itself works.
I have four issues which I would like to discuss with a maintainer of this project to get my feature fully integrated and ready for release with a new version.

I've not invested enough time to fully understand the configuration and how it is read etc. I've copied the initialization of other attributes for my version but I've not fully tested it with everything kivy has to offer. The fastest solution would be to have someone who's more familiar with the project have a quick look at my changes and give me feedback.
I can create my implementation with two or one attribute. The version with two attributes is more verbose will be slower. The other implementation is faster but relies on the assumption that None in modifiers will always evaluate to False.
I've updated the doc strings already in the mouse.py file but two other files need to have their docs updated. This point should be resolved in conjunction with Point 1.
I'm not very familiar with the development of the kivy project. A quick scroll through the branches didn't reveal a development branch which is used to merge new features into. This is why I'm opening an issue and not a pull request.

What I've tried:
At first, I tried to create a callback at Window level to listen for events of the mouse which I could filter and then proceed to send via self.dispatch_children(...). However this method failed for now since I was not able to create a correctly formatted MouseMotionEvent. And even with guessed values filled in for the all the positional attributes, it wasn't working correctly, mostly because I believe the stop_event was never triggered. I only dispatched the start event. (With more time and more reading through the code, I'm probably able to get this solution working but it's hacky and I don't really like it.)
Then I've modified the source code of kivy and managed to get it working flawlessly by modifying the kivy/inputs/providers/mouses.py however I would like this feature to be incorporated in the main kivy repo so I don't have to modify the source with every update.
Context:
I'm mostly using a mouse with only a vertical scroll wheel. I have a mouse with a horizontal scroll wheel but I don't like that mouse. So I would like to have my kivy app emulate the horizontal scroll wheel with a modifier key.
Additionally, this feature is quite useful since a lot of mice don't have a horizontal scroll wheel, and the scrolling via 'dragging' the Widgets around seems unprofessional and less precise to me. So I'd think, having a global setting with which to enable / disable this feature would be a desirable addition to the kivy project.
Edit:

Changed the link to point to the changes directly instead of my repository.

There is a contribution guide here that explains how to PR to master: https://kivy.org/doc/stable/contribute.html
I'll be frank. I don't like your chances of getting much one-on-one time with a core developer - they have a huge backlog, and this seems like an improvement with a very limited scope (does anyone apart from you alone want this?).

Oh, I see you have already submitted a PR. Missed that, sorry.


PDF outline issue with code

Description
The following heading is not rendered properly in the PDF outline:
= Some `code` block

Basically, code will be removed from the PDF outline.
Reproduction URL
No response
Operating system
Windows
Typst version

[X] I am using the latest version of Typst

Related to #1143, #1098


Custom Menu addition: Dealing with Distro Upgrades

Discovered the hard way through the Kubuntu 22.04 upgrade that using old launch commands through a custom menu can cause problems. Added a warning and some details on how to update a custom menu to use newer ones.

Discovered the hard way through the Kubuntu 22.04 upgrade that using old launch commands through a custom menu can cause problems. Added a warning and some details on how to update a custom menu to use newer ones.

Well that's a bummer, and yeah thanks for the heads up @Jacksaur


[stable/telegraf] Mount utmp for system input

The system input (enabled by default) requires access to /var/run/utmp, which needs to be mounted from the host.
If you don't have utmp mounted, the system input always fails with an error:
Error in input [system]: open /var/run/utmp: no such file or directory

This change adds /var/run/utmp as a volume mount, and mounts it using hostPath in the Deployment.

@jagregory This is mounted on the Daemonset. Why are you trying to run a single instance that is mounting host volumes? I'm separating the two charts to make this more clear.

Thanks for the reply. I wouldn't necessarily say I was trying to do anything in particular.
The default setup of the standalone telegraf works but dumps errors into the logs about not having access to utmp, so I gave it access.
Another angle is: does it make sense for the standalone telegraf to have the system input enabled by default? If it does, then it needs my proposed change, if it doesn't then we should disable it and then this problem goes away.

@jagregory The system plugin is required for another member of our stack Chronograf to properly populate some canned dashboards, but the data doesn't have to be good! 🙊  I'm open to merging this to fix the error.
I am also planning on splitting this chart in two (-ds and -s) And can incorporate this change into the new chart.

@jackzampolin @jagregory how would you like to proceed with this?

I've opened PRs that split this chart into two as well as a PR deprecating this chart

https://github.com/kubernetes/charts/pull/823
https://github.com/kubernetes/charts/pull/822
https://github.com/kubernetes/charts/pull/742

I we can close or merge this PR. Work on this chart will be moved to the two new charts

Closing due to inactivity. Feel free to re-open if needed @jagregory.

@jackzampolin What's the resolution on this? I appreciate splitting up the charts, but this issue is specific to the standalone telegraf spewing errors into the log when it's apparently behaving normally (due to the need for the system monitor to be present, but not being configured correctly). Is this just wontfix until kronograf has a better way of listing hosts?

@jagregory That's what I was thinking. But, I'll back another PR on this one if you want to put it up. Maybe just have a note for users to ignore errors?


RAM usage?

How much ram does this use assuming that I'm using this in combination with tiny yolo?

NNPACK returns required scratch space size to the deep learning framework, but as a low-level library it can't provide a way to estimate total memory consumption. Refer to you deep learning framework for this functionality.


[v2.6] Update Chinese translation

Think it might be too late for 2.6.12. In theory there will be no more 2.6 functional releases now. We do have a release-2.6 in case there is, but it's unlikely to be used. @vickyhella up to you if you wish to change the branch to release-2.6 or close the PR.

I will close this PR and thanks for the info ^


Chart scroll, zoom how to listen

I want to get the value of getDataSpace() dynamically

Instance api subscribeAction(type, callback)


Confirmation email link

Currently the link in the confirmation email is an API route, it should be changed to http://localhost:300/confirm/some_token

Issue has been fixed.

Misunderstood the issue, however now it's actually fixed


feat: add additional test cases

Checklist:

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the main branch of freeCodeCamp.
[X] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Having a single test on these challenges means campers can hardcode the test rather than using the actual callback function.
Adding a test that uses strings instead of numbers should make things more robust.

After some discussion on Discord, I've added another test case that leverages the other parameters that should be present in the callback.


Ability to run the command again against only fresh data

Currently every time you run sqlite-comprehend entities it runs against every row, costing you money for rows that may already have been processed.

I can teach it to only run against rows that don't have corresponding records in the pages_comprehend_entities table (unless you pass --reset or similar) and that will work... but it will still try again for any records that didn't return any entities.
I need a way of recording "this document has been processed but returned no entities".
Two options:

Record a row with nulls in it in the pages_comprehend_entities table. This feels messy, it's likely to confuse people querying the data later on.
Create a pages_comprehend_entities_none table to record that case. I think I like this option best.

The other option would be a table that records a row for every input page that has been processed. This feels a bit more elegant than a _none table that may or may not exist, but will take up very slightly more space.

I played with GPT-3 to see what it thought the best SQL query would be for "return just records that haven't been processed yet":

I'm going to have the command default to only running against new records.
The --reset option can be used to discard that data and run from scratch.
It might be useful to have a mechanism in the future that lets you re-run against the documents specified with the --where clause WITHOUT completely dropping the existing tables. Not sure how to design that option though.

Added a note to the README:

You can delete records from that _done table to run them again.


issue: if 'isValid' value is used, mode and revalidationMode behaves like 'onChange'

Version Number
7.43.9
Codesandbox/Expo snack
https://codesandbox.io/s/react-hook-form-basic-forked-5gi2ng
Steps to reproduce
Based on the closed issue here https://github.com/react-hook-form/react-hook-form/issues/10215 i try to "reopen" this bug.
It makes no sense, that this behaviour of 'isValid' has changed and that the issue was closed with the answer (https://github.com/react-hook-form/react-hook-form/issues/10215#issuecomment-1492946013)
Expected behaviour
isValid should not change useForm modes to onChange
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct

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

I will update the doc once we migrated to 18 to reduce conflicts before the merge: https://github.com/react-hook-form/documentation/pull/940

any news on this issue? I am facing lots of trouble and waste of time trying to mimic the same behavior I had with the validate api from register that existed even with mode onChange. It is totally different now... before, with onChange, this api would not run for all fields on every change or blur event. Now even on blur the hole thing runs,