Movie-Info-App

Add a movie information giving website using HTML, CSS, Javascript, that give all relevant information of any movie input by the user
Expected behavior
on clicking button- cast, imdb rating, poster, director like information should be displayed
Screenshots (optional)

Additional context (optional )

@sadanandpai pls assign this issue to me

This repository is specifically for logical front-end challenges and not for full-blown websites/UIs.
So this issue will not be worked on.

Hey @arpansaha13 I guess it is not a full blown website as we are only making a API call in it. It is similar to other projects which are already merged. Please reconsider it.

HTML + CSS full pages will be the future plan, If it is an API fetching and displaying piece, will consider it.


@rustbot ready and @rustbot author erroring out in a few cases

on this PR: https://github.com/rust-lang/rust/pull/95696#issuecomment-1242892564
Tried using @rustbot ready shortcut to switch labels and got an error

Error: The "Ready" shortcut only works on pull requests.

I don't know what is different about this pull request that produces such an error.
Zulip:
https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/.40rustbot.20author.20not.20working

Another example: https://github.com/rust-lang/rust/pull/101442#issuecomment-1242932619


"Barcode Found" but result handler not called

Hello, I'm using the following code to scan for a QR code, apparently the scanning works because when pointing the camera to a QR code [ZXing.Net.Mobile] Barcode Found is logged from ZXing, however my defined HandleScanResult function is not called, am I registering the callback wrong?
        void scan()
        {
            var opts = new MobileBarcodeScanningOptions
            {
                PossibleFormats = new List<ZXing.BarcodeFormat> {
                    ZXing.BarcodeFormat.DATA_MATRIX,
                    ZXing.BarcodeFormat.QR_CODE
                },
                CameraResolutionSelector = availableResolutions => {

                    foreach (var ar in availableResolutions)
                    {
                        Console.WriteLine("Resolution: " + ar.Width + "x" + ar.Height);
                    }
                    return null;
                }
            };

            scanFragment.StartScanning(HandleScanResult, opts);

        }

        private void HandleScanResult(ZXing.Result obj)
        {
            if (obj.Text.IsNullOrEmpty()) //BREAKPOINT HERE, NEVER REACHED
            {
                return;
            }
        }

When googling further I found this issue:  #643 implementing the solution suggested by @ElteHupkes (thank you very much btw! :)) seems to resolve this issue.
I'll leave this issue open as I think this could use either a fix or some documentation.

What version of ZXing.Net.Mobile are you using?

Doesnt work

I'm using the following packages:
ZXing.Net.Mobile.Core, Version=<IP_ADDRESS>
ZXing.Net.Mobile.Forms, Version=<IP_ADDRESS>
ZXing.Net.Mobile.Forms.Android, Version=<IP_ADDRESS>
ZXingNetMobile, Version=<IP_ADDRESS>
zxing.portable, Version=<IP_ADDRESS>

I'm using the following packages:
ZXing.Net.Mobile.Core, Version=<IP_ADDRESS>
...

Well, the reason of why the issue you referenced is closed is because it could be already fixed in the 3.0.0-beta version. Please test this version.

Running 3.0.0-beta5 and still have this issue on Android.

Running 3.0.0-beta5 and still have this issue on Android.

It is a timing issue it seems.
scanner in ZXingScannerFragment gets set up in OnCreateView which is a lifecycle method. However, in the FragmentActivity code the call to StartScanning happens after the Fragment is initialized. This means that OnCreateView hasn't been called yet, and the internal Scan() method isn't called and callback is never hooked up.

It is a timing issue it seems.
scanner in ZXingScannerFragment gets set up in OnCreateView which is a lifecycle method. However, in the FragmentActivity code the call to StartScanning happens after the Fragment is initialized. This means that OnCreateView hasn't been called yet, and the internal Scan() method isn't called and callback is never hooked up.

@Cheesebaron Yes, that was exactly my conclusion here: https://github.com/Redth/ZXing.Net.Mobile/issues/643#issuecomment-357204858. I actually thought this had been resolved by now. Anyway, the workaround I added there probably still does the trick.

@Cheesebaron Yes, that was exactly my conclusion here: https://github.com/Redth/ZXing.Net.Mobile/issues/643#issuecomment-357204858. I actually thought this had been resolved by now. Anyway, the workaround I added there probably still does the trick.

I believe you are correct, in the end a coworker implemented a workaround for this, looking at our code he added a delay before setting up the scanner. The whole setup etc is still called in OnCreateView
        public override void OnRequestPermissionsResult(int requestCode, string[] permissions, [GeneratedEnum] Permission[] grantResults)
        {
            base.OnRequestPermissionsResult(requestCode, permissions, grantResults);

            var lbNotGrantedPermission = Array.Exists<Permission>(grantResults, permission => permission != Permission.Granted);

            if (lbNotGrantedPermission == true)
            {
                // Some permissions were not granted
                moCameraPermissionsDescription.Visibility = ViewStates.Visible;
            }
            else
            {
                // All permissions were granted
                Handler loHandler = new Handler();
                Action loAction = () =>
                {
                    SetUpScanner();
                };

                // We need some delay due to animated transition between the fragments. Also, without delay
                // the scanner don't work right after permissions were granted(only the first time)
                **loHandler.PostDelayed(loAction, miSetupScannerDelay);**
            }
        }

I believe you are correct, in the end a coworker implemented a workaround for this, looking at our code he added a delay before setting up the scanner. The whole setup etc is still called in OnCreateView
        public override void OnRequestPermissionsResult(int requestCode, string[] permissions, [GeneratedEnum] Permission[] grantResults)
        {
            base.OnRequestPermissionsResult(requestCode, permissions, grantResults);

            var lbNotGrantedPermission = Array.Exists<Permission>(grantResults, permission => permission != Permission.Granted);

            if (lbNotGrantedPermission == true)
            {
                // Some permissions were not granted
                moCameraPermissionsDescription.Visibility = ViewStates.Visible;
            }
            else
            {
                // All permissions were granted
                Handler loHandler = new Handler();
                Action loAction = () =>
                {
                    SetUpScanner();
                };

                // We need some delay due to animated transition between the fragments. Also, without delay
                // the scanner don't work right after permissions were granted(only the first time)
                **loHandler.PostDelayed(loAction, miSetupScannerDelay);**
            }
        }

Ah, yes. You are right. Not sure what the better approach would be though. I don't like the delay code.
Perhaps, just check if callback was set in OnCreateView, and call StartScanning if so. This way it doesn't automatically start scanning if someone didn't call StartScanning already.

Ah, yes. You are right. Not sure what the better approach would be though. I don't like the delay code.
Perhaps, just check if callback was set in OnCreateView, and call StartScanning if so. This way it doesn't automatically start scanning if someone didn't call StartScanning already.


Link for Message object is dead

Expected behavior
Open a page which describes Message object
Actual behavior
404
Steps to reproduce

Access this page: http://pulsar.incubator.apache.org/docs/latest/admin/GeoReplication/#Selectivereplication-dl0fh
Click the third link, "Message", in a paragraph below.

System configuration
N/A

Confirmed. Thanks.


Add dynamic settings api for plugins

Here is the report for 439adf2a46050908a06fa49c2c34c93ca8becb53 (korycins/saleor @ dynamic_settings_for_plugins)
Base comparison is 7818fa14feadd8f9deb746ce45b5278de804c18e.
No differences were found. (click me)

# api.benchmark checkout
  test name                           	left count 	right count	duplicate count
  ------------------------------------	-----------	-----------	---------------
  add billing address to checkout     	         34	         34	             20
  add shipping to checkout            	          7	          7	              0
  checkout payment charge             	         14	         14	              0
  complete checkout                   	          6	          6	              0
  create checkout                     	         41	         41	             20

# api.benchmark homepage
  test name                           	left count 	right count	duplicate count
  ------------------------------------	-----------	-----------	---------------
  retrieve main menu                  	          5	          5	              0
  retrieve product list               	          4	          4	              0
  retrieve secondary menu             	          5	          5	              0
  retrieve shop                       	          2	          2	              0

# api.benchmark product
  test name                           	left count 	right count	duplicate count
  ------------------------------------	-----------	-----------	---------------
  product details                     	         13	         13	              3

# api.benchmark variant
  test name                           	left count 	right count	duplicate count
  ------------------------------------	-----------	-----------	---------------
  retrieve variant list               	          9	          9	              2

@korycins what about if the plugin owner wants to change their default configuration or add entries to it? Wouldn't it be better to just have a configuration to {} by default and then merge the defaults and the db one?

@NyanKiyoshi
Each plugin can have a different configuration structure. It can have 2 or 5 or 7 different fields and because of that, the configuration is stored in DB. See model PluginConfiguration.
When someone integrates new plugin, like Avalara or Vatlayer, the active plugin needs to save its default configuration into DB. For most of them, it will be only a template of configuration structure that API will send to the Dashboard.  Shop owner can modify his plugin configuration directly from the Dashboard.
So to answer your question.  Plugin owner creates own configuration with as many config fields as he needs to have. He creates own default configuration that should be saved in DB. This config will be served by API.


test: ignore unused arguments in tests

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

When invoking clang directly, with a newer clang, it is possible to get an
unused argument error failing the test.  Silence this by telling clang to ignore
unused arguments.  Since this is for testing purposes we are not too concerned
about ensuring that the exact set of arguments are supplied to the compiler.

@swift-ci Please test

I don't have push rights, could you please take care of this for me?

-1 from me. I definitely want to know when I misspelled an argument and Clang allowed it through anyway.

@jrose-apple while I agree that would be nice, it doesn't always work out.  I just disabled it for the case where there can be an error due to the unused argument (-fmodules-cache-path).

When is that unused?

@jrose-apple I ran into a couple of cases of this causing errors against a newer clang.  I suppose that we could limit this to master-next, but, Im not sure that there is any harm in pushing this to master instead.

I maintain that this makes it harder to write new tests. We already ignore most warning output anyway, and it isn't an error, so why do we care?

I ran into a few cases where the unused option was an error for the clang importer.  BTW, this doesn't disable the unknown warnings, it just permits adding options that are unused into the invocation.

