Improved nginx options

Added support for configuration nginx vhost directly in authentic without the need to add a separate entry in the nginx service. I've also added support for using wildcard/multiple domain certificates when using useACMEHost.
Breaking Changes:

forceSSL is not automatic set anymore if enableACME is set
recommendedTlsSettings inside the nginx service is not being automatically set anymore if enableACME is set

Future PRs:

I am currently evaluating if the proxy pass is needed to happen to the https port 9443 or if 9000 on http would be sufficient
I am also willing to upgrade this to 23.11 and therefor update postgres deprecations
Improvements/cleanup regarding package builds

Hey, thanks for the PR!
Without having looked at the changes yet, just a heads-up about your mentioned "Future PRs", I'm currently reworking the packaging approach to make individual components patchable, which is currently extremely inconvenient to accomplish.

Ok, ill wait with the packaging. But I'm still going to file other PR's after this, regarding the nix module.

Ok, I hope I've tested everything. The certificate is now appearing about one hour after setup in the webui. I may goging to improve the deprecation warnings to remote the current breaking changes.

@MarcelCoding, are you talking about the removal of forceSSL and recommendedTlsSettings?
I wonder why you want to remove those, and especially why do you think this would be a better default for all users of this flake.
Do you know that you might as well force these settings by
  services.nginx = {
    recommendedTlsSettings = lib.mkForce false;
    virtualHosts."your.host" = {
      forceSSL = lib.mkForce false;
    };
  };

Okay we could leave them as they are, but to me this seemed like a side effect so nginx. Especially the tls proxy settings. The other thing is more like a beauty thing. I deploy two reverse proxies and the first one directly behind authentic is listening on a non-443 port and therefore a https redirect is not necessary. This is handled by the front facing proxy. Yes I can force this to false. But the tls settings seems to me like an evil side effect.

Hmm, depends on the use case, i guess.
For my use case, it is convenient since it runs on a single machine with no other nginx hosts configured.
I can't tell what the most likely scenario of running authentik will be, so i'd rather stick with the initial settings to not break assumptions people already using this flake might have.

and how about recommendedTlsSettings?

Do they prevent you from running the proxy unsecured? I did not check thoroughly, but my guess would be they only do have an effect when connections are secured, and do not harm otherwise. And then i think, they represent NixOS best practice for running secured nginx hosts, more knowledgeable people than me have put their thoughts into and will keep them updated over time.
So, if this side effect really should turn out to be without effect, why bother?

I mean they change the global SSL configuration of nginx. But nvm I leave it as it was.

Now everything works as expected.

Does it for you? For me, if i build the config with vhost = { enableACME = true; };, it does no longer set forceSSL = true; like it did before.

That is what i was thinking as well, but it turns out that it still does not set forceSSL = true.
Module before changes:
nix eval ./\#nixosModules.default --json --impure --apply 'authentik:
let cfg = (import "${(builtins.getFlake "'$PWD'").inputs.nixpkgs}/nixos/lib/eval-config.nix" { modules = [authentik { config.services.authentik = { enable = true; nginx = { enable = true; host = "example.org"; enableACME = true; }; }; }]; }).config;
in cfg.services.nginx.virtualHosts."example.org".forceSSL'
true

Module after changes:
nix eval ./\#nixosModules.default --json --impure --apply 'authentik:
let cfg = (import "${(builtins.getFlake "'$PWD'").inputs.nixpkgs}/nixos/lib/eval-config.nix" { modules = [authentik { config.services.authentik = { enable = true; nginx = { enable = true; host = "example.org"; vhost.enableACME = true; }; }; }]; }).config;
in cfg.services.nginx.virtualHosts."example.org".forceSSL'
false

Somehow the default value of forceSSL (https://github.com/NixOS/nixpkgs/blob/nixos-23.11/nixos/modules/services/web-servers/nginx/vhost-options.nix#L163) is conflicting with my definition of forceSSL (https://github.com/nix-community/authentik-nix/pull/4/files#diff-d08d64ddbf5f8a384c8213d871167c6f55002970d7312c302b4bd441fafb5e8dR234). If I remove my mkDefault nix failed with a conflict. But I don't know what the default value is not handled as an actual default value but rather like a manual supplied value. This is probably how I imported the part form the nginx module. I will continue to investigate this.

Ok I fixed it, the default value is not treated as the default anymore as soon as you are using mkMerge or similar things.


Find by nested object property

Hey David,
Please take a look at the following example:
    internal class VideoFile
    {
        public string Address { get; set; }
        public long Length { get; set; }
    }

    internal class Video
    {
        [BsonId]
        public int Id { get; set; }
        public VideoFile[] Files { get; set; }
        public string Title { get; set; }
    }

And this piece of code:
    var fileInfo = new FileInfo("some video file");
    var videos =
        DataStore.Videos.Find(v => v.Files.Any(f => f.Length == fileInfo.Length))
            .ToArray();

This code supposed to find videos having a file with same Length as the file specified. However, it always return an empty result. Same code works if I replace Find with FindAll and then apply the Where Linq method. But there are thousands of videos and this is very cpu and memory intensive.
What is your advice?

Hi @falahati, nice to see you again here. I think your problem can be with linq expression "Any". Try do:

First, create an index:
DataSote.Videos.EnsureIndex("idx_length", "$.Files[*].Length");
Now, search using index:
DataStore.Videos.Find(Query.EQ("idx_length", fileInfo.Length));

If you want still using LINQ expression, try:
DataStore.Videos.Find(x => x.Files[0].Length == fileInfo.Length)
Remember: using 0 index doesn't mean search only in first index (0) but it´s simple way to access child array. This linq expression will be translated into $.Files[*].Length

This worked David, Thanks
The code is now a little harder to read and understand but the difference in performance was significant.

Yep, I not "natural" as expected. That's why I'm changing this for v5: Now LiteEngine will work fully with BsonExpression (string expressions) and LINQ will be converted into BsonExpression. That's will be much more transparent to user.

We should be able to do something about indexes too. Now I had to "ensure" them inside my singleton class. But it would be great to be able to define them somewhere inside the model class. We had an attribute for that but I think it is now marked as deprecated.


BuddyPress Compatibility

https://wordpress.org/support/topic/buddypress-avatars-not-syncing/

I don't see any way to make it work in stateless mode.
Might be possible if we save some data in database.

https://github.com/wpCloud/wp-stateless/commit/667d4d430751a36e3c7affeb933f5770f0a1114d#diff-1248ddff5840bb0344e6d6b7bdfe7398

@alimuzzaman what's the status here?

@alimuzzaman can you explain in detail what happens here? I see this commit https://github.com/wpCloud/wp-stateless/commit/20d07d06e479e477d773933b7327d2a5f75f8d7b was reverted later. What 'some new idea' you mean?
And what exactly I should test/review?

@antonkorotkov seems like I have applied that commit later. It was a way to sync the Banner image.
Please test if the avatar/banner image syncing working. Or is there anything more that can be done.
I don't think there is anything left to do than testing.

Ok, will try to setup BuddyPress

Looks like the current state of BuddyPress Compatibility breaks avatars, even not BP avatars.

Going to investigate that.

All avatars work now. Custom user avatars also work and load from GCS.


addition of preview Accept headers in RepositoriesService.ListByOrg causes errors with GHE

Preview headers cause server 500 Errors with GHE (observed with GHE version 2.11 - in particular, it is the application/vnd.github.scarlet-witch-preview+json header that is causing it).  It happens rarely - only on some requests with some specific page parameter value - but when it does, it happens consistently (always for the same request / URL) thus preventing the listing of public repositories.
Currently the several preview Accept types are added to ALL RepositoriesService.ListByOrg calls - even when no preview features are needed or wanted, with no possibility to turn the header addition off.  Maybe this can be made configurable so that clients could at least turn off the Accept header addition - for example, through an additional field in RepositoryListByOrgOptions or some other way.  Alternatively, we could make the users who do need to use the preview features to specify corresponding options.

Thank you, @dmitris, for this PR, and sorry for the delay in reply.
We currently don't have a good way to support GitHub Enterprise customers with regards to removal of custom preview headers. It has always been the policy of this repo to attempt to support as many preview headers as possible and remove them when they are deprecated by the public GitHub API.
I'll leave this issue open to alerts GHE users about the problem (and so they can patch in the change), but until we have a good filtering mechanism of custom preview headers (which I don't foresee happening), we will have to let this issue (and corresponding PR) remain open until the preview header is officially removed by the GitHub Developer API team.


Remove demisto/content from ecosystem checks

Summary
Follow-up to https://github.com/astral-sh/ruff/pull/12129 to remove the demisto/content from ecosystem checks. The previous PR removed it from the deprecated script which I didn't notice until recently.
Test Plan
Ecosystem comment

Should we delete the deprecated Script?

Yeah, I think that can be done.


Warn when a app / pod ID is longer than 54 chars

Such service IDs might not play well with Mesos DNS due to SRV records length limitation.
https://mesosphere.github.io/marathon/docs/application-basics.html#service-name-length-limitations
https://jira.mesosphere.com/browse/DCOS_OSS-3722

LGTM. (I'm not one of the two reviewers, so I can't sign this off, but for such a small change I don't know that it's necessary)


refactor: ad-hoc modules

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

As we are introducing more and more ad-hoc modules (nuxt/screens, nuxt/components, nuxt/telemetry), it makes sense to make an internal array to keep them. This helps to:

