Titan Security Key Support

Google Titan keys should be accepted, or an explanation should be provided. Why would you allow a pin or picture password but not a FIDO security key like Titan? It makes no sense from a security perspective and certainly not from the user's perspective.

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

ID: aacf4c87-5c77-1d03-0c60-bc608fabe2f8
Version Independent ID: 70d65968-6f5e-8013-0b0b-6d5d660969e0
Content: Microsoft-compatible security key - Microsoft 365 Security
Content Source: windows/security/identity-protection/hello-for-business/microsoft-compatible-security-key.md
Product: w10
Technology: windows
GitHub Login: @mapalko
Microsoft Alias: mapalko

I vote more for Nitrokey which are trustworthy then the Google ones.
But supporting Fido keys in generally is a more then once already requesting feature

For more information on logging into Windows with FIDO security keys, you should see the Azure documentation on the feature. This has an included list of compatible keys that have implemented the set of functionality listed to be compatible with Windows sign in.
https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-authentication-passwordless#fido2-security-keys

@mapalko but why is this only on azure doc instead of doc for normal windows usage?
No windows enduser use azure.

I second this post.  Why are Titan keys no longer supported?

The issues section of this repository is for article defects.
Please ask this question via the Microsoft with the Feedback Hub app.
Thank you.


[CHANGE]: Remove Chaching

Desired Change
Remove Caching.
Reason/Motivation for Change
Not really needed and only causes headaches.
Impact of Change
No response

change in commit ebc6732f7bb755d23d64057a85220d535b937370.


Build problems on El Capitan

I'm using an up-to-date, Brew-installed version of node (v4.2.1) and npm (v2.14.7) on a OS X system running El Capitan (v10.11). Having cloned the repository, I'm attempting to run the command "npm install --dev", and running into several pages of warnings about unmet dependencies, culminating in a fatal error:
npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/Cellar/node/4.2.1/bin/node" "/usr/local/bin/npm" "install" "--dev"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! Please include the following file with any support request:
npm ERR!     /Users/mcfate/Projects/jsbin/npm-debug.log
Any ideas?

Node 4 isn't supported. Node 0.10 is.


Improve the user experience to enable HAMi vgpu on Volcano

Issue or feature description
As we know, vgpu feature consists of several parts such as HAMi core, volcano-vgpu-device-plugin and scheduler. How to coordinate these parts to help user to enable it easier is so important especially for latest enhancement like vgpu binpacking and spreading ability. This issue is used to track the vgpu feature doc optimizition.

[ ] Add the Volcano installation step in Install and Uninstall part.
[ ] Add examples or guide for user reference to enable HAMi and device sharing scheduler plugin in Volcano.

@Monokaix please help to add the Volcano installation step in the readme.


Update L10N resource files with 4.6 strings from Transifex (20151023)

This is a "open" PR until the RC1 for Apache CloudStack.
I will updated this PR next week (and time to time). The release manager team for 4.6 will accept/merge just before the first RC.
cc @remibergsma

Thanks, great stuff @milamberspace !

Mishandling git commands. I've recreated this open PR for the localization files, see #984
Closes this PR.


NifDoc v0.9 support

The following library does not support Nif.xml 0.9, making it impossible to use with newer nif programs.
Is there any plan for updating this repository and/or the docsys? (I was forced to use a fork of it since the normal one does not generate the files with the v0.9)

There is currently work ongoing on the nif.xml format specification. That needs to be formalised first. We don't have anyone who would be actively working on this project, but open to contributions.

Thanks for your response, I tried looking at the forum or the discord server but nothing looks active., that's why I started this issue to begin with.
If it's still relevant, I was going to upgrade the Niflib for v0.9, I could, eventually, send a pr.

You'll probably want to have a look at this - https://github.com/niftools/nifxml/pull/75

I was using jonwd7's nifdocsys actually as a base for work, but I wasn't aware that you have pushed the new specification to the main repository.

It's only merged into the develop branch, there is a PR from dev > master.
There is also some discussion on https://github.com/niftools/pyffi/pull/62 around parsers


size limit for entries json string

There seems to be a 512 char limit on the json string.
Is there any possibility I could use more chars for my id entry?

Hi,
The limit is actually 520 bytes.  However, you can get more by using the "import" field.  This is not particularly well documented at the moment, though.

I couldn't find any documentation, and what I tried doesn't seem to work :   d/ulrichard   id/ulrichard
Are the includes resolved by the namecoin daemon or the querying application such as nmcontrol, bitmessage ...?

@ulrichard It's handled by NMControl.  I'm actually not sure if we currently implement multiple imports in a single name (I see you're using a list).  The import code is going to be refactored, so we'll make sure lists work properly when we do that.

Wouldn't it be better if it was expanded by namecoind?
That way it would directly work for other applications as well. For example BitMessage.

@ulrichard The intention is for applications such as Bitmessage to read the blockchain using NMControl rather than directly querying namecoind.  I believe Bitmessage supports reading from NMControl, no?


Improve and update documentation and examples

Also, move the major part of the docs to https://github.com/graphprotocol/docs

@dotansimha, I've already update The Graph docs to better showcase graph-client: https://github.com/graphprotocol/docs/pull/183/files#diff-eb3f534cddd1e9353423a2efa6d73b602c6ed681c7f7bf5162733655526c4862R28
Is it sufficient or would you like to see more usage/configuration details?

Yeah, that's perfect for now. I do want to move some usage and examples for specific features, but we want to make some features enabled and included by default (like @live).


Images loading from local storage very slowly

I've been seeing some issues recently with images loading very slowly. I provide the view with the file path uri to the image and it typically loads in a few seconds but every few times I load an image is takes 2+ minutes to load it. I'm not sure what else to do or even where to look. Any tips would be appreciated.

To give extra context, I have a ViewPager with Fragments. Each fragment has one SubsamplingScaleImageView. The user can load this full screen gallery and flip through images that are located on disk. I've found that closing this page and opening it again is slower each successive time. But once it's loaded, flipping through the fragments is fast and without increasing delays. is there some sort of cleanup that must be done?


[SMALLFIX] Fix S3 Document

What changes are proposed in this pull request?
fix docs docs/cn/ufs/S3.md, change alluxio-env.sh to alluxio-site.properties
Fixes＃15035

alluxio-bot, merge this please


Added universal flash algorithm

Added universal flash algorithm(LPC810,LPC812,LPC1114,LPC11U35,LPC1347,LPC1768,LPC1769)

Hi @va009039, please move this to DAPLink if you want this to be mainlined. This repo is going to be end -of-lifed soon.


Collapse prevents radio button update

When using data-toggle="collapse" and data-target on a radio button, the clicked radio button is not checked. See this minimal fiddle: https://jsfiddle.net/p0xkotyr/1/. Reproducible for me in Chrome (54.0), Safari (9.1.2) and Firefox (49.0.2) on OS X 10.11.6.
I didn't find any current open issue on this, just a couple of rather old closed ones:

https://github.com/twbs/bootstrap/issues/1060
https://github.com/twbs/bootstrap/issues/3857

Thanks for taking a look!

Yes it's due to this line : https://github.com/twbs/bootstrap/blob/v4-dev/js/src/collapse.js#L354
IMO, If you want to check the radio button, you have to listen this event show.bs.collapse and checked manually your radio button.
$('input').on('show.bs.collapse', function() {
  $(this).attr('checked', 'checked');
})
.on('hide.bs.collapse', function() {
  $(this).attr('checked', '');
});

I get that, but isn't the point of using data- attributes to avoid the need to roll your own JS? But if this is by design, perhaps it's worth a short explanation in the docs?

As it said in the documentation (See http://v4-alpha.getbootstrap.com/components/collapse/#via-data-attributes) :

Just add data-toggle="collapse" and a data-target to the element to automatically assign control of a collapsible element.

By doing this you didn't declare your Collapse in JavaScript like this $('input').collapse() that's all

The behavior comes from the call to event.preventDefault(); in the click event handler. Is the recommended option to check if the target is a radio/checkbox input, or to actually add custom code to counter the effect by adding a checked attribute manually?
Testing the type of target should not be hard, but would probably require to think about which elements should fall into this list if not just radio and checked.
I have tried @Johann-S 's suggestion but this specific event is triggered on the targeted collapsed element, not the originator. I found the click.bs.collapse.data-api event though, but whatever I tried to do the checkbox doesn't reflect it's checked property or status.

Yeah my suggestion was bad sorry for that but yes what I want to suggest is exactly what you said :

Testing the type of target should not be hard, but would probably require to think about which elements should fall into this list if not just radio and checked.

Closing as a dupe of #22049.


Update provisioning script to add ARM toolchain to PATH

Description
This update is to ensure all ARM tools are available for compilation/deployment, as currently arm-none-eabi-objcopy and such tools are missing from the PATH.

Sending today.

Thank you @boldninja - is there a backlog for the open source ARK work? I can't promise I'll get around to much, but it'd be good to know in case something relevant comes up again as I'm working on ledger stuff for a while.


Creating a new release

@domcleal @djberg96 Would one of you be willing to add me as an owner on https://rubygems.org/gems/rkerberos, so that I can create new releases at some point? I'm https://rubygems.org/profiles/sonOfRa on rubygems.

@sonOfRa ok, I added you.

Thank you.

@sonOfRa You should add your email to the gemspec and add yourself to the "Authors" in the README.

I'll do that in the commit that I'll tag for the next release, probably some time this weekend.


Pagination accessibility focus not working

I'm submitting a ...
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior
Pager pages li element not focused/highlighted if using keyboard navigation (tab) to get there.
Expected behavior
Focused/Highlighted pager page should be outlined with a border for accessibility.
Reproduction of the problem
Please see this exmaple: http://swimlane.github.io/ngx-datatable/#virtual-paging, a user is able to tab to a page number and then press enter to go there. However the page number container is not focused/highlighted.
What is the motivation / use case for changing the behavior?
This is needed from an Accessibility point of view.
Please tell us about your environment:
Windows 10

Table version:
14.0.0

Angular version:
Angular 7.1.3

Browser:
all

Language:
TypeScript 3.1.6

Hi, I am currently working on improving the accessibility of ceph-dashboard datatable component which is also affected by this issue. The pagination elements are not focusable. I would like to work on a fix


Clean up code

Remove extra new lines. Remove semicolon at the end of closing bracket.

Thanks for the attention.


investigate ffmpeg/ffmpeg-probe/vercel compatability

as mentioned in #14, I need to investigate how to get video dimensions/resolution server side from a url.
due to the varied nature of video codecs, this pretty much requires the use of ffmpeg.
there is a nodejs wrapper for it: https://github.com/fluent-ffmpeg/node-fluent-ffmpeg
the use of ffmpeg is likely going to involve some extra setup for server deployments, but this might help: https://www.npmjs.com/package/@ffprobe-installer/ffprobe
depending on how difficult installation is for users of this library and vercel deployment limits, this might actually be cause for creating 2 separate libraries, one that only supports images, and one that supports images+videos.

https://betterprogramming.pub/how-to-process-video-with-ffmpeg-and-nodejs-940a8e510791 useful article


aws-creds: default to a 30-second request timeout

This is technically a breaking change, but no (infinite) timeout is a bad default, and incentivises libraries to override the global timeout at all sorts of different values. We have been running with a 30-second timeout in production for more than a month, without any problem: in a healthy state, credentials requests return in milliseconds. That seems like a reasonable, if conservative, default.

Anything is better then Inf :)


Rebase Scash onto Bitcoin Core 26.1

Please describe the feature you'd like to see added.
Bitcoin Core 26.1 was released on 2 April 2024
https://bitcoincore.org/en/2024/04/02/release-26.1/
Is your feature related to a problem, if so please describe it.
No response
Describe the solution you'd like
No response
Describe any alternatives you've considered
No response
Please leave any additional context
No response

Closing. No action. Rebase onto 27.0 instead #13


log path configuration in EMBArk

Hi,
I would like to scan large bin files with EMBArk and the default 80GB disk space of kali is not enough to execute the test. First I just added a new partition but EMBArk was installed on the default /dev/sda1 partition and EMBArk does not support log parameter, it used the installation partition.
Now I have a separate /dev/sda3 and I installed EMBARk to this folder but in the future it would be great to install EMBArk to the default partition and if I would use the same -l option as EMBA offers I could put the logs and extracted items to a separate disk for huge binary scans.
If possible please look into the possibility of this.

We will not include the log path parameter in EMBArk. If you need more disk space you need to  mount a larger disk/partition to the EMBArk log directory. Do not forget to copy your current data to the new disk.


AsyncRedisStorage does not write to Redis

Hi, I'm using an async Httpx client with Hishel transport, that I create with such code:
transport = hishel.AsyncCacheTransport(
    transport=httpx.AsyncHTTPTransport(),
    storage=hishel.AsyncRedisStorage(
        client=get_redis_connection(),
        ttl=300,
    ),
    controller=hishel.Controller(
        cacheable_methods=["GET", "POST"],
        cacheable_status_codes=[200],
        allow_heuristics=False,
        clock=None,
        allow_stale=True,
        always_revalidate=False,
        force_cache=True,
        key_generator=custom_key_generator,  # Same func from docs
    )
)

I make requests using client looking at the state of my Redis instance at the same time, and can see no keys appearing.
However, I can see responses are returned from cache. response.extensions["from_cache"] is True.
Seems like Hishel falls back to RAM caching instead of using Redis for some reason.

Hi!
I can't reproduce the issue locally:(
My code:
import httpx
import hishel
import anyio

def get_redis_connection():
    import redis.asyncio as redis

    client = redis.Redis()
    return client

async def main():

    transport = hishel.AsyncCacheTransport(
        transport=httpx.AsyncHTTPTransport(),
        storage=hishel.AsyncRedisStorage(
            client=get_redis_connection(),
            ttl=300,
        ),
        controller=hishel.Controller(
            cacheable_methods=["GET", "POST"],
            cacheable_status_codes=[200],
            allow_heuristics=False,
            clock=None,
            allow_stale=True,
            always_revalidate=False,
            force_cache=True,
        )
    )

    async with httpx.AsyncClient(transport=transport) as client:
        response = await client.get("https://hishel.com")
        print(response.extensions["from_cache"])

anyio.run(main)

My redis response
<IP_ADDRESS>:6379> KEYS *
1) "41ebb4dd16761e94e2ee36b71e0d916e"