Sorry, I'd like to see that there's not a reasonable workaround before accepting this.

@compnerd I think we would rather catch those issues via this option and just update the tests.

Okay, in that case, the following tests were the ones that complained:

PrintAsObjC/cdecl.swift
PrintAsObjC/classes.swift
PrintAsObjC/empty.swift
PrintAsObjC/enums.swift
PrintAsObjC/simd.swift

Would it be preferable to add a new lit "tool" to avoid the -fmodule-cache-path?

If there's really just that few, I think it's best to just add -Qunused-arguments to those particular invocations that need to pass -fno-modules.
Thanks for looking into this, Saleem!

@jrose-apple sounds reasonable to me; Ive uploaded a modified version of the change that just applies it on those particular tests.  Happy to help :-).

Sanity-check time:
@swift-ci Please smoke test

@jrose-apple don't have push rights, would you mind pushing this for me?

Oops, meant to after the checks passed. Thanks!


/docs/home/ links to current release docs even for older versions

This is a Bug Report

Problem:
https://kubernetes.io/docs/home/ links to pages on https://kubernetes.io/
However:

https://v1-18.docs.kubernetes.io/docs/home/ links to pages on https://kubernetes.io/ (and not https://v1-18.docs.kubernetes.io/)
https://v1-17.docs.kubernetes.io/docs/home/ links to pages on https://kubernetes.io/
https://v1-16.docs.kubernetes.io/docs/home/ links to pages on https://kubernetes.io/

you get the picture!
Discussion
[How] should we address this?
Page to Update:
https://kubernetes.io/docs/home/ (and backports?)

Kubernetes Version:
I originally logged this issue just after the v1.19 release.
/kind bug
/priority important-longterm
(because we want people to find useful documentation for older versions, and not to be misled)

@sftim I would like to solve this
/assign


194 feature decision tree implement stopping behavior

Description
To also handle stop signs the intersection behavior is extended. If a stop sign is detected and no traffic light is recognized, just like in the real world where a traffic light has a higher priority than a stop sign, the agent has to wait in front of the intersection. There is also a new mock topic intersection_clear that indicates that we can drive through the intersection. This is only necessary if there is a stop sign, as we can drive through the intersection only if there is no other traffic.
please note that this PR will only be merged after #192, and should be reviewed after that one as there are many redundant changes
Fixes #194
Time invested
Josef: 5 h
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Does this PR introduce a breaking change?
no
Most important changes
intersection.py
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works (might be obsolete with CI later on)
[x] New and existing unit tests pass locally with my changes (might be obsolete with CI later on)

This is now ready for review

This PR can be merged and when the main branch is ready, it can be put into #197. For now, I have worked on that branch independently, bc it was testable. The additions in this PR shouldn't have too many changes compared to #197.


Parallel taks are forwarded to the end command

ERROR in multi main
Module not found: Error: Cannot resolve module 'build.test,build.staging,build.edge'

p-s version: 1.0.2
node version: 6.6.1

The command executed:
npm start -p build.x,build.y

The output:
ERROR in multi main
Module not found: Error: Cannot resolve module 'build.x,build.y'

Problem description:
My build command run webpack to build a bundle file for my project. But when running npm start -p build.x,build.y, it appends the parallel commands to webpack and produce an error:
webpack 'build.x,build.y'

I think the parallel taks shouldn't be forwarded to the end command

Thanks for the report!
Hmmm... Very interesting. If you'd like to dig, here's where we exclude p-s flags from the args that are forwarded on to the scripts.

Thanks, I'll take a look :)

@kentcdodds When running npm start -p this,that. program.parallel is undefined in getScriptsAndArgs.

Oh I see...
npm start -p this,that is executing p-s "this,that".. So the parallel option is gone. I guess npm takes it as an option instead of p-s :/
So I'm now using npm start -- -p this,that which resolve the issue.
Closing the ticket, unless you know of a "fix"?

Ah, yep, that's the solution. Do you think we could/should add something to the docs as a common pitfall?

Might be useful to add a note for it when using npm start instead of p-s. In my case, I'm using npm start because it's part of a build system. And using p-s is not possible. Using ./node-modules/.bin/p-s fails to run sub-commands because p-s is not found.

Might be useful to add a note for it when using npm start instead of p-s. In my case, I'm using npm start because it's part of a build system

Actually, the recommended use is to use npm start, but to put the scripts to be run in package-scripts.json. So generally you'd put the script you're trying to run in the package-scripts.json like this. Also, I think the thing that caused confusion is a fundamental misunderstanding of how npm scripts work. So maybe documenting something to remind people that if you want to make sure to pass arguments to a script, you need to use --. That's what I was thinking.

And using p-s is not possible. Using ./node-modules/.bin/p-s fails to run sub-commands because p-s is not found.

I think you have a typo. node-modules should be node_modules. You should be able to run node_modules/.bin/p-s. But really, you should be just using p-s in an npm script and it will work fine.

Oh I see, you mean having a simple script which will run my tasks in parallel. Yep I could do that too.
And yes, sorry for the typo. What I mean though was that if I manually run ./node_modules/.bin/p-s this and then this also run p-s that, the second command fails because p-s is not available. But that's expected I guess ;)

Ah, I see what you're saying. Yeah, basically the way that p-s works is it spawns a script with the same process.env as the current environment. So if the currently PATH doesn't include node_modules/.bin then the spawned script wont have it either. I suppose that p-s could explicitly add node_modules/.bin to the PATH. I'll create an issue for discussion about that.


Specify uid gid

Feature overview:

Adds non-privileged user valheim-server
uid and gid of valheim-server can be specified as environment variables USER_ID and GROUP_ID and defaults to 1001.
permissions for files needed for running valheim are adjusted during container startup by bootstrap process.

Internal changes

valheim-server, valheim-bootstrap, valheim-backup, and valheim-updater are running with user valheim-server
use debian's cron instead of busybox (setuid required for valheim-updater to modify crontab, but don't want to use setuid for all busybox binaries)

👍 🚢


A issue about deepL browser extension

that is the browser extension pronunciation function, which actually pronounces the translated text instead of the original, it is ridiculous.

Hi @httpsColon, I've asked the team responsible for the DeepL Chrome extension about this issue -- they are aware of this issue and it is on their to-do list.

This should now be addressed in the DeepL Chrome extension.


fix: add course_run to video engagement dataset (FC-0051)

This change adds course_run to fact_video_engagement, which enables filtering based on course_run to any charts that rely on fact_video_engagement.

Thanks for the pull request, @SoryRawyer! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.


added unique key prop to  components

Child components should all have unique keys per the React documentation. React will actually log an error to the console if no key is provided. This is a tiny change that adds a key to the Swatch components in the TwitterPicker only, using their index as the unique key. This will improve React's performance as well as stop the unnecessary errors.

done! thank you!


Add some free ebooks and courses about bash in French

What does this PR do?
Add resource(s)
For resources
Description
Shell and bash courses in French
Why is this valuable (or not)?
There is only one guide in the French section and those links remains the most complete free courses available in French since several years.
How do we know it's really free?
Because licences (GPL and Creative Commons) says so and mostly because I'm one of the writers.
For book lists, is it a book? For course lists, is it a course? etc.
Yeah I consider the first link as book because:

you can download offline and printable PDF or epub version on each of thoses
it is a real book of almost 100 pages and is very complete

The two other links are complementary smaller courses and exercices (but you can also download a PDF or epub version)
Of course we can debate on this.
Checklist:

[X] Read our contributing guidelines
[X] Search for duplicates.
[X] Include author(s) and platform where appropriate.
[X] Put lists in alphabetical order, correct spacing.
[X] Add needed indications (PDF, access notes, under construction)

Followup

Check the output of Travis-CI for linter errors!

Thanks, and welcome to free-programming-books!

Thanks, and welcome to free-programming-books!

Thanks and thanks for this amazing work!

Stop sending me imail pls
Em dom, 29 de ago de 2021 02:01, Idriss Neumann @.***>
escreveu:

Thanks, and welcome to free-programming-books!
Thanks and thanks for this amazing work!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/EbookFoundation/free-programming-books/pull/5502#issuecomment-907729346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APNXEGS4NOP2ELJNVJE2AGLT7G5JRANCNFSM5C7KAAIQ
.

I don't want to receive these emails anymore.


Url not changing on tab change

The url in the title bar does not change, when the tab is changed, however the title does change.

Fixed by #13


Add authorization check for private repos

Codecov Report
Base: 68.72% // Head: 67.52% // Decreases project coverage by -1.20% :warning:

Coverage data is based on head (fc3c951) compared to base (d225420).
Patch coverage: 3.44% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##              int     #315      +/-   ##
==========================================
- Coverage   68.72%   67.52%   -1.21%
==========================================
  Files          15       15
  Lines        1570     1598      +28
==========================================
  Hits         1079     1079
- Misses        375      402      +27
- Partials      116      117       +1

Impacted Files
Coverage Δ

apiclient.go
66.26% <0.00%> (-22.45%)
:arrow_down:

