Types import issue

looks like that the typescript package will be wrong generated.
in https://github.com/commercetools/commercetools-sdk-typescript/tree/master/examples/me/server
@commercetools/sdk-client-v2/src/types/sdk is not working only via dist folder.
not clean variant: @commercetools/sdk-client-v2/dist/declarations/src
If it is possible, I guess it makes sense to change the path into @commercetools/sdk-client-v2/types

ok, so means to run the examples it needs to change it? or needs to execute something before?
examples/me/server/src/utils/auth/auth.ts
examples/me/server/src/utils/auth/tokenProvider.ts

ok, so means to run the examples it needs to change it? or needs to execute something before?
examples/me/server/src/utils/auth/auth.ts examples/me/server/src/utils/auth/tokenProvider.ts

You don't need to work with those file. All you need to do is follow the instruction in the README.md file to run the example application.
Cheers 🥂

Well that is the point it runs into an issue like described. However, works for me after the change.

I just tried it and could reproduce your issue when working with a clean repository. When running yarn install in the repository root the described issue is gone.

@jenschude This happens because the repository is a monorepo, if you try importing a package which is part of the monorepo, it will want to use the local version instead of pulling it from npm.

This error should now be fixed.


Release new version

Since last update on https://www.npmjs.com/package/redis this library got many more comments and PR merged do you have plans to update npm package ?.
What is the status on this ?.

No update on this?

+1

@bengl

I would need someone who sponsors my work to properly continue working on node_redis. I would love to do that but so far this is my main constraint to continue everything. It is just very time consuming. If there's anyone who would be willing to sponsor me, that would be great! I am happy not only to continue supporting everything depending on the sponsoring but also to implement new features.

@BridgeAR - ok completely understood, but the only extra work being requested here is changing one line of code.  I'll submit the pull request right now.  I am seeing a lot of popular repositories responding with the same answers.

@BridgeAR Could npm fund at least help get the word out (though it looks like it would require at least one new release)?
https://dev.to/ruyadorno/npm-6-13-0-7f3

Have started a conversation here about this: https://github.com/NodeRedis/node_redis/issues/1040#issuecomment-581418899

Hey, v3.0.0 is now published to NPM; https://github.com/NodeRedis/node-redis/releases/tag/v3.0.0


Creating issue template

I like to create a GitHub issue template for this repository.
Because maybe we want to know

A used internal qemu version
Used docker or docker compatible software (podman, singularity) and the version.
Which compatible images are used, or own image with qemu-user-static
What command was executed.
What the expectation and actual result are.

https://help.github.com/en/articles/about-issue-and-pull-request-templates
https://help.github.com/en/articles/creating-issue-templates-for-your-repository
I think below is a good example about the content though it is a old version of the template.
https://github.com/containers/libpod/blob/master/.github/ISSUE_TEMPLATE.md
Below is a case for the new version.
https://github.com/WorksOnArm/cluster/tree/master/.github/ISSUE_TEMPLATE
Shall we create it?
I believe this makes our work better.

If you like, I can sent pull-request for that.


Feedback: Tutorial 2018

Please provide your feedback in the comments.
After one week, hardly anyone had completed the Tutorial. Apparently, some people thought they should stop after installing an IDE, without actually practicing to use it? Despite all my cautionary tales about clueless IDE users, they were planning to remain clueless. Luckily, the first classroom session is planned after the second week.
After the second week, participants reported efforts from half an hour to over an hour. About 15 minutes of that for the actual debugging and coding, the rest for environment and IDE setup.
During the Sockets classroom exercise (#70), IDEs were a major problem again. One student suggested to drop the IDE altogether and just go with the command line.
I'll change the Tutorial to de-emphasize IDEs, see #72.

The table of contents for the Tutorial currently starts...

Prerequisites
Setup
Exercise
...

Maybe "Exercise" was understood to mean "classroom exercise", and that's why people stopped after the setup. I'll rename that section to "Tutorial Exercise" to make it clear.


Roll forward "Don't outline splat constants."

This reverts commit c4e0f3b01a874e1bb0b3d3b71d54d5b70f3129e6 to roll forward https://github.com/google/iree/pull/6816, now that https://github.com/google/iree/pull/7370 has landed and unaligned buffer fills are supported by the compiler and runtime.
I tested this sequence of changes with the person_detect program mentioned at https://github.com/google/iree/pull/7370#issuecomment-952379671 and https://github.com/google/iree/pull/7462#issuecomment-952332376, but we don't yet have complete test coverage in the main IREE repo.

We can also monitor https://github.com/google/iree-samples/blob/main/tflitehub/mobilenet_quant_test.py after the change makes to the snapshot release. (test hung indefinitely with unaligned splat fill_buffer before the reversion c4e0f3b )

Yep! I wasn't able to repro that one (couldn't figure out how to run the program with or without these changes)

We can also monitor https://github.com/google/iree-samples/blob/main/tflitehub/mobilenet_quant_test.py after the change makes to the snapshot release. (test hung indefinitely with unaligned splat fill_buffer before the reversion c4e0f3b )

Yep! I wasn't able to repro that one (couldn't figure out how to run the program with or without these changes)

I "think" you can replace iree-translate in iree-samples.venv/bin/ with the one built with changes. The python package is just a wrapper around the binary. The change is on the compiler side and should not affect the runtime tools.

FYI, https://github.com/google/iree-samples/blob/main/tflitehub/mobilenet_quant_test.py runs fine with https://github.com/google/iree/releases/tag/snapshot-20211104.628 with the commit included. Thanks for the change!


django-allauth upgrade integration fixes

Upgrades to our drupal oauth allauth provider and adapters to work with the upgraded version of allauth

Spurious token failure seems to happen about 5-10% of the time.


Heatmap on ScrollView

Hello,
I tried to put a heatmap on a ScrollView, but it doesn't work...

Share your code.


Refactored ReadMe

This PR:

Removes the Getting Started section, as it's redundant with the Learn More Section.
Moves the Contact Us section to the end of the file.
Removes the links for Subscribe and mail. The underlying links do not redirect me anywhere, and thus I feel they are not needed.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @damccorm


Add MySQL types and generate JSON tags

Map MySQL types to Go types

bit -> bool
date -> *time.Time

Add JSON tags to structs generated for MySQL

I have no problem merging this -- but can you do a couple things:

Add the json tags to the other *.type.go.tpl files as well. After I merge this commit, I will also add an option to disable the json tag generation (or something else), but I'd like the types to be consistent

Please collapse the commit history to a single commit (git rebase -i)

Thanks!

@kenshaw added json tags to the other tpl files but I'm not set up to test those DBs.

I've merged this, however I do believe the bit addition for MySQL is incorrect. I believe it should be a []uint8, with a special case when the column precision is 1. This also needs to be fixed in the other databases. I didn't catch this originally, as I don't personally use bit column types.
I'm in the middle of 2 fairly large rewrites, one not related to this, and another that is related to better standardizing the type parsing. I should have those changes done relatively soon, and will push them out when available.

BTW, thanks for the submission!

I agree about the bit type. It didn't look like the precision making it down to the type conversion function though. Should I wait for the rewrite or is it worth looking into fixing it in the interim?
You're welcome and thank you for making this tool available.

I believe all of the various database Loaders produce the database datatype (dt) in the format of type(precision) but I could be wrong (or the MySQL schema query isn't returning that).
You're more than welcome to work on it more and submit other pull requests, as I haven't started the rewriting of the type parsing.

You're right. I didn't see the ParsePrecision call.


Work Initiated , Support Page

Started Basic work on support page
Website optimisation is kinda tricky (will do later (NEXT YEAR!!! 😆 ))

Is the Deployment Disabled, other contributors help if you visit this comment!!

@ritikZ18  this includes security and deployment criteria checks to ensure that the website remains secure, performs optimally, and maintains stability. These checks are designed to prevent site crashes, minimize loading times, and address any potential vulnerabilities during deployment.


Using custom kernels in Falkon

Hey,
After checking kernel.py, I think it should be possible to write a custom kernel and use it in Falkon, but I'm not sure about the conditions under which I'll get proper speedups using my custom kernel. Let me elaborate on the kernel that I have:
Suppose that given a pair of datapoints (x1, x2), my kernel is deterministic, meaning that I have a function to compute k(x1, x2) directly (not super fast, and not trivial to compute, but deterministic). Thus, I think in this case, no training (.fit) is needed in Falkon, am I right? Moreover, I'm not able to write the KeOps  routine to compute my kernel (thus, if I use DiffKernel as my parent class, I'm not able to write _keops_mmv_impl, and I have to set KeOps to False).
I'd like to know if in such a case, do I need to compute the full n^2 kernel matrix to compute the KRR predictions, or my space and time complexity will be O(n sqrt(n))?
P.S: In my case, kernel computation is expensive and I'd like to minimize the number of kernel computation calls.
Thanks for the great work!

Hi,
I recently did a lot of refactoring of the kernel classes. In particular there is a notebook on how to implement a custom kernel [https://falkonml.github.io/falkon/examples/custom_kernels.html] ! Try to pull from master and have a look, especially kernel.py.
You do not need to use DiffKernel (unless you want the autodiff capabilities), but just Kernel.
You'll need to implement the compute function, which essentially takes a few data-points and computes a kernel matrix.
Let me know if you run into memory issues (that's the tricky bit I haven't expanded on in the notebook).
For KeOps support, you can also try to ask the KeOps people on gh. but note that if your data is high dimensional (d > 100) KeOps may not help much...


3 *7lucjlo0t6 by EUPHXRIA

Song Name

3 *7lucjlo0t6

Artist Name
EUPHXRIA
Source
Youtube
Youtube Link
IR2kd_kDD7sdtjnF
Direct File Link
No response
Song ID
1
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 102688428

I hope this sound is accepted :)

reject
invalid YouTube link


Can this document be updated with the steps for a newer version of Ubuntu?

[Enter feedback here]

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

ID: 24f0c76a-39ec-6205-7913-f9bd66b6bfaa
Version Independent ID: 30ef4b8e-16eb-ebdc-e9c8-6127463e629f
Content: Analyze Azure network security group flow logs - Graylog
Content Source: articles/network-watcher/network-watcher-analyze-nsg-flow-logs-graylog.md
Service: network-watcher
GitHub Login: @damendo
Microsoft Alias: damendo

