Can't config proxy in configureWebpack

Description
I am following config devServer proxy in vuecli
Steps to reproduce

Add proxy to webpack config

configureWebpack: {
    devServer: {
      proxy: {
        '/.netlify/functions/**': {
          target: 'http://localhost:9000',
          changeOrigin: true,
          secure: false,
          pathRewrite: {
            '^/\\.netlify/functions': ''
          }
        }
      }
    },
  },

Expected result
Should change host
Actual result
No change host

I wasn't able to get the webpack devServer proxy to work, but I'm not 100% sure how the gridsome internals worked. Since it looks like express is used internally, I used a similar approach to creating a proxy in gatsby. This seemed to resolve the issue for me...
Steps:

yarn add -d http-proxy-middleware or npm install http-proxy-middleware --save-dev
Create gridsome.server.js in the project root (same directory as gridsome.config.js)
Add the following code:

var proxy = require("http-proxy-middleware");

module.exports = function(api) {
  api.configureServer(app => {
    app.use(
      "/.netlify/functions/",
      proxy({
        target: "http://localhost:9001",
        pathRewrite: {
          "/.netlify/functions/": ""
        }
      })
    );
  });
};

It's worked. Thank you 👍

THANKS for this

Tried on 5/22 - Getting error : proxy is not a function. Tried {proxy} as well.
Any help much appreciated! 😀

@BobDempsey
The http-proxy-middleware package has since been renamed the proxy method to createProxyMiddleware. You should now import the method like this:
const { createProxyMiddleware } = require('http-proxy-middleware')

@BobDempsey
The http-proxy-middleware package has since been renamed the proxy method to createProxyMiddleware. You should now import the method like this:
const { createProxyMiddleware } = require('http-proxy-middleware')

This is absolutely true, however at the time of this writing, Gridsome uses version 0.19 of that package so everyone should just import the version available with Gridsome and use the old syntax for now.


Add version metadata to feature gates

This is a Feature Request

What would you like to be added
The feature gates page is generated from lots of small Markdown files. We have a demo of how we can add metadata to the front matter of each page.
This issue is about two things:

setting version metadata in the front matter of those pages
adding some MVP validation to fail a website build if the version metadata is present but invalid

Why is this needed
We want to automate the process of updating feature gate information. It's very common to move features from alpha to beta and we want to make it easy for contributors to do that. However, it's a big change to make all in one go.
So, this issue is an incremental improvement. We get to set version metadata and make sure it's not obviously wrong, and we end up closer to the point where we can build on this. The demo in PR https://github.com/kubernetes/website/pull/43491 shows only one possibility.
People have had other ideas; for example, we could change our feature-state shortcode so that it loads the feature state based on the metadata we have for a feature gate.
If you want to implement your own idea, and especially if you can do that change without updating every feature gate we list, then you would be welcome to.
Comments
/area web-development
If you pick this up, you can choose one of two approaches:

add the validation code and set the version metadata for some feature gates

for example, you could add it just to the feature gates that have already been removed
for example, you could add it just to the feature gates that begin with the letter A
that leaves work for other contributors to do in a future PR, and helps keep your change small

add the validation code and set the version metadata for all feature gates

Anyone is welcome to work on this. It is not particularly beginner friendly, so if you want to help here and haven't already worked on a web development issue in this repository, you might like to pick up a simpler web development issue first and then return to this one.

/priority backlog
/triage accepted
We'd like to do this, but it's not our top priority.

/assign

We could split this up into subtasks that people could claim.

This is done
/close

I wonder if we can do something around automatically comparing against https://github.com/kubernetes/kubernetes/blob/master/test/featuregates_linter/test_data/unversioned_feature_list.yaml


Fix AuthSupport StringIndexOutOfBoundsException

Fix Bug:HTTPCLIENT-2009

@ITonyLi Could you please squash all those commits into a single one and give it a more descriptive commit message that includes the JIRA ticket and affected class(es) / method(s)?

@ITonyLi What happened? Why did you decide to close the PR?