agent.go
75.68% <12.50%> (-2.14%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Is there an equivalent to DotNetUtilities.ToRSA() for ECDsa?

I have used OpenSsl.PemReader() and Security.DotNetUtilities.ToRSA() to load RSA keys from a PEM file and I'd like to be able to do the same for ECDsa keys.  Is there an equivalent function for this?

Hi!
Is there any news about this topic?
On advice from peterdettman issue/113 it is possible to use copy/paste of DotNetUtilities class for topic purpose. It is correct?


Android build?

Unsure if this is the right place to be asking, but I'm wondering if there are any plans for an Android build. It'd be nice to have a comfortable client for my phone.

Yes there is. Check it out: https://gmi.skyjake.fi/gemlog/2022-03_android-beta1.gmi

Awesome, thanks! I tried to install it via F-Droid, but even after adding the repo I couldn't find it via search,

I don't know what could be the problem with F-Droid, as it seems to work for me. However, the F-Droid repo APKs can be directly accessed here: https://github.com/skyjake/skyjake.github.io/tree/master/fdroid/repo


[i2c] Allow tx_fifo to self clear upon transaction complete

Currently, if tx fifo data is not completely drained during a target read, a nonempty interrupt is fired to alert software.
However, if before software handling is available another read is started, it is possible we will send out stale data (imagine for example the reads are targetting different registers).
In order to get around this, allow the tx fifo to self clear upon completition, this will cause the target to stretch and give software ample time to complete.
Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

does this make sense to you @a-will ? of course now i wonder if we need to capture how much was leftover before clearing..

based on #16579, it may be better to clear when there is a direction change instead of always clearing on start / stop.


missing type definition for withRecursive

Environment
Knex version: 0.16.3
Database + version: postgres 10.5
OS: Mac OS
Bug
The following example from the docs:
knex.withRecursive('ancestors', (qb) => {
  qb.select('*').from('people').where('people.id', 1).union((qb) => {
    qb.select('*').from('people').join('ancestors', 'ancestors.parentId', 'people.id')
  })
}).select('*').from('ancestors')

Doesn't type check 😟
Indeed, it doesn't appear in this file at all: https://github.com/tgriesser/knex/blob/master/types/knex.d.ts

@jrr Would you consider contributing a PR for this?

This was taken care of as a part of https://github.com/tgriesser/knex/pull/3209


Add more space between the page title and the content starting

e.g. as on the individual story pages


Newest goblin trader update cause fatal error with Apotheosis installed

Tried to boot up my datapack with the new goblin trader update and it crashes while loading and doesn't mention the cause.
Found out the mod that causes it was Apotheosis.
Attached the latest log, the error doesn't leave a crash log.
latest.log

This should be fixed now in the latest patch!


The http://blog-learnit.com/Files/powerbi/html web page does not exist for the beginners training

The http://blog-learnit.com/Files/powerbi/html web page does not exist for the PowerBi Beginner Tutorial on YouTube.  An error stating Page not found 404 keeps coming up.
Please can someone help as I will not be able to follow the training exercises without this.

Hello @Hashininirasha thanks for reaching out. Which Youtube video are you referring to? I don't recognize the link, but want to check if this is related to a Youtube video published by our team at Microsoft or if it's someone else that published it. If it's someone else, I am afraid I can't help you.


Bump 'extend' Dependency to 3.0.2

A security vulnerability alert for 'extend' was issued for versions >= 3.0.0, < 3.0.2. The vulnerability allows arbitrary properties to be attached onto the Object prototype. This pull request addresses this by bumping the version number of 'extend' to 3.0.2.

(Shamelessly stolen from @jonschlinkert)

Semver already solves this. Patch the root library once, and all downstream libraries get the patch. Thus, any library that depends on the module will automatically get the patched version by simply reinstalling. If you are not getting the latest version, you are probably using a lockfile that is preventing semver from doing its job.
Don't create issues on dependent libraries when you see a vulnerability message. ALWAYS, AND ONLY create issues on the library that has the vulnerability so that it can be patched. ONLY WHEN AND IF that library has not been fixed in a timely manner does it make sense to create issue on dependent libraries.

Not sure if I agree, but alright.


add optimization under uncertainty showcase

Also updated it from NLopt.jl to Optimization.jl to keep it in the family.

@xtalax we need the fix backported in MethodOfLines or NeuralPDE updated by the end of today to get this building.


docker-proxy seg fault on CentOS 7.5.1804

docker-proxy seg faults causing containers needing the service to fail.
The easiest way to reproduce is to use ldd docker-proxy:
$ ldd /var/lib/snapd/snap/microk8s/237/usr/bin/docker-proxy
/usr/bin/ldd: line 116:  3529 Segmentation fault      LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$@"

Other binaries in usr/bin do not seg fault on ldd.
inspection-report-20181026_152226.tar.gz

I forgot to mention I have a Vagrant box exhibiting the issue: https://app.vagrantup.com/double16/boxes/linux-dev-workstation/versions/201810.1 . Warning: it's 6.29G.


Support for Firebird CHAR(16) CHARACTER SET OCTETS / UUID

Firebird has basic support for UUID fields ( CHAR(16) CHARACTER SET OCTETS ) and in editor it should present values like UUID. FlameRobin does that. isql does that. DBeaver has support for binary fields to format as hex strings, but this does not work for Firebird. Field type is not binary but char.
Firebird 2.5 functions to use
gen_uuid() : generate random 16 byte value
uuid_to_char(col) : formats 16 byte value as UUID string presentation
char_to_uuid(str) : converts UUID string presentation to 16 byte(char)
CREATE TABLE TEST (
    ID  CHAR(16) CHARACTER SET OCTETS NOT NULL,
    TEXT VARCHAR(300),
    CONSTRAINT PK_TEST PRIMARY KEY (ID));

INSERT INTO TEST  VALUES (gen_uuid(), 'data1');
INSERT INTO TEST  VALUES (gen_uuid(), 'data2');
INSERT INTO TEST  VALUES (gen_uuid(), 'data3');

Well, Firebird driver drives me crazy every time I'm trying to make anything that isn't supported out of the box.
Anyhow, this will be the first proof-of-concept:


Autodetect QoS

Dear RViz2 developers,
This PR contains a way to determine the topic QoS when subscribing to a topic.
I would appreciate the opinion of @LoyVanBeek and @zmk5, because we were talking about this in this thread and maybe they want to contribute to this PR.
I hope it helps!!
Signed-off-by: Francisco Martín Rico<EMAIL_ADDRESS>

Seems to work!
I tested this briefly from ipython
import rclpy
from rclpy.node import Node
from rclpy.qos import DurabilityPolicy, HistoryPolicy, LivelinessPolicy, HistoryPolicy, QoSProfile, qos_profile_sensor_data
from sensor_msgs.msg import LaserScan

rclpy.init()
node = Node('ipython')
rclpy.spin_once(node, timeout_sec=0.01)
node.create_publisher(LaserScan, 'laser', qos_profile_sensor_data)

weird_qos = QoSProfile(history=HistoryPolicy.KEEP_ALL, durability=DurabilityPolicy.TRANSIENT_LOCAL)

node.create_publisher(LaserScan, 'weird_laser', weird_qos)
rclpy.spin_once(node, timeout_sec=0.01)

and indeed the weird QoS settings are automatically set in RViz :+1: :+1:

Dear @ivanpauno @clalancette
Any comment about this PR? Do you think it is useful/valid? Any improvement that you want I do.
Thanks!!


Player can still play after round over

A second winning condition can be met if the player fills the board fast enough. This allows for 2 points per round, instead of 1.

Thanks, fixed!


pdb_cluster_zip: Docs accepts pdb output but it is not supported

Documentation indicates "pdb" or "zip" formats accepted for the output, but only zip is accepted.

Removed  "pdb output" option from the documentation (docstrings, json schemas)


[meta] 6.45 content planning

variant dungeon: @quisquous
criterion dungeon:
criterion savage dungeon:
carnivale stage 32:
I'll take the variant dungeon, as I'm planning on poking at all the routes and it's not urgent.
I am also planning on doing the criterion dungeon blind this time since I don't get to do much blind content in ffxiv.  (Scheduling-wise it might be a little bit before I get there too.) I don't know if anybody else wants to volunteer to review any of these PRs in my place so I don't have to look at them? otherwise I'll just merge them and trust the authors to fix any issues as they come up.
blu eden raids have gotten a first pass from @xiashtra (thank you). I'm not sure if strats without roles need more info (e.g. advanced relativity telling you who your partner is and not just who double winds are), but we can fix that up as we go.

I'll work on 32 I've just been busy this week.

I'm a little busy irl right now, and not sure when I'll have time to dig into the criterion dungeon.  But if no one has started dropping stuff for it by next week, I'll try to at least get started on it.

I'm a little busy irl right now, and not sure when I'll have time to dig into the criterion dungeon. But if no one has started dropping stuff for it by next week, I'll try to at least get started on it.

Pretty much the same for me.

This is done other than #5718, which I'll land ... next week maybe I hope


Treat the first endpoint for each scheme as default

The idea is that all non-default endpoints should get a target port allocate in the manifest. Only the default gets it omitted.
Fixes #3786.
Microsoft Reviewers: Open in CodeFlow

There's a regression here, we only want this logic for http and https schemed endpoints.


changelog for v0.20.8

Description of changes:
This is a manual cherry-pick of #8890.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.21

/approve

/lgtm


Create MakeFlow for GATK

btw, any file system based pipeline should use atomic file
creation to ensure that incomplete results don't get mistake for
completed ones.
Extremely simple and makes a huge difference.

Created: https://github.com/jvivian/10k_exome_project/blob/master/Code/MakeFlow_Tests/Makeflow
Since the provided EC2 support for things like Work_Queue don't seem to work anymore, we could use MakeFlow but we'd have to write our own python wrapper to orchestrate the WQ system's "workers" with spot priced instances.   MakeFlow keeps a log of what things succeeded so resumability is actually pretty great (and could include things like downloading, uploading to S3), but that means the MakeFlow file would have to originate from the Master which means either generating a MakeFlow file for all 10k pairs, or have one MakeFlow file that runs 10k jobs (seems a bit insane).


Copy binaries to final container in single step.

This eliminates three intermediate layers, which is nice for rootless systems using the VFS storage driver.
Multiple COPY reference: https://docs.docker.com/engine/reference/builder/#copy

Thanks, didn't know COPY supported that.


Need to make sure that Sprite Importer uses CPS

Sprite import ignored 3 CPS setting for sprites but sprite builder used the limitation so it wasn't able to match up correctly.
This sprite has too many colors (4 vs 3).

This is fixed.


Spelling mistake

Type: Bug
In the Terminal menu there is a spelling error. Where you type "Rreiniciar..." you should type "Reiniciar tarea en ejecución..."
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:41:37.860Z)
OS version: Linux x64 6.5.0-18-generic
Modes:

a screenshot would help


All copilot always steps are shown in the top left corner of the screen. [bug]

Hi! I  just cloned your copilot example app and all steps always are shown in the top left corner of the screen.
No changes in your code were done.

It should be fixed in 3c23125. Could you please try again?