@hughesst , thank you for your feedback. I see you already have raised this request before # https://github.com/MicrosoftDocs/azure-docs/issues/102594 and it is assigned to our Product Group team for review.
Once the PG team reviews the request, they will provide an update on that issue.
Since this is a duplicate request, we are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Add files to logical folders

Is your feature request related to a problem? Please describe.
There is a way to Add and Move projects to logical "folders" on a solution, however there is no way to add existing files into it.
Describe the solution you'd like
Right clicking on an existing folder, it should provide an option to include existing file or create a new one,.
Describe alternatives you've considered
Opening the solution file on Visual Studio 2022 and adding files, or manually editing the sln file.
Additional context

This issue https://github.com/dotnet/sdk/issues/9112 may perhaps be related? Because as far as I'm aware not even the .NET CLI currently let's you add solution items?

Currently you can add  a project to the solution and them drag it and drop inside a solution folder.
Or if you are creating a new project, you can specify the folder in the last step...

@fernandoescolar Not talking about projects, this issue is related to "Solution Files".

In the last version (v0.6.2) you can add existing files to your solution folders. And you can drag and drop them between different solution folders :).


Fix Typo In Hello World Example

The cfg in the example referenced blanked-impl-comp when it should have been blanket-impl-comp.

Thank you! Good catch :)


Rename gernerate_max_key_length.php to generate_max_key_length.php

Where is this file called? I couldn't find any uses in the codebase?

@GrahamCampbell Sorry for the delay. I only needed the function to generate a list of max length chars, so that we know how often we need to iterate over a string for a specific language. And I did this only for strings bigger than 3 chars, so that we do not have a breaking change. ⇉ in short: I saved the output here (https://github.com/voku/portable-ascii/blob/master/src/voku/helper/data/ascii_language_max_key.php), so that we do not need to calculate it on runtime.

Cool. Maybe a quite note in the contributing docs could help. :)


How to use in side a functional component

Hey,  how would I would use this inside a functional component instead of class component, I am new to this but I guess I cant access this in a functional component and don't understand how to access the Notification component to trigger the show method.

Sort of figured it out I used the useRef hook.


Middleware Arguments Access

Hi, how can I access route's args in my middleware?
Here's how I am adding the middleware:
$route->add(function ($request, $response, $next) use ($mw) {
    return $mw->middlewareFunc($request, $response, $next);
});

Currently, in order to get the arguments, I do this manually (it works, but I wish this was built in in Slim):
$path = strtok($_SERVER['REQUEST_URI'], '?');
$path = str_replace(SUB_FOLDER, '', $path);
$pathArr = array_values(array_filter(explode('/', $path)));
/* remove from args array the known routes (user, category, product etc.)
* loop through all routes and delete all the non-variables (non {}) */
foreach ($this->routes as $route) {
    $routeUrl = array_filter(explode('/', $route['url']));
    foreach ($routeUrl as $key => $url) {
        if ($url[0] != '{') { // this is not an arg
            if (isset($this->prefixes[$key])) {
                if (!in_array($url, $this->prefixes[$key])) { // we don't already have this prefix
                    $this->prefixes[$key][] = $url;
                }
            } else {
                $this->prefixes[$key][] = $url;
            }
        }
    }
}
$args = [];
foreach ($pathArr as $key => $value) {
    /* remove prefixes from url in the right position */
    if (!isset($this->prefixes[$key])) {
        $args[] = $value;
    } else {
        if (!in_array($value, $this->prefixes[$key])) {
            $args[] = $value;
        }
    }
}

return $args;

Like this:
$route = $request->getAttribute('route');
$route->getArguments();
// or
$route->getArgument('argumentName');

Great, thank you very much.

@silentworks I think we should mention this in docs, because it's common question.

@dopesong good point, you wanna PR it or I will add it later on in the week.

@silentworks https://github.com/slimphp/Slim-Website/pull/68/files

Done


Is there a description of the different error/exit codes?

Is there a documentation over the different error/exit codes that dependency check uses?
It could be handy to know what the error/exit code means when trying to figure out what goes wrong.

These have not been documented - because in general you need the output/log to understand the error. In general, an error log message is written out when the error code is set:
https://github.com/jeremylong/DependencyCheck/blob/main/cli/src/main/java/org/owasp/dependencycheck/App.java#L167

not that I can think of. You could use the --exclude option.

yes, I have, was just hoping I could do that over properties, then I could just change the property file and get all the builds to ignore the git directory instead of going into each build and add the --exclude option and in some cases need to keep in mind on the max number of options that ms-cmd allows.
As you already answered my original question, I'll close this one.


Main is now targeting .NET 7

This is a heads up that the primary repos of the stack have branched for .NET 6 GA/servicing/RCs, and that the main branch for those repos has become .NET 7.
Anything special to note about .NET 7?
The biggest difference between .NET 6 and .NET 7 flow is that the SDK repos will have their own channel (.NET 7.0.1xx SDK) from the very beginning. While .NET 6 had this channel, we never used it in development. For .NET 7 we will have a runtime and SDK channel from the beginning. Having this split also makes it easier to identify potentially problematic stack dependencies.
What does this mean for the repos I'm using?
If you're using any of the repos below, then: the main branch has been updated to target .NET 7 or .NET 7.0.1xx (for SDK repos).

Repo
Channel

dotnet/aspnetcore
.NET 7

dotnet/efcore
.NET 7

dotnet/emsdk
.NET 7

dotnet/icu
.NET 7

dotnet/runtime
.NET 7

dotnet/windowsdesktop
.NET 7

dotnet/winforms
.NET 7

dotnet/wpf
.NET 7

mono/linker
.NET 7

dotnet/installer
.NET 7.0.1xx SDK

dotnet/roslyn
.NET 7.0.1xx SDK

dotnet/sdk
.NET 7.0.1xx SDK

dotnet/templating
.NET 7.0.1xx SDK

There are quite a few other repos that were targeting .NET 6 that are not part of the main product flow. Their config might need to be tweaked by the repo owners to do the right thing depending on their development schedules:

aspnet/AspLabs
dotnet/command-line-api
dotnet/format
dotnet/hotreload-utils
dotnet/iot
dotnet/llvm-project
dotnet/msquic
dotnet/runtime-assets
dotnet/scaffolding
dotnet/test-templates
dotnet/wcf
microsoft/vstest
xamarin/xamarin-android
xamarin/xamarin-macios

.NET 7 and .NET 6 RC 2 info will be added soon to dotnet/installer.

How can i figure out about new features from dotnet 7 ?

Check out themesof.net, specifically https://themesof.net/roadmap?product=.NET&release=7.0


When can I expect production release of v8.4.0-alpha.1?

I need to use TypedClient in my production environment.
Could you please let me know by when this alpha release v8.4.0-alpha.1, be made a production release?

Hi!
While I cannot give you a fixed date, I can say this should happen soon.


[SMALLFIX] Use static imports for standard test utilities in alluxio/core/client/fs/src/test/java/alluxio/client/file/FileSystemContextTest.java