Make debugging easier
Ensure all hooks are registred before their entrypoint
No overriding happens when developing these modules themself when nuxt adds them (this requires we expose meta field from modules

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #7452 into dev will increase coverage by 0.06%.
The diff coverage is 78.57%.

@@            Coverage Diff             @@
##              dev    #7452      +/-   ##
==========================================
+ Coverage   70.23%   70.29%   +0.06%
==========================================
  Files          88       88
  Lines        3699     3700       +1
  Branches     1009     1008       -1
==========================================
+ Hits         2598     2601       +3
+ Misses        893      892       -1
+ Partials      208      207       -1

Flag
Coverage Δ

#unittests
70.29% <78.57%> (+0.06%)
:arrow_up:

Impacted Files
Coverage Δ

packages/config/src/config/_app.js
100.00% <ø> (ø)

packages/config/src/config/_common.js
100.00% <ø> (ø)

packages/config/src/options.js
96.34% <62.50%> (+0.85%)
:arrow_up:

packages/core/src/module.js
94.38% <100.00%> (+0.26%)
:arrow_up:

Continue to review full report at Codecov.

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


How to ignore the selected ite,

I am new to this package. I have a requirement to show a static placeholder even though there are any selected items or not. I have been trying to get the solutions of it but failed. Is there a way to keep the place holder permanently with selected or not selected items in the drop down list

I want the list to display like above. Please guide me.


[WFCORE-1373]: Unable to specify custom configuration directory via -Djboss.server.config.dir

Making the resetEmbeddedServerProperties a little more selective to enable some configuration params on first usage of the embedded server.
Jira: https://issues.jboss.org/browse/WFCORE-1373

retest this please

@luck3y please approve. Thanks.

Looks good to me!


fix: use tsconfig.build.json to build outputs

Bug fix 🐛
Thanks for great library. 🙌
This might fix this issue
Check outputs below.

I'll make other pull request using builder bob if you prefer builder bob.

Thank you for your contribution.
Love u, Bro

Use Builder Bob as my previous libraries are also using it.
Thank you for your contribution.

Use Builder Bob as my previous libraries are also using it. Thank you for your contribution.

Okay I'll make other pull request using builder bob!
Thanks for quick reply!


VCF annotation and consensus visualization

…peline

@crohlicek let's separate out the IGV logic into a separate PR so we can merge this first -- could you also update the PR description with a bulleted list of functionality added in this PR?


feat: add DPI rule to reject SYN with RST|ACK

Part of https://github.com/ooni/probe/issues/1803

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

29 of 31 (93.55%)  changed or added relevant lines in 1 file are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.2%) to 82.799%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

dpiblock.go
29
31
93.55%

Files with Coverage Reduction
New Missed Lines
%

router.go
2
81.25%

ndt0.go
3
93.92%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
2195

Relevant Lines:
2651

💛  - Coveralls


Discard unknown fields in grpc-gateway?

Currently we have DiscardUnknown: false in our grpc-gateway config. This means that we get an invalid argument error when the JSON message includes unknown fields.
However, gRPC calls that include an unknown field succeed (the unknown field is discarded).
I think the behaviour should be consistent.

I think the reason it was enabled was because REST API users were getting confused by invalid requests (with typos) being accepted and discarded silently.
With gRPC, you can only have an unknown field if you use a newer version of the protobuf, right? It's more "controlled" in that way compared to JSON.

Yep, fair enough.
It is a pain in the JS SDK because the gRPC client works after introducing a new field, but the HTTP one doesn't. The problem is really that the generated toJSON method doesn't normalize the message, so by including the new field set to the zero value, it makes it into the JSON when it could (should?) be omitted.
Even if we changed this going forward, I'll still need a workaround in the SDK to keep compatibility with earlier versions, so I will have to figure it out 🙂


Handle the usage of quotes in commands

This makes it so that instead of strings being broken by the use of single quotes, common in words such as it's, let's, etc. This allows users to input plain English as a reason. Commonly encountered in my own usage with situations such as "We've talked about it, it's time to go". It's just a quick little fix of using triple quotes for strings instead.
Although it's really an edge case, considering most reason fields (for ban and kicks at least) can be filled with "spam" or "troll", it is nice to not encounter an unknown error in these scenarios, even though the action is completed successfully.

I'm not really sure where this is coming from, setting a reason via the bot while using single quotes works fine. Additionally, the changes you made have no effect on the actual bot. Using triple quotes for strings is purely cosmetic and has no change to the actual instantiated strings.


Catch NoMethodErrors in FEDEX find_and_parse_rate method

See https://github.com/Shopify/active_shipping/issues/307
The parse_rate_response method would crash and return a NoMethodError whenever the service type was missing in the XML response from FEDEX.
This seems to be related to the new version of the upstream API. As a workaround before we implement this new version, this PR proposes to catch all NoMethodErrors in the parse_rate_response, and return as much as possible while logging the faulty XML response.

@christianblais @mdking
I changed things a bit following your comments.
I will try to "catch" missing service_type fields and log the xml. The rates list will then be compacted and kept as successful, as not to raise an exception afterward.
The idea is to log the bad behaving XML in a warning, but still give as much information as possible, as a best effort.
Tell me if the idea and the flow seem legit.

@christianblais @mdking
I've added a log message and replace the if by a larger begin/rescue

Can you please provide a good PR description and meaningful commits please?

Code LGTM.
On our end when exception occurs for the NoMethodError it will be rescued and the response is logged. To log the warning our code will have to be modified to initialize the logger object when the carrier adapter is created.

One comment. But mostly a big improvement. Thank you!

Is it :rocket: ready?