Added request attribute annotation.

Hey guys!
I saw following request on the slice-users list, and decided to implement it: http://slice-users.2340343.n4.nabble.com/Pass-Parameters-from-Sightly-to-Slice-td66.html
I have added a new annotation, @RequestAttribute, where you can inject a request attribute into a slice resource. This can then be used in the following way:
data-sly-use=${'com.cognifide.slice.TestModel' @ myAttribute='aValue'}
@SliceResource
public class TestModel {

    @RequestAttribute
    private String myAttribute;

    public String getMyAttribute() {
        return myAttribute;
    }

}

What do you guys think?

Coverage decreased (-1.0%) to 65.98% when pulling d9b165d70ccb213100f752a7dbf4b76c61ed27a4 on royteeuwen:feature/injectable-request-attribute into 382453cdaee33417a7cdf2a0eaee13ea6b2091fa on Cognifide:master.

Have to see to add some tests maybe

Did this change make it into the codebase via another means, or is it still waiting merge? I tried to use this approach today (albeit with the Sling RequestAttibute annotation) on a project using Slice 4.3.2 but without joy. If it's in a newer version I can try updating to use it.

Never found the time to fix the remarks to be honest, so it isnt in the main branch no. You are welcome to fix the remarks and get it merged, its as good as finished

Hey @royteeuwen thanks for the speedy reply. This is tempting, I might give it a go.
But...
Log update aside, this looks dead. It's not seen an update for three years now. @mmajchrzak is this project still alive, or is it now hosted and updated elsewhere?

Hey @antonyh, we definitly still use this project and even updated to aem 6.5 with java 11. There is a slice 4.5 release that supports this, but the docs havent been updated.
I also find Slice pretty feature-complete, we dont need an entire new Spring, thats what the other bundles from AEM are for.
But on the other hand is Sling Models probably the way to go if you would start from scratch for a new project, because it is OOTB included

Quite agree, Sling Models is superior, but legacy code needs to be maintained and enhanced. As an aside, I found a way to achieve my objective without needing to use @RequestAttribute this time.

Hi @antonyh. This project has been put into "maintenance mode". We support it (and as @royteeuwen said there was even a release to make it java 11 compatible) but we've stopped actively add new things. The top reason for this is that it's hard to compete with SlingModels as it comes OOTB and does most of what Slice can do. Imo SlingModels still lacks decent dependency injection but its custom one is good enough for simple models and simple business logic. And to be fair, a need for robust DI in AEM is diminished every year as things are moved outside of AEM into middle layers or front.


How to measure the size of the Voxblox mesh map built?

As the question suggests, I am trying to measure the size of the Voxblox mesh that has been built so that I can calculate the amount of area that has been explored by the UAV.
Any idea on how to implement this?

It really depends what you mean by area and which representation you are using.
The easiest to calculate would be the viewed surface area, which would be as simple as iterating through the triangles and summing their area.
Another possibility would be to calculate the explored volume. If you are using the ply mesh output however this information has been lost. If you use the Mesh.msg a pretty good approximation to this can be given by the number of blocks with unique indexes multiplied by the volume of each block. However this is more easily done by counting blocks allocated in the actual voxblox map.
If you want 2D area, you can do the same as above but only consider the x and y component of the block when deciding if it is unique.


Signup/signin flow

I'm getting HTTP errors in the console when signing up/signing in

It would be helpful if you could provide a screenshot of the errors, also, are you trying to use it on vercel bc that won’t work? You need to run the front and backend manually

I know there were console errors occurring when there was an issue with signin/signup, but I couldn't find a way to fully remove them, only changing the form of the popup to a more user friendly toast instead of the automatically generated error popup


Explain use of never[] as most generic function argument

For newbies like me that read the manual start-to-end to get an introduction into the concepts, the appearance of never[] here is surprising, inexplicable and confusing. So, I was very happy about the thorough explanation linked in this commit.

Ping - anybody out there?

@andrewbranch Is this of interest?


TypeError: plugins.filter is not a function

Trying to use this example: https://react-page.github.io/docs/#/builtin_plugins?id=react-pageplugins-spacer
Made 2 changes:

Set initial state as null as per #869
prop plugins renamed to cellPlugins

Error:

sorry, there is a typo, its cellPlugins not plugins. Your IDE might warn you about that

Yup, you can see I've done that already:

Made 2 changes:

Set initial state as null as per #869
prop plugins renamed to cellPlugins

the docs used an outdated example. i removed that for the time beeing


Citation annotation offset outside passage

Hey @creisle , I've come across a citation annotation that is outside the associated passage. One of my scripts checks some things on BioC files and this got flagged. I think that it doesn't seem right. What do you think?
Below is an example where the passage offset is 56733 but the zero-length citation is at offset 56732 which is just before the passage starts.
    <passage>
      <infon key="section">floating</infon>
      <infon key="subsection">None</infon>
      <infon key="xml_path">floats-group/table-wrap/table/thead</infon>
      <offset>56733</offset>
      <text> (µg/mL)    S-2366 K M (mM) V MAX (mAU/min)</text>
      <annotation id="ANN_c6f8f533-0764-4484-8663-c18655ca06f3">
        <infon key="citation_text">1</infon>
        <infon key="type">citation</infon>
        <location offset="56732" length="0"/>
        <text/>
      </annotation>
    </passage>

To reproduce, I've included the source PMC XML file: PMC8466798.xml.gz and I converted it with the line below.
python src/convert.py --i PMC008xxxxxx/PMC8466798.xml --iFormat pmcxml --o test.bioc.xml --oFormat biocxml

Sorry for the long delay, this completely fell off my radar. I've been debugging this and it looks like the reason this happens is a case where the citation is the first thing in a passage. Now since we remove the in-text citation and attribute it to the text that precedes it this ends up putting the annotation in the wrong passage. Should be an easy fix but first I'd like to see why those passages are being split. Seems like maybe they shouldn't be

Ok this one is really weird.... the citation is actually in a strange position in the original text. Would it make sense to append it to the previous passage after the table description or should we just be adjusting the position so the reference is the start of the table header passage?

Wow, what a weird one. Some bug in the publishers' code to convert to PMC XML. It's probably just better to work with the data that we've got instead of trying fixes that may sometimes work. So I guess insert it into the table header? What'd you think?

ya, that's probably the simplest solution


Refactored ConDir to car_dir

See #129

Following naming convention can it be refactored to cardir?

Yeah that's fine, I'll do it tomorrow :+1:

Yes didn't see you had it updated... I see now the commit... Either assign it to me, or better now we use appropriate tags.

Check my pull request on your repo/branch. Got no conflicts when merged master so not sure why it complains here.
If my PR is fine and merged which will auto-update here, change the tag to "ready for review" and assign it to me.

@yianni This needs testing, but should be alright to merge now :)

I ll have a look tomorrow, but unit tests should be sufficient for this.

Checks pass. Looks alright to me.


Troubleshooting installation steps.

Some of the errors observed during installation and compilation of NNTrainer, and their working solutions.

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #689. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/689-202011030228050.99103808403015-ee3b61fd144b9f783bfadaae7fe8c18af3c47df7/report/misspelling_result.txt.

To contributor, We have used 'Signed-off-by:' notation by default to handle the license issues, that result from contributors. Note that 'Is there a Signed-off-by line?' is important because lawyers tell us we must have to it to cleanly maintain the open-source license issues even though it has nothing to do with the code itself.

:octocat: cibot: @nnstreamer, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

@meteozay Thanks for the PR.
I request you to please sign the commit and add a commit message body to pass the CI errors.

Fixing commit errors.

Deleting troubleshooting branch.

please fork the repository and make a branch from the forked repository :)


Fix initialization of Rails logger

@matthewd Please review
cc @himdel

:+1: works for me :) (also cc @mzazrivec)
Thanks!


Adapt imports for flutter_quill>3.4.4

flutter_quill just updated to 4.0.0, so I think we should change flutter_quill: ^3.0.0 => flutter_quill: ^4.0.0

flutter_quill just updated to 4.0.0, so I think we should change flutter_quill: ^3.0.0 => flutter_quill: ^4.0.0

flutter_quill 4 requires flutter 2.10. I'm not sure delta_markdown has been tested against this flutter version

flutter_quill just updated to 4.0.0, so I think we should change flutter_quill: ^3.0.0 => flutter_quill: ^4.0.0

flutter_quill 4 requires flutter 2.10. I'm not sure delta_markdown has been tested against this flutter version

is there any progress or plans in testing for flutter 2.10? atm our project which is using your package is stuck at 2.5.2 since we can't update quill due to this package and for flutter 2.10 we need a new quill version.

flutter_quill just updated to 4.0.0, so I think we should change flutter_quill: ^3.0.0 => flutter_quill: ^4.0.0

flutter_quill 4 requires flutter 2.10. I'm not sure delta_markdown has been tested against this flutter version

is there any progress or plans in testing for flutter 2.10? atm our project which is using your package is stuck at 2.5.2 since we can't update quill due to this package and for flutter 2.10 we need a new quill version.

What I did was to create a branch on my fork in which I have as dependency flutter_quill ^4.0.0 and I use it as:
  delta_markdown:
    git:
      url: git://github.com/devtud/delta_markdown.git
      ref: flutter_quill_4

You can do the same until delta_markdown will officially push a version compatible with flutter_quill 4.

flutter_quill just updated to 4.0.0, so I think we should change flutter_quill: ^3.0.0 => flutter_quill: ^4.0.0

flutter_quill 4 requires flutter 2.10. I'm not sure delta_markdown has been tested against this flutter version

is there any progress or plans in testing for flutter 2.10? atm our project which is using your package is stuck at 2.5.2 since we can't update quill due to this package and for flutter 2.10 we need a new quill version.

What I did was to create a branch on my fork in which I have as dependency flutter_quill ^4.0.0 and I use it as:
  delta_markdown:
    git:
      url: git://github.com/devtud/delta_markdown.git
      ref: flutter_quill_4

You can do the same until delta_markdown will officially push a version compatible with flutter_quill 4.