I will pull request again
发自我的iPhone
------------------ Original ------------------
From: Oleg Kalnichevski<EMAIL_ADDRESS>Date: Sun,Aug 11,2019 8:33 PM
To: apache/httpcomponents-client<EMAIL_ADDRESS>Cc: ITonyLi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [apache/httpcomponents-client] Fix AuthSupport StringIndexOutOfBoundsException (#158)
@ITonyLi What happened? Why did you decide to close the PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

https://github.com/apache/httpcomponents-client/pull/159
发自我的iPhone
------------------ Original ------------------
From: Oleg Kalnichevski<EMAIL_ADDRESS>Date: Sun,Aug 11,2019 8:33 PM
To: apache/httpcomponents-client<EMAIL_ADDRESS>Cc: ITonyLi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [apache/httpcomponents-client] Fix AuthSupport StringIndexOutOfBoundsException (#158)
@ITonyLi What happened? Why did you decide to close the PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Why not try..match?

I know it might be a little confusing at first but I don't think the original syntax is bad, we could just do something like try..match to specify that "error" instantiates a certain class.
try {
  // some error producing code
} match (TypeError error) {
  console.error(`We got a type error: ${error}`);
} catch (error) {
  console.error(`We got an unknown error: ${error}`);
} finally {
  // handle shutdown
}

The syntax for match is questionable and debatable, but I prefer to keep the part that we don't have an implicit variable to get the error data, an explicitly named variable is much better.

That seems like a good alternative syntax to consider once pattern matching’s shape is solidified.

I think it implicitly introduces Typization to JS (or at least it looks like it, which adds ambiguity), I would also wanted it but not this way. The more JS-style would be something like this
try {
  // some error producing code
} catch (error; error instaceof TypeError) {
  console.error(`We got the known error: ${error}`);
} catch (error; error instaceof SyntaxError) {
  console.error(`We got another known error: ${error}`);
} finally {
  // handle shutdown
}

That would also allow matching any boolean value, which is more flexible.

what is "typization"?


Update Wiki link

Describe the bug
I know the wiki has largely been moved to the blog but the redirect/hyperlink errors out.
To Reproduce
On clicking https://www.woodys-findings.com/scout/wiki which returns
{"error":true,"reason":"Not Found"}

Expected behavior
Hyperlink takes you to https://www.woodys-findings.com/scout or specifies the specific wiki articles https://www.woodys-findings.com/scout/news-4.0.0 /  https://www.woodys-findings.com/documentation/scout/new-4.0.0
I would throw in a PR to make it easier but editing the wiki appears to be looked down. Thanks for the great tool!

Hi ! Thank you for reporting this. Could you clarify where the dead link ça ne found? I'll change it.
The wiki is not open source yet (for the command-line part) since I needed some extra services which I implemented on my blog. And open sourcing this part would be easier if the overall blog was open source, which would require me to rework large parts of it 😅

Resolved with release 4.1.0


Add locked count to Visualizations endpoint

Related to https://github.com/CartoDB/cartodb/issues/14482
The /viz endpoint now returns a new property total_locked with the count of locked datasets:
{
  "visualizations": [...],
  "total_entries": 3,
  "total_user_entries": 3,
  "total_locked": 1,
  "total_likes": 0,
  "total_shared": 0
}

@alrocar good catch! I was really retrieving the lock count for all the users... :man_facepalming:

That is the expected behaviour: the locked count must only take into account the owned visualizations (https://github.com/CartoDB/cartodb/issues/14482#issuecomment-444416604).
Regarding the request parameters, we are sending exclude_shared=false, but also shared=no, which discards the shared ones in the end. Anyway, this is for the main visualizations. We make another request for the locked count.

Acceptance 🍏

After merging this I've realized there was a dependent PR https://github.com/CartoDB/cartodb/pull/14504
Please remember to remove this branch, once everything is merged.


for #2846 4.0.x version MasterSlaveRuleConfiguration properly

4.0.x version of the configuration MasterSlaveRuleConfiguration properly.
Fixes #2846
Changes proposed in this pull request:

Adjust MasterSlaveRuleConfiguration.java property Settings
Add a no parameter constructor
Add the property @setter

We should update document later, but a full parameters' constructor is necessary.

Pull Request Test Coverage Report for Build 9118

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 64.063%

Files with Coverage Reduction
New Missed Lines
%

sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/util/IpUtils.java
3
76.0%

Totals

Change from base Build 231:
0.0%

Covered Lines:
9054

Relevant Lines:
14133

💛  - Coveralls


Cannot use jest.mock

Can you use jest.mock ?
With this:
import { myFunc } from '~/api';
jest.mock('~/api');

I get:
Cannot find module '~/api' from 'jest.setup.js'
If I change it:
jest.mock('./src/api');
The error is gone, but myFunc is not mocked.
Here is my code:
https://github.com/martpet/vite-play/blob/Add-tests/src/store/features/translations/translationsThunks.test.ts

What was the issue here? @martpet

jest.mock doesn't work with ES modules, but there is now jest.unstable_mockModule which is supposed to work.


Hope to add servers in China

As the number of users increased, more and more Chinese users joined habitica, but the response was particularly slow when visiting the website in China, which seriously affected the player's experience.

Hi @skogsng, I'm just the developer of the Pomodoro extension, I believe you should contact<EMAIL_ADDRESS>Good luck!


Sequencer:Determine whether sequencer sends the invalid block during the process of permission block output

Scheme changed. Sequencer does not produce blocks


Is this project still active?

Hi @brunobowden @advayDev1, does this project still active ? could we securely rely on it?
Thanks for the awesome job you did so far !

You can certainly use it. But you need to patch a few things to make it work with the bleeding edge git branch of j2objc.

The project does seem to be on a bit of a pause, but it is still usable. You can use j2objc-gradle 0.6.0-alpha with the latest version of J2ObjC 1.0.2 provided you add this to your j2objcConfig section in build.gradle:
j2objcConfig {
  j2objcVersion "1.0.2"
  .
  .
  .
}

Also, you have to stay at Android Studio 1.5.1 due to Gradle version incompatibilities. j2objc-gradle will only work with Gradle 2.8 or lower, but the Gradle Android plugin used by Android Studio 2.0 requires Gradle 2.10. If you stay at Android Studio 1.5.1 (and thus the older Gradle Android plugin), you can use Gradle 2.8 with it and j2objc-gradle. There is a workaround posted to this issue that allows you to use j2objc-gradle with Gradle 2.10. I haven't had a chance tried it.
One other note: if your project uses Guava directly a little workaround is needed.

I think the answer is definitively "no" as of right now: https://groups.google.com/forum/#!topic/j2objc-discuss/jQ_eyW9nxmQ


index.d.ts and index.js do not exist

There is no index module.
When this library is imported with yarn add waveguide, it cannot find the files.
In the package.json, it points to ./lib/index.js as expected but the files do not exist.
The result we're after is export { wave, managed } from 'waveguide'.
Are you happy for me to make a pull and fix it?

The expectation was that users would import directly the submodules they wanted similar to the functioning of fp-ts. We don't currently publish any built artifacts and I'm skeptical this library would be of any use from javascript anyway.
If you think there is benefit in providing a single import at lib/index.ts listed as the main entry that would be ok also. Or we could simply remove that field from package.json.


enable default timeout

currently: SerialManager(..,timeout=None)
timeout should have a default value, it can be between 1-5 sec
Reason: we got better error reports with stack from new users.
I don't know any operation in the firmware which can take more seconds other than sleep(),
but using long sleep() in the firmware  is a bad solution .
see #33

Work in progress, I'll work on it during this we

Closed by https://github.com/nanpy/nanpy/commit/2ded6d8d00938fcdb55d1f253f095b1c92fa1506


Intent Recognized InCorrect

rasa NLU version 0.7.2
Used backend / pipeline spacy_sklearn
Operating system:windows,
Issue:
I try to build a FAQ NLP engine, I loaded 500 questions into RASA NLU, in my data file, I use question as "intent" and "text". So I have 500 intent and 500 training text. After deploy, I found even I use exact question to test RASA NLU, I often get a wrong intent with low confidence (0.0xx).

Unfortunately, these are too many intents with too few training examples. For the machine learning model to properly distinguish between the different questions, you would need way more training examples for each question.
Since, FAQ is a very specific (but also quite different use case from "normal" chat interactions) we are thinking about different solutions here as well. We don't have a ready to use solution yet but if you feel adventurous there is a lot of research about this topice, e.g. http://ijcai.org/Proceedings/15/Papers/188.pdf


[Suggestion] EmbedCreator | Embed Pages

I have no idea if this is plausible but it would be really cool.
So if you wanted to like create a help with custom commands/aliases or whatever to show.
That might grow into a very long embed when it's posted or perhaps ending up having too many characters for one embed.
My suggestion/question is if it would be possible to have options to decide what text would be on what page of several embeds.
You define how many pages you want it to have. You give it an embed for a specific page. One at a time or something. Like an interactive option like some cogs use. Or whatever works better.
embed menu <pages>
After that you get questions to upload an embed for page 1, then page 2 and so on.
Finally when using the command that is aliased to drop page 1, or something just pulling this out of the blue, it will know that this embed has more than one connected to it and will add the left/right arrows to change page and also the crossmark so you can delete if you want.
I hope I didn't leave anything out from my mind to try and explain it. But I think you probably get what I mean.

Added in 5e5f8d44775417b516819b894690d5dc8b068c0c


decrease size of schedule items

decrease size of schedule items to make them fit without break

another update on the way

@alanderex: Please also update the original files in ./partials/pycon/_schedule.scss so that the update doesn't get lost when we recreate the all.css. Thanks.


Cannot find place to submit problems

I can find no way to indicate problems I have found with the toolkit.

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

ID: f2fb5332-4c1b-fc63-1be9-9032440ff424
Version Independent ID: f2fb5332-4c1b-fc63-1be9-9032440ff424
Content: .NET MAUI Community Toolkit documentation - .NET Community Toolkit
Content Source: docs/maui/index.md
Product: dotnet-communitytoolkit
GitHub Login: @bijington
Microsoft Alias: joverslu

It is a good point that we don't explicitly state where to do this. I guess I had assumed that if you had the toolkit installed you would have used NuGet which includes a link to the project repository. That url is https://github.com/CommunityToolkit/Maui
Please do raise any issues that you have there.
We can leave this issue open and aim to add something to the documentation pages to make it more clear.


Porting stable versions over from Goest

This PR copies in stable versions of the contracts from Goest

I did a second check, and I think we should be good. The two unchanged files are externals for contracts without external API changes. Going to go ahead and merge


Fix: pom amendments

Refactoring of POM:

Moved versions number to properties section
Moved  plugin configuration to plugin management

Built successfully and services running correctly when deployed in CDAP.
Returning JSON of company house:


Suggestion to make onClick lambda parameter in Modifier.clickable optional

Today I've got a usecase where I only needed the onLongClick callback of the Modifier.clickable funnction. But to add just a LongClick or DoubleClick callback you have to also define the onClick callback which provided not the wanted result

This is shared API with Android, please report at https://issuetracker.google.com/issues and post number here.

Thanks for the reply
Wasn't sure if this was an compose for desktop thing or not
That means this issue was a missunderstanding and is not meant to be in this repository

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Search icon in search input in header is misaligned

The Search icon in the search box that appears in the header of the search page looks a bit high.

Wagtail 2.16a0 (current main)
Tested on Firefox 93 and Brave 1.34.80 (Chromium 97). Both on Linux

@amelia291 It's in the header of the results page that you get after running a search, e.g. http://localhost:8000/admin/pages/search/?q=test

I cannot identify the bug mentioned in the issue. It seems like this has been fixed.

Looks like the search icon in the page chooser is misaligned on version 2.16.1 .

Fixed in #8310.


.consul domain should not be hardcoded in package definitions

this is not going to be necessary going forward: https://github.com/CiscoCloud/mantl/issues/1252


Does not recognize enum definitions starting with "_"

Enum definition "_undefined = 0;" caused an issue with the lexer (error printout: "Did not parse all of file"). Removing the underscore fixed the problem.

Hmmm... according to the google protobuf language spec (https://developers.google.com/protocol-buffers/docs/reference/proto2-spec), a leading underscore is not valid for an enumerator name. It has to be a lower-case or upper-case letter for the first character. No?
But I suppose this wireshark plugin doesn't need to be so pedantic. (and even if it is, it should print out better error info)

That makes sense. I'm using a third-party's proto files, so they probably
didn't bother to standardize. It was an easy change to remove the
underscores for it to work.
Either decision is fine by me, but I agree that a better description may be
helpful. It may save others with similar issues in the future.
On Mon, Apr 25, 2016 at 2:31 PM, Hadriel Kaplan<EMAIL_ADDRESS>wrote:

Hmmm... according to the google protobuf language spec (
https://developers.google.com/protocol-buffers/docs/reference/proto2-spec),
a leading underscore is not valid for an enumerator name. It has to be a
lower-case or upper-case letter for the first character. No?
But I suppose this wireshark plugin doesn't need to be so pedantic. (and
even if it is, it should print out better error info)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/128technology/protobuf_dissector/issues/1#issuecomment-214472162


WIP -- [explore-v2] make chart container work with nvd3_vis.js

this PR is a work in progress...

makes <ChartContainer /> use existing nvd3_vis.js module to render charts.

todo:

[x] use vizMap object to map chart type to vis module
https://github.com/ascott/caravel/blob/master/caravel/assets/visualizations/main.js#L3
[ ] figure out if other vis modules have other different dependencies than than the nvd3_vis module

/exploreV2/ with line, bar, area, pie, bubble, box_plot

cc @mistercrunch @vera-liu

table type has a dependency on slice.d3format:

big number with trendline doesn't show big number

big number doesn't render big number:

directed force layout looks a little different....

region filter is broken on /explore/

/exploerV2/ has dependency on slice.getFilters

heat map has some layout issues:

pivot table type throws an error in V2:

sankey as layout/visual issues in V2:

sunburst has layout/visual issues in V2:

word_map type throws an error in V2:

@mistercrunch added support to use the mapping from vis type to vis file. i removed some components I had duplicated in explorev2, and also removed the new line chart in favor of using the existing viz files. i added an issue documenting the outstanding issues with wrapping the vis's in V2 and will make another PR with fixes for those. https://github.com/airbnb/caravel/issues/1341. PTAL!


labelIMG crashing while selecting Create Rect box

OS:
PyQt version:

labelIMG crashes

code

p.drawLine(int(self.prev_point.x()), 0, int(self.prev_point.x()), int(self.pixmap.height()))
p.drawLine(0, int(self.prev_point.y()), int(self.pixmap.width()), int(self.prev_point.y()))

As you can see here, the arguments have changed to int.
However, yours not.
I guess you need to upgrade labeling ? or clone this repo and use it.

Have the same problem. Downloaded through pip as well.

Have the same issue, run by Python3.10, download it using pip3

I have the same issue. Has it been resolved when downloading through pip?

I can't recall the details anymore, but I think I resolved it by downloading this repository and installing by running pip install -e . inside of the directory. If I recall correctly the version uploaded to pip was outdated.

On 18. Apr 2022, at 13:06, John Edward Binay @.***> wrote:
I have the same issue. Has it been resolved when downloading through pip?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

Can you please share the updated version with us?
Thanks ,
Get Outlook for iOShttps://aka.ms/o0ukef

From: Thomas Johannesmeyer @.>
Sent: Monday, April 18, 2022 8:16:38 PM
To: tzutalin/labelImg @.>
Cc: ASETS-LUX - Info @.>; Mention @.>
Subject: Re: [tzutalin/labelImg] labelIMG crashing while selecting Create Rect box (Issue #838)
I can't recall the details anymore, but I think I resolved it by downloading this repository and installing by running pip install -e . inside of the directory. If I recall correctly the version uploaded to pip was outdated.

On 18. Apr 2022, at 13:06, John Edward Binay @.***> wrote:
I have the same issue. Has it been resolved when downloading through pip?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

—
Reply to this email directly, view it on GitHubhttps://github.com/tzutalin/labelImg/issues/838#issuecomment-1101625086, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXLQYQO4IR4ZDHGS2OD7ZJTVFWRINANCNFSM5MH2N4RQ.
You are receiving this because you were mentioned.Message ID: @.***>

facing the same issue now. anybody got a solutions ?

facing the same issue now. anybody got a solutions ?

https://github.com/tzutalin/labelImg/issues/899#issue-1274532359 try check this one, the owner has fixed it

after using the latest version it fixed now

@tzutalin I do not see the canvas.py changes to fix the cast to int( ) when 'pip install labelimg'. It installs version 1.8.6, but, this version still has the broken canvas.py code that tries to use float. Any suggestions on how I can pip install the latest with the fix?

facing the same issue when installing through pip, any solution?

#error
drawLine(self, l: QLineF): argument 1 has unexpected type 'float'
#how to fix it
on the python3.11/site-packages/libs/canvas.py
change the code to int;
p.drawRect(int(left_top.x()), int(left_top.y()), int(rect_width), int(rect_height))
p.drawLine(int(self.prev_point.x()), 0, int(self.prev_point.x()), int(self.pixmap.height()))
p.drawLine(0, int(self.prev_point.y()), int(self.pixmap.width()), int(self.prev_point.y()))

I fixed it by creating new environment with python 3.6

This video solved everything:- Float to Int

This video solved everything:- Float to Int

Its absolutely did as of 21NOV2023, this still works! thank you ashok01620!

For those who face this error. This is step by step:

For me its work on python version 3.8.0
Update pip version, put this command on gitbash:python -m pip install --upgrade pip
put this command on gitbash to download labelImg:pip3 install labelImg
run it on gitbash with this command:labelImg

hope this will fix your problem.


Add task doc for alpha dynamic kubelet configuration

This documents how to change the Kubelet configuration on a single node in a live cluster with the new, alpha, Dynamic Kubelet Configuration feature.
/cc @luxas @dchen1107

This change is

@mtaufen, To make this new topic appear in the left nav, add a line to _data/tasks.yaml.

@mtaufen, Please rebase your branch so that it picks up 99fbc2b. That will fix the deploy/netlify failure. Thanks.

Probably we are supposed to add some text about the KubeletConfigFile feature gate as well.

@tengqm yeah, we should mention it somewhere. I think a mention and a link to a separate doc would be most appropriate, as it is a separate (though related) feature.

I'll start a docs review now.

@mtaufen Just a couple of comments.

Updated PTAL.
I still need to do a final run-though of all the steps to make sure it works after my most recent changes, so don't expect everything to be perfect yet.

@mtaufen, Just one more thing: The {% include feature-state-alpha.md %} should be immediately after {% capture overview %}

@steveperry-53 looks like Travis is timing out?


chore: bumping version to 1.2.0

Bumping version to 1.2.0

In releasing.md we need to change the variables to:
PRV_VER="1.1.0"
CUR_VER="1.2.0"
NEXT_VER="1.3.0"

This part should be simplified. I am thinking to change it


IHttpContextAccessor resolved as null

I am using IdentityServer3 with dotnet core and am upgrading to RC2 and have hit a snag.
I have a custom user service which I want to resolve out of the aspnet core container. So I get access to the Request services like this:
var idsrvOptions = new IdentityServerOptions
{
    Factory = new IdentityServerServiceFactory
    {
        UserService = new Registration<IUserService>(r =>
        {
            var owin1 = r.Resolve<OwinEnvironmentService>();
            var httpContext1 = (HttpContext) owin1.Environment["Microsoft.AspNetCore.Http.HttpContext"];
            return httpContext1.RequestServices.GetService<CustomUserService>();
        })
    }
...

Not pretty, but I couldn't figure out how else to go from identity servers internal container to the request container without doing this. It calls into my factory fine:
services.AddScoped(p =>
{
    var httpContextAccessor = p.GetService<IHttpContextAccessor>();
    var portalOptions = p.GetService<IOptions<AuthenticationApiOptions>>();
    return new IdentityStoresApi(
        portalOptions,
        _portalApiHandler(),
        httpContextAccessor,
        _selfApiHandler);
});

Inside the AddScoped callback, httpContextAccessor is null. Any ideas what I have missed? The options are resolved fine.

In RC2, IHttpContextAccessor isn't registered by default. This means you have to register it yourself, explicitly; https://github.com/aspnet/Mvc/blob/dd774366f6fb18af9382ca84c276e6eb73c66b3a/test/WebSites/BasicWebSite/Startup.cs#L23
Related: https://github.com/aspnet/Razor/issues/768

Following is my startup.cs file code snippet
` public void ConfigureServices(IServiceCollection services)
{
// Add framework services.
services.AddDbContext(options =>
options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")));
        services.AddIdentity<ApplicationUser, IdentityRole>()
            .AddEntityFrameworkStores<ApplicationDbContext>()
            .AddDefaultTokenProviders();

        services.AddMvc();
        services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();
        services.AddSingleton<IActionContextAccessor, ActionContextAccessor>();
        //services.AddCaching();
        services.AddSession();
        // Add application services.
        services.AddTransient<IEmailSender, AuthMessageSender>();
        services.AddTransient<ISmsSender, AuthMessageSender>();
    }`

I'm unable to get Httpcontext in my static class
` public static class TestHelper
{
public static IHttpContextAccessor HttpContextAccessor;
    public static void Configure(IHttpContextAccessor httpContextAccessor)
    {
        HttpContextAccessor = httpContextAccessor;
    }

public static string UrlFinder(this IHtmlHelper helper, string controlid)
{
HttpContextAccessor httpContextObj = new HttpContextAccessor();
//This line worked in RC1
var urlHelper = httpContextObj.HttpContext.RequestServices.GetRequiredService();
};
}
`
I already tried the steps said in following link comments

https://github.com/aspnet/Mvc/issues/3936
https://github.com/aspnet/Razor/issues/768

Please help us to find out solution.

@manikandan05 You can't just create an instance of HttpContextAccessor and expect it to know about the current HttpContext. You need to get it from the container. That's why you're registering it.

Hi @khellang , I just want to get the urlHelper for my action. I tried out get the value from the below mentioned way.
'  var urlHelper = httpContextObj.HttpContext.RequestServices.GetRequiredService(); '

@khellang so the behaviour of the DI in core is to return null when things are not registered rather than throw an error? That seems broken =/
I didn't even check for it not being registered because I assumed if something is not registered it would throw saying it cannot resolve.

@JakeGinnivan Yes, when calling GetService. If you want to make sure it throws for invalid configurations, you need to call GetRequiredService :smile:

@manikandan05 I'm not sure what you're trying to do. You want to resolve IHtmlHelper from the services? You already have it as a parameter?
You could do something like
public static class TestHelper
{
    public static string UrlFinder(this IHtmlHelper helper, string controlid)
    {
        var httpContext = helper.ViewContext.HttpContext;

        // Do something with httpContext...
    }
}

BTW, it sounds like you want to get the URL for something. You know there's already a utility called IUrlHelper?

Sweet, i'm all sorted. will leave this issue open for @manikandan05

Gonna close this, @manikandan05's issue doesn't seem to be related.

Hi @JakeGinnivan, still i'm trying to resolve from my end. i didn't get solution for get the value from IUrlHelper in GetRequiredService<>()

@manikandan05 I suggest you file a separate issue with a good description of what you're trying to achieve and why it's not working. It doesn't seem related to this...

Hi @khellang, i have tried your solution also, but i'm cant escape from this UrlHelper. Now i have the face some other problem.
Please help to find out the solution.
WebApplication4.zip

I'd prefer not to download and unpack a random zip on my computer. Can you post it as a gist or something? Create a GitHub repo?
It would be nice if you could try to explain what you're trying to achieve. Or provide more info on what's wrong. :smile:

Hi @khellang, I have posted my code snippet (gist) in the following online link.
https://gist.github.com/manikandan05/5fa6bc50ae739675834fa75ec5025024

@manikandan05 I've basically give you the solution above. Get the HttpContext from the IHtmlHelper: helper.ViewContext.HttpContext

ok @khellang , After HttpContext, i'm not further using RequestServices.GetRequiredService<>() get the UrlHelper value to call Action(controller,method). This is the issue form my starting point.

@manikandan05 I still can't remember reading what your original issue is. Are you not getting the IUrlHelper from the services? Can't you just create it? new UrlHelper(helper.ViewContext)

Hi @khellang, Thanks for your valuable suggestion. Now i got the solution :smile:
Thanks...


Icon for SettingToggle

Is it possible to have a icon on SettingToggle in the same way that SettingPicker and SettingPage do?
I see you've created #23 that will allow for lots more composability of these views, but I just wanted to double check this wasn't already possible.
Thanks so much for making this btw, I know you're a young guy, and you've got tremendous amounts of talent! You've helped me have better Settings options more my users, and helped me to start implementing SwiftUI in my UIKit app 😊

Yeah, currently not supported - should be an easy addition though. I'll get back to this when I get the time

Hi, do you know when you might get back to this?


Update Azure.AI.Projects entry to set Type column to client

The Azure.AI.Projects entry was updated in this PR yesterday but the Type column was left empty which is why this is showing up under Uncategorized instead of under Cognitive Services.

I'm going to squash and merge. I'd had to manually run azure-sdk - ci against the refs/merge of this PR and it passed.


Use NoopMeterRegistry by default (again)

Motivation:
Using Metrics.globalRegistry can make Server or ClientFactory attempt to
register meters with duplicate IDs.
Modifications:

Use NoopMeterRegistry.get() instead of Metrics.globalRegistry

Result:
Server or Client does not fail due to duplicate meter IDs.

I just realized this may not be a correct fix. Will update.


Error: Formulae found in multiple taps with brew install fully-qualified-name

brew tap Linuxbrew/science
brew install linuxbrew/science/opencv3
==> Installing opencv3 from linuxbrew/science
Error: Formulae found in multiple taps:
 * linuxbrew/science/openni
 * homebrew/science/openni

Please use the fully-qualified name e.g. linuxbrew/science/openni to refer the formula.

This makes no sense since I specified the fully-qualified name.

Furthermore, could we use a different name in the example? because brew install linuxbrew/science/openni leads to a hard-to-install formula:

==> Installing openni from linuxbrew/science
intltool: Unsatisfied dependency: XML::Parser
Homebrew does not provide special Perl dependencies; install with:
  `cpan -i XML::Parser`
systemd: Unsatisfied dependency: XML::Parser
Homebrew does not provide special Perl dependencies; install with:
  `cpan -i XML::Parser`
Error: Unsatisfied requirements failed this build.

NOTE: this seems like a blocker for installing anything from linuxbrew/science
NOTE: moved from https://github.com/Linuxbrew/homebrew-core/issues/1586

It looks like that error message isn't referring to the fully-qualified linuxbrew/science/opencv3 you specified, but the unqualified depends_on "openni" => :optional declared inside the opencv3 formula. That's why openni appears in the message; it's not just an example formula.


Add icons and choosed fonts

Selecting assets
I have chosen the fonts.
I will use the Awesome Font website to grab icons for the webpage.

Good job so far 👍 on choosing the fonts.


Custom export attributes with custom base class fails

In our setup we use this type of construct via Nuget MEF to have shared stuff on the base export attribute.
You can argue that we could do this differently, but nonetheless it works in Nuget MEF :-)
If you have questions or comments, please contact me.

BTW I can see the commit comment on my second commit was a bit misleading. I meant to say "Exports with custom export attribute..."

@nicolaihenriksen feel free to force push to correct the commit if you want. I won't be building on your commits at least for several hours, and likely a couple days.

So interestingly enough, it turns out that the crux of the reason for your test to fail is that your derived custom metadata attribute doesn't have a [MetadataAttribute] attribute affixed to it. MEFv2 didn't require it, but VS MEF did. Adding that attribute to the derived custom metadata class works around the problem.
I've fixed the shortcoming though, so VS MEF with this PR will support what you were trying to do. But I removed your tests in favor of a single line change to our existing tests to exercise this feature.
While at it, I noticed your comment about how MEFv2 doesn't support properties defined on base custom metadata classes. I also noticed we already had a test for this, but it was disabled for VS MEF because VS MEF did not share that shortcoming. However, since the goal is for VS MEF to read MEFv2 attributes the same way MEFv2 would (with a few exceptions) I also "fixed" VS MEF to have the same shortcoming, and enabled the test we already had to assert this.

Codecov Report

Merging #48 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #48   +/-   ##
=======================================
  Coverage   82.12%   82.12%
=======================================
  Files          73       73
  Lines        5711     5711
  Branches      881      881
=======================================
  Hits         4690     4690
  Misses        790      790
  Partials      231      231

Impacted Files
Coverage Δ

...mposition/Configuration/AttributedPartDiscovery.cs
95.65% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Meh, I don't care too much for emulating MEFv2's limitation regarding properties on custom metadata attribute base types. I'm going to keep VS MEF superior in that regard.

@AArnott  Great!! Is there a CI build available now, or do I have to wait until the PR is completed?
I guess I can just add the [MetadataAttribute] attribute and go from there until I have a new CI package to work with...

Is there a CI build available now, or do I have to wait until the PR is completed?

Not yet. We have AppVeyor set to not publish packages for PRs. I expect this PR will complete in the next couple business days.
But ya, you can just add the [MetadataAttribute] to workaround it for now.


to_json/from_json format suggestion

Hi!
I have a suggestion regarding evm::to_json, evm::from_json JSON formatting.
At the moment, to deserialize an Account object from JSON file, you have to provide it in the following format:
{
            "address" : "0x100",
            "balance" : "0x100000000000000",
            "nonce"   : 0,
            "code"    : [0]
}

All is fine for address and balance, for the nonce I have to provide an integer instead of integer string, and for the code I have to provide array of values.
The last thing looks very inconvenient because most of the tools (solc, web3 console at least?) output code part of an address in a hex string, so we have a compatibility issue here.
What do you think about making the code field a hex-string compatible? I mean, is there any special arguments against it? The same goes for nonce, actually.
If you don't mind, I would make it on my own producing pull request afterwards.
Thanks!

Hi,
You're absolutely right - both of these should accept hex strings!
Looks like we got away with this because nothing is actually using the to_json conversion for evm::Accounts. The parseAccount function in tests/harness.cpp should be using this (its parsing from json in the format you describe, with hex-string nonce and code), but is instead manually converting each field.
There are helpers in include/util.h which should be used here: 'to_bytes' and 'to_uint64'.
If you could create a PR fixing this, I'd be very grateful.
Thanks!

Yeah, thanks for clarification!
I think the reason you have resorted to manually creating objects in parseAccount is that
EVM tests are formatted in a special way: the address of account is specified in the name of
the object, while other fields are its attributes.
Have a look (taken from vmRandomTest.json)
 "pre": {
    "0x0f572e5295c57f15886f9b263e2f6d2d6c7b5ec6": {
       "balance": "0x0de0b6b3a7640000",
       "code": "0x7745414245403745f31387900a8d55",
       "nonce": "0x00",
       "storage": {}
      }
}

On the other hand, evm::from_json(const nlohmann::json& j, Account& a) expects the JSON object to contain the "address" field.
In harness.cpp, the parseAddress function is used exactly for those 'pre' and 'post' objects,
so this makes evm::from_json a little bit inappropriate in this setting.
At the moment, I see such options here:

We can artificially add "address" field to the json object in parseAddress(), and then pass it
into from_json(). This may introduce extra copy, because we have const_iterator passed into parseAddress().
Contrary, we can change from_json according to described tests format.
In harness.cpp, we can leave things as they are, but nevertheless change accounts.cpp. This options does not introduce uniformity, in my opinion.

What do you think?

Rather than injecting the address field into the json object, I think it would be neater to try to parse the Account object from the existing json with all the other fields, and then insert the address from the iterator key. Something like:
parseAccount(...)
{
  auto account = it.value().get<Account>();
  account.address = from_hex_str(it.key());
  return {account, j["storage"]};
}

The intermediate copy of the Account object should be cheap where any json manipulation may not be. from_json function will also need to be a little more robust, assigning from "address" (and other keys) if they exist, but simply ignoring them if not present.

Yeah, didn't know about json::get<T>() function, looks nice.
The only thing I feel sad is that if we construct Account using from_json but some fields are missing, then we potentially would have undefined values, and we never know that it is so afterwards. I don't have any suggestions regarding this, because, afaik, it is a common thing in C++ programs.
I am thinking about adding a test that will check to_json, from_json mutual compatibility. For example, initialize Account using from_json, convert that account into json using to_json, and check that both jsons are comparable. What do you think?

Those fields won't be dangerously undefined - the default constructor for an Account will call the default constructor for an Address, which will just set the address field to 0.

Yeah, but is it also true for balance and nonce?
Generally speaking, I would ask myself if it is a good thing to construct
an object without providing all the values at once.
I think, it can backfire if you , for example, serialize a half-initialized
Account object and pass resulting JSON to someone who will deserialize it
later and use it in its own application/logic.
пятница, 9 августа 2019 г. пользователь Eddy Ashton <
<EMAIL_ADDRESS>написал:

Those fields won't be dangerously undefined - the default constructor for
an Account will call the default constructor for an Address, which will
just set the address field to 0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.<
https://ci5.googleusercontent.com/proxy/msUn4HmkexZV8aoefq2o3pdZD-RhqBOw4h8oRzYzM9GQnwMcRXcwnllpUFBSADhxu0ixB-K0Qb15t84-PPrfERUCFs9XtX3Ks6h93cYW5zdri5mRtWXflueVS6pA1ILYWCrQ85AmYcEWv-wcrXdfIg2HXbF9PZ6t1AHYgwg9EtMlN_CvO2cN4GIgdB2eT5bYeAWiB8ItTSqYB5r3wnEO-tn3a-AnRTeyHyMUjXJZ4Q=s0-d-e1-ft#https://github.com/notifications/beacon/AIS5XW7LE254WNIHQMI7ZHLQDWSS3A5CNFSM4IKTR5J2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD37JMTY.gif>

Sorry, I was unaware of the fact that uint256_t relies on cpp_int  under the hood, which defaults to zero (C++ is not my native language at the moment).
Still, the nonce is left uninitialized when default constructor is used?

Should this test pass?
TEST_CASE("from_json, to_json tests")
{
  Account acc1, acc2;
  nlohmann::json j;
  evm::to_json(j, acc1);
  evm::from_json(j, acc2);
  CHECK(acc1 == acc2);
}

As for now, it doesn't because of uninitialized nonce.

We can ensure the nonce (and other fields) is always initialised by setting a default value:
struct Account
{
    Address address = {};
    uint64_t nonce = {};
    uint256_t balance = {};
    Code code = {};

(This is the same as writing uint64_t nonce = 0, but the uniform initializer {} should work for every type)
That test should pass, and I believe with the current code it will? to_json should always write all 4 values, producing a json object with address, balance, nonce, and code fields. from_json should convert that json object back to an identical Account, but will also accept json objects which are missing those fields.
The json::get<T>() function uses argument-dependent lookup to find the from_json function for the specified type, but in most cases the same lookup should be done for the assignment operator:
Account a1;
nlohmann::json j = a1;
Account a2 = j;

So you should never need to call to_json or from_json directly. (I prefer auto a2 = j.get<Account>() because it is explicit, and removes compiler errors in a few places where the assignment would otherwise be ambiguous).

Yeah, this looks very C++-11 -ideomatic. Lets discuss further details in the PR.

This is now fixed. Closing...


No warning when getting built in Callable from Dictionary

Tested versions
4.3.dev [b04263644c3307b8b4a20838cd48f3c19692f1d2]
System information
Godot v4.2.stable - Windows 10.0.22621 - GLES3 (Compatibility) - Intel(R) Iris(R) Xe Graphics (Intel Corporation; <IP_ADDRESS>55) - 12th Gen Intel(R) Core(TM) i5-1235U (12 Threads)
Issue description
A GDScript feature was recently added (https://github.com/godotengine/godot/pull/82264) that allows methods of built-in Variant types to be accessed as Callables. For example the feature makes the following code work.
var vec: Vector2 = Vector2(1.5, 2.5)
var callable: Callable = vec.ceil
print(callable.call()) # prints (2, 3)

This is a great feature, except there are cases where it could lead to potential confusion.
var dict: Dictionary = {&"clear" : randf}
var callable: Callable = dict.clear # does this refer to randf or the built in clear method?
callable.call()
print(dict) # does this print a blank dictionary or the original dictionary?

I'm not entirely sure what the best solution is, bet as the title suggests, it might make sense to emit some kind of GDScript warning when the user creates or accesses a key that has the same name as a built in method.
Steps to reproduce
Run the script above.
Minimal reproduction project (MRP)
N/A

This is a great feature, except there are cases where it could lead to potential confusion.
var dict: Dictionary = {&"clear" : randf}
var callable: Callable = dict.clear # does this refer to randf or the built in clear method?

Note that the feature currently skips dictionaries for compatibility reasons. Both dict.clear and dict["clear"] refer not to the method, but to a key (regardless of whether it exists).
Problems:

Lack of a convenient way to construct a Callable for Dictionary methods in GDScript. The most expected syntax would be dict.clear, but this is ambiguous with keys and breaks compatibility. See also the Rocket Chat discussion starting from the comment. Possible options:
1.1. (Breaks compatibility) Always treat dict.clear as Callable and dict["clear"] as a key (if missing, it produces an error). Both dict.not_a_method and dict["not_a_method"] are treated as keys. This is not the worst option, since the behavior does not depend on whether the key is in the dictionary or not. Also, this does not break compatibility for keys whose names do not match the methods.
The only downside is that adding a new Dictionary method may break compatibility when using .attribute syntax (but not ["index] syntax). But for objects, we are constantly adding new properties/methods and do not consider this as breaking compatibility.
1.2. (Breaks compatibility) Other ways with behavior depending on the presence of the key in the dictionary. I think that all the ways break compatibility, but also behavior depending on the key list of the dictionary is rather bad. Let me know what you think about it.
1.3. Some new syntax. In my opinion this is unjustified.
1.4. Leave as is.

Lack of any way to construct a Callable for Dictionary methods in GDScript. We could add an ad hoc solution like Dictionary.get_method(), but I think we should solve problems 1 and 3, or at least just 3, instead.

Lack of a universal way to construct a Callable for an arbitrary Variant (without checking the value type). I think one possible solution would be a Callable(Variant, StringName) constructor (currently there is only Callable(Object, StringName)). But this is problematic to bind since the existing system expects specific Variant types. Another option is a static method (like Callable.create()), this shouldn't be a problem.

First, a quick question about compatibility considerations. Although (https://github.com/godotengine/godot/pull/82264) has been merged, I wonder since it is only in a dev build whether the policy around compatibility breakage is less strict.
I definitely agree that the behavior shouldn't depend on what keys are in the dictionary. Of the options you listed, I like 1.1 the best. The only other alternative I can think of is to emit a warning whenever "clear" is used as a key in a dictionary, but I'm not sure it's much better than 1.1.
For problem 3. Callable(Variant, StringName) certainly makes the most sense to me semantically. I don't quite understand the issues with binding it. Also, is there really no universal way to construct a Callable for an arbitrary Variant?. Can't I do func(): my_variant.my_func()?

I don't quite understand the issues with binding it.

I looked at this issue. A suitable binder class is not implemented, it may be non-trivial to do as far as I remember. Also, I'm not sure whether the problem could be that the signature Callable(Variant, StringName) includes Callable(Object, StringName), i.e. call Callable(object, "method") will match two overloads at once.


Click propagated to underlying element when exiting fullscreen

Hello,
I'm having an annoying issue with fullscreen in mobile devices.
When exiting fullscreen by clicking the appropriate button, the thing that will appear behind the button gets clicked as well! (I tested with Firefox and Chrome, Android 10, but also in desktop Firefox with dev tools)
In my case, it is the home link, so the user gets teleported away 😭
An example page: https://sanmichelealfiume.it/archivio/201229224009_giorgi.jpg_details
The corresponding JS code: https://sanmichelealfiume.it/archivio/actions/javascript.js
Did I do something wrong?
Thanks!

Hello! Doesn't seem like something you did wrong… Perhaps a bug in OpenSeadragon?
Is it still happening? I tried to reproduce on Mac Chrome and Firefox, but when I hit the "leave full screen" button it just exits without doing anything else.

Hello! Doesn't seem like something you did wrong… Perhaps a bug in OpenSeadragon?
Is it still happening? I tried to reproduce on Mac Chrome and Firefox, but when I hit the "leave full screen" button it just exits without doing anything else.

Hello! Thanks for your reply.
I still have the problem. To be clear: I know it happens in Android phones, I guess it may appear in all mobile devices as well but I don't have an iPhone to check.

Hello! Thanks for your reply.
I still have the problem. To be clear: I know it happens in Android phones, I guess it may appear in all mobile devices as well but I don't have an iPhone to check.

@serl
If you have time, could you please try the OpenSeadragon library build here
Although that patch doesn't change anything specific to full-screen, the updated event handling (coming v2.5.0) may fix the issue


RFC: introduce a patches file in /nix-support/

Motivation for this change
This is more of a request for comments than an actual PR, I would like to collect some feedback in order to find ways to scan for vulnerabilities in a live system without the need to have derivations available in the nix store.
Vulnix is a great tool in the Nixpkgs development context but when we want to use it for automating scans of live systems where derivations aren't necessarily available it becomes a bit tricky. An example of such systems is machines that are deployed with NixOps where the derivations are built in a deploy server or machines that rely on a binary cache to substitute paths.
The idea in this PR is to introduce a patches file that would be created under /nix/store/<hash>-<pkg-name>/nix-support/; in such a file we would dump the list of patches filenames. Afaik, Vulnix already relies on the assumption that CVE patches would have a filename that mentions the CVE id, from the README:

vulnix will inspect derivations for patches which supposedly fix specific CVEs. When a patch filename contains one or more CVE identifiers, these will not reported anymore. Example Nix code:

patches = [ ./CVE-2018-6951.patch ];

So we can follow the same approach for Nix store paths and teach Vulnix to look for the patches file under nix-support to auto-detect security fixes
cc: @ckauhaus
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Not sure why this is needed, because those file names are already accessible through the derivation value itself, pkgs.mxisd.patches -> [ /home/infinisil/src/nixpkgs/pkgs/servers/mxisd/0001-gradle.patch ]

@Infinisil If you have an installed package there is no way to get that. What you suggested is the same as the current situation which is parsing the derivation.

Ah I see. You can still do this though:
$ nix show-derivation $(nix-store -q --deriver \
  /nix/store/681354n3k44r8z90m35hm8945vsp95h1-glibc-2.27) \
  | jq '.[].env.patches'
"/nix/store/r0rc2prwi70hgw4jray5a8sd41fhvjm7-rpcgen-path.patch /nix/store/pp29isd0nvy4jrm9q2f92pjlc83xwa0i-nix-locale-archive.patch /nix/store/5212825a2npxaf7qd81sxfrqq6219rlx-dont-use-system-ld-so-cache.patch /nix/store/mnglr8rr7nl444h7p50ysyq8qd0fm1lm-dont-use-system-ld-so-preload.patch /nix/store/za0pg7fmysrcwrqcal26fnmzw6vycgdn-fix_path_attribute_in_getconf.patch /nix/store/xkd50xxii6k7l1kmw4l5x6xzbhamcs87-allow-kernel-2.6.32.patch /nix/store/nqa9d4yxz1l2cgswzqr1pkm4jfrksm0q-locale-C.diff /nix/store/7kw224hdyxd7115lrqh9a4dv2x8msq2s-fix-x64-abi.patch"

@Infinisil the whole point is to not require derivations to be available :)
Your example still makes the assumption that you can pull the glibc derivation which is not always possible as I mentioned in the PR description

Oh right, I forgot that .drv's aren't always present.
So the main use case for this is for end users being able to check what patches their software has?

@Infinisil yeah. For me the idea is to use Vulnix to automate vulnerability scans of live systems.
I want to be able to do vulnix -S --json on a machine that is deployed from nixops and substituting most of the packages.

I'm :+1: on this idea then :)

Changed from draft to ready to review to get automatic reviewers.
Would be good to get @ckauhaus's opinion still as the Vulnix maintainer.

No objections from my side. This scheme would require a bit of code chang though (vulnix currently relies only on .drv files), but this is quite manageable in my opinion.

rebased onto staging since there is some positive comments that this makes sense

in such a file we would dump the list of patches filenames.

For that to be useful it would need to be the store paths. We don't really want to keep those on the system as they're build-time inputs.
I think this approach is incomplete, and think we better put effort into supporting pure evaluation so the expressions can be stored.

Why do we need full store paths ? we just need the CVE identifiers to know if a CVE is patched or not.

Alright, I had missed the following part:

CVE patches would have a filename that mentions the CVE id

That changes it.

Can you explain a bit more what you're trying to suggest, I don't see at all what does pure evaluation has to do with the context of this PR.

You mentioned you don't always have the Nix expressions available for a certain machine. There are ways to include those, so you could eval then after all. Unfortunately, the current solution is not very good, and so we should use pure eval.

@FRidh I don't want to rely on the evaluation/derivations for the context of this PR/problem, I want to be able to login to a server and run a security check with the available store paths whether they're substituted or not.
If I have a certain store path which is used in my current system closure, say /nix/store/<hash>-openssl and which was substituted from some binary cache i.e I don't have the derivation that created it; for a security check and given the current assumption that CVEs are patched with certain filenames it would be cool if I can just check the package directory for a file that lists the patched CVEs. That way I don't care how it was created, which nixpkgs channel or whether it's using an overlay/overrideDrv, and I can just check without needing to know the steps to produce the same derivation.
I hope I made myself more clear, let me know if that was your understanding as well.
And yeah the current solution isn't really the best, but it's building on top of what Vulnix now does which in my opinion makes it even more harder to do vulnerabilities scans of live systems by requiring derivations to be available, also relying on derivations won't differentiate build time dependencies from runtime dependencies so you can get false positives when a build time dependency is reported when it's not really used in the final runtime closure. So this approach will make it at least more accurate to avoid false positives.
I'm open to other ideas if that solves the above issues that I have now with the Vulnix behavior :)

bump :arrow_up:

See also #39392 for discussion on how to put structured information on applied patches directly into a package's Nix expression.

Yeah at the very least that stuff should be in its own output, but I am also skeptical of us not being able to do something with eval-time metadata or drvs.

@ctheune Comments?

I haven't been following the discussion on pure evaluation but my gut feeling tells me that the idea of adding structured metadata to the output is a good idea. This is also something that the Python community in their packaging has been banging their heads on and they're moving towards structured, static metadata attached to package releases instead of having to evaluate (untrusted) Python code in some location. Obviously Nix is in a better spot here, but still, my intuition tells me that this might become an ever-repeating corner case issue so I'd be in favor of computing static metadata and attaching that to the output.
The format ($out/nix-support) might need to be thought of a little bit more: Who manages that namespace? Should we use multiple files or a single file? Is the intended consumer better served using a structured format like JSON?
We might want to start with something like what we have now and then deprecate or evolve the format later (adding a version identifier early on could be helpful for consumers).
One specific note on this patch: AFAICT this only includes the metadata on the dev output, but IMHO those should be present in all outputs.

Nix already has a way to keep the structured metadata: keep-derivations = true.
Because patches are referred in derivations they will be present there as well and so this issue is covered there.

Right, however, I'm not sure whether that helps - you can create stores that will never have the derivations in the first place and thus it's not an issue of preventing GC but getting them in the first place ... or did I get that wrong?

True, you can do that. Maybe Nix could have an option require-derivations, although I can imagine that to give trouble as well.
As soon as we have structured attributes, the stdenv could have an output "drv" into which we would copy the .attrs.json.

Can we revisit this? cc @nikstur (discussions on SBOM at sprint)

@RaitoBezarius Yeah SBOMs would be the right way to go forward with this, I don't know if they were a thing in 2019 when I initially created the issue :D but it certainly is what I wanted to have. SBOM+VEX is probably the thing we need for nix packages, it can be also an artifact that is part of the store path output ?

Sounds like CycloneDX would be the ideal fit. It is an easy to read JSON and can be BOTH a SBOM and a VEX (and many more things) at the same time. We could either expose the SBOM as a passthru argument/derivation or include it in the output of the derivation. You can then use a tool like bombon (which I have written) to collect the SBOMs of the dependencies and assemble them into a single document for an arbitrary closure.

I don't really get the point of this.
If you have an output path on a system but not the accompanying derivation, you're likely managing that system remotely and in that case you have the nix expressions handy.
If you have the need to audit your systems, you should use the Nix expressions directly. The state of a system should always be a direct result of the Nix expressions, so looking at it should contain no more information than was available before which means there's no point looking at it other than to verify it's indeed the result of some Nix expressions.

This is assuming a very Nix expression driven world, but Nix store is a lower level primitive that can be used in more contexts than simply Nix expressions IMHO.
Moreover, not all tooling is going to understand how to derive this information from Nix expressions, having them as part of derivations is a neat way to make them understandable for "simple tooling" (scanners, compliance, etc.).

Then also the patches are put into the dev output which you'll likely not actually have in a system closure as that's part of the build-time closure at best.
Next problem is a minor one but it's still smelly: The patches are now referenced by the dev output which means they become part of its closure. Build-time deps leaking into the output paths doesn't feel right.

Maybe, let's not have patches but SBOMs? Would that solve the smell?

This is assuming a very Nix expression driven world, but Nix store is a lower level primitive that can be used in more contexts than simply Nix expressions IMHO.

I can't imagine how you'd arrive at output paths in any other way than Nix expressions outside of highly experimental tooling. (well, other than using GUIX); not something you'd do in a productive environment that cares about security enough to warrant checks.

not all tooling is going to understand how to derive this information from Nix expressions

If you care about security at all, you should teach the tooling how to get the info from Nix expressions or use better tooling.

having them as part of derivations is a neat way to make them understandable for "simple tooling" (scanners, compliance, etc.).

Good point.
I'm not against optional support for this sort of thing. If you are forced to use bad tooling for security audits etc., there's no other way. I'd be fine with an opt-in flag to store patches, SBOM or whatever lesser source information in the output.
Not on my machine though please. I don't need thousands of useless patches in my closure.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/tweag-nix-dev-update-46/26872/4


napari plugin malfunctioning with time_slicer in the background

Hi @haesleinhuepf ,
I am having problems to make specfic functions available as Napari plugin widgets if these functions are decorated with the time_slicer.frame_by_frame() decorator.
The specific function which is failing is napari_stress.rescale() which is located at napari_stress > src > _preprocess.py. I first thought it was because the functions that convert 4D data to lists of frames couldn't differentiate between 4D 3D data but I fixed this here. I have written tests for this function which pass for 4D/3D data.
However, when I open some timelapse data (for instance this) in Napari and open the function entry from the plugins menu I get an error in the decorator.
Solution
While writing up this issue, I found the error: I annotated the scale factors argument as an array (one entry for every dimension) -
which magicgui cannot handle. Setting the arguments to using a separate scale factor for each dimension solves the issue.
--> PR coming!

Solved in PR #20


Apply bugfix in url regex

apply bugfix from fastify/fast-proxy to correctly handle consecutive slashes in query parameters

Hi @yoosful, thanks for contributing and keeping an eye on backports.
Can you also add the test case as well?
Regards

@jkyberneees done, i've also reflected this review comment for better performance

Hi @yoosful tests are failing with latest addition. Would you like to check?

@jkyberneees sorry, that was my bad. i've run the tests locally and they seem to be passing now

@jkyberneees sweet, thanks for the quick review. may i also ask when you plan to bump the dependencies in fast-gateway?

Hi, as we released the fix as a patch version, it should be sufficient for
users to run “npm update”. New installs will already get the update.
Can you try and let me know?
Kind Regards
On Tue 11. Apr 2023 at 14:48 유용환 @.***> wrote:

@jkyberneees https://github.com/jkyberneees sweet, thanks for the quick
review. may i also ask when you plan to bump the dependencies in
fast-gateway https://github.com/BackendStack21/fast-gateway?
—
Reply to this email directly, view it on GitHub
https://github.com/BackendStack21/fast-proxy-lite/pull/5#issuecomment-1503267106,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7IGXBZHMORKHAGQWXIVJDXAVHKZANCNFSM6AAAAAAWVVJQDI
.
You are receiving this because you were mentioned.Message ID:
@.***>

@jkyberneees you're right, it works like awesome. ty for all your work


Update azurediagnostics.md

@EdB-MSFT
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Made some modification and it's approved.

#sign-off

Not sure what is the right procedure, I thought I need to give the comment and reviewer, or Ed should commit and merge.
Let me know if I need to do something.

completed in another PR
#please-close


Add pne.chat use openai provider

🚀 Feature Request
Add pne.chat() use openai provider to proxy some specified model, eg:
import promptulate as pne

pne.chat(messages="hello", model="gpt-4-turbo")

If developer want to use openai provider by pne.chat(). They can use pne.chat(messages="hello", model="openai/custom-model", model_config={"base_url": "xxxx", "api_key": "xxx"}) to chat with custom model. Model name use openai prefix.
Why?
There are lots of providers use OpenAI SDK to proxy their model, eg:

https://platform.deepseek.com/api-docs/api/create-chat-completion
Original:

from openai import OpenAI

client = OpenAI(api_key="<your API key>", base_url="https://api.deepseek.com")

response = client.chat.completions.create(
    model="deepseek-chat",
    messages=[
        {"role": "system", "content": "You are a helpful assistant"},
        {"role": "user", "content": "Hello"},
  ],
    max_tokens=1024,
    temperature=0.7,
    stream=False
)

print(response.choices[0].message.content)

Expect:
import promptulate as pne

pne.chat(
    messages=[
        {"role": "system", "content": "You are a helpful assistant"},
        {"role": "user", "content": "Hello"},
    ],
    model="openai/deepseek-chat",
    model_config={
        base_url="https://api.deepseek.com",
        max_tokens=1024,
        temperature=0.7,
        stream=False
    }
)

2.https://openrouter.ai/docs#principles

from openai import OpenAI
from os import getenv

# gets API Key from environment variable OPENAI_API_KEY
client = OpenAI(
  base_url="https://openrouter.ai/api/v1",
  api_key=getenv("OPENROUTER_API_KEY"),
)

completion = client.chat.completions.create(
  extra_headers={
    "HTTP-Referer": $YOUR_SITE_URL, # Optional, for including your app on openrouter.ai rankings.
    "X-Title": $YOUR_APP_NAME, # Optional. Shows in rankings on openrouter.ai.
  },
  model="openai/gpt-3.5-turbo",
  messages=[
    {
      "role": "user",
      "content": "Say this is a test",
    },
  ],
)
print(completion.choices[0].message.content)

zhipu

What to do?

Optimize pne.chat() core code.
Add unit test
Add docs and notebook to show how to use custom model by openai in pne.chat()

Attention
In openrouter, openai need to add extra_headers. It's a question to consider.

solve

solve


feat: Support private repository when using kairos-agent bundle-install

Is your feature request related to a problem? Please describe.
When I tried to use bundle to publish software, I found that it had no way to pull images from the private repository.
Describe the solution you'd like
Hope it will be supported when kairos-agent install-bundle：

Provide private repository authentication
Read repository information from the specified configuration file like luet install --config

Additional context
Currently, authentication information cannot be added when luet repo add, I try to make it support：https://github.com/mudler/luet/pull/370
In kairos-sdk：https://github.com/kairos-io/kairos-sdk/blob/d334d86d4369929e47d569d9d8a6eeb4698e55ca/bundles/bundles.go#L287
Is it expected to point the software installation location(--system-target) and repo config to the same location? I think most of the time software needs a separate directory for storage.
In kairos-sdk：https://github.com/kairos-io/kairos-sdk/blob/d334d86d4369929e47d569d9d8a6eeb4698e55ca/bundles/bundles.go#L304

PR was merged, thanks @Bao0ne !
https://github.com/mudler/luet/pull/370
Closing this Issue


Problem with standard value

Hey Manuel,
I'm having an issue with ViewModel in combination with ReactiveArray. For example, I'm having this array:
var userMessages = [{message:'hello',self:true}, {message:'hey, how are you'}];

Now I'm defining a messagebox viewmodel:
Template.messagebox.viewmodel({
messages: function () {
return userMessages.list();
}

});

Template:
<template name="messagebox">

<input type="text" placeholder="{{_ "holder_text"}}" id="message">

    {{#each messages}}
        {{>message}}
    {{/each}}

</template>

Now a single message:
Template.message.viewmodel({
self:false
});

<template name="message">

{{message}}

</template>

This is what happens: Both messages will be displayed with class "me", but only 1 chat message has "self:true" as property. If I add "self:false" to the other message, everything works fine. I'm just wondering why he sets "self:true" for the message without the self property.

The example as you show it doesn't work. This works as expected:
Template.messagebox.viewmodel({
  messages: [{message:'hello',self:true}, {message:'hey, how are you'}]
});

{{> messagebox}}

<template name="messagebox">
  {{#each messages}}
      {{>message}}
    {{/each}}
</template>

<template name="message">

{{message}}

</template>

Mhhh okay, but in my case (just a new example) I got this, each message represents a ViewModel - the left one is correct, but the right one not.
Picture: http://www.tiikoni.com/tis/view/?id=7003070
The collection objects are correct.

So if my checks are right, the problem here was the missing Template.subscriptionsReady.
This one seems to work fine:
{{#if Template.subscriptionsReady}}
                {{#each messages}}
                    {{>message_text}}
                    {{/each}}
{{/if}}

...and this one fails:
  {{#each messages}}
                    {{>message_text}}
  {{/each}}

I just don't understand this behavior.

Make me a github repro that I can clone.
As a side note, I'd put the isMe function in a mixin.
On Jan 16, 2016 7:17 AM, "dnish"<EMAIL_ADDRESS>wrote:

So if my checks are right, the problem here was the missing
Template.subscriptionsReady.
This one seems to work fine:
{{#if Template.subscriptionsReady}}
{{#each messages}}
{{>message_text}}
{{/each}}
{{/if}}
...and this one fails:
{{#each messages}}
{{>message_text}}
{{/each}}
I just don't understand this behavior.
—
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/150#issuecomment-172210903
.

Let me know when you have a repro.


Mirror Wrapper is out of synch

For https://github.com/phetsims/QA/issues/649. Seen on Win 10 Chrome in https://phet-dev.colorado.edu/html/capacitor-lab-basics/1.6.20-rc.3/phet-io/wrappers/mirror-inputs/mirror-inputs.html.
If you drag something outside the the top iframe, let go, then return, the top frame drops the item and the bottom doesn't, leading to an out-of-synch mirror wrapper.

Can also happen with the about dialog so may connect to https://github.com/phetsims/scenery/issues/1218#issuecomment-842493101

Happens in Resistance in a Wire

Happens in Molarity.

Patched in the above 3 simulations. Was this an exhaustive list for what sims had this issue?

I think so, but many couldn't be checked as they didn't load.

For https://github.com/phetsims/QA/issues/653, since some sims don't load the mirror wrapper (I think this is expected) we are unable to confirm those issues for those sims. @jonathanolson how do you want us to handle those sims?

@KatieWoe is there a good way to check deployed sims for this?

If there are links to the deployed versions of the phet-io sims we could go through them

I don't have an easy way to filter to just phet-io links, but here are the links:
acid-base-solutions 1.2 ()

[ ] acid-base-solutions 1.2.25

area-builder 1.1 ()

[ ] area-builder 1.1.21

area-model-algebra 1.2 ()

[ ] area-model-algebra 1.2.2

area-model-decimals 1.2 ()

[ ] area-model-decimals 1.2.2

area-model-introduction 1.2 ()

[ ] area-model-introduction 1.2.2

area-model-multiplication 1.2 ()

[ ] area-model-multiplication 1.2.2

arithmetic 1.0 ()

[ ] arithmetic 1.0.25

atomic-interactions 1.2 ()

[ ] atomic-interactions 1.2.1

balancing-act 1.1 ()

[ ] balancing-act 1.1.25

balancing-act 1.2 ()

[ ] balancing-act 1.2.4 phet-io
[ ] balancing-act 1.2.4 phet-io Studio

balancing-chemical-equations 1.2 ()

[ ] balancing-chemical-equations 1.2.11

balloons-and-static-electricity 1.3-phetio ()

[ ] balloons-and-static-electricity 1.3.17 phet-io
[ ] balloons-and-static-electricity 1.3.17 phet-io Instance Proxies

balloons-and-static-electricity 1.4 ()

[ ] balloons-and-static-electricity 1.4.15

beers-law-lab 1.4 ()

[ ] beers-law-lab 1.4.19

beers-law-lab 1.6-phetio ()

[ ] beers-law-lab 1.6.16 phet-io
[ ] beers-law-lab 1.6.16 phet-io Instance Proxies

bending-light 1.1 ()

[ ] bending-light 1.1.21

blackbody-spectrum 1.0 ()

[ ] blackbody-spectrum 1.0.8

build-a-fraction 1.0 ()

[ ] build-a-fraction 1.0.13

build-a-molecule 1.0 ()

[ ] build-a-molecule 1.0.3

build-an-atom 1.5-phetio ()

[ ] build-an-atom 1.5.19 phet-io
[ ] build-an-atom 1.5.19 phet-io Instance Proxies

build-an-atom 1.6 ()

[ ] build-an-atom 1.6.16

capacitor-lab-basics 1.6 ()

[ ] capacitor-lab-basics 1.6.20
[ ] capacitor-lab-basics 1.6.20 phet-io
[ ] capacitor-lab-basics 1.6.20 phet-io Instance Proxies

charges-and-fields 1.0 ()

[ ] charges-and-fields 1.0.49

charges-and-fields 1.0-phetio ()

[ ] charges-and-fields 1.0.21 phet-io
[ ] charges-and-fields 1.0.21 phet-io Instance Proxies

circuit-construction-kit-black-box-study 1.1-phetio ()

[ ] circuit-construction-kit-black-box-study 1.1.17 phet-io
[ ] circuit-construction-kit-black-box-study 1.1.17 phet-io Instance Proxies

circuit-construction-kit-dc 1.2 ()

[ ] circuit-construction-kit-dc 1.2.3

circuit-construction-kit-dc-virtual-lab 1.2 ()

[ ] circuit-construction-kit-dc-virtual-lab 1.2.3

collision-lab 1.1 ()

[ ] collision-lab 1.1.1

color-vision 1.1 ()

[ ] color-vision 1.1.25

color-vision 1.2-phetio ()

[ ] color-vision 1.2.17 phet-io
[ ] color-vision 1.2.17 phet-io Instance Proxies

concentration 1.3 ()

[ ] concentration 1.3.21

concentration 1.5-phetio ()

[ ] concentration 1.5.15 phet-io
[ ] concentration 1.5.15 phet-io Instance Proxies

coulombs-law 1.0 ()

[ ] coulombs-law 1.0.10

curve-fitting 1.0 ()

[ ] curve-fitting 1.0.1

diffusion 1.0 ()

[ ] diffusion 1.0.5

energy-forms-and-changes 1.4 ()

[ ] energy-forms-and-changes 1.4.1
[ ] energy-forms-and-changes 1.4.1 phet-io
[ ] energy-forms-and-changes 1.4.1 phet-io Studio

energy-skate-park 1.1 ()

[ ] energy-skate-park 1.1.2

energy-skate-park-basics 1.1 ()

[ ] energy-skate-park-basics 1.1.20

energy-skate-park-basics 1.3-phetio ()

[ ] energy-skate-park-basics 1.3.15 phet-io
[ ] energy-skate-park-basics 1.3.15 phet-io Instance Proxies

equality-explorer 1.0 ()

[ ] equality-explorer 1.0.13

equality-explorer-basics 1.0 ()

[ ] equality-explorer-basics 1.0.13

equality-explorer-two-variables 1.0 ()

[ ] equality-explorer-two-variables 1.0.13

expression-exchange 1.1 ()

[ ] expression-exchange 1.1.15

faradays-law 1.3-phetio ()

[ ] faradays-law 1.3.18 phet-io
[ ] faradays-law 1.3.18 phet-io Instance Proxies

faradays-law 1.4 ()

[ ] faradays-law 1.4.2

forces-and-motion-basics 2.1-phetio ()

[ ] forces-and-motion-basics 2.1.107 phet-io
[ ] forces-and-motion-basics 2.1.107 phet-io Instance Proxies

forces-and-motion-basics 2.3 ()

[ ] forces-and-motion-basics 2.3.17

fraction-matcher 1.2 ()

[ ] fraction-matcher 1.2.2

fractions-equality 1.1 ()

[ ] fractions-equality 1.1.2

fractions-intro 1.0 ()

[ ] fractions-intro 1.0.13

fractions-mixed-numbers 1.0 ()

[ ] fractions-mixed-numbers 1.0.13

friction 1.5 ()

[ ] friction 1.5.11

function-builder 1.0 ()

[ ] function-builder 1.0.24

function-builder-basics 1.0 ()

[ ] function-builder-basics 1.0.15

gas-properties 1.0 ()

[ ] gas-properties 1.0.5

gases-intro 1.0 ()

[ ] gases-intro 1.0.6

gene-expression-essentials 1.0 ()

[ ] gene-expression-essentials 1.0.17

graphing-lines 1.3 ()

[ ] graphing-lines 1.3.11

graphing-quadratics 1.1 ()

[ ] graphing-quadratics 1.1.6
[ ] graphing-quadratics 1.1.6 phet-io
[ ] graphing-quadratics 1.1.6 phet-io Studio

graphing-slope-intercept 1.1 ()

[ ] graphing-slope-intercept 1.1.10

gravity-and-orbits 1.4 ()

[ ] gravity-and-orbits 1.4.1
[ ] gravity-and-orbits 1.4.1 phet-io
[ ] gravity-and-orbits 1.4.1 phet-io Studio

gravity-force-lab 2.2 ()

[ ] gravity-force-lab 2.2.3
[ ] gravity-force-lab 2.2.3 phet-io
[ ] gravity-force-lab 2.2.3 phet-io Studio

gravity-force-lab-basics 1.0 ()

[ ] gravity-force-lab-basics 1.0.3

hookes-law 1.0 ()

[ ] hookes-law 1.0.24

isotopes-and-atomic-mass 1.1 ()

[ ] isotopes-and-atomic-mass 1.1.10

john-travoltage 1.4-phetio ()

[ ] john-travoltage 1.4.17 phet-io
[ ] john-travoltage 1.4.17 phet-io Instance Proxies

john-travoltage 1.5 ()

[ ] john-travoltage 1.5.13

least-squares-regression 1.1 ()

[ ] least-squares-regression 1.1.21

make-a-ten 1.0 ()

[ ] make-a-ten 1.0.17

masses-and-springs 1.0 ()

[ ] masses-and-springs 1.0.11

masses-and-springs-basics 1.0 ()

[ ] masses-and-springs-basics 1.0.10

molarity 1.4 ()

[ ] molarity 1.4.13 phet-io
[ ] molarity 1.4.13 phet-io Studio

molarity 1.5 ()

[ ] molarity 1.5.3

molecule-polarity 1.0 ()

[ ] molecule-polarity 1.0.16

molecule-shapes 1.2 ()

[ ] molecule-shapes 1.2.9

molecule-shapes-basics 1.2 ()

[ ] molecule-shapes-basics 1.2.9

molecules-and-light 1.3-phetio ()

[ ] molecules-and-light 1.3.14 phet-io
[ ] molecules-and-light 1.3.14 phet-io Instance Proxies

molecules-and-light 1.5 ()

[ ] molecules-and-light 1.5.9

natural-selection 1.1 ()

[ ] natural-selection 1.1.2

natural-selection 1.2 ()

[ ] natural-selection 1.2.1 phet-io
[ ] natural-selection 1.2.1 phet-io Studio

natural-selection 1.3 ()

[ ] natural-selection 1.3.1
[ ] natural-selection 1.3.1 phet-io
[ ] natural-selection 1.3.1 phet-io Studio

neuron 1.1 ()

[ ] neuron 1.1.19

number-line-integers 1.1 ()

[ ] number-line-integers 1.1.1

number-line-operations 1.0 ()

[ ] number-line-operations 1.0.2

ohms-law 1.4 ()

[ ] ohms-law 1.4.10

pendulum-lab 1.0 ()

[ ] pendulum-lab 1.0.16

ph-scale 1.3 ()

[ ] ph-scale 1.3.5

ph-scale-basics 1.3 ()

[ ] ph-scale-basics 1.3.5

plinko-probability 1.1 ()

[ ] plinko-probability 1.1.19

projectile-motion 1.0 ()

[ ] projectile-motion 1.0.16

proportion-playground 1.0 ()

[ ] proportion-playground 1.0.16

ratio-and-proportion 1.0 ()

[ ] ratio-and-proportion 1.0.1

reactants-products-and-leftovers 1.2 ()

[ ] reactants-products-and-leftovers 1.2.12

resistance-in-a-wire 1.3-phetio ()

[ ] resistance-in-a-wire 1.3.13 phet-io
[ ] resistance-in-a-wire 1.3.13 phet-io Instance Proxies

resistance-in-a-wire 1.6 ()

[ ] resistance-in-a-wire 1.6.11

rutherford-scattering 1.1 ()

[ ] rutherford-scattering 1.1.10

states-of-matter 1.2 ()

[ ] states-of-matter 1.2.2
[ ] states-of-matter 1.2.2 phet-io
[ ] states-of-matter 1.2.2 phet-io Studio

states-of-matter-basics 1.2 ()

[ ] states-of-matter-basics 1.2.1
[ ] states-of-matter-basics 1.2.1 phet-io
[ ] states-of-matter-basics 1.2.1 phet-io Studio

trig-tour 1.0 ()

[ ] trig-tour 1.0.23

under-pressure 1.1 ()

[ ] under-pressure 1.1.19

unit-rates 1.0 ()

[ ] unit-rates 1.0.18

vector-addition 1.0 ()

[ ] vector-addition 1.0.1

vector-addition-equations 1.0 ()

[ ] vector-addition-equations 1.0.1

wave-interference 2.0 ()

[ ] wave-interference 2.0.3

wave-on-a-string 1.1 ()

[ ] wave-on-a-string 1.1.23

waves-intro 1.1 ()

[ ] waves-intro 1.1.1

They look good


Update flyway-core to 8.2.1

Updates org.flywaydb:flyway-core from 7.15.0 to 8.2.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.flywaydb", artifactId = "flyway-core" } ]

labels: library-update, commit-count:1, early-semver-major, semver-spec-major

Superseded by #592.


Configuration question regarding card-templater

Before you submit a new bug report, please check that

[X] I have read frequently asked questions and limitations

Write your question here
I am trying to follow your directions for setting up a custom card for garbage collection. I am not understanding what the 'sensor.bio' entity is, or where it is derived from:
type: 'custom:card-templater' card:     type: picture-entity     name_template: >-       {{ state_attr('**sensor.bio**','days') }} days     show_name: True     show_state: False     entity: **sensor.bio**     state_image:       "0": "/local/containers/bio_today.png"       "1": "/local/containers/bio_tomorrow.png"       "2": "/local/containers/bio_off.png" entities:     - **sensor.bio**
Are you able to shed some light on this, please?

In this example, sensor bio is the entity created by the garbage collection helper.
This is not essential for this helper to use, it is just an example to illustrate a possible (advanced) use in a dashboard.
If you find it hard to use, just ignore it.


Sync with discourse (Feb 26, 2021)

@r-f-g can you have a quick look? I have removed the domain-name key from clouds.yaml. I think it's not needed, since the project and user domain names already configured the required details.


build fail

Goals
To build the project without error.
Actual Results
/Users/liupeng/Documents/workspace/macstore/PhotoCloud/Carthage/Checkouts/realm-cocoa/Realm/module.modulemap:1:18: error: redefinition of module 'Realm'
A shell task (/usr/bin/xcrun xcodebuild -workspace /Users/liupeng/Documents/workspace/macstore/PhotoCloud/Carthage/Checkouts/realm-cocoa/Carthage/Realm.xcworkspace -scheme RealmSwift -configuration Release ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** BUILD FAILED **

The following build commands failed:
	CompileC /Users/liupeng/Library/Developer/Xcode/DerivedData/Realm-dniksdmiugtvldawcddszgswgzwf/Build/Intermediates/Realm.build/Release/Realm.build/Objects-normal/x86_64/NSError+RLMSync.o Realm/NSError+RLMSync.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

Steps to Reproduce
None provided.
Code Sample
None provided.
Version of Realm and Tooling

Realm framework version: v2.5.1
Xcode version: 8.3
iOS/OSX version: 10.12
Dependency manager + version: ?

Hi @liufsd. Thanks for reaching out. I've edited the issue to follow our format. Please edit it and provide more information including the version of Carthage that you're using as well as any other supporting information that you can offer that would help us reproduce/solve the issue.

i have update my carthage version to 0.20.1
and build success by 'carthage update'
thanks.


Chrome 97 On Android 10 - navigator.userAgentData Undefined

I'm using Chrome 97 on Android 10 (a Samsung Galaxy S9+).  When I enable remote debugging and enter navigator.userAgentData in the Chrome DevTools Javascript console I get a return of undefined.  Am I missing some configuration in Chrome 97 for Android?  CanIUse.com reports that Chrome for Android supports userAgentData as of v90.

Hi Bill
Sorry to hear this isn't working!
I've tried this out in Chrome 97.0.4692.87 on Android 12 but I can't reproduce the error (i.e. it works for me). I don't have a Samsung Galaxy on hand — FWIW I tried an S9+ with DevTools on BrowserStack, and that seemed to work, but that may not be realistic.
I think you should try once more, using navigator.userAgentData from DevTools and, if it still doesn't work, then file a bug via crbug.com/new.
Sam

It would also be helpful if you could share the output from the demo page here: https://user-agent-client-hints.glitch.me/javascript.html
I did notice though, and I'll look into details on this, navigator.userAgentData is only available when you're inspecting an actual web page. So, if you're using the console to inspect something like the new tab page at chrome-native://newtab/ or about:blank then you will get undefined as if you look at the the navigator object in the console, you will see that fewer APIs are available.

And to expand, navigator.userAgentData requires a secure context, e.g. https://…. So, you will not see it available on insecure http:// pages or internal browser pages as well.

@rowan-m, Thanks for the reminder about using https://.  That was the problem.  Everything's working as expected now.

I'm using Chrome 97 on Android 10 (a Samsung Galaxy S9+). When I enable remote debugging and enter navigator.userAgentData in the Chrome DevTools Javascript console I get a return of undefined. Am I missing some configuration in Chrome 97 for Android? CanIUse.com reports that Chrome for Android supports userAgentData as of v90.

#80 #78 #69

Great to hear - let's close here.


Add xtask to generate manpages

For information about the cargo xtask workflow pattern see: https://github.com/matklad/cargo-xtask
This PR adds an xtask crate with only one task, mangen, which generates a ROFF manual page under target/dist/man directory for the vhost-device-sound and vhost-device-scmi binaries.
The manual pages are placed in target/dist/man/vhost-device-sound.1 and target/dist/man/vhost-device-scmi.1.
Future support for other crates in this repository is possible and provisioned for.
Fixes #687
Fixes #697
Demo: Rendered man pages as plain text
Generate the manpages:
$ cargo xtask mangen
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.04s
     Running `target/debug/xtask mangen`
Generated the following manual pages:
/path/to/rust-vmm/vhost-device/target/dist/man/vhost-device-sound.1
/path/to/rust-vmm/vhost-device/target/dist/man/vhost-device-scmi.1

Plain text rendered with:
man -l /path/to/rust-vmm/vhost-device/target/dist/man/vhost-device-sound.1 | xclip

vhost-device-sound(1)
vhost-device-sound(1)                                                                                General Commands Manual                                                                                vhost-device-sound(1)

NAME
       vhost-device-sound - A virtio-sound device using the vhost-user protocol.

SYNOPSIS
       vhost-device-sound <--socket> <--backend> [-h|--help] [-V|--version]

DESCRIPTION
       A virtio-sound device using the vhost-user protocol.

OPTIONS
       --socket=SOCKET
              vhost-user Unix domain socket path

       --backend=BACKEND
              audio backend to be used

              [possible values: null, pipewire, alsa]

       -h, --help
              Print help

       -V, --version
              Print version

VERSION
       v0.2.0

REPORTING BUGS
       Report bugs to the project's issue tracker: https://github.com/rust-vmm/vhost-device

                                                                                vhost-device-sound 0.2.0                                                                                vhost-device-sound(1)

man -l /path/to/rust-vmm/vhost-device/target/dist/man/vhost-device-scmi.1 | xclip

vhost-device-scmi(1)
vhost-device-scmi(1)                                                                                General Commands Manual                                                                                vhost-device-scmi(1)

NAME
       vhost-device-scmi - vhost-user SCMI backend device

SYNOPSIS
       vhost-device-scmi <-s|--socket-path> [-d|--device] [--help-devices] [-h|--help] [-V|--version]

DESCRIPTION
       vhost-user SCMI backend device

OPTIONS
       -s, --socket-path=SOCKET_PATH
              vhost-user socket to use

       -d, --device=DEVICE
              Devices to expose

       --help-devices
              Print help on available devices

       -h, --help
              Print help

       -V, --version
              Print version

VERSION
       v0.3.0

REPORTING BUGS
       Report bugs to the project's issue tracker: https://github.com/rust-vmm/vhost-device

                                                                                vhost-device-scmi 0.3.0                                                                                vhost-device-scmi(1)

I just realized the man pages don't/won't include an EXAMPLES section, oops.
I think we can either do it in this PR or on a followup PR to reduce iterations


Ingester default healthcheck port

Requirement - what kind of business use case are you trying to solve?
Run the jaeger-ingester with sane defaults easily
Problem - what in Jaeger blocks you from solving the requirement?
$ go run cmd/ingester/main.go                                                                                ingester-binaries
{"level":"fatal","ts":1538145911.902807,"caller":"ingester/main.go:66","msg":"Could not start the health check server.","error":"port not specified","errorVerbose":"port not specified\ngithub.com/jaegertracing/jaeger/cmd/flags.(*SharedFlags).NewHealthCheck\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/cmd/flags/flags.go:110\nmain.main.func1\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/cmd/ingester/main.go:64\ngithub.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra.(*Command).execute\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra/command.go:698\ngithub.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra.(*Command).ExecuteC\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra/command.go:783\ngithub.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra.(*Command).Execute\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra/command.go:736\nmain.main\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/cmd/ingester/main.go:124\nruntime.main\n\t/Users/ledor473/bin/go/src/runtime/proc.go:201\nruntime.goexit\n\t/Users/ledor473/bin/go/src/runtime/asm_amd64.s:1340","stacktrace":"main.main.func1\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/cmd/ingester/main.go:66\ngithub.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra.(*Command).execute\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra/command.go:698\ngithub.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra.(*Command).ExecuteC\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra/command.go:783\ngithub.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra.(*Command).Execute\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/vendor/github.com/spf13/cobra/command.go:736\nmain.main\n\t/Users/ledor473/go/src/github.com/jaegertracing/jaeger/cmd/ingester/main.go:124\nruntime.main\n\t/Users/ledor473/bin/go/src/runtime/proc.go:201"}

Proposal - what do you suggest to solve the problem or improve the existing situation?
Add a default healthcheck HTTP port just like Collector and Query
Any open questions to address

Which port should we use?

Which port should we use?

Is it, or will it be, included in the all-in-one? If so, it could be the health-check port that is used there +1 (14270 then)

In time, I'm not implying that the all-in-one would have two health-check ports if the ingester gets added :)

Here's the various default ports:
CollectorDefaultHealthCheckHTTPPort = 14269
QueryDefaultHealthCheckHTTPPort = 16687

I think the all-in-one should include everything, turning on the required components on demand

I see - I agree with what you mentioned earlier then!

As a newcomer, I would expect the "all-in-one" to include "all" components, including the ingester.

eh, I am not convinced of that. The point of all-in-one is to be, well, all in one. Even though we support external storage, it does not break the notion that the rest of Jaeger components are "all in one". But with Kafka ingester it kind of breaks down, since you need another component writing to Kafka. And while it could be the same process both writing and reading Kafka, we're getting into a weird territory.
Another objection is that currently the code is not so well structured as to make the all-in-one easy to maintain with more and more components. It's main is huge compared to others. Unless there's a very strong reason for including ingester there I would rather not do it.
Anyway, I think the question about the health port is answered?  14270?  (I don't really care)


Remove: Google.Chrome version 119.0.6045.106

## Vanity URL - New version (119.0.6045.124) is available in repo

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Microsoft Reviewers: Open in CodeFlow

= = = = = = InstallerUrl does not contain prVersion = = = = = =
7:18:44: Google.Chrome prVersion 119.0.6045.106 is less than ManifestVersion 119.0.6045.124
Thanks for helping to clean up old vanity URLs.


github-runner: 2.319.0 -> 2.319.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for github-runner is: Self-hosted runner for GitHub Actions
meta.homepage for github-runner is: https://github.com/actions/runner
meta.changelog for github-runner is: https://github.com/actions/runner/releases/tag/v2.319.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.319.1 with grep in /nix/store/rc1qr3y8hjr6a9g12j0xnxfzlj7gwlw3-github-runner-2.319.1
found 2.319.1 in filename of file in /nix/store/rc1qr3y8hjr6a9g12j0xnxfzlj7gwlw3-github-runner-2.319.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

github-runner

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rc1qr3y8hjr6a9g12j0xnxfzlj7gwlw3-github-runner-2.319.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A github-runner https://github.com/r-ryantm/nixpkgs/archive/43064d95b8784d326c86067fc808a2ceae7d1818.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/43064d95b8784d326c86067fc808a2ceae7d1818#github-runner

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rc1qr3y8hjr6a9g12j0xnxfzlj7gwlw3-github-runner-2.319.1
ls -la /nix/store/rc1qr3y8hjr6a9g12j0xnxfzlj7gwlw3-github-runner-2.319.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

github-runner

Maintainer pings
cc @veehaitch @newAM @kfollesdal @aanderse @zimbatm for testing.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 335501 run on x86_64-linux 1

1 package built:

github-runner