[Backport release-23.11] dnf5: 5.1.7 -> 5.1.8, re-enable tests, add man pages, fix hash

Description of changes
Backporting PRs https://github.com/NixOS/nixpkgs/pull/269512 and https://github.com/NixOS/nixpkgs/pull/270669
Supersedes https://github.com/NixOS/nixpkgs/pull/270148

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

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

2 packages built:

dnf5
dnf5.man

@ofborg build dnf5


[Outlook] (on-send) Add note about manifest validation message

Docs Build status updates of commit 7a83a4a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/outlook-on-send-addins.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 311ddea:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/outlook-on-send-addins.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fixed load_data()

I fixed a problem in logistic_sgd.py when I try to run it, but it's not very elegant ...

fixed another similar problem in cnnMNIST.py

These models were for testing system configuration and trying out new optimisers.  We would remove them from final mitosis detection source code.


"cannot be set as it is read only"

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.0.0
on linux_amd64

provider registry.terraform.io/cloudflare/cloudflare v2.21.0

Affected resource(s)
cloudflare_zone_settings_override
Terraform configuration files
resource "cloudflare_zone_settings_override" "test" {
  zone_id = "${cloudflare_zone.test.id}"
  settings {
    # settings here
  }
}

Debug output
No response
Panic output
No response
Expected output
Should update the provided settings.
Actual output
Different errors each time. Such as
Error: invalid zone setting "prefetch_preload" (value: ) found - cannot be set as it is read only`

or
Error: invalid zone setting "sort_query_string_for_cache" (value: ) found - cannot be set as it is read only

Steps to reproduce
Enter some settings.
If you have the free plan you get an error saying some settings are read only even though you didn't specify these settings anywhere.
Additional factoids
No response
References
No response

It happens if you give even a single setting. Any setting you give has the same problem.
I didn't import this resource but I imported cloudflare_zone resource.

Please provide an example of it not working with a single setting that your zone is entitled to. Free zones do not have all settings available.

for anyone else hitting this and finding this issue, please see https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/zone_settings_override#plan-dependent-settings

This issue is also happening to me
Terraform and Cloudflare provider version
Terraform v1.1
on linux_amd64
provider registry.terraform.io/cloudflare/cloudflare v3.10.0
Affected resource(s)
cloudflare_zone_settings_override
Terraform configuration files
data "cloudflare_zone" "zone" {
  name = "example.org"
}

resource "cloudflare_zone_settings_override" "settings" {
  zone_id  = data.cloudflare_zone.zone.id

  settings {
    ssl                                      = "full"
    always_use_https            = "on"
  }
}

Debug output
No response
Panic output
No response
Expected output
Should update the provided settings.
Actual output
Different errors each time. Such as
Error: invalid zone setting "prefetch_preload" (value: ) found - cannot be set as it is read only`
or
Error: invalid zone setting "sort_query_string_for_cache" (value: ) found - cannot be set as it is read only


Empty String returned in the aud claim in the ID Token in OIDC flows.

Describe the issue:
After configuring an OIDC based application in the console, the returned ID token upon calling the https://localhost:9443/oauth2/token contains an empty aud claim value. The value for the aud claim in the ID Token must be trusted by the client and the value must not be null or empty string.[1]

How to reproduce:
Configure an OIDC application through the console. [2]
Try the OIDC Authorization Code grant flow. [3]
Obtain an ID token.
Parse the ID token and check the aud claim value.
With the default configurations, it should contain the client id and an empty string.
[1] https://openid.net/specs/openid-connect-core-1_0.html#IDTokenValidation
[2] https://is.docs.wso2.com/en/5.11.0/learn/configuring-oauth2-openid-connect/
[3] https://is.docs.wso2.com/en/5.11.0/learn/try-authorization-code-grant/
Expected behavior:
With the default configurations, the aud claim should only contain the client id of the application.
Environment information:

Product Version: IS 5.12.0-M6

Migara Pramod will be working on this.

Migara Pramod will be working on this.

In addition to the backend fix, we need to fix the console app to avoid sending empty or duplicate audience values.

In addition to the backend fix, we need to fix the console app to avoid sending empty or duplicate audience values.


Menu links not working anymore when media library is opened

Describe the Bug

When the media library is opened, all other links outside the media library are not working anymore and are just interpreted as directory ids for the media library.
E.g., when clicking on the link http://localhost:8000/admin_dashboard/, the preact router catches this URL and actually opens http://localhost:8000/media-library/#/admin_dashboard/, which causes the server error ValueError: Field 'id' expected a number but got 'admin_dashboard' and the in the frontend, the error An error has occurred. Please try again later. appears.
Steps to Reproduce

Go to the media library
Click on any link outside the media library
See error

Expected Behavior

Normal links should still work
Actual Behavior

All links are treated as internal media library links of the preact router
Additional Information

This seems to be only a problem, when we are in the admin view of the library. The Preact component seems to call the directory content API everytime a link is clicked.


No support for SQLModel relationships

Checklist

[X] The bug is reproducible against the latest release or master.
[X] There are no similar issues or pull requests to fix it yet.

Describe the bug
SQLModel does not store relationships data directly in attributes, so trying to use them like vanilla SQLAlchemy attributes like that
class ModelA(SQLModel, table=True):
    id: uuid.UUID = Field(default_factory=uuid.uuid4, primary_key=True, nullable=False)

class ModelB(SQLModel, table=True):
    id: uuid.UUID = Field(default_factory=uuid.uuid4, primary_key=True, nullable=False)
    model_a: Optional[ModelA] = Relationship(sa_relationship=relationship("ModelA"))

class ModelBAdmin(ModelAdmin, model=ModelB):
    column_list = [ModelB.model_a]

results in error:
AttributeError: type object 'ModelB' has no attribute 'model_a'

Trying to use attribute used by SQLModel does not work either:
class ModelBAdmin(ModelAdmin, model=ModelB):
    column_list = [ModelB.__sqlmodel_relationships__["model_a"].sa_relationship]

error:
 File "/usr/local/lib/python3.9/site-packages/sqladmin/models.py", line 590, in get_model_attr
assert isinstance(attr, (str, InstrumentedAttribute))
 AssertionError

since what is checked in this assertion is sqlalchemy.orm.RelationshipProperty
I tried to work around that making some patch:
from typing import Union

from sqladmin.models import ModelAdmin
from sqlalchemy.orm import InstrumentedAttribute, RelationshipProperty, ColumnProperty

class ModelAdminWithSQLModelRelationships(ModelAdmin):

    def get_model_attr(
        self, attr: Union[str, InstrumentedAttribute, RelationshipProperty]
    ) -> Union[ColumnProperty, RelationshipProperty]:
        if isinstance(attr, RelationshipProperty):
            return attr

        return super().get_model_attr(attr)

But it didn't work either
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/langhelpers.py", line 1214, in _fallback_getattr
  raise AttributeError(key)
AttributeError: key

so I've added some utitlity function to workaround that:
def get_sqlmodel_relationship(model, name):
    rel = model.__sqlmodel_relationships__[name].sa_relationship
    rel.key = name
    return rel

class ModelBAdmin(ModelAdminWithSQLModelRelationships, model=ModelB):
    column_list = [get_sqlmodel_relationship(ModelB, "model_a")]

At this point app could complete startup and I could access admin panel, but when I tried to access list of ModelB objects exception was raised:
sqlalchemy.exc.ArgumentError: Can't find property named "model_a" on mapped class ModelB->modelb in this Query.

so, at this point I gave up, it seems that it would need much more monkeypatching than I anticipated
Steps to reproduce the bug
No response
Expected behavior
Possibility to use SQLModel Relationship in admin panel just like in vanilla SQLAlchemy
Actual behavior
No response
Debugging material
No response
Environment
OS: Manjaro
Python: 3.9.7
SQLAlchemy: 1.4.36
Additional context
No response

Not sure if I'm missing something but this works fine:
class User(SQLModel, table=True):
    id: uuid.UUID = Field(default_factory=uuid.uuid4, primary_key=True, nullable=False)
    name: str = Field()

class Hero(SQLModel, table=True):
    id: uuid.UUID = Field(default_factory=uuid.uuid4, primary_key=True, nullable=False)

    user_id: uuid.UUID = Field(foreign_key="user.id")
    user: User = Relationship(sa_relationship=relationship("User"))

class UserAdmin(ModelAdmin, model=User):
    column_list = [User.name, User.id]

class HerAdmin(ModelAdmin, model=Hero):
    column_list = [Hero.id, Hero.user, Hero.user_id]

This issue seems to be in SQLModel which doesn't work with SQLAlchemy>=1.4.36. You need to pin that.


CSS Library: Tables on IE has incorrect color gradient

Correct gradient is:
filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#ffffff', endColorstr='#dddddd');
...on ".datagrid th"
Thanks to @adrianvanlan

This issue was resolved in version 0.9.3.


Fixed Employee Form; Fixed Rest Endpoints to return correct Version