Ok thx for the tip
For us the issue is, we already make quite a stretch by using a not production ready package for our project and if we than have to rely on a fork somewhere the situation doesn't get better :)
Hopefully an official version compatible with flutter_quill 4 will follow soon :)

Is there any update on this issue?


Switching from compact overlay to full screen doesn't change the layout

Describe the bug
Windows provides a universal shortcut for full screen in all CoreWindow based apps: Windows+Shift+Enter. I've noticed that in Calculator when you invoke that hotkey while being in compact overlay, the layout doesn't get changed to the normal layout.
Steps To Reproduce

Expected behavior
When you full screen it from compact overlay, it should go back to the normal layout.
Capture
Here's a recording showcasing the issue.

Device and Application Information

OS Build: 10.0.21390.0
Architecture: x64
Application Version: 10.2103.8.0
Region: en-US
Dev Version Installed: False

Requested Assignment

If possible, I would like to fix this.

I guess it switches the layout when you click the compact overlay button but ideally it should handle the SizeChanged event, check if it's still in compact overlay and switch the layout if necessary. It will also work for full screen.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Good find! This appears to be a bug with system behavior (I can reproduce this issue with other apps that support CompactOverlay). I am going to close this issue here, but route it to the right internal team to address this at the system level.


cmd/link: misc/cgo/testshared fail on ARM64

What version of Go are you using (go version)?
tip +bba1ac4
What operating system and processor architecture are you using (go env)?
linux/arm64
##### ../misc/cgo/testshared
2016/10/27 20:49:17 executing go install -installsuffix=8674665223082153551 -buildmode=shared runtime sync/atomic failed exit status 2:
# /tmp/go-build461932225/libruntime,sync-atomic.so
/home/cherry/src/go/pkg/tool/linux_arm64/link: running gcc failed: exit status 1
/usr/bin/ld.gold: error: /tmp/go-link-711780168/go.o: unsupported reloc 311 against local symbol
/usr/bin/ld.gold: error: /tmp/go-link-711780168/go.o: unsupported reloc 312 against local symbol
/usr/bin/ld.gold: internal error in relocate, at ../../gold/aarch64.cc:5651
collect2: error: ld returned 1 exit status

It wasn't broken yesterday when I tested my CL 32180 locally. So, I think it is probably somewhere between 829aa67 and bba1ac4.

I think it is probably somewhere between 89632aa and bba1ac4.
I was wrong. 89632aa is today. The commit I tested yesterday was 829aa67.

I presume this is 8b07ec20f7a971edce9eaf413b20e453c50858c6. Where has the arm64 builder gone? :(

Although that worked when backported to 1.7 on Ubuntu zesty: https://launchpadlibrarian.net/291097700/buildlog_ubuntu-zesty-arm64.golang-1.7_1.7.3-1ubuntu2_BUILDING.txt.gz -- which version of gold do you have installed?

Where has the arm64 builder gone? :(

I am wondering it, too.

which version of gold do you have installed?

$ gold --version
GNU gold (GNU Binutils for Debian 2.25) 1.11
Copyright (C) 2014 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

Looks like this was fixed in October 2015 (https://sourceware.org/bugzilla/show_bug.cgi?id=19042) which I think means binutils 2.26.
I'm a bit confused as to how this is happening. Can you confirm that it really is the commit I mentioned that causes the problem? (I don't have easy access to an arm64 system with a sufficiently old version of gold installed).

Thank you for investigation. Yes, it is indeed that commit. I tested it and one commit before to confirm.
So, the problem seems that my gold linker is too old? Are we going to require a newer version? At the least we should document it, though I'm not sure where.

Well there is something strange going on in that we really shouldn't be accessing a local symbol via the GOT. Can you see if https://github.com/mwhudson/go/commit/f30efbdea5849ab467768dc7459954e6a42b3067 helps?

This indeed works. Thank you! (I have not tested on other architectures though.)


novatel_oem7_driver: 1.1.0-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository novatel_oem7_driver to 1.1.0-1:

upstream repository: https://github.com/novatel/novatel_oem7_driver.git
release repository: https://github.com/novatel-gbp/novatel_oem7_driver-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.9.3
previous version for package: 1.0.0-1

Fixed broken binary builds.


Fix go version and kubectl install command

Description of changes:

Changes Go v1.21 to v1.21.0
Fix the step installing kubectl in integration image
Push new image tags and regenerates jobs.yaml

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

I need to build and push the images
/hold

/unhold

Please follow up so we can unpin Go binary patch version. But works for me, for now.
/lgtm


Roll back problematic pod labeling feature

What type of PR is this?
/kind cleanup
/kind feature
What this PR does / why we need it:
Some time ago I introduced a feature for the SPO to label denials for
pods. While this seemed like a good idea at the time, it introduces too
much privileges for te SPOd (update and patch all pods).
While there hasn't been any security incidents reported for the SPOd,
the drawbacks of giving such privileges are more critical than the
features the labeling would have enabled. So, let's get rid of this
feature and revisit the problem another time.
This fully removes the flag as there is no documented usage of the feature.
Which issue(s) this PR fixes:
None
Does this PR have test?
The test was removed.
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Pod denials labeling feature was removed.

Codecov Report

Merging #1088 (300b5b8) into main (e259f4f) will increase coverage by 0.51%.
The diff coverage is 100.00%.

:exclamation: Current head 300b5b8 differs from pull request most recent head ea9e50a. Consider uploading reports for the commit ea9e50a to get more accurate results

@@            Coverage Diff             @@
##             main    #1088      +/-   ##
==========================================
+ Coverage   50.13%   50.65%   +0.51%
==========================================
  Files          42       42
  Lines        4789     4740      -49
==========================================
  Hits         2401     2401
+ Misses       2309     2262      -47
+ Partials       79       77       -2

/test pull-security-profiles-operator-test-e2e

/retest

So I'm fine removing this functionality (AFAIK nothing and nobody uses it now), but I'd like to discuss alternatives, because I think it's something users will ask for.
The use-case I care about the most is:

a developer records an initial policy in CI
an SRE deploys the app and the policy. Both acknowledge that the initial policy version is not 100% correct and want to find out AVCs/seccomp denials
so far I was thinking about adding a "permissive" flag to be added to the profiles which would change the defaultAction to SCMP_ACT_LOG for seccomp profiles and inherit from typepermissive process for SELinux policies.
this would produce logs, then the question is how to gather them and there we'd probably do what your approach did, but maybe label the profiles instead of the workloads? I think this would be more palatable from the RBAC perspective. Maybe we could issue events, too, not sure what would be best for SREs in the end.

@jhrozek I was actually thinking about doing events instead. But struggled to introduce them without adding a lot of extra complexity to the code-base. We might need to do some refactoring.

@jhrozek I was actually thinking about doing events instead. But struggled to introduce them without adding a lot of extra complexity to the code-base. We might need to do some refactoring.

Let's file an issue, then

/retest


FAT-203

Test plan for mod-template-engine added

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


Allow hiding fields by configuration

Would you accept a pull request for configuring the fields shown on checkout via store config or do you strongly recommend to fork and customize for the use case instead?

CC @kolaente

Hi, create PR, I will check how it looks :)

PR is up: #19

@kolaente I was thinking a little bit about this PR and I decided to not merge it.
The reason is that this module is still rather an example of how to create custom checkout form using UI component and how to change it or extend, instead of using plugin on LayoutProcessor.
I have a plan to build a different module which allow you to customize checkout.
https://github.com/sbodak/magento2-checkout-builder
Currently, I've released a 1.2 tag which has a few fixes for displaying form in expecting place, after shipping address and it's tested in Magento 2.3.
thanks for your work

Hm what a pity ...
So we have to keep up our fork for a while.
Would be cool if you could create some tickets for the planned feature of the checkout builder in the other repo, maybe we can participate a bit in the development.


Vickel: Watch Wallshield[\W_]+Cyber[\W_]+Security[\W_]*+Service

Vickel requests the watch of the watch_keyword Wallshield[\W_]*+Cyber[\W_]*+Security[\W_]*+Service. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Wallshield[\W_]*+Cyber[\W_]*+Security[\W_]*+Service has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


ensure Scalar::from_repr is always Some

seems like doing this without breaking constant time approach is not trivial


Define policy for compiler upgrades on our machines

At present we have an ad-hoc mechanism for determining when to perform compiler upgrades. the process is now reasonably well defined (although documentation needs to be collated) but we should also have a policy of checking for critical security upgrades and determining when to perform upgrades for upcoming OpenJDK releases and/or updating the compilers for old machines and verifying that they get deployed in a timely manner.

To anyone picking this up - it might be useful to understand what other providers are doing in terms of compiler versions for each platform.

It would be great if there was a trail of documentation. Which JDK uses which compiler/os version etc.

It would be great if there was a trail of documentation. Which JDK uses which compiler/os version etc.

Yeah totally agree. At the moment that's all in the https://github.com/adoptium/temurin-build/tree/master/build-farm/platform-specific-configurations scripts but making that more visible would be a very useful thing to do alongside this.

@andrew-m-leonard Would be good to have your input on this, especially in light of the number of outstanding issues mentioned in the previous comment. I know we also spoke about getting JDK <20 moved to building on the Windows Server 2022 machines - I don't think I've seen that change so is that still feasible or are we too late to make that happen now for the April cycle?

@sxa I think with only 1 week to go, i'd rather stabilize on what we currently have, unless there's a particular reason to move for this release?

@sxa I think with only 1 week to go, i'd rather stabilize on what we currently have, unless there's a particular reason to move for this release?

OK but we do need to try and get some attention on this post-release - most of the issues above haven't seen much action and we need to ensure we remain as current as practical and consistent with what the upstream project supports.

I've put together a first draft at an actual policy that we can follow for future releases. Let me know your thoughts and once we've made any edits we can take it to the PMC:
Policy for Compiler Upgrades on Adoptium Build Machines
1. Objective
The objective of this policy is to establish a systematic and efficient approach to upgrading compilers on Adoptium build machines. This policy aims to ensure timely updates, reduce security risks, maintain compatibility with OpenJDK releases, and enhance overall system performance.
2. Scope
This policy applies to all compilers utilised on Adoptium build machines, including but not limited to compilers and any other tools or utilities that contribute to the build process.
3. Compiler Upgrade Policy
3.1. Security Updates
The infrastructure/security team will continuously monitor relevant sources, for critical security updates. In the case of any critical security update, the team will:

Assess the potential impact on Adoptium build machines.
Prioritise the update and develop a timeline for deployment.
Notify the relevant parties and coordinate with them to upgrade the compilers with minimal disruption.

3.2. OpenJDK Releases
To maintain compatibility with OpenJDK releases, the team will:

Closely track the OpenJDK release cycle and compiler version requirements.
Test compatibility with new compiler versions in a staging environment before deployment.
Schedule and perform compiler upgrades in sync with OpenJDK releases, ensuring minimal impact on ongoing projects.
Review compiler levels each time a new major release of OpenJDK is added to the CI system.

3.3. Compiler Upgrades for Old Machines
For older build machines, the team will:

Regularly evaluate compiler performance and compatibility with current build requirements.
Identify any build machines that require compiler updates and prioritise them accordingly.
Develop an upgrade plan and coordinate with the relevant parties for deployment.

4. Upgrade Process
4.1. Notification
The team will notify all relevant stakeholders about the planned compiler upgrade, including the expected timeframe, potential impact, and any required actions on their part.
4.2. Testing
Before deploying compiler updates on production machines, the team will:

Test the updates in a controlled staging environment to ensure compatibility and performance.
Identify and resolve any issues or conflicts that may arise during the upgrade process.

4.3. Deployment
The infrastructure team will coordinate the deployment of compiler upgrades on the build machines, ensuring minimal disruption to Adoptium projects.
4.4. Documentation
The team will maintain detailed documentation for each upgrade, including the reason for the upgrade, the new compiler version, and any issues encountered and resolved during the process. This documentation will be readily accessible for future reference and audits.
5. Monitoring and Review
The team will continuously monitor the performance and stability of the updated compilers on the build machines. They will also review this policy annually or as needed to ensure its effectiveness and relevance.

All fairly standard stuff so fundamentally no objections to using that as a policy, although we still need to decide the details of 3.2 in terms of when we choose to update (outside critical security updates)
For example, in the latest docs it says "The minimum accepted version of gcc is 5.0. Older versions will generate a warning by configure and are unlikely to work. The JDK is currently known to be able to compile with at least version 11.2 of gcc. In general, any version between these two should be usable."
Should we aim to be tracking Oracle's (which is the 11.2 that it's "known" to compile with)?
I'll note that we should typically be able to handle 3.2 by regular ansible updates putting the newer versions on, but that's not the case at present. And I'll also note that all of this is applicable to the levels of boot JDK which we have installed on the machines.
We could add reproducibility testing to 4.2 as well (It is unlikely to be reproducible pre and post upgrade, but verifying that it's the same for two builds of the updated compiler would make sense.
Initially for 4.4 we can probably cover that with a relevant GitHub issue for the update.

All good feedback @sxa. How about this?
Policy for Compiler Upgrades on Adoptium Build Machines
1. Objective
The objective of this policy is to establish a systematic and efficient approach to upgrading compilers on Adoptium build machines. This policy aims to ensure timely updates, reduce security risks, maintain compatibility with OpenJDK releases, and enhance overall system performance.
2. Scope
This policy applies to all compilers utilised on Adoptium build machines, including any other tools or utilities that contribute to the build process.
3. Compiler Upgrade Policy
3.1. Security Updates
The infrastructure/security team will continuously monitor relevant sources, for critical security updates. In the case of any critical security update, the team will:

Assess the potential impact on Adoptium build machines.
Prioritise the update and develop a timeline for deployment.
Notify the relevant parties and coordinate with them to upgrade the compilers with minimal disruption.

3.2. OpenJDK Releases
To maintain compatibility with OpenJDK releases, the team will:

Track the OpenJDK release cycle and compiler version requirements, aiming to track Oracle's version of gcc (11.2).
Test compatibility with new compiler versions in a staging environment before deployment.
Schedule and perform compiler upgrades in sync with OpenJDK releases, ensuring minimal impact on ongoing projects.
Review compiler levels each time a new major release of OpenJDK is added to the CI system.
Regularly evaluate the levels of boot JDK installed on the machines and prioritize their upgrades accordingly.

3.3. Compiler Upgrades for Old Machines
For older build machines, the team will:

Regularly evaluate compiler performance and compatibility with current build requirements.
Identify any build machines that require compiler updates and prioritize them accordingly.
Develop an upgrade plan and coordinate with the relevant parties for deployment.

4. Upgrade Process
4.1. Notification
The team will notify all relevant stakeholders about the planned compiler upgrade, including the expected timeframe, potential impact, and any required actions on their part.
4.2. Testing
Before deploying compiler updates on production machines, the team will:

Test the updates in a controlled staging environment to ensure compatibility, performance, and reproducibility.
Identify and resolve any issues or conflicts that may arise during the upgrade process.

4.3. Deployment
The infrastructure team will coordinate the deployment of compiler upgrades on the build machines, ensuring minimal disruption to Adoptium projects.
4.4. Documentation
The team will maintain detailed documentation for each upgrade, including the reason for the upgrade, the new compiler version, and any issues encountered and resolved during the process. This documentation will be readily accessible for future reference and audits, and can be recorded in relevant GitHub issues.
5. Monitoring and Review
The team will continuously monitor the performance and stability of the updated compilers on the build machines. They will also review this policy annually or as needed to ensure its effectiveness and relevance.

FYI @fredg02 :)

