Add hkupty/iron.nvim.

Checklist:

[x ] The plugin is specifically built for Neovim.
[x ] The lines end with a .. This is to conform to awesome-list linting and requirements.
[ x] It's not already on the list.
[ x] The title of the pull request is Add `username/repo`  when adding a new plugin.
[ x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized).
[ ] If it's a colorscheme, it supports treesitter syntax.

Thanks for the PR!
You are missing a . at the end of the line, when you add that I can merge your PR. See the failing CI.


How to keep track of the drawn layers

[leafletLayers] takes an array of polygons. How can I keep track of the polygons present in the array. for instance assume I have 3 markers each representing a store. How can I know, in the array, which element belongs to which store ?

You could loop through the elements in the array and just console.log() them.

I'm gonna close this cause I think I addressed the question. Thanks!


Define aliased tools as binaries

Define tools as sh_binary's instead of aliases to filegroups, allowing use with rules that expect files_to_run.executable attributes (e.g. https://github.com/erenon/bazel_clang_tidy).

@rrbutani It looks like the failures in CI are unrelated to this change. Are these known to be flaky?

@oliverlee Yup, the external tests are flaky. There were some related changes recently that I think your branch is missing but even with those changes the external tests will still fail.
I wouldn't worry about it and this PR looks good to me but @siddharthab should take a look too (I'm not really an active maintainer of this repo anymore).

Can you rebase your branch on the latest master? I think at least one of those failure is gone by now.
But independent of the test failure, I would not wrap the aliased file in a sh_binary. If one does not exist, maybe making a small custom rule would do the job.


Uniformly draw histograms of data, count, and interval tables

Counts and intervals are the same, I think. Points are just lower bounds of intervals in counted data.


Documentation should make it clear that NumberOptions needs to be set to AllowSign in order to parse negative values

The Integer and Decimal examples in the documentation are incorrect. They give the impression that Terms.Integer() and Terms.Decimal() will successfully parse negative values. However, parsing negative values requires NumberOptions to be set to AllowSign, e.g. Terms.Integer(NumberOptions.AllowSign).

Please submit a PR

I'll check the source to be sure it's intentional. Seems weird. Might be a bug more than a lack of documentation.

I fixed the documentation, this was intentional.


AOP problem

Question
After accessing through Apache shenyu, the project's aop will become invalid and cannot be accessed

whats mean ?

Local service startup Apache sheyu can access AOP normally, but after deployment to the server, it cannot be accessed. What is the reason?


feat: update rst2pdf to 0.99

ReportLab-based reStructuredText to PDF renderer
Issue: https://github.com/linuxdeepin/developer-center/issues/6334
Log: update repo

/test

/test github-trigger-obs-ci

/topic ghostscript

/topic ghostscript


Removing a large section

#sign-off

#sign-off @ashannon7 Thanks for your contribution. Since you are Microsoft internal, you can use azure-docs-pr repo in the future to avoid the added checkpoint. Thanks, Jason


sf::st_write Doesn't Automatically Create Spatial Index and Stores geometry metadata in a non-standard way

sf::st_write does not do two things that I would think would be standard---create a spatial index on a new layer and store correct geometry metadata in the geometry_columns table.
On 1, looks like you must manually create a spatial index on table creation using CREATE INDEX. On 2, looks like you must manually ALTER COLUMN to specify a geom type and CRS (see https://github.com/r-spatial/sf/issues/1429)---apparently, it's done this way to support multiple CRSes in geom column which... seems like a wreck and I don't quite understand why on earth that would ever be desirable, but okay.

Addressed in 01cd348


Command not correct processed if Args is 1 string long

When passing Args: []string{} to the child process, having only a single string in the array produces an incorrect result (i.e. the command doesn't run). Having more than one string produces the correct result.
Args: []string{"some verb", "some other verb"}
Works
Args: []string{"some verb"}
Does not work

Thank you for the report, @timfallmk
A value of Daemon.Args field is passed to os.StartProcess without any modifications exclude a case when the value is nil.
I can't reproduce the issue. Could you provide detailed steps (and code) to reproduce the issue and information about your OS: go env & uname -a.

See my comment in #35 :)


Better dependencies cache for CI

bors cancel

@curquiza do we want to merge this PR on the releasev0.22 branch?

@irevoire, nope, this will be for v0.23.0 🙂
Plus we have an issue currenlty on the CI (many is working on the fix right now) so you will not be able to merge it ;)

bors merge


Optimize _bulk_get

As part of optimizing the replicator and implementing _bulk_get support for it, noticed that _bulk_get is implement in the most inefficient way possible: it makes sequential fabric:open_revs/4  calls for each {doc_id, rev}, when instead it could be grouping documents by shard range an issuing a bulk open_revs request per shard range, not unlike what _bulk_docs does.

For instance, here is a snippet of logs from running a basic benchmark with couchdyno:
POST /cdyno-0000001/_bulk_get?latest=true&revs=true&attachments=false 200 ok 420
POST /cdyno-0000002/_bulk_docs 201 ok 122
POST /cdyno-0000001/_bulk_get?latest=true&revs=true&attachments=false 200 ok 429
POST /cdyno-0000002/_bulk_docs 201 ok 126
POST /cdyno-0000001/_bulk_get?latest=true&revs=true&attachments=false 200 ok 419
POST /cdyno-0000002/_bulk_docs 201 ok 124
POST /cdyno-0000002/_bulk_docs 201 ok 130
POST /cdyno-0000001/_bulk_get?latest=true&revs=true&attachments=false 200 ok 387
POST /cdyno-0000001/_bulk_get?latest=true&revs=true&attachments=false 200 ok 375
POST /cdyno-0000002/_bulk_docs 201 ok 137

The numbers at the end are the milliseconds it took to process the request. It looks like the _bulk_get (read) requests are almost 2x-3x as expensive as a _bulk_docs (write) requests. So it seems there is room for some optimization there.


Duplicate exclude paths (in subhierarchy) in tsconfig lead to complete ignorance

The tsc binary falsely parses sub directories of the excludes Array. If you add multiple subpaths that have a */subpath notation, the complete content of * will be parsed and all exclude entries will be ignored (not only the ones related to */).
Take this example tsconfig.json:
{
  "exclude": [
    "node_modules",
    "typings/globals",
    "typings/main"
  ]
}

Then the tsc compiler will always parse the given subdirectories, even if they are inside the exclude array and even if there's another top-level path hierarchy. So in this case both node_modules and typings are parsed, that means the typings/* influence the parsing algorithm so that the node_modules entry will be ignored (even if it is parsed correctly itself).
On the other hand, if you only use the most upper directory path only, it will work:
{
  "exclude": [
    "node_modules",
    "typings"
  ]
}

@riknoll can you take a look.

I can't seem to reproduce this behavior. For example, given this set of files:
node_modules/a.ts
typings/globals/a.ts
typings/main/a.ts
typings/other/a.ts
typings/a.ts
a.ts

and this tsconfig.json:
{
    "exclude": [
        "node_modules",
        "typings/globals",
        "typings/main"
    ]
}

The files that I see tsc including are the following:
typings/other/a.ts
typings/a.ts
a.ts

Can you give a more complete example of the file structure you have? Also, can you make sure that the files you are excluding aren't being included because of imports or triple slash references? That doesn't sound like the case since you said the other exclude pattern worked, but it's worth a check.

Jep, I'm gonna need some time. Going to make a small reduced test case demo today in a separate repository so that it's easier to follow. Added you as a collab so that we can freely tweak arount things there. (Link to Repo)

Is this still an issue? do you have a smaller repro?

closing for now. please reopen of still an issue.


Extend the 'build a basic model' tutorial

What is the need for this task.
The 'build a basic model' tutorial is not yet complete. The following items are missing: branch, calculation grid, cross-sections and boundaries.
What is the task?
Add the missing items to the notebook.

Hi @rhutten:
Below is some example material I gave to @RuudHurkmans about Laterals with bc timeseries. Maybe it is a starting point for the extension of the basic tutorial for laterals (and boundaries):
from hydrolib.core.io.bc.models import Constant, ForcingModel, RealTime, TimeSeries
from hydrolib.core.io.ext.models import Boundary, ExtModel, Lateral
from hydrolib.core.io.mdu.models import FMModel

def test_foo():
    bndext = Boundary(
        nodeid="foo",
        quantity="waterlevelbnd",
        forcingfile=ForcingModel(),
    )
    bndext.forcingfile.filepath = Path("foo.bc")

def _create_time_series_values():
    return dict(
        name="boundary_timeseries",
        function="timeseries",
        timeinterpolation="blockTo",
        offset="1.23",
        factor="2.34",
        quantityunitpair=[
            ("time", "minutes since 2015-01-01 00:00:00"),
            ("dischargebnd", "m³/s"),
        ],
        datablock=[["0", "1.23"], ["60", "2.34"], ["120", "3.45"]],
    )

def testfoobar():
    fm_model = FMModel()
    fm_model.filepath = Path(r"d:\path_to_mdident.mdu")

    forcing = TimeSeries(**_create_time_series_values())

    forcing_model = ForcingModel()
    forcing_model.filepath = Path(r"d:\path_to_filename.bc")

    ext_model = ExtModel()
    ext_model.boundary.append(
        Boundary(quantity="dischargebnd", nodeid="example1", forcingfile=forcing_model)
    )

    forcing_model.forcing.append(forcing)

    fm_model.external_forcing.extforcefilenew = ext_model
    fm_model.save(recurse=True)


link para editar no figma
imagem de fundo usada
Originally posted by @K0rgana in https://github.com/gmatheus66/reqon/issues/127#issuecomment-553704846

fiz caquinha, ignorem


ngPluralize: support for HTML tags in translations?

I found myself in a situation where some of the translation, and not all, must be within a strong tag. Since the ngPluralize directive uses element.text() (source) then the string is HTML escaped, and it doesn't work.
<ng:pluralize count="users.length" when="{other:'<strong>{}</strong> users'}" />

Since it may lead to XSS issues, I was wondering how to allow ngPluralize to use element.html() in some cases. If $interpolate already escapes the interpolated values, then maybe the directive could use element.html()? Or may be add an attribute like as="html" to give the user control over the HTML safeness of the translation? All it would need then is:
function ngPluralizeWatchAction(newVal) {
  if (attr.as === 'html') {
    element.html(newVal);
  } else {
    element.text(newVal);
  }
}

+1

+1. In the mean time I've created a gist that I'm using in place of ngPluralize where I need HTML

+1

:+1:

+1

+1

Using html with pluralize should be strait-forward with a small ad-hoc directive as it is the case here
http://plnkr.co/edit/mkKt5rqYorGu4a1t93J8?p=preview

+1

+1

+1


Initial repo commit

Signed-off-by: Mike Ng<EMAIL_ADDRESS>

Merged based on Xiangjing's revivew.


Consider not sending empty headers

Steps to reproduce

Run the AgentHeader unit test. Observe that an unset grpc/ or rest/ header is still sent.
Expected behavior: Such headers with no value should not be sent.

Code example
Please see the AgentHeader unit test. Context: #322.

cc: @alicejli


Convert from discord.py to disnake.

Closes #227.
Updated dependencies too.

@ChrisLovering I'm not sure how I didn't catch these. Will fix.

I didn't look into the requested changes enough lol, I thought I had missed that many discord instances.

Fixed some changes regarding bumping from old to new discord api


accounts-db/write-cache/refactor: move remove_slots_le to test context

Problem
remove_slots_le can be moved to test context.
Summary of Changes
move remove_slots_le to test context.
Fixes #

Codecov Report
Attention: Patch coverage is 90.90909% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 82.8%. Comparing base (92b093d) to head (c203368).
Report is 4 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1489   +/-   ##
=======================================
  Coverage    82.7%    82.8%
=======================================
  Files         876      876
  Lines      371130   371130
=======================================
+ Hits       307273   307321   +48
+ Misses      63857    63809   -48


firebase_messaging: Management of data messages when activity is killed

If the app is in a killed state and a data message is sent, the app will call the onMessageReceived of the FlutterFirebaseMessagingService, but since the Activity is killed the FirebaseMessagingPlugin can not respond to the intent and the message is lost.
This is a problem when somebody wants to perform an action depending on the data which is contained in a message.
Are there any plans to handle this kind of behaviour?

We have a similar use case. When the app is terminated the notification is not delivered. We would still like to store a record of these messages in the application where a user can view or delete them later from the app. Currently, this is not possible on Android devices, although this worked when not using flutter and just the standard android sdk. Would really like to see an option for this use case.

I would also like to see this feature

Can we add one more class extending FirebaseMessagingService and register in Manifest file, is this possible?

@jankuss
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/829. Any further collaboration will be done there.


Improve search fields by adding clearing

Enhancement
We are not using the full potential of the search input field, by using type="text" instead of type="search"

[ ] Add type="search" to input field

Main overview / search view views/search.templ
Adding publications in dataset view views/dataset/add_publication_dialog.templ
Adding datasets in publication view views/publication/add_dataset.templ
Adding departments views/publication/add_department.templ and views/dataset/add_department.templ

[ ] When using the clearing icon x, the search is refreshed

@mietcls Project search popups also?

Yes please, thanks!


Gitea module creates system user and group without reproducible UID/GID

Describe the bug
Gitea module creates system user and group without reproducible UID/GID.
Expected behavior
Every user and group should be created with a statically defined UID/GID.
Additional context
Unfortunately, defining a value now would result in a breaking change. What would be the best way to handle this?
Notify maintainers

@srhb @ma27 @disassembler @bjornfor
Metadata
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:
  - services.gitea

We only declare UIDs/GIDs statically if we have a reason to. Please elaborate why this is the case here.

I would have assumed that every user/group that is created by an official module that resides in nixpkgs has a reproducible UID/GID configured. That would help in several occasions like data synchronization via a shard NFS for example. Using fixed UIDs/GIDs whereever possible would help in getting a really consistent system across different reinstalls.

See https://github.com/NixOS/rfcs/blob/master/rfcs/0052-dynamic-ids.md for further context.
UIDs/GIDs aren't unreproducible per-se, as soon as a UID is allocated for a user X (and saved in /var/lib/nixos), users-groups.pl will ensure that only X will ever get this UID (i.e. no other user can get the UID in question if X was removed). By backing up /var/lib/nixos, the re-install issue shouldn't be a problem anymore. Also, NFS supports different kinds of permission-mappings IIRC.
All in all, we're trying to avoid static UIDs/GIDs whenever possible, so I don't see such a change happening for gitea soon, hence I'm closing. If you'd like to discuss this more thoroughly, I'd suggest to do it in a separate issue instead since this is not a gitea problem.


Stack overflow exception when re-loading VS Code

Install VS Code stable
Install latest pre-release version of Python extension
Open a Python file
Reload VS Code
Open the Extension Host logs

Here's the error in the logs
2023-10-19 22:42:01.557 [error] An error occurred when deactivating the subscriptions for extension 'ms-python.python':
2023-10-19 22:42:01.558 [error] RangeError: Maximum call stack size exceeded
    at Function.from (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3417)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761048)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)
    at v.dispose (/Users/donjayamanne/.vscode/extensions/ms-python.python-2023.19.12921011/out/client/extension.js:2:761074)
    at v.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3521)
    at v.dispose (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:3618)