change import org.junit.Assert; to import org.junit.Assert.fail;
modify all assert.fail(* to fail(*
Put the static imports before non-static imports.

alluxio-bot, check this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3526/
Test PASSed.

alluxio-bot, merge this please


fix: ignored error

The goal is that err at line 141 is filled with last error and not nil.
https://github.com/go-gitea/gitea/compare/master...sapk-fork:return-err?expand=1#diff-f94444002d94f8c2766292e69cefbee2R141

Codecov Report

Merging #8550 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #8550      +/-   ##
==========================================
- Coverage   41.74%   41.74%   -0.01%
==========================================
  Files         526      526
  Lines       68403    68403
==========================================
- Hits        28557    28554       -3
+ Misses      36203    36197       -6
- Partials     3643     3652       +9

Impacted Files
Coverage Δ

routers/api/v1/repo/file.go
71.31% <0%> (ø)
:arrow_up:

models/repo_indexer.go
68.36% <0%> (-1.82%)
:arrow_down:

modules/migrations/migrate.go
21.22% <0%> (-1.68%)
:arrow_down:

modules/migrations/gitea.go
10.25% <0%> (-1.5%)
:arrow_down:

models/repo_list.go
73.17% <0%> (-0.98%)
:arrow_down:

models/repo.go
48.89% <0%> (-0.06%)
:arrow_down:

models/error.go
33.33% <0%> (+1.25%)
:arrow_up:

modules/task/migrate.go
28.2% <0%> (+3.84%)
:arrow_up:

models/unit.go
67.56% <0%> (+5.4%)
:arrow_up:

modules/indexer/indexer.go
55.26% <0%> (+10.52%)
: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 de4f10b...288e65e. Read the comment docs.


triton.language.sum is incorrect with tensor which is float16 dtype

In a specific case, triton.language.sum is not correct with float16 tensor. But there is no issue with float32 tensor.
You can reproduce this issue by following below steps.

git clone https://github.com/kakaobrain/trident.git
cd trident
git checkout triton/issue_1960
export PYTHONPATH=${PYTHONPATH}:${pwd}
pytest -k test_kernel

You can find a test case at here and a sum kernel at here.

This issue is resolved. The reason of incorrect result is the precision. Use float32 internally to calculate sum.


[Testbed validation] Error during ACDC submission

Hi @ticoann ,
I've just found an issue in cmsweb-testbed ReqMgr. I was trying to create an ACDC workflow and
when I hit "submit" button a pop-up comes out with this message:
{"exception": 400, "message": "Create request failed, 'ResubmissionWorkloadFactory' object has no attribute 'requestName'", "type": "HTTPError"}
It seems we've removed this attr in the later releases and I believe the error is in this line:
https://github.com/dmwm/WMCore/blob/61be1750aadabae7c14c14246e732d5ac5b74de4/src/python/WMCore/WMSpec/StdSpecs/Resubmission.py#L35
shouldn't it be originalRequestName?
Thanks

Hi Alan, actually code in testbed is this one.
https://github.com/dmwm/WMCore/blob/1.0.3.pre10/src/python/WMCore/WMSpec/StdSpecs/Resubmission.py
It seems the error is on the validation, it looks like validation code ran before request name is created.
How do you create the ACDC? are you using wmstats interface or script?
Could you send me the command you are running to create ACDC?

I'm using WMStats, you can try creating ACDC for this one (testbed):
amaltaro_700_pre11_ZJetsLNu_LHE_v1_150121_162739_7178

Hi Alan, I was able to test the fix. It seems it is at least creating the workflow. Thank you for all your help.
I will create the new tag and request the testbed update. Is there anything else need to be updated.
I set the latest version on https://reqmgr2-dev.cern.ch/


Is all of functionality now in base or other packages for Julia 0.4

I am just starting to move some of my code from Julia 0.3 to the new 0.4 release.  When I discovered NumericExtensions in 0.3 it dramatically sped up some of my code.  I noticed that NumericExtensions does not work with 0.4 and then I saw multiple posts on the git site and Julia-Users suggesting it was just a stopgap until 0.4 came out and that some of the stuff in NumericExtensions was put in base or other packages like StatFuns.
After a bit of searching I was able to find one of those functions in Base and I looked at StatFuns but I could not find any others.  My question is have all of the equivalent functionality been moved to base and/or other packages or just some of it?  If not, is there a generally way with respect to changes in 0.4 to reproduce some of it without being an expert (particularly for functions like wsumfdiff)?  Below are the functions I have used and what I have found in base and the functions or equivalent functions I have not found yet.
Here are the functions that I have been using:
Found:
sum(Abs2Fun(),x)
found equivalent with sumabs2 in base in reduce.jl
Not Sure:
sum(LogFun(),x)
I am not sure if sum(log(x)) is now the same or as fast as sum(LogFun(),x)
Cannot Find:
wsumfdiff(rcp!(x),Abs2Fun(),yperm,that)
cannot find the equivalent of rcp!  which is equivalent to x<- 1./x
cannot find the equivalent of wsumfdiff or wsumsqdiff
I found sqL2dist(a,b) in Statsbase but I am not sure if you can or how to incorporate weights
I am sorry for the noise if the answers to this have already been posted somewhere that I have not found.

I looked at the sqL2dist function in StatsBase and thought I could modify it to include a weight to make it equivalent to wsumsqdiff in NumericExtensions.  Below is the original sqL2dist function from deviation.jl of StatsBase then a modification to incorporate weights and then another modification that incorporates the inverse of a vector for the weights (my use case).  I would like to know if these look reasonable (i.e. as fast an efficient).  I am not asking to merge these into Statsbase or anything like that but to determine if this would be equivalent to wsumsqdiff?
As a side note,  I wasn't sure if if should have a separate S<:Number for the w variable instead of use the same T<:Number used for a & b is the input may be an integer or a float separate from variables a and b.
I also wrote (macro) instead of the "at" symbol to avoid pinging anyone with that user name.
squared L2 distance
function sqL2dist{T<:Number}(a::AbstractArray{T}, b::AbstractArray{T})
n = length(a)
length(b) == n || throw(DimensionMismatch("Input dimension mismatch"))
r = 0.0
for i = 1:n
(macro)inbounds r += abs2(a[i] - b[i])
end
return r
end
here is my modified version:
squared L2 distance with weights i.e. sum( w[i] * abs2(a-b)  )
function wsqL2dist{T<:Number,S<:Number}(a::AbstractArray{T}, b::AbstractArray{T}, w::AbstractArray{S})
n = length(a)
length(b) == n || throw(DimensionMismatch("Input dimension mismatch"))
length(w) == n || throw(DimensionMismatch("Input dimension mismatch"))
r = 0.0
for i = 1:n
(macro)inbounds r += w[i] * abs2(a[i] - b[i])
end
return r
end
Here is my version that incorporates the inverse (1/w) of the weights:
squared L2 distance with inverse weights i.e. sum( (1/w[i]) * abs2(a-b)  )
function winvsqL2dist{T<:Number,S<:Number}(a::AbstractArray{T}, b::AbstractArray{T}, c::AbstractArray{S})
n = length(a)
length(b) == n || throw(DimensionMismatch("Input dimension mismatch"))
length(w) == n || throw(DimensionMismatch("Input dimension mismatch"))
r = 0.0
for i = 1:n
(macro)inbounds r += (1/w[i]) * abs2(a[i] - b[i])
end
return r
end

If found that in 0.3 my wsqL2dist function was on par with wsumsqdiff. However if found that if I write:
function sumlog {T<:Number}{a::AbstractArray{T}}
r = 0.0
for i = 1:size(a,1)
(macro)inbounds r += log(a[i])
end
return r
end
this sumlog(x) function take about about 60% of the time that sum(log(x)) does.


⚠ Bofrost.de has degraded performance

In cf4d566, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1298 ms

Resolved: Bofrost.de performance has improved in 9305dfc.


Update k8s tests and libraries to v1.27.0-rc.0

Signed-off-by: Chris Tarazi<EMAIL_ADDRESS>

Closing in favor of #24837


Fix cooking sizzle noise

About the PR

I noticed the sizzle noise when cooking meat wasn't playing. This PR fixes that.
Technical details

We were trying to play a sound based on an entity about to be deleted (raw meat -> cooked meat). This uses the same solution from PlaySoundBehavior for DestructibleSystem where we use the current location rather than the entity which might be deleted soon.
Since construction graphs regularly replace one entity with another (and don't tend to move while being constructed), it made sense to use this new behavior in all cases, but I could also create a new IGraphAction for this case if that is better.
Media

https://github.com/user-attachments/assets/9257236c-b81b-4f54-891b-c3a0baf8217c
Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

cl not needed

Test failure looks unrelated?

Test failure looks unrelated?

Yeah, that one randomly fails sometimes. I will re-run them for you.

Why not have it so it plays that sound whenever there's meat on it?

Why not have it so it plays that sound whenever there's meat on it?

That's a nice idea for an improvement. I had just been thinking about fixing the existing behavior. I can look into this too.


Tried to update from 0.2 to 0.3

Problem 1
- Can only install one of: evenement/evenement[v2.0.0, v1.0.0].
- Can only install one of: evenement/evenement[v2.0.0, v1.0.0].
- react/zmq v0.3.0 requires evenement/evenement ~2.0 -> satisfiable by evenement/evenement[v2.0.0].
- Installation request for react/zmq 0.3.* -> satisfiable by react/zmq[v0.3.0].
- Installation request for evenement/evenement == <IP_ADDRESS> -> satisfiable by evenement/evenement[v1.0.0].
Regards

I'd like to get the next release out and believe this has been answered already, so I'm closing this for now. :shipit:
Please come back with more details if this problem persists and we can reopen this :+1:


feat: crv incentives for crvUSD vault epoch 5

Context
LlamaRisk crvUSD Vault (Epoch 5) - 29,000 CRV over 4 weeks

start:<PHONE_NUMBER>n, // Fri Sep 20 2024 17:05:08 GMT+0000
end:<PHONE_NUMBER>n, // Fri Oct 18 2024 17:05:08 GMT+0000

Merge conditions checklist

[x] Ensure there is at least one week between the PR submission and the start of the Program(s).
[x] Send funds to the URD; the PR will only be merged after the funds have been received.

Important: If the delay between the PR creation and the start of the Program(s) is less than one week, or if we do not see any funds sent to the URD, the PR will not be merged, and the Program(s) will not be created.

Funds sent to urd: https://etherscan.io/tx/0x7a7cff32d8a97e5d0ff51fb589868465c8d85ed551f3bce5d9ee1e26e8efb01f
Ready to merge

Thanks again @0xValJohn! Really nice PR description and tx link that helps a lot 🙏


Cache build_docker_image step when used repeatedly in a prefect deploy

If N deployments have a build step that builds the same image, the image will be built N times.
Docker will cache layers, but it would be nice to avoid even running the step when we know its been done before.
Not saying this is the right solution, but one could imagine something like lru_cache directly on the build_docker_image step function itself, allowing it to be skipped after the first invocation in given prefect deploy

Yes, same issue here, we have many deployments involving the same "large" docker image in our case, and it seems wasting quite a lot of time the more deployments we have using the same image. (even if all the layers are cached)
I second this :-)


Fix license

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Hmm, linter still not happy. Let me find a recent recipe with GPL-3 and copy the values there. :thinking:


Instagram API Announcement - how it will impact on instafeed?

I have reveived this email

Hi Instagram Sandbox Developer,
We have recently announced new features to the Instagram API and are upgrading it to Facebook's Graph API. We encourage you to check out the exciting announcement shown here: https://business.instagram.com/blog/new-instagram-api-features/. With these new implementations, we will only be allowing and reviewing new applications for the basic permission level of the existing Instagram API (instagram.com/developer).
Starting October 1st, developers will no longer be able to apply to access any permissions other than the basic permission via the existing API. Since you are in sandbox mode, this means that you are in development so we highly encourage you to submit your API application before the end of September if you are interested in accessing more than the basic permissions.
For more information on the new Instagram Graph API, including the new permissions and what they can offer your product, please navigate to the facebook.com/developer site.
Thanks,
The Instagram Platform Team

A bit concerned as well 😟

@PrestaShark Are you sure this is real and not some spam email? What's the reply-to address?

@sidan5 I think it's pretty serious.

@richjdsmith Saw it only after log out...
That's a bad move :(

I hope this is not too off topic, but is using this script to simply show an instagram feed on a html website dead with this new API. Besides, I can't even get past registering a new client because the re-captcha fails and some imaginary data that is not completely filled in. And yeah, no issues on using this script have been resolved for ages. Dead fish in the water?

@alFrame Today I had all of those problems. First I fixed by registering my app in a incognito window (with Chrome, details here) and now I can't get the instafeed to work, seems like the API has changed something that made this plugin to break.

@Dannymx Thanks for chiming in. I tried to register in incognito mode in Chrome on Windows. And tried it in any other browser on Windows and Mac (not Chrome on Mac though). To no avail. That form is broken.
And you say the plugin is broken too now? Is there any intention of the team behind this plugin to fix it (hope hope)?
How on earth can we implement a specific users Instagram feed on a manually coded website then? It's a breeze using WordPress, but I kinda stepped away from WordPress for simple websites. The maintenance with updates and everything became a hassle...
Anyone good some good advice on this?

@alFrame, I read somewhere that someone managed to register it via Firefox on Windows.
I've written here all I know about current situation  https://stackoverflow.com/questions/46635195/how-to-access-instagram-feed-of-any-user-with-new-graph-api

@markfinst thanks! It Worked in a FireFox private window... Thought I tried that, but apparently not. So much about sing and dance... sigh...

I thought I post here again that after being able to register a client with Instagram and figuring out how to get my userId (RTFM) I am actually able to get the script to work. Seems that the new API does not have that much implication on the functionality of instafeed.js.
That said, I would like to thank everybody who contributed to this script and this thread!

Still on the registering issue @alFrame, were you able to get the script running simply using a cliend_id? It seems that option is not available anymore on the API, only by using oAuth right?

This is the code I got it running with:
var userFeed = new Instafeed({
  get: 'user',
  userId: 'number you get from here: https://smashballoon.com/instagram-feed/find-instagram-user-id/ or the first group of numbers in the access token, until the period ',
  accessToken: 'acces token you get form registering the app with instagram',
  sortBy: 'most-recent',
  limit: limitWidth,
  resolution: 'low_resolution',
  template: '<div>... customize to your needs</div>'
});
userFeed.run();

@alFrame How did you get the access token?  I wasn't allowed to register the app w/ Instagram

I got it through in FireFox on windows in a private window... Launched FireFox private window with no other instance open.

You can attach ?__a=1 to your instagram Link to load JSON content. example: https://instagram.com/eightyfourrooms/?__a=1
{
  user: (...), # <- contains media/nodes
  logging_page_id: "..."
}

@dec23rd1986 Register your application at https://www.instagram.com/developer to get your client ID then follow all the instructions at https://www.instagram.com/developer/authentication/ to get your access token. It involves posting to https://api.instagram.com/oauth/authorize/?client_id=CLIENT-ID&redirect_uri=REDIRECT-URI&response_type=code with your info where it's all caps, and then after this in terminal, making a request as follows (again with your info where the caps are. The code is what you get a the end of the URL once you follow the step above) :
curl -F 'client_id=CLIENT_ID'
-F 'client_secret=CLIENT_SECRET'
-F 'grant_type=authorization_code'
-F 'redirect_uri=AUTHORIZATION_REDIRECT_URI'
-F 'code=CODE'
https://api.instagram.com/oauth/access_token
Follow the instructions at https://www.instagram.com/developer/authentication/  and you'll get there.

My summary of the steps to do:

Login instagram developer.
Create a managed client with redirect_uri http://localhost and uncheck Disable implicit OAuth.
Open this url in browser (replace the placeholder [CLIENT_ID_HERE]) https://instagram.com/oauth/authorize/?client_id=[CLIENT_ID_HERE]&redirect_uri=http://localhost&response_type=token
The token is in the redirected link. User id is the beginning part of the token( user_id = token.split('.').first).


Use GitHub Actions?

Hi,
Please use GitHub Actions to build automatically the application, e.g. https://medium.com/rkttu/write-your-github-actions-workflow-for-build-windows-application-94e5a989f477
Thank you.

Besides actions it necessary to create cert and publish signed binary.


feat(#277): Remove Code Duplication Between References

In this PR I combined Linked, Reference and Duplicate classes into a single well-tested class.
Closes: #277.

PR-Codex overview
The focus of this PR is to refactor code in the opeo package.
Detailed summary

Removed Linked.java and Reference.java
Modified StoreArray to handle opcodes differently
Updated Invocation to handle arguments
Refactored Constructor to handle different nodes
Implemented Root to return opcodes
Updated NewArrayAgent to handle array construction
Updated tests for ArrayConstructor
Refactored InvokespecialAgent to handle different nodes
Updated XmirParser to handle references
Added tests for Duplicate
Updated StoreToArrayAgent to handle array storage

The following files were skipped due to too many changes: src/main/java/org/eolang/opeo/ast/Duplicate.java, src/test/java/org/eolang/opeo/decompilation/DecompilerMachineTest.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@volodya-lombrozo Thank you for your contribution! We appreciate your effort, but there are a few areas for improvement. You've earned +5 points: +20 base, -7 for excessive hits-of-code (566 ≥ 200), -15 for missing code review, and -5 for insufficient comments (only 2). We encourage you to focus on quality and ensure proper code review in future submissions. Keep up the good work, and don't hesitate to ask for guidance. Your current balance is +201.


[4.0] Crashed when GDScript 2.0 export  property with get and set

Godot version:
master [4.0-commit 76c308f47bb53d16de39b62b55ac27ee44b03440]
OS/device including version:
Windows 10, GTX 2070
Issue description:
When add @export to a property with set and get in gdscript 2.0, it crash like this:
@export var test_var = 20:
	get:
		return test_var
	set(value):
		test_var = value

Steps to reproduce:
Open the demo project, open Node3d.tscn, then it alert crashed.
Minimal reproduction project:
TestExport.zip

Duplicate #42463


[DO NOT MERGE] Create snapshot of hooks work for easier review.

This is a snapshot of #959, separated out so that I can get feedback on the design without drowning in the bajillion file changes in the main PR.
This PR contains changes to the helper methods and ShopperBaskets, and contains a new Test API that's a copy of ShopperBaskets, if you want to review without the diffs.

Over time, the implementations of query and mutation hooks have gotten a bit convoluted, and support has been added for features that we no longer deem necessary. This PR aims to simplify the signatures of the hooks and clean up the internal logic used.
As a result, query hooks now follow a pattern similar to:
const {
  data // Basket only, returning Response is no longer supported
} = useBasket(
  apiOptions // passed through to commerce-sdk-isomorphic
  queryOptions // passed through to @tanstack/react-query
)

Mutation hooks have also been simplified:
const { mutate } = useShopperBasketsMutation('createBasket') // Only takes the mutation name, now
mutate(apiOptions) // passed through to commerce-sdk-isomorphic

Under the hood, I've moved as much logic as I could from the endpoint hooks into the useQuery and useMutation helpers, to reduce repetition.
I've also refactored the query update logic. That must be implemented manually for each endpoint, so I've moved it out of the mutation.ts file, which is generated, and into a new config.ts file (per API, i.e. peer of mutation.ts). I've moved a lot of things around between the various locations (updateCache, useMutation, and the per-API methods), to hopefully simplify the interface as much as possible, and I've DRYed up some repeated logic.
In addition to cleaning up / fixing types, I made two major changes to query keys / cache updates: First, query keys previously only used parameters set on the options, but parameters can also be set on the config. So I've updated the logic to merge config/options before generating query keys / cache lookups. Secondly, we previously had cache lookup logic that accepted a query key, and created a lookup function from that. I've refactored the code so that we provide the lookup functions directly, which we can build from composable helpers. This provides us much more flexibility.

Description

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

(change1)

How to Test-Drive This PR

(step1)

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

Great work on the refactoring, a few comments. I understand that you refactored the useQuery in a way to make it more flexible and less repetitive, but I find that the new signature is less readable. In comparison before and after refactoring, the line of code we have in each hook (e.g useBasket) ends up having more lines of code than before, same with useQuery. This is due to the fact we have to pass argument and config from hook to useQuery for heavy duty. I find if we let the hook handle a bit of argument verification, we can have a simpler implementation.
Also, I'd like to respect the signature of current useQuery because it is readable, and it is mimicking react-query useQuery, which we most familiar with
export const useBasket = (
    apiOptions: Argument<Client['getBasket']>,
    queryOptions: Omit<UseQueryOptions<DataType<Client['getBasket']>>, 'queryFn'> = {}
): UseQueryResult<DataType<Client['getBasket']>> => {
    const {shopperBaskets: client} = useCommerceApi()
    const method = (arg: Argument<Client['getBasket']>) => client.getBasket(arg)
    const requiredParameters = ['organizationId', 'basketId', 'siteId'] as const
    const parameters = mergeOptions(client, apiOptions)
    const queryKey = [
        '/organizations/',
        parameters.organizationId,
        '/baskets/',
        parameters.basketId,
        // Full parameters last for easy lookup
        parameters
    ] as const
    return useQuery(queryKey, method, {
        enabled: hasAllKeys(parameters, requiredParameters),
        ...queryOptions
    })
}

export const useQuery = (
    queryKey,
    queryFn,
    queryOptions
) => {
    // const netOptions = mergeOptions(hookConfig.client, apiOptions)
    const authenticatedMethod = useAuthorizationHeader(queryFn)
    return useReactQuery(
        // End user can override queryKey if they really want to...
        queryOptions.queryKey ?? queryKey,
        () => authenticatedMethod(apiOptions), // method that wrapped in useAuthorizationHeader
        queryOptions
    )
}

Closing as this is pretty out of date and #959 is fairly stable at this point.


List exercise test

Coverage increased (+10.0%) to 86.471% when pulling 1374ea3ebc03793b5f92ac7dc009c78bdee9a757 on list-exercises-tests-mikko into cb0e37eeb31cc2b4df88d187cbf88d694319aac6 on master.

LGTM.


run on mac success but need some modification in executable path

ffmpeg
cd ~/Downloads
curl -LOC - https://evermeet.cx/ffmpeg/ffmpeg-6.0.zip
unzip ffmpeg-*.zip

stellarium
cd ~/Downloads
curl -LOC - https://github.com/Stellarium/stellarium/releases/download/v23.3/Stellarium-23.3-qt6-macOS.zip
unzip Stellarium-*.zip
mv Stellarium.app /Applications/
open /Applications/Stellarium.app

kalstar
cd ~/Downloads
git clone https://github.com/beltoforion/kalstar
mkdir -p ~/.stellarium/scripts

edit kalstar.py for the path apps
        proc_stellarium = subprocess.Popen(['/Applications/Stellarium.app/Contents/MacOS/stellarium', '--startup-script', '/Users/your_mac_user/.stellarium/scripts/kalstar.ssc', '--screenshot-dir', self.__frame_folder], stdout=subprocess.PIPE);

        proc = subprocess.Popen(['/Users/your_mac_user/Downloads/ffmpeg',

run app
cd ~/Downloads
python3 kalstar/kalstar.py -t "Paris, France" -lat 48.8566 -long 2.3522 -d 2020-01-01 -az 90 -alt 25 -fov 70 \
-fps 30 -ts 1 -dt 30 -o ~/Downloads/out.mp4

suggestion

for different os perhaps need some parameter for executable app,
e.g.
kalstar.py -stelarium_path /bin/stellarium -ffmpeg_path /bin/ffmpeg
or
make another files,
e.g.
kalstar_ubuntu.py, kalstar_mac.py, kalstar_windows.py

note
already report about user must create directory manually ~/.stellarium/scripts,
but still not fixed tested on both ubuntu n mac
best regards

Unfortunately I cannot support Mac's. I'm willing to merge any PR addressing this issue provided it does not break the script on other systems. But personally I don't have a mac and i'm not inclined to invest time into supporting something i don't use and cannot test.

same file (kalstar.py just different the executable path for mac n linux)
same argument
python3 /mnt/c/kalstar_linux.py
-t "Nairobi, Kenya" -lat -1.2921 -long 36.8219 -d 1948-12-22 -az 90 -alt 25 -fov 70
-fps 10 -ts 2 -dt 10 -o /mnt/c/out.mp4
python3 ~/Downloads/kalstar_mac.py
-t "Nairobi, Kenya" -lat -1.2921 -long 36.8219 -d 1948-12-22 -az 90 -alt 25 -fov 70
-fps 10 -ts 2 -dt 10 -o ~/Downloads/out.mp4
different (os and apps version,
ubuntu use stellarium 0.20.4, mac 23.3,
ubuntu use ffmpeg 5, mac version 6
have different result in time
in ubuntu the video duration 1:12
while in mac < 1 minute
not sure, the problem in ffmpeg different version
or
stellarium different version
or
in os
the result generated with ubuntu uploaded on my youtube channel
https://www.youtube.com/watch?v=18_wm9s8ZFk&list=PLQLwDsJdI4wtGMMLhUfe2o4kL26V4Rk2_

closed; Its pretty obvious that if the script creates different results with different Stellarium versions the reason for the behavior is probably a change in Stellarium. This is outside of the scope of this script.


How to support .NET 4.7.2 and is it injectable

Hello,
Could you explain me quickly how I would do to bring support to .NET 4.7.2 ?
Also, if I want to hook the CompileMethod in another process, would it work to embed it into a dll, and inject this dll. Hook.hook would then be called at loading using this hack( C# equivalent of dllMain).
Thank you :)

@maddnias Up ?

Ok, 2 things, first you don't answer to issue, it's your choice, I'm still thankful that you provided your code, however, a little support would take you much time. Secondly, your commented code in Test doesn't work and will never work like this: because the HookedCompileMethod will be called in turn, creating an infinite loop which ends by a stack overflow... And a little note in the comments indicating this problem wouldn't be bad and prevent people for trying to make it work


Begging you for not changing release artifacts name so wildly

I'm using scoop, a package manager for Windows, I wrote manifests for Thorium. I enjoy it so much.
I'm have problems automating getting recent releases.
In previous releases, I obtain version from tag_name, filter it with regex, here's example:

key
value

tag_name
M126.0.6478.231

regex
M([\\d.-]+)

version
126.0.6478.231

url
https://github.com/Alex313031/Thorium-Win/releases/download/M$version/Thorium_AVX_$version.zip

actual url
https://github.com/Alex313031/Thorium-Win/releases/download/M$version/Thorium_AVX_126.0.6478.231.zip

And now, it's, TOTALLY BROKEN because the artifact names becomes so *CENSORED* strange just like thorium_Th24_BETA2_126.0.6478.251.zip
just wondering wtf is this why doing this, now there is no easy way to use the autoupdate feature so I have to update version manually
I don't know if you would change the pretty random naming rule, like using [Semantic Versioning](https://semver.org/), if not simply close this issue

I'm not sure why you define this as "wildly"? th24 is our recent work to fix some issues with the cr23 style, and there may continue to be versions marked as th24-beta until we consider th24 to be stable.
If you don't care about some of the issues with the cr23 style, you can completely ignore these th24-beta versions

I mean, the naming rule, is wild

If you feel this is not good enough, do you have a better naming scheme for this situation?

following previous naming syntax is enough; I also mentioned Semantic Versioning

This should be harmless since I'm not asking to change branch or tag names, or the release *title*.
If the project is using CI building, it's also a good practice.

The th24-beta version may still not use the previous naming scheme. As for semantic versioning, I will discuss it with Alex. @

Also, Alex and I don't care about GitHub CI, which doesn't help much for the Thorium project.

Then how do you build releases? in my case CI is really helpful when building things, I can take a break while it's running xD

The windows version of Thorium is basically compiled by me on my windows or linux machine, without using GitHub CI.
GitHub CI is not really suitable for compiling a large project like Chromium.

I'm quite annoyed stucking at old version and drank an overdose of coffee, causing Tachycardia and headache, so very for being emotional and impolite :(

Agree. so slow and difficult to solve building errors.
Thanks again for creating this project.


Issue/8008 resource scheduler polishing

Description
Polished the resource scheduler and addressed todos and review comments from #8001. I attached some comments to the diff with more details / motivation.
Please also have another look at the comments you made in #8001 to see if they have been resolved to your satisfaction.
closes #8008
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[x] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in 7356a831fee247aa68b0200681f13fc26af65a08


[md-select] Scrolling when open with ARROW_DOWN/UP not consistent

Bug, feature request, or proposal:
Bug
What is the expected behavior?
When the select is open and the list of options visible, scrolling with the ARROW_DOWN/UP key should go one by one on each option until the last/first one. When key is pressed on the last visible option on the viewport, the list should move one position up/down with each key press.
What is the current behavior?
After opening the select which contains 10 positions, we start scrolling down with the ARROW_DOWN key, when on the last option displayed on viewport (no.5 - Dr. Pepper), next one (no.6 - Coffee) is ok being the only one displayed as next element, then on next keypress three more elements are added to the viewport (no. 7,8,9), no.7 being the one on focus -correct-, then the scroll continues normally. On the way up, same thing happens in reverse.
What are the steps to reproduce?
The behavior is reproducible using the developer demo app inside the angular material 2, md-select element, first select on the page containing 'Drinks'
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular - 4.3.6
Material - 2.0.0-beta.11
OS - Windows 10
Typescript - 2.5.2
Chrome - 60.0.3112.113
Is there anything else we should know?
Material2 cloned after commit 2f1f0fd

Here's a plunker to go with it: http://plnkr.co/edit/4u75bMC2W7dKwt1XbaC7?p=preview

@willshowell, the plunk is broken. If I take away the MdCoreModule from the exports array in the PlunkerMaterialModule, it starts working normally.

Thanks @julianobrasil, updated!

@willshowell, thanks for the plunker


Add a "static site" handler to serve resources from a camliRoot

Addresses https://github.com/perkeep/perkeep/issues/1275
This PR adds a static site app handler to enable serving static web resources, like a single page app, from a configured camliRoot node.
Once you configure the handler, you can "install" the app by uploading the files to a camliRoot.
Build everything:
$ go run make.go
Start the app:
$ devcam server
Upload the app's source files:
$ pk-put file --permanode --title='Static App Source' ./test-app-source
Make the source permanode a camliRoot:
$ pk-put attr --add [last permanode sha from previous output] camliRoot "Static App Source"
Note: You can also configure a search root for the app handler to enable searching via the app route:
pk-put permanode --title='Test App Search Root'
This will add search support to the app's endpoint while limiting queries to the nodes contained in the specified search root:
$ curl -X POST http://localhost:3179/static-app/search -d' { "expression" : "is:image", "describe": {} } '

Finally, add the static app prefix configuration to your server's config:
"/static-app/": {
	"handler": "app",
	"enabled": ["_env", "${CAMLI_STATICAPP_ENABLED}"],
	"handlerArgs": {
		"prefix": "/static-app/",
		"serverListen": "localhost:3179",
		"program": "staticapp",
		"appConfig": {
			"staticRoot": "Static App Source",
			"searchRoot": "Test App Search Root"
		}
	}
}

And restart the server:
$ devcam server -staticapp
You should be able to now visit your static app at the app prefix hosted by your Perkeep server.

Hey, that looks pretty cool.
Looking at this, I am thinking of the following:

We should rename the current fs package to fuse.
We should create an fs package that implements io.FS on top of a fetcher (and/or client).
Your app your use that new package. Removing most of the logic from it.

I'd be willing to help with some of that work if you also agree that it makes sense.

@aviau I think that's an interesting idea. Do you think the idea would be that this new implementation could eventually replace the pk-mount backend? I know that's built with fuse, but I'm not sure if the implementations would align well. I took a cursory glance at the mount code and it seems like that uses a 3rd party FS interface for emulating the filesystem. Maybe we would just keep them separate, but I could see some overlap between the filesystem emulation currently built in the existing fuse package, and whatever would be added to this proposed fs package. What are your thoughts?

In other words, I hadn't thought about it until your comment, but maybe it would have made more sense if I had initially used the existing CamliFileSystem implementation via NewRootedCamliFileSystem to fetch static files, rather than using my own lookup implementation and schema.NewFileReader directly. Had I done that, is there still value in wrapping the existing CamliFileSystem behind the new io/fs abstraction interfaces? Would it make sense to just make the existing CamliFileSystem implement the io/fs interfaces? Or does it still make sense to you to start fresh and let the fuse-specific filesystem implementation sit alongside some new filesystem abstraction layer?

Actually, on further thought, it probably doesn't make sense to try to make the existing CamliFileSystem conform both to a io/fs implementation and a fuse.FS implementation given the interfaces overlap in conflicting ways. Rather, a new filesystem abstraction built with the io/fs package could possibly be used as an implementation detail by the existing fuse-based CamliFileSystem, but regardless would be separate from the existing fuse package.

ways. Rather, a new filesystem abstraction built with the io/fs package could possibly be used as an implementation detail by the existing fuse-based CamliFileSystem, but regardless would be separate from the existing fuse package.

Yes, exactly.
The current FUSE package should eventually be switch to a user of the FS interface. If we implement io/fs we can get WebDAV almost for free too, and that would help mac users since basil no longer supports macos.


Add the "FLAG_log_year_in_prefix"

Add the "FLAG_log_year_in_prefix" in order to not write the year in the log line prefix

Codecov Report

Merging #771 (8ae4e53) into master (224f66b) will increase coverage by 3.92%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #771      +/-   ##
==========================================
+ Coverage   72.63%   76.56%   +3.92%
==========================================
  Files          17       13       -4
  Lines        3241     2500     -741
==========================================
- Hits         2354     1914     -440
+ Misses        887      586     -301

Impacted Files
Coverage Δ

src/glog/logging.h.in
80.64% <ø> (+0.64%)
:arrow_up:

src/logging.cc
75.11% <100.00%> (+1.76%)
:arrow_up:

src/base/mutex.h
100.00% <0.00%> (ø)

src/raw_logging.cc
100.00% <0.00%> (ø)

src/windows/port.h

src/windows/dirent.h

src/stacktrace_unwind-inl.h

src/windows/port.cc

src/demangle.cc
97.50% <0.00%> (+0.02%)
:arrow_up:

src/signalhandler.cc
6.76% <0.00%> (+0.31%)
:arrow_up:

... and 5 more

Continue to review full report at Codecov.

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


feat(AztecNr): Implement Serialize/Deserialize traits for u64

Lack of these implementations makes it impractical to use with our aztec-nr state variables.
Note: Look for "TODO(#4990)" in the codebase.

Might run into https://github.com/noir-lang/noir/issues/4463
Workaround inside!


tgl reports but list entries chronologically like tgl continue

Would have to use the regular API endpoints with a filter applied with the respective selected project/client as the reports API only gives totals...
or maybe the detailed reports endpoint?

Use -d (--date) flag or something; tgl reports day projects -d


Tooltip: Move to Internal Tooltip

Summary
Moving to an internal tooltip. Original change description is in #3187.  It was reverted in #3209 due to failing tests.
What changed?
This fixes extra rendering that was happening in the useEffect

Can you dociment, take a screenshot of the useEffect and some context of what was happening?


internal: Improve version handling for numbagg

Uses the approach in #8316, a bit nicer. Only internal.

I actually made this change on another PR (I was wondering why it seemed like I was writing code I'd already written!), so this ends up being a tiny variable naming change. I'll still merge.


[Proposal] 17: User Defined Coupon Expiry w/ FPSBA

Summary

implements EIP-14 but using a FPSBA kind of blind auction with the spirit of the coupon auction outlined in v2

Description
An auction is initiated for every epoch, during that epoch people may place bids -> {how much they want to pay, max coupons they want to buy, the epoch they want coupon to expire}. Bids that exceed the max coupon to token ratio are rejected immediately. Tokens that are in the wallets at the time of bidding, but not by the time of settlement are ignored and not filled.
At the end of the epoch:

if TWAP > 1, the auction is canceled, coupons are auto-redeemed in order of placement in prior auctions that were successfully settled (i.e first place winners in each auction first, then second place, etc until redemption pool is empty). Rate of expansion is determined by prior auction internals (inverse of avg of the avg yields of the individual auctions that still have non expired coupons in them, this will allow for market driven dynamics to determine the rate of token growth), not by hard-coding in the protocol.

if TWAP < 1, the auction is settled and coupons assigned in order and tracked on chain within an auction based on min euclidean distance of yield and expiry (i.e. the person that submitted the smallest yield, smallest expiry gets filled first and the most amount of esd they are willing to burn) until all are filled, the next auction is created.

Tests have been implemented for coupon bid and auction settlement (auto-redemption tests are in progress). Thanks to everyone for helping me flesh this out in the discord conversations.
Tracking
Status: Pre-proposal
Implementation:

if TWAP < 1, the auction is settled and coupons assigned based on min euclidean distance of yield and expiry (i.e. the person that submitted the smallest yield and smallest expiry gets filled first) until debt is erased, the rest of the bids get rejected and auction is markets as finished. the next auction is created.

I'd change this minimum Euclidean distance. Shorter expiry is riskier, therefore it has first priority (probability of getting paid after expiry is 0 with 100% confidence). Thereafter, ties should be sorted by the lowest premium.
I understand this would totally change this proposal. Still, think it is worth pointing it out.

if TWAP < 1, the auction is settled and coupons assigned based on min euclidean distance of yield and expiry (i.e. the person that submitted the smallest yield and smallest expiry gets filled first) until debt is erased, the rest of the bids get rejected and auction is markets as finished. the next auction is created.

I'd change this minimum Euclidean distance. Shorter expiry is riskier, therefore it has first priority (probability of getting paid after expiry is 0 with 100% confidence). Thereafter, ties should be sorted by the lowest premium.
I understand this would totally change this proposal. Still, think it is worth pointing it out.

I'd change this minimum Euclidean distance. Shorter expiry is riskier, therefore it has first priority (probability of getting paid after expiry is 0 with 100% confidence). Thereafter, ties should be sorted by the lowest premium.
I understand this would totally change this proposal. Still, think it is worth pointing it out.

I was trying avoid sorting twice and it was simpler for me to weight the importance of both lowest yield and lowest expiry equally. Feel free to implement that sorting algo.

I'd change this minimum Euclidean distance. Shorter expiry is riskier, therefore it has first priority (probability of getting paid after expiry is 0 with 100% confidence). Thereafter, ties should be sorted by the lowest premium.
I understand this would totally change this proposal. Still, think it is worth pointing it out.

I was trying avoid sorting twice and it was simpler for me to weight the importance of both lowest yield and lowest expiry equally. Feel free to implement that sorting algo.

first shot at premium decay of coupon with longer expiry
updates for eulers number and missing import
fix multiplier
fix uint256 assignment
first stab at coupon auction
sort bids by euclidan distance with equal weights on min bid and min maturity
fix: sort on distance not on struct
add coupoun assignment/selected and rejected fix yeild calc
remove unused imports and constants
dont subtract off constant epoch when assignment
fixing some compiler errors
fixing more compiler errors
first pass with implementing FPSBA
changing contract inheritance of Auction

first shot at premium decay of coupon with longer expiry
updates for eulers number and missing import
fix multiplier
fix uint256 assignment
first stab at coupon auction
sort bids by euclidan distance with equal weights on min bid and min maturity
fix: sort on distance not on struct
add coupoun assignment/selected and rejected fix yeild calc
remove unused imports and constants
dont subtract off constant epoch when assignment
fixing some compiler errors
fixing more compiler errors
first pass with implementing FPSBA
changing contract inheritance of Auction

))

))

Is there also a web 3 provider?

And is it possible for 0?


[REQUEST] Get elapsed time from Task in Progress

Hello! Rich has been super useful, to the point that I'm replacing a very similar home-built multi-progress-bar display solution with it. Now, perhaps this is something that already exists, but it wasn't obvious how to do it.
When using Progress, how do you get the final Task's elapsed time, in order to print that out to a log file?
I'm currently doing this, which while it works, doesn't seem right:
with rich.progress.Progress(*STD_PROGRESS_COLS, expand=True) as progress:
    tasks = []
    for i, thing in enumerate(things_to_do):
        tasks.append(progress.add_task(f"[blue]Thing {i}:[/] {thing}"))

        <threaded_stuff>(thing, tasks[i], progress)

    <threaded_stuff>.join()

    with path_log.open(mode='a') as lfp:
        lfp.write("Final times per task:\n")
        for i, thing in enumerate(things_to_do):
            # pylint:disable=protected-access                         # <-- Feels dirty
            f_time = progress._tasks[tasks[i]].elapsed                # <-- Probably shouldn't do this
            s_time = time.strftime("%Hh:%Mm:%Ss", time.gmtime(f_time))
            lfp.write(f" Task {i}, {thing}: {s_time}")

Is there a better way?  I would just add an extra timer, but it seems like I should be able to just get the existing timer values from Task.
If directly accessing the private _tasks list is currently the only option, Here's a PR that adds a getter for that value from the Progress object, if this is a better way of doing it: #2345

To show elapsed time you can use TimeElapsedColumn
from rich.progress import Progress,TimeElapsedColumn

columns = [
  *Progress.get_default_columns(),
   TimeElapsedColumn()
]
progress =Progress(*columns)

which shows the value calculate by elapsed = task.finished_time if task.finished else task.elapsed as you have discovered. you can use the progress.tasks property instead of progress._tasks to feel less dirty 😄


#1929 - Children as Property Resource Wrapper API array support

Adds array property support. Values can also be written in using Lists.

Pull Request Test Coverage Report for Build 4633

8 of 37 (21.62%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 53.294%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bundle/src/main/java/com/adobe/acs/commons/synth/children/ChildrenAsPropertyResource.java
8
37
21.62%

Totals

Change from base Build 4631:
-0.05%

Covered Lines:
13762

Relevant Lines:
25823

💛  - Coveralls


Operations between replicated arrays on different meshes fails if mesh devices have different orders

Description
Operations between replicated arrays created using different meshes can succeed, but only if the different meshes happen to have the same internal device order (apparently C contiguous order, for multi-dimensional meshes).
This surprised me because the sharding attributes on these arrays is a GSPMDSharding({replicated}) object, for which the public API suggests device order doesn't matter: .device_set and .addressable_devices are set objects. Could the underlying device assignment checks also be made to be order invariant, e.g., by using sets instead of tuples, or by sorting devices on replicated arrays?
Example code to reproduce:
import functools
import chex
import jax
import numpy as np

chex.set_n_cpu_devices(4)

P = jax.sharding.PartitionSpec

@functools.partial(jax.jit, static_argnames=['mesh'])
def replicated(x, mesh):
  sharding = jax.sharding.NamedSharding(mesh, P(None))
  return jax.lax.with_sharding_constraint(x, sharding)

devices = jax.devices()
devices_2d = np.reshape(devices, (2, 2))

mesh = jax.sharding.Mesh(devices, axis_names=['x'])
mesh2 = jax.sharding.Mesh(devices_2d, axis_names=['x', 'y'])
mesh3 = jax.sharding.Mesh(devices_2d.T, axis_names=['x', 'y'])

x = replicated(np.zeros(4), mesh)
y = replicated(np.zeros(4), mesh2)
z = replicated(np.zeros(4), mesh3)
print(x.sharding)  # GSPMDSharding({replicated})
print(x - y)  # succeeds
print(x - z)  # fails

DeviceAssignmentMismatchError             Traceback (most recent call last)
third_party/py/jax/_src/pjit.py in _python_pjit_helper(fun, infer_params_fn, *args, **kwargs)
    154   try:
--> 155     out_flat = pjit_p.bind(*args_flat, **params)
    156   except pxla.DeviceAssignmentMismatchError as e:

12 frames
third_party/py/jax/_src/core.py in bind(self, *args, **params)
   2632                  else axis_main.with_cur_sublevel())
-> 2633     return self.bind_with_trace(top_trace, args, params)
   2634

third_party/py/jax/_src/core.py in bind_with_trace(self, trace, args, params)
    382   def bind_with_trace(self, trace, args, params):
--> 383     out = trace.process_primitive(self, map(trace.full_raise, args), params)
    384     return map(full_lower, out) if self.multiple_results else full_lower(out)

third_party/py/jax/_src/core.py in process_primitive(self, primitive, tracers, params)
    789   def process_primitive(self, primitive, tracers, params):
--> 790     return primitive.impl(*tracers, **params)
    791

third_party/py/jax/_src/pjit.py in _pjit_call_impl(jaxpr, in_shardings, out_shardings, resource_env, donated_invars, name, keep_unused, inline, *args)
   1068
-> 1069   in_shardings = _resolve_in_shardings(
   1070       args, in_shardings, out_shardings,

third_party/py/jax/_src/pjit.py in _resolve_in_shardings(args, pjit_in_shardings, out_shardings, pjit_mesh)
   1001   # same.
-> 1002   pxla._get_and_check_device_assignment(
   1003       it.chain(

third_party/py/jax/_src/interpreters/pxla.py in _get_and_check_device_assignment(shardings, devices)
   1783       if first_sharding_info[0] != arr_device_assignment:
-> 1784         raise DeviceAssignmentMismatchError([
   1785             DeviceAssignmentMismatch(*first_sharding_info),

DeviceAssignmentMismatchError: [DeviceAssignmentMismatch(da=(CpuDevice(id=0), CpuDevice(id=1), CpuDevice(id=2), CpuDevice(id=3)), m_type=<MismatchType.ARG_SHARDING: 0>, source_info=None), DeviceAssignmentMismatch(da=(CpuDevice(id=0), CpuDevice(id=2), CpuDevice(id=1), CpuDevice(id=3)), m_type=<MismatchType.ARG_SHARDING: 0>, source_info=None)]

During handling of the above exception, another exception occurred:

UnfilteredStackTrace                      Traceback (most recent call last)
<ipython-input-29-fad052feb49e> in <module>()
     34 print(x - y)  # succeeds
---> 35 print(x - z)  # fails

third_party/py/jax/_src/numpy/array_methods.py in deferring_binary_op(self, other)
    257     if isinstance(other, _accepted_binop_types):
--> 258       return binary_op(*args)
    259     if isinstance(other, _rejected_binop_types):

third_party/py/jax/_src/traceback_util.py in reraise_with_filtered_traceback(*args, **kwargs)
    165     try:
--> 166       return fun(*args, **kwargs)
    167     except Exception as e:

third_party/py/jax/_src/pjit.py in cache_miss(*args, **kwargs)
    207   def cache_miss(*args, **kwargs):
--> 208     outs, out_flat, out_tree, args_flat = _python_pjit_helper(
    209         fun, infer_params_fn, *args, **kwargs)

third_party/py/jax/_src/pjit.py in _python_pjit_helper(fun, infer_params_fn, *args, **kwargs)
    162         fun_name, fails, args_flat, api_name, arg_names)
--> 163     raise ValueError(msg) from None
    164   outs = tree_unflatten(out_tree, out_flat)

UnfilteredStackTrace: ValueError: Received incompatible devices for jitted computation. Got argument x1 of jax.numpy.subtract with shape float32[4] and device ids [0, 1, 2, 3] on platform CPU and argument x2 of jax.numpy.subtract with shape float32[4] and device ids [0, 2, 1, 3] on platform CPU

cc @yashk2810
What jax/jaxlib version are you using?
No response
Which accelerator(s) are you using?
No response
Additional system info
No response
NVIDIA GPU info
No response

I am trying to lift that restriction (actively) but it is hard and also might lead to inefficiencies so it will require more testing than usual. But currently those restrictions exist.
Is this blocking you? I can suggest a workaround!

Glad you're working on this!
I was able to figure out my own work-around pretty quickly once I figured out what was going on.
(In my case, I have two meshes, one of which is 1D. So I can just copy the device order for the 1D mesh from the ND mesh.)


Fileupload dialog

the dialog should be using the grid system, our something.
currently if on small display only a fraction of it is visible. On large displays when you drag it up or down it changes size

Do not use a dialog, let's show it in the page itselft e.g., above the drop area

please comment on https://github.com/ufal/lindat-dspace/tree/issue_120


ffmpeg requires version 4.0.0 above

日志：
3/17/2019 03:04:45 13801 [INFO] Node Media Server v1.4.12
3/17/2019 03:04:45 13801 [INFO] Node Media Rtmp Server started on port: 1935
3/17/2019 03:04:45 13801 [INFO] Node Media Http Server started on port: 8000
3/17/2019 03:04:45 13801 [INFO] Node Media WebSocket Server started on port: 8000
3/17/2019 03:04:45 13801 [ERROR] Node Media Trans Server startup failed. ffmpeg requires version 4.0.0 above
3/17/2019 03:04:45 13801 [ERROR] Download the latest ffmpeg static program: https://johnvansickle.com/ffmpeg/releases/ffmpeg-release-64bit-static.tar.xz | https://johnvansickle.com/ffmpeg/releases/ffmpeg-release-32bit-static.tar.xz

app.js：
const { NodeMediaServer } = require('node-media-server');

const config = {
  rtmp: {
    port: 1935,
    chunk_size: 60000,
    gop_cache: true,
    ping: 60,
    ping_timeout: 30
  },
  http: {
    port: 8000,
    allow_origin: '*'
  },
  trans: {
    ffmpeg: '/usr/bin/ffmpeg',
    tasks: [
      {
        app: 'live',
        hls: true,
        hlsFlags: '[hls_time=2:hls_list_size=3:hls_flags=delete_segments]',
        dash: true,
        dashFlags: '[f=dash:window_size=3:extra_window_size=5]'
      }
    ]
  }
};

var nms = new NodeMediaServer(config)
nms.run();

reinstall ffmpeg using static install , default version is 3.2.1 lower 4.0

@TheresaQWQ did you figure out what the problem was for you? Maybe close this issue or give us an explanation, please. Thank you.

Ok, now I did a few tests.
When FFmpeg 3.x is installed, then an error message is shown that FFmpeg 4.x is necessary to use Node Media Server. It also gives download links to statics which are no longer working.
Best would be to replace the static download link with something like this:
https://johnvansickle.com/ffmpeg/
Since this page actually offers the different files which the user may need for their system.
The change would be around this area:
https://github.com/illuspas/Node-Media-Server/blob/890d70082dd4cac07dcf020e35d872c3b51783bc/node_core_utils.js#L70
Either link to the download link to begin with, or add arm64 would be an idea as well (I am running on an arm64 server from scaleway).

@TheresaQWQ the docker version use ffmpeg 4 with RTMPS support see https://github.com/illuspas/Node-Media-Server/pull/356


Open Inbox

Hello,
When I press "I" to open my Inbox I get a prompt that says "new Messages" but I can't open them. Hope can I see my messages?
Thanks
ro0kie4

This feature isn't available yet, but I'm actively working on it. There's a discussion about the feature in #109. Hopefully I'll have a pull request up with at least basic functionality by the end of next weekend.

Closing as duplicate issue


NIM-19755 - replace "null" param values to null

You did it @rakeshnpatel!
Thank you for signing the Anthem Opensource Software CLA.


YoloV3 Support

Fixed Issue(s)

fixes #1507
Changelog

[x] I thought about the changelog and included a changelog update if required.

Do we still need this PR merged into master?

Yeah

is it ready for review?

Yup!


Fixes #54: Ryanair integration

Just implemented requested changes. Also, thanks for all the input, it allows me to learn more, I appreciate it ☺


Improve error messages when handling stream 0

I’m not sure if I should provide a better message about stream 0 being “special”, but at least the traceback no longer comes from halfway inside priority.
Fixes #48.

I’ve added a new exception and tweaked the tests. I also realised that blocking/unblocking stream 0 isn’t necessarily wrong, so let’s allow that – unless you can think of a reason not to?
CI is failing because the prioritize method is now too complicated. Any ideas?

@alexwlchan Yeah, blocking/unblocking stream 0 is definitely wrong. =) Let's forbid that. As to reprioritize, I think you can simplify it by pulling stream_cycle out of the definition and making it a private method at module scope.

Now restricting blocking/unblocking on stream 0, reprioritize() has been refactored, and changelog entry added.

Done and done.


fix: Fix building of quadratic parameter in Vowpal Wabbit

Summary
With the recent parameter refactoring, all Array[T] parameters were converted to build as comma-separated lists (e.g. {"aa", "bb"} => "q=aa,bb").  For Vowpal Wabbit parameter "q", this is a regression.  The parameter should be repeated once for each array element, e.g. "q=aa q=bb".  I added a new appendRepeatableParamIfNotThere method to the ParamsStringBuilder that can handle this special case.
Tests
Extended existing ParamsStringBuilder tests to include the new appending methods.
Dependency chances
If you needed to make any chances to dependencies of this project, please describe them here.

/azp run

/azp run


Migrate to NATS Jetstream

For exactly once delivery

The implementation needs in-progress changes to nats.py, the NATS python client, to support JetStream.  Once those changes are in place, we can proceed with the exactly-once implementation.


Strategy to improve Service Attention issues management

Currently the language repos have issues opened and classified as Service Attention. In some cases this issues don't get the neccesary traction. What will be the best way to improve this?

Should issues be moved to the REST API repo? open an ICM?
How will the service team will be notified about them?
Should the service team resolve them or have a target in order to be able to publish their next RESt API version?
etc...

@ronniegeraghty, if you can add some clarity on what we want to do here (which may require broader discussion/consensus from stakeholders), then you can assign it to @JimSuplizio for implementation.

@kurtzeborn, this is a long ongoing discussion and I think @maririos is just capturing some questions and ideas for updates to the engagement experience tools.
Right now, I don't have any updates or changes planned for our GitHub Actions process, besides onboarding the azure-rest-api-specs repo at some point. I'll let you and @JimSuplizio when I have more information on that effort.
@maririos, for your points:

Should issues be moved to the REST API repo? open an ICM?

I've been thinking about this one. If the issue is related to a generated library and to resolve the issues the TypeSpec needs to be updated, then I would say yes. But we'd need proper docs on how the partner teams could troubleshoot issues and make sure they aren't actually issues in our generators for a specific language.
With respect to moving the issue to an ICM, we've also though about that as well and already as customers to do this if the issues are related to the service and not the SDKs. However, it was decided that we'd need input from higher up if we'd start telling customers to also take their SDK related issues (Service Attention Issues) to an ICM. I can answer more questions about this in a private repo issue or via teams.

How will the service team will be notified about them?

Service teams are notified by being mentioned on customer issues that have their specific service label and the 'Service Attention' label. This mentioning is set up through our CODEOWNERS files and the label is also automated through a ML application for the service label and our CODEOWNERS file for the Service Attention label.
We could think about additional tools like an app where partner teams manage a set of emails that get sent a weekly report for the customer issues for their service label across the different languages. The CXP team had something akin to this set up for a few groups.

Should the service team resolve them or have a target in order to be able to publish their next RESt API version?

I do believe it's reasonable to set some sort of threshold that says a service team has too many open customer issues that are in total some number of days past their SLA requirement to be resolved. And then block them on release APIs or Libraries until the issues are back within an acceptable range. We'd want some kind of warning system for this, so a team isn't blindsided on a critical release, but they know for the next release they'd need to resolve issues before getting the go ahead.

The one issue here is we would need a mapping between the Service's service tree id and there specific Service Label in the repos.


add QhullError to the public API for scipy.spatial?

A recent PR to scikit-image (not yet merged) involves use of QhullError as imported from scipy.spatial.qhull, but it looks like this is not public API (reference discussion at https://github.com/scikit-image/scikit-image/pull/6008/files#r744350997). My question is whether this attribute should be public? The use case is to check for this error type and return a sensible result when a convex hull for an object cannot be found.
It seems this would just involve adding it to __all__ here so that it can be imported using from scipy.spatial import QhullError.
ping @czgdp1807 and @rgommers who worked on defining the scipy.spatial API recently in #14923

Not sure what Ralf thinks, but most of the work under the hood is done by Qhull so at first glance it doesn't seem like a bad idea to make the error object public/"official."
Handling degenerate conditions/lack of general position can also be a pain for many of the diagrams so if we can leave that to Qhull as much as possible that might be a win (and folks would presumably want to be able to catch those errors sometimes). Maybe there are downsides I'm not thinking of though.

My question is whether this attribute should be public? The use case is to check for this error type and return a sensible result when a convex hull for an object cannot be found.

When I integrated the UNU.RAN library, I made a decision to make the error object public for the same reason @grlee77 mentioned. Not sure if it applies to Qhull but generally having the error object public also improves the readability of the user code (e.g. in a try...except block, instead of except RuntimeError, we could have except QhullError which is much more informative).

So would it be OK for me to submit a PR based on @grlee77 suggestion?

Seems reasonable to me. Submitting a PR sounds good, thanks @boazmohar.


Add registry property to PullSubscription CRD

Adding the eventTypes the PullSubscription source can produce in its CRD.
Setting schema to empty for now, as it seems it might change based on the transformer configured.
Removing unnecessary apiVersion, kind, and metadata.

/lgtm
/approve


Add MIT LICENSE

Every Github repository should have a license.  I added the MIT license because it is very similar to not having a license at all. It is also the same license used in BuilderIO's other repository qwik.
You can see more information about the MIT license here.

doh, thank you!

But license was already there in the package.json using ISC ? Not that it really matter as they are "the same".

But license was already there in the package.json using ISC ? Not that it really matter as they are "the same".

Thanks for bringing this up! This has been fixed in #68


DP cluster.crt is added to lua_ssl_trusted_certificate.

Note that the cluster certificate (from either cluster_cert or cluster_ca_cert, depending on the mtls mode) is added to the content (if any) of lua_ssl_trusted_certificate.

@dndx the diff link you provide points to this PR -- did you have a different page for which you wanted to indicate needed changes?

https://github.com/Kong/docs.konghq.com/pull/2976/files#diff-104d732e7c6555667f350ecd8b6b31fd126acc6d36edc573f713276d072ec51bR333 and another reference below in the same file should be updated as well.

Are you saying there is another section in the doc that needs updating @dndx ? If so, what lines please?

Hello @HCloward,
I added the necessary changes in d0d608e45142cdea8f76b150dc3e91946860feb3.


TCP hangs on FreeBSD

I've seen this for savi-Postgres and now as well on savi-MQTT.
After sending a couple of packets, this can be 2, 50 or 100, it just hangs.
Also, sometimes when running savi spec, the test suite hangs. Likely that the two issues are related.
The process is in Idle state.
To reproduce:
https://github.com/mneumann/savi-MQTT/
savi run example

You need a MQTT broker (mosquitto) running on localhost. (you can see that it is publishing by running mosquitto_sub -t topic

When I run with --ponymaxthread 1 it does not hang. Am I using the wrong ponyrt version or libsavi_rt?

> ./bin/example --ponyversion
 [release]
Compiled with: LLVM  -- Clang-9.0.1-

I am trying to build libponyrt.bc tomorrow myself.

@mneumann - This may potentially be the same issue as https://github.com/savi-lang/TCP/issues/2
At any rate, I'm going to move the issue to the TCP repo for consistency.


Perform FMEA testing for Numaplane with dataLossPrevention = false

Summary
Cover FMEA for testing availability, reliability.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

FYI @xdevxy I broke this issue into two, one for the feature flag turned on and one for it turned off. I assigned @chandankumar4 to this one and myself to the other.

now that we will primarily be doing PPND, we can probably not do this I'm thinking


Update Everything to New Phase 6 Design

In This PR
Throughout the project, the specs/starter code/instructions/petshop code have been updated to match the following rules:

In phase 6, the JOIN_PLAYER and JOIN_OBSERVER UserGameCommands have been merged into one called CONNECT. It only requires a gameID in addition to the other fields included in UserGameCommand.
In phase 3, the Join HTTP method (PUT /game) no longer accepts null values for the color. A null color should return 400 (though the tests have not been changed yet). In other words, there is no such thing as "observing" a game via HTTP.
In phase 5, the options for joining as a player and as an observer are still in the post-login menu, but the language has been updated and joining as an observer has no functionality until phase 6.
The endpoint that the WebSocket connects with is now /ws rather than /connect to avoid confusion in phase 6.

In addition to these rule updates, wording in the specs has been updated so that the word "join" can ONLY refer to the HTTP join.

@prattnj In your first commit you're removing Dr. Rodham's websocket diagram because it's outdated. What specifically is outdated? I think he's going to want to update it.

In his diagram, he references JoinPlayer and JoinObserver, which we replaced with one command called Connect. I plan on updating the diagram, but for the sake of quickly updating things for this term, I temporarily removed it in the mean time.

I'd rather not delete his diagram, in case we forget to replace it. It seems like a simple change. You can either ask him to update it and send you the update diagram to include in another commit or maybe he can provide the original so you can update it.

I'd rather not delete his diagram, in case we forget to replace it. It seems like a simple change. You can either ask him to update it and send you the update diagram to include in another commit or maybe he can provide the original so you can update it.

I can just remake it, there's plenty of time since the queue isn't too busy.

He may want to have the original. I'll ask him if he wants to update it or if he wants you to remake it.

He may want to have the original. I'll ask him if he wants to update it or if he wants you to remake it.

I just updated it, it wasn't as difficult as I thought because apparently the software I use for this kind of thing can edit PDFs.

Since Dr. Rodham moved the diagram to a better location (the Phase 6 specs directory), I removed it from its location here. It isn't actually deleted, just moved. It should be ready for merging now.


Only get backing array of ByteBuffer when it has one

ByteBuffer.array() shouldn't be called unless ByteBuffer.arrayOffset() is used or if the ByteBuffer was initialized using ByteBuffer.wrap() or ByteBuffer.allocate().

@dmsolr can you please confirm that whether the ByteBuffer passed by Avro server is always backed with an array , if that’s the case, we don’t need to fix this


Update MySQL connector errors to align with error guidelines

Update MySQL connector errors to align with error guidelines

Closed by: https://github.com/datafusion-contrib/datafusion-table-providers/pull/180


Anchore Layer Caching storage deletion.

Is this a request for help?:
yes
Query
Hey I have a question about anchor Layer Caching, I have given layer_cache_max_gigabytes option to 10GB, we are using anchore to scan even for the windows images, due to the volume of our registry and when the scan happens, this scratch volume goes beyond 50 Gigs and we are using AWS EFS for this purpose, so if the size goes beyond the declared value 10GB, will the deletion of the extra GB happens from anchore side or we have to delete this scratch volume data periodically?
anchore-cli, version 0.9.0
Engine version v0.9.0
What happened:
The Size of the scratch volume goes beyond the declared layer_cache_max_gigabytes size.
What did you expect to happen:
Once the size exceeds beyond the declared layer_cache_max_gigabytes size, will the clean up of these layers automatically?
What docker images are you using:
Windows, alpine, Debian, dotnet
Anything else we need to know:
We are using AWS EFS, bursting mode, will this slow down the scan process?

hi @prudhvigodithi , the layer cache will expand to the size needed to download the image, but will then remove layers to get back to the stated max value. This ensures that images can always be analyzed, but the cache itself will never remain larger than the stated value. The cleanup is done after the image analysis is complete, and is performed automatically.

Hey @zhill, thanks for the update, got cleared now, can you please add this in the docs for future reference?
Thanks

I have created a docs issue linked to this one. I'll close this issue since the question was answered and we can track the docs update in the other issue. Thanks @prudhvigodithi


Cupcake content: designer guidelines

Wonil-Suh1 created the following on Aug 05:
Introduction
This story is part of the first phase work (research) towards the cupcake website.
The problem
As a designer, I need to understand how to design with the new design system and language.
Expected outcomes

[ ] A list of pages, each with description, references if applicable

Original issue: https://github.ibm.com/webstandards/digital-design/issues/1366

On Aug 06, chsanche commented:
@Wonil-Suh1 based on our conversation today, we will publishing guideline content via Cupcake repo.

On Aug 22, chsanche commented:
@Wonil-Suh1 @spbokma
Here's a list of guidelines for our consideration to be included in the guidelines session :

Overview
Accessibility (or Usability)
Color
Content
Grid
Frameworks
Icons (or Iconography)
Illustrations
Infographics
Interaction
Layout
Localization
Navigation & IA
Motion
Photography
Social and Sharing
Themes (or Themeing)
Type (or Typography)

On Aug 23, chsanche commented:
@Wonil-Suh1 Let's review and set priority together.