Only comment is that I don't know if we need 3.2 and 3.3 to be separate - 3.2 has "Schedule and perform compiler upgrades" and that should always be applied to all existing or future machines to ensure they are consistent.
Otherwise I'm happy with this.

Agreed! how about this @sxa:
Policy for Compiler Upgrades on Adoptium Build Machines
1. Objective
The objective of this policy is to establish a systematic and efficient approach to upgrading compilers on Adoptium build machines. This policy aims to ensure timely updates, reduce security risks, maintain compatibility with OpenJDK releases, and enhance overall system performance.
2. Scope
This policy applies to all compilers utilised on Adoptium build machines, including any other tools or utilities that contribute to the build process.
3. Compiler Upgrade Policy
3.1. Security Updates
The infrastructure/security team will continuously monitor relevant sources, for critical security updates. In the case of any critical security update, the team will:

Assess the potential impact on Adoptium build machines.
Prioritise the update and develop a timeline for deployment.
Notify the relevant parties and coordinate with them to upgrade the compilers with minimal disruption.

3.2. OpenJDK Releases
To maintain compatibility with OpenJDK releases and ensure consistency across all machines, the team will:

Track the OpenJDK release cycle and compiler version requirements, aiming to follow Oracle's version of gcc (11.2).
Test compatibility with new compiler versions in a staging environment before deployment.
Schedule and perform compiler upgrades in sync with OpenJDK releases, ensuring minimal impact on ongoing projects.
Review compiler levels each time a new major release of OpenJDK is added to the CI system.
Regularly evaluate the levels of boot JDK installed on the machines and prioritize their upgrades accordingly.

Additionally, for older build machines, the team will:

Regularly evaluate compiler performance and compatibility with current build requirements.
Identify any build machines that require compiler updates and prioritize them accordingly.
Develop an upgrade plan and coordinate with the relevant parties for deployment.

4. Upgrade Process
4.1. Notification
The team will notify all relevant stakeholders about the planned compiler upgrade, including the expected timeframe, potential impact, and any required actions on their part.
4.2. Testing
Before deploying compiler updates on production machines, the team will:

Test the updates in a controlled staging environment to ensure compatibility, performance, and reproducibility.
Identify and resolve any issues or conflicts that may arise during the upgrade process.

4.3. Deployment
The infrastructure team will coordinate the deployment of compiler upgrades on the build machines, ensuring minimal disruption to Adoptium projects.
4.4. Documentation
The team will maintain detailed documentation for each upgrade, including the reason for the upgrade, the new compiler version, and any issues encountered and resolved during the process. This documentation will be readily accessible for future reference and audits, and can be recorded in relevant GitHub issues.
5. Monitoring and Review
The team will continuously monitor the performance and stability of the updated compilers on the build machines. They will also review this policy annually or as needed to ensure its effectiveness and relevance.

In the absence of further comments I'm going to consider this closed and it can be revised as and when required.


docs: Drafted Software Distribution Hub

Created dedicated section (README.md, tenants.md, release-hub.md)
Created an entry in SUMMARY.md
Showed tenants as a prerequisite to releasehub-related actions
Added Enterprise tagging
Added visuals (snapshots, gifs, videos)
Explained the purpose in README.md (Why and when and who)
Gave examples wherever necessary for the user-input fields
Explained rescind and on-hold actions in Extras
Showed Partial Release and Full Release in Extras
Included RBAC (super-admin as of now)

I'm not sure if this is planned in next phase but few missing stuff:

How release stages dependency is goverened?
Talk about unmapped environment
Release notes and catalog of tenant and releases
Defining applications at release track (Guessing this will be in next phase of doc)
RBAC for deploying with release is not superadmin anymore (Guessing this will be in next phase of doc)
Release track Dashboard (Guessing this will be in next phase of doc)

Need to discuss with you
Need to discuss with you
Added 👍
Hmm. Didn't get it.
Updated 👍
Need to discuss with you


hardikparwana/cuda12-ubuntu22

IMAGE SYNC

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


JavaScript API and configuration

We've heard feedback that the wrangler.toml configuration is not the most intuitive format. TOML is uncommon among tools in the JavaScript ecosystem, unlike Rust, so much so that there's a challenge to find a well-maintained library to edit it. We still want to support the wrangler.toml, but we're also considering another configuration format for improvements we're planning in 2.x, such as:

Support for multiple Workers in the same configuration.
A plugin/extension system.
A programmatic API.