@DonJayamanne Both of those are coming from tensorboard usage tracker

This is probably because it includes itself.
    constructor(
        @inject(IDocumentManager) private documentManager: IDocumentManager,
        @inject(IDisposableRegistry) private disposables: IDisposableRegistry,
        @inject(TensorBoardPrompt) private prompt: TensorBoardPrompt,
        @inject(TensorboardExperiment) private readonly experiment: TensorboardExperiment,
    ) {
        disposables.push(this);
    }

    public dispose(): void {
        Disposable.from(...this.disposables).dispose();
    }


Feature/home page text

Enter Received the latest home page text from the product team.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Brandon-Aubrey sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Missing underscore dependency

I get a dependency problem with a fresh install from NPM.
Error: Cannot find module 'underscore'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (./node_modules/jshint/src/cli.js:3:25)
    ...

Whoa. My bad. Just noticed that's coming from elsewhere. As you were.


[osx] In full screen mode, clicking the top-left red circle to exit leaves a blank screen

I would add a screenshot, but it'd be all black...

I cannot replicate this. Is it still happening for you @JustinDrake?

Yes, I can still replicate on master. Exact steps:

Open the client
Go full screen (Ctrl + Cmd + F)
Click on the top-left red circle
Observe a completely black screen (I think it's a blank Mac OS X 'desktop')

How are you even getting it full screen?

Oh probably because it isn't supported yet. I'll take a look.

@hoffmabc: I go full screen via View > Toggle Full Screen. Also, you can use the shortcut Ctrl + Cmd + F.

Update @JustinDrake

Is this still a problem @JustinDrake or @morebrownies ?

Full screen functionality has been removed so I cannot trigger this bug. But then full screen seems essential.

@morebrownies can you check on this?

As Justin said, it seems full screen has been disabled so the problem is kind of fixed, but now the question is do people want full screen support on mac? I would think yes, but definitely seems low priority at this point.

Ok no problem. I can go full screen in Windows, so enabling full screen for OSX makes a lot of sense. We can target a fix before v1 mainnet release.

@drwasho Are you sure you were going into fullscreen mode on Windows or just in a maximized window state? They are two different things, with the former being "chrome-less" (i.e. minimize, maximize and close buttons disappear... at least on OSX). (Please pardon me if you totally knew that :)
Anyhow, I've got a PR in for this issue:
https://github.com/OpenBazaar/OpenBazaar-Client/pull/960

Oh right, I was referring to maximised. No I can't go F11 full screen.

This was fixed. It's ready for verification.

Fullscreen works, some modifications are in a PR to change the keyboard shortcut (which is minor).


Support initramfs in FIT

Together with advancedtelematic/meta-updater-raspberrypi#25, this change moves initramfs into FIT.
Having initramfs in FIT is beneficial in several ways:

checksumming for initramfs
signing initramfs
no need to change u-boot scripts or environment if initramfs is removed or added.
..and more.

There is one issue with this pull, which I completely forgot about... In fact, this is an issue with initramfs script.
The issue is that init script from ostree-initrd.bb uses pivot_root and therefore should be on a filesystem using ramdisk (legacy initrd). So it should be on a filesystem of some kind - ext4 right now.
But OE doesn't suppose anybody would use initrd instead of initramfs, it only supports initramfs (not filesystem image, but a cpio archive), see kernel.bbclass and kernel-fitimage.bbclass.
See [1] for more information on ramfs/initramfs and ramdisk/initrd.
Basically, what needs to be done in addition to changes already present in this PR, is:

change init script to use switch_root instead of pivot_root
change INITRAMFS_FSTYPES to some cpio variant

[1] Linux kernel: ramfs, rootfs and initramfs

Ok, I have fixed initramfs-ostree-image issue (3rd commit).
This was tested on a custom platform and doesn't require changes to OE anymore.
I will test this on stock RPi3 next week. (waiting for feedback anyway!)

Am I right in thinking that we have two conflicting requirements here:

AGL uses Smack and xattrs, which doesn't (didn't?) work with a cpio Initramfs (@OYTIS ?)
FIT images require a cpio format initramfs (@Jmennius ?)

Not really a conflict, but a missing feature(s).

There are patches on the (kernel) mailing list which add xattrs support to cpio (format, kernel, tools). I am not sure if these were accepted. This is definitely a long-term solution.

Not really. FIT itself and related infrastructure doesn't care.
The only thing which only likes cpio is OE (see kernel.bbclass and kernel-fitimage.bbclass).
We can send a (trivial) patch to fix that. Initially, I thought that it would not be appropriate since initrd is kind of legacy (initrd == everything that requires an actual filesystem; cpio does not). But if initramfs (cpio) is not on par with initrd (ext and other FS) feature wise - it makes sense.

IMO, the best way is to have cpio support for xattrs. Need to look into it.
BTW, we can boot into ostree system w/o ramdisk, what do you think about this?