If I am not wrong, there is no any fall back logic in the storages.
Try something like this from your code
# get all keys
print(await transport._storage._client.keys("*"))

If it print keys, I guess you were connected to the wrong redis instance.


Find a better solution for InlinePanel template init scripts

While working through eslint and Pretter adoption, there are two template JS files that are not able to be formatted due to the way they are using Django template strings within the JS files
 wagtail/admin/templates/wagtailadmin/edit_handlers/inline_panel.js
 wagtail/contrib/search_promotions/templates/wagtailsearchpromotions/includes/searchpromotions_formset.js

It would be good to find a better way to do these inline panel JS injects.
Some options

Adding the script to the HTML file
Moving the init data to data attributes (and just a small init script is needed only)
Working around the template strings with putting content in comments or other JS strings, similar to wagtail/search/templates/wagtailsearch/queries/chooser_field.js
Using Telepath for the InlinePanel inits

This would avoid the need for these files to be in eslint ignore also.
Originally posted by @lb- in https://github.com/wagtail/wagtail/pull/7908#discussion_r798059655

@thibaudcolas here are two potential approaches

Just use a bit of comment syntax and string parsing to 'hide' template {{ usage

https://github.com/lb-/wagtail/commit/486b52d4ac48800ce153da1a618dda8fa0d9979f

Move most template based data to data-attributes on the .multiple ul in HTML and just make the two init scripts read that data, the original selector though still needs to use the template syntax

https://github.com/lb-/wagtail/commit/c406b5b059f57c17acce4ec5509da45e8f8429e8
This still needs to have the two JS files, but it looks possible to abstract this a bit further by moving the DOM element reading to the actual InlinePanel function (passing a queryselector string or a DOM element as the param instead of opts and handling both cases in the InlinePanel code.

Feel free to ignore for now or use if helpful, otherwise we can just address as a separate new issue.

https://github.com/wagtail/rfcs/pull/78 RFC 78 will give us a solid path forward here.

As of #8194 the inline_panel.js template code has now been moved into wagtail/admin/templates/wagtailadmin/panels/inline_panel.html alongside the corresponding HTML template code. It's still using the 'template code inside JS' antipattern, and it would be nice to eliminate this, but at this point it's more or less at parity with the numerous other components that do <script>initFoo(...)</script> (e.g. most things in admin/templates/wagtailadmin/widgets/).

This issue has been added to the Stimulus RFC project - the aim is to migrate InlinePanel to this new approach.

I've now started on the initial implementation of this for basic expanding formsets only. I'll update this issue to reflect a multi-step plan for this soon.
Additionally I've found that our current approach to modifying the delete widget can also be improved now that we have dropped support for older versions of Django.
Django 4.0 added support for deletion_widget / get_deletion_widget.

https://docs.djangoproject.com/en/5.0/releases/4.0/#forms
https://docs.djangoproject.com/en/5.0/topics/forms/formsets/#deletion-widget
https://code.djangoproject.com/ticket/32984

This issue has been re-written and the part one PR is up. https://github.com/wagtail/wagtail/pull/11633
Would love your feedback on either when you get the chance; @gasman / @thibaudcolas  / @laymonage


migrate frontend to docusaurus

Refs https://github.com/badges/shields/issues/7982
This PR is now ready for review.
As with https://github.com/badges/shields/pull/8966 the commit history for this isn't very useful. Sorry. If it is just too much of a mess, let me know and I will try to do a massive rebase/squash and clean it up a bit.
I've set up a review app at https://pr-9014-badges-shields.fly.dev/ which won't delete itself for the moment because we haven't merged https://github.com/badges/shields/pull/9069 yet.
I've been though all the comments. Anything that is resolved or hidden is now irrelevant. Anything still unresolved is still relevant. Note that I've spent so much time chatting away to myself in this PR that Github has started to hide bits of it.

Once we get this merged/deployed, I'll start writing up the next steps from this PR and #8966 into issues which we can hopefully tackle a bit more incrementally.
I'll need to remove test-frontend from the required checks in settings when we merge this.
I've attempted to give us some basically sensible content as an opening gambit, but we can always fiddle with content later. I'm mainly trying to get the tech bit right in this PR.

These lists probably are not complete. Also needs a general sweep. Grep for frontend, gatsby, etc
TODOs that need to happen in this PR:

Inline comments once https://github.com/badges/shields/pull/8966 is in
E2E tests
Update docs
Review ESLint config again. Any config specific to the old frontend we can ditch?

TODOs that I will punt to later:

Flag URL conflicts between badge server and frontend
CI automation to warn about swizzled components when upgrading docusaurus-theme-openapi
Bring back the blog
Triage https://github.com/badges/shields/issues?q=is%3Aopen+is%3Aissue+label%3Afrontend and close most of them

Socket flags a couple of possible issues to look into with dependencies introduced in this PR which are packages that use postinstall scripts. Having reviewed the scripts, I'm fine with them.

Have finally done a full pass through this and think it's in good shape. I don't have any blocking concerns nor issues, just a few thoughts and questions left inline.
There's only two things I'd like to give a spin/glance before moving ahead. I anticipate having time to do both this week, so I'd suggest we leave the remainder of the week for that, and then once that's done or if Sunday comes, I'd be good with resolving the conflicts and moving ahead.
Two things I'd still like to do:

Seeing the frontend live with these changes (the review app has been down for me ever since I first looked at this PR. that being said, I should be able to rebuild the app or fix that myself)
Pulling things down locally and launching the server to get a feel for the inner dev loop experience discussed above.

Finally, thanks again for taking this on. It's been a long standing desired and need, and was obviously a major, time consuming haul.

This review is getting pretty disjointed, so just to try and make it super-clear. Here's a list of links to the comments I've left in this pass:

https://github.com/badges/shields/pull/9014#discussion_r1225450812
https://github.com/badges/shields/pull/9014#discussion_r1225451196
https://github.com/badges/shields/pull/9014#discussion_r1225451360
https://github.com/badges/shields/pull/9014#discussion_r1225451667
https://github.com/badges/shields/pull/9014#discussion_r1225452261
https://github.com/badges/shields/pull/9014#discussion_r1225451909

I'd like to give a spin/glance before moving ahead.

To help out with this, I've merged all this week's package bumps and resolved all the conflicts. There is a review app up at https://pr-9014-badges-shields.fly.dev/
If it has deleted itself, you can re-deploy it

I think I'd ideally like to get this merged and deployed next week.
If you're able to find a few mins to have a poke about in the review app on Sunday that would be absolutely ideal :pray:

I'm on pretty pedestrian hardware and although my first npm start wasn't what I'd describe as snappy, I also don't think it was all that noticeably worse than my experience with gatsby.
I don't view impact on the inner dev loop as a deal breaker, whatsoever

Not sure if this is a quirk, bug, or pebcak, but any ideas what's happening with these seemingly duplicative Azure DevOps badge listings in the sidebar?

As compared to what we have today:

I feel like I may have seen this elsewhere too but didn't register it at the time while browsing

any ideas what's happening with these seemingly duplicative Azure DevOps badge listings

Yep, so this is something that we've touched on before
Definitely in https://github.com/badges/shields/issues/7982#issuecomment-1346871332
and probably somewhere in the review for https://github.com/badges/shields/pull/8966
but worth a recap.
In OpenAPI, query string params can be optional but there is no such thing as an optional path (positional) parameter, so you can't do
{
  "name": "branch",
  "in": "path",
  "required": false,  // nope
  "description": "Branch",
  "schema": { "type": "string" }
}

This means we need to generate a separate page for every with/without optional param variant.
If we haven't already got 2 separate examples for each with/without optional route param variant, I'm creating the variants using https://github.com/badges/shields/blob/2651e5fe87d92e0b344e3f0ca41dae0b3f9a9502/core/base-service/openapi.js#L91-L119 but I'm just doubling up the existing title for now. It is not perfect, but it is workable to get this part of the migration done.
So the difference between

https://pr-9014-badges-shields.fly.dev/badges/azure-dev-ops-builds-job
https://pr-9014-badges-shields.fly.dev/badges/azure-dev-ops-builds-job-1

is one has a branch param, and one doesn't.
Also, separately from that, we've also got a bunch of places where we already have duplicated titles in the existing examples e.g:

which we also replicate on the new site.
I am very aware that having multiple menu items with the same title is unhelpful for discovery and navigation now that the only thing the user can see is the title, but one of the ways I'm trying to avoid boiling the whole ocean at once is by separating platform and content a bit. As an opening gambit to get the "platform" bit of the migration done, I'm comfortable if every bit of content is not perfect to start with.
Once we move to defining the open api definitions on the service classes directly, there's a lot of content improvements I'd like to make (once we've got the right structure in place, it will be possible to do this in lots of smaller simpler "improve docs for service X" PRs rather than mixing it in with the platform migration) and sorting out duplicate titles is going to be one of those jobs.
Maybe once we get to a point where each one has a unique title, we can add a check somewhere (maybe the service loader) to ensure all the titles are unique.

one of the ways I'm trying to avoid boiling the whole ocean at once is by separating platform and content a bit. As an opening gambit to get the "platform" bit of the migration done, I'm comfortable if every bit of content is not perfect to start with.

Believe I follow the prior portion of the response explaining the presence of the duplicative titles, and at least AIUI, the same underlying reasoning also explains the absence of some titles (and corresponding different badges).
I think the platform -> content sequencing is a reasonable approach, although along this aspect :point_down:

Yep, so this is something that we've touched on before

I'm certainly having trouble maintaining a mental model of all these aspects, though admittedly the size of changes and the delta between the windows I'm actively thinking about it are both certainly aggravating factors.
Do we have anything like a high level tracking issue with a succinct enumeration of some of these content-related items we're aware of and deferring to follow up work? (and apologies if we do, my lack of awareness of such an issue speaks back to that failing mental model :brain:).
If not, do you think it would be reasonable to pull something like that together? I know you've probably got such a list in your head and I'm sure the items that would constitute such a list are covered within various Issue and PR discussions, but I feel like having things captured in one place would make them more easily consumable and trackable

Yep so the top post of https://github.com/badges/shields/pull/8966 starting from

Next steps from here (may not be exhaustive) are something like:
[bullets points]

was my last attempt to do that and is still broadly accurate. Obviously this PR is the first thing in that list.
There are probably some other things that do exist in my head or as bits where I've said "This is a bit crap - we should make it better" somewhere in a diff comment on this PR or on https://github.com/badges/shields/pull/8966 at the moment that need extracting into issues.
One of the next things I want to do after we merge this is go through https://github.com/badges/shields/issues?q=is%3Aopen+is%3Aissue+label%3Afrontend work out what (if any of it) is still relevant, but probably close all/most of them. Then write up a bunch of new frontend issues for the next steps on this with some proper details. If you want though I can try to pull all that together into a rough bullet list here tomorrow evening before we merge this.

today is the day


RN to upgrade to 0.18 icon is not shown

I'm on 0.19.0 and on Android the icons do not display either.

Same issue here.

My RN version is 0.19.0.
I do all the steps as the readme guides except step3 include fonts
I do it in my MainActivity
public class MainActivity extends ReactActivity {
    private CodePush _codePush;

    /**
     * Returns the name of the main component registered from JavaScript.
     * This is used to schedule rendering of the component.
     */
    @Override
    protected String getJSBundleFile() {
        return this._codePush.getBundleUrl("index.android.bundle");
    }

    @Override
    protected String getMainComponentName() {
        return "GitFeed";
    }

    /**
     * Returns whether dev mode should be enabled.
     * This enables e.g. the dev menu.
     */
    @Override
    protected boolean getUseDeveloperSupport() {
        return BuildConfig.DEBUG;
    }

    /**
     * A list of packages used by the app. If the app uses additional views
     * or modules besides the default ones, add more packages here.
     */
    @Override
    protected List<ReactPackage> getPackages() {
        // 4. Instantiate an instance of the CodePush runtime, using the right deployment key

        // 5. Add the CodePush package to the list of existing packages
        return Arrays.<ReactPackage>asList(
                new MainReactPackage(), new ReactNativeIcons());
    }
}

Same issue here,Seeking solutions

+1

+1, RN 0.19.0

I do not believe this is going to be fixed. Please note this message from the home page of this project:
WARNING: Support for this library is being discontinued, I highly recommend using https://github.com/oblador/react-native-vector-icons instead as its more fully featured.
In order to upgrade to RN 0.19, I had to switch my icons over to react-native-vector-icons. It wasn't too bad. Good luck!

That is correct, I recommend migrating over ASAP.

Closing this as support for this library is being discontinued, I highly recommend using https://github.com/oblador/react-native-vector-icons instead as its more fully featured, I've added a warning to the Readme about this as well.


Optimize handling of null values in load_data_lookup

Whenever we load a registered dataset with a load_data_lookup.parquet we have to filter out rows with NULL data id values. Those are needed to validate intentionally excluded dimension combinations during dataset registration. Per discussion with @lixiliu we could do two things to make this better:

At registration time, after validation and before we copy the file to the registry, strip the NULLs from the dataframe and write them to a secondary file. That secondary file would not be used by dsgrid; it would only provide a way to retrieve the original dataset.
Allow the dataset contributor to provide the secondary file during registration.

No longer relevant/correct


Microcharts breaks on iOS 13.3.1

After updating to iOS 13.3.1, microcharts on my application stopped showing. I tested this with another phone as well, and the iOS update broke it on that phone too.

I'm running it inside of iOS 13.3. This is my first time to use the library but the basic example works for me. Is it still not working for you?

I have updated to iOS 13.3.1, since then I have performed the same issue.

Sethom it works in 13.3, but not 13.3.1 for me

did you get any solution? I am facing the same problem.

I have not found any solution

I'm experiencing weird behaviour because the chart is showing properly in simulator (iOS 14.0) but it doesn't show anything on my device (iOS 13.3), maybe it is the same issue. I'll try to update to 14.1 on my device and maybe it will work, I will add the result later

So it apparently works after the update to iOS 13.4.1.

@hunterbrodie @triskacik @yesmeco @sethom
I believe the issues you guys are experiencing are likely linked to the "device specific builds" setting, see my bug report here: https://github.com/dotnet-ad/Microcharts/issues/217

I've tried what @wolf81 suggested but no success.
The application crashes when start with this message in Visual Studio:
2021-06-11 16:56:09.320 Xamarin.PreBuilt.iOS[11880:738685] Xamarin.Forms AppDelegate name: AppDelegate
=================================================================
Native Crash Reporting
Got a segv while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
Native stacktrace:
0x104410120 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : mono_dump_native_crash_info
0x104406cbc - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : mono_handle_native_crash

0x104413a60 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : mono_sigsegv_signal_handler_debug
0x1ddde829c - /usr/lib/system/libsystem_platform.dylib : <redacted>
0x19238c5ec - /usr/lib/system/libdyld.dylib : <redacted>
0x19237c008 - /usr/lib/system/libdyld.dylib : <redacted>
0x19238c418 - /usr/lib/system/libdyld.dylib : <redacted>
0x19237c948 - /usr/lib/system/libdyld.dylib : <redacted>
0x19238cf30 - /usr/lib/system/libdyld.dylib : <redacted>
0x19238c9c0 - /usr/lib/system/libdyld.dylib : <redacted>
0x19238e928 - /usr/lib/system/libdyld.dylib : <redacted>
0x19237fecc - /usr/lib/system/libdyld.dylib : <redacted>
0x1045bc970 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : do_icall

0x1045bb010 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : do_icall_wrapper
0x1045b1a8c - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : interp_exec_method_full

0x1045afeb0 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : interp_runtime_invoke
0x104416d3c - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : mono_jit_runtime_invoke
0x1044c52c0 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : mono_runtime_invoke_checked
0x1044ca564 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : mono_runtime_exec_main_checked
0x1043fb8f4 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : mono_jit_exec
0x1045ad984 - /private/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : xamarin_main
0x1043c3c34 - /privat

e/var/containers/Bundle/Application/DFE6208E-FDDF-4113-92EA-8BF3DDED3841/Qiagen.QuantiFERON.iOS.app/Xamarin.PreBuilt.iOS : main
0x19237acf8 - /usr/lib/system/libdyld.dylib :
=================================================================
Basic Fault Address Reporting
Memory around native instruction pointer (0x10e59b11c):0x10e59b10c  c3 bc 00 94 e0 03 13 aa 5f 00 03 94 20 00 20 d4  ........_... . .
0x10e59b11c  f4 4f be a9 fd 7b 01 a9 fd 43 00 91 73 09 00 b0  .O...
{...C..s...
0x10e59b12c  73 82 2b 91 61 08 00 b0 21 38 2f 91 e0 03 13 aa  s.+.a...!8
/.....
0x10e59b13c  02 00 ae 52 63 bc 00 94 60 82 01 91 ce bc 00 94  ...Rc...`.......
=================================================================
Managed Stacktrace:
  at <unknown> <0xffffffff>
  at ObjCRuntime.Dlfcn:_dlopen <0x00026>
  at ObjCRuntime.Dlfcn:dlopen <0x00010>
  at Xamarin.PreBuilt.iOS.Applications:LoadFrameworks <0x0009e>
  at Xamarin.PreBuilt.iOS.Applications:Main <0x00202>
  at <Module>:runtime_invoke_direct_void_string[] <0x00092>

=================================================================
Thread started:  #4
Thread started:  #5
Thread started:  #6
Thread started:  #7
The app has been terminated.

Are you sure it's the library? Have you removed it?

Yes by removing the library I do not have any problems at all

Any update or workarounds for this? Android emulator runs fine but on IOS the app does not start. I get the same error as Rabosa616.

if I had a good test case brought to me someone could try to reproduce it.

Ok I believe it has something to do with the latest IOS version (14.6). I created a new shell project and just implemented the chart example.


docs: add keepalive documentation

It adds documentation about how to enable keepalive traffic on SSH services.

That documentation update was pretty useful to read (even if it's not merged yet), thanks @kuisathaverat !


Farmhash-modern throws webassembly error in Nextjs

[REQUIRED] Step 2: Describe your environment

Operating System version: Linux Ubuntu 24.04
Firebase Admin SDK version: v12.2.0
Firebase Product: Admin auth
Node.js version: v20.11.1
NPM version: v10.2.4

[REQUIRED] Step 3: Describe the problem
I'm trying to configure firebase-admin SDK on my nextjs + TS project. Whenever i try to invoke any SDK function, i get a webAssembly error. In my case, i am trying to configure a middleware for the server side api, and when i call the verifyIdToken method it throws the error. I'll paste it below, i also noticed that the affected dependency farmhash-modern was just replaced in this version of firebase.
Steps to reproduce:
The error occured when i called the verifyIdToken() method in my middleware.ts file.
Relevant Code:
This is the middleware file.
import { auth } from "./lib/config/firebaseConfig";
import { NextResponse } from "next/server";
import { NextRequest } from "next/server";

interface ExtendedNextRequest extends NextRequest {
  uid?: string;
}

export async function middleware(req: ExtendedNextRequest, res: NextResponse) {
  try {
    let token = req.headers.get("Authorization");
    if (!token)
      return NextResponse.json({ message: "Access Denied" }, { status: 403 });
    if (token.startsWith("Bearer ")) {
      token = token.split(" ")[1];
    }

    let decodedToken = await auth.verifyIdToken(token);
    let uid = decodedToken.uid;
    req.uid = uid;

    return NextResponse.next();
  } catch (error: any) {
    console.log(error.errorInfo);
    return NextResponse.json({ message: "Invalid Token" }, { status: 401 });
  }
}

This is the error output
⨯ ./node_modules/farmhash-modern/bin/bundler/farmhash_modern_bg.wasm
Module parse failed: Unexpected character '' (1:0)
The module seem to be a WebAssembly module, but module is not flagged as WebAssembly module for webpack.
BREAKING CHANGE: Since webpack 5 WebAssembly is not enabled by default and flagged as experimental feature.
You need to enable one of the WebAssembly experiments via 'experiments.asyncWebAssembly: true' (based on async modules) or 'experiments.syncWebAssembly: true' (like webpack 4, deprecated).
For files that transpile to WebAssembly, make sure to set the module type in the 'module.rules' section of the config (e. g. 'type: "webassembly/async"').
(Source code omitted for this binary file)

Import trace for requested module:
./node_modules/farmhash-modern/bin/bundler/farmhash_modern_bg.wasm
./node_modules/farmhash-modern/bin/bundler/farmhash_modern.js
./node_modules/farmhash-modern/lib/browser.js
./node_modules/firebase-admin/lib/remote-config/condition-evaluator-internal.js
./node_modules/firebase-admin/lib/remote-config/remote-config.js
./node_modules/firebase-admin/lib/app/firebase-namespace.js
./node_modules/firebase-admin/lib/default-namespace.js
./node_modules/firebase-admin/lib/index.js
./lib/config/firebaseConfig.ts

This question is also on stackoverflow

Does configuring webpack by setting asyncWebAssembly to true in your next.config.js work for you?
Something similar to the following:
module.exports = {
  webpack: (config, { buildId, dev, isServer, defaultLoaders, webpack }) => {
    config.experiments = {
      asyncWebAssembly: true,
    };
    return config;
  },
};

I'm getting the same issue.. This code does seem to "fix" the issue, but src/middleware is now failing (hanging) to compile.

Does configuring webpack by setting asyncWebAssembly to true in your next.config.js work for you? Something similar to the following:
module.exports = {
  webpack: (config, { buildId, dev, isServer, defaultLoaders, webpack }) => {
    config.experiments = {
      asyncWebAssembly: true,
    };
    return config;
  },
};

Experiencing the same issue.

Downgrading to 12.0.0 worked for me as well.

Does configuring webpack by setting asyncWebAssembly to true in your next.config.js work for you?
Something similar to the following:
module.exports = {
  webpack: (config, { buildId, dev, isServer, defaultLoaders, webpack }) => {
    config.experiments = {
      asyncWebAssembly: true,
    };
    return config;
  },
};

I also tried this, but as @Keegan-lee said src/middleware doesn't compile. It displays the compiling middleware message and stays there forever.

I am experiencing the same exact issue.
Adding the asyncWebAssembly flag indeed causes an indefinite compiling for middleware.
Switching back to ^12.0.0 doesn't work either.
Workaround
For now, I have moved all the pages that needed that middleware into a specific route (can also be an anonymous route).
I am using the layout file as a kind of middleware: before displaying any data it runs a server action, where the issue is not yielded.
This workaround produces an error when hot reloading, but seems to work fine otherwise.
Also, using ^12.0.0 issued an error regarding the usage of the os module, which may be a clue on where to debug this issue.

Am having the same problem here, searched the best i could and it seems that there is no direct solution yet...

Am having the same problem here, searched the best i could and it seems that there is no direct solution yet...
The best that i had saw is utilize another lib called next-firebase-auth-edge (https://github.com/awinogrodzki/next-firebase-auth-edge)

I am guessing that Firebase Auth cannot be used on Edge runtime due to the need for some Node-only modules.
FWIW I suggest to use this library with extreme caution due to how it manipulates and generates tokens and other security-related Firebase Auth features.

Hey Guys,
I'm having the same issue, but I completely replaced auth part of firebase-admin with next-firebase-auth-edge, only using admin part and firestore, should I still be getting this error?

Hey Guys, I'm having the same issue, but I completely replaced auth part of firebase-admin with next-firebase-auth-edge, only using admin part and firestore, should I still be getting this error?

You shouldn’t get the error, the package should be able to smoothly run on all NextJS environments.
I however renew my suggestion of being cautious when using the package

Hey Guys, I'm having the same issue, but I completely replaced auth part of firebase-admin with next-firebase-auth-edge, only using admin part and firestore, should I still be getting this error?

You shouldn’t get the error, the package should be able to smoothly run on all NextJS environments.
I however renew my suggestion of being cautious when using the package

Are you sure? I see plenty of people complaining about the same thing (that it won't work when using middleware). I'm using firestore and admin (but not auth) from firebase-admin and it leads to that error.

Hey Guys, I'm having the same issue, but I completely replaced auth part of firebase-admin with next-firebase-auth-edge, only using admin part and firestore, should I still be getting this error?

You shouldn’t get the error, the package should be able to smoothly run on all NextJS environments.
I however renew my suggestion of being cautious when using the package

Are you sure? I see plenty of people complaining about the same thing (that it won't work when using middleware). I'm using firestore and admin (but not auth) from firebase-admin and it leads to that error.

How are you importing the library?
Also, yes I am sure, as per the documentation of the package:
The official firebase-admin library depends heavily on Node.js’s internal crypto library, which isn’t available in [Next.js Edge Runtime](https://nextjs.org/docs/api-reference/edge-runtime).

This library solves that problem by handling the creation and verification of [Custom ID Tokens](https://firebase.google.com/docs/auth/admin/verify-id-tokens) using the Web Crypto API, which works in Edge runtimes

updated my response above.

As pointed out earlier, Firebase seems to work only in the Node server.
My workaround was to create an API endpoint with call API/session/route and export a response as JSON from the @auth session, then call the auth API in the middleware.
This works well for me, but I'm unsure about its security implications.
// /api/auth/session
import { auth } from "@/auth"
export async function GET(_request: Request){
const session = await auth()
if(!session) return Response.json(null, { status: 401 })
return new Response(JSON.stringify(session), {
status: 200,
})
}
// middleware.ts
export async function middleware(_request: NextRequest) {
const res = await fetch(new URL('/api/auth/session', _request.url), {
method: 'GET',
credentials: 'include',
headers: {
'Content-Type': 'application/json',
},
})
const schema = z.custom<Session | null>()
const isAuthenticated = schema.parse(await res.json())
console.log(isAuthenticated)
const respond = NextResponse.next()
return respond
}

First of all, I suggest that you all try to format the code in the thread correctly. You can do so via backticks.
Also, try to keep the thread clean! Don't turn it into a StackOverflow question! :D
@hassanzadeh I can't test your code right now, but the issue might lie in the fact that you are still using firebase-admin within firebase-init.ts, which you are then importing in your middleware.
@brouza Seems like an okay workaround as far as I'm concerned; you could even try using a server action to abstract away the REST paradigm. I would at least try to secure the endpoint, however, even though it's a server-to-server communication. There might be more security implications as well.
I am as well awaiting an official response regarding this issue.

Thanks @nicolopadovan ,
I updated my response to fix the backticks issue.
I'm not sure I understood your point, I'm importing firebase-init, but all I'm using there is admin and db, but not auth, is that a problem?

As pointed out earlier, Firebase seems to work only in the Node server. My workaround was to create an API endpoint with call API/session/route and export a response as JSON from the @auth session, then call the auth API in the middleware. This works well for me, but I'm unsure about its security implications.
// /api/auth/session import { auth } from "@/auth"
export async function GET(_request: Request){ const session = await auth() if(!session) return Response.json(null, { status: 401 }) return new Response(JSON.stringify(session), { status: 200, }) }
// middleware.ts export async function middleware(_request: NextRequest) { const res = await fetch(new URL('/api/auth/session', _request.url), { method: 'GET', credentials: 'include', headers: { 'Content-Type': 'application/json', }, }) const schema = z.custom<Session | null>() const isAuthenticated = schema.parse(await res.json())
console.log(isAuthenticated)
const respond = NextResponse.next()
return respond }

Thanks, I first need to know why my current code is not working especially that I'm not using firebase-admin auht at all.

Ok, I think you are right.
Thanks

Use webassembly in middlewares is not common practice. Using native code means you are applying a complex solution to improve efficiency. Middleware in Next.js is designed for handling requests and responses, but your approach may be misusing it.
In the case of Firebase, it's best to separate the methods into distinct files, such as firebaseServerSide.ts and firebaseClientSide.ts. Again, middleware in Next.js does not support running WebAssembly, and it’s generally a bad practice to run this type of code there (since firebase-admin uses WebAssembly).
My recommendation is to enhance your login and authentication processes. Consider implementing straightforward checks, such as validating tokens with JWT or other libraries, or even using libraries like next-auth for this purpose.
Another important observation is that if you are using firebase-admin on the client side(or import methods that use firebase-admin), it is considered a bad practice and poses significant security risks, which will likely lead to similar problems.

Use webassembly in middlewares is not common practice. Using native code means you are applying a complex solution to improve efficiency. Middleware in Next.js is designed for handling requests and responses, but your approach may be misusing it.
In the case of Firebase, it's best to separate the methods into distinct files, such as firebaseServerSide.ts and firebaseClientSide.ts. Again, middleware in Next.js does not support running WebAssembly, and it’s generally a bad practice to run this type of code there (since firebase-admin uses WebAssembly).
My recommendation is to enhance your login and authentication processes. Consider implementing straightforward checks, such as validating tokens with JWT or other libraries, or even using libraries like next-auth for this purpose.
Another important observation is that if you are using firebase-admin on the client side(or import methods that use firebase-admin), it is considered a bad practice and poses significant security risks, which will likely lead to similar problems.

Thanks for the insight. I did some research and understand the issue better.

Same error when using 12.6.0

We removed the dependency on farmhash-modern in the latest release v13. This should be now fixed in the latest release. Let us know if you are still running into issues. Thanks!
https://github.com/firebase/firebase-admin-node/pull/2760


[Question] Secure way to persist keys on Azure

I would like to have some guidance for securely manage DataProtection on Azure.
1/ Persistence
For now, there is three ways to persist keys on Azure.

Into the instance-shared file storage
Into Redis database
Into an Azure blob storage

Are those implementations secured ?
Are those implementations secured by default ?
I imagine that each implementation require to be secured correctly. Is there any guidance ?
Is KeyVault a valuable option ?
Related : #92
2/ Key protection

With DPAPI/DPAPI NG : Not on Azure
With a certificate

Is KeyVault a valuable option ?
Related : #178

By default any shared storage is not encrypted. You need to layer x509 on top of it. You can use a certificate if, and only if, you target .NET Framework, rather than .NET Core, which doesn't have the right classes yet. That would be the safest option, however not that on azure web apps you cannot upload a certificate to use unless you're on the higher SKUs.
We have a branch for keyvault to protect the keyring, but when you rotate the keyvault master key it will no longer be accessible, so all data protection keys protected with it suddenly can't load (unlike with certificates where we can still decrypt, just not encrypt new items). Until that changes, and we've asked, we feel pushing the KeyVault package out could result in data loss.

If I resume,  Azure web apps key ring may be secured on any shared storage, if I am capable to use certificates.
Certificates usage require adequate SKU & .Net Framework.
Any visibily on .Net core required class? I had an issue on trying to build a client certificate authentication middleware.
With KeyVault, if nobody rotate the keys, is there any matter?
Or shouldn't we store the keys as secret instead of keys?

You should always rotate keys, it's just best practice. We don't store the keys themselves as secrets, as the API for reading secrets has way way too much overhead.

We've been working with the KeyVault team, and finally hope to have an answer for our 2.0 time frame.

This issue was moved to aspnet/Home#2519


[Feature Request] Add intermediate  level quizes seperate quiz page

🚀 Feature Request
Is your feature request related to a problem? Please describe.
Add intermediate  level quizes seperate quiz page
Describe the solution you'd like
Add intermediate  level quizes seperate quiz page
Describe alternatives you've considered
Add intermediate  level quizes seperate quiz page
Additional context
Add intermediate  level quizes seperate quiz page
Would you like to work on this feature?

[x] Yes
[ ] No

Please don't create spam. We need only four issues open, not a large number. If you want to work on more issues, you can try other open source projects. A large number of issues in a single project can create problems for you and for us.


cut extra renders for performance

Hi,
I ran a react optimization tool called why-did-you-update to find reasons why items render on every little interaction when they shouldn't. This tool runs deep equality for the changing props and state to figure out where props or state differ in reference but not in content. I discovered hundreds of extra render and cutting them is not very hard to fix. Fixes mostly are just changing some components to pure components or prevent next state with deep equality to set the upper-level component's state which causes the whole component to rerender.

hi @Ilaiwi ill try to review this stuff this week or next. I'm really slammed at work 😄


Focus doesn't fully switch to VSCode if right-clicking in the file explorer tab. Enables file renaming but input still goes to the other focused window

VS Code Version: Version: 1.55.2
OS Version: macOs Big Sur Version 11.3

Steps to Reproduce:

Open VSCode
Open any other window
Switch focus to the other window by clicking on it
While focused on the other window, right-click on any file or folder in the explorer and select "Rename"
The focus seems to be on the file explorer and the UI enables file renaming, but if you try to type anything your input will remain on the other window, making it impossible to rename the file.

As it is not always obvious where the focus is, it leads to mistakes such as typing in the terminal, hitting enter and then realizing you didn't rename the file.
P.S.: It is not specific to this version of Big Sur as it is happening ever since I switch to a mac mini m1 in January. Not sure if this is true with versions of macOs anterior to Big Sur though.

Does this issue occur when all extensions are disabled?: Yes

This is a long standing electron issue. I know there is a duplicate however I do not know which issue it is.
If you want to find the dupliacte I suggest you search through our exisitng issues. Thanks

I thought it might be, but I couldn't find a duplicate... Thanks for the quick response anyway!


statefulset create-yaml error

I updated create-yaml to return "Error loading schema for " so the whole page doesn't break if part of it fails to load:

This will allow the Statefulset forms to load correctly #921 but doesn't address whatever underlying issue there is with the schema.

I opened a new issue for the error part to investigate further: https://github.com/rancher/dashboard/issues/1336


Excuse me, are the initial weights of features all 0?

Hello. I did not see the ocp_hermes.ini file initializing the weights. Are the initial weights of features all 0?

Hi @szuhzw yes, the weights are initialized to zero. See inc/perc_pred.h:80.
Please create a post in the discussion section of the repository (https://github.com/CMU-SAFARI/Hermes/discussions) for further questions.


How to select for a drop-down box with attribute span - pending replication

The drop-down selection box of the website is a span, which cannot be selected when using select

Do you have a sample script that can run that that website? So that other folks here can test out?
span shouldn't be a problem, the logic for the select() function checks for child elements of a parent element, without restriction on the type of element. If the website is not publicly accessible, you can try automate clicking on it first, then click on the option you want.

import rpa as r
r.init(chrome_browser=True)
r.url('https://ant.design/components/select-cn/')
r.select('//*[@id="components-select-demo-basic"]/section[1]/div[1]/div/span[2]', 'Jack')

import rpa as r
r.init(chrome_browser=True)
r.url('https://ant.design/components/select-cn/')
r.select('//*[@id="components-select-demo-basic"]/section[1]/div[1]/div/span[2]', 'Jack')

Like this, I can't get him to pick Jack, is there something wrong with the way I use it?

This dropdown looks like not a standard dropdown box. There are not child elements under it even when clicked on -

In that case you can do that in 2 clicks, first click on the dropdown, then click on the option. Both XPath identifiers below can be found by right-clicking and inspecting on the element. There is probably nicer looking XPaths that you can rewrite to. For eg the option can be clicked with - r.click('//*[@class="ant-select-item-option-content" and text()="Jack"]')
r.click('//*[@id="components-select-demo-basic"]/section[1]/div[1]/div/span[2]')
r.click('/html/body/div[5]/div/div/div/div[2]/div[1]/div/div/div[1]')

Ok brother, thank you for your detailed answer, I think I already know how to get the value, I will close this issue


Fix missing = in environment variable example

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[ ] The title, template, and date` are all set
[ ] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[ ] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[ ] Has passed bart check
[ ] Has run npm run build-index
[ ] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
[ ] Headings are using Title Case
[ ] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[ ] Have tested with npm run test and resolved all errors

Preview workflow failure is a known issue and can be ignored - looks like preview does not yet play nicely with the typical fork-based GH workflow, only with branches created directly in the main repo.


Feature/add pg for production

Add pg gem for production

@fusion94 Hi there!.
There is some way to know if you are going to continue maintaining this repo?... I see a few open PR's... hope we can have an answer soon :+1: :beers:


nimble install nimwc fails (4.0.5)

When running nimble install locally from a git clone there's no problem, but when running nimble install and fetching through Nimble install fails:
Installing<EMAIL_ADDRESS>   Building nimwc/nimwc using c backend
    Prompt: Build failed for<EMAIL_ADDRESS>would you like to try installing 'nimwc@#head' (latest unstable)? [y/N]

https://github.com/ThomasTJdev/nim_websitecreator/blob/master/nimwc.nim#L87
Fails to read the Version from the *.nimble file, because nimble install seems to delete it ?.


Remove print statements

Print statements in the library are not very helpful, and you can always add them to your code according to your needs. So I suggest to drop them.

+1

Thanks!

+1 Thanks @emrekyv


add NCBI downloader

Missed one thing - can you add a test file that at least imports it and runs a noop test so it's included in the coverage info

In the future we might want to add something that doesn't do the download if the gene ID already exists or something to speed up updates, but we can add that later


connector incompatible with alternate current

Mod Name
alternate current
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/alternate-current
Describe the bug
crash at the startup
Steps to reproduce

have ffapi, connector, atlernate current
run the game
and he crash

Logs
https://pastebin.com/1EPcT4c1
Additional context

Alternate Current provides an invalid forge modid (alternate-current). This is an issue with the mod itself, as it happens without connector, too. See https://github.com/SpaceWalkerRS/alternate-current/issues/30


Change all spring related modules' artifact id to spring-cloud-azure-xxx

Parent task: https://github.com/Azure/azure-sdk-for-java/issues/23925
Design doc: https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Cloud-Azure-design#312-artifact-id

Hi, @saragluna .
FYI:

I created this issue.
Now this issue does not have assignee.

Closed in #24719.


UUID not being auto generated

I'm using the ecto from the latest master and I'm trying to get UUIDs to auto generate before being inserted to Postgres, but I don't see the id being inserted.
Here's my model, am I missing something or is this a bug?
defmodule FeedService.Feed do
  use FeedService.Web, :model

  schema "feeds" do
    field :user_id, :string
    field :name, :string
    field :filters, :map
    timestamps
  end

  @primary_key {:id, :binary_id, autogenerate: true}
  @required_fields ~w(user_id name)
  @optional_fields ~w(filters)

  @doc """
  Creates a changeset based on the `model` and `params`.

  If `params` are nil, an invalid changeset is returned
  with no validation performed.
  """
  def changeset(model, params \\ :empty) do
    model
    |> cast(params, @required_fields, @optional_fields)
  end
end

[info] POST /feeds
[info] Processing by FeedService.FeedController.create/2
  Parameters: %{"feed" => %{"filters" => %{"foo_id" => ["324"], "bar_id" => ["152"]}, "name" => "Test", "user_id" => "1723423"}, "format" => "json"}
  Pipelines: [:api]
[debug] BEGIN [] OK query=0.3ms
[debug] INSERT INTO "feeds" ("filters", "inserted_at", "name", "updated_at", "user_id") VALUES ($1, $2, $3, $4, $5) RETURNING "id" [%{"foo_id" => ["324"], "bar_id" => ["152"]}, {{2015, 6, 26}, {17, 50, 11, 0}}, "Test", {{2015, 6, 26}, {17, 50, 11, 0}}, "1723423"] ERROR query=0.4ms
[debug] ROLLBACK [] OK query=0.2ms
[info] Sent 500 in 21ms
[error] #PID<0.975.0> running FeedService.Endpoint terminated
Server: localhost:4000 (http)
Request: POST /feeds
** (exit) an exception was raised:
    ** (Postgrex.Error) ERROR (not_null_violation): null value in column "id" violates not-null constraint
        (ecto) lib/ecto/adapters/sql.ex:184: Ecto.Adapters.SQL.query/4
        (ecto) lib/ecto/adapters/sql.ex:475: Ecto.Adapters.SQL.model/5
        (ecto) lib/ecto/repo/model.ex:52: anonymous fn/10 in Ecto.Repo.Model.insert!/4
        (ecto) lib/ecto/adapters/sql.ex:548: Ecto.Adapters.SQL.transaction/8
        (ecto) lib/ecto/adapters/pool.ex:414: Ecto.Adapters.Pool.do_transaction/4
        (ecto) lib/ecto/adapters/pool.ex:400: Ecto.Adapters.Pool.transaction/5
        (ecto) lib/ecto/adapters/sql.ex:524: Ecto.Adapters.SQL.transaction/3
        (ecto) lib/ecto/repo/model.ex:233: Ecto.Repo.Model.with_transactions_if_callbacks/6

You need to define @primary_key before your schema block. Elixir is lexical, so the order statements like import, alias, and attributes are defined often matter.

Got it, thanks!


Add Enterprise Hub Serverless API Notebook

What does this PR do?

Adds the Serverless API notebook for Enterprise Hub section
Who can review?
@MoritzLaurer @merveenoyan

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@merveenoyan @MoritzLaurer
This PR is ready for review, however the only thing that would hold up merging is that there seems to be an issue with suno/bark behind the Inference API. Might make sense to hold off until that is fixed before merging.
One other quick question - anyone know of a way to get the audio widget to be displayed / useable in section: "4. Generating Speech from Text"?
Thanks in advance for the review!!

Great recipe @andrewrreed ! Particularly cool how the outputs from the different APIs are inputs for the next API!
I've left a few additional comments.

Great TIP :)

View entire conversation on ReviewNB

Good call - I added this language that's hopefully not to overwhelming for users: Next, you'll need to create a [User Access Token](https://huggingface.co/docs/hub/security-tokens). A token with read or write permissions will work, however, we highly encourage the use of fine-grained tokens. For this notebook, you'll need a fine-grained token with Inference > Make calls to the serverless Inference API permissions.

View entire conversation on ReviewNB

It's my savior with VSCode notebooks :)

View entire conversation on ReviewNB

Just too subtle :)

View entire conversation on ReviewNB

Good call!

View entire conversation on ReviewNB

Interesting, it renders fine here... I guess it's just a limitation of our docs builder. I'm going to look into it a bit further.

View entire conversation on ReviewNB

The motivation for including this was to show the simplicity before introducing the client which abstracts things away. I think I'll leave it, but take Moritz's advice and convert to Python requests rather than curl

View entire conversation on ReviewNB

Yes, this is a good call. I swapped out curl for requests

View entire conversation on ReviewNB

I'd also probably slightly rephrase the sentence on 500 000 being available in the very beginningReplaced 500k with "thousands" that explain how the serverless API works in the backendI do have some language just after the section that explains it. The goal was to introduce the simplicity and then explain how it worked. But I agree that adding some info about list_deployed_models() is a good idea. Will add that here!

View entire conversation on ReviewNB

While creating the dedicated endpoint notebook, I noticed that fine-grained token access to serverless API calls alone is not enough, but the fine-grained token also needs access to the model repositories for downloading the tokenizer/processor. In your case that's llama-3 and idefics2 I think. Maybe add a note on this to avoid people being confused when they cannot download the tokenizer.
I might actually recommend using a read-only token for quick experimentation, otherwise users need to add each new model to their fine-grained token permissions where they need to download a tokenizer/processor. The fine-grained token should then be used in production. WDYT?

Great catch @MoritzLaurer - I just pushed a commit to add some language on this

I think this is all ready to go now - feel free to merge @MoritzLaurer @merveenoyan @stevhliu!


Move element rendering to JavaScript

Currently all elements are rendered server side using Pode view files, and all output actions are rendered client side using JavaScript. This exhibits an issue with limited element support in Tables, and stops the ability to render new elements on the page on-the-fly.
The plan here is to move all of the Pode view files into client side JavaScript, allowing Tables to support all elements, and to be able to create elements on-the-fly.
I've been testing this one over the few days, and it works as expected. The plan is:

Move all Pode view files into JavaScript to allow client side rendering
The existing index.pode view will still render the sidebar and navigation, the body will be async
A new Page route for /content. which will be called on page load to render the elements
JavaScript classes should be utilised with a factory pattern around output actions
The above classes should be extendable and override-able so people can create custom elements/actions

With the work done at the moment we could be looking at a Pode.Web v1.0.0 release. With all the element rendering now being far more dynamic it renders the Out-PodeWebTable etc. functions redundant - and replaces them with their main New-PodeWebTable etc. counterparts.

Hi @Badgerati,
just had a quick test with the project I'm currently working on and this branch and it looks good - no issues spotted so far. 😄 Just missing my enhancements from #412 but I'll make sure to add them again to this version so you don't have to do it.

Hey @RobinBeismann,
That's good to hear!
On #412 the changes are actually there 😉 for the Textbox it's the same, I've just added a Disabled/DisabledState parameter. For the Select I renamed ReadOnly/ReadOnlyState to be the new disabled counterparts. As I was migrating I spotted that ReadOnly and Disabled were being used interchangeably - which doesn't make sense for an <input> element as it can have readonly and disabled properties. So I split the two out to make more sense.
ReadOnly and Required are now automatically dealt with by the new PodeFormElement base class, and Disabled by the PodeElement base class 😃

Raised feature/enhancement issues from most of the todo comments. Only thing left is to write the migration guide.


force:mdapi:deploy:report uses stash.json/SOURCE_DEPLOY instead of stash.json/MDAPI_DEPLOY

Summary
Somewhere in recent versions there is a break in force:mdapi:deploy:report where it is using the ~/.sfdx/stash.json:SOURCE_DEPLOY.jobid value instead of ~/.sfdx/stash.json:MDAPI_DEPLOY.jobid if --jobid is not provided. This means that force:mdapi:deploy followed by a force:mdapi:deploy is non-functional. This is breaking a step in our CI process where we start the deployment, go and do other things, then try and come back and wait for the deployment to finish, using the stashed jobid instead of tracking it ourselves.
I'm not sure exactly what version breaks this but I can easily compare sfdx-cli/7.8.1-8f830784cc and 7.13.0-27dbcb37d3. It is working in 7.8.1 and broken in 7.13.
Steps To Reproduce:

Prepare a MDAPI deployment package
Deploy that package to the org without an increased wait parameter (will queue the job but not monitor it)
Attempt to use force:mdapi:deploy:report to check the status of the previously started job

The command will do one of two things:

If force:source:deploy was previously used targeting this org it will likely report the results for that old job, you can confirm this by checking the reported jobid from the force:mdapi:deploy with the one returned in the status output.
If force:source:deploy has been used on this machine but not against this org you will see:
ERROR running force:mdapi:deploy:report:  The job for [0Af2i000000oQz6CAR] doesn’t exist. Try again with a valid job ID.
If force:source:deploy has never been used on this machine it will error with
ERROR running force:mdapi:deploy:report:  The job for [0Af2i000000oQz6CAR] doesn’t exist. Try again with a valid job ID.

Expected result
force:mdapi:deploy:report should respect the old and described behavior "defaults to your most recent CLI deployment" and when I run a deploy I should immediately be able to check the status of that deployment with force:mdapi:deploy:report.
Actual result
force:mdapi:deploy:report fails because it is getting confused with force:source:deploy:report on which properties each of them owns.
Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.13.0-27dbcb37d3 win32-x64 node-v10.15.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-commands 1.2.2 (core)
@oclif/plugin-help 2.2.0 (core)
@oclif/plugin-not-found 1.2.2 (core)
@oclif/plugin-plugins 1.7.8 (core)
@oclif/plugin-update 1.3.9 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.5 (core)
analytics 1.1.2 (core)
generator 1.1.0 (core)
salesforcedx 46.3.0 (core)
├─ force-language-services 46.8.0 (core)
└─ salesforce-alm 46.7.0 (core)

sfdx-cli 7.13.0 (core)
sfdx-heber 0.0.2 (link) C:\Users\aheber\dev\sfdx-heber
sfdx-typegen 0.6.2
shane-sfdx-plugins 3.19.0

OS and version:
Windows 10

If I had to guess I'd think the problem is here:
lib\mdapi\mdapiDeployReportCommand.js:16             new MdapiDeployReportApi(context.org, undefined, Stash.Commands.SOURCE_DEPLOY);
It seems that commands\force\source\deploy\report.js and commands\force\mdapi\deploy\report.js should be passing in some context for which Stash.Commands property to retrieve instead of allowing mdapiDeployReportCommand to always retrieve Stash.Commands.SOURCE_DEPLOY.

we have this as W-6293873 in closed.  Pretty sure it's not happening now.


Problem in Grafana variables

When I use trickster in grafana variables as datasource there is problem when you use variable in variable like this:

$host | label_values(pg_up{job=~"postgres-exporter-.*"}, instance)
$instance | label_values(pg_static{instance=~"$host", job=~"postgres-exporter-.*"}, server)
$datname | label_values(pg_locks_count{instance=~"$host", server=~"$instance"}, datname)

In $instance and $datname is no data or some not valid data seem like it not updating. When I use Prometheus directly all works fine.

Hey @lohmag can you please share which version of Trickster you are using? Thanks!

I may be seeing a different issue, but the outcome is 'screwed up Grafana variables'. The nub of my issue is that Trickster appears to be returning cached results for the previous label_values query.
Example: I have two variables, dc (datacenter) and role. The queries for them are as follows:
label_values(system_uptime{role=~"consul|bastion"}, dc)
The system_uptime metric from all 'consul' and 'bastion' roles returns a small set of hosts that exist in all datacenters.
label_values(system_n_cpus{dc=~"$dc"}, role)
This returns all roles in the $dc datacenter. (I use a different metric to make troubleshooting this issue more obvious)
When I configure this dashboard to use Promxy directly, the variables work fine.  I see the following behavior in the browser's developer tools:
Request URL:  https://grafana.domain/api/datasources/proxy/2/api/v1/series?match[]=system_n_cpus{dc=~"eu1"}&start=1559223299&end=1559234099
Results:
data | […]
-- | --
0 | {…}
__name__ | system_uptime
dc | eu1
host | consul1.eu1
role | consul
-- | --
1 | {…}
__name__ | system_uptime
dc | us1
host | consul1.us1
role | consul
-- | --
2 | {…}
__name__ | system_uptime
dc | ap1
host | consul1.ap1
role | consul
-- | --
3 | {…}
__name__ | system_uptime
dc | eu1
host | bastion1.eu1
role | consul
-- | --
4 | {…}
__name__ | system_uptime
dc | us1
host | bastion1.us1
role | consul
-- | --
5 | {…}
__name__ | system_uptime
dc | ap1
host | bastion1.ap1
role | consul
-- | --

So, my browser sends a query for system_n_cpus in the 'eu1' datacenter, but it gets back results for the previous 'system_uptime' query, which specified just 2 roles. So instead of getting a full list of all roles in eu1, I just get those two.
I'm currently using the latest Trickster 1.0 beta 5

Hey @lohmag can you please share which version of Trickster you are using? Thanks!

1.0.0 beta 5

This is potentially related to caching requests to  the Prometheus series endpoint (#73). I will revisit that feature request and make sure it is working properly.

@lohmag this should be all fixed up in the next beta release which we'll cut later today (we  have one more merge to come in first).


Thumbs subscription keeps unsubscribing in prod environment

So I created a Meteor app that has an image upload feature based heavily on the image upload functionality in the Socially tutorial.  That tutorial has me doing the following on the server:
import { UploadFS } from 'meteor/jalik:ufs';
import { Images, Thumbs } from './collection';

export const ThumbsStore = new UploadFS.store.GridFS({
    collection: Thumbs,
    name: 'thumbs',
    transformWrite(from, to, fileId, file) {
        // Resize to 100x100
        const gm = require('gm');
        const WIDTH = 100;
        const HEIGHT = 100;

        gm(from, file.name)
            .resize(WIDTH, HEIGHT)
            .gravity('Center')
            .extent(WIDTH, HEIGHT)
            .quality(75)
            .stream()
            .pipe(to);
    }
});

export const ImagesStore = new UploadFS.store.GridFS({
    collection: Images,
    name: 'images',
    filter: new UploadFS.Filter({
        contentTypes: ['image/*']
    }),
    copyTo: [
        ThumbsStore
    ]
});

and then subscribing to these collections on the client:
        this.subscribe('thumbs', () => [
            this.getReactively('files', true) || []
        ]);

        this.subscribe('images');

        this.helpers({
            thumbs() {
                return Thumbs.find({
                    originalStore: 'images',
                    originalId: {
                        $in: this.getReactively('files', true) || []
                    }
                });
            },

            image() {
                return Images.findOne({
                    _id: this.getReactively('selectedImageId')
                });
            }
        });

When I run it locally on localhost:3000 it runs great, images get uploaded, and the thumbs collection gets populated correctly.
However, when I deploy my app to the production environment, the "thumbs" subscription keeps getting unsubscribed and uploaded files never get copied into it. So my "images" collection has all the images, but the "thumbs" collection is completely empty. Using the Meteor dev tools for Chrome I can see the following messages sent over DDP:
subscribing to thumbs with PEAbhgKe7eukJoj7y "{"msg":"sub","id":"zYjmkFEHB68QpvZQQ ... }
unsubscribing from thumbs "{"msg":"unsub","id":"PiZzG2W8uafKbsKta"}"
subscription ready for thumbs "{"msg":"ready","subs":["zYjmkFEHB68Q ... }
unsubscribed from thumbs "{"msg":"nosub","id":"PiZzG2W8uafKbsKta"}"

I would appreciate any help you all could provide.
Casey

Hi @CaseyDStein, you should investigate the behavior of your this.getReactively() method which is the one that make the subscription change. Otherwise this issue is out of the scope of UploadFS. Please post it on StackOverflow or Meteor forums.


d3js not rendering bar graph

sometimes the bar graphs might not render even though the data is correct. upon inspection the console shows d3 errors with negative values.

solved, 301 error was cached.


problem with core_getopt.sh  and server commands

When i use the ./csgoserver command i get the error
/opt/csgoserver/functions/core_getopt.sh: line 68: column: command not found
Same goes for ./csgoserver status
Also when i enter ./csgoserver details i get no information except for the command-line parameters.
Everything else says command not found.
I installed the server today with    wget http://gameservermanagers.com/dl/csgoserver

"The column command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/."
http://linux.die.net/man/1/column
apt-get install util-linux

What distro are you using for the record ?
That may be something we need to add to the dependencies.

Thanks I will try that.
I use Debian 8.4 Jessie.

Hello. Now it is working
I installed   bsdmainutils with
apt-get install bsdmainutils

how odd maybe bsdmainutils is what is required in debian however util-linux in Ubuntu and CentOS. Need this confirming then I will update the instructions

For the record, we had similar issues, probably with minimal OS installs.
https://github.com/dgibbs64/linuxgsm/issues/613
https://github.com/dgibbs64/linuxgsm/issues/864

bsdmainutils is now a requirement for LGSM


add os, version, and architecture to verbose output

Adding System.Info.os, System.Info.arch, and the ghcid version to the verbose output. Addressing #172 and #196.
%OS: darwin
%ARCH: x86_64
%VERSION: 0.7

Thanks!


chore: add test for container image

Type of change

Chore (any other change that doesn't affect source or test files, such as configuration)

Test plan

New test cases added

Of course it was merged before my review.


[ISSUE #2911]update fastjson version from 1.2.69 to 1.2.76

Make sure set the target branch to develop
What is the purpose of the change
fastjson version is too old.
https://github.com/apache/rocketmq/issues/2911
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.1%) to 54.019% when pulling 088dd29364405621f9a2fbc1bc31aa44fb786b20 on nibiwodong:develop into 4e73ba0ee374d6a5484eb6184bbc8ff3829a7075 on apache:develop.

Codecov Report

Merging #2923 (088dd29) into develop (4e73ba0) will increase coverage by 0.03%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #2923      +/-   ##
=============================================
+ Coverage      47.70%   47.73%   +0.03%
- Complexity      4521     4523       +2
=============================================
  Files            552      552
  Lines          36509    36509
  Branches        4830     4830
=============================================
+ Hits           17415    17428      +13
+ Misses         16867    16859       -8
+ Partials        2227     2222       -5

Impacted Files
Coverage Δ
Complexity Δ

...apache/rocketmq/remoting/netty/ResponseFuture.java
85.00% <0.00%> (-5.00%)
16.00% <0.00%> (-2.00%)

...rocketmq/remoting/netty/NettyRemotingAbstract.java
46.86% <0.00%> (-4.06%)
20.00% <0.00%> (-2.00%)

...a/org/apache/rocketmq/filter/util/BloomFilter.java
59.13% <0.00%> (-2.16%)
25.00% <0.00%> (-1.00%)

...rocketmq/client/impl/factory/MQClientInstance.java
50.94% <0.00%> (-0.73%)
90.00% <0.00%> (-2.00%)

.../main/java/org/apache/rocketmq/common/UtilAll.java
37.98% <0.00%> (-0.33%)
43.00% <0.00%> (ø%)

...main/java/org/apache/rocketmq/store/CommitLog.java
66.42% <0.00%> (ø)
79.00% <0.00%> (ø%)

.../apache/rocketmq/logging/inner/LoggingBuilder.java
63.92% <0.00%> (+0.15%)
3.00% <0.00%> (ø%)

...a/org/apache/rocketmq/store/StoreStatsService.java
30.16% <0.00%> (+1.31%)
26.00% <0.00%> (+1.00%)

...ava/org/apache/rocketmq/filter/util/BitsArray.java
62.39% <0.00%> (+2.56%)
31.00% <0.00%> (+1.00%)

...ava/org/apache/rocketmq/test/util/VerifyUtils.java
49.25% <0.00%> (+2.98%)
15.00% <0.00%> (+1.00%)

... and 4 more

Continue to review full report at Codecov.

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


Fix for Issue #85 (Duplicated move records)

Changes our query to order by the same column that it is using to determine if objects are unique.  Also added testing.

Sorry for the mess, it looks like it put all of my commits here.  I'm quite new to git, so I had some trouble when I tried to merge in the latest version.
2109213 was my original local fix.
648d933 was a failed attempt to merge phalt/master to my repo.
8956615 was an attempt to revert but it reverted to the wrong version.
a36bdd0 was my successful attempt to get my repo in sync with phalt/master .
54b174f contains all of the relevant info.
If someone has a suggestion on how I can cancel this request and get a cleaner one, please let me know, because I agree this is a mess.


documentation update: xgemm and s/d trsm are no longer thread-safe.

update version number to 2.11

We are going to wait to merge this PR, and see if the thread safety fixes #235 from David resolve the customers issues.


Use container agent for CI build

Use container agent for CI job
https://github.com/jenkinsci/bom/pull/1338#issuecomment-1198016897 notes that there is an automated test failure in the bill of materials and plugin compatibility tests.  This change is trying to duplicate that failure on ci.jenkins.io.
The first commit in this pull request will be considered "successful" if the build status is failing for the first run.

 (build 1 aborted for build 2)
 - build 2 (confirms problem visible on ci.jenkins.io)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have referenced the GitHub comment related to my changes in one or more commit messages
[x] Unit tests pass locally with my changes
[x] I have added documentation as necessary
[x] No Javadoc warnings were introduced with my changes
[x] No spotbugs warnings were introduced with my changes

Types of changes

[x] Infrastructure change (non-breaking change which updates dependencies or improves infrastructure)

org.jenkinsci.plugins.gitclient.verifier.NoHostKeyVerifierTest#testVerifyServerHostKey which do not verify keys at all and simply return true failed with  Caused by: java.net.ConnectException: Connection timed out (Connection timed out).
Kind of we can't connect from container using ssh...

@Pldi23 I've run out of time that I can spend on this investigation.  I've made multiple guesses and tried multiple alternatives without understanding the root cause.  I've tried closing the JGitConnection explicitly in the test.  I've tried removing the parallel execution with forks.  I've tried reducing dependencies.  No change.
There was a period where the tests were passing on maven-11, then they started failing again.  I don't know what changed.
I've added conditionals that exit the tests early if the test is running on a Kubernetes agent on ci.jenkins.io.  By limiting the exclusion to only kubernetes on ci.jenkins.io, that will allow the tests to continue running on my cluster.
I'd like to deliver git client plugin 3.12.0 from the master branch early this week so that JGit 5.13.1 is available to Jenkins users and so that the master branch represents a recent delivery.  Does that seem reasonable to you?

I'd like to deliver git client plugin 3.12.0 from the master branch early this week so that JGit 5.13.1 is available to Jenkins users and so that the master branch represents a recent delivery. Does that seem reasonable to you?

@MarkEWaite fine for me to deliver 3.12.0. (When I have some free time, I will also try to figure out what could be the reason here)


Path-based routing Ingress not working

Rancher Versions:
Server: 1.5.1
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Docker Version: 1.12.6
OS and where are the hosts located? (cloud, bare metal, etc): Ubuntu 16.04; AWS EC2 instance
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB) single node rancher
Environment Type: (Cattle/Kubernetes/Swarm/Mesos) Kubernetes
Steps to Reproduce:
I am running a Kubernetes cluster (which has the default rancher-ingress-controller) and trying to use an ingress with path-based routing. I first run some service/deployment (i.e. nginx-svc) and then create an ingress as follows:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: path-based-ingress
spec:
  rules:
  - http:
      paths:
      - path: /foo
        backend:
          serviceName: nginx-svc
          servicePort: 80

Then I make a request to the host ip address with a path i.e. curl -i http://<IP_ADDRESS>/foo
Results:
I get the following response:
HTTP/1.1 404 Not Found
Date: Thu, 09 Mar 2017 02:13:49 GMT
X-FRAME-OPTIONS: SAMEORIGIN
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html; charset=ISO-8859-1
Content-Length: 280
Server: Jetty(9.2.13.v20150730)
...

However, if I change the path in the ingress config file to just "/" such that the yaml looks like this:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: path-based-ingress
spec:
  rules:
  - http:
      paths:
      - path: /
        backend:
          serviceName: nginx-svc
          servicePort: 80

then run curl -i http://<IP_ADDRESS>/, everything works fine; I get a valid response:
HTTP/1.1 200 OK
Date: Wed, 08 Mar 2017 17:58:17 GMT
X-FRAME-OPTIONS: SAMEORIGIN
Content-Type: text/html
Content-Length: 6047
Server: Jetty(9.2.13.v20150730)

Thanks in advance for any help!

FYI, I also tried using the native Load Balancer feature in Rancher; I selected "Add Load Balancer" to the 'default' stack. The result is the same. as described above. If I set a path to something like "/foo", I get a 404 - Not Found response. If I set the path to "/", it works properly.
As I understand it, Rancher uses HAProxy for its load balancing, so perhaps there is some general issue with HAProxy handling paths in the config?

It's not that the LB is not working, but that /foo doesn't exist in your nginx-svc.
If the LB wasn't working, it'd be a 503.

Specifically the misunderstanding is probably that /foo is not stripped off the request sent to the backend.  The rule chooses what backend service will receive the request, but the request itself is not modified.  So the target service receives GET /foo,  and it returns 404 because doesn't have a foo.
You can use the custom haproxy config to cause the balancer to strip the prefix off of the request.  But this is not on by default breaks any application that returns absolute or root-relative URLs and expects those to be retrievable.  This is very common with a HTML response that includes references to CSS/JS/image files.

@vincent99 I see. I guess I was not entirely clear on how path routing is supposed to work with Ingress. I thought the path value /foo in the request would be mapped to nginx-svc:80/, but it is actually trying to route to nginx:80/foo?
So is there a way to use Ingress to route from path /foo in the request i.e. http://<IP_ADDRESS>/foo to path / in the actual service? Or is the only way to do this via a custom haproxy config?
Thanks for your help!

The only way is with custom haproxy config.  Because like I said, it's very commonly not actually useful.


display_interface package has wrong dependencies

It claims to depend on roscpp, rospy, std_msgs. But actually it needs rospy, sensor_msgs, cv_bridge.

Hi Joep,
Many thanks for your feedback, we confirmed your advice, you are right.
Could you please post a pull request directly?
I will merge your pull request?
Thanks!

already merged your pull, many thanks!


Improve xml prettyfier

prettier's xml pluggin now supports a much better XML autoformatting mode. See https://github.com/prettier/plugin-xml/issues/138#issuecomment-724547415.
Below are my findings on how to make it work.
You need a .prettierrc.cjs instead of .prettierrc.yml, so prettier can load the plugin even when run from pre-commit:
/** @type {import('prettier').Config} */
const config = {
  plugins: [require.resolve("@prettier/plugin-xml")],
  bracketSpacing: false,
  printWidth: 88,
  proseWrap: "always",
  semi: true,
  trailingComma: "es5",
  xmlWhitespaceSensitivity: "preserve",
};

module.exports = config;

And the pre-commit config needs to be adapted like so:
  - repo: https://github.com/pre-commit/mirrors-prettier
    rev: v3.0.3
    hooks:
      - id: prettier
        name: prettier + plugin-xml
        additional_dependencies:
          -<EMAIL_ADDRESS>          - "<EMAIL_ADDRESS>

You need a .prettierrc.cjs instead of .prettierrc.yml, so prettier can load the plugin even when run from pre-commit

Prettier was always able to load the XML plugin until now. Did something relevant change in that regard?

Apparently prettier 3 changed module discovery in a way that is incompatible with pr-commit. It's a rabbit hole and this approach is the best I could find


GUI using Gradio or Pygame or Streamlit

We would have a better interface and keep modes for changing the model.
For the model change we will the GUI so that it will be vv easy for the user to change the model.
I would love to work on this if someone is ready to guide along with it.. I am familiar with Gradio,Pygame and Streamlit.
One inspiration is this privateGPT UI using Gradio:

There are many GUIs available for ollama if your ask is that. Check out the list in their repo. My fav is ollama-webui

There are many community built web and desktop UI. Here's a non-exhaustive list. The intent with this project is to create a foundation for the community to build tools and applications so a UI is out of scope.
Feel free to use this project or ollama-js to build your own GUI if the ones I mentioned above don't satisfy your use case!


Implemented a slue of new functions to interact with the realms API

This PR implements a handful of new functions to interact with even more parts of the Minecraft realms API—all the way from banning players to deleting a realm with the specified ID. You can find the added functionality below:
Bedrock & Java

Get realm subscription info
Get detailed realm subscription info
Change active realm slot
Change realm name and description
Delete realm

Bedrock

Reset realm
Update realm configuration
Remove realm invite
OP realm player
DEOP realm player
Remove all realm players
Ban player from the realm
Unban player from the realm
Remove realm from joined list
Update forced texture pack rule
Update realm default permission
Update realm player permission

Feel free to leave suggestions or comments if you need anything fixed, added, or updated. Thanks

Are we wanting to add tests for all of these calls?

Sounds good! Thank you for the feedback and the review. Expect everything to be pushed by the end of today. (in ~4 hours from now max)

For now, I'm not pushing anything related to removing all realm players for now. There seems to be an issue with setting values as null in the body of the requests.
I will be creating another PR for this issue to address it better and to keep it separated from here.

Fixed everything there, there are a couple of small things that still need to be fixed but I already have another PR cooking up to address them.

If you could just make one big list of changes that need to be made it'd be greatly appreciated. It's nice to just have one big push of fixes then the commit history doesn't get all clogged unless we're doing a rebase when merging.

Don't worry about the PR commits. It will be squashed on merge.

If you have any feedback for anything else that is out of scope or that you think doesn't belong in this PR just let me know and I'll create another PR. Right now I'm just trying to get a good baseline to start from to expand further and improve.

So I should be making custom types for responses for every function that returns something other than void in index.ts?

Yes, either don't return anything or doc what is returned

Any other changes that need to be made?

So after a second review, some of the doc/types you updated aren't things changed in the code, so instead of making changes there per my previous comments (about how we should throw), what you can do is simply revert those changes (like changes to .open()). We can handle those later, so we can get this merged quicker.
Also, @LucienHH do you think the configuration object will change or break in the future? If so we should move that out of the PR until some abstraction is implemented there. If not then I think it's ok if we just leave it as an dynamic object.

Also, @LucienHH do you think the configuration object will change or break in the future? If so we should move that out of the PR until some abstraction is implemented there. If not then I think it's ok if we just leave it as an dynamic object.

The config can change from update to update so should definitely be abstracted away, funnily enough the config has already changed from the one in this PR.

What is the status of this PR? what's missing to finish it ?

@LucienHH @extremeheat what do you think on this PR?

I commented out the changeRealmConfiguration method since that's not stable API, we can handle this in another PR

Thanks for the work on this. We can discuss the remaining changes in the other PR. I'll merge so we can resolve the PR backlog.