@ge0ffrey Merged your suggested changes, plus fixed a bug with the views where the start and end times will be wrong if the database in a different timezone (my database is in my timezone, so no issue was noticed) - the old way was getting the LocalDateTime part of an OffsetDateTime, which will fail if the OffsetDateTime is in the wrong timezone. The new way is LocalDateTime.ofEpochSecond(offsetDateTime.toEpochSecond(), offsetDateTime.getNano(), zoneId.getZoneRules().getZoneOffset(offsetDateTime.toInstant())


Build an App: Update txn code samples to return values as part of the transaction

In our code samples with transaction retry logic, the transaction doesn't return anything but errors or, sometimes, a success message. The code performs a select on the updated account balances after the transaction.
Instead, we should adapt the transaction wrapper to allow values to be returned to the client, and then return the updated account balances as part of the transaction.

[ ] Go
[ ] Python
[ ] Ruby
[ ] Java
[x] Node (The wrapper is ready (see https://github.com/cockroachdb/docs/pull/1603), but the transaction itself needs to be updated and the SELECT following the transaction needs to be removed)
[ ] C++
[ ] Clojure
[ ] PHP
[ ] Rust

@vy-ton can PTAL at this?

@jseldess I'm taking a look at this.
Are you suggesting perform the select as part of the transaction itself?

We have closed this issue because it is more than 3 years
old. If this issue is still relevant, please add a comment and reopen
the issue. Thank you for your contribution to CockroachDB docs!


Create extensions on String, NSCache, NSDate, etc for Mac/Linux Foundation API differences.

Currently, we have platform-specific checking scattered around a lot of our code. Beyond hurting code quality and readability, it makes it very hard to keep track of these special case usage if it's everywhere in our codebase. We should instead, try to keep these in contained files:
String.swift
NSCache.swift
NSDate.swift
Inside, we can have extensions that are applied if the user is running on Linux in order to migrate them to the newer set of APIs. Developers will therefore use the latest (03-24 API) and the extensions will map the call to the older API if the user is running in Linux.
Once the Foundation library reaches parity with the newer APIs, we can simply remove these extensions from our codebase.

Ok, new plan:

Reach out to mailing list and see if there is a timeframe for migrating to the new API
If no plans, and no current PRs, then work on making the API migration directly to corelibs-foundation.

Update:

Hi Robert,
This is something we really do need some help with. Our goal is to have the Linux version match the Darwin version exactly.
There is also a PR up to change some of the results of the automatic renaming by the importer, here:
https://github.com/apple/swift/pull/2093
So we should take those into account as well.

Tony

It seems as if the API differences are already being taken care of. In order to avoid creating throw away code, we are just going to wait and delete the Linux specific code when we can.


gitlab-runner: 14.5.2 -> 14.6.0

Motivation for this change
https://gitlab.com/gitlab-org/gitlab-runner/blob/v14.6.0/CHANGELOG.md
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

/cc @bachp @zimbatm @globin @dlouzan

@max-wittig The shell patch doesn't apply anymore when I try to build it.

@bachp makes sense. Patch removed.

This broke the gitlab-runner build, as the other patch doesn't apply either. Please revert or fix the patch.

Reverted for now. I should have run nixpkgs-review on the PR before merging.

Is there a way to build just one package and test it? Or do you always need to build the whole os?


Keys with collection values will be stringified as YAML due to JS Object restrictions

Recently started to see this warning during codegen:
(node:17948) YAMLWarning: Keys with collection values will be stringified as YAML due to JS Object restrictions. Use mapAsMap: true to avoid this. at line 6, column 11:
JSON: { [key: string]: any }

codegen.yml:
overwrite: true
schema: "src/schema/**/*.graphql"
documents: null
scalars:
    DateTime: Date
    JSON: { [key: string]: any }
config:
    contextType: ../context#Context
generates:
  src/generated/graphql.ts:
    plugins:
      - "typescript"
      - "typescript-resolvers"

not sure where/how to use "mapAsMap" to fix the issue

Could you try to change that line to JSON: "{ [key: string]: any }"?

yeah, that seems to work just fine.

thanks for quick workaround.

 The first one was not valid for YAML syntax. But the second one is valid because you want to pass a string that will be used in the generated code which is generated as string as well.


Update members.json

Remove duplicate user

wait i have to make some changes

Thanks @sampoder for approving


Expose config option for intellij_aspect path

Our use case:
To allow developing from the IDE on a mac OSx, with bazel running inside a local docker container.
In order to make the --aspects=@intellij_aspect available inside the container, we currently need to modify the bazel command, search for the value of --override_repository=intellij_aspect (let's call it src_dir), copy it into the container (to dest_dir), and then subsequently replace src_dir with dest_dir on every bazel command run.
Exposing some config option for the aspect location (similar to the bazel binary location in the plugin settings) would make this much smoother to manage.

@brendandouglas wdyt?

We could make it configurable, and copy it to the requested location.
As a simpler change, we could move the aspect flags before the 'sync_flags', to let you override it via a .blazeproject setting. That would mean you'd need to copy it to the container separately, but at least you wouldn't have to intercept and modify the bazel commands.

Thanks for responding!
@talya wdyt?
On Fri, 31 Aug 2018 at 19:33 brendandouglas<EMAIL_ADDRESS>wrote:

We could make it configurable, and copy it to the requested location.
As a simpler change, we could move the aspect flags before the
'sync_flags', to let you override it via a .blazeproject setting. That
would mean you'd need to copy it to the container separately, but at least
you wouldn't have to intercept and modify the bazel commands.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/intellij/issues/397#issuecomment-417719692,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF4XWFIy0KS-euWPrJvucXz7rYrFeks5uWWVwgaJpZM4V86nW
.

tks @brendandouglas for your reply.
I like the option of being able to override via a settings file.
It will allow us to have a one time setup for our dev container, and as you say will also rid us of the need to intercept this on all bazel commands.
re .blazeproject - I failed in finding relevant documentation, is it's location a guaranteed one? Would like to avoid our setup script failing on some future version on the plugin / IntelliJ changing the relative path of these setting files.

For the first problem, do you already check in a .bazelproject file shared between devs? Or is it that only a subset of devs need this workaround?
For the second, we already do macro substitution before sending flags to blaze, which I suspect already includes IDE_HOME. So you could perhaps just use ${IDE_HOME} directly in the sync_flags entry?

@talya  hi, i wonder can you debug a program that is running in the container in Intellij UI?


Volume of TTS decreases when reading aloud after speech recognition. (iOS)

I use text to speech along with speech recognition (on iOS). Whenever I invoke a speech recognition, the overall volume of the app decreases (the tts speech is hard to hear).Any ideas?

I have the same problem with my iOS app! Please HELP!
Here is what happened to me:
***** This is only if you are using the sound from your phone... It works flawlessly with headphones or speakers plugged in. *****
-Everything is at full volume when I open the app on my iPhone, and then as soon as I push my "Start Speech Recognition" button, the volume goes down to a VERY low level.
-I can manually get the volume back up to about 60% of the original volume by following these steps:

Click the "Start Speech Recognition" button
Swipe up from bottom of iPhone to bring up iOS control centre
Swipe right to see the music and audio controls
At the bottom, tap "iPhone"
Switch the output to "iPhone Speaker" (Which is not available when I first open my app)

I have the same problem, too. HELP!

[session setCategory:AVAudioSessionCategoryPlayAndRecord withOptions:AVAudioSessionCategoryOptionDefaultToSpeaker error:&err];
[session setMode:AVAudioSessionModeDefault error:&err];
Finally, I got a solution. In my case, the second line recovered the low volume.

Hi nice2seeu,
how did you change the code? Did you use an av-audio-session plugin in addition?
How can I solve it with Javascript?
Thanks for your help and best regards

@pbakondy this appears still to be an issue.  I have a new Ionic 4 app using the plugin and if I play TTS when the app starts up it plays at a normal level.  Once speech recognition is called and then TTS is played again, the volume sounds like it is cut in half.  This is 1.2.0

Problem still continues. Any solution?

I confirm the same. Has the pointed fix (also related in other "volume" on this issues tracker) has been properly merged and distributed on the latest npm release?
Thanks

I report a workaround that is to play an empty string '' everytime before playing the right phrase.


targets.py: NRF51: support S110 builds for OTA and BOOT targets

Current S110 support is only available for default (SoftDevice + App)
images.
At the moment, a BOOT image built for micro:bit will contain the S130
SoftDevice and the app will be located at 0x1c000, even though we want a
S110 SoftDevice.
Since the elf build is still done with the S110 linker script, the entry
point will be offsetted by 0x2000 and it will fail to run.
This patch creates an interface class that allows all S110 targets to
override the SoftDevices list.
Signed-off-by: Jean-Philippe Brucker<EMAIL_ADDRESS>
@screamerbg please consider this patch as a fix for BOOT and OTA builds on the micro:bit

@screamerbg please review

Looks good, though can you please remove the duplicate labels from the target classes since the MCU_NRF51_16K_S110 class includes them too?
     self.extra_labels += ['MCU_NRF51_16K_S110']
     self.macros += ['TARGET_MCU_NRF51_16K_S110']

bump @jpbrucker

@screamerbg I'm not sure I fully understood what you meant by duplicates. I factored the labels into the common class MCU_NRF51_S110, and sent a new pull request


Legibility issues in diffs

Loving this theme, nice work! 🔥
Not sure if this is the right place to report this, but I ran into this while reviewing a PR. Notice how the content of the highlighted selection is difficult to read (the 7d).

Nice to hear you enjoy the theme; and no worries, this is the perfect place to report this. ^—^
I'm actually not quite sure what the best way to fix this would be tho.. but I'll look into it. Thanks for letting me/us know.

Implementation-wise I am not sure either, but I think perhaps changing this particular instance to Base seems to help a bit:

It still doesn't seem to hit any contrast checks. It is better for sure, but still hard to make out on a quick glance.. tho still better than nothing. :D

Okay, so I have this very serious pull request to try and figure out a solution. The issue is, that I don't even run into the same problem you run into. D:

Did you highlight (with the cursor) the 7d, or was the 7d the exact range that changed in your diff? My screenshot is for the latter.

Oh! My bad, I read that as a regular selection.
This now captures the issue. Thanks again. :3

@jeffijoe heya! I think I found a way that fixes this without breaking on the dark themes. Feel free to give it a test drive and let me know what you think. c:

That looks great! Ship it! :shipit:

Completely random, but I just noticed this too 😂  The @andreasgrafen (mention) highlighting looks a bit weird on the light theme 😅

I'll merge the changes into main in a bit.
As for the other things - the Actions def. need fixing. I'd suggest opening a new Issue to track that, but I can also do that once I'm on the train. The Github mobile app is just ... built different. xd

closed as per #29. c:


add login required message when getting comments

Title: Add login required message when retrieving comments
Fixes #2230  #2234
This change addresses the issue where Instagram now requires login to access comments on posts. By adding a message indicating the need for login, users will be informed about the requirement and can take appropriate action.
The proposed change adds a conditional check to get_comments method in the code. If the user is not logged in, it raises a LoginRequiredException with a message indicating the necessity of logging in to access comments.

Thanks for addressing this!
Could you also add the "Requires --login." note in the documentation (docs/cli-options.rst) and the --help output (instaloader/__main__.py)?

Thanks for addressing this!
Could you also add the "Requires --login." note in the documentation (docs/cli-options.rst) and the --help output (instaloader/__main__.py)?

ready...


Windows Defender Detecting: Trojan:Script/Wacatac.B!ml

suddenly i can't start the program. i try uninstal and download v 1.4.2
when i instal it, windows defender say it have Trojan script.
file: C:\xxxxxxx\xxxx\Downloads\Setup-swyh-rs-1.4.2.zip
the log:
webfile: C:\Users\xxxxxx\Downloads\Setup-swyh-rs-1.4.2.zip|https://objects.githubusercontent.com/github-production-release-asset-2e65be/291054463/61321c38-2a2d-4073-a1a6-4c0530948d09?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220805%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220805T054750Z&X-Amz-Expires=300&X-Amz-Signature=93d3771b0dcde8c99f630d5e2a72ed0f6b2d043b6c6e3aac172913157fe23138&X-Amz-SignedHeaders=host&actor_id=24316940&key_id=0&repo_id=291054463&response-content-disposition=attachment%3B%20filename%3DSetup-swyh-rs-1.4.2.zip&response-content-type=application%2Foctet-stream|pid:280,ProcessStart:133041520723337481
Screenshot:
https://prnt.sc/BqkqztI8Egb5

It looks like a false positive I sometimes get with a freshly compiled version.
It's all built from source code in the official Git repos/Rust crates, and a scan with Defender gives no errors.
I suppose it's the network activity that makes Defender suspicious.


Only CPU

How to run it only on cpu? I need to run it on an environment of no gpu

I don't think it can work like that unless there is a valid Vulkan device implementation for your CPU installed on the system. Do you mean with Lavapipe or some such?

okay I'm really new to this, everything works fine for me on PC.
I need to shift my code to a cloud VM (no gpu) when I run it, gives an error
vkEnumeratePhysicalDevices failed -3
invalid gpu device

What do you suggest?

Okay, well first off I'm just a user (like you), so this is based on what I know which may or may not be the final answer.
That said, this software requires a Vulkan device. If you don't have a Vulkan device in the system, it won't work - hence the GPU requirement.
There is a Mesa project that provides Vulkan on CPU in Mesa 20.3 (read about it here) but I'm not sure it's complete enough to actually run this yet. My attempts to do so have not been successful.

Thanks for this, will look into this!

https://github.com/nihui/waifu2x-ncnn-vulkan/releases/tag/20210102
support Apple M1
support running on cpu, which can be panellized with gpu, via -g -1

https://github.com/nihui/waifu2x-ncnn-vulkan/releases/tag/20210102
support Apple M1
support running on cpu, which can be panellized with gpu, via -g -1


RequestBuilder headers() method behaviour different than header() with multiple values for same key

When adding headers through headers() one at a time all keys are properly set. However when constructing a HeaderMap beforehand and adding it using headers(), only one value from a certain key is kept.
Is this the desired behaviour? It surprised me and took a while to debug until I echoed the full request that was actually sent.
Caused by using insert() in headers() and append() in header().
https://github.com/seanmonstar/reqwest/blob/c4985674aaa1cd23ec70ee7dfc24c76b714285c5/src/request.rs#L192
https://github.com/seanmonstar/reqwest/blob/c4985674aaa1cd23ec70ee7dfc24c76b714285c5/src/request.rs#L151
EDIT: Apparently even when I append manually, they are removed when sending. Seems like its impossible to send multiple headers.
https://github.com/seanmonstar/reqwest/blob/c4985674aaa1cd23ec70ee7dfc24c76b714285c5/src/async_impl/client.rs#L452
These examples are then broken because they would never be sent:
https://docs.rs/reqwest/0.9.5/reqwest/header/struct.HeaderMap.html#method.append
In that example, only "earth" is actually sent in the network request.
GET / HTTP/1.1 user-agent: reqwest/0.9.5 accept: */* host: earth accept-encoding: gzip

I think this is partly a bug. Here's the behavior I'd expect:

header: Always appends.
headers: Replaces any existing headers for the same key, but then appends all values of the same key from the new HeaderMap.

So, I'd expect this behavior:
let mut hdrs = HeaderMap::new();
hdrs.insert("foo", "bar".parse().unwrap());
hdrs.append("foo", "baz".parse().unwrap());

client
    .get(url)
    .header("im-a", "keeper")
    .header("foo", "pop me");
    .headers(hdrs)
    // ...

That should have a header map of the following:
{
    "im-a": ["keeper"],
    "foo": ["bar", "baz"]
}


Valide a plugin struct

i tried to add plugin to my api and also to my oauth server and i only gate a validation error. How can i make it validated. my request below
PUT /apis/alain HTTP/1.1
Accept: application/json, /
Accept-Encoding: gzip, deflate
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE1MTI2NTc0MjMsImlhdCI6MTUxMjY1MzgyM30._NmN-qTzeNjR4pvVdt-c8MwWn-3OMivhokDNi0FQxYU
Connection: keep-alive
Content-Length: 165
Content-Type: application/json
Host: janus:8081
User-Agent: HTTPie/0.9.9
{
"plugins": [
{
"config": {
"limit": "5-M",
"policy": "local"
},
"enabled": true,
"name": "rate-limiting"
}
]
}
HTTP/1.1 400 Bad Request
Content-Encoding: gzip
Content-Length: 74
Content-Type: application/json
Date: Thu, 07 Dec 2017 13:58:24 GMT
Vary: Origin
{
"error": "name: non zero value required;proxy: non zero value required"
}

Hey @rjtch,
That's probably happening because you are using the PUT method. According to how HTTP methods should work, when using a PUT you should provide the whole API definition. If you do that you won't get this error.
We will also work on improving this error message that doesn't have much sense.

@rjtch @hellofresh/janus is going to support Patch endpoint pretty soon, stay tuned 😉


[New game]: Jump the Ball

🎮 Game Request
Game logic and basic description
This is a single-player game made of HTML, CSS, and JavaScript.  The basic logic of the game is the ball moves forward in a positive X direction and should not touch the obstacles. The player clears as many obstacles rewarded with the same number of points.
Point down the features
Game points
The player jumps the ball using the keys on their key board.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Darkrider0007 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Darkrider0007!
We are already having a similar game request in #1333 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.

Hey @Darkrider0007 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Fix Instance example

This pull request fixes an example in the documentation. Previously it didn't build because of ownership issues.
This changes the Instance::new / Instance::with_loader functions to take an Iterator to Item = &'a str, instead of Item = &'a &'a str.
It also replaces unwrap with ?.

The problem is that this is a breaking change.

@tomaka It is, however there is probably little code out there which uses layers.
The only layers which exist right now are the validation layers, and the docs recommend enabling them using environment variables, not manually.
We're just future-proofing the code here, to make it easier to use when layers become more popular.
In other words, most code would be using None for layers, meaning no breakage.
P.S.: should I also update the changelog in this pull request, mentioning this change?

This looks good to me. However, it needs an entry in the changelog before I can merge it.

Thanks


fixer of callable-types breaks syntax with intersection type

Bug Report

TSLint version: 5.16.0
TypeScript version: 3.1.6
Running TSLint via: CLI

TypeScript code being linted
export type T2 = T & {
    (): void;
}

with tslint.json configuration:
{
    "rules": {
        "callable-types": true
    }
}

Actual behavior
export type T2 = T & (() => void;)

Expected behavior
export type T2 = T & (() => void)

I found code in the fixer deleting trailing  semicolon, but it seems not to work correctly along with parentheses

I'd like to take a shot at this!

💀 It's time! 💀
TSLint is deprecated and no longer accepting pull requests other than security fixes. See #4534. ☠
We recommend you instead use typescript-eslint to lint your TypeScript code with ESLint. ✅
👋 It was a pleasure open sourcing with you!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


Add -info switch to compute Shannon information; Sort according to -order up -order down

Compute the information content of each field value in the hierarchy.
print the info content after each line
sort the branches up or down as specified by -order

Reter to wikipedia for defintion of information content https://en.wikipedia.org/wiki/Information_content

This being experimental, it should be tried in Lua first.


Making a field mandatory is not working in multifieldpanel

I am using multifieldpanel and there is textfield and description field. Problem is that the textfield should be a mandatory field. Outside the multifield panel the "required = true" is working properly but in multifieldpanel it is not working.Do you have any idea about this??

@schoudry any ideas?

@justinedelson i see that the validator was implemented in classic multifieldpanel, nothing exists for touch (node store and json store).... 'll work on it....


Merge back Version bump and Changelog for 2.0.0-beta.4

Description

Related Issue

Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

test environment:
test case 1:
test case 2:
...

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

:boom: Acceptance test cs3ApiTests-ocis failed. Further test are cancelled...

Could you please delete the changelog file update-web-beta.4.md? The actual changelog of web for beta.4 is in update-web-5.6.0-beta.4.md. The other one only has some TBD content in it and slipped in accidentally I suppose.

done

@kulmann We need to check it there is more to do here because of the resharing feature default value.


Implement Send and Sync for softbuffer types

Previously, types in softbuffer were !Send and !Sync. However it would
be nice if types could be shared across threads. Therefore I've made the
following changes:

Context is Send+Sync iff D is Send+Sync
Surface<D, W> is Send iff D is Send+Sync and W is Send
Buffer<'x, D, W> is Send iff D if Send+Sync and W is Send

Materially, I've made the following changes across the backends:

X11, Wayland and KMS use Arc for their displays instead of Rc.
MacOS uses MainThreadBound to secure windowing resources. This
restriction was already implicitly enforced anyhow.
Windows uses a subclassing strategy to manage creating and destroying
resources. This subclass is applied to windows that are registered
into softbuffer, and is then used to manage resources.
Web just isn't Send.

Closes #205, still WIP

@jackpot51 Please advise on Redox failures. I'm not familiar enough with Orbital's internals to know if it is thread safe or not.

@jackpot51 Friendly reminder. I'm not familiar enough with Orbital to know how to proceed here.

It seems that there are still bugs in the Windows backend. Sometimes sending a message to a window on another thread doesn't work. Standby while I investigate.

It seems that there are still bugs in the Windows backend. Sometimes sending a message to a window on another thread doesn't work. Standby while I investigate.

Okay, I've set up a new strategy for multithreading on Windows. It's a little hacky but it seems to work.

I think we have approval from all platforms, so I'll go ahead and merge this. But I'll wait a week before releasing, that way the people using the master branch directly over Git have a breathing period to find bugs.


SELinux Policy

I'm currently trying to test out this role against a Vagrant Box (CentOS 7.3).  However, I cannot get the service to start.  I believe it relates to this where they're talking about the need for a custom SELinux policy.
Has anyone else encountered this? If so, would it be possible to get this added to the role (I wouldn't mind contributing, I would just need to figure out the SELinux stuff), but I'm surprised that this hasn't been brought up or caught by anyone (or in testing).
RUNNING HANDLER [dj-wasabi.zabbix-agent : restart zabbix-agent] ********************************************************************************************
fatal: [vagrant]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to restart service zabbix-agent: Job for zabbix-agent.service failed because a configured resource limit was exceeded. See \"systemctl status zabbix-agent.service\" and \"journalctl -xe\" for details.\n"}

  5386:20170621:002521.382 using configuration file: /etc/zabbix/zabbix_agentd.conf
  5386:20170621:002521.382 cannot set resource limit: [13] Permission denied
  5386:20170621:002521.382 cannot disable core dump, exiting...

$ cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)

Oh, and this one: https://bugzilla.redhat.com/show_bug.cgi?id=1393332

Hi @fxfitz I have not encountered it so far, but if you want to create a pr is all fine!

Same problem here.

Quick solution: semanage permissive -a zabbix_agent_t

Ansible solution:
tasks:
- name: Install policycoreutils-python
yum: name=policycoreutils-python state=installed
become: true
 - name: Allow zabbix_agent to start (SELinux)
   selinux_permissive:
    name: zabbix_agent_t
    permissive: true
   become: true

I merged an PR. You can enable selinux by setting: zabbix_selinux: True into the group_vars. Is there a possibility that you can check if this all works ok?

Will do! I'll let you know shortly. :-)

@dj-wasabi This does appear to work completely for us! I would appreciate it if you could release the latest to Galaxy for us! :-D

Yes, will create a release probably this weekend or Monday.

Thanks!

I've uploaded release 0.10.0 into the Galaxy.

LGTM! Thanks!


Add scheduledEvents field on audit log object

Add scheduledEvents field on audit log object
#1828

https://github.com/discordeno/discordeno/blob/40ef1f963a6ee15b326b01c72cb1def5f63918fc/src/helpers/guilds/getAuditLogs.ts#L19
This also requires fixing here. Scheduled events should be added here also

@Skillz4Killz Is there any transformer for thread? I can't seem to find one (interface AuditLog has threads: Channel[] but return value of getAuditLogs function missing threads)

@Skillz4Killz anything else I need to do?

Oops DON'T MERGE

Argument of type 'string | import("file:///C:/Users/lts20050703/Documents/GitHub/discordeno/src/types/messages/createMessage").CreateMessage' is not assignable to parameter of type 'string | import("https://deno.land/x/discordeno@13.0.0-rc11/src/types/messages/createMessage").CreateMessage'.
  Type 'CreateMessage' is not assignable to type 'string | CreateMessage'.
    Type 'import("file:///C:/Users/lts20050703/Documents/GitHub/discordeno/src/types/messages/createMessage").CreateMessage' is not assignable to type 'import("https://deno.land/x/discordeno@13.0.0-rc11/src/types/messages/createMessage").CreateMessage'.
      Types of property 'components' are incompatible.
        Type 'import("file:///C:/Users/lts20050703/Documents/GitHub/discordeno/src/types/messages/components/messageComponents").MessageComponents | undefined' is not assignable to type 'import("https://deno.land/x/discordeno@13.0.0-rc11/src/types/messages/components/messageComponents").MessageComponents | undefined'.
          Type 'MessageComponents' is not assignable to type 'ActionRow[]'.
            Type 'import("file:///C:/Users/lts20050703/Documents/GitHub/discordeno/src/types/messages/components/actionRow").ActionRow' is not assignable to type 'import("https://deno.land/x/discordeno@13.0.0-rc11/src/types/messages/components/actionRow").ActionRow'.
              Types of property 'components' are incompatible.
                Type '[SelectMenuComponent | ButtonComponent | InputTextComponent] | [ButtonComponent, ButtonComponent] | [...] | [...] | [...]' is not assignable to type '[SelectMenuComponent | ButtonComponent] | [ButtonComponent, ButtonComponent] | [ButtonComponent, ButtonComponent, ButtonComponent] | [...] | [...]'.
                  Type '[SelectMenuComponent | ButtonComponent | InputTextComponent]' is not assignable to type '[SelectMenuComponent | ButtonComponent] | [ButtonComponent, ButtonComponent] | [ButtonComponent, ButtonComponent, ButtonComponent] | [...] | [...]'.
                    Type '[SelectMenuComponent | ButtonComponent | InputTextComponent]' is not assignable to type '[SelectMenuComponent | ButtonComponent]'.
                      Type 'SelectMenuComponent | ButtonComponent | InputTextComponent' is not assignable to type 'SelectMenuComponent | ButtonComponent'.
                        Type 'SelectMenuComponent' is not assignable to type 'SelectMenuComponent | ButtonComponent'.
                          Type 'import("file:///C:/Users/lts20050703/Documents/GitHub/discordeno/src/types/messages/components/selectMenu").SelectMenuComponent' is not assignable to type 'import("https://deno.land/x/discordeno@13.0.0-rc11/src/types/messages/components/selectMenu").SelectMenuComponent'.
                            Types of property 'type' are incompatible.
                              Type 'import("file:///C:/Users/lts20050703/Documents/GitHub/discordeno/src/types/messages/components/messageComponentTypes").MessageComponentTypes.SelectMenu' is not assignable to type 'import("https://deno.land/x/discordeno@13.0.0-rc11/src/types/messages/components/messageComponentTypes").MessageComponentTypes.SelectMenu'.
                                Property 'InputText' is missing in type 'import("https://deno.land/x/discordeno@13.0.0-rc11/src/types/messages/components/messageComponentTypes").MessageComponentTypes'.

@Skillz4Killz reverted.


Add expect_field! macro

Added expect_field! macro:
https://github.com/knox-networks/bigerror/blob/93b087f0ee8447b55ceb67efd980711d0c6cfba6/src/lib.rs#L982-L988
the above expect_field! invocation desugars into:
// ...
let my_field = bigerror::OptionReport::ok_or_not_found_field(my_struct.my_field, "my_field")?;
// ...

added FrError
added SetupError
added just printerr <test::uri> to show the error trace of a given unit test

@Mergifyio queue default


raylib: Fix audio

When upgrading from 4.2.0 to 4.5.0 in #243155 the audio fix was
removed. This fix didn't apply properly any more, because the cmake
build in 4.5.0 is producing shared objects with the wrong version in
the name.
The commit https://github.com/raysan5/raylib/commit/0d4db7ad7f6fd442ed165ebf8ab8b3f4033b04e7
which fixes the versioning issue does not appear to have made it into
the 4.5.0 tag.
Removing the audio fix did actually makes the project compile, however
when running games built against raylib, no audio device was found.
Description of changes

Added patch to fix version of lib in cmake build
Restored the audio fix that was present in 4.2.0 that is still relevant

Things done
I have tested a few games in raylib-games to make sure the audio works on my machine (NixOS 23.05)

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

If you have the time, maybe @t4ccer or @drupol could review this PR? :innocent:

Thanks! :smile:
What are the next steps to get this merged? Wait for CI? And then someone with write access can merge it or is it automated?

I'll wait for the ci to be done and merge afterwards

I'll wait for the ci to be done and merge afterwards


Remove OP Tag from anon

https://stacker.news/items/223995

I don't think I can "self-assign" this, but I can make this change!

Closed in #422


[Feature Request] Variable Fonts Support

I tried to use the Bold and Condensed styles of the Bahnschrift font without success as the variations are in a single file.
I found this demonstration of variable font with fontkit.
https://github.com/devongovett/fontkit-demo

Closing this for now. Added it to the roadmap in https://github.com/Hopding/pdf-lib/discussions/998.


🐛 Bug Report: Unable to use a different name for the Authorization token

📜 Description
We use an external authorization layer on our ingresses, and configured oauthProxy as the auth provider.
While some plugins properly implement the FetchMiddlewares.injectIdentityAuth method, which allows us to use a custom header name, there are multiple places in code where we assume the name of the header is 'Authorization' (examples: https://github.com/search?q=repo%3Abackstage%2Fbackstage+"Authorization%3A+`Bearer"+language%3ATypeScript+path%3A&type=code) - techdocs, catalog being the most striking.
LE: this is by design. Fronted plugins must use fetchAPI while backend plugins must pass an Authorization header. The bug scope is reduced to only fronted plugins.
👍 Expected behavior
All frontend API  requests should use the configurable fetchAPI so that the header name can be configured and not overlap with other authentication layers.
👎 Actual Behavior with Screenshots
Authorization header is (sometimes) hardcoded
👟 Reproduction steps
Try to change the name of the Authorization header.
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Hey 👋 ! This is a bit of a two-headed problem.

Some clients haven't been migrated to the new fetchApi in the frontend or pulled code from older implementations. These are pretty easy to find as they use the browser's fetch and call identityApi.getCredentials. Based on the number of plugins that are still doing this, we may need to update the docs for this as well.
Some clients are intended to be consumed by both the frontend and the backend. These are a bit more difficult to transfer if they aren't already, the CatalogClient is a great example of this. It needs to support service-to-service requests as well as frontend authenticated requests. In the frontend, it uses the fetchApi, https://github.com/backstage/backstage/blob/patch/v1.22.0/plugins/catalog/src/plugin.ts#L63-L71 and in the backend uses cross-fetch. In the backend, the pattern of calling it looks something like this, https://github.com/backstage/backstage/blob/patch/v1.22.0/plugins/catalog-backend-module-backstage-openapi/src/InternalOpenApiDocumentationProvider.ts#L123.

The project has settled on using Authorization for backend requests, what we call service-to-service auth. For frontend requests, we should definitely be consistent in using fetchApiRef.
There's also a bit of work going on in #2260 that will affect the pattern of calling these clients from the backend.

Total side note @aramissennyeydd - that was actually meant to use node-fetch :) Not that it makes a huge difference in practice.

@freben Ooo, that would make sense. Should I update the OpenAPI template for that? I was basing off of the existing CatalogClient.

For backend, yeah.
The deal for the catalog has been

in the frontend, inject fetchApi (whatever it happens to use under the hood, which likely is the native browser fetch)
in the backend, inject node-fetch and supply tokens to each individual call.

Now with the new auth work we're doing, we'll see if that backend picture shifts or not :)

Wait, wouldn't this fit into the last section of the ADR?

Isomorphic packages should have a dependency on the cross-fetch package for mocking and type definitions.

Just spent like 15 minutes going down the rabbit hole of node-fetch as fetch not working 😅 .

As which particular fetch? ;)
yeah I see the catalog client actually uses global.fetch as its input type but uses cross-fetch as the default actual fallback implementation

There's also a bit of work going on in https://github.com/backstage/backstage/pull/2260 that will affect the pattern of calling these clients from the backend.

@aramissennyeydd I believe #2260 is the wrong link here?
If I understand correctly, frontend should be consistent in using the fetchApi (which allows the authorization header to be named differently) while backend (service-to-service) must use Authorization. We self host backstage so if I'm not mistaken backend traffic doesn't leave the pod - there are scheduled tasks that run and talk to the API but I assume they do it on localhost:7007.

@alexef Yup, should be #22603, must have accidentally deleted the last digit. And yes, you're correct, the frontend should use fetchApi and the backend should continue to use Authorization. Backend traffic shouldn't leave the pod, but some users may have split backends with traffic going between pods.
We'd love your help in making that frontend consistency happen!

ok, so here is the battle plan. frontend plugins to adjust to use the fetchApi:

plugins/todo
plugins/sonarqube
plugins/search
plugins/rollbar
plugins/linguist
plugins/kafka
plugins/kubernetes-react
plugins/jenkins
plugins/fossa
plugins/devtools
plugins/catalog-import
plugins/azure-sites
plugins/azure-devops

frontend plugins to adjust passing auth with configurable header name but without fetchApi:

plugins/techdocs (uses event-source-polyfill and hardcoded Authorization header name)
plugins/scaffolder (same)

need more clarity:

plugins/permission-common - common library, but it hardcodes the header name
packages/catalog-client - should we just not pass options.token when the library is used from client code? or indicate somehow that only backend code may bring its own token?

can I bundle multiple plugin updates in one PR or should I do one per plugin?

The BEP explicitly calls out in its non-goals section that it does not aim to make room for the ability to change out the Authorization header as the carrier.
One big reason for leaving that out of that particular workstream is to not scope creep. But also, we realize that Authorization is uniquely positioned in the sense that it doesn't get logged or otherwise handled in such a way that it might be compromised. All parties in all call chains know the semantics of how to handle it. Therefore it seemed like something that if it were to be made a priority, it warranted being a separate thing to look into.
In the current work based on that BEP, the old contrib article for securing your backend goes away entirely, and is replaced by the platform "forcibly" locating, validating and unpacking the incoming credentials so that when the plugin is reached, the validity and chain of trust for the caller is already established. And the platform code will only, as part of this initial work at least, look at the Authorization header.
We did speak a bit about this subject when we started out, which is why it's mentioned at all in the non-goals. There were some ideas that were floated, including using multiple Authorization headers.
To get unblocked, sure, if you only want to deal with the frontend calls to the backend, you could replace the fetchApi and then on the server side have a small middleware at the very top that looks for the custom header and injects it again as an authorization header so the rest of the stack gets happy. But I'm not sure we have the ability in the new backend system yet to inject such a middleware THAT high up that it's even happening before auth handling. 🤔
I will say though, moving forward with ensuring that the fetchApi is universally used is a massively valuable thing either way. And if/when there's official support for alternative headers, the groundwork has been laid.

I've got a PR for updating the Azure DevOps, DevTools, and Linguist plugins 👍
https://github.com/backstage/backstage/pull/23046

@freben Thoughts on a new eventSourceApi that uses EventSourcePolyfill under the hood for plugins/catalog and plugins/scaffolder (to be used for other SSE's as well)?
On a bit of a separate note, might it be worth moving some of that backend complexity to an abstracted backend implementation of fetchApi? Rugvip added some thoughts in the BEP around that, https://github.com/backstage/backstage/blob/master/beps/0003-auth-architecture-evolution/README.md?plain=1#L319-L324, but I'd be curious to see if this is something we can revisit especially as we start adding more to the service-to-service request layer. This would also hopefully save us entirely from passing the token into the client for just backend requests. Might be follow on work after the BEP/implementation lands.
@alexef For the CatalogClient, yes, we shouldn't be passing token when this is used in the frontend. I'm not sure if this a restriction we can enforce, but it should generally not be happening. For the PermissionClient, I think this should be updated to follow the pattern in CatalogClient (allowing an override for the fetch implementation it uses instead of just using cross-fetch).
For PRs, I'd recommend splitting it into 2 pieces, the PermissionClient updates and the frontend fetchApi updates. @awanlin is a speed demon and already hopped on his plugins 😁 .

@freben Thoughts on a new eventSourceApi that uses EventSourcePolyfill under the hood for plugins/catalog and plugins/scaffolder (to be used for other SSE's as well)?

Hm maybe. The usages are pretty few though. Would it be worth making it something even higher-level in its naming, so that it could support other tech backing it, or does that just make things unnecessarily complex? Probably.

@freben

then on the server side have a small middleware at the very top that looks for the custom header and injects it again as an Authorization header so the rest of the stack gets happy.

how do I add a middleware to my backend, I couldn't find an example?

@alexef You register a custom httpRouter service, and pass in a configure callback to it that adds what you want.
Something along the lines of (not tested ...)
backend.add(rootHttpRouterServiceFactory({
  configure({ app, applyDefaults() }) {
    app.use(myMiddleware);
    applyDefaults();
  }
});

tested, works!

I wonder if another approach here could be to switch to a fetch-based event source. Afaik there's nothing particularly special about the EventSource API, and it's just a client that knows how to slowly parse a chunked HTTP response.
Quick search found https://github.com/Azure/fetch-event-source, which could be a good candidate. It allows for a custom fetch implementation to be passed too.

I can try an alternative implementation using microsoft/fetch-event-source. thanks for the pointer!

I can see that some of the plugins in the list were moved unmodified to https://github.com/search?q=repo%3Abackstage%2Fcommunity-plugins Authorization&type=code
will follow up with the remainder

https://github.com/backstage/backstage/pull/24861 and https://github.com/backstage/backstage/pull/24878 ready

Not fully completed (missing events and a finall checkup that no hardcoded indentityApi token remains)

@alexef How can I change the name of the backstage authorization header?

@ggkoning first of all, in packages/backend/src/index.ts, you need:
...
const backend = createBackend();
 backend.add(rootHttpRouterServiceFactory({
   configure: ({ app, applyDefaults }) => {
     app.use((req, _, next) => {
       if (req.headers['backstage-authorization']) {
         req.headers.authorization = Array.isArray(req.headers['backstage-authorization']) ? req.headers['backstage-authorization'][0] : req.headers['backstage-authorization'];
         delete req.headers['backstage-authorization'];
       }
       next();
     });
     applyDefaults();
   },
 }));

(to trick the backend into consuming authorization from the custom header)
then in: packages/app/src/apis.tsx:
...
 createApiFactory({
     api: fetchApiRef,
     deps: {
       configApi: configApiRef,
       identityApi: identityApiRef,
       discoveryApi: discoveryApiRef,
     },
     factory: ({ configApi, identityApi, discoveryApi }) => {
       return createFetchApi({
         middleware: [
           FetchMiddlewares.resolvePluginProtocol({
             discoveryApi,
           }),
           FetchMiddlewares.injectIdentityAuth({
             identityApi,
             config: configApi,
             header: {
               name: 'Backstage-Authorization',
               value: (backstageToken) => `Bearer ${backstageToken}`,
             }
           }),
         ],
       });
     },
   }),

(to trick clients to send the custom header instead of default)

@alexef Where do I need to import rootHttpRouterServiceFactory from?

@alexef Thanks it works. You said that it is not fully completed yet what can I do to help?

@ggkoning thanks for offering. you can try to spot other frontend->backend clients that don't use the fetchApi or that hardcode the "Authorization" header. (backend->backend is fine)
also, similar changes to those in the PR linked to this ticket need to be done to the plugins that moved out in: https://github.com/backstage/community-plugins

@alexef I want to make the changes to this plugin https://github.com/backstage/community-plugins/tree/main/workspaces/jenkins/plugins/jenkins But how can I locally add  and test that this plugin will work in our backstage deployment?

@alexef I don't know how to test it but do you think these changes I made are good? https://github.com/backstage/community-plugins/pull/548


Fix CVE of undertow lib

retest this please.

Seems update to xnio-3.3.8 final is still failing the ftests. Maybe we should wait for new undertow update(I saw they have 2.0.22.Final now in github: https://github.com/undertow-io/undertow/tree/2.0.22.Final)


the first 787-8 livery, TUI

@kolos26  can you try to fix the tail

how do you make these maps so fast!?!? even if the aircrafts are not even available yet!?!?

how do you make these maps so fast!?!? even if the aircrafts are not even available yet!?!?

I have no idea


optimizer refactor

@piiswrong can you fix the lint error? We should aim to bring quick refactors in

Is the name lr_mult commonly used in learning rate scaling?
Please do the following things

Add a few unit testcases on the new attribute function to ensure setter/getter works correctly.


URDF loading problem

Describe the bug
Cannot create instance of <class 'compas.robots.model.geometry.Origin'>. Message=init() takes at most 4 arguments (5 given)
To Reproduce
Steps to reproduce the behavior:

Rhino 6, Grasshopper.
See the URDF below.
See the URDF below.
See error:

Runtime error (TypeErrorException): Cannot create instance of <class 'compas.robots.model.geometry.Origin'>. Message=__init__() takes at most 4 arguments (5 given)

Traceback:
  line 143, in parse_element, "C:\Users\sercan\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\compas\files\urdf.py"
  line 128, in parse_element, "C:\Users\sercan\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\compas\files\urdf.py"
  line 128, in parse_element, "C:\Users\sercan\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\compas\files\urdf.py"
  line 48, in __init__, "C:\Users\sercan\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\compas\files\urdf.py"
  line 65, in from_file, "C:\Users\sercan\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\compas\files\urdf.py"
  line 103, in from_urdf_file, "C:\Users\sercan\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\compas\robots\model\robot.py"
  line 30, in script

Expected behavior

Robot model loaded successfully.

Screenshots

Desktop (please complete the following information):

Windows 10
Python 3.7
conda

Additional context

URDF here: https://github.com/gramaziokohler/rob_tech_on_site_construction/blob/master/docs/robot_description/chiron/robot_description.urdf

Hi @philianeles! in line  283 of your file you have 4 values for origin, but only 3 are allowed (x y z):
<origin rpy="-1.57079632679 -1.57079632679 0" xyz="0 0.3124 -0.0004177 0"/>
That's the problem.

Closing this, it should work when you change it.

👌


merge from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 -x 'tests/**/*.mjs' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/*-test.mjs' as in template
chore(package): set $.ava.extensions='mjs' as in template

Coverage increased (+0.8%) to 41.893% when pulling b8702efbea2593af6b76a71acab0b69a0c167717 on npm-template-sync/1 into e1e8c7456347845dbd70454a7b795946fa86d0fc on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Not working on IE

I have tested the demo on IE 11 , it is not working.
Chrome works like a charm.

Thanks for letting me know about this. So, currently this directive is not a proper angular2 module, I am planning to covert it into proper module first. I will try to cover this issue in between. If you have any idea why it is not working please share that would be really helpful.

The strange thing is that for me its not working in IE11 either but only when I try it from a 'real' build. When I try it with the angular-cli and 'ng serve' it works in IE11.
I really dont understand why..

@ewolution94  the demo is not updated yet, may be this is the issue. Also, I haven't able to test it on IE11.
@sharpCompiler and @ewolution94  do you guys know how to test it on Mac for IE11 any guidance regarding that would be great help.
Thanks.

I witten a new one the works with all browsers.
Den 30 mars 2017 14:16 skrev "ewolution94"<EMAIL_ADDRESS>
The strange thing is that for me its not working in IE11 either but only
when I try it from a 'real' build. When I try it with the angular-cli and
'ng serve' it works in IE11.
I really dont understand why..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CoderAjay/ng2Draggable/issues/10#issuecomment-290393184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhkmPyazXttDW0q6ynd_WsrjVOkQXxbks5rq50xgaJpZM4MkbwP
.

@sharpCompiler Could you share it please? :)

@sharpCompiler Can you please share with us ?

I will make a project real soon.
Den 15 apr. 2017 18:06 skrev "Ali Al-Obaji"<EMAIL_ADDRESS>
@sharpCompiler https://github.com/sharpCompiler Can you please share
with us ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CoderAjay/angular-draggable/issues/10#issuecomment-294302312,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhkmMPxy9YTLIR9gv9ezr2-8k22LLbjks5rwOsDgaJpZM4MkbwP
.

@argc79 just made it work for all modern browsers.
https://github.com/AliObaji/classHistory/tree/master/src/app/directives

@AliObaji @argc79 @CoderAjay @ewolution94
This I just made it public
https://github.com/sharpCompiler/dragon
This is the first check it but I will refactor it during the time.
There is an example in it as well.
Best regards.

it is not working with Mozilla @sharpCompiler


Migrate github actions to Node 16

As described here: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
Our current actions started to fail, perhaps, due to the older version of node.

Seems like we are actually using node 17 in CI. Seems like the link for the windows binary is broken: https://nodejs.org/dist/v17.9.1/win-x64/node.exe

Ah, it's a bug on their side: https://github.com/nodejs/build/issues/3231
Shall we close this?

In the bottom of Github actions, e.g. https://github.com/informalsystems/quint/actions/runs/4451572805

Ah, I didn't see that. Seems like we will have to update the actions we use from @v2 to @v3 and that might fix this.

What you need to do
For Actions maintainers: Update your actions to run on Node 16 instead of Node 12 (Actions configuration settings)
For Actions users: Update your workflows with latest versions of the actions which runs on Node 16 (Using versions for Actions)

From the link in the warnings

Related: #867
Probably makes sense to streamline versions between docs and CI.

This is resolved afaik!

Ah yes, I didn't know there was an issue. Fixed in #1171


Have away to fetch the project id from the environment

Currently we can fetch the authentication credentials from the environment, via gcloud's default app credentials, metadata server, etc... We should be able to do the very same for the project id, the metadata server serves that and it should be possible to get that from gcloud if necessary or even an environment variable.
I think that this would simplify the code even further and allow the code to be written without hardcoding the project id on it.

Agreed - this is a request under consideration already on a cross-platform basis. I will check on the progress though...

No update on this at the moment.

Closing this as stale - I'm not expecting this to change any time soon, nice as it would be.


Version/1.0

@Matiduck - please find revise version of the library.

Map<T1, T2> method was added to faciliate print available command either by writing custom HelpCommandHandler or using out of the box HelpCommandHandler. Previously there was a problem with circular dependency, and all handlers were initialized unnecessary - only to return CommandType.
RootCommandHandler was replaced by static method
IArgumentDeserializer was extrected out - for custom implementation if needed.

I would consider to slowly closing the discussions and every remaining topic move into Issues section. My proposition is to bundle issues into prepared Version 1.1 milestone


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1146

Questions ?
Please refer to the Backport tool documentation


[2.3] hotfix/#700 excel dn behavior inconsistent with pandas

#700

Please, before merging wait for https://github.com/Avaiga/taipy-core/pull/709 to be approved to propagate changes.


Allow to not pass mobile phone to report error (API call)

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


Revert "Merge pull request #195 from williamtsoi1/master"

Sysinternals changed urls back.
This reverts commit 8b68d4958c283101e7624a20702686a982f4f357, reversing
changes made to 0ae9e8a721a1b3a7ab0962118c7e93ae3f9dba86.

@bmolz Thanks. At the moment both URL's work fine. Just wait and see what happens next ;-)

@StefanScherer @bmolz What about moving away from SDelete in favor of a pure PowerShell alternative? At some point this will be a problem with Windows Nano, thanks @mwrock for pointing this out.

@sneal @mwrock Good fund! SDelete is probably 32bit only.

yeah. that was the issue @StefanScherer - 32bit only

OK, http://download.sysinternals.com/files/sdelete.zip now returns 404, back to upper-case UrL. I'll merge this one to fix it for now and close #202.

Thanks @bmolz


Add tubelib mod

Resolves partially #12

Since I have done some updates on the main branch, I'll close this PR and restart the feature, since more than the tubelib2 mod needs to be added. The tubelib2 mod is just a lib, it will not add anything visible to the server by itself.
Thanks for the help! Kindly follow up on #12 discussion.

Ok


@before_event w/set[BUG]

I used example:
class TimestampMixin(BaseModel):
    created_at: datetime = Field(default_factory=datetime.utcnow)
    updated_at: Optional[datetime] = None

    @before_event(Insert)
    def set_created_at(self):
        self.created_at = datetime.utcnow()

    @before_event(Update, Save, SaveChanges, Replace)
    def set_updated_at(self):
        self.updated_at = datetime.utcnow()

And then excuted:
product = await Product.get("644465ec0c9c7f6f19dc232a")
await product.set({Product.name: "Gold bar"})

The event is lunched, but the field "updated_at" not update.
If I instead used:
await product.save()

work fine!

There are two different approaches to update documents:
Saving changes to existing documents by setting an instance attribute and then using save or replace to push the changes to the database.
Alternatively Update queries via update, set etc. will apply changes directly on the database level and then update the application side instance to match the database document.
In the example set_updated_at is correctly executed and temporarily changes the instance attribute updated_at.
But product.set({Product.name: "Gold bar"}) only updates the name field in the db and the attribute updated_at is reset to None, as this is the state of the db side document (see code.)
So probably not a Bug? However the Event-based actions Documentation could include a hint, that @before_event(Update) decorators are not appropriate for methods that alter instance attributes, as this mixes the two update approaches "instance-then-db" and "db-then-instance".

The explanation is very clear, thank you very much for your time answering.


Change prepare hook to prepublishOnly

Hey there!
Thank you for maintaining this plugin!
I wanted to ask if it would be possible to use the prepublishOnly hook instead of prepare for the build script.
I have created an Nx monorepo with our capacitor whitelabel apps and to make dependency management easier I have adpoted this system:
https://github.com/nxext/nx-extensions/discussions/794#discussioncomment-5218635
And the problem is that the prepare hook is executed when installing the the plugins to the inner package.json with
npm install file:../../node_modules/@capacitor-community/barcode-scanner.
So I wanted to ask if it was possible to use the prepublishOnly hook instead?
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 3989f9c..5033efe 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -36,7 +36,7 @@
     "build": "npm run clean && tsc && rollup -c rollup.config.js",
     "clean": "rimraf ./dist",
     "watch": "tsc --watch",
-    "prepare": "npm run build",
+    "prepublishOnly": "npm run build",
     "verify": "npm run verify:ios && npm run verify:android && npm run verify:web",
     "verify:ios": "cd ios && pod install && xcodebuild -workspace Plugin.xcworkspace -scheme Plugin -destination \"platform=iOS Simulator,name=iPhone 12\" && cd ..",
     "verify:android": "cd android && ./gradlew clean build test && cd ..",

Don't see an issue in this, I will create a release today :)


DASH LiveTV stream from mediavitrina.ru not playing

Checklist

[x] I'm reporting a feature request
[x] I've verified that I'm running youtube-dl version 2019.07.30
[x] I've searched the bugtracker for similar feature requests including closed ones

Description

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://edge02r.mediavitrina.ru/dash-live11/streams/iz/iz.mpd']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2019.07.30
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: none
[debug] Proxy map: {}
[generic] iz: Requesting header
WARNING: Falling back on generic information extractor.
[generic] iz: Downloading webpage
[generic] iz: Extracting information
ERROR: No video formats found
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp3oef8xsp\build\youtube_dl\YoutubeDL.py", line 796, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp3oef8xsp\build\youtube_dl\extractor\common.py", line 530, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp3oef8xsp\build\youtube_dl\extractor\generic.py", line 2379, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp3oef8xsp\build\youtube_dl\extractor\common.py", line 1327, in _sort_formats
youtube_dl.utils.ExtractorError: No video formats found

Stop mentioning unrelated 3rdp

@dstftw I don't see any duplicates from the link you gave.


[WFLY-4472] Upgrade HornetQ to 2.4.6.Final

[WFLY-4282] Add listDeliveringMessages and listScheduledMessages to JMS Queues

Linux with security manager Build 1133 is now running using a merge of 12f374ea05c06ccd596d797e16c27c63d5f86293

Windows Build 1269 is now running using a merge of 12f374ea05c06ccd596d797e16c27c63d5f86293

Linux Build 6157 is now running using a merge of 12f374ea05c06ccd596d797e16c27c63d5f86293

Linux with security manager Build 1133 outcome was SUCCESS using a merge of 12f374ea05c06ccd596d797e16c27c63d5f86293
Summary: Tests passed: 814, ignored: 352 Build time: 0:06:11

Windows Build 1269 outcome was SUCCESS using a merge of 12f374ea05c06ccd596d797e16c27c63d5f86293
Summary: Tests passed: 2833, ignored: 412 Build time: 0:53:34

Linux Build 6157 outcome was SUCCESS using a merge of 12f374ea05c06ccd596d797e16c27c63d5f86293
Summary: Tests passed: 2832, ignored: 412, muted: 1 Build time: 0:53:43


Support component integrity verification

This issue expands on issue in upstream dependency track. An initial POC for this has been completed and demoed using hyades-apiserver and hyades
Below features need to be addressed as part of actual implementation:
### Tasks
- [ ] Allow integrity check for maven on components
- [ ] The integrity check would be enabled/ disabled universally with a single feature flag/ config in apiserver
- [ ] The meta information along with the published date and hashes would be sent back from hyades to apiserver in one message in the same topic as meta analysis result.
- [ ] When published date for a component is already present in the db, then we do not need to make the api call for it.
- [ ] This information of component hashes and published date would be stored in a separate table.
- [ ] This table would be used to perform hash check on components, in case info is present. If not, api call would be requested.
- [ ] Regardless of whether the integrity check is enabled/ disabled, we would fetch the information of component and store it in the db. If integrity check is enabled, the analysis would also be performed and stored. If not enabled, the analysis would not be performed
- [ ] Implement this functionality for npm and pypi as well. The initial understanding is that the source of truth used to validate integrity information uses the head request to dependency files to reveal their checksum information. This would be expanded on in the future.
- [ ] In addition to bom upload, this check should also happen on re analysis and manual addition of components.
- [ ] Project deletion should happen successfully.
- [ ] Unit tests for the entire functionality
- [ ] Future enhancement : add validation on repo URLs if integrity check can be performed on it or not.

Based on the PR review for https://github.com/DependencyTrack/hyades/pull/727 we wanted to also store the published date information from the same end point that is used to fetch integrity information for packages.
However, as per current design, integrity check is an optional check that the user can enable/ disable for a repo of choice and then the integrity check would be performed for components considering the configured repo as the source of truth.
This is viable for integrity checks alone.
But published date is a field that we want for all components all the time and is not optional. Also, the repository from which the component is actually fetched should be used to get the published date for the component. Thus we cannot use the integrity check external call as is to support the published date feature.
There are a few options on how we could get publised date too:

Use separate repos to get published date information for packages. For example, we could use maven central to get published date for maven packages. In this case, the user can configure only one source from where the published date would be fetched. If the user does not select any source, we will use maven central. In this case, the integrity check info fetch is separate from the published date config. Can also use artifactory in this sense.
Use deps.dev as the central source of truth for both integrity check and published date. In this case, allow the user to configure integrity check as currently is available. But published date is always fetched for component, if new, from deps.dev. This is not configurable by the user.
The downside is that the published date feature is an additional call to a similar end point if it is not the same configuration as that used for integrity check.
This is found to be part of the head request response as was done for integrity check. The header is x-modified.. to be looked for in this call.

Meeting notes from discussion on September 18 2023.
Use Cases
Integrity Verification

Detection of "smuggled" packages (Replacing of packages in the package repository)

Modified package was resolved from internal repo during build, and is included in SBOM
Comparison of package hashes from SBOM with hashes from Maven Central will yield a mismatch

Detection of Man In The Middle’d packages

Bad actor replaces packages during build when package manager fetches them from repository

Nice-to-have: There should be metrics of how many integrity violations occurred per component / project

Doesn’t add too much value because metrics in the UI are not used that much

It is not necessary to configure repositories specifically for integrity checks; Use the same repository for latest version check, integrity check, published date
Integrity check enabled/disabled should be a feature flag at first

When disabled, analysis and metrics inclusion would not happen
Fetching of the data (hashes, published date) will happen no matter if enabled or not

Multiple Repositories for integrity verification

Being able to use Artifactory / other custom repositories
Configuration would be priority-based, such that Maven Central can be assigned a higher priority than internal repos

Fall-through logic; Iterate through all repos, return on first match, otherwise proceed to next repo

Assumption: Only a single repository should match, we only need to store results from one, and not multiple
Future: deps.dev could be added as another repository

pkg:maven/com.citi/citi-lib → Artifactory (Internal)
pkg:maven/org.springframework/spring-core → Maven Central
Published Date

"Component Age" policies
Displaying published date in UI / return in REST API

dtrack.repo-meta-analysis.component

Consumer listening for this topic will fetch:

Latest Version
Published Date
Hashes

Problems:

Latest Version changes over time, published date and hashes (hopefully) do not
More precise details and flow to be added by @VithikaS

Create new table to store hashes

 CREATE TABLE IF NOT EXISTS public."COMPONENT_METADATA" (     "ID" bigint NOT NULL,     "PURL" character varying(1024) NOT NULL,     "MD5" character varying(1024),     "SHA1_HASH" character varying(1024),     "SHA256_HASH" character varying(1024),     "PUBLISHED_AT" timestamp with time zone,     "LAST_FETCH" timestamp with time zone,     "REPOSITORY_ID" bigint     CONSTRAINT "COMPONENT_METADATA_PK" PRIMARY KEY ("ID") )

Create data model and queries for new table

Create Initialiser which will kick off update of new table with hash information and publishedAt date on application startup

Check that no records exist in COMPONENT_METADATA. Select count(ID) should be 0
If empty,  Insert into COMPONENT_METADATA table select DISTINCT purls from COMPONENT table. publish_date and hashes will be null
Updated fetch_date and call api to get hashes information for the package type
Repeat for all records where publish date / hashes are null

Task Highlights

[ ] Create new table and queries. @sahibamittal
[ ] Create Initialiser. @sahibamittal
[ ] Hyades-apiserver changes (bom-upload dispatching event; updating new table after repo-meta analysis results). @mehab
[ ] Hyades-apiserver changes (perform integrity analysis if enabled and update db).
[ ] Changes at hyades end (repo-meta analyzer : receiving event, calling repositories, sending data back in repo-meta analysis results). @sahibamittal

AnalysisResult Proto should include fields for Component Metadata
message AnalysisResult {
  // The component this result is for.
  Component component = 1;

  // Identifier of the repository where the result was found.
  optional string repository = 2;

  // Latest version of the component.
  optional string latest_version = 3;

  // When the latest version was published.
  optional google.protobuf.Timestamp published = 4;

  optional bool integrityMetaAvailable = 5;
  optional IntegrityMeta integrityMeta = 6;
}

message IntegrityMeta {
  optional string md5 = 1;
  optional string sha1 = 2;
  optional string sha256 = 3;
  // When the component current version last modified.
  optional google.protobuf.Timestamp currentVersionPublished = 4;
}

AnalysisCommand Proto :
`
message AnalysisCommand {
  // The component that shall be analyzed.
  Component component = 1;
  bool fetch_integrity_data = 2;
  bool fetch_latest_version = 3;
}

Analysis Command notes:
fetch_latest_version flag → map latest_version and latest_version_published.
fetch_integrity_data flag → map current_version_published and hashes info.

initializer → [fetch_integrity_data=true, fetch_latest_version=false]
bom-upload → if integrity data doesn't exist then [fetch_integrity_data=true, fetch_latest_version=true]
else [fetch_integrity_data=false, fetch_latest_version=true]
scheduled anaysis → [fetch_integrity_data=false, fetch_latest_version=true]

A point to note is the change of repository from user when he has already supplied a repository for a package type. If this happens, currently the projects/ components for which the integrity information has already been fetched will not be refreshed with new information. In order to support this feature, keeping in mind that we only support one repository at a time for a given package and not act as mirror for multiple repositories, we could re factor the initializer code to get triggered on whenever the user changes repository url and refresh information for all the existing components.
And then newer projects and components can be filled for information as existing functionality

the changes have now been completed hence closing the issue


Initial public feed

Create MessageFeedServlet.java and add functionality for servlet
Add getAllMessages() to Datastore.java

#14

I tried to consolidate the message function code in Datastore.java, I'm not sure if I did it the best way though. I also merged master into this branch locally, resolved conflicts, and pushed back to this branch.


Fix deprecations and Ember canary/beta

Looks great so far!

It looks like our current blocker is this thing that doesn't have a fix yet https://github.com/emberjs/ember-render-modifiers/pull/33 🙈


Fork repo into CDCgov org

Question from @arnejduranovic
Summary: Fork https://github.com/LinuxForHealth/hl7v2-fhir-converter into CDCgov org

Does anyone know who has permission to create a repo in the CDCGov organization or how I would go about doing that? We want to fork a public repository... https://github.com/CDCgov. This is the library we want to fork: https://github.com/LinuxForHealth/hl7v2-fhir-converter. We have already done this for https://github.com/HL7/v2-to-fhir but that was Carlos and Patricia

It's the same as creating a new repo. Just open a request for a new repo and put in the notes that you want to fork it from somewhere. I think the link is bit.ly/join_cdcgov but adding @boris-ning-usds in case there's a different form or something. I remember quite a few repos getting on CDCGov this way and you can kind of see based on the fork lineage.
You specify that you want to the be the admin, so that will let you send PRs back to the origin and stuff.


Typo "Azure functions"→"Azure Functions"

https://docs.microsoft.com/en-us/azure/azure-functions/functions-develop-local

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

@ggailey777 - Could you review the proposed update to your article?
For reference, the internal cloud style guide says this:
"Use Azure Functions as necessary to distinguish it as an Azure service. It's OK to use just Functions when the context makes it clear you're referring to the Azure service.
To refer to something built using Functions or in a generic reference, use lowercase function app."
Thanks.

#sign-off


Server-side performance fixes for Manage Packages page

https://github.com/NuGet/NuGetGallery/issues/6755
These fixes drastically improve the performance of the Manage Packages page.

Include RequiredSigners in the initial request for packages. Previously, the page was making a SQL request for every package in ListPackageItemRequiredSignerViewModel.

Exit the ChecksPermissionsOnBehalfOfAnyAccount call early. ChecksPermissionsOnBehalfOfAnyAccount has two implementations-- both return whether or not the action can be done on behalf of any owner, but one returns the list of owners the action can be done on behalf as well. To get the full list of owners the action can be done on behalf of, we were enumerating the full list of possible owners every time, even if we didn't care about which owners the action can be done on behalf of. By exiting the loop early when we don't care about the list, we drastically reduce the number of permissions checks that are done on accounts with many packages or packages with many co-owners.

Tested in against NuGetTestAccount on dev, the page won't even load without the fixes. NuGetTestAccount has around 30,000 packages, which is 6 times the number of packages owned by the Microsoft account.
With the fixes, I got page load times of:

Let's get a graph of page load durations for 10-20 iterations before and after.
Let's run against a real DB, like DEV DB.

Agree with @joelverhagen. I'd like to see average/percentile of before and after results, preferably quantified with the %diff (after - before / before * 100) calculation.
I also like to document the investigation by sharing a screenshot of the profile showing the inclusive %CPU before optimization. Of course, you also need to define the scenario that's being tested (e.g., lots of packages, lots of packages with lots of versions, etc).
For instance: https://github.com/NuGet/Engineering/issues/1453

Unfortunately, it's not very easy for me to test an account that loads the page before the change locally against a SQL DB (due to AAD login), so I plan to gather data after this is deployed to DEV.

@scottbommarito You can test with AAD locally. In OneNote "Microsoft Logins (MSA) and NuGet Gallery", search for "Test Accounts for local usage". It would probably be nice if we stored this in the DEV AKV instead.


vuex state wasn't loaded in nuxtjs mounted() after hard-reload

I've been building my first app in nuxtjs but I have some issues with vue state. I've integrated vuex-persistedstate and js-cookie to persist the state.
I'm trying to get the vuex state and set the values in the component inner state (data () {}).
Notification.vue
computed: {
   ...mapState({
     user: state => state.auth.user
   })
 },
mounted() {
  this.notifications = this.user.notification
}

This is working fine if I come to this page from the other page.
But if I reload the notification page directly, this.user(vuex state) is null. if I wrap it in setTimeout(), I'm getting the state correctly even after the reload the page.
for example:
mounted () {
  setTimeout(() => {
    this.notification = this.user.notification
  })
}

I believe this is async issue with vuex & nuxtjs but I don't think it's a good idea to wrap the setTimeout in all components mounted() method.
Is there any way to resolve this?
Many thanks.

I have a similar issue. When i try to update state on Nuxt mounted, the state is updated. But persisted LocalStorage data aren't updated.
It work fine
// store actions
const actions = {
  refresh() {
    commit('SET_MY_STATE', [])
  }
}

// nuxt mounted hook
mounted() {
  setTimeout(() => {
    this.$store.dispatch('myModule/refresh')
  }, 0)
}

But the following don't work
// store actions
const actions = {
  refresh() {
    commit('SET_MY_STATE', [])
  }
}

// nuxt mounted hook
mounted() {
  this.$store.dispatch('myModule/refresh')
}

I encountered this issue awhile back and found that onNuxtReady is executed late. In my case, my auth middleware is executed first and therefore does not recognize the login state of the user. Removed it from onNuxtReady and it works fine.
I'm not sure if there will be side effects in doing so but I'm assuming there's none since store is already available by this time.
import createPersistedState from 'vuex-persistedstate'

export default ({ store }) => {
  createPersistedState({})(store)
}

I encountered this issue awhile back and found that onNuxtReady is executed late. In my case, my auth middleware is executed first and therefore does not recognize the login state of the user. Removed it from onNuxtReady and it works fine.
I'm not sure if there will be side effects in doing so but I'm assuming there's none since store is already available by this time.
import createPersistedState from 'vuex-persistedstate'

export default ({ store }) => {
  createPersistedState({})(store)
}

This solved the problem for me, thank you so much. Can you tell me if this encountered any problem later?

I encountered this issue awhile back and found that onNuxtReady is executed late. In my case, my auth middleware is executed first and therefore does not recognize the login state of the user. Removed it from onNuxtReady and it works fine.
I'm not sure if there will be side effects in doing so but I'm assuming there's none since store is already available by this time.
import createPersistedState from 'vuex-persistedstate'

export default ({ store }) => {
  createPersistedState({})(store)
}

This solved the problem for me, thank you so much. Can you tell me if this encountered any problem later?

Hi @prantaDutta, haven't had issues with it. It is also confirmed in this pull request that it is not necessary to have it inside onNuxtReady.

Removed it from onNuxtReady and it works fine.

How? how did you remove it from nuxt ready? could you provide a code snippet of what you did.


add huggingface TEI Support with intel max GPU

Rahul from Intel liftoff provided me with some code with support for intel GPU max, that he wanted some of the college students to use to process embeddings, I told him that I wanted the college students to design against the OPEA reference standard, and I asked him whether this was implemented inside of huggingface Text Embedding Interface TEI. He was unsure whether or not this was implemented, and so therefore, I am raising a feature request here and adding his code.
https://gist.github.com/rahulunair/5e048b76518962eddeeafaf9bcf8da1b

Hi @endomorphosis , currently the support for Max GPU is not prioritized.


Popup component is not exported

Hello,
I installed 3.0.2, and tried import Popup component, but my IDE says
Module '"react-native-map-link"' has no exported member 'Popup'.
It exports PopupProps and PopupStyleProp, but there was no Popup. Is it intended?

i am having the same issue, any update?

I am having the same issue
version: 3.0.2


Fix stale ProtostarFixture configuration file issue

Protostar fixture needs to be able to recognise changes made to the .toml  (adding contracts, etc) and be able to reload config file in subcommands, so i.e. contracts are not stale.
Example:
https://github.com/software-mansion/protostar/pull/1526#discussion_r1151878758_

@Arcticae what is the expected behavior?

@abulenok ideally, after adding a contract through ProtostarFixture.add_contracts, protostar.toml should be reloaded in the fixture, meaning i.e. fresh construction of the config file object and rebuilding the command objects inside the ProtostarFixture.


j2lint should have an option for verbose logging on stdout

Currently j2lint logs to a file. There should be an option to see the debug logs on stdout as well.

Added --vv option to see the logs on stdout.
PR- https://github.com/aristanetworks/j2lint/pull/22


which version  of PyKDL  is compatible

def urdf_joint_to_kdl_joint(jnt):
    origin_frame = urdf_pose_to_kdl_frame(jnt.origin)
    if jnt.joint_type == 'fixed':
        return kdl.Joint(jnt.name, kdl.Joint.Fixed)

Exception has occurred: AttributeError       (note: full exception trace is shown but execution is paused at: _run_module_as_main)
type object 'Joint' has no attribute 'Fixed'
File "/home/robot/motion_control/humanoid_planning/relaxed_ik_ros2/install/relaxed_ik_ros2/lib/relaxed_ik_ros2/kdl_parser.py", line 62, in urdf_joint_to_kdl_joint
return kdl.Joint(jnt.name, kdl.Joint.Fixed)
File "/home/robot/motion_control/humanoid_planning/relaxed_ik_ros2/install/relaxed_ik_ros2/lib/relaxed_ik_ros2/kdl_parser.py", line 103, in add_children_to_tree
kdl_jnt = urdf_joint_to_kdl_joint(urdf.joints[jidx])
File "/home/robot/motion_control/humanoid_planning/relaxed_ik_ros2/install/relaxed_ik_ros2/lib/relaxed_ik_ros2/kdl_parser.py", line 109, in kdl_tree_from_urdf_model
add_children_to_tree(root)
File "/home/robot/motion_control/humanoid_planning/relaxed_ik_ros2/install/relaxed_ik_ros2/lib/relaxed_ik_ros2/robot.py", line 35, in init
self.kdl_tree = kdl_tree_from_urdf_model(self.robot)
File "/home/robot/motion_control/humanoid_planning/relaxed_ik_ros2/install/relaxed_ik_ros2/lib/relaxed_ik_ros2/relaxed_ik_rust.py", line 73, in init
self.robot = Robot(setting_file_path)
File "/home/robot/motion_control/humanoid_planning/relaxed_ik_ros2/install/relaxed_ik_ros2/lib/relaxed_ik_ros2/relaxed_ik_rust.py", line 210, in
relaxed_ik = RelaxedIK()

rust 1.58.1


make default max_offset on every helix equal to the max end of domain on any helix; closes #351

If the max_offsets of helices are not specified, make the max_offset the same for every helix (by setting it equal to the max end of domain).

I made a mess of the dev and master branches today. Ben and I are going to try  to fix it later tonight. Until then, I'll leave this PR where it is.

When the tests ran they failed and threw an "Instance of 'IllegalDNADesignError'" error. Not sure if this means there is an issue with my code, or if it was caused by committing.

At this point, who knows. I made a mess of things this morning. My goal is to get the dev (and eventually master) branches to look like this commit: https://github.com/UC-Davis-molecular-computing/scadnano/commit/52a03ca2cbbcc5e1029a038691b659a461cfc64f But my naive attempt to do so (doing a PR to merge that commit into dev) fails to actually get all of the changes into dev.

Sorry, it appears that this is going to clobber most of the changes I made in the past week. This is probably my fault from the mess I made this morning. But if you look at the "files changed" tab, it's going to change 48 files and undo a lot of stuff.
Sorry if this is extra work, but it's probably best to just start over and make a brand-new branch, after pull the latest dev branch.