A JavaScript (and TypeScript) configuration would accomplish these goals and is similar to tried-and-trusted tools like esbuild, jest, webpack, rollup, also Miniflare, etc. (links go to configuration docs)
A new configuration would also make it easier to introduce breaking-changes from 1.x to 2.x. If a wrangler.toml is detected, defaults from 1.x are used; otherwise, the 2.x defaults are used. While these differences would need to be prominently documented, it allows new features such as Service environments and bindings to be introduced.
Here's an example of what the API/configuration could look like. (this is just for demonstration)
// worker.config.js

import { uploadWorker, previewWorker } from "wrangler";

await uploadWorker({
  name: "auth-service",
  environment: "production",
  entryPoint: "./worker.js"
});

import { readFile } from "node:fs"

const server = await previewWorker({
  compatibilityDate: "2020-11-01",
  variables: {
    "MY_VAR": "..."
  },
  entryContent: readFile("./worker.js"),
});
server.listen(8787);

Small thoughts:

Why import instead of default export? This makes it easier for IDEs to pickup the types of the config.
An API allows developers to use wrangler to create other tools, like a unit-testing runner.
What about CLI arguments? Yes, there would be a corresponding CLI arguments for each JavaScript API.

Thanks for kicking off this discussion @Electroid. IMO I think it would be wise to make a decision on this before Wrangler 2.0.0 general release. A few thoughts...

It feels like the suggested configuration is actually conflating two separate concepts: configuration and programmable API. While I think it is valuable to have both, I think they should be considered separately.
I suspect that you are taking the lead from esbuild here, where there are only two options for "configuration":
a. Use the esbuild command line binary - in this case the only way to configure the build is via command line options
b. Write a script that uses the esbuld API to execute a build - in this case all the configuration is done within this script programmatically.
This sort of approach does allow for highly customisable behaviour, but for anything non-trivial, it requires that developers do write such a script and run it directly. I think this goes against the approach we have taken with Wrangler which is more like an interactive development tool.
I think that creating an API is a very good idea, especially to support other usages from outside the Wrangler CLI, such as a VS Code plugin. But consider how one would configure a project to be able to accessed from the command line and VS Code? I think having an executable script in this case would be what we want?
While an imperative programmable script provides the most flexibility, it is also the most difficult to automate updates.
We have already talked about automated migrations between versions, but also UI based tooling, such as a VS Code plugin, would want to be able to update the configuration - I envisage adding and removing environments/bindings for a Worker/Service.

So my preference would be to align more with the TypeScript tooling approach:

provide a programmatic API that can be used to create complex use-cases such as plugins
provide a declarative (expandable?) configuration syntax with APIs for modifying this - I would still suggest JSONC (or perhaps something YAML related) which is well understood by JS developers and has well supported tooling
ensure that (almost?) all configuration options can be overridden at the command line

this is being tracked in https://github.com/cloudflare/wrangler2/issues/1185, closing this out


Auto-updater fixes

I ended up downloading Windows 10 for use in a VM. With these changes, the auto-updater actually works.


Question on estimation

Hi Junior,
Just a simple question. I've seen that in the example files (Prof. Tau zha tutorials) there is an implementation using the parallel computing toolbox to estimate various models simultaneously. My question is, does RISE have a form to do the parallel computation in the estimation process just for one model (to do more efficient the procedure)?
Many thanks in advance.
Leonard A.

Hi Leo,
I am so sorry this issue fell through the cracks...
At the moment we do not have a parallelization set for the estimation of
one single model. Note however that the user can, if they wish, easily use
their own optimization algorithm instead of the ones used in RISE.
Cheers,
Junior

Thanks for your response, Junior!
regards,
Leonard.


Add info about stable destination ActorPaths

It could additionally mentioned that the actor must actually exist, therfore it must not be a lazy val. Perhaps an example in the line of "instead of this do this" would be helpful?

I just checked the current documentation on reliable delivery: it uses a destination: ActorPath and does not show the side that passes this ActorPath to the ExampleActor. Then it would make sense to add this side to the example as well, so that the comment regarding the lazy actor does not cause confusion.

@magro In the documentation ConfirmedDelivery is mentioned as a tool in context of remote communication, so you can never be sure if the destination actor actually exists (or is able to receive the message). That is why you should invoke redeliverUnconfirmed on a regular basis (as shown in the example).

Right, makes sense. So I also don't see the need for further adjustments.

LGTM


Bump version to 0.11.0

Summary by CodeRabbit

New Features

Version 0.11.0 officially released, introducing a ball tree data structure for improved nearest neighbor searches.

Documentation

CHANGELOG updated to reflect the new version release and changes made in version 0.11.0.

Chores

Version number updated in package configuration to signify the new release.

Please don't forget to update the CHANGELOG to reflect the ndarray version bump, since this crate's public API exposes ndarray types.


Log requests and responses in tests

Is the main intent of this PR to provide us with more info to debug flaky tests?

Yes, it is the goal :)

Is there a way to validate the new code? Perhaps having a test that sends out a request we know will fail and then asserting data that was logged in the process?

I've tested the code manually by making a test fails. I'm not sure we can test the content of TestContext.WriteLine.


Istio 0.5.1 Tracker

Istio 0.5.0 is plagued by various bugs and we are likely going to cut a 0.5.1 to remedy the critical ones.
ATM the plan is only to cherrypick fixes into 0.5.0. Please add the PRs that must be cherrypicked into 0.5.0 in this issue. Note that only critical bugs will be addressed in patch releases.
A fine print: due to the still changing build system, it is possible that simple cherrypicks may not work. If that is the case, we may cut 0.5.1 at head which can include all fixes, but also increase the risk of opening doors to other bugs. This is only a fall back option.

https://github.com/istio/istio/pull/2965
https://github.com/istio/istio/pull/3008
https://github.com/istio/istio/pull/3010
https://github.com/istio/istio/pull/3175/

Hey, sorry to be a pain in the arse but I don't see how https://github.com/istio/istio/issues/3099 doesn't fall into this list?  Mixer is completely broken

Ah, you're referring to fixes already in place for an immediate cut.

another one:  #3182

@Stono yes if you a think a fix is important enough to be included in 0.5.1, please add the PR here.

https://github.com/istio/istio/pull/3150

checked with @smawson. Cutting 0.5.1 at master/head is not an option. Only the PRs that can be merged back to the 0.5.0 branch will be included in 0.5.0.
We will carefully inspect the PRs added to this list to ensure their feasibility, and severity.

#3183 is needed on top of #3150

Low impact: https://github.com/istio/istio/pull/3101

Restore Ingress metrics: https://github.com/istio/istio/pull/3142

Ingress controller not respecting route rules: https://github.com/istio/istio/pull/3218

^ Please.

K8s workload cert rotation fix: https://github.com/istio/istio/issues/3155 (Sorry, I committed it to V0.5.1 branch, you can revert it if this doesn't meet the requirements)

Expose concurrency flag of envoy https://github.com/istio/istio/pull/3065

Servicegraph is broken: #3079

I can't recall if https://github.com/istio/istio/pull/2901 was in 0.5.0, but I'd like to see it included in 0.5.1.

0.6.0 is expected to be cut mid month but it won't be out for another week.
There are some demand for fixing the critical bugs in 0.5.0.
At the same time, this is a good exercise to test the release pipeline for
creating a patch release.
Krishna, the release branch should have been 0.5 like Laurent said.
On Wed, Feb 7, 2018 at 3:47 PM, Laurent Demailly<EMAIL_ADDRESS>wrote:

As it is feb 7th already we should consider making an early 0.6.0 ? (which
would be Feb 15)
On the other hand, exercising and demonstrating our ability to make a
patch release is useful
ps: can we call the release branch release-0.5 (like we did for 0.1 and
0.2) instead of 0.5.1 ? if we make a 0.5.2 it will likely be on that same
branch, the patchlevel varies
(likewise this isn't critical for this but for LTS releases we need a long
term multi patch protected branch)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/3179#issuecomment-363951399, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AeRtkBOw4ZnyRvEgKQtzG42AknBGzUkFks5tSjX1gaJpZM4R6AOK
.

https://github.com/istio/istio/pull/2942

#3283
#2970

@rkpagadala https://github.com/istio/istio/pull/3101 can be ignored if you choose, its just that users who deploy 0.5.0 will have to recreate that crd

#3078   * Update proxy SHA to almost latest.

What's the target release date for 0.5.1?

Targeting next Monday.
On Fri, Feb 9, 2018 at 11:20 AM, Ross Guarino<EMAIL_ADDRESS>wrote:

What's the target release date for 0.5.1?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/3179#issuecomment-364533737, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AeRtkMNwqlEEaYD2kqN6C_C74urLaMlRks5tTJqTgaJpZM4R6AOK
.

Just to confirm that's Monday the 12th?

Yes
On Fri, Feb 9, 2018 at 11:26 AM, Ross Guarino<EMAIL_ADDRESS>wrote:

Just to confirm that's Monday the 12th?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/3179#issuecomment-364535803, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AeRtkHZeO3eFUt3P74hK_am5ch0llwN4ks5tTJv1gaJpZM4R6AOK
.

docs for minikube setup https://github.com/istio/istio.github.io/pull/921

0.5.1:
mixer's   statsd-to-prometheus:
Image:         prom/statsd-exporter:v0.5.0

@ldemailly  The tags for statsd exporter come from prometheus official docker releases and unrelated to our 0.5.1 version.
https://hub.docker.com/r/prom/statsd-exporter/tags/

oh nice coincidence, thanks @rkpagadala - @douglas-reid do you know why we are using the version from 3 months ago vs 1 month ago (0.6.0)

It this still happening today?

@rkpagadala is in the process of cutting 0.5.1. right now. Will update this bug when the release artifacts become available.

@ldemailly because we added it ~3 months ago and have not since updated.

0.5.1 is released.
https://github.com/istio/istio/releases/tag/0.5.1

Thanks for all of the work on this Istio team. 🍻  We have 0.5.1 in our integration cluster now and we're seeing a few of the bugs we saw go away. Namely, the wildcard routing one is resolved.

FYI - I forgot to include https://github.com/istio/istio/pull/3036 in the 0.5.1 release cherry-pick list. I've updated the setup instructions to refer uses to download the missing scripts directly from github (see https://github.com/istio/istio.github.io/pull/983)