Booting without ramdisk would be a great thing to support, that would be nicer for an embedded system and solve the smack/xattrs problem at the same time.
Have you looked into how much work the no-ramdisk option is? If it is easy then we can consider using that as the route for smack/xattrs support.

Just had a chat with @OYTIS. AGL is the only user of xattrs (via smack) that I'm are aware of, and we can simply override INITRAMFS_FSTYPES in the AGL config to fix it up for them.  I'm not completely sure why the ramdisk needs to support xattrs when we pivot root to a filesystem that does, but neither @OYTIS or myself have had time to investigate that fully.
If/when cpio xattrs make it into mainline kernel, or when meta-updater supports booting without a ramdisk, or when the problem with smack booting from cpio goes away, then we can drop the 'ext4' initrd thing altogether. That feels like a good trade-off to get FIT images for everyone else!

I forgot the cp ${DEPLOY_DIR_IMAGE}/${INITRAMFS_IMAGE}-${MACHINE}.${INITRAMFS_FSTYPES} boot/initramfs-${checksum} change wasn't in this branch yet. I just backed this merge out.  Can you make that change on your branch and I'll merge it, please?

I have pushed a fix to branch (although this pull request is closed - I suppose you'll need to merge manually).
Regarding AGL overriding INITRAMFS_FSTYPES - sounds good, but there is one caveat which I have mentioned previously - kernel-fitimage.bbclass won't include non-cpio image in FIT.
OE-core needs to be patches for this to work:
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -377,7 +377,7 @@
 	#
 	if [ "x${ramdiskcount}" = "x1" ] ; then
 		# Find and use the first initramfs image archive type we find
-		for img in cpio.lz4 cpio.lzo cpio.lzma cpio.xz cpio.gz cpio; do
+		for img in cpio.lz4 cpio.lzo cpio.lzma cpio.xz cpio.gz cpio ext4.gz ext4; do
 			initramfs_path="${DEPLOY_DIR_IMAGE}/${INITRAMFS_IMAGE_NAME}.${img}"
 			echo "Using $initramfs_path"
 			if [ -e "${initramfs_path}" ]; then

So maybe we don't really want to merge this until we resolve this cleanly :(

Would it be possible to make the AGL/xattrs case work by disabling FIT images in the AGL config?

Yes, but to support FIT and non-FIT simultaneously we'll also need two u-boot scripts or a bit more sophisticated script to check whether standalone initramfs is available.
advancedtelematic/meta-updater-raspberrypi#25 will only work when initramfs is not standalone (it is either not present at all or in FIT).
In general, I would try to avoid diversity.
If closing this pull is not urgent I would try either of:

Send a patch to oe-core (allowing ext4 initramfs in FIT)
Try to understand the status of cpio+xattrs, and if it is going to be accepted - we can add it as a patch.

With 1 being a temporary/fast solution, and 2 for a long run.


'error writing body to connection' after dropping eventstreaming connection

Bug Report

As part of https://github.com/awslabs/amazon-qldb-driver-rust/pull/77/ I noticed that after I drop the send/receive channels of an eventstreaming connection I get an error logged. I'm not sure if this is doing any harm.
Version

This is a custom build (due to unreleased features) based off smithy-rs tag v0.27.0-alpha. I can try again using a newer version if that helps, but it requires a bunch of effort on my part :).
Platform

macOS.
AWS Services

QldbSessionV2 (unreleased)
Description

the following via tracing:
2021-11-12T18:50:02.573788Z TRACE send_data{sz=83 requested=1}: h2::proto::streams::prioritize: buffered=83
2021-11-12T18:50:02.573800Z DEBUG amazon_qldb_driver::pool: connection pool shutting down
2021-11-12T18:50:02.573841Z TRACE send_data{sz=83 requested=1}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::prioritize: requested=83 additional=82 buffered=83 window=1047868 conn=2030908
2021-11-12T18:50:02.573873Z TRACE send_data{sz=83 requested=1}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::prioritize: assigning capacity=82
2021-11-12T18:50:02.573906Z TRACE send_data{sz=83 requested=1}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::stream:   assigned capacity to stream; available=83; buffered=83; id=StreamId(1)
2021-11-12T18:50:02.573950Z TRACE send_data{sz=83 requested=1}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::prioritize: available=83 requested=83 buffered=83 has_unavailable=true
2021-11-12T18:50:02.574069Z TRACE send_data{sz=83 requested=1}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::store: Queue::push
2021-11-12T18:50:02.574137Z TRACE send_data{sz=83 requested=1}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::store:  -> first entry
2021-11-12T18:50:02.574188Z TRACE send_data{sz=83 requested=1}: h2::proto::streams::prioritize: available=83 buffered=83
2021-11-12T18:50:02.574242Z TRACE send_data{sz=83 requested=1}:Prioritize::queue_frame{stream.id=StreamId(1)}: h2::proto::streams::prioritize: schedule_send stream.id=StreamId(1)
2021-11-12T18:50:02.574271Z TRACE send_data{sz=83 requested=1}:Prioritize::queue_frame{stream.id=StreamId(1)}: h2::proto::streams::store: Queue::push
2021-11-12T18:50:02.574294Z TRACE send_data{sz=83 requested=1}:Prioritize::queue_frame{stream.id=StreamId(1)}: h2::proto::streams::store:  -> already queued
2021-11-12T18:50:02.574342Z TRACE h2::proto::streams::counts: transition_after; stream=StreamId(1); state=State { inner: Open { local: Streaming, remote: Streaming } }; is_closed=false; pending_send_empty=false; buffered_send_data=83; num_recv=0; num_send=1
2021-11-12T18:50:02.574409Z TRACE reserve_capacity{stream.id=StreamId(1) requested=1 effective=84 curr=83}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::prioritize: requested=84 additional=1 buffered=83 window=1047868 conn=2030826
2021-11-12T18:50:02.574441Z TRACE reserve_capacity{stream.id=StreamId(1) requested=1 effective=84 curr=83}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::prioritize: assigning capacity=1
2021-11-12T18:50:02.574468Z TRACE reserve_capacity{stream.id=StreamId(1) requested=1 effective=84 curr=83}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::stream:   assigned capacity to stream; available=84; buffered=83; id=StreamId(1)
2021-11-12T18:50:02.574493Z TRACE reserve_capacity{stream.id=StreamId(1) requested=1 effective=84 curr=83}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::stream:   notifying task
2021-11-12T18:50:02.574518Z TRACE reserve_capacity{stream.id=StreamId(1) requested=1 effective=84 curr=83}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::prioritize: available=84 requested=84 buffered=83 has_unavailable=true
2021-11-12T18:50:02.574546Z TRACE reserve_capacity{stream.id=StreamId(1) requested=1 effective=84 curr=83}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::store: Queue::push
2021-11-12T18:50:02.574570Z TRACE reserve_capacity{stream.id=StreamId(1) requested=1 effective=84 curr=83}:try_assign_capacity{stream.id=StreamId(1)}: h2::proto::streams::store:  -> already queued
2021-11-12T18:50:02.574749Z TRACE want: signal: Closed
2021-11-12T18:50:02.574800Z TRACE hyper::proto::h2: send body eos
2021-11-12T18:50:02.574821Z TRACE h2::proto::streams::streams: Streams::recv_eof
2021-11-12T18:50:02.574857Z TRACE h2::proto::streams::state: recv_eof; state=Open { local: Streaming, remote: Streaming }
2021-11-12T18:50:02.574907Z TRACE clear_queue{stream.id=StreamId(1)}: h2::proto::streams::prioritize: dropping frame=Data { stream_id: StreamId(1) }
2021-11-12T18:50:02.574980Z TRACE h2::proto::streams::counts: transition_after; stream=StreamId(1); state=State { inner: Closed(Error(Io(BrokenPipe, None))) }; is_closed=true; pending_send_empty=true; buffered_send_data=0; num_recv=0; num_send=1
2021-11-12T18:50:02.575009Z TRACE h2::proto::streams::counts: dec_num_streams; stream=StreamId(1)
2021-11-12T18:50:02.575051Z TRACE h2::proto::streams::counts: transition_after; stream=StreamId(1); state=State { inner: Closed(Error(Io(BrokenPipe, None))) }; is_closed=true; pending_send_empty=true; buffered_send_data=0; num_recv=0; num_send=0
2021-11-12T18:50:02.575082Z TRACE mio::poll: deregistering event source from poller
2021-11-12T18:50:02.575095Z TRACE h2::proto::streams::counts: transition_after; stream=StreamId(1); state=State { inner: Closed(Error(Io(BrokenPipe, None))) }; is_closed=true; pending_send_empty=true; buffered_send_data=0; num_recv=0; num_send=0
2021-11-12T18:50:02.575137Z TRACE h2::proto::streams::streams: drop_stream_ref; stream=Stream { id: StreamId(1), state: State { inner: Closed(Error(Io(BrokenPipe, None))) }, is_counted: false, ref_count: 1, next_pending_send: None, is_pending_send: false, send_flow: FlowControl { window_size: Window(1047868), available: Window(0) }, requested_send_capacity: 0, buffered_send_data: 0, send_task: None, pending_send: Deque { indices: None }, next_pending_send_capacity: None, is_pending_send_capacity: false, send_capacity_inc: true, next_open: None, is_pending_open: false, is_pending_push: false, next_pending_accept: None, is_pending_accept: false, recv_flow: FlowControl { window_size: Window(2096489), available: Window(2097152) }, in_flight_recv_data: 0, next_window_update: None, is_pending_window_update: false, reset_at: None, next_reset_expire: None, pending_recv: Deque { indices: None }, recv_task: None, pending_push_promises: Queue { indices: None, _p: PhantomData }, content_length: Omitted }
2021-11-12T18:50:02.575257Z TRACE h2::proto::streams::counts: transition_after; stream=StreamId(1); state=State { inner: Closed(Error(Io(BrokenPipe, None))) }; is_closed=true; pending_send_empty=true; buffered_send_data=0; num_recv=0; num_send=0
2021-11-12T18:50:02.575373Z DEBUG hyper::proto::h2::client: client request body error: error writing a body to connection: user error: inactive stream