@mdking @kmcphillips @christianblais
Sorry, still not used to the correct github ping policy :(

@christianblais I've changed the title of the text to better explain that the system code belong to the shipping rate, made the empty lines cleaner, and added explicit validation for the content of the XML.

:+1:

Thanks @heinzf.

Released in 1.6.4


tests/storage: Replace hardcoded patch operation with patchset

Use the PatchSet struct from the patch package to replace hardcoded jsonpatch operations to improve readability, in the tests/storage package.

What this PR does
Before this PR:
Hardcoded jsonpatches in the tests/storage package.
After this PR:
All hardcoded jsonpatches were updated to use patch.patchSet type, for readability and maintainability .

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/sig code-quality

/approve
@orenc1 Thank you!


spec: go not as smart about log.Panicf() as it is about panic()

Go is quite happy with the following program:
package main

import "fmt"
// import "log"

func foo(x int) int {
	if x == 0 {
		return 0
	}
	// log.Panicf("Not yet handling case %d", x)
	panic(fmt.Sprintf("Not yet handling case %d", x))
}

func main() {
	foo(0)
}

It understands that panic() is a "NoReturn" function, and so it eliminates foo()'s responsibility of returning an int in that case.  It compiles and runs.  However, if you swap the panic() with the log.Panicf() line (and of course swap the imports), go now complains:
.\panic.go:12: missing return at end of function

It seems that something needs to inform the compiler that log.Panicf() (and other similar functions) are also NoReturn.
$ go version
go version go1.4.1 windows/amd64

This is working as defined by the spec: http://golang.org/ref/spec#Terminating_statements

Where should I post issues about the spec?  It seems like having the concept of NoReturn would be a nice extension of the terminating statement idea.

Generally language change requests are first discussed at https://groups.google.com/forum/#!forum/golang-nuts


Reading some fields of FetchEvent.client causes a crash in Viceroy in js-compute >= 3.0

FetchEvent.client is of type ClientInfo, which contains information about the currently connected client.
One thing to note is, these crashes do not occur when deployed to Fastly Compute.
Reading some of these fields in Viceroy (including fiddle) causes crashes, starting with<EMAIL_ADDRESS>(the problem does not happen in js-compute@2.x): 'tlsJA3MD5', 'tlsCipherOpensslName', 'tlsProtocol', 'tlsClientCertificate', 'tlsClientHello'.
The error I get is something like this:
Error while running request handler: tls_cipher_openssl_name_get: A `None` error. This status code is used to indicate when an optional value did not exist, as opposed to an empty value.

NOTE: In Fiddle the error looks like this:
tls_cipher_openssl_name_get: Generic error value. This means that some unexpected error occurred during a hostcall.

This means that simply trying to perform a console.log(event.client) in local development will cause a crash.
However, these crashes do not occur when deployed to a Fastly service. The reason for this I'm speculating may be because these fields always have values on Fastly.
I noticed this because a library I had written back in js-compute@2 started crashing in a debug logging statement after switching to js-compute@3, but only on local dev.
I have a repro here: https://fiddle.fastly.dev/fiddle/adac0871

Thanks for this.
We should probably return undefined if these host-calls return a None error.
Should we return undefined for any other type of error that the host-calls return?
@guybedford what do you think?

Perhaps we can have a more general fallback for all None errors like No value returned for host call ...?
But then for these specifically, returning undefined makes sense. I don't know which XQD functions may possibly return None, it's a problem of the typing overall, but a fallback none error might at least help catch those cases further.

I've gone ahead with the null return implementation here in https://github.com/fastly/js-compute-runtime/pull/979.
This means not getting an error anymore, but does require more careful type checks going forward.


[Darwin] Enable OTA Provider server for controllers

Problem
Currently, to test OTA updates, the ota-provider-app and ota-requestor-app are used. In a more realistic scenario, a controller would likely be the OTA Provider. The OTA Provider server should be enabled for controllers
Proposed Solution
Enable OTA Provider server in src/controller/data_model/controller-clusters.zap

Controllers will need to do this as they choose, depending on their endpoint configuration.
For Darwin, this is now set up, with #15932 and https://github.com/project-chip/connectedhomeip/pull/15887

Updating this issue to track the changes for Darwin only

In that case, I think this is more or less fixed.  Remaining bits:

Make the Darwin server do mdns advertising.  Created https://github.com/project-chip/connectedhomeip/pull/15951 for that.
Ensure that other nodes can create CASE connections to the Darwin server.  Still sorting that out.
Implement an OTA provider delegate, etc.

The following PRs address the bare minimum needed to support OTA provider for Darwin controllers:

https://github.com/project-chip/connectedhomeip/pull/15885
https://github.com/project-chip/connectedhomeip/pull/15887
https://github.com/project-chip/connectedhomeip/pull/15932
https://github.com/project-chip/connectedhomeip/pull/16504
https://github.com/project-chip/connectedhomeip/pull/16546


empty vcat, empty csv

Two separate commits with bugfixes. Each with tests that fail prior to the commit.

replaced by #879 and #891


bug: pouch not pull containerd when containerd get killed unexpected

Ⅰ. Issue Description
pouch not pull containerd when containerd get killed
Ⅱ. Describe what happened
pouch pull containerd
Ⅲ. Describe what you expected to happen
pouch not pull containerd
Ⅳ. How to reproduce it (as minimally and precisely as possible)

start pouch , pouchd
kill containerd, kill containerd
check containerd is be pulled by pouchd , ps -ef | grep pouch

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

pouch version (use pouch version):
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

I am working on it.

Design of keep pull containerd when it get accident.
At first I think about using containerd event subscribe function to instead of task wait to wait task finish signal,  but the result did not show it will be a better way,  the only benefit take by event maybe is we do not care about task status when containerd is killed unexpected. Because in task wait way, when  containerd is killed unexpected, task status channel will get a channel broken message rpc error: code = Internal desc = transport is closing.
Since event design not take more better, we still use task wait way. In design, when containerd is killed unexpected, handleConnectContainerd will restart containerd and restore task, since task status channel has broken, so we make a new channel for task, and do re-wait for task exit.

By the way, I do not get what is use for function isContainerdDead and setContainerdDead , when containerd killed unexpected,  task wait channel receives broken message's is not sure, it can be before or later when containerd is dead completely，so there is no good timing to setContainerdDead. But to choose a zero timestamps to decided whether a exit message is useful.
about setContainerdDead,  WDYT @HusterWan .


Whisper parameter tweaks for hallucinations / ghosting

Hi
There are some discussions about those ghost transcriptions with whisper and there are some parameter tweaks around, which reduces those hallucinations by ~90%. The most important parameter is called „condition_on_previous_text“.  But that parameter is nowhere to see in whisper.net.
Can you include that parameter anytime soon? I think it is highly important
You can follow the discussion about that topic here:
https://github.com/openai/whisper/discussions/679
What do you mean?

Unfortunately, that parameter is not added in https://github.com/ggerganov/whisper.cpp/tree/master and this library is a wrapper for whisper.cpp.
If that option would be added there, it will be added in this library as well automatically in order to update to latest version, but for now, there is not much we can do here.

Thanks for your answer. So i will ask the question @ whisper.cpp as well, as it is very important parameter setting. it reduces those hallucinations heavily and we cant see any relevant negativ side effects.

If you don't have this parameter, have you solved your hallucination problem so far? I often encounter hallucination problems and haven't found a solution yet
@Karrde1984


where is the convo5_block3_1_conv  file

i am interested to your code and run your code but i m not  found the convo5_block3  file please give me this file ,
from tensorflow.keras.models import load_model
loading the fine-tuning model
model=load_model('..................../conv5_block3_1_conv.hdf5')

this code is for training the based model based on fine-tuning strategy, which means gradually train more layers by tuning the learning parameters until a significant performance boost is achieved
Here, I select Resnet50 as a pre-trained model and define some top layers to train
#define the fine-tuning layers fine_tuning_layers=[176,171,168,165]
At the checkpoint, I save the best model 'hdfs' with the significant weights for later use to evaluate the model in a new task.
in the for loop,
for i in fine_tuning_layers:
the model using the first fine_tuning_layers= 176 which is a dense layer and saving the model with the name of its layer, after completing 100 eps, the training is transferred to the next number in the list (171) and so on.
you ask where is conv5_block3_1_conv.hdf5 ?
You have to train the model up to layer [165] to save the model with its name

Thx for the shareing information
On Tue, 11 Jan, 2022, 6:40 PM Asmaa Abbas, @.***> wrote:

this code is for training the based model based on fine-tuning strategy,
which means gradually train more layers by tuning the learning parameters
until a significant performance boost is achieved
Here, I select Resnet50 as a pre-trained model and define some top layers
to train
#define the fine-tuning layers fine_tuning_layers=[176,171,168,165]
At the checkpoint, I save the best model 'hdfs' with the significant
weights for later use to evaluate the model in a new task.
in the for loop,
for i in fine_tuning_layers:
the model using the first fine_tuning_layers= 176 which is a dense layer
and saving the model with the name of its layer, after completing 100 eps,
the training is transferred to the next number in the list (171) and so on.
you ask where is conv5_block3_1_conv.hdf5 ?
You have to train the model up to layer [165] to save the model with its
name
—
Reply to this email directly, view it on GitHub
https://github.com/asmaa4may/DeTraC_COVId19/issues/8#issuecomment-1009950012,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMTV6ANGDPPTVI6TH5NEDDUVQT5TANCNFSM5LVKX73Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix crash in - [ARTiledImageView drawRect:], line 74

Version: 2.3.2 (2015.12.01) | net.artsy.artsy
Stacktrace
ARTiledImageView;drawRect:;ARTiledImageView.m;74
ARTiledImageViewWithBreadcrumb;drawRect:;ARZoomView.m;33
Reason
objc_msgSend() selector name: layer
Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/37029/crash_reasons/71870734

Closing in favour of #773.


How can Tact make use of DIVMOD and MINMAX without tuple support?

For example, in stdlib.fc, we have
;;; Sorts two integers.
(int, int) minmax(int x, int y) asm "MINMAX";

How can this be used in Tact?

In Tact, you'll need to declare a native function like this:
// the @name() here
@name(minmax)
native minmax(a: Int, b: Int): Pair;

Where Pair is the struct representing the tuple return type (int, int) of FunC in Tact:
// you may call it or its fields differently:
struct Pair {
    a: Int;
    b: Int;
}

Now, to give a complete example which you can test right away:
import "@stdlib/deploy";

struct Pair {
    a: Int;
    b: Int;
}

@name(minmax)
native minmax(a: Int, b: Int): Pair;

contract BlankContract with Deployable {
    init(){}
    get fun test(): Pair {
        return minmax(2, 1); // will return a Pair, where a = 1, b = 2
    }
}

excellent


PrimitiveParser: Decide on a policy and API surface area for parsing hexadecimal numbers from text

When parsing hexadecimal characters from text, should there be specific overloads for strings containing uppercase ABCDEF and lowercase abcdef? Should there be one overload that is case-insensitive?

@KrzysztofCwalina FYI - this issue has been created and I have assigned myself. @yizhang82 has recommended that the overloads be case-insensitive, since the alternative seems to be bloated in terms of API surface area. What do you think?

The advantage of having separate overloads would be better performance, right? So, what is the performance difference?

We don't know yet. We will be writing performance benchmarks to better understand and compare our options.

The parsers has been productized and moved to corefx. I think hex parsing is now case insensitive:
https://github.com/dotnet/corefx/blob/master/src/System.Memory/src/System/Buffers/Text/Utf8Parser/ParserHelpers.cs#L29


Set sources folders correctly on open dub project

See issue #56 for more context

Fixed by implementing import dub project


lineHeight doesn't work.

in react-native the line-height needs to be an absolute value right?

Here the line-height needs to be 1.25 * fontSize

Hi @apostopher
Have you tested the outputted values in react-native?
If there is something wrong happening I would love a PR for that.
I know I struggled with the line height values so there is a possibility I did something wrong.
greetings
Thomas

Hello @TVke
Thanks for getting back.  First of all, thanks for this awesome lib! I'm using it in my projects and it works great!
I'm using react-native 0.61. The workaround I have in my code is a custom Text component. something like:
<Text as="h1" leading="tight">Heading 1</Text>
inside the text component, I'm calculating the lineHeight based on the fontSize.
{lineHeight: fontSize * lineHeight}
react-native needs an absolute point value. on the web, we can specify line-height as a multiplier. but not in react-native :-(

Hi @apostopher
I have not needed to change lineHeight all that much, so I have only limited experience with it.
In react-native-tailwincss I just pass the lineHeight values to the lineHeight prop so you can change your config file and that should work (if it does not work, let me know which values you have set).
If you think the defaults settings need changing, I am all ears.
greetings
Thomas

I noticed the same problem.  For some reason it is outputting "2px" instead of "2em" for leadingLoose - I realize "em" aren't supported by tailwind so maybe that's why.

I think we found the problem in the last comment so closing this.
Feel free to reopen or create a new one if there is still a problem related to react-native-tailwindcss


Allow cd mode for drives that don't read into the lead-in of audio discs

Hi sarami, right now, DIC aborts reading the disc if the drive reports an error reading the lead-in, like this:
Set read command: 0xbe, subcode reading mode: Raw
LBA[-00001, 0xffffffff], [F:ReadCDPartial][L:2235] OperationCode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 04, ff, ff, ff, ff, 00, 00, 01, f8, 01, 00
dwBufSize: 2448

The only way to read such a disc is to use audio mode starting from LBA 1 instead of 0. But with audio mode we lose the cuesheet, track splitting and c2 correction that cd mode offers.
Is there any way to add an option to skip lead-in reading in DIC?

Please use the supported drive of lead-in.


error on maximum players reached

missing param ws in game.join:
def join(self, player):
    ...
    if self.count_alive_players() == settings.MAX_PLAYERS:
        self.send_personal(->ws<-, "error", "Maximum players reached")
        return

thanks for noting, that should be "player.ws"


Qt deprecation warning

In regard to the following warning:
WARNING: The next major version of capybara-webkit will require at least version 5.0 of Qt. You're using version 4.8.6.
I have posted a question, http://stackoverflow.com/questions/33121490/upgrading-qt-on-mac-osx-10-10-5 about the best way to upgrade to Qt 5.  However, no one has answered the question in three weeks, indeed it has been downvoted. You have extensive information on installing Qt, but none that I can find on upgrading. Is it possible to answer my stackoverflow question, or add some information on your page dealing with installing capybara-webkit and Qt?

Do you know how Qt was installed? It doesn't come with OS X, so you must have installed it some point, possibly as a dependency of something else. The way you'd upgrade it depends on how you installed it.
Using which qmake will hopefully tell you where it's installed, which can sometimes be revealing.
The two most common ways to install it are through the official packages and through Homebrew. If you used the official installer, I think you can just run the latest official installer. If you used Homebrew, you can use brew upgrade.

It turned out it was installed with Homebrew.  After an El Capitan problem causing an issue with brew update, brew upgrade qt worked fine.
Thank you


notparallel variable is broken

See original issue on GitLab
In GitLab by [Gitlab user @willsalmon] on Jul 10, 2020, 10:39
Summary
The notparallel variable dose not seem to force MAKEFLAGS: -j1 in the environment
This means that projects that have bugs associated with make -j2 can not be built, eg slang.
Please see the failure: https://gitlab.com/celduin/bsps/bst-boardsupport/-/jobs/625698066
The variable being incorrectly set on line 21 in the log: https://gitlab.com/celduin/bsps/bst-boardsupport/-/jobs/625698066/artifacts/file/artifact/freedesktop-sdk/components-slang/1ad3d1df-build.3146.log
The element https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/blob/master/elements/components/slang.bst showing the:
variables:
  builddir: ''
  notparallel: true

The problem is further compounded by the fact that bst will not let you set MAKEFLAGS in the environment section as it is protected

In GitLab by [Gitlab user @willsalmon] on Jul 10, 2020, 10:39
changed the description

In GitLab by [Gitlab user @willsalmon] on Jul 10, 2020, 10:40
mentioned in merge request celduin/bsps/bst-boardsupport!17

In GitLab by [Gitlab user @cs-shadow] on Jul 17, 2020, 13:58
First, I am not able to reproduce this. In my experiments, BuildStream Core sets the max-jobs variable to 1 when notparallel: true is specified. And, the autotools plugins sets MAKEFLAGS: -j%{max-jobs}. If you can try again, and provide a minimal repro case, I might be able to dig into it more.

The problem is further compounded by the fact that bst will not let you set MAKEFLAGS in the environment section as it is protected

Also, I'm not sure if I follow this. You should be able to set MAKEFLAGS to whatever you want. Where did you get the idea that it was protected in some way?

In GitLab by [Gitlab user @tristanvb] on Nov 6, 2020, 09:24
Closing this with needinfo, please reopen if this is still an issue.

I can reproduce this issue, can someone reopen this or should I file a new one?

I can reproduce this issue, can someone reopen this or should I file a new one?

This feels unlikely, with which plugin are you able to reproduce? It is the plugin YAML which is responsible for setting MAKEFLAGS according to %{max-jobs} (but that is already mentioned here).
Is %{max-jobs} not being setup properly in the core ?
Or, is it possible you are confusing the role or notparallel with the role of the —builders cli option ?

I'm still not sure exactly what happens as I'm yet to reproduce it locally but here is the element: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/blob/abderrahim/bst2/elements/components/slang.bst
And here is a failing build https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/1849722318/artifacts/file/cache/buildstream/logs/freedesktop-sdk/components-slang/9cfbabfb-build.169.log (notice MAKEFLAGS is set to -j8)

It seems to be that max-jobs is not being setup correctly in core. As I'm trying to reproduce the issue, I notice that some elements which don't have notparallel set are being built with -j1. I'm not sure what's happening exactly.

So the above theory is correct: expanding the variables in https://github.com/apache/buildstream/blob/master/src/buildstream/element.py#L2834 changes the value of the class variable __defaults.
The line responsible for this is default_env._composite(environment) as defined in Element.__extract_environment(). The following change fixes the issue, though I'm not sure if it's the right approach or if the _composite() method should be modified instead.
diff --git a/src/buildstream/element.py b/src/buildstream/element.py
index ee3b2fc75..b1c8d16a0 100644
--- a/src/buildstream/element.py
+++ b/src/buildstream/element.py
@@ -2947,7 +2947,7 @@ class Element(Plugin):
         else:
             environment = project.base_environment.clone()

-        default_env._composite(environment)
+        default_env.clone()._composite(environment)
         element_env._composite(environment)
         environment._assert_fully_composited()

Build in fdsdk using bst2 fail because of this atm: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/1979958539
@gtristan

For now I'm adding this basic test which shows notparallel working properly: https://github.com/apache/buildstream/pull/1570
It would be good to expand on this to reproduce this quirky behavior we are seeing in fdsdk.

Maybe the lines of code in master have shifted since this comment, my 2834 says:
    self.__environment = unexpanded_env.strip_node_info()

So the above theory is correct: expanding the variables in https://github.com/apache/buildstream/blob/master/src/buildstream/element.py#L2834 changes the value of the class variable __defaults.

I'll try to summarize what should be happening here in __initialize_from_yaml() (which is outlined here in the docs:

self.__init_defaults() will initialize the class variable __defaults, this is a composition of project level overrides on top of plugin provided defaults

Questionably this composition should also be composited on top of project.base_variables, I think the reason why we cannot immediately cache builtin -> project.conf -> plugin -> project.conf overrides is because of the dual-pass loading of project.conf where the first pass is not a complete load.

self.__extract_variables() will compose the variables

The previously cached default_vars is loaded from the class variable __defaults
The default_vars (which is only plugin + overrides) is composited on top of the project.conf vars
The element_vars is composited on the very top of this composition and has the last word

Now that we have a fully sane composition of the variables MappingNode for this particular element instance, the Variables() object instance is created for this element instance

This is where the notparallel magic happens, forcing the max-jobs variable to 1, this seems like the right time to do this to me.

self.__extract_environment() will now compose the environment following similar rules

The previously cached default_env is loaded from the class variable __defaults
The default_env (which is only plugin + overrides) is composited on top of the project.conf environment
The element_env is composited on the very top of this composition and has the last word

Now the previously created Variables() instance is used to expand variables in the fully composited unexpanded_env, at this point the Variables() instance should have max-jobs set to 1 already and we should have the correct MAKEFLAGS

The line responsible for this is default_env._composite(environment) as defined in Element.__extract_environment(). The following change fixes the issue, though I'm not sure if it's the right approach or if the _composite() method should be modified instead.

If your patch does indeed change something, then I think you've indeed found a bug in MappingNode.composite(), this function should modify the target node only and should not cause residual side effects in the source node.

Yup, lines have shifted. The line in question is
self.__variables.expand(unexpanded_env)

So what happens is that Node._composite() does a shallow copy of the nodes, then Variables.expand() modifies them in-place, resulting in a modified __defaults class variable. which is then composited into other elements with the wrong value.
Here is a minimal reproducer for the issue:
from buildstream.node import Node
from buildstream._variables import Variables

default = Node.from_dict({'MAKEFLAGS': '-j%{max-jobs}'})
element = Node.from_dict({'name': 'my-element.bst'})

print(default, element, sep='\n')
# [synthetic node]: {'MAKEFLAGS': '-j%{max-jobs}'}
# [synthetic node]: {'name': 'my-element.bst'}

default._composite(element)

print(default, element, sep='\n')
# [synthetic node]: {'MAKEFLAGS': '-j%{max-jobs}'}
# [synthetic node]: {'name': 'my-element.bst', 'MAKEFLAGS': '-j%{max-jobs}'}

v = Variables(Node.from_dict({'max-jobs': '1'}))
v.expand(element)

print(default, element, sep='\n')
# [synthetic node]: {'MAKEFLAGS': '-j1'}
# [synthetic node]: {'name': 'my-element.bst', 'MAKEFLAGS': '-j1'}

I just stumbled upon this old MR: https://gitlab.com/BuildStream/buildstream/-/merge_requests/1929
It seems to suggest we're indeed supposed to use Node.clone() with composition.
CC: @BenjaminSchubert

I think that's indeed the right thing to do here as far as I can tell

I think that's indeed the right thing to do here as far as I can tell

I think this is clearly wrong.
Any code that I can think of which composites one mapping on top of another mapping, expects the source mapping to remain unmodified by the operation, only the target mapping should be affected by composition.

Are we still going to merge the bug fix? This is from freedesktop-sdk point of view beta blocker.

Are we still going to merge the bug fix? This is from freedesktop-sdk point of view beta blocker.

I don’t want to merge the workaround for what I think is clear cut broken behavior of MappingNode._composite(), this is probably an indicator of further brokenness we haven’t discovered yet. Probably this went unnoticed until now because we don’t do very much compositing of nested dictionaries and lists.
I’ve asked @BenjaminSchubert to come back and comment on this.

[...]

Here is a minimal reproducer for the issue:
from buildstream.node import Node
from buildstream._variables import Variables

default = Node.from_dict({'MAKEFLAGS': '-j%{max-jobs}'})
element = Node.from_dict({'name': 'my-element.bst'})
v = Variables(Node.from_dict({'max-jobs': '1'}))

print(default, element, sep='\n')
# [synthetic node]: {'MAKEFLAGS': '-j%{max-jobs}'}
# [synthetic node]: {'name': 'my-element.bst'}

default._composite(element)

print(default, element, sep='\n')
# [synthetic node]: {'MAKEFLAGS': '-j%{max-jobs}'}
# [synthetic node]: {'name': 'my-element.bst', 'MAKEFLAGS': '-j%{max-jobs}'}

v.expand(element)

print(default, element, sep='\n')
# [synthetic node]: {'MAKEFLAGS': '-j1'}
# [synthetic node]: {'name': 'my-element.bst', 'MAKEFLAGS': '-j1'}

So I'm trying to put together a minimal reproducer with a proper end-to-end test in tests/format/variables.py but still having trouble reproducing this.
I've got 2 manual elements where one depends on the other, and I'm unable to get one of them to pollute the other, by setting notparallel in one element and observing max-jobs in bst show --format '%{vars}' output.
Setting either element to notparallel does not pollute the second element, even adding a third element where the base element and toplevel element are both notparallel but the middle element does not specify notparallel still yields the expected result.
Were you able to reproduce this in a simplified end to end test ?

Nope, my failed attempt is here: https://github.com/abderrahim/incorrect-max-jobs
I'll try to find out what the problem is.

Maybe composite itself could be unittested to get it to break?

Here you go: https://github.com/abderrahim/incorrect-max-jobs
bst show --format %{env} parallel.bst and bst show --format %{env} notparallel.bst will show the correct MAXJOBS variable. but bst show --format %{env} parallel.bst notparallel.bst will show the same value for both elements.

Maybe composite itself could be unittested to get it to break?

Possible but I'm really more interested in reproducing the issue with an end-to-end test, I'd rather keep internal unit testing down to a minimum if and when it is at all possible to reproduce a bug in action.

Here you go: https://github.com/abderrahim/incorrect-max-jobs
bst show --format %{env} parallel.bst and bst show --format %{env} notparallel.bst will show the correct MAXJOBS variable. but bst show --format %{env} parallel.bst notparallel.bst will show the same value for both elements.

I've provided an isolated test case for this in the https://github.com/apache/buildstream/tree/tristan/test-notparallel branch now.
To observe the broken behavior, you can type tox -- tests/format/variables.py::test_notparallel_twice

Now #1570 has been updated to contain both:

The updated test case which triggers the issue
The fix for MappingNode._composite() which ensures that we overwrite target nodes with clones of source nodes, so that the composite source is not left vulnerable to mutations when code goes on to mutate the composited target node.


What happens if an user sends a HUGE ammount of data?

This should be tested.

Related to #102. I'm not fixing this.


[Noetic] Loading robot model does not work

should be fixed by updating the code to use Python3 in f3a10cb

should be fixed by updating the code to use Python3 in f3a10cb

confirmed fixed

confirmed fixed


Time in message details displayed wrong

-> Meldung erstellen -> Uhrzeit 22:22
After saving the message, the message details are displayed and on that page the Uhrzeit is now 10:22

fixed, but not yet merged


Component test script ci

Summary: Refactor build_ut script for use in component tests. Create action to run client component tests on PR.
Type: Feature
Test Plan: Unittests, Component Tests.
Jira: RIALTO-410

https://jenkins.code.rdkcentral.com/job/github-triggered/44143/ started

https://jenkins.code.rdkcentral.com/job/build-component/82754/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9884/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15105/ started.

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31558/

https://jenkins.code.rdkcentral.com/job/github-triggered/44145/ started

https://jenkins.code.rdkcentral.com/job/build-component/82757/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9885/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15108/ started.

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31565/

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31566/

https://jenkins.code.rdkcentral.com/job/github-triggered/44151/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9891/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15110/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9894/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/44154/ started

https://jenkins.code.rdkcentral.com/job/build-component/82760/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15111/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/44156/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9896/ started

https://jenkins.code.rdkcentral.com/job/build-component/82761/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15112/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/44158/ started

https://jenkins.code.rdkcentral.com/job/build-component/82763/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9898/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15115/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9901/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/44164/ started

https://jenkins.code.rdkcentral.com/job/build-component/82766/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15116/ started.

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31567/

https://jenkins.code.rdkcentral.com/job/github-triggered/44166/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9902/ started

https://jenkins.code.rdkcentral.com/job/build-component/82767/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15117/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9904/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/44168/ started

https://jenkins.code.rdkcentral.com/job/build-component/82768/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15118/ started.

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31574/

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31575/

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31576/

https://jenkins.code.rdkcentral.com/job/github-triggered/44172/ started

https://jenkins.code.rdkcentral.com/job/build-component/82771/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9907/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15120/ started.

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31588/

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31589/

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31590/

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31591/

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31592/

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31593/

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31594/

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31596/

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31597/

https://jenkins.code.rdkcentral.com/job/github-triggered/44182/ started

https://jenkins.code.rdkcentral.com/job/build-component/82777/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/9915/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/15128/ started.

Sanity tests for ['RPI4 Hybrid'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31603/

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/31608/

'['BCM Reference Refapp2']' Sanity test FAILURE, investigation pending.
Build Job/Num: build-brcm-refboard2/2779
Flash BCMREF [SUCCESS]
BCMREF - Video Test [FAILURE]
RefApp Channel Change Video Tests [FAILURE]
RefApp Lightning Bouncing Ball App Launch and Exit Test [FAILURE]
Video local (H264) using gst-play-1.0 [SUCCESS]
HLS Video Streaming using aamp-cli [SUCCESS]
DASH Video Streaming using aamp-cli [SUCCESS]
PLAYREADY_DRM Video Streaming using aamp-cli [SUCCESS]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-bcmref-refapp2-flow/6954/

'['BCM Reference Refapp2']' Sanity test FAILURE, investigation pending.
Build Job/Num: build-brcm-refboard2/2781
Flash BCMREF [SUCCESS]
BCMREF - Video Test [FAILURE]
RefApp Channel Change Video Tests [FAILURE]
RefApp Lightning Bouncing Ball App Launch and Exit Test [FAILURE]
Video local (H264) using gst-play-1.0 [SUCCESS]
HLS Video Streaming using aamp-cli [SUCCESS]
DASH Video Streaming using aamp-cli [SUCCESS]
PLAYREADY_DRM Video Streaming using aamp-cli [SUCCESS]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-bcmref-refapp2-flow/6957/

'['BCM Reference Refapp2']' Sanity test FAILURE, investigation pending.
Build Job/Num: build-brcm-refboard2/2782
Flash BCMREF [SUCCESS]
BCMREF - Video Test [FAILURE]
RefApp Channel Change Video Tests [FAILURE]
RefApp Lightning Bouncing Ball App Launch and Exit Test [FAILURE]
Video local (H264) using gst-play-1.0 [SUCCESS]
HLS Video Streaming using aamp-cli [SUCCESS]
DASH Video Streaming using aamp-cli [SUCCESS]
PLAYREADY_DRM Video Streaming using aamp-cli [SUCCESS]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-bcmref-refapp2-flow/6958/

'['BCM Reference Refapp2']' Sanity test FAILURE, investigation pending.
Build Job/Num: build-brcm-refboard2/2783
Flash BCMREF [SUCCESS]
BCMREF - Video Test [FAILURE]
RefApp Channel Change Video Tests [FAILURE]
RefApp Lightning Bouncing Ball App Launch and Exit Test [FAILURE]
Video local (H264) using gst-play-1.0 [SUCCESS]
HLS Video Streaming using aamp-cli [SUCCESS]
DASH Video Streaming using aamp-cli [SUCCESS]
PLAYREADY_DRM Video Streaming using aamp-cli [SUCCESS]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-bcmref-refapp2-flow/6959/

'['BCM Reference Refapp2']' Sanity test FAILURE, investigation pending.
Build Job/Num: build-brcm-refboard2/2786
Flash BCMREF [SUCCESS]
BCMREF - Video Test [FAILURE]
RefApp Channel Change Video Tests [FAILURE]
RefApp Lightning Bouncing Ball App Launch and Exit Test [FAILURE]
Video local (H264) using gst-play-1.0 [SUCCESS]
HLS Video Streaming using aamp-cli [SUCCESS]
DASH Video Streaming using aamp-cli [SUCCESS]
PLAYREADY_DRM Video Streaming using aamp-cli [SUCCESS]
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-bcmref-refapp2-flow/6965/


Linear Algebra routines

Resolves https://github.com/Quansight-Labs/unumpy/issues/47

Superceded by #56


Using dictionary pairs for requirement history

Record the version of the specification in which a requirement was introduced. The validation developers have requested the field. Implementation could be fairly simple, again the examples have had the current XPath and Cardinality information removed see #707 :
<requirement ID="CSIP112" REQLEVEL="MUST" EXAMPLES="structMapExample2">
    <description>
        Type of locator

The locator type is always used with the value "URL" from the vocabulary in the attribute.

since

v2.1.0

    </description>
</requirement>

The issue is going to be discussed by the DILCIS Board

I have nothing to opose to this suggestion. Its just better documentation.

The DILCIS Board have agreed to approve this suggestion on its meeting 2023-12-06.

This can go ahead then. This will need a proper pass over the specifications but @stephenmackey and I should be able to get it done for some time in Feb 2024.

@johnmackey actually, way beyond me. 😊
Stephen Mackey
Senior Consultant
Penwern Limited
+33 668 397 453
@.***
From: Carl Wilson @.>
Sent: Tuesday, January 9, 2024 12:08 AM
To: DILCISBoard/E-ARK-CSIP @.>
Cc: Stephen Mackey @.>; Mention @.>
Subject: Re: [DILCISBoard/E-ARK-CSIP] Using dictionary pairs for requirement history (Issue #710)
This can go ahead then. This will need a proper pass over the specifications but @stephenmackeyhttps://github.com/stephenmackey and I should be able to get it done for some time in Feb 2024.
—
Reply to this email directly, view it on GitHubhttps://github.com/DILCISBoard/E-ARK-CSIP/issues/710#issuecomment-1881962583, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIKSFYJ6FTPQONTBLJVM3DDYNR357AVCNFSM6AAAAAA4PSKGDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRHE3DENJYGM.
You are receiving this because you were mentioned.Message ID: @.***>

The decision made by the DILCIS Board gives the addition in the description of a requirement to include the version the requirement was added with this code:

since

v2.1.0

7 DILCIS Board members have acknowledge the issue
7 DILCIS Board members agree with the solution
The suggestion of updated encoding of requirement addition will be part of the next release of the specifications

The next version of the SIP does not include new features, only fixes to the documentation. I believe this is not applicable at this stage so I'm closing the issue.


Per service wake up setting

Service hibernation can be enabled / disabled per service, but auto wake up can only be set globally. Some services need it (e.g. mail, messengers), while others do not (e.g. services for notes, documents, passwords, etc.). Would be nice to have an option to enable / disable auto wake up per service.

I like the idea, and I had thought of this when I implemented the "wake up service" behavior. But, I don't have time to work on this atm. Will wait for any contributor for the same.
That being said, the darkMode setting is the pattern that can be followed (there's a global setting, that can be overridden by the service-specific setting). Please also check the android-messages recipe for related changes in the recipe.


Missing upgrade note for 1.23.0 Ambient mode

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
Upgrading Istio Ambient mode from 1.22.2 to 1.23.0 and it seems there is a missing upgrade note in https://istio.io/latest/news/releases/1.23.x/announcing-1.23/upgrade-notes/
My Istio configuration details (I would paste my IstioOperator manifest but it's on another network):

Profile: ambient
Istiod is deployed to istio-system
CNI and ztunnel pods are deployed to kube-system. We do not allow privileged pods in any other namespace.

My issue was nearly identical to https://github.com/istio/istio/issues/52057 except I encountered the error only after upgrading Istio and changing nothing else in my configuration. Thanks to @yardenshoham commenting on that issue, I figured out the fix. I had to configure the env var CA_TRUSTED_NODE_ACCOUNTS: "kube-system/ztunnel" for the pilot component in my config then everything worked smoothly.
The default value for this env var on the istiod container was istio-system/ztunnel on my Istio 1.23.0 deployment. I checked my most recent v1.22.2 deployment and that env var was set to istio-system/ztunnel,kube-system/ztunnel automatically. So either the documentation should have mentioned that this value would need to be configured appropriately when upgrading to 1.23.0, if this change was intended, or there is a regression where that env var isn't being configured correctly anymore when deploying ztunnel to a different namespace.
Version
Istio v1.23.0
Kubernetes 1.30.2

Additional Information
No response

cc @bleggett

For helm we may need to have users explicitly do it, but for istioctl we can automatically set trustedZtunnelNamespace based on components.ztunnel.namespace. Should be a 1 line change.

Yeah this is another one that I definitely created a release note for but which didn't make it into the published notes, for reasons that I'm not clear on.
https://github.com/istio/istio/pull/51311

Oh it is in the change notes: https://istio.io/latest/news/releases/1.23.x/announcing-1.23/change-notes/#installation

The reason we did not simply sustain the previous default was that the previous default granted access to two namespaces, only one of which would ever be used, which was arguably a security hole.

Oh it is in the change notes: https://istio.io/latest/news/releases/1.23.x/announcing-1.23/change-notes/#installation

I don't use the Helm chart however and nothing in that line tells me that previous default behavior changed. Based on the upgrade notes, I expected to be able to install Istio 1.23.0 using my current IstioOperator manifest and the istioctl command.

The reason we did not simply sustain the previous default (istio-system/ztunnel,kube-system/ztunnel) was that the previous default granted access to two namespaces, only one of which would ever be used, which was arguably a security hole.

I definitely agree with that sentiment. In my new configuration I only configured it for kube-system.

Installing ztunnel to a different namespace than istiod requires explicit configuration, in all cases.

Are all of the various places it needs to be configured documented somewhere? I haven't come across a complete list of the places updates are needed, I kind of just figured it out when I initially deployed Ambient mode on 1.22.x.

Agreed, fair. It could have been more explicit that because the default behavior was a problem, the default behavior has changed. Since ambient is still in beta, maintaining strict back compat is not a requirement, but the relnote (that I wrote) could have been worded more explicitly.

Ah to be honest, Ambient mode has worked so well I kind of forgot it is technically a beta feature :sweat_smile:

Or in operator-resource-speak:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  components:
    pilot:
      trustedZtunnelNamespace: <MY_ZTUNNEL_NS>

Thank you! That is simpler than specifying via the environment variable.

Ah to be honest, Ambient mode has worked so well I kind of forgot it is technically a beta feature 😅

Please ping me on Slack so we can publish a case study based on that sentiment :)

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  components:
    pilot:
      trustedZtunnelNamespace: <MY_ZTUNNEL_NS>

Using that config results in Error: generate config: error unmarshaling JSON: while decoding JSON: unknown field "trustedZtunnelNamespace" in isitio.operator.v1alpha1.ComponentSpec
It doesn't look to be a valid part of https://istio.io/latest/docs/reference/config/istio.operator.v1alpha1/#ComponentSpec either. I tried nesting it under spec.components.pilot.spec, Istio deploys but istiod has the incorrect CA_TRUSTED_NODE_ACCOUNTS again.
This is the config that is currently working for me but I don't know if it is a recommended way of configuring it. I grepped through the manifests included in the Istio v1.23.0 release and it looks like this env var is the only place .Values.pilot.trustedZtunnelNamespace is used.
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  components:
    pilot:
      k8s:
        env:
        - name: CA_TRUSTED_NODE_ACCOUNTS
           value: "kube-system/ztunnel"

https://github.com/istio/istio/pull/51311/files#diff-74a4ba6cc7c1c0c2070204a32d2f14931b8f379cd72424d5fa4639f625c3587eR982
It should be in values_types already.

oh @Phenix66 my bad - it should be
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  values:
    pilot:
      trustedZtunnelNamespace: default

(why do we have 6 ways to do one thing? IDK - I do apologize tho)

oh @Phenix66 my bad - it should be
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  values:
    pilot:
      trustedZtunnelNamespace: <MY_ZT_NAMESPACE>

Because the IstioOperator indirects the Helm values, but (apparently) in several different ways. (component.pilot = no, values.pilot = yes)
(why do we have 6 ways to do one thing? IDK - I do apologize tho)

That worked perfectly, thank you!

Closing since we found this is documented in https://istio.io/latest/news/releases/1.23.x/announcing-1.23/change-notes/#installation and issue resolved above. Thanks everyone.


Application not working when I add SVG img.

When I trying add SVG img it take me to binding.dart as you see in the picture .

hey, can you share the code, where you are trying to implement the SVG file

can you share the assets folder tree? and what platform do you use

You can use flutter_svg to add SVGs to your app. Flutter does not support SVGs outside of Web. This is working as intended and therefore, I will close this issue. Thank you


Profile Shortcut returns 'Page not found' if Enhanced Profiles UI is turned on

Describe the bug
If Enhanced Profiles is turned on in User Management Settings, and you click on the Profiles shortcut, it takes you to a page that says "Page not found".
To Reproduce
Steps to reproduce the behavior:

In User Management Settings in Salesforce, turn on Enhanced Profile List Views and Enhanced Profile User Interface.
In the extension, click on Shortcuts.
Search for "profiles" and click on the result.
See page not found error.

Expected behavior
If Enhanced Profiles is turned on, the page should direct you to https://orgname.lightning.force.com/lightning/setup/EnhancedProfiles/home
Desktop (please complete the following information):

OS: macOS Ventura
Browser: Chrome 114.0.5735.198
Version 1.18

Hi @chelseastrong,
You're completely right !
I found out this issue one or two weeks ago and added a new shortcut for Enhanced Profile.
This issue will be fixed in the next version which should be released in one or two weeks! 🚀

If you want to try it, you can install locally the releaseCandidate branch which is the future version 1.19 containing this fix

@chelseastrong If you were searching for a particular profile, this new feature (also delivered in 1.19) should help you:
You'll be able to search for profiles (by name) in the shortcut tab


Add support header comma-separated values

https://tools.ietf.org/html/rfc3261#section-7.3.1
The following groups of header field rows are valid and equivalent:

      Route<EMAIL_ADDRESS>      Subject: Lunch
      Route<EMAIL_ADDRESS>      Route<EMAIL_ADDRESS>
      Route<EMAIL_ADDRESS><EMAIL_ADDRESS>      Route<EMAIL_ADDRESS>      Subject: Lunch

      Subject: Lunch
      Route<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Should be implemented in #5


[Bug]: lastDays not include today's data

What happened?
I'd like to use this library for my filament projects however when using last7Days() or last30Days() both are calling the function lastDays(int $days) which is using now()->startOfDay() to query the days.
However using startOfDay() results in today's data not being included in the data (when using timestamps).
Is this intended or can it be changed to endOfDay() to include today's data?
How to reproduce the bug
SimpleStat::make(User::class)->last30Days()->dailyCount()

Package Version
0.1.3
PHP Version
8.3.0
Laravel Version
11.0
Which operating systems does with happen with?
No response
Notes
No response

I assumed this was a bug, if that's the case I already created a PR at #6

We'll handle this further at #6


cmd/link: ld: warning: -no_pie is deprecated in new macOS version

refer to this comment but tigger another error -buildmode=pie not supported when -race is enabled  when running go test -race -buildmode=pie, is there any suggestion to solve this problem?

See #20038 and #53539

See #20038 and #53539

I see, it seems this combination is not available, can I change the value of buildmode to avoid this warning ld: warning: -no_pie is deprecated in new macOS version  and pass -race as well?

I think this is a duplicate of #55112.


Empty folders created during rt download

I am using the below code to download the files (Including sub-directories) from Artifactory Source, and I have some EMPTY folders in my Source Repository
jfrog.exe rt dl --threads=10 --include-dirs=true --flat=true --recursive "Artifactory-Source-Repo/Test_Project/(*)" "Test_Project/{1}"
The files are downloaded successfully, but after download, I see EMPTY folders are created in each and every directory with the above command.
I tried the same without "--include-dirs" in the above command and the EMPTY folders are NOT created, but by removing this option, Empty folders from Source are not created in Local.
Output of the above command:
Source:
reponame/path/to/my/project/dir1/file1
reponame/path/to/my/project/dir1/dir2/file1
reponame/path/to/my/project/dir1/dir2/file2
Target:
/dir1/file1
/dir1/dir2/file1
/dir1/dir2/file2
/dir1/dir2/dir2  (I don't want this directory to be created)
Can someone provide me an option for downloading all EMPTY folders and at the same time, NOT to create the duplicate EMPTY folders with the above command?  Thanks.

@shivaprasadh,
I think that the following command should get you what you want:
jfrog rt dl --threads=10 --include-dirs --recursive "Artifactory-Source-Repo/Test_Project/" "Test_Project/"

Please let me know if this works.

I had exact same issue and leave a solution.
Do not enable --include-dirs option.
jfrog rt dl --threads=10 --include-dirs=false --recursive "Artifactory-Source-Repo/Test_Project/" "Test_Project/" or jfrog rt dl --threads=10  --recursive "Artifactory-Source-Repo/Test_Project/" "Test_Project/"

Thank you for sharing @busymans!


Add drone builders

I made a new recipe, want to have builders that are set to use it by default.  These are meant to run builds and then isolate build outputs for other builders to package.

If I understand correctly, the purpose of this PR is to separate builds from other tasks, so that we can use powerful machines later for building, is that right?

It's so we can make a request to a machine that only does a build (and then isolates certain files/directories for later usage).  Our current engine recipe is more complicated and does a ton of other stuff.
So at a high level, yes, more or less that's the case.


Failed Upgrade - Could not get lock /var/cache/apt/archives/lock. It is held by process 37677 (python3)

The Script was aborted at the Step

( stage Update Plesk extensions / action update Plesk extensions: docker, grafana, panel-migrator, ruby, site-import ) 03:06 / 15:40

The last log lines:
2024-06-23 23:29:18,408 - INFO - Reading package lists...
2024-06-23 23:29:18,754 - INFO - Building dependency tree...
2024-06-23 23:29:18,754 - INFO - Reading state information...
2024-06-23 23:29:19,144 - INFO - Calculating upgrade...
2024-06-23 23:29:19,319 - INFO - The following packages were automatically installed and are no longer required:
2024-06-23 23:29:19,320 - INFO - g++-10 guile-2.2-libs libaom0 libbpf0 libcbor0 libdav1d4 libdns-export1110
2024-06-23 23:29:19,320 - INFO - libisc-export1105 libldap-2.4-2 libmpdec3 libprocps8 libpython3.9
2024-06-23 23:29:19,321 - INFO - libpython3.9-minimal libpython3.9-stdlib libstdc++-10-dev libusb-0.1-4
2024-06-23 23:29:19,322 - INFO - libx265-192 linux-image-4.19.0-26-amd64 python3.9 python3.9-minimal telnet
2024-06-23 23:29:19,322 - INFO - Use 'apt autoremove' to remove them.
2024-06-23 23:29:19,327 - INFO - E: Could not get lock /var/cache/apt/archives/lock. It is held by process 37677 (python3)
2024-06-23 23:29:19,327 - INFO - E: Unable to lock directory /var/cache/apt/archives/
2024-06-23 23:29:19,328 - ERROR - Command ['apt-get', 'dist-upgrade', '-y', '-o', 'Dpkg::Options::=--force-confdef', '-o', 'Dpkg::Options::=--force-confold'] failed with return code 100
2024-06-23 23:29:19,328 - ERROR - Failed: do dist-upgrade. The reason: Command '['apt-get', 'dist-upgrade', '-y', '-o', 'Dpkg::Options::=--force-confdef', '-o', 'Dpkg::Options::=--force-confold']' returned non-zero exit status 100.
2024-06-23 23:29:20,134 - DEBUG - Going to write json '/usr/local/psa/var/debian11to12/actions.json' with new data
2024-06-23 23:29:25,424 - DEBUG - Sent error report
2024-06-23 23:29:25,433 - DEBUG - Trying to send status of conversion by report-update utility '/var/cache/parallels_installer/report-update'
2024-06-23 23:29:25,558 - ERROR - debian11to12 process has failed. Error: Failed: do dist-upgrade. The reason: Command '['apt-get', 'dist-upgrade', '-y', '-o', 'Dpkg::Options::=--force-confdef', '-o', 'Dpkg::Options::=--force-confold']' returned non-zero exit status 100.
2024-06-23 23:35:33,489 - INFO - Started with arguments ['./debian11to12', '--prepare-feedback']
2024-06-23 23:35:33,490 - DEBUG - Got upgrader name 'Plesk::Debian11to12Upgrader' for feedback preparation from '/usr/local/psa/var/debian11to12/resume.json'
2024-06-23 23:35:33,490 - DEBUG - Detected current OS distribution as Distro.DEBIAN12
2024-06-23 23:35:33,490 - DEBUG - Current system description: BasicSystemDescription(os_name='Debian', os_version='12')
2024-06-23 23:35:33,490 - DEBUG - Available upgraders: [Debian11to12Factory(upgrader_name=Plesk::Debian11to12Upgrader)]
2024-06-23 23:35:33,490 - DEBUG - Looking for upgrader by the name 'Plesk::Debian11to12Upgrader'
2024-06-23 23:35:33,490 - DEBUG - Found upgraders: [Debian11to12Factory(upgrader_name=Plesk::Debian11to12Upgrader)]
2024-06-23 23:35:33,490 - DEBUG - Selected upgrader: Debian11to12Upgrader
2024-06-23 23:35:33,490 - DEBUG - Upgrader Debian11to12Upgrader support of your system: as source = False, as target = True
From my understanding, the lines
2024-06-23 23:29:19,327 - INFO - E: Could not get lock /var/cache/apt/archives/lock. It is held by process 37677 (python3)
2024-06-23 23:29:19,327 - INFO - E: Unable to lock directory /var/cache/apt/archives/
means that another plesk update process running which locks the apt
I have seen it multiple times in manual dist upgrades..
If you wait a while here, and den re-execute the command it will works (on manually updates)
I've seen in the feedback zip archive sensitive information. So i will not upload it here.
If it helps, i can send you the log output, please provide a e-mail or similar.

If it's reproducible, could you please show the details of the process holding the lock? That is, its command line and parent tree as output by  pstree -alstTp <pid>.

I've seen in the feedback zip archive sensitive information.

Could you elaborate what kind of information in feedback archive do you consider sensitive?

@kpushkaryov

If it's reproducible

A second try this evening works as expected. Thank you for the great tool!!
I will use your tool in the next months many times :-)
Hopefully i can give you something back with some nice pull requests ;)
About the sensitive information, no panic but maybe a good point to remove it in the log :-)
in the log "\var\log\plesk\debian11to12.log" are apt output which contains the hostname of the machine.

2024-06-23 23:24:47,807 - INFO - apt-listchanges: Mailing root: apt-listchanges: news for xyz

Also in the "\version.txt" are kernel output which contains the hostname of the machine.

Kernel information: Linux xyz 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux


Restrict discoveryProperties key name format

What this PR does / why we need it:
ref #634
Add pattern for discoveryProperties key to avoid empty string as key name.  Expected key name format is C_IDENTIFIER ("^[_A-Za-z][_A-Za-z0-9]*$")
Special notes for your reviewer:
If applicable:

[ ] this PR has an associated PR with documentation in akri-docs
[ ] this PR contains unit tests
[ ] added code adheres to standard Rust formatting (cargo fmt)
[ ] code builds properly (cargo build)
[ ] code is free of common mistakes (cargo clippy)
[ ] all Akri tests succeed (cargo test)
[ ] inline documentation builds (cargo doc)
[ ] all commits pass the DCO bot check by being signed off -- see the failing DCO check for instructions on how to retroactively sign commits

/version patch


bug: poor constrast

What version of daisyUI are you using?
v3.2.1
Describe your issue
Grab the background color and button component's background color and throw them into a contrast checker:

Seems like there are contrast tests, but they don't check base-100 and base-200. Which is what the background and button are using for their colors respectively. The button isn't the only thing this applies to, many components are using base-200 as their background color.
What browsers are you seeing the problem on?
No response
Reproduction URL
https://daisyui.com/components/button/

You're comparing the background text of the button with the background text of the page. As you can see in your screenshot, the contrast tool you're using is for comparing the text color on a background color. For example, you can compare the text color of button with the background color of the button.

@saadeghi The last section in the screenshot is titled "Graphical Objects and User Interface Components". The page says:

WCAG 2.1 requires a contrast ratio of at least 3:1 for graphics and user interface components (such as form input borders).


Adds json response validation and class transformation

Task: https://github.com/users/sebdei/projects/1?pane=issue&itemId=44751913
A proposal for gpt json response validation by decorating the properties of the target class based on the npm packages

class-validator
class-transformer
reflect-metadata

Alternatives:

The npm package Ajv JSON schema validator with TypeScript support

A small example of this PR:
The key target contains the validated JSON object. The first ingredient is missing the key amount. Therefore, the validation fails with the error message amount must be a string as it was undefined. The following JSON is an output of a failed validation.
[
  {
    "target": {
      "name": "Kartoffelbrei",
      "duration": "30 Minuten",
      "ingredients": [{ "description": "Kartoffeln" }, { "amount": "1", "description": "Zwiebel" }],
      "steps": [
        {
          "description": "Kartoffeln und Zwiebeln schälen und in kleine Stücke schneiden."
        },
        {
          "description": "Kartoffelbrei zubereiten."
        },
      ]
    },
    "value": [{ "description": "Kartoffeln" }, { "amount": "1", "description": "Zwiebel" }],
    "property": "ingredients",
    "children": [
      {
        "target": [{ "description": "Kartoffeln" }, { "amount": "1", "description": "Zwiebel" }],
        "value": { "description": "Kartoffeln" },
        "property": "0",
        "children": [
          {
            "target": { "description": "Kartoffeln" },
            "value": undefined,
            "property": "amount",
            "children": [],
            "constraints": { "isString": "amount must be a string" }
          }
        ]
      }
    ]
  }
]

@sebdei PING


[FLINK-21521][k8s] Pretty print K8s specifications in logging

What is the purpose of the change
Currently, we are using the fabric8 toString to print the spec. It could be improved by using jackson to do the pretty print(yaml format with indent).
Brief change log

Pretty print K8s specifications in logging

Verifying this change

Set the log level to DEBUG in src/test/resources/log4j2-test.properties and run the test Fabric8FlinkKubeClientTest#testCreateFlinkTaskManagerPod in your IDE. You will find the pretty print yaml for TaskManager pod.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @tillrohrmann would you like to have a look at this simple change?

cc @tillrohrmann would you like to have a look at this simple change?

cc @tillrohrmann would you like to have a look at this simple change?

@tillrohrmann Thanks for you review. Comments addressed.

cc @tillrohrmann PR updated.

cc @tillrohrmann PR updated.


Cannot increase counter

I can't increment/decrement the counter by typing any keys. Even when pressing /, it doesn't enter input mode. The app works (i.e. app ticker increases), but it seems it doesn't receive input, not even Ctrl-C to quit. Any ways to debug this?
Thanks!

Can you type cargo run -- --version?
ratatui-async-template v0.1.0-10-f59c265

Following the nicely written tutorial/book, I stumbled over the configuration.
Creating a config.toml with the following content (Help does not exist, example needs to be updated):
[keymap]
"q" = "Quit"
"j" = "ScheduleIncrement"
"k" = "ScheduleDecrement"
"/" = "EnterInsert"
"ESC" = "EnterNormal"
"Enter" = "EnterNormal"
"Ctrl-d" = "Quit"
"Ctrl-c" = "Quit"
"Ctrl-z" = "Suspend"

and then running with RATATUI_ASYNC_TEMPLATE_CONFIG=. cargo run to have the app pick up the config makes it work.
ratatui-async-template on  main [?] via 🦀 v1.72.0 ❯ cargo run -- --version
    Finished dev [unoptimized + debuginfo] target(s) in 0.13s
     Running `target/debug/ratatui-async-template --version`
ratatui-async-template v0.1.0-6af1fed

Authors: Dheepak Krishnamurthy

Config directory: /Users/$USER/Library/Application Support/com.kdheepak.ratatui-async-template
Data directory: /Users/$User/Library/Application Support/com.kdheepak.ratatui-async-template

Oh my! Good point.
I think in addition to improving the documentation, I have to make it such that the app works even without a configuration file.

I've updated the code such that a default keymap will be used if there's no configuration file. I'll update the documentation later today.
Thanks for the error report!

That did the trick, thanks to all! ^_^

c


Question about maybe using imgui for love2dcs?

is it possible to draw onto a imgui widget?

In my oponion, It is feasible.
I search for C# version of ImGui. and i get https://github.com/mellinoe/ImGui.NET
It said :

Dear ImGui does not care what technology you use for rendering; it simply outputs textured triangles.

And I found that ImGui.NET can be used with XNA : https://github.com/mellinoe/ImGui.NET/tree/master/src/ImGui.NET.SampleProgram.XNA
So you just need to adapt this folder with Love2DCS, you should be able to achieve your goal.

That would be nice, love needs a gui system

wait so this should run in love2cs's draw hook?
or does it need special implementation?

i think it need to update IO information  and generate rendering instructions,
so we need give the ImGui the input, and implement the rendering instructions:
:

// on load ..
 ImGui.SetCurrentContext(ImGui.CreateContext())

// ... game loop ...
while (true )
{
            var io = ImGui.GetIO();
             io.deltaTime =  ... // update time
            io.KeysDown =// ... update mouse & key input
            ImGui.NewFrame();

           ImGui.Text()  //  ... layout gui
           //   layout gui
           ImGui.Image()  // layout gui ....

            ImGui.Render();
            var drawData = ImGui.GetDrawData()
            // render the draw data here :
            Render_drawData(drawData);
}

this would be nice but there is actually Eto.Forms which might be better for native looking gui
https://github.com/picoe/Eto
it would need a love2dcs implementation though.


[ALS-5307] Omit user store fields for api update/create user request

Since the user store now has the createdAt field, it is sent in api requests, which block fields not listed in the validation scheme. We also don't need to send this in the request, so we're going to omit from user create/update requests.
Also, simran requested adding a user name column. So just adding that in and changing default widths.
Checklist:

[X] Have you successfully tested with your changes locally?
[x] Have you successfully deployed to an AWS account with your changes?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Reviewed in office hours, 12/07/2023.


changed save icon to red

#2
Made the changes needed for the website.

@Akhilbisht798  Great Job

#2
Made the changes needed for the website.

You have done great job
Once again go through whole site & check for all features and colors combination then ill merge and close this issue 😄

@Akhilbisht798  https://www.linkedin.com/in/prasad-chavan2003/  connect lets do some discusson

Yes i have checked entire code and it look good to me.

@prasad-chavan1 surely. I will connect to you.

Yes i have checked entire code and it look good to me.

When i refresh page then the icon color is reverting back to green solve that bug

Hey this might be due to cache can you check in some other browser can confirm it. I have same problem but i have tried it a another browser and it work good.

If that is not the case  with you i can look what is the problem.

If that is not the case with you i can look what is the problem.

Come on linkedIn chats

okay I'll try it later today
On Mon, Oct 2, 2023, 11:04 AM Akhil Bisht @.***> wrote:

Hey this might be due to cache can you check in some other browser can
confirm it. I have same problem but i have tried it a another browser and
it work good.
—
Reply to this email directly, view it on GitHub
https://github.com/prasad-chavan1/Animesthetic-Social-Media/pull/17#issuecomment-1742422044,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXFPHSUYT22IBTJHAABSSZTX5JG6PANCNFSM6AAAAAA5O3PCDA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey I have fixed the issue. This is complete.

Hey I have fixed the issue. This is complete.

Try changing logo that stuff also comes under color combination & themes

Hey @prasad-chavan1, I can open another pr for that. It may took some time.
And It will be more clear and concise that i do that stuff seprately in order to not clear any conflict

Also we will some discussion. To that stuff. I have'nt started searching for logo yet. But i may start this process using ai genration


rename rust-matching-angle-bracker-timer to rust-matching-angle-bracket-timer

This corrects a typo in a variable name.

r? @pnkfelix
(rust_highfive has picked a reviewer for you, use r? to override)


The segmentation code is not working; there is a problem in tensor dimension

The InitializationNotebook is not working properly. As segmentation is the core of this repository, it would be great if the developers can fix the issue and update their code.
The error below has been reported many times:
        RuntimeError                              Traceback (most recent call last)

~\AppData\Local\Temp\2\ipykernel_6640\517464012.py in <cell line: 19>()
32             x = x.to(device)
33             #print('x shape', x.shape)
---> 34             y = np.concatenate([model(x[i:(i + block), :, :, :])["out"].detach().cpu().numpy() for i in range(0, x.shape[0], block)]).astype(np.float16)
35             print(y.shape)
36             start = 0
RuntimeError: Given groups=1, weight of size [45, 3, 1, 7, 7], expected input[1, 104, 3, 112, 112] to have 3 channels, but got 104 channels instead

Hello, I have the same problem, did you find any solutions for it?

Check out #11, it is not merged but they did fix quite some bugs in the notebook there.


Hentai2Read

Hentai2read
Link: https://hentai2read.com
Reason: large NSFW source with all chapters of the title combined into one (also has better quality of some titles)

I'm on the job 🫡

I'm on the job 🫡

Thanks mate.
Any progress?

pr is open but it needs some more changes before being merged


Dependencies

Would be nice to be able to pick which Reactive Framework you want to use without Xcode downloading all of them to your project.

Nevermind doesn't seem to affect the current project with dependencies list in Xcode


Clean up after the 10th birthday

Remove the special banner support added in https://github.com/kubernetes/website/pull/46684, leaving some scaffolding in place.
/kind cleanup

Alternative: someone (ideally, not me) has capacity and makes time to tidy that support up a bit more, so we can show a less prominent message every project birthday if wanted. I'll be delighted if that happens; if not, we should merge this.

/lgtm

This PR needs approval required from sig-docs-website-owner

@kubernetes/sig-docs-leads PTAL (not urgent)

/approve


updateauth doesn't check for uniqueness of keys

Despite what the comment says:
https://github.com/EOSIO/eos/blob/master/libraries/chain/include/eosio/chain/authority.hpp#L70-L91

The reference link in this issue is no longer relevant. I think the way authority is validated is already updated in the latest code. I'm closing this issue as it's no longer relevant, but if you find issue with the latest code, please open a new issue. Thanks!


"Previously answered on YYYY-MM-DD" text is missing from some prefilled answers

Describe the bug
"Previously answered on YYYY-MM-DD" text is missing from some prefilled answers
To Reproduce
Steps to reproduce the behavior:

Apply to a program and submit
Reapply to program, all answers should be prefilled
Notice that only some of those prefilled answers have the "previously answered on " text.

Expected behavior
All prefilled answers should have the "Previously answered on YYYY-MM-DD" text
Screenshots

Note: until recently we stored pre-submit data in the application but largely read it from the applicant stored data too. It seems likely that is having an effect here.

I tested this out and I'm seeing that the "previously answered on" text will show if I answered those questions in a different program. If I answered the questions in the current program, they won't show up.
So for example:

I apply for Accessibility Primary
I reapply to Accessibility Primary and see my answers but no "previously answered" text
I apply to Accessibility Secondary and see "previously answered" for all answers that I filled out in Accessibility Primary
I change some answers in Accessibility Secondary
I go back to Accessibility Primary and see "previously answered" for all answers that I changed in Accessibility Secondary (or on the same page as other answers I changed)

@jeanniefu, I just want to check what the intended behavior should be? This seems to be working as intended if we want to only show the "previously answered on" for questions answered in a different program, but if we want it to show for questions answered previously in the same program, this would be a bug. Let me know what you think - thanks!

Thanks @dkatzz for investigating! Sounds like the feature is working as intended as originally designed.
However, I personally think the current UI confusing. What do you think about just marking all of them as "previously answered"? So we don't have a filter for whether it was used in this program vs a different program.
@bion - Do we have a UX person who could help make a decision?

@mferhut for UX

We can include ‘Previously answered on…’ for all questions regardless if it was answered on another program or the one the applicant is currently on. The date will help distinguish the exact timing of it to the applicant.


Preparing Request Manager / Fill Manager - Tearing down test agents

Before announcing we need to

[x] shutdown our mainnet test agents
[x] remove them from whitelist
[ ] add real agents to whitelist
[x] configure the correct limits in the Request managers

Agreed transfer limits are 1000 USDC (1_000_000_000). @istankovic can you adjust the limits?

On it. :+1:

Our mainnet agents have been removed from the whitelists:
https://optimistic.etherscan.io/tx/0xc012e8d6cee447e13bcf5fa6b89e14a2eb3bdce88ec87f7eff8f36b9f7d568b8
https://optimistic.etherscan.io/tx/0x3ec1ed6127bbb1fc8064f109c809c0c343eb23cc6a00ad2aeaf418d742cc0743
https://bobascan.com/tx/0xe4f3165a9b3a59e84505fea8866d7f58c187aa8608fd3c909ec609e118cc5b9a
https://bobascan.com/tx/0x08f1bf9161367aac5f44337321770d9d7554ebc6d512b221ab981266e5d3f044

Whitelisted 0xe9070FFc3B1b513F79a35983784C19AeFa093521:
https://optimistic.etherscan.io/tx/0x546ddb6960431c82638dd2eea6f0b14cad852d34f6dddabda10696807f156e3c
https://bobascan.com/tx/0x363d72ed696fc9412cfaf03ff77e992f200927f48afb6154732c490b55b55e00

This is done now.


zsh: strange alignment problems after recent update

Describe the bug
I updated nixpkgs recently and got some strange zsh behavior. I have quite complex zsh config, so I'm not sure how to reproduce it properly yet. But there are some observations:

it doesn't work properly with starship right_format which is RPROMPT:

Note where is the cursor - it's behind the arrow and once it type anything it overwrites the arrow. Also RPROMPT is not aligned properly - it has too much space at the right border which wasn't the case before.

tab completion also suffers:

Here I just typed echo  and then pressed TAB for completion, and it printed echo at wrong position, making it printed twice (if I press backspaces it just deletes second printed echo and stops).

And finally remote building doesn't work for me anymore - it just hangs at ssh attempt (I see the established connection on the builder but it does nothing). It might be related to shell, but might be a completely different problem.

Steps To Reproduce
Steps to reproduce the behavior: not sure yet
Additional context
I'm filling this issue in a hope that someone might know what has recently changed. Will try to investigate it further and add an additional info here.
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 6.4.4, NixOS, 23.11 (Tapir)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.15.1`
 - channels(root): `"nixos-21.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Hm, my locales are also broken - I can type only English letters in my terminals.
Also it seems zsh has problems only when starship is enabled.

Yet another observation - midnight commander can render only ascii symbols now.

Looks like something is wrong with locale generation:
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

ok, found the problem. I was overriding i18n.supportedLocales and didn't have C.UTF-8/UTF-8 there. It somehow worked before the update, but broke after. Adding it to supportedLocales fixed the problem.


Nomination Scraper issue?

I keep getting an error in nomination_info.py, line 204. This showed up for me 3 days ago, is anyone else having an issue with it?
My guess is that the page changed slightly. I am looking into it.
Traceback (most recent call last):

  File "tasks/utils.py", line 173, in process_set
    results = fetch_func(id, options, *extra_args)

  File "tasks/nomination_info.py", line 57, in fetch_nomination
    nomination = parse_nomination(nomination_id, body, options)

  File "tasks/nomination_info.py", line 204, in parse_nomination
    raise Exception("Choked, couldn't find nominee info.")

Scraper being written for congress.gov which may resolve this issue. See https://github.com/unitedstates/congress/issues/173

Closing b/c of #173.


bindr ignores mouse click

I have this in my config:
bindr=SUPER,Super_L,exec,killall -INT rofi || rofi -show
When I move or scale a window with SUPER-mouse drag and then release SUPER the binding is activated.
Expected result:
The binding is not activated because the mouse click cancels it.

fixed in 19cd04c85f6c1cf8f4a88f6a1588ff676f1c9779