TD-2814 Create ImageCard component

Closes TD-2814 Create ImageCard component
Contributes to TD-2784 Create Versions tab for road details
Changes

A new component Infogaphic is introduced. Along with the concept of CardContents.

Infographic component created consisting of <CardMedia> and <VersionChip>
FileCard renamed to FileDetails and is not a card, but card content. The <CardMedia> was removed from FileCard.
DetailsCard updated to accept CardContents, namely Infographic and FileDetails.
Minor fixes like variable renaming, spelling and comments.

Dependencies

UI/UX
Infographic component with VersionChip:

From Figma:

FIGMA

Testing notes

pnpm i
pnpm run storybook This should open storybook.
Use the sidebar to navigate to CARDCONTENT/Infographic
Check that docs are added and input fields are initialised
Make sure that changing the size of the image, doesn't change the size of the parent container (use inspect element)
Navigate to CARD/DetailCard make sure that the card looks exactly the same as before. Screenshot of the old DetailsCard from main

Author checklist before assigning a reviewer

[x] Reviewed my own code-diff.
[ ] Branch has been run in docker.
[x] PR assigned to me or an appropriate delegate.
[x] Relevant labels added to the PR.
[x] Appropriate tests have been added.
[x] Lint and test workflows pass.

I think this should be destined for a release branch and not main? We should align with my label chip group component which is now complete. I'll wait for this to be merged and then resolve any conflicts in my branch.

@AronPetrauskas Please change the base to a release branch. What happned to release/v7.10.0 branch? where this PR got then merged to.

I added id's as per the QA testing process to all the components affected by this PR. I also have changed the destination branch for the PR.

A lot has been changed to the PR because of the "passing VersionChip as a prop fiasco". I'll try to outline everything here:

VersionChip slightly rewritten (versionType prop removed, component automatically decides on versionType)
Props for VersionChip and Infographic changed
id changed to className
Tests for VersionChip and Infographic rewritten to reflect changes.

Testing:

pnpm i
pnpm run storybook This should open storybook.
Navigate to /general-versionchip--default
Check chip automatically renders major or minor svg based on the version provided
Check that VersionChip does not render when wrong format provided for version (aka not <number>.<number>). Open browser console to see a warning that provided format was wrong.


open_browser doesn't work from config file

open_browser doesn't work from config file
Expected Behavior
When adding open_browser = True in .okta_aws_login_config it will be honored
Current Behavior
open_browser doesn't work from config file
Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

App Version used: 2.8.0
Environment name and version:
Operating System and version:

This fix will be release in 2.8.1


Single cote seems to make the script fail

Hi bro,
In my last version of librefox i have some lines with // Default Value : " and // "
This seem to make the script fail without an error feedback...
I just removed those single quote lines from my mozilla.cfg file to fix the problem... its just to let you know about it ;)
Thanks
MiiiAAAaWWwwwooOOooo :D :+1:
EDIT : i am still debugging it seem to be related to something else

Grr still not finding... it could be the length of my script over 3400 lines...

I did not find what exactly make it fail i think its a combinations of multiple thing in the comments... i am just moving those lines to a separate files... i will comeback here once those will be published ;)

Waddup!
I tried comparing your mozilla.cfg to an user.js but I didn't have any issues. I can look for the culprit pretty easily if you give me a sample that doesn't work on your end.

Yes i removed a whole block of comment/wiki to have it working for users who wants to play with your scripts... i will post when i finish building binaries... it makes me sick :( esr/x64/x32/... all the platforms... i don't know if i will keep that like that... i will close this for the moment and come back with the exact info :)


Posterior quantiles

Should we change this to 16th and 84th percentiles? Which are more common to quote as uncertainties?
https://github.com/wbalmer/backtrack/blob/930c57124dea87df3f73430150265ce07949746a/backtrack/backtrack.py#L453

I'm not too familiar with dynesty. After looking at the code it seems it calculates quantiles for each of the parameters and stores it in the pkl results files. It also uses them to draw parameters for the trackplots (labeled 1 sigma). So 0.16, 0.84 sound like the correct quantiles as you suggest. However taking the lower and upper 1 sigma value of each of the parameters combined will not be the same as plotting the 1 sigma contour for where we can find our star (our parameters are not independent). Which is a different problem highlighted by https://github.com/wbalmer/backtrack/pull/13 . So: 0.16, 0.84 is better as it gives correct values in the pkl files, but we probably need to rewrite part of the code in the plotting routine to show actual 1 sigma probabilities in the trackplots.

for some reason while i wrote that line of code i thought that 0.5+/-0.18 = [0.32,0.68] was the 1 sigma interval, but that must have been late night coding (probably while up observing). this should be corrected in commit de0e8f6 and folded into PR #18


Build sets completionTime while in progress

I see:
 status:
    builder: Cluster
    cluster:
      namespace: default
      podName: app-from-source-00001-kxj8j
    completionTime: 2018-09-29T20:58:43Z
    conditions:
    - lastTransitionTime: 2018-09-29T20:58:43Z
      message: Pending
      reason: 'pod status "Initialized":"False"; message: "containers with incomplete
        status: [build-step-build-and-push]"'
      status: Unknown
      type: Succeeded

Fixed in https://github.com/knative/build/pull/384


Fixes for 'Edit this page' 🔨

Please describe the changes this PR makes and why it should be merged:
This fixes 'Edit this page' button in GCommands guide.
Status and versioning classification:

I know how to update typings and have done so, or typings don't need updating
This PR only includes non-code changes, like changes to documentation, README, etc.

Please, make this PR for Hyro-devdocs branch.


inline nots generates incorrect Verilog

This is a placeholder for a FIRRTL emitter bug introduced by #1270.
Checklist

[ ] Did you specify the current behavior?
[ ] Did you specify the expected behavior?
[ ] Did you provide a code example showing the problem?
[ ] Did you describe your environment?
[ ] Did you specify relevant external information?

What is the current behavior?
What is the expected behavior?
Steps to Reproduce

Your environment
External Information
See chisel-users

Resolved by #1422.


Displaying Incorrectly in Tmux

Hi all,
Not sure if this is an issue specifically that affects me, or if it affects other tmux users. Long story short, using the same terminal (urxvt) with tmux produces illegible output, and without tmux produces completely fine output.
Although the asciinema recording of the tmux version is not a 100% accurate representation of what I see, it's fairly close (and does demonstrate how illegible it is) - let me know if you want a proper screen recording :) Any assistance is appreciated!

Just a follow up - it's slightly better in xterm than it is in urxvt, but not drastically different. Still broken when attempting to use it (i.e. trying to "show" an entry results in "action aborted by user"). See screenshot below - top is in tmux, bottom is not, but both are in xterm:
https://i.imgur.com/VnMKMp0.jpg

Okay, looks like I've found the solution @dominikschulz - thanks for assigning the labels :) The tmux config line in question that was causing issues was:
set -g default-terminal "screen-256color"

Which is interesting, because screen actually worked fine! But, adjusting that line to the following resolved the issue:
set -g default-terminal "rxvt-unicode-256color"

I just ran into this issue myself; changing the TERM variable will mask but not actually solve the problem (and can cause issues with other apps in your tmux sesssion).
The issue is with the new (breaking) changes to terminfo files for ncurses 6.1, which alters certain counts from 16-bit integers to 32-bit integers. This is pretty much only seen when you switch to a -256color version of a stock terminfo file — e.g., TERM=tmux-256color or TERM=screen-256color (rxvt-unicode-256color bypasses it by being a non-stock terminfo file built with an older ncurses version).
The solution has to go upstream to whatever gopass uses to render those TUI windows — I'm by no means a Go expert, but it looks like that's jroimartin/gocui, which in turn depends on nsf/termbox-go, which should have had this issue solved in commit https://github.com/nsf/termbox-go/commit/08476232a9953536788d8a9e6c6ddfe80ac73767. Perhaps something in gocui or gopass just needs to be told to use the newer revision?

@Celti Thanks a lot for you research. That was super helpful!
I've updated the term UI related libraries in #789. Maybe someone can check if that fixes the problem?

Amazing, thanks @Celti !


should hugginface app work?

I look at https://huggingface.co/spaces/FinGPT/FinGPT-Forecaster page App and see
Runtime error
10/site-packages/peft/peft_model.py", line 554, in load_adapter
    adapters_weights = load_peft_weights(model_id, device=torch_device, **hf_hub_download_kwargs)
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/peft/utils/save_and_load.py", line 171, in load_peft_weights
    has_remote_safetensors_file = hub_file_exists(
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/peft/utils/hub_utils.py", line 26, in hub_file_exists
    get_hf_file_metadata(url)
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/huggingface_hub/utils/_validators.py", line 118, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1624, in get_hf_file_metadata
    r = _request_wrapper(
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 402, in _request_wrapper
    response = _request_wrapper(
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 425, in _request_wrapper
    response = get_session().request(method=method, url=url, **params)
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/huggingface_hub/utils/_http.py", line 63, in send
    return super().send(request, *args, **kwargs)
  File "/home/user/.pyenv/versions/3.10.13/lib/python3.10/site-packages/requests/adapters.py", line 532, in send
    raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: (ReadTimeoutError("HTTPSConnectionPool(host='huggingface.co', port=443): Read timed out. (read timeout=10)"), '(Request ID: a1426b7c-51df-4a5a-a8f3-17dfb709d5c8)')

Can this be fixed?

https://fingpt.bot/

https://fingpt.bot/

Hey Evgeny, this website is not maintained by the FinGPT team, please always refer to the huggingface one: https://huggingface.co/spaces/FinGPT/FinGPT-Forecaster
we will have more markets available soon

Topic: Using Open-Source Code for App Development
As an open-source community, we are committed to fostering innovation and collaboration. We are delighted to hear that our users are interested in building their apps using our open-source code.
Please feel free to explore our repositories and utilize the resources available. If you have any specific questions or need further assistance, do not hesitate to contact us. We are here to support your development journey and look forward to seeing the amazing applications you create.
Best regards,
Bruce Yang