I think all of that is simply triggered by dropping the pairs:
https://github.com/awslabs/amazon-qldb-driver-rust/blob/ad2479b168efd8a768ffe71e88bdc40f00cedc01/amazon-qldb-driver/src/pool.rs#L67-L71

cc @seanmonstar do we need to flush somehow prior to dropping? Or is this error benign?

I wrote a test using ReplayingConnection (near identical to the transcribe-streaming one) and the error doesn't show up there. However, my test fails because ..
thread 'test_success' panicked at 'assertion failed: `(left == right)`
  left: `3`,
 right: `4`: Frame count didn't match.

So, under test I have different behavior to what I captured (using RecordingConnection). I do not get the 'error writing a body' message under test.

This is a rather old issue and the sdk has gone GA since this issue was opened. Can you update to the latest version and see if you're still running into this problem?


keep list names visible while scrolling

Hi,
Thanks for this tool. I found it via Mike Masnick's article in Techdirt.
When I scroll my follower list I lose track of which column is which group because the labels stay at the top of the page. This patch should fix that. Full disclosure, I "tested" it via dev tools by adding style attributes to the thead but I haven't really tested it the way it's done in the PR.

Awesome!  I have been wanting to implement this, so glad that you did.  I will review it a bit later today.

No rush! Happy new year!
On Sat, Dec 31, 2022, 16:50 acbeers @.***> wrote:

Awesome! I have been wanting to implement this, so glad that you did. I
will review it a bit later today.
—
Reply to this email directly, view it on GitHub
https://github.com/acbeers/mastodonlm/pull/20#issuecomment-1368284270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALPH7Y7WMB65XMC336K63WQCTB3ANCNFSM6AAAAAATNA3WQ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes, this works reasonably well.  The one change I'd make would be to leave the appbar and controls stable at the top as well (this is another problem with today's layout, where they scroll off the top of the page, too).  If you are willing to try to make that work, go for it.  Or, if not, I'll incorporate this change here into that larger solution

The most direct way I see to do that is to set those elements (the MuiBox-root div and the div containing MuiFormControl-root) to position: sticky as well and then set the top attributes to make them stack (so 0px, 64px, and 144px).
I again tried this out by editing the CSS live and it works. However, I'm not sure if these heights are actually static or if they are being computed somehow. Another approach would be to measure the element heights at runtime and set the top attributes once the page loads.
Is that the approach you would take? Or is there a better way to do this that's built in to MUI?

I have a local solution to this problem using CSS flexbox to get the behavior I described, that doesn't rely on knowing the heights of those elements.  See it here: https://github.com/acbeers/mastodonlm/tree/beers-scrolling

Nice. I won't be offended if you close this then :+1:

Incorporated into a larger change, per above.


refactor: enable noUncheckedIndexedAccess

Closes https://github.com/Mikhus/graphql-fields-list/issues/38

Pull Request Test Coverage Report for Build 79

18 of 19 (94.74%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.6%) to 98.425%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

index.ts
18
19
94.74%

Totals

Change from base Build 70:
-1.6%

Covered Lines:
130

Relevant Lines:
131

💛  - Coveralls


[Feature Request] Allow serving umami.js and the collect api under a base path

It should be possible to configure umami to serve everything from a base path, so that sites that use /api/collect can still serve umami on the same domain

No sure what you mean. Can you provide an example?

Sure, I've hacked it in place for my use on https://perl.bot/ right now it's serving up https://perl.bot/umami/umami.js and hitting the api under https://perl.bot/umami/api/collect, this is so that it can be on the same domain easily without causing any conflicts as the site itself uses /api/ on the same domain for it's own internal use.

I see. Curious how you got it to work. Did you do something like this? https://nextjs.org/docs/advanced-features/multi-zones
But I think it would be possible to pass a hostname to the tracking script instead of defaulting to the current hostname. Then you can host the script wherever you want.

Nothing quite that fancy, I've just edited the tracking script to always assume the api is under /umami/api/collect for now, and then done some fun with the nginx reverse proxy.  The actual admin page I've put under another unrelated domain

Hi there,
I second this one - I want to be able to setup an NGINX ProxyPass directive so that I can make the script look like it's hosted on the same server as my WordPress installation (so browsers know it's just a local script).
I've tried Location /dashboard and Location /_next with ProxyPass but can't get the _next ones to work - not sure if I've misunderstood Nginx ProxyPass directives but it's not working. If I could set a base path I could just Proxy the entire basepath to Umami
At least I think I should be able to...
Unless you have an example set of Nginx ProxyPass rules that you know do work?
Ta for this by the way, it looks really, really good so far

I am also interested in a solution to this since I have spent some time to try to achieve the same thing as @snibbo71 without luck.
Would also be great with deployment examples somewhere, e.g. under the Deployment section on the wiki?
Maybe off topic (sorry) but I provide a basic snippet of a Nginx configuration that I hope could be useful for others if you setup umami behind Nginx reverse proxy.
    # The POST request back from the web page to umami
    location /api/collect {
        proxy_pass http://umami:3000;
        proxy_redirect http://umami:3000/ /;

        # May not need or want to set Host. Should default to the above hostname.
        proxy_set_header          Host            $host;
        proxy_set_header          X-Real-IP       $remote_addr;
        proxy_set_header          X-Forwarded-For $proxy_add_x_forwarded_for;
    }

    # Fetch umami.js from umami so it dosn't need to be stored together with the webpage
    location ~ ^.*(umami.js)$ {
        proxy_pass http://umami:3000/$1;
    }

This commit 78888c3728fe2cbfe363486839f88bfc3f29df3f should enable you to run umami under a subfolder. Can you test if it works?

Ok, in the latest release you can add data-host-url to your script and it will use that value instead.


Android port

Hey, not really a bug.
I've found your and Jason's work pretty handy, so I built an Android app over it. Here is a link to the repo. Standalone apk also available. Hoping you could include it in the readme so it can help others.

great! happy to add a link once the license.md is mirrored and a note about the license is added to the readme, like this:

It is available free for non-commercial use, and may be redistributed under these conditions. Please see license.md for complete details. For commercial use, request a quote.

Done.

thanks!


can't get one vip kit to show available

This kit is a custom kit for our elite members, but for some reason it shows to be used even though this is a new wipe, we have tried everything from creating a new kit to test to even delete and rebuild the plugin.. any help would be apreciated thanks.

Did you delete the data file AFTER the plugin was unloaded? Data is definitely persisting somehow.


[POI] add speak related en-us

Purpose
What is the context of this pull request? Why is it being done?
Close #98
Changes
Are there any changes that need to be called out as significant or particularly difficult to grasp? (Include illustrative screenshots for context if applicable.)

add speech related for en-us only
add CardNames
remove old speech
fix from https://github.com/microsoft/botframework-solutions/pull/3006

Tests
Is this covered by existing tests or new ones? If no, why not?
Feature Plan
Are there any remaining steps or dependencies before this issue can be fully resolved? If so, describe and link to any relevant pull requests or issues.
Checklist
General

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated the appropriate tests
[ ] I have updated related documentation

Hi @darrenj, what do you think of this? If it is good, I will apply these to other languages. Thanks!


iOS build fails on RN 0.60.x with native dependencies

Expected behaviour
Building a<EMAIL_ADDRESS>project that uses react-native-magic-move and its native dependencies successfully on iOS.
Show Actual behaviour
RN relies on CocoaPods from v0.60 onwards to autolink native dependencies.
Doing:
$ cd ios
$ pod install

I get a warning saying this library does not support autolinking.
I tried the classical manual link steps, but I get odd errors with React *.h files not found. My guess is that this library tries to fetch React deps from libraries folder instead of the newly pods I guess, but I am not sure.
Do you foresee an easy fix to support Cocoapods in the upcoming days?
I'm seeing this behaviour on

Device: any iOS simulator
Routing/transition library<EMAIL_ADDRESS>React-native version: v0.60.4
react-native-magic-move version: v0.6.5

Hi. Thanks for letting me know. I've fixed the issue and released a new version:
https://github.com/IjzerenHein/react-native-magic-move/releases/tag/v0.6.6
Let me know whether it works for you now.
cheers

Thanks, works as expected!


Question about using service accounts

Hi, I am part of an org that would like to start using our google drive for some of our applications. It seems a service account would be the most appropriate way to achieve this. The steps I've done so far:

Created an project on our org's Google Cloud console and enabled the Google Drive API for the project
Created a service account in said project and saved its json & client ID
Added the service account's client ID to our org's Google Workspace API section with the google doc and google drive scope
Installed google-drive-ocamlfuse in our Ubuntu test environment

My question is does the service account need to impersonate a Google Workspace user in order for google-drive-ocamlfuse to work? I know it's mentioned in the docs here about impersonation so maybe I am misunderstanding Google's APIs, but why would we want to create a service account only for the service account to actually add files to drive under the guise of another user in the org? Or is the more correct way to think about service accounts is that they are a special type of API authentication that is allowed to modify any Workspace user's data within a given scope hence the name "service?"

Yes, a service account is tied to an application, and if you enable domain delegation (https://developers.google.com/identity/protocols/oauth2/service-account#delegatingauthority), your users can access their data as themselves without having to manually authorize access to the Drive scope.

Okay the that makes sense. From a bookkeeping standpoint, if we want a specific application to be the modifier and owner of the files on the shared drive would we create a new user on our org's workspace, say application@domain, and then use that with the service account or would it be better from a security standpoint to generate a client ID & client secret and authorize those with the application@domain user?

If you want to keep everything segregated, you should create a specific client id/secret. Then you could share single files/folders between actual users and the application. It's more manual work but it's safer.

Thanks for your help, I appreciate it!


Maintain query string

Currently a query string is not preserved on redirect.

Maybe this could be a setting, off by default as not to break any existing installs.


Unimplements dynamic http urls as it wasn't actually requested

I misunderstood a request from @nicmunroe about caching the URL and then
pre-maturely implemented dynamic urls. In practice we've not had a
request for dynamic URLs with URLConnection.

Long story short: this undoes the fanciness as better sooner than later.

cc @nicmunroe

LGTM! 👍


feat(general): bump version to 1.x.x

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


Events not consistently passed to wrapped React components

Describe the bug
Howdy! I'm using @microsoft/fast-react-wrapper to convert these web-components into React components. I've noticed that, for some components, event handler props like onInput and onClick work totally fine, but for others, these props don't seem to do anything. For example, say I have the following wrapped React components 👇
import { provideReactWrapper } from '@microsoft/fast-react-wrapper';
import {
  vsCodeButton,
  vsCodeDropdown,
  vsCodeOption,
  vsCodeTextField,
} from '@vscode/webview-ui-toolkit';

const { wrap } = provideReactWrapper(React, provideFASTDesignSystem());

const VSCodeButton = wrap(vsCodeButton());
const VSCodeDropdown = wrap(vsCodeDropdown());
const VSCodeOption = wrap(vsCodeOption());
const VSCodeTextField = wrap(vsCodeTextField());

I'm able to use the onClick prop of the VSCodeButton component without trouble.
<VSCodeButton
  onClick={() => {
    console.log('works! ✅');
  }}
>
  Click Me
</VSCodeButton>

Likewise, the onInput prop of the VSCodeTextField component works just fine.
<VSCodeTextField
  onInput={(e) => {
    console.log('i see this logged ✅');
  }}
/>

However, the onChange prop of VSCodeDropdown never seems to fire.
<VSCodeDropdown
  onChange={(e) => {
    console.log('never works ❌');
  }}
>
  <VSCodeOption>Value #1</VSCodeOption>
  <VSCodeOption>Value #2</VSCodeOption>
  <VSCodeOption>Value #3</VSCodeOption>
</VSCodeDropdown>

Additionally, I've noticed that the prop types for the generated components aren't totally right. Here, appearance should be a valid prop, but TS throws an error.

Note that this doesn't happen for the wrapped fastButton component.
import { fastButton, provideFASTDesignSystem } from '@microsoft/fast-components';

const { wrap } = provideReactWrapper(React, provideFASTDesignSystem());

const FastButton = wrap(fastButton());

Expected behavior
I'd expect these props to work consistently across the generated React components, but it's quite likely that I'm misunderstand the respective APIs of these components.
Do you have any idea what might be going on?
Desktop (please complete the following information):

Toolkit Version: 0.8.3

@hawkticehurst Good question. I admittedly haven't run through every component, but the lack of prop behavior seems to be sporadic. Part of the problem is that I don't know which props to expect, so it could ultimately just be an education/documentation sort of issue.
I'll keep on digging and add stuff to this issue as I find it

For instance it turns out that I just might be using the dropdown component incorrectly 🤦 . The following code works.
<VSCodeDropdown
  onInput={(e) => {
    console.log(e);
  }}
>
  <VSCodeOption>Value #1</VSCodeOption>
  <VSCodeOption>Value #2</VSCodeOption>
  <VSCodeOption>Value #3</VSCodeOption>
</VSCodeDropdown>

@mattrothenberg thought I'd give you a heads up that there is a conversation going on in another issue thread that might be very relevant/helpful to what we're talking about here.
https://github.com/microsoft/vscode-webview-ui-toolkit/issues/283#issuecomment-959734811

Also thanks for the updates! This is helpful information for me to keep in mind as I start to work on the React sample/docs.

@hawkticehurst Of course! I'm totally down to 🍐 on the React docs with you if you need an extra hand/brain :)

Ooh, I will happily take you up on that offer! Thank you!
I have some low-hanging issues/bugs that I'm trying to tackle this week, but I'll set up a time to chat sometime next week once I'm a bit more started up on the React work.

For instance it turns out that I just might be using the dropdown component incorrectly 🤦 . The following code works, though I still get a weird type error saying that value isn't a valid prop for the option component.
<VSCodeDropdown
  onInput={(e) => {
    console.log(e);
  }}
>
  <VSCodeOption>Value #1</VSCodeOption>
  <VSCodeOption>Value #2</VSCodeOption>
  <VSCodeOption>Value #3</VSCodeOption>
</VSCodeDropdown>

I also encountered this type error, I guess it's the type error of fast-react-wrapper package, maybe need to replace ReactModule.HTMLAttributes with ReactModule.AllHTMLAttributes , how should I define a type to solve it now?

onChange seems to be broken for radio-group as well.
Workaround that I use for now.
<div onClick={e => console.log(e.target.value); } >
    <VsCodeRadioGroup value={1} orientation="vertical">
        <VsCodeRadio value={1}>One</VsCodeRadio>
        <VsCodeRadio value={2}>Two</VsCodeRadio>
        <VsCodeRadio value={3}>Three</VsCodeRadio>
    </VsCodeRadioGroup>
</div>

This issue should be fixed now!
The problem was the result of a limitation in how TypeScript does type inference––you can read more about it in this issue. The solution was to just be more explicit in adding the correct types when registering toolkit components.
Also as a heads up, I'm probably going to wait a bit to publish the changes so that the React component work also gets published at the same time.

@hawkticehurst It appears this type issue has appeared again:
          <VSCodeTextArea
            name="description"
            value={descContent}
            onInput={(e) => setDescContent(e.target?.value)}
            required
          />

I'm currently using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Shoot well that's disappointing to hear. 😔 Thank you for the heads up, however!
As a heads up, we're pretty tightly resourced at this time so it might take a bit of time for me to dive into this but I'll try and put this closer to the top of my priority list during the next few weeks.


feat: ability to add metadata to mint backup

We've discovered that it's useful to add extra data to backups, and absent any more general purpose backup module it's the easiest to just add a field that clients can use to put whatever they desire.

@dpc  ## FAILED: cli_test_rust_tests fails
is that flaky, too?

Requires rebase now, but I think all concerns were addressed.


la-go-live

closes #1511, et alia.

Docs Build status updates of commit 3cf9648:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/messaging-extension/action-on-card.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/messaging-extension/zero-term-query.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/request-a-team-one.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/request-a-team-two.jpg
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/calls-meetings-bots-overview.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/rate-limit.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/update-and-delete-bot-messages.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/build-and-test/prepare-your-o365-tenant.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/submission-checklist.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/components/buttons.md
:white_check_mark:Succeeded
View

msteams-platform/messaging-extensions/design/messaging-extension-design.md
:white_check_mark:Succeeded
View

msteams-platform/messaging-extensions/what-are-messaging-extensions.md
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/design/tabs.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/cards-reference.md
:white_check_mark:Succeeded
View

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add Unzip command

Other than sha256 I don't see any issues with this.

And probably unzip should be in builder/commands I think it's just an old mistake to keep tarcmd out of the commands

Ok I'll do this.
I wanted to implement checking sha256 in another PR for all commands that have this option.

Sorry, that I'm skipped details in previous comment. Here is how hashsum changes the game:

Since we have cryptographically strong hash sum of the download anyway we don't need to version URL of the download
It's better to make cache content-addressable. I.e. make cache entry derived from sha256sum rather than URL (we should probably add another cache folder)

This is to make useful improvement: you can change a URL to a mirror, proxy, local dir, whatever, and this doesn't change the container. At some point in future we can also make something similar to url.<base>.insteadOf setting of git.
I think it's important to get checksumming right form the start because changing checksums of the containers is painful for users.

Well, and another issue: you must download a file to a temporary location, check the checksum, and then move the file into a permanent place (and delete otherwise). We don't want to store broken downloads in the cache (when reading old file from the cache it should be checked too, and double-checking of the freshly fetched files should be avoided, for that matter)

Merged. Thanks!


Mask Ratio Issue

The mask ratio for EEG pretraining in your paper is 75%, but in your code (config.py), the ratio is 10%. Could you please tell me the mask ratio you used for EEG pretrain? Many thanks.

Due to my experiment, I think 75% is more rational. For more detail you can see my comment in issue #9

Due to my experiment, I think 75% is more rational. For more detail you can see my comment in issue #9
How much video memory did you use in the second step?  24G or 48G?

Due to my experiment, I think 75% is more rational. For more detail you can see my comment in issue #9
How much  memory did you use in the second step?  24G or 48G?

Sorry, I haven't conducted the second step of the experiment yet. I don't think I have enough GPU Memory. ( I have 24G by the way )


fix(ffe-account-selector-react): fixed accessibility errors

You can link to an issue (or PR) by typing # and the issue (or PR) number in a comment. Github will create a link. So #244 becomes #244 :rocket:

Coverage remained the same at 80.028% when pulling 61605c8517166e2d8c685b5ca9e801d4c801f097 on accessibility-fix-ffe-account-selector-react into 6012f5aaeb8393a89782993041046b371c5515a5 on develop.

#244

@wkillerud could you please review again?


Using default associated types with Lender

I'm trying to use supertrait to add a default for an associated type in the lender crate:
#[supertrait]
pub trait Lending<'lend, __Seal: Sealed = Seal<&'lend Self>> {
    /// The type being lent.
    type Lend: 'lend;
    type Seal: Sealed = __Seal;
}

The problem apparently is that the lifetime 'lend is not propagated to the DefaultTypestrait:
            pub trait DefaultTypes<__Self, __Seal: Sealed = Seal<&'lend Self>> {
                /// Used internally to represent the `Self` type.
                #[doc(hidden)]
                type __Self;
                type Seal: Sealed;
            }
```
You can see the original Lender code here: https://github.com/vigna/Lender/blob/3cb44732f180723135a638c68cfde4f6aa545e8a/src/traits/lender.rs#L25

Do you have any suggestions/workaround for this case? Thanks!

Thanks for the report. Might not get to this for a little bit but would be happy to guide your or anyone through how to fix this and submit a PR!
The key is looking at the visitor pattern that updates lifetimes and making sure it is hitting whatever edge case this represents

Given my personal experience with procedural macros, unless they're impeccably documented it is almost to do anything beyond trivial fixes, but I'll give it a try. :)


Added websites developers should visit.

A couple of generic website developers can visit to keep upto date. (technology specific ones can be added later)

Thank you for contributing.
Unfortunately, I am very reluctant to merge this into the repo. There are two reasons.
Reason 1
From a philosophical standpoint, I am against resources which generate hype and provide an endless stream of distractions (which HN and Lobsters).
The only resource I find to be valuable in this category so far is The Morning Paper.
Reason 2
This list consists of evaluated resources, which you can consume and get guaranteed results (mindset change or actionable ideas).
I try to cut down time-consuming resources with questionable value.
The info streams are like that - a time sync with questionable return of investments.


Remove Visual Studio Installer

In containers you probably never want to update/modify the installed build tools, but instead just build a new image. Because of that it would be nice to uninstall the VS Installer after the build tools are installed to keep image size down. I tried to run '"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" /uninstall' which is the uninstall string found in the registry, but it doesn't work. I also tried with --uninstall --quiet --passive and a lot of combinations of these switches but none of them seem to actually remove the installer.
Is there any way this can be done apart from manually removing the folder from program files (which is rather hacky)?

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

ID: b91a4a43-5353-97cf-7532-7644aa3b497f
Version Independent ID: 858d9a5c-72f3-6a85-9270-0a0dd9e0438b
Content
Content Source

I have a follow up question to @heaths's answer. Microsoft Visual Studio Installer (MSVI) is listed in Windows 10 the apps list. Simply deleting the Installer folder, will not clear it from the list.
It seems that the deletion-type solution is not win10-oriented.
Do you know of another way that will also clear it from the app list?
Thanks!

We do write the necessary registry to show up here so it can be easily removed via the Settings app. This question was in the context of containers and clearing space, so if you're seeing that you're not in a container. The registry values we write should be no more than 1KB.
This isn't about how to complete remove the installer. If you want to do that in a physical or virtual machine, use the entry you see above instead of deleting the folder.

how public production winform pro.


Introduce the blockdevicefactory module, primarily the get_blockdeviceapi helper function.

Fixes https://clusterhq.atlassian.net/browse/FLOC-1836
Taken from #1347

Address the above points, and then merge.


release-2.1: sql,sqlbase: fix the introspection for pre-2.1 BIT columns

PR: https://github.com/cockroachdb/cockroach/pull/34201
From release notes:

The value of information_schema.columns.character_maximum_column is set to NULL for all integer types, for compatibility with PostgreSQL. [#34201][#34201] {% comment %}doc{% endcomment %}

Closing as issue is out-of-date.


class @Something extends SomethingElse

I'm not getting proper highlighting of anything after the "@something" in "class @something extends SomethingElse"
I'm not using TextMate; I'm using SublimeText, which is compatible with tmLanguage files, just so you know.

class @something also isn't shown in Sublime Text 2's "Goto Symbol" and "Goto Anything" dialogs.
I was able to fix this with a one-line change. In Syntaxes/CoffeeScript.tmLanguage, line 390 in my version, there's a line that says:
<string>(class\b)\s+([a-zA-Z\$_][\w\.]+)?(?:\s+(extends)\s+([a-zA-Z\$\._][\w\.]*))?</string>

You just need to add @? right before each [a-z, i.e., change the line to:
<string>(class\b)\s+(@?[a-zA-Z\$_][\w\.]+)?(?:\s+(extends)\s+(@?[a-zA-Z\$\._][\w\.]*))?</string>

(The first @? is for class @something, and the second one would allow extends @something too.)
But it would probably take me a couple days to learn enough Git to create a pull request for this one-line fix. If someone else wants to make a pull request, or just commit the fix, that'd be great.

I just put it in myself. Also fixed that class names had to be more than one letter long for highlighting to work.
On Saturday, 25 February, 2012 at 7:44 PM, Joe White wrote:

class @something also isn't shown in Sublime Text 2's "Goto Symbol" and "Goto Anything" dialogs.
I was able to fix this with a one-line change. In Syntaxes/CoffeeScript.tmLanguage, line 390 in my version, there's a line that says:
(class\b)\s+([a-zA-Z$][\w.]+)?(?:\s+(extends)\s+([a-zA-Z$.][\w.]*))?
You just need to add @? right before each [a-z, i.e., change the line to:
(class\b)\s+(@?[a-zA-Z$][\w.]+)?(?:\s+(extends)\s+(@?[a-zA-Z$.][\w.]*))?
(The first @? is for class @something, and the second one would allow extends @something too.)
But it would probably take me a couple days to learn enough Git to create a pull request for this one-line fix. If someone else wants to make a pull request, or just commit the fix, that'd be great.

Reply to this email directly or view it on GitHub:
https://github.com/jashkenas/coffee-script-tmbundle/issues/63#issuecomment-4178481

Merged.


haskell-language-server: nuked references to GHC causes hlint plugin to fail

Describe the bug
The builder for haskell-language-server removes references to GHC in HLS binary. This causes plugins like hlint to fail: https://github.com/haskell/haskell-language-server/issues/591.
To Reproduce
Steps to reproduce the behavior:

nix-shell -p haskell-language-server (on unstable channel)
Launch VS Code (or any other editor that can connect to HLS)
Try applying any hlint quick fix ("Apply hint: ...") in the editor
Observe error

Expected behavior
Applying hlint suggestion via HLS should not fail.
Additional context
This seems to only affect haskell-language-server (and not haskellPackages.haskell-language-server). Applying hlint suggestions with haskellPackages.haskell-language-server works.
Here is the actual root cause: https://github.com/alanz/ghc-exactprint/issues/96.
Maybe it would be possible to fix this in nixpkgs while we wait for the fix upstream? I think the references to GHC are removed here https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/haskell/haskell-language-server/withWrapper.nix#L19. I am not actually sure why it's necessary to remove these references. Is it because of using haskell.lib.justStaticExecutables? Would something else break if references were not removed?
Notify maintainers
@maralorn
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: [ haskell-language-server ]
# a list of nixos modules affected by the problem
module:

Huh, interesting. The hlint plugin works for me despite of the nuked references. But not sure if I've tried the other package you mentioned.
The problem is, that haskell-language-server per default pulls in 4 hls packages and therefore would pull in 4 ghc dependencies.
That means installing pkgs.haskell-language-server would have a closure size of around 4 GBs ...
So nothing would break explecitly, but I expect people would be annoyed. Finding a fix for this issue would be great!

The manual describes in section https://haskell4nix.readthedocs.io/nixpkgs-users-guide.html#how-to-install-a-compiler-with-libraries how to set the environment variables NIX_GHC_LIBDIR et al. I assume that you have not set that environment variable for your shell environment? If that is so, could you please set the variable (and the others) and try again? I'm pretty sure that configuring the path to your ghc installation in the environment would fix the issues you're seeing.

Sorry for the late reply. I have found that NIX_GHC_LIBDIR does indeed fix the issue. Here is an environment that works for me:
with import <nixpkgs> {};
mkShell {
  buildInputs = [
    ghc
    cabal-install
    haskell-language-server
  ];

  shellHook = ''
    export NIX_GHC="${ghc}/bin/ghc"
    export NIX_GHCPKG="${ghc}/bin/ghc-pkg"
    export NIX_GHC_DOCDIR="${ghc}/share/doc/ghc/html"
    export NIX_GHC_LIBDIR="${ghc}/lib/ghc-$($NIX_GHC --numeric-version)"
  '';
}

However, I am now quite confused why these environment variables are not needed to be set up for the language server under haskellPackages.

I'm wondering about the state of this issue. Can we close this? Or is there any particular action left that we have to do?

I'm wondering about the state of this issue. Can we close this? Or is there any particular action left that we have to do?

@peti The question here is this, and I think you are the most qualified to answer it, would not nuking those references fix the noticed issue under some circumstances or is the claimed relation in this issue just wrong?

@peti The question here is this, and I think you are the most qualified to answer it, would not nuking those references fix the noticed issue under some circumstances or is the claimed relation in this issue just wrong?

I think we can close this. The culprit was that I didn't know about the NIX_GHC... env variables.
Also, the upstream issue seems to be fixed: https://github.com/haskell/haskell-language-server/pull/1225.

I think we can close this. The culprit was that I didn't know about the NIX_GHC... env variables.
Also, the upstream issue seems to be fixed: https://github.com/haskell/haskell-language-server/pull/1225.


Update to google-protobuf 3.2.0

Codecov Report

Merging #58 into master will increase coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
+ Coverage   99.29%   99.43%   +0.13%
==========================================
  Files          13       13
  Lines        1428     1421       -7
==========================================
- Hits         1418     1413       -5
+ Misses         10        8       -2

Impacted Files
Coverage Δ

spec/google/gax/operation_spec.rb
100% <100%> (+0.51%)
:white_check_mark:

lib/google/gax/operation.rb
100% <100%> (ø)
:white_check_mark:

spec/google/gax/bundling_spec.rb
100% <ø> (+0.3%)
:white_check_mark:

Continue to review full report at Codecov.

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


Incorrect license

The tooling may have declared an incorrect license.  Please see https://github.com/clearlydefined/curated-data/pull/2058 for details.

@ignacionr @geneh Tagging you both on this since you likely don't look at this repo much :-)


Was Able to Generate A Community Without handle now I can't edit it but it shows up on Search

Describe the bug
Created a community and https://explorer.mainnet.near.org/transactions/9xDZThM287v2kvqEvvM2HrSTG7DWPwSerL6h2yeWwVQ6 it went through but for some reason handle left out
To Reproduce
Steps to reproduce the behavior:

Created community
somewhere along the way I logged in with different account on near.social gateway
Expected behavior

You must put a Community handle to continue
OR able to edit Community you are admin for (admin dashboard)
Able to view the DAO
Communities page omit any communities without handle

Screenshots
If applicab

Desktop (please complete the following information):

MACOS Desktop

Correction: the community was created with a handle, but then the handle updated to an empty string ( same for the tag )


[Feature] Japanese language support

Background
There are many people using this workflow in Japan, and I would like to create a Japanese version of the README since it does not exist.
WHAT
make README (Japanese ver)

It's cool, thank you

Thank you!!
I have created a pull request, please review and merge!


Tooltip remains visible after pressing Android back button

See video, I would expect the tooltip to dismiss on back press. How can we solve this?
https://github.com/appcues/appcues-react-native-module/assets/1288101/43acc34e-a13a-44e9-b83a-1c25f0a70895

Any update here?

@jp1987 sorry the delay we are still investigating a possible solution for this.

adding some context to this issue.
The problem is that the native back button or the navigation back is getting ignored on Android for ViewPresenters that shouldHandleBack is true (Modals, Tooltips).
The reason is because we rely on an Android onBackPressedDispatcher to get called by the Activity when the onBackPressed() method is called, the default behavior is overridden for ReactActivity that instead calls for its own delegate (forward the back behavior to any RN navigation system that is being used)
one possible solution is to override your apps MainActivity to include this lines in order to prioritize any onBackPressedDispatcher registered (hasEnabledCallbacks):
override fun onBackPressed() {
  if (onBackPressedDispatcher.hasEnabledCallbacks()) {
    onBackPressedDispatcher.onBackPressed()
  } else {
    super.onBackPressed()
  }
}

Please let me know if this works for your app. in case you want to take this privately you can also reach me at<EMAIL_ADDRESS>


(fix): Dropdowns in the FAQ section

Issue Title
Dropdowns in the FAQ section
Issue Description
When the dropdown to any question is clicked in the FAQ section the whole footer section and the left part of the section is moving up and down with the question.
Expected Behavior
Only the right side questions section should move and respond to the animation.
Actual Behavior
When the dropdown to any question is clicked in the FAQ section the whole footer section and the left part of the section is moving up and down with the question.
Steps to Reproduce
Keep this in mind:

This can be fixed by fixing the height of that section.
Maintain the responsiveness of the section.
Don't alter the alignment or existing design.

Please assign me this issue.

Go Ahead! @Rehan52004 !

@Arindam200 can you assign me this issue ?

Go ahead!

sure

i have created the PR any changes are needed on it or not ?


Build freetype font library via an external script

Further development work, on the back of the PR https://github.com/AdoptOpenJDK/openjdk-build/pull/117

It would be nice to automatically run this if I specify a freetype directory that doesn't exist?

Just to understand what you say - you like me to put a check in there, that if the destination folder specified as path does not exists to run the script otherwise just return.
Where would we be using this script (out of curiosity):

manual execution
via ansible scripts
via Jenkins jobs
via the makejdk / build scripts?


Managed identity auto-login periodically fails from Azure Function App

I have an Azure Function App setup with a system-assigned managed identity. It is initiating a move of files from one storage account in the same subscription as the Function to a storage account in another subscription, but in the same tenant. It is executed several times for different folders every hour, and it works most of the time, but then randomly it'll fail for a bunch of invocations and then work again later in the hour, and by the next hour it's always completely working fine again.
The error is:
Failed to perform Auto-login: ManagedIdentityCredential: Get "http://<IP_ADDRESS>:41044/msi/token/?api-version=2019-08-01&resource=https%3A%2F%2Fstorage.azure.com": dial tcp <IP_ADDRESS>:41044: connectex: No connection could be made because the target machine actively refused it..
My C# code that calls it is:
string arguments = "copy https://source.blob.core.windows.net/ab12345/ABCLog/DEF/ https://destination.blob.core.windows.net/container/AB12345 --recursive=true --include-before 2024-11-25T09:30:42.7597254-05:00 --include-after 2024-11-25T10:30:42.7597254-05:00
ProcessStartInfo startInfo = new ProcessStartInfo()
{
    FileName = "azcopy.exe",
    Arguments = arguments,
    RedirectStandardOutput = true,
    UseShellExecute = false,
};
startInfo.EnvironmentVariables.Add("AZCOPY_AUTO_LOGIN_TYPE", "MSI");
startInfo.EnvironmentVariables.Add("AZCOPY_LOG_LOCATION", Environment.GetEnvironmentVariable("TEMP"));
startInfo.EnvironmentVariables.Add("AZCOPY_JOB_PLAN_LOCATION", Environment.GetEnvironmentVariable("TEMP"));
Process process = new Process()
{
    StartInfo = startInfo
};
process.Start();
process.WaitForExit();

Which is basically equivalent to running:
$env:AZCOPY_AUTO_LOGIN_TYPE=MSI
azcopy.exe copy https://source.blob.core.windows.net/ab12345/ABCLog/DEF/ https://destination.blob.core.windows.net/container/AB12345 --recursive=true --include-before 2024-11-25T09:30:42.7597254-05:00 --include-after 2024-11-25T10:30:42.7597254-05:00

I also opened an issue on the Azure functions repo, as I'm not sure where this error is coming from, the function app itself or the implementation from AzCopy.

Do you have a custom AAD configured in your network?
Failed to perform Auto-login: ManagedIdentityCredential: Get "http://<IP_ADDRESS>:41044/msi/token/?api-version=2019-08-01&resource=https%3A%2F%2Fstorage.azure.com": dial tcp <IP_ADDRESS>:41044: connectex: No connection could be made because the target machine actively refused it..

Above error indicates AzCopy is not able to retrieve a token as the AAD refused the connection.

This error looks more on the networking side which may be due to some wrong configuration. Can you please get in touch with the networking team.

I have directly engaged Microsoft Azure Support.


update manual testing of undo redo

Pull Request Test Coverage Report for Build 572

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 85.654%

Totals

Change from base Build 571:
0.0%

Covered Lines:
2036

Relevant Lines:
2377

💛  - Coveralls


[BUG] Hotbar layout configuration wrong order

Hotbar layout configuration wrong order
Steps to reproduce the behavior:
Set hotbar configuration to 3x4 or 2x6
Hotbars should increment slot left to right first, then top down
These go down, then right. It looks like the 4x3 and 6x2 were rotated
I'm super super excited for this project. I've been saying that this tool should be built for years, and that desire actually got me to start learning to code.
I'm still nowhere near where I'd need to be to implement something like this, so i'll be following closely!

Added screenshot for reference during fixing.
Additionally, the hotbar numbers are at the wrong spot.

Hey @Rukongai ! First of all, thank you very much for the report.
As you said that you code already and it got you to start coding, I think this would be a very good first issue to get started as the change should just be a minor logical one in the hotbar.component.scss in how the width is being calculated.
Please let me know if you want to give it a try and I'll keep it for you. Otherwise I'll take this back around end of next week ;)
Cheers

i'll take a look!


How to set 'selected'?

client gets options for multiselect from server when page is loading, but I can't set item, it worked on 0.3.1, but didn't work on 1.1.3, could u help me? sorry for my english)

Please provide some more details. How does your code look like? Are you sure you’re following the documentation? There were several breaking changes from 0.3.1 and 1.1.3.

index.coffee
template = require('./index.jade')()

Multiselect = require('vue-multiselect').Multiselect

module.exports =
  name: 'form'
  template: template
  components:
    'app-multiselect': Multiselect
  props:
    model:
      type: Object
  data: ->
    options: [
      text: '2005'
      value: 1
    ,
      text: '2006'
      value: 2
    ,
      text: '2007'
      value: 3
    ]

index.jade
app-multiselect(v-bind:options="options"
                v-bind:selected.sync="model.year"
                v-bind:multiple="false"
                v-bind:searchable="true"
                v-bind:close-on-select="true"
                v-bind:allow-empty="false"
                placeholder="Начните вводить для поиска"
                deselect-label="Выбрано"
                select-label=""
                selected-label="Выбрано"
                label="text"
                key="value")```

if I understand correctly, it's not working because props are loading after page, and selected doesn't change dynamically, but this code is working on 0.3.1

Please look into the documentation. .sync is deprecated. You have to handle the change manually with v-on:update="updateHandler" function.

v-on:update is useful only when selected changes by multiselect, if I'm changing selected in code (e.g.) v-on:update cant help me (or I'm mistaken?) so, I did it by adding timeout in asyncData, now it works. thank you for your help)

If you want to change the selected value outside of multiselect you simply have to change the model.year props. Multiselect should update automatically.

is there an event to detect changed of selected value outside of multiselect?

I’m not sure I understand the question. You can just modify the :value to change the selected value of Multiselect. If the change happens outside of Multiselect why should multiselect emit any events? Just set a watch on the parent component on the value that you pass.


app:civ_border_width and   app:civ_border_color are not working.

Well, I'm pretty sure the attributes are not broken in general. Please have a look at the sample app and provide some details about your setup.


Better status writing

Istio writes status now/soon in a few places:

Analysis: uses status manager, enqueues diag.Messages as context and has some special logic in the status manager to translate this into a UpdateStatus call.
Gateway: uses status manager, enqueues the full Status object and writes that as an UpdateStatus object.
IP allocation: uses its own queue, with PatchStatus
(future) ambient status writing (https://github.com/istio/istio/pull/51945): uses its own queue, with PatchStatus

The status manager works by enqueuing some work. It essentially has a map of 'pending work' which is object key -> controller -> context. It will process these with dynamic concurrency (a nice feature to avoid serializing all work!). On each object, it fetches that latest object, then applies the context to it in some ways, then calls UpdateStatus.
Effectively, this is a patching mechanism; each controller user just gives info that can be applied to the object. They do not give the whole status object... except the Gateway usage, which passes the whole status object as context, and to 'apply' it does config.status = context.
This is problematic, as it could wipe out previous work.
Ideally, all usage is patch based. This could be both in the library, but also in the actual API server call. This is easy for some fields, but harder for condition based ones or Gateway which has many many fields. If we don't have patching, then we need to be able to handle conflicting writings. Today, we don't have conflicting writes, since objects are either GW API or Istio, and there is no overlapping status writers for these types.
Moving to server side apply may be an option here; if we do that, controllers may be able to always write "patch" type logic, and k8s handles the conflicts. However, this may not work well for Gateway API -- in that case, we actually explicitly overwrite status messages written by other controllers in some places.
If we don't have patching, and use a shared queue, we need a method to block a write and have the controller re-queue. With the current semantics, it is fire-and-forget; you EnqueueStatusUpdateResource and that is it. We would need one of two things:

Trust that the object status changing (from the other controllers change) would trigger the caller to reconcile and retry. I don't think this is safe; for example, we could have a conflict with a write that was actually a NO-OP or otherwise didn't trigger a reconciliation.
We could only support "patch" styles; I don't think this will work well for Gateway usecase
We could have a callback to tell the caller to retry. This still kind of sucks with Gateway, since we only have one giant ReconcileEverything() function, but that is basically what would happen today anyways.

Another option is to forget about trying to use a shared 'status manager' at all. Each controller that wants to write to status can have their own queues and handle things as they see fit. We are already doing this today in 1-2 of the status writers. We could steal the WorkerPool there, and possibly even have a generic shared pool (such that the concurrency of the entire system never exceeds the limit, rather than having N workers * M controllers).

This was a sloppy brain dump, hopefully it makes sense... @ilrudie @MorrisLaw @therealmitchconnors

Thanks for sharing all of this context @howardjohn, very helpful!
Initially, I'm inclined to go with what seems to be the more forward-thinking way of having status writing controllers use their own queue and leveraging a generic shared pool. I'm assuming you're leaning towards that as well? Given the Ambient Status Writing PR where it uses it's own queue with PatchStatus.
If we had to stick with a shared status manager though, server-side apply seems ideal since we're letting K8s do it's job. I agree with what you pointed out with the shared queue approach, reconcile and retry loop can get messy when the reconcile loop isn't triggered. I've worked on systems like that and it's my least favorite. It can get super buggy when you're just trusting objects to trigger things as expected; there's always edge cases that get missed and it can get very nuanced. I'm not too familiar with Gateway API limitations around overwriting status but based on what you've pointed out that might be a bad idea. But again, not too familiar.
Assuming controllers write to their own queue and they have a generic shared pool.....
I'm curious about how the flow could look like. Some clarifications/questions:

have a centralized generic worker pool created that is shared by status update controllers
the worker pool should have a global limit set for pool size. is there a good method to determining appropriate size or is it decided iteratively/overtime? just a best guess based on number of controllers/expected controllers?
one of N controllers submits a status update task to it's own queue. completely independent of the design and implementation of other status update controllers and their queues. (side note: might make sense to document best practices for designing controllers for this new way of status writing to ensure some type of standard/expectation when leveraging the shared worker pool... if it's not obvious that is)
conflict resolution handled by the controllers and their respective queues (maybe include some type of callback mechanism when status update fails)
how do we handle prioritization of the more critical status updates?
lastly, if the intent is to move all status writing to one similar model. I'm a big fan of this! Would make things less complicated logically in the codebase instead of having different ways of doing the same thing.

We have 2 different types of status writing going on as well. There are informational status updates that are useful for understanding the state of the system, troubleshooting, etc... and there are functional status updates which enable some feature to function or proceed. Functional status updates are things we may want to handle differently from informational since things like the gateway deployment controller failing to update the address for gw/waypoint is pretty different in impact from failing to write that a policy was accepted.

We have 2 different types of status writing going on as well. There are informational status updates that are useful for understanding the state of the system, troubleshooting, etc... and there are functional status updates which enable some feature to function or proceed. Functional status updates are things we may want to handle differently from informational since things like the gateway deployment controller failing to update the address for gw/waypoint is pretty different in impact from failing to write that a policy was accepted.

I half agree. But also one persons informational status is another's functional, as they could build third-party tooling that depends on the status?
Maybe they shouldn't do that, though. AS part of our status work, we should clear describe the stable and unstable surface

Agree with @ilrudie 's classification of status writing. I think that is a good way to think about optimizing/prioritizing them in shared pool.

Agree with @ilrudie 's classification of status writing. I think that is a good way to think about optimizing/prioritizing them in shared pool.

Good point. That answers this question I had how do we handle prioritization of the more critical status updates?


Webauthn verifier

[x] Base64URL
[x] Webauthn verifier
[x] Base64URL tests
[x] Webauthn tests

Currently manually tested using the input generated in scratchpad https://github.com/daimo-eth/daimo/pull/330

100% coverage


Same color scheme for all creations

Hello, every time I run a new imagine "" all of my creations have the same colors and are looking generally similar and bland. Is there any way to get more variation? I can upload examples if you'd like.

Please do upload them! Make sure that you have enough num_layers


0.9.7 not published on npm

Can you please keep Bower and NPM synchronized? Thanks.

+1 for that! I had to download everything manually from GitHub! :+1:

+1

+1

+:+1:

Been having an error trying to publish to npm, it seems to think there is already a version that exists
"You cannot publish over the previously published version 0.97.0." : materialize-css

Saw that when i ran the npm info materialize-css command
{ name: 'materialize-css',
description: 'Builds Materialize distribution packages',
'dist-tags': { latest: '0.96.1' },
versions: [ '0.95.3', '0.96.1' ],
maintainers: 'materialize<EMAIL_ADDRESS>time:
{ modified: '2015-06-22T01:34:19.494Z',
created: '2015-02-27T17:45:42.343Z',
'0.95.3': '2015-02-27T17:45:42.343Z',
'0.96.1': '2015-04-07T04:18:11.404Z',
'0.97.0': '2015-06-22T01:29:26.639Z' },.......

Reading from https://github.com/npm/npm-registry-couchapp/issues/148, it seems npm will have to updated when the next version is released.

I'm confused... so npm is not allowing new versions? When will this be fixed? As of right now materialize is still on 0.96.1 on npm.
When can we expect to see 0.97.0?

I thin 0.97.0 will be skipped from npm and the next version should be publishable there.

So... you're just not going to release this version on npm? NPM users will have to wait until 0.97.1 is published? How long will that be?


Many To Many with string based IDs

When following the Many To Many example in the docs:
https://vuex-orm.github.io/plugin-graphql/guide/relationships.html#many-to-many
I get the following error when using string based IDs:
TypeError: Cannot read property 'hasIncrementFields' of undefined

Only thing I changed on the User model is:
id: this.attr(null) // instead of this.increment()

Is there a way to get Many To Many work with string based IDs?

Could you check if this is still an issue with the latest release?


how to perform a performance test of mmproxy-rs?

iperf server install on vds?
iperf client on home pc?
next, run iperf clinet - by specifying the address of the iperf server?
Are there any ways to test TCP mmproxy-rs?
What are the commands for testing TCP mmproxy-rs?

Start an echo server in the same machine as mmproxy-rs is running and then point mmproxy-rs to it
Install tcpkali and run the following command on that same machine:

tcpkali -c 50 -T 10s -e1 'PROXY TCP4 <IP_ADDRESS> <IP_ADDRESS> \{connection.uid} $ECHOSERVERPORT\r\n' -m 'PING\r\n' <IP_ADDRESS>:$MMPROXYPORT

Please note that we have an open issue (#4) that aims to improve the throughput of the TCP proxy by approximately 100%, but I have not yet had the time to fully work on it because of upcoming final exams.

Start the echo server on the same machine running mmproxy-rs - how to start the echo server?

One option for setting up an echo server is to use ncat. To do so, simply enter the command ncat -e /bin/cat -kl 1122 in the terminal. This will start an echo server on port 1122. Another option, which is faster but requires a bit more setup, is bpf-echo. If you want to use this option, you can follow the installation instructions on the GitHub page.

I ran "ncat -e /bin/cat -kl 1122" which command should I enter next to check the performance?

I think I will add more detailed benchmarking docs when I have some time

When should I wait ?


ci(release): v1.0.2

Automated changes by create-pull-request GitHub action

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


ProjectAssignment interface has project and client untyped

ProjectAssignment.project and ProjectAssignment.client are both object in the interface, when in reality they are actually Project and Client (the models already exist).
This causes me issues because I can't do this:
const assignments = projectAssignments.me();

// error: property 'name' does not exist on type 'object'
const projectNames = assignments.map(p => p.project.name);

The same would occur if I wanted to get the name of all clients for my project assignments.

I've raised a fix for this in #118

:tada: This issue has been resolved in version 2.2.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added more details to README.md

Added more details that shines a light on what this project is about.

I've made all the requested changes.


skipServe command line params

Describe the bug
Override skipServe with command line param
To reproduce
Steps to reproduce the behaviour:

Run e2e-test with --skipServe (or something like that
skipServe from config is not overridden with command line params

Expected behaviour
skipServe from config should be overridden with command line params
The same could be applicable to other config params?
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

added skipServe with a few others to PR #22 @andreacaldera .  Hopefully that config is all that's needed for it (there's already a check for it in start-dev-server) :man_shrugging: .


style problem.

after facing a lot of problems and solve them, one of them i was obliged to change my main OS to Ubuntu instead of win 11, now i have this style issue.

please help.

@yks-ny please i didnt find something util in your reference, please if you have any suggestion share it with me. thanks


Add ability to close connection

There should be an ability to gracefully close a connection

I would like to have something the same. I sometimes have problems with duplicated event handlers..

:tada: This issue has been resolved in version 3.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Download Dataset Fails on Windows

This function
def _download_data(name, url):
    _make_dir(RAW_DATADIR)
    input_file_path = os.path.join(RAW_DATADIR, f"{name}.txt")
    if not os.path.exists(input_file_path):
        with open(input_file_path, "w") as f:
            f.write(requests.get(url).text)

Fails on windows 10. f.write fails with an encoding error, Windows needs the text encoded to utf-8

Addressed by this PR: https://github.com/any-LABS/anyGPT/pull/17


We should support a closed and Not merged mode since merged PRs are all closed

This would allow to have three distinct sets.

I think this has been covered with https://github.com/microsoft/vscode-pull-request-github/issues/3271.


Remove teardown.sh

This script shows it's age and is not needed.

It refers to RCs when we use DCs;
It hard codes the service name when 'mysql-master' is just the default
value of the MYSQL_MASTER_SERVICE_NAME template parameter;
It doesn't clean up all objects created by the template, as its name
may suggest.

@mnagy @bparees PTAL

lgtm

green tests


chore: Update to liquid 0.19

This will resolve a borrow checker warning.

For background, the intention of the new filter API is:

Reduce error checking in filters (the new API does type checking, number of args checking, etc)
Speed up parsing by front loading parameter handling to parse time rather than render time
Allow auto-generating help by inspecting what filters are included in the parser

The last one is the one you all will care about the most though it still needs some additional APIs to get it to work.
What we're still not happy with (ie potential future breakages)

Even with the derive macros, writing the new API is a bit clunky to write
The organization of the filters that liquid exposes.  We're still trying to figure out what is the best way to expose std and non-std filters.