Returning the duration from the fragment

I'm new to Android dev so this is probably a really easy question, but how does one get the duration from the TimePicker fragment?
I've got the TimePicker.java fragment in the directory with my activity. The activity successfully opens the fragment when the user long clicks on some text, but I can't figure out how to return the duration value from the fragment back to the activity. I spent a few hours yesterday messing around with interfaces but never got it to work.

Which class are you using? Are you using the time picker directly (class TimeDurationPicker) or the dialog fragment (TimeDurationPickerDialogFragment)?

I'm using TimePickerDialogFragment. Completely unchanged except for the units, which I'ved changed to MM_SS.

You need to override the fragment's onDurationSet() method. See the example in the README.md.
This might seem inconvenient, but as you get used to Android you'll learn, that there is no other way on interacting with fragments than deriving own classes from them. This is due to configuration changes (e.g. device orientation change) where the activity itself will be destroyed and recreated, but the fragments will be serialized and restored.
Hope this helps?

I'm assuming you're referring to
@Override     public void onDurationSet(TimeDurationPicker view, long duration) {         DurationToast.show(getActivity(), duration);     } }?
I've got that in the fragment, and I'm able to get a Toast notification to work but that's about it. I don't want to take up too much of your time with teaching me something I can learn on my own, so do you have any suggestions of reading I can do to figure this out? Thanks!

Where do you need the entered duration? In your Activity?

Yes sir.
On Wed, Dec 28, 2016 at 7:12 AM, Sven Wiegand<EMAIL_ADDRESS>wrote:

Where do you need the entered duration? In your Activity?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/svenwiegand/time-duration-picker/issues/6#issuecomment-269475197,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACzEHT1_49sYpURRTM04Ndbw37xaykxlks5rMmBQgaJpZM4LW0RK
.

Try the following:

In your Activity class (lets assume it is called MyActivity) add an event handler method e.g. likeprotected void onDurationSet(long duration) {
  // do something with the duration here
}

Implement the onDurationSet() method of the fragment to forward the result to the activity like this:@Override public void onDurationSet(TimeDurationPicker view, long duration) {
  ((MyActivity) getActivity()).onDurationSet(duration);
}

Now you can use the duration in your activity.
The Fragments Guide in the Android developer documentation is a good read -- especially the section Communicating with the Activity addresses your current problem.
Did this help?

That did it! Thank you so much.

Happy I was able to help.


Master to Live

Docs Build status updates of commit 65100bf:
:clock10: Full build: the average full build time is 11 min(s) 51 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 65100bf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/devices/New-ActiveSyncMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Set-IRMConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearchAction.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/Move-CsUser.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


addTemplate() create files with last modified date 01.01.1970

Files which copied with with the addTemplate() function to the docker container has the last modified date 01.01.1970. This can cause several problems, if an application use this date.
Sample:
$ stat test.txt
  File: './test.txt'
  Size: 89              Blocks: 8          IO Block: 4096   regular file
Device: 3ch/60d Inode: 60          Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 1970-01-01 00:00:00.000000000 +0000
Modify: 1970-01-01 00:00:00.000000000 +0000
Change: 2016-03-22 09:24:09.239482349 +0000
 Birth: -

Unfortunately this is a workaround that is necessary to ensure that the docker caching mechanism works.
If a specific (or newer) last modified date is required, please use touch or touch -mt to explicitly set the date.


Private Subnets

Some orgs have security requirements to only have EC2 running in private subnets. Can we make this some kind of option for this terraform deployment?

I actually have found the option necessary to make that happen. My local work isn't synced to the development here because of different nodegroup options, but just this morning I pushed my work to a new branch unmanaged_nodegroups.
In that branch, the bits of note are mostly here. Basically, you need the following in the vpc module block:
module "vpc" {
  ...

  private_subnets = [something]

  enable_dns_hostnames = true
  enable_dns_support   = true
  enable_nat_gateway   = true
  single_nat_gateway   = true

  private_subnet_tags = {
    "kubernetes.io/cluster/${var.cluster_name}" = "shared"
    "kubernetes.io/role/internal-elb"           = "1"
  }
}

and the following in the eks module block:
module "eks" {
  ...
  subnets = module.vpc.private_subnets
  cluster_endpoint_private_access = true
  ...

The use of single_nat_gateway is really just helpful because an AWS account only gets 5 IP addresses, I think, so you can use just one instead of three (one for each subnet). I have a working cluster configuration with this.
Terraform should have the capability to allow us to dynamically set up public / private subnet usage for the modules based on an input variable. Is that what you are thinking of having?

Managed nodegroups also just got the ability to be in private subnets.

STScI is still very interested in this topic,  but before we run off and start coding,  I wanted to double check the status of the unmanaged_nodegroups branch.  Is there a plan to merge that anytime soon?   If not,  can you suggest an approach for us which would avoid/minimize conflicts with your branch when unmanaged_nodegroups does merge?   If possible we'd like to contribute back,  maybe we could do the input variable handling to make private  subnets optional?

@jaytmiller So I think since the main branch and unmanaged_nodegroups specifically have managed vs unmanaged nodegroups, they wouldn't really be in the same branch. I could see them being parallel, but separate, because of these two different use cases. Managed nodegroups (I hear) usually lag behind in terms of features.
That said, we could try to configure an option to opt in or out of having the nodegroup being managed. This might be easier if we turn this repo into a Terraform module, which is a whole other can of worms.
I can definitely take some time next week to examine unmanaged_nodegroups and see what should be done. I think it contained my development work while making some hackweek infrastructure but that now lives in hackweek-template-infrastructure. We could move the relevant work into the main branch and delete unmanaged_nodegroups. What are your thoughts? Happy to collaborate here.


Question: support pause reconciliation for vmcluster cr

Consider adding support for pause reconciliation for vmcluster cr, similar to what have been done in vmalertmanager
https://github.com/VictoriaMetrics/operator/blob/8f025b3b4fce6e3472cabaa49b07c748aa6e3ffa/api/victoriametrics/v1beta1/vmalertmanager_types.go#L151
This feature would be helpful when performing operational tasks. I am willing to submit a pull request if you are open to merging this change. @f41gh7

Sounds like a good feature to all the components.
But I don't see any related implementation for VMAlertmanagerSpec.Paused now, seems like a unfinished TODO.

Looks valuable feature to me. And good catch, currently Paused option is no-op for alertmanager.

Changes included to the v0.44.0 release


Changes CND to prevent redirections

When fetching https://twemoji.maxcdn.com/2/svg/XXX.svg the response status is "301 Moved Permanently" with "Location<EMAIL_ADDRESS>To avoid redirections and  we change the CDN.
Moreover, asciidoctorjs in version 3 does not correctly manage these redirections to download images in SAFE mode. Changing the CDN works around the problem.

Thanks!


Qualified statement

Purpose
Add type for the statements that is received from dApps (unqualified) and add methods to convert them into the ones that are needed for proofs (qualified).

I'll address the comments/fix stuff when we finish with the can-prove-statement.


transmog frame

Hi,
I found a bug related to the transmogrification window. When I open it (true, from Grand Expedition Yak) I have a separate background left which doesn't disappear after closing the window.

When I disable Drift the bug disappears. I tried with "miscellaneous" option unchecked but the bug persisted. Unfortunately there is no error popping up. I think is related to Drift because I checked with every addon on and off which may interfere in anyway with such frames (and I don't have UI modifiers like ElvUi or Skinner or anything like that).
I will see if this appears when visiting the transmog guy instead of mount derived frame.

Hi @lenoirrichelieu - Thanks for the bug report and detail! You're correct that it's related to Drift. I recently implemented a workaround for Collections, and this looks like it's related. I can reproduce the issue, and I will work on a fix.

@lenoirrichelieu - This should be fixed in Drift v1.0.21. Can you download the update and let me know if the issue is fixed on your end? Thanks!

@jaredbwasserman - It is fixed. I checked on multiple chars with and without other addons enabled. I consider this issue closed.

Thanks for confirming!


INS-674 - First pass at making the send button more visible

Closes #3152
Closes INS-674
This is a first pass attempt at a way to make the send button more visible in the current layout. I verified all current core themes to make sure each had the improvement.
Below are some example screenshots of different themes, with hover states as well.

I rebased it for you and added 33fbde6e14cc3f646bbfd61df62dcf90564556ec which does:

The color isn't right (obvi) but I had a moment to throw it in there.  Since this change is all about making it standout/so prominent, I thought that it would be appropriate for the preview to have it.  Not 100% sure how to theme it, but I'm sure we can figure it out by observing how the other things (e.g. sidebar) are themed.  I only had a few moments between two calls to do it so I thought it'd be better than nothing to get the ball rolling with at least placing it.

Ah interesting! I didnt even think to update that little SVG. I'll dig in on how to get proper colors in.

Updated the colors

no biggie, but I'm curious: why is it that in the core default the color for the dark theme is #a39af9 while the swatch is #796dc5.  For all of the rest of them it seems to match, but for just core-default it's brighter.

Code updated to change the gRPC button (since it uses insomnia-components as its more modern) and updated the CSS to add a small left margin to prevent text from pushing up against the rest/graphql send button


Is there a way to change topSpacing after initializing the sticky sidebar?

So after I do
var topSpacing = 100;
mySidebar.stickySidebar({
    topSpacing: topSpacing
});

Can I change the value of topSpacing?

No that is not the way that javascript works for primitive data types! https://developer.mozilla.org/en-US/docs/Glossary/Primitive
In this library, you can use  a function to calculate the top spacing
mySidebar.stickySidebar({     topSpacing: function(){         return true ? 100 : 150;     } });

Pretty sure OP is asking if there's a way to update the values of stickySidebar options after they've been set.
Example: You want topSpacing: 50 on mobile and topSpacing: 100 on desktop.
I haven't been able to find a way to do this, so what I do is I destroy the stickySidebar and re-create it with values depending on screen width.


publish reference documentation

What article on docs.github.com is affected?
GitHub Actions / Reference
There seems to be no reference documentation for workflow_run (and many other items for that matter). This is very problematic as it leaves us struggling to find information in the guides, which are not complete in that regard.

Hey @Morriz Thanks for reaching out! We've got to make sure our docs balance having every possible answer with being maintainable and readable, so we don't document absolutely everything.
Please keep in mind that repeatedly opening the same issue (or very similar issues), can be considered a violation of the harassment clause of our Code of Conduct.
Thanks so much for your passion in improving the GitHub docs!

It is more about having answers, but about having reference documentation that is complete...so made by machines, not humans

Where can I take this concern now that I get shut down twice already?

As a developer using Github Actions this has been a constant frustration as well.
Often when something in the reference is vague, it can be difficult to seek out the answers we seek for clarification. Official responses at best may reference documentation for API responses elsewhere unrelated to Github Actions. That may be sufficient for those familiar with the documentation and API's, but for those whom rarely are involved with needing to look through Github's various docs, it's not a pleasant experience.
Rather than blame the users, consider that the documentation process itself is at fault? You can still provide the balance you want by default, while catering to more complete documentation upon user action, commonly known as progressive disclosure in UX design.
If the concern is regarding duplicate content, the documentation ideally would have a build process that share common data (eg with mkdocs there is a snippets extension for exactly this purpose). I would hope that all the API response examples are not copy/paste into docs, they can be version controlled as separate files and imported as part of the build process.

Regarding any concerns about adding verbosity..
Have admonitions that are collapsed by default like this. When the user is actually interested in the information they can interact with it to view it.

This isn't the first time I saw requests to address problems with the docs being dismissed for such reasons. I hope that Github takes the feedback more seriously, seeing as it has done so well at becoming the dominant CI of choice on it's own platform.
We lose far more time attempting to search and find answers when the documentation lacks. I understand that the pages are lengthy as-is, but I'm provided with structured documents (and ctrl+f) to quickly view content of interest. Meanwhile when information is lacking, I can find multiple users confused and sharing workarounds that aren't safe in github issues or the same questions being asked in the community support forum without any answers for months.
Solid documentation is highly valuable.

Hi @janiceilene,
I've gone down the rabbit hole of trying to learn more about workflow_run fields, following the general path of:

https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads#workflow_run
Various external websites
https://github.com/github/docs/issues/799
https://github.com/github/docs/issues/4435
And eventually landing on this issue.

Unfortunately, the fields that are accessible through workflow_run are still not apparent to me. Maybe I'm missing some other documentation?
So, I sympathize with the sentiments that @Morriz has expressed - and thought I would pass along my own experience of trying to learn.
My next steps will probably be to start up some ad-hoc workflow_runs so I can export the object to manually introspect the available fields.

TL;DR: There's quite a bit of friction introduced by a lack of documentation, missing support in official actions (with some issues spanning 1-2 years), leaving many developers to flounder around to piece together a solution and potentially introducing more risks.

This has been my experience as well.

Hey @Morriz Thanks for reaching out! We've got to make sure our docs balance having every possible answer with being maintainable and readable, so we don't document absolutely everything.

I just found out about github.event.workflow_run.head_branch and it would have saved me a lot of time if that information had been available in the docs. I see the new "Many workflow_run keys, such as head_branch, conclusion, and pull_requests are the same as those in a check_suite object." line now that I know exactly what to look for, but it would have been great to have these keys enumerated and explained. Maintainability and readability are certainly good to keep in mind, but documentation needs to give information about how to use the system.
I don't think leaving things out of the docs is a good idea.

In case of anyone is still wondering what are the properties of the workflow_run event, here is an excerpt of the object:
workflow_run: {
      artifacts_url: 'https://api.github.com/repos/...',
      cancel_url: 'https://api.github.com/repos/...',
      check_suite_id: 123456789,
      check_suite_node_id: 'NODEIDACDEFGHUIADASD',
      check_suite_url: 'https://api.github.com/repos/...',
      conclusion: 'success',
      created_at: '2021-06-07T18:44:28Z',
      event: 'workflow_dispatch',
      head_branch: 'main',
      head_commit: [Object],
      head_repository: [Object],
      head_sha: 'SHAACBADSADAASDASD',
      html_url: 'https://github.com/....',
      id: 123456789,
      jobs_url: 'https://api.github.com/repos/...',
      logs_url: 'https://api.github.com/repos/...',
      name: 'workflow-that-completed',
      node_id: 'NODEIDACDEFGHUIADASD',
      pull_requests: [],
      repository: [Object],
      rerun_url: 'https://api.github.com/repos/...',
      run_number: 14,
      status: 'completed',
      updated_at: '2021-06-07T18:47:28Z',
      url: 'https://api.github.com/repos/...',
      workflow_id:<PHONE_NUMBER>,
      workflow_url: 'https://api.github.com/repos/...'
    }

I extracted it using this Action to print the context, hope is of any help :)

Having it in the documentation will help prevent breaking changes. Currently, I'm very much concerned that someday my GHA would stop working for some reasons.


Linkify ipfs-ish text

options to turn plain /ipfs/ and ipfs:// text into links and context menu entries to open any highlighted multihash as ipfs links would be nice.

Sounds useful  :+1:
My thinking:

A new context menu item "Open IPFS resource" visible when there is a text selection that match IPFS resource regex
Not sure about turning text into links. I think it could be done, but modifying pages on the fly should be configurable via checkbox on the Preferences screen and probably disabled by default.

If there is no PR with this I'll try to add it in my spare time.. some day. ;-)

Yeah, modification of the DOM should be optional.


Dialog container should have maxHeight 100% and no margins

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
The Dialog container should have maxHeight 100% and no margins.
Motivation 🔦
Currently, the dialog container is not responsive because of the margins and the maxHeight not being 100%. E.g. :

I would like it to take the full width and full height.

See the fullWidth prop.

fullScreen prop does what I want, but I don't think it is responsive. I want it to be fullScreen only for a certain size of screen. Hence, the solution I propose is responsive.

@lcswillems Does https://material-ui.com/components/dialogs/#responsive-full-screen cover your requirement?

Wow!! This is exactly what I need. I love the concept of useMediaQuery. Sorry for not having seen that.


Task 10

Issue: #219
Added the screenshot

Hey @Darkknight0125
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!


Since the variable "max_result" is not used in the code, it has been removed to avoid causing confusion for users. (The example code was tested, and the presence or absence of max_result does not affect the results.)

thx


targets brotli 1.0 branch

There was only remouval of deprecated methods which are not used by crate.\
All C files are stored in c directory now, I included to build all necessary files, but not every one
A bit unsure right now what exacly caused example test to fail

Thanks! Looks good to me, but CI appears to be failing?

@alexcrichton Yes, it seems something changed in brotli internally and example has some failures due to https://github.com/alexcrichton/brotli2-rs/blob/master/src/write.rs#L151
It seems it needs more output but it didn't consume anything at all
Since I'm not very well familiar with brotli API, I'm not sure what's going on there exactly.
For no I'm trying to prototype myself to get a hang of it.

Ah sorry I don't have the time to help debug this, but I'm pretty confident in CI so if it's working there seems fine to merge!

The way it looks, at some point brotli starts returning NeedOutput despite Write interface periodically taking bytes out of it.
It is not even consuming any input once it happens.
Which looks like bug there but I'm not all that sure


LPIPS  evaluation should add normalize=True

Hi, thanks for the great work.
I noticed that the LPIPS evaluation does not include normalize=True given that the inputs are in the [0,1] range. Adding this would change the results from 0.292 to 0.339. Despite this increase, the result still remains significantly better than the baseline.
https://github.com/Wangt-CN/DisCo/blob/8cb938712c8f5cdf33190731f804c2c4a7a3f56a/tool/metrics/ssim_l1_lpips_psnr.py#L74-L97
LPIPS:
https://github.com/richzhang/PerceptualSimilarity/blob/31bc1271ae6f13b7e281b9959ac24a5e8f2ed522/lpips/lpips.py#L112-L115

That's right, the result should be higher if using the right value range.
The result should be updated.


Pottential Bug in low_power_sweep.py

The tests related to low_power fails due to NameError in the file low_power_sweep.py
Version : gem5 version <IP_ADDRESS>
No modifications made, running stable version
To Reproduce
Steps to reproduce the behavior. Please assume starting from a clean repository:

Compile gem5 with command  scons  build/ALL/gem5.opt -j64
Execute the simulation with

 /home/simulators/gem5-latest/build/ALL/gem5.opt /home/simulators/gem5-latest/configs/dram/low_power_sweep.py -p open_adaptive -r 2

Terminal Output
gem5 Simulator System.  https://www.gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 version <IP_ADDRESS>
gem5 compiled Nov 22 2023 14:34:52
gem5 started Nov 22 2023 16:25:22
gem5 executing on arcortx3080.pc.ac.upc.edu, pid 1340484
command line: /home/simulators/gem5-latest/build/ALL/gem5.opt /home/nitesh/simulators/gem5-latest/configs/dram/low_power_sweep.py -p open_adaptive -r 2

NameError: name 'TrafficGen' is not defined

At:
  /home/simulators/gem5-latest/configs/dram/low_power_sweep.py(270): <module>
  src/python/m5/main.py(630): main

Host Operating System
Ubuntu 23.10
Host ISA
X86
Compiler used
gcc 10.5.0

Hi @Nitesh8998,
The bug is probably due to the missing dependency of protobuf. gem5 doesnt not build the traffic generator is protobuf is not installed (see line https://github.com/gem5/gem5/blob/b99af93183b2f77781b6f4759bc06f717d3bb9bc/src/cpu/testers/traffic_gen/SConscript#L66).
The script should work if you install the dependency with the command
sudo apt install libprotobuf-dev protobuf-compiler libgoogle-perftools-dev

For more details take a look at building gem5 documentation https://www.gem5.org/documentation/learning_gem5/part1/building/.


fix(anomaly): convert y values to float before saving

When the y values are integers, anomaly fails while saving with the error sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) can't adapt type 'numpy.int64'.
This is noticeable either with KPIs that have their metric column as an integer type or with Data Quality count.
The commit fixes this by always casting the y values to float.

Superseded by #1077


update blog contribution policy

This introduces a stricter policy on how we accept blog posts:

It still makes sure that anyone can create a blog post
It requires an issue to be raised before a PR is made (we had that already)
It asks authors to list technologies they use
It requires a related SIG to sponsor[^1] a PR, and a SIG approver/maintainer to provide review

The big changes come with 3. and 4. By listing the technologies we can verify early that no commercial software is used or that the technology used is "appropriate" (e.g. they use Jaeger and not another semi-commercial trace visualization). By asking them to provide a SIG that is "sponsoring" the blog post, we ensure the following:

Nothing changes for SIGs when they contribute blog posts (see the collector roadmap + collector survey blog post, both have sponsors easily since they come out of the SIG)
No blog posts are introduced that go against what a SIG would say about a certain topic (e.g. if someone would push a blog post with an alternative automatic instrumentation for a language which is for reasons unknown to SIG Comms not what the language SIG wants to be pushed)
No blog posts are handed in as a PR directly and we as maintainers/approvers need to feel bad for rejecting it.

[^1]: Looks like "sponsor" is word of the year in otel land ...

LGTM. Slightly concerned that the nominate a SIG maintainer requirement might close the doors to entirely external contributors. This is currently not a requirement for docs, so why making it a requirement for blog posts?

Not a maintainer, an approver is good enough as well. And we kind of have a similar requirement for docs, we ask SIG maintainers/approvers for review. Reason is that by that we make sure that blog posts do not say something that the SIG would not approve (let's say someone writes a blog post about the collector and describes some inner workings wrong, etc.)

Thanks @codeboten, it looks like I messed something up in another PR:
https://github.com/open-telemetry/opentelemetry.io/pull/3834/commits/102e258b4dccb5dc6f31daa5e85d60e1bab9a618

Will create a follow up PR soon to address some of the feedback around mandatory/recommended


Handle voip call signalling on high latency servers

Simultaneously starting calls happens often even on low-latency servers. In this case, it is impossible to answer the call from Element.
Alice places a call (sends m.call.invite), and Bob places a call too (before seeing the Incoming Call from Alice because of server latency). Both of them has sent an m.call.invite
In this case, both Alice and Bob has a dialing screen, and can't accept either call because Element would need to display an Incoming Call screen.
I can imagine 2 solutions:

Could the two m.call.invite data somehow be used to set up the WebRTC connection? If yes, then this should be done.
Otherwise, when both Alice and Bob receives the other m.call.invite (2 calls are active simultaneously), use the one with newer server timestamp. Send hangup for the one with older timestamp. Send accept for the newer timestamp. In this case, the one who sent the newer timestamp version, has their call answered.

This issue is called "glare", and is already solved in the spec ( https://matrix.org/docs/spec/client_server/r0.6.1#glare ).  However, clients might not have it implemented correctly (e.g. https://github.com/vector-im/element-web/issues/2199 ).


Rxbindings

Create extension functions for better support of RxJava2

closes #92

RxJava 3 is around the corner. Are we planning to add a store-rx3 artifact with the same APIs?

Sure!

Cool. In that case we might want to rename rx to rx2 in the package name in this PR.

One thing we should add is scope <-> scheduler conversion.

we should add a fun scheduler(...) that will be wrapped via a scope
This one is a little tricker, rxSingle and co take an optional scope parameter. It would probably be wise to have that run on the store scope. Though you might need to re-add RxStore in order to support it as I don't think converting the builder parameters would be enough (sorry!)

Actually the methods that create a new single are extension on Store not StoreBuilder. If you make Store.scope public, you could use it to set the right default

Should be all set, added the rx/scope builder function, added more comments, cleaned up visibility where I could

I was thinking to make the other ones top level to. It will then be like flow{} or rxSingle{}

IMHO this can be confusing as there are same APIs in the coroutines artifact.

@ychescale9 I thought to make them
flowStore{} &
nonFlowStore{}

giving us the four
rxSingleStore{}
rxFlowableStore{}
flowStore{} &
nonFlowStore{}

That’s much more intuitive although the lambda still returns a builder rather than a store...
I slightly prefer the extension function on Builder more but I’m not strongly against this either.


Fix debugger exception detection

The exception detection introduced in https://github.com/ruby/debug/pull/150 doesn't apply to GNU/Linux platforms. A test fails after the detection is added but it only presents on some platforms (like macOS)

✦ ❯ ruby test/debug/catch_test.rb -n /reject/
Loaded suite test/debug/catch_test
Started
E
=========================================================================================================================================================================================================================
Error: test_debugger_rejects_duplicated_catch_bp(DEBUGGER__::BasicCatchTest):
Traceback (most recent call last):d because of:
        1: from /var/folders/yg/hnbymwxd5pn7v94_clc59y6r0000gn/T/debugger20210709-94267-3vfzfn.rb:4:in `<main>'
  /var/folders/yg/hnbymwxd5pn7v94_clc59y6r0000gn/T/debugger20210709-94267-3vfzfn.rb:4:in `/': divided by 0 (ZeroDivisionError)

The detection shouldn't use Traceback for detection because it'll include the exceptions raised by the program itself.

So this PR fixes these 2 issues and introduce better formatted messages for debugger exceptions.

The detection shouldn't use Traceback for detection because it'll include the exceptions raised by the program itself.

Exception can be thrown at other locations. I'll try to fix it later.


gquic branch usage

Is the gquic branch still available now? I used this piece of code to send a gquic request of the q043 version, and received the following error message.
package main

import (
	"fmt"
	"net/http"
	"net/url"

	"github.com/lucas-clemente/quic-go"
	"github.com/lucas-clemente/quic-go/h2quic"
)

func main() {
	roundTripper := &h2quic.RoundTripper{
		QuicConfig: &quic.Config{Versions: []quic.VersionNumber{quic.VersionGQUIC43}},
	}

	defer roundTripper.Close()
	hclient := &http.Client{
		Transport: roundTripper,
	}

	url, _ := url.Parse("https://www.litespeedtech.com/")
	req := &http.Request{
		Method: http.MethodGet,
		URL:    url,
		Header: nil,
	}

	resp, err := hclient.Do(req)
	if err != nil {
		fmt.Println(err.Error())
	} else {
		fmt.Println(resp.StatusCode, resp.Proto)
	}
}

error message:
Get "https://www.litespeedtech.com/": HandshakeTimeout: Crypto handshake did not complete in time.

https://www.litespeedtech.com/ is a website that supports the gquic q043 version protocol, and the version of the quic-go package I use is github.com/lucas-clemente/quic-go v0.10.3-0.20190519135638-0810051757ce.

Maybe it's still available in git, but frankly, I don't care about gQUIC at all. And neither should anyone else, it has loooong been deprecated.


Relaying of message for Newsfeed

Contains the work of PR 1 and 2, will review after those are merged and just the work done after that is in the diff.


2024-11-23-UMass-flusion

it looks like you need to remove the "model_id" column and then this will be valid.


Historical DB Is Too Stale

curl -X GET   'http://localhost:8000/ledgers?cursor=now&order=desc&limit=1'
{
"type": "https://stellar.org/horizon-errors/stale_history",
"title": "Historical DB Is Too Stale",
"status": 503,
"detail": "This horizon instance is configured to reject client requests when it can determine that the history database is lagging too far
behind the connected instance of stellar-core.  If you operate this server, please ensure that the ingestion system is properly running.",
"extras": {
"core_latest_ledger": 30206789,
"history_latest_ledger": 0
}

The protocol upgraded yesterday. Please confirm you have followed the instructions here and upgraded all software before opening a bug report: https://www.stellar.org/developers-blog/guide-to-protocol-13-prep


[INLONG-7058][Sort] Support Apache Kudu connector

Prepare a Pull Request
[INLONG-7058][Sort] Support Apache kudu connector

Fixes #7058

Motivation
CREATE TABLE kudu_tbl(
uid int,
fee double,
event_id bigint,
remark varchar
)
WITH(
 'connector'='kudu-inlong',
 'connector.masters'='localhost:8081;localhost:8080',
 'connector.table'='actual_tbl',
 'flush-mode'='AUTO_FLUSH_SYNC',
 'lookup.max-cache-size' = '-1',
 'lookup.max-cache-time' = '60s',
 'sink.start-new-chain' = 'true',
 'max-retries' = '3',
 'sink.max-buffer-size' = '100',
 'sink.write-thread-count' = '5',
 'sink.max-buffer-time' = '30s',
 'sink.write-with-async-mode' = 'false',
 'sink.write-with-upsert-mode' = 'true',
 'sink.cache-queue-max-length' = '-1',
 'ignore.all.changelog' = 'false'
);

The Apache Kudu sort-connector is fully integrated with Flink 1.13.x's Table and SQL API. By configuring KuduTableInfo (connector.masters, connector.table and other attributes), the kudu table can be queried and inserted by Flink SQL.
Modifications
DDL options

Option
Default value
Required
Remarks

connector.masters
null
true
The master addresses of kudu server, like 'localhost:8080,localhost:8081'

connector.table
null
true
The table name of kudu

flush-mode
AUTO_FLUSH_SYNC
true
The flush mode of Kudu client session, AUTO_FLUSH_SYNC/AUTO_FLUSH_BACKGROUND/MANUAL_FLUSH.

lookup.max-cache-size
-1
true
The maximum number of results cached in the lookup source.

lookup.max-cache-time
60s
true
The maximum live time for cached results in the lookup source.

sink.start-new-chain
true
true
The sink operator will start a new chain if true.

max-retries
3
true
The maximum number of retries when an exception is caught.

sink.max-buffer-size
100
true
The maximum number of records buffered in the sink.

sink.write-thread-count
5
true
The maximum number of thread in the sink.

sink.max-buffer-time
30s
true
The maximum wait time for buffered records in the sink.

sink.write-with-async-mode
false
true
Use async write mode for kudu producer if true.

sink.write-with-upsert-mode
true
true
Force write kudu with upsert mode if true.  This option is used for upsert using the primary key of the kudu table

sink.cache-queue-max-length
-1
true
The maximum queue lengths.

ignore.all.changelog
false
true
Whether ignore delete/update_before/update_after message. If true, all message will insert

Data type

Flink/SQL
Kudu data type

STRING
STRING

BOOLEAN
BOOL

TINYINT
INT8

SMALLINT
INT16

INT
INT32

BIGINT
INT64

FLOAT
FLOAT

DOUBLE
DOUBLE

BYTES
BINARY

TIMESTAMP(3)
UNIXTIME_MICROS

Verifying this change
(Please pick either of the following options)

[x] This change is a trivial rework/code cleanup without any test coverage.

[x] This change is already covered by existing tests, such as:
(please describe tests)

[ ] This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

Please add some describe for your design and implements, thanks.

Please add the access protocol for it(add KuduLoadNode in the sort-common).

I will submit another PR.

Please add some describe for your design and implements, thanks.

I have supplemented some document information in the pr description, please check

add fileSet for kudu connector in inlong-distribution/src/main/assemblies/sort-connectors.xml


[bounty] $150 build windows CLI and make it installable & usable in less than 60 seconds

definition of done:

windows CLI is being built somewhere convenient in the CI/CD (release-cli along linux and mac brew stuff) and uploaded build somewhere (like releases)
docs is updated, clear
dependencies are packaged with the CLI somehow

/bounty 150

Will give it a shot!
/attempt #757

done


posix: implement fgets()

This is part of the See POSIX Roadmap for LTSv3 (RFC #51211).
fgets() is required as part of POSIX_DEVICE_IO Subprofiling Option Group.
For more information, please refer to https://pubs.opengroup.org/onlinepubs/9699919799/functions/fgets.html

@cfriedt, do you have a draft PR for this? If not I would like to work on this.


Too strict when checking usage of exclamation mark (!).

JSHint warns "Confusing use of !" when encouts codes like below:
function myFunction(intergerA) {
	intergerA = parseInt(intergerA);
	if (!(integerA > 0)) { // in case the parsed integerA being NaN, the "!(integerA > 0)" is still false
		throw('Invalid intergerA');
	}
}

however:
function myFunction2(intergerB) {
	intergerB = parseInt(intergerB);
	if (integerB <= 0) { // in case the parsed integerB being NaN, the error wont throw
		throw('Invalid intergerB');
	}
}

Please see #780

In this case, if you would like to handle NaN values, I would recommend being
explicit:
 function myFunction(intergerA) {
   intergerA = parseInt(intergerA);
-  if (!(integerA > 0)) {
+  if (integerA <= 0 || Number.isNaN(integerA)) {
     throw('Invalid intergerA');
   }
 }

Reason being: expressing this with !(integerA > 0) implicitly relies on the
behavior of NaN > 0, and the result of that operation is not especially
intuitive. Using Number.isNaN is a clear signal that the condition is
intended to recognize (and reject) NaN values.
That said, you may also disable the relevant warning, W018 in one of two ways:

for your entire project by placing "-W018": true in your .jshintrc file

For just this case: surround the expression with /* jshint -W018 */ and
/*jshint -W018 */, as in
 function myFunction(intergerA) {
   intergerA = parseInt(intergerA);
+  /* jshint -W018 */
   if (!(integerA > 0)) {
+  /* jshint +W018 */
     throw('Invalid intergerA');
   }
 }


Replacing the CloseableHttpAsyncClient with a shared OkHttpClient is still causing huge memory usage

Reference PR: https://github.com/splunk/splunk-library-javalogging/pull/135
We use the version of 1.8 and we still face the same issue what is describe in the referenced PR.
The situation is the same with CloseableHttpAsyncClient and OkHttpClient too.
That is all what we have in our logback.xml (Java 8, SpringBoot, Tomcat)
    <appender name="SPLUNK" class="com.splunk.logging.HttpEventCollectorLogbackAppender">         <url>XYZ</url>         <token>XYZ</token>         <index>XYZ</index>         <source>XYZ</source>         <sourcetype>XYZ</sourcetype>         <host>XYZ</host>         <messageFormat>json</messageFormat>         <disableCertificateValidation>true</disableCertificateValidation>         <middleware>HttpEventCollectorMiddleware</middleware>         <layout class="ch.qos.logback.classic.PatternLayout">             <pattern>                 %msg             </pattern>         </layout>     </appender>
It burns the entire heap up in some minutes.

The problem is related to the fact that this appender does not control the flow in any way at all. Current implementation just assumes that it can push as many events without any kind of "backpressure" as it can, that results in OOM - right now there is no way ready-to-use option to monitor the queue or controll it - appender just keep putting requests in http client's queue (see OkHttpClient dispatcher) and so far I don't see an easy way to stop.
This makes current implementation completely broken for schenarios with high spikes of log events or when some logs are fine to loose (that is easily achieved in other loggers by wrapping real logger in async one and configuring queue options there).

Hi @czirjak,
We have made few changes (in v1.11.5) related to timeout settings and also upgraded its okhttp library to version 4.9.3 (Vulnerability CVE-2021-0341 was fixed in v4.9.2).
Please re-validate your use case and let us know, if you still face any issue.

Hi @czirjak,
We assume that the issue might have been resolved based on above comment.
We are closing this ticket for now.
Please let us know in case of any further queries.
Thank you.


[Bug]: Auto Save

I have

[X] updated to the latest version of Inner Ink
[X] confirmed that this issue is not a duplicate

Steps to reproduce
Open application -> Type something in the second textarea at home page -> Reload application or change selected day
Expected behavior
The value of the second textarea should be the same as before the reload
Actual behavior
The last change is not saved. By change, I mean any character updated (typed or deleted) or some content updated (cut or pasted)
Workarounds
Before quitting the application or changing the selected day using the date picker or a keyboard shortcut, if you have changed the content of that day's entry, insert a space. This will make the last change a space insertion, and the previous changes will be saved.
Inner Ink Version
v1.3.0
Which operating systems have you used?

[X] Windows
[ ] MacOS
[ ] Linux

Code of Conduct

[X] I agree to follow this project's Code of Conduct

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Autoloader issues with extension that uses own autoloader

I have a project with an extension that uses its own composer autoloader (and vendor folder). This worked fine until the vendor folder was included in Symphony, which simplified the autoloading. (Before this commit, Symphony obviously used its own autoloader in my installation, because there was no vendor folder for Symphony at all.)
But now autoloading of the extension is completely broken.
Is it not possible to have two autoloaders (and vendor folders) in one project?
I would really like to keep the extension as a subproject, separate from Symphony (and Symphony's autoloader).

I did a quick test with 2.6.0 and the CommonMark extension, which also uses its own vendor folder and autoloader. I didn't run into any issues at all, so I guess the problem is something else.

I will take a look at how the CommonMark extension does it! Maybe I can find a significant difference.

I will take a look at how the CommonMark extension does it! Maybe I can find a significant difference.

FYI... I had to require the autoloader in the text formatter instead of the extension driver, but also included it in the extension driver for testing purposes, with no issues.

LOL, I found it!
My extension used a relative path like require_once 'vendor/autoload.php';. Changing that to require_once EXTENSIONS . '/extension_name/vendor/autoload.php'; solved it!

Thanks, Jens, for the quick feedback!

I recently ran into another issue with extensions and composer autoloading. It's not a core issue, and not specific to one extension, so no idea where to discuss this. Any suggestions?

and not specific to one extension

That would be here then...


Fix "undefined reference to `net_addr_pton'" error.

socket.h includes net_ip.h which declares net_addr_pton, however it is not defined when CONFIG_NET_RAW_MODE=y.
See this thread for reference https://devzone.nordicsemi.com/f/nordic-q-a/48792/function-net_pton---compiling-issue-on-macos/

Found the following issues, please fix and resubmit:
Gitlint issues
1: UC2 Body does not contain a 'Signed-off-by:' line
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "Fix "undefined reference to `net_addr_pton'" error."
3: UC4 Line exceeds max length (110>72): "socket.h includes net_ip.h which declares net_addr_pton, however it is not defined when CONFIG_NET_RAW_MODE=y."
Identity/Emails issues
f38b1209ea09e861c625dccde69c85e374ba3869: author email (Gordon Klaus<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.

Hi @gordonklaus could you address the gitlint issues?

@gordonklaus I think that this change should target upstream Zephyr repository. We aim to minimize differences between upstream and fw-nrfconnect-zephyr.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 13 committers have signed the CLA.:x: hakonfam:x: nordic-krch:x: ioannisg:x: gordonklaus:x: rlubos:x: ChristopherBittner:x: sigvartmh:x: SebastianBoe:x: thst-nordic:x: ru-fu:x: oyvindronningstad:x: jtguggedal:x: nvlsianpuYou have signed the CLA already but the status is still pending? Let us recheck it.

@rlubos I tried to reproduce this upstream but ran into too many unrelated errors along the way and gave up.
In any case, I think I identified the issue as being related to this larger one.


Set article to flex with justify-content: space-between and align-ite…

…ms: center, also add margins within article.
Ben, take a look and let me know what you think. I am open to any modifications.  Thanks!

:shipit:


descendants swollen vegetative cell

has  no descendants
I expected,
viable swollen vegetative cell
inviable swollen vegetative cell
swollen spherical vegetative cell
(I thought has_parts were displayed as descendants now?)

Amended xp defs to use has_part 'swollen vegetative cell' instead of 'swollen cell'. That should sort it.

edit file: fd602879fa65355870ae8d5088ae34201572015f
release: 181b3899dabcbb4162464ba5e7afb857bd6e6776


Use Cilium with CAPA

Story
-As a cluster admin, I want to use Cilium instead of aws-cni on Cluster API for AWS clusters in order to have a flexible Kubernetes network solution.
Background
Cilium is currently used on:

CAPG;
CAPO;
Vintage AWS management clusters;

The plan is to replace aws-cni with Cilium in the AWS v18.0.0 release for vintage workload clusters.

https://github.com/giantswarm/default-apps-aws/pull/34 to use cilium with CAPA, there might be still need for some cleaning up

done,


e2e: test should always pull latest image

We might not use versioned image in test, e.g. nightly build dev image.

LGTM


Considering:  Change default to NOT use pg_dump

Details
:warning:  Breaking Change Proposed :warning:
I expect the Experimental designation will be removed from --append mode in the near(ish) future, either late 2022 or early 2023.  I am considering making --append the default recommendation.  With that change, it would be nice to not have to always include --skip-dump if that's the recommended / most common method used.  Being Pre 1.0, if this change is going to be made now is the time to do it.
Currently the default is to run pg_dump by default, and specify when you don't want it.  Running pg_dump doesn't make much sense when using --append.  The purpose of the .sql is to load to your databases.  With append this shouldn't be necessary.
The process to export the .sql file would use a new option --pg-dump.
Feedback welcome
If you have thoughts on this in either direction let me know. I'm not dedicated to making this change if it will cause a lot of friction with existing users.  My main motivation for this is that I think users will appreciate being able to use --append and that will gain traction.

Asking for feedback.
https://mastodon.social/@rustprooflabs/109357178475099314
https://twitter.com/RustProofLabs/status/1593094106158628869

totally makes sense to me, besides it can always be executed with docker exec when needed

This change has been made, currently in the dev branch and :dev Docker image.


[ZEPPELIN-3014] NPE bug fix and Error message enhancement with Kylin Interpreter

What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html
What type of PR is it?
Bug Fix
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-3014

How should this be tested?

Setup Travis CI as described on https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
Use existing unit tests in kylin module.

Screenshots (if appropriate)
before: NPE when result set is empty

after: no NPE when result set is empty, just an empty table

before: when query fails, only error code is returned, no error message

after: when query fails, both error code and error message are displayed to users

Questions:

Does the licenses files need update? No.
Is there breaking changes for older versions? No.
Does this needs documentation? No.

@zjffdu @felixcheung can you please review? I have rebased and created this new pull request. [was https://github.com/apache/zeppelin/pull/2634]. Thanks for your time!

Thanks @jinxliu  does kylin has some utility class for integration test ? Very few people in community has experience of kylin, it is better to have test for the bug fix and avoid regression

@zjffdu sure, kylin interpreter has unit test class, and I will add the test when result set is empty.

@zjffdu please review. Thanks.

Thanks @jinxliu wait for CI pass and will merge if no more comments

@zjffdu the CI checks seems to get stuck, even after rebase.

@zjffdu Thanks for your comments and review. There seems something wrong with validating pull request.

@yiming187  I have made the changes and updated pull request. You can review now.


Add models for v0.2

Which models are being added for this PR?

These were the models we reviewed during yesterday's meeting. So the new test model sets are:
Primitive_Attribute
Texture_Sampler
We've also split one of the previous sets in to new sets:
Material_Alpha
Material
And all of the test model sets have had individual models added/removed.

These properties are not resulting in visible changes.
Material

Normal Scale
Occlusion Strength

Material-Alpha

Blend vs Mask
Mask w/ factor

Closing. v0.2 has been committed directly.


10-bit support

Is there 10-bit video support?

Sorry, currently we did not support 10-bit videos as we developed this algorithm mainly for compressed 8-bit videos


Bug: Import paths in the generated typescript schema file contains backslashes when codegen is run on Windows 11

Hello! I've been trying out this project this weekend. Really interesting, nice work!
I noticed that the import paths in the generated typescript schema contains backslashes. Here's what mine look like:
import { count as queryCountResolver } from "./modules\\api-tester";
import { files as folderFilesResolver } from "./modules\\file";
import { dir as queryDirResolver } from "./modules\\file";
import { error as queryErrorResolver } from "./modules\\api-tester";
import { greeting as queryGreetingResolver } from "./modules\\api-tester";
import { increaseCount as mutationIncreaseCountResolver } from "./modules\\api-tester";

I ran into this when I tried to bundle my graphql server using tsup, which then outputs an error due to this path format:
ESM Build start
Error: R] Could not resolve "./modules\\api-tester"

    src/schema.generated.ts:2:44:
      2 │ import { count as queryCountResolver } from "./modules\\api-tester";
        ╵                                             ~~~~~~~~~~~~~~~~~~~~~~~

Error: R] Could not resolve "./modules\\file"

    src/schema.generated.ts:3:45:
      3 │ import { files as folderFilesResolver } from "./modules\\file";
        ╵                                              ~~~~~~~~~~~~~~~~~

ESM Build failed

I'm very curious why grats outputs imports like this!

Interesting, I haven't seen this before. May I ask which operating system you are using?

I am using Windows 11. I've been comparing with the codegen results in my CI (which runs ubuntu) and my CI generates typescript with proper import paths. So it does indeed seem to depend on OS. So could this be considered a bug perhaps?
I have a CI step that asserts that the codegen is up to date, which currently yields false negatives if I submit code that was generated on windows machine.

Got it. Yeah, this sounds like a bug. I'll try to investigate. We can use this issue to track it.

Quick update. Still trying to get a windows environment working where I can look at this. If this is blocking you let me know and I can brainstorm some workarounds.

I worked around it by adding a simple transformer to esbulld for now, 😆: https://github.com/kasper573/yas/blob/master/apps/graphql-server/tsup.config.mjs#L15
So no worries, not blocked!

I've landed a change which I think addresses the slash issue. I think we might still be writing files with different line endings on different platforms but I think Git tries to normalize those?
Can you try<EMAIL_ADDRESS>and see if it resolves the issue for you?

@captbaritone Yes, it seems to work as expected! Yeah I think the line endings might still be a problem theoretically, but you're right that git normalizes them for most users. I don't have a problem with line endings, but some users may use git with a different configuration/workflow so it could still be a problem for some.

@kasper573 Thanks for confirming. I've opened #136 to track line endings.


Add hello-world examples

Pivotal Tracker: #103042238

added average and variance function as a hello-world example
added simple logistic regression as a iterative example

Closing this as we ended up with a duplicate of commit a184a8a


fix(app): labware setup modal updates to match designs

Overview
updates the labware modal that is shown when a piece of labware is tapped on the deck map during protocol setup to match the designs
closes RAUT-530

Test Plan
opened the deck map from the labware setup page, tapped a labware, verified the modal style matches the designs and outside click behavior works as expected

Changelog

switched out LegacyModal for Modal in ProtoclSetupLabware for the labware details modal
made use of the LocationIcon component instead of the text based location display

Review requests
ensure the PR addresses the noted issues in RAUT-530

Risk assessment
Low

@koji I have added the nickName to the labware details modal. Ready for a second review

lgtm 🎉

awesome, would you mind moving the ticket in Jira to "Done" for me? It seems mine and Eric's access to Jira and Slack has been revoked a bit too early. Much appreciated 🙏

oh... and merging this? I can't do that either now

oh... and merging this? I can't do that either now

😭 😭 😭
@jgbowser
Sure I'll update the jira ticket and merge this PR into edge.
Really appreciate your great work!


Overlapping array copy

Fixes Bug 7484,

Something is wrong here. This pull request is showing stuff from the your std.algorithm.all pull request.  My guess would be that you didn't use a clean branch for this pull request.

I have no clue how that happened.    There is some weirdness in how I got there, but the end result (the diff) is what I intended.

On second thought, closing, opening a new one...


403 instead of 401 when there's no JWT

Bug description
I have the following configuration in my namespace:
apiVersion: "security.istio.io/v1beta1"
kind: "AuthorizationPolicy"
metadata:
  name: "standard-istio-jwt-policy"
  namespace: development
spec:
  selector:
    matchLabels:
        jwt-validation: "true"
  rules:
    - from:
      - source:
          requestPrincipals: ["*"]
    - to:
      - operation:
          paths:
            - /actuator/health
            - /actuator/prometheus
            - /health
            - /metrics
            - /nginx-health
            - /oauth/health
            - /app-health
---
apiVersion: "security.istio.io/v1beta1"
kind: "AuthorizationPolicy"
metadata:
  name: "standard-istio-jwt-policy-system"
  namespace: development
spec:
  selector:
    matchLabels:
      jwt-validation: "true"
  rules:
  - from:
      - source:
          namespaces: ["istio-system", "kube-system", "infrastructure"]
---
apiVersion: "security.istio.io/v1beta1"
kind: "RequestAuthentication"
metadata:
  name: "standard-istio-jwt-policy-tmp"
  namespace: development
spec:
  selector:
    matchLabels:
      jwt-validation: "true"
  jwtRules:
    - issuer: "https://my-keycloak/auth/realms/dev"
      jwksUri: "http://my-keycloak/auth/realms/dev/protocol/openid-connect/certs"
      forwardOriginalToken: true

When making a simple HTTP request to a labelled pod from another pod in the same namespace with no Authroization header (using curl) I get a 403 instead of a 401 as expected.
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Envoy proxy should respond with a 401 Unauthorized because there is no Authorization header.
Steps to reproduce the bug
Use the above configuration (or similar) and execute something like curl -v http://my-labelled-service/
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
Istio: 1.5.8
k8s: v1.14.9-eks-f459c0
helm: v2.14.3
How was Istio installed?
Modified Helm chart. mTLS fully enabled in permissive mode, SDS deployed to provide certs.
Environment where bug was observed (cloud vendor, OS, etc)
AWS EKS

Hi Gerard, I think it because the jwksuri your included is not valid. https://istio.io/latest/docs/ops/common-problems/security-issues/ here describes the jwksuri should be able to be opened in a browser. Thanks!

I've replaced the real URI for security reasons. The actual URI is an externally accessible one in our environment. It can definitely be opened using either a browser or accessed from inside a pod using curl.

When making a simple HTTP request to a labelled pod from another pod in the same namespace with no Authroization header (using curl) I get a 403 instead of a 401 as expected.
Envoy proxy should respond with a 401 Unauthorized because there is no Authorization header.

It's expected to get 403 in this case. A request without authorization header is allowed, 401 is only returned if the jwt token is invalid. See https://istio.io/latest/docs/concepts/security/#request-authentication

This 401 is expected per https://github.com/istio/istio/issues/26559#issuecomment-675682440, I am going to close this issue. Please feel free to reopen.

e jwksuri y

for me using the config of
[
jwtRules:

issuer<EMAIL_ADDRESS>jwksUri: "https://raw.githubusercontent.com/istio/istio/release-1.8/security/tools/jwt/samples/jwks.json"
]
https://preliminary.istio.io/latest/docs/tasks/security/authentication/authn-policy/

works...
when i use my keycloak instance that is on the same cluster (since i use it on k8s on my machine) it gives the error :
### Jwt issuer is not configured
i wonder is a config on keycloak


Cannot find module 'angularfire2/interfaces'

Hello, when i try to run the "ionic" example, i get:
typescript: node_modules/angularfire2-offline/database/database.d.ts, line: 2
Cannot find module 'angularfire2/interfaces'.

L2:  import { FirebaseListFactoryOpts, FirebaseObjectFactoryOpts } from 'angularfire2/interfaces';

For some reason, FirebaseListFactoryOpts is located at 'angularfire2/database/interfaces' not on 'angular/interfaces'
Im using:
<EMAIL_ADDRESS><EMAIL_ADDRESS>I manage to fix the code by correcting the imports, however i don't know how to do a pull request

Hi @netomarchiori, thanks for posting!
I was able to reproduce the issue and have updated the example to avoid the error. It looks like angularfire2 at version 4.0.0-rc.2 resulted in type erros but version 4.0.0-rc.0 works weel so I pinned the version.
Steps to test change
Following these steps should now no longer produce the type errors you mentioned:

git clone https://github.com/adriancarriger/angularfire2-offline.git issue-62
cd issue-62/examples/ionic
npm install
npm run ionic:serve

Let me know if you have any questions. Thanks! 👍

spot on! worked as expected! thanks @adriancarriger


solved issue regarding login

What is the change?
Typos corrected in user router to load the login page.
Related issue?
close: #644
How was it tested?
Tested it on my local machine and worked fine.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Did you lint your code before making the Pull Request?
[] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
https://user-images.githubusercontent.com/55927827/114062119-c6191580-98b4-11eb-8a17-9635d7e9a705.mp4

Hey @Pranav016, Is it possible to add the labels now and would that make any difference in my merged PR count because GSSOC authorities told me that the maintainer hasn't added labels to the PR that's why I haven't got the points for this PR.

Hey @Pranav016, Is it possible to add the labels now and would that make any difference in my merged PR count because GSSOC authorities told me that the maintainer hasn't added labels to the PR that's why I haven't got the points for this PR.

No it won't make any difference, added 👍
Thanks for reminding, must have forget coz was busy fixing bug yesterday


[bugfix] bugfix hvd bug

limit hvd gpu settings to hovorod related strategies

 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.


Make packages installable (binary)

Not sure if this is better to bring up here or in deno's repo, but I'd like to be able to host an installable (not 'addable') package on jsr.io, i.e., deno install @example/my-runnable-package.
Maybe this is already possible but not documented which URL I would need to install from,  and it's as easy as marking a package as installable which updates the JSR installation instructions:
{
  "version": "1.0.0",
  "installable": true,
  "exports": "./main.ts",
  "imports": {
    "@example/package": "jsr<EMAIL_ADDRESS>  }
}

In Deno you can install a JSR package with deno install jsr:@example/package.

@lucacasonato Thank you! Probably just starting to work with Deno here. I personally would feel it would be nice to have jsr: be the default inferred package manager for deno install, but if that's not on the table this issue can be closed :)

In Deno you can install a JSR package with deno install jsr:@example/package.

This is great, but for me part of the appeal of JSR is that it just works with all of the runtimes. Is it possible to publish an installable/binary in a way that it can be npm installed, then run with npx <name> or <name> (if -g is used)?


Possible change in documentation for Image Bundling

mdx-bundler version: 4.0.0
node version: 14.16.1
yarn version: 1.22.10

Relevant code
const result = await bundleMDX(markdownSource, {
  cwd: path.join(process.cwd(), "/posts"),
  esbuildOptions: (options) => {
    options.outdir = path.join(process.cwd(), "/public/generated");
    options.loader = {
      ...options.loader,
      ".png": "file",
    };

    options.publicPath = "/generated/";

    options.write = true;

    return options;
  },
});

What happened:
I followed the bundling images guide in the documentation. See my bundleMDX function above. All my images will be bundled into the notouch/ directory under public/.
When you build with this config, you might get these errors:

Errors
(1)
> Build error occurred
Error: Export encountered errors on following paths:
        /
    at /.../node_modules/next/dist/export/index.js:31:1106
    at async Span.traceAsyncFn (/.../node_modules/next/dist/telemetry/trace/trace.js:6:584)
    at async /.../node_modules/next/dist/build/index.js:43:49
    at async Span.traceAsyncFn (/.../node_modules/next/dist/telemetry/trace/trace.js:6:584)
    at async /.../node_modules/next/dist/build/index.js:25:1475
    at async Span.traceAsyncFn (/.../node_modules/next/dist/telemetry/trace/trace.js:6:584)

(2)
Error: ENOENT: no such file or directory, unlink '/.../public/generatedimages/_mdx_bundler_entry_point.js'

(3)
ReferenceError: Component is not defined
    at eval (eval at getMDXComponent (/blog/node_modules/mdx-bundler/dist/client.js:34:50), <anonymous>:3:2)
    at getMDXComponent (/blog/node_modules/mdx-bundler/dist/client.js:35:10)
    at Page (/blog/.next/server/pages/[code]/[slug].js:4044:55)
    at d (/blog/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:33:498)
    at bb (/blog/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:16)
    at a.b.render (/blog/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:42:43)
    at a.b.read (/blog/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:41:83)
    at exports.renderToString (/blog/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:52:138)
    at Object.renderPage (/blog/node_modules/next/dist/next-server/server/render.js:54:854)
    at Function.getInitialProps (/blog/.next/server/pages/_document.js:721:19)

I got them around 50% of the times I ran yarn build
Reproduction repository:
https://github.com/ninest/next-mdx-bundler-images-bundling-issue
The important file is mdx.js at https://github.com/ninest/next-mdx-bundler-images-bundling-issue/blob/main/lib/mdx.js#L42
(None of the blog mdx files have images, but the error still occurs)
A few things to note:
When I use remark-mdx-images, I get the error:

Error with remark-mdx-images
Error: Build failed with 1 error:
node_modules/esbuild/lib/main.js:863:33: error: [plugin: esbuild-xdm] Cannot read property 'start' of undefined
    at failureErrorWithLog (blog/node_modules/esbuild/lib/main.js:1443:15)
    at blog/node_modules/esbuild/lib/main.js:1125:28
    at runOnEndCallbacks (blog/node_modules/esbuild/lib/main.js:915:63)
    at buildResponseToResult (blog/node_modules/esbuild/lib/main.js:1123:7)
    at blog/node_modules/esbuild/lib/main.js:1230:14
    at blog/node_modules/esbuild/lib/main.js:606:9
    at handleIncomingPacket (blog/node_modules/esbuild/lib/main.js:703:9)
    at Socket.readFromStdout (blog/node_modules/esbuild/lib/main.js:573:7)
    at Socket.emit (events.js:315:20)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23) {
  errors: [
    {
      detail: TypeError: Cannot read property 'start' of undefined
          at onload (file://blog/node_modules/xdm/lib/integration/esbuild.js:87:32)
          at callback (blog/node_modules/esbuild/lib/main.js:863:34)
          at runMicrotasks (<anonymous>)
          at processTicksAndRejections (internal/process/task_queues.js:93:5)
          at async handleRequest (blog/node_modules/esbuild/lib/main.js:649:30),
      location: [Object],
      notes: [Array],
      pluginName: 'esbuild-xdm',
      text: "Cannot read property 'start' of undefined"
    }
  ],
  warnings: []
}
 > node_modules/esbuild/lib/main.js:863:33: error: [plugin: esbuild-xdm] Cannot read property 'start' of undefined
    863 │               let result = await callback2({
        ╵                                  ^
    at onload (file://blog/node_modules/xdm/lib/integration/esbuild.js:87:32)
    at callback (blog/node_modules/esbuild/lib/main.js:863:34)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async handleRequest (blog/node_modules/esbuild/lib/main.js:649:30)

   node_modules/esbuild/lib/main.js:733:22: note: This error came from the "onLoad" callback registered here
    733 │         let promise = setup({
        ╵                       ^
    at setup (file://blog/node_modules/xdm/lib/integration/esbuild.js:35:11)
    at handlePlugins (blog/node_modules/esbuild/lib/main.js:733:23)
    at Object.buildOrServe (blog/node_modules/esbuild/lib/main.js:1018:7)
    at blog/node_modules/esbuild/lib/main.js:1742:17
    at new Promise (<anonymous>)
    at Object.build (blog/node_modules/esbuild/lib/main.js:1741:14)
    at Object.build (blog/node_modules/esbuild/lib/main.js:1617:51)
    at bundleMDX (blog/node_modules/mdx-bundler/dist/index.js:192:33)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async getMDX (webpack-internal:///./lib/mdx.js:33:18)
    at async getStaticProps (webpack-internal:///./pages/blog/[slug].js:86:7)
    at async renderToHTML (blog/node_modules/next/dist/next-server/server/render.js:28:1780)
    at async blog/node_modules/next/dist/next-server/server/next-server.js:112:97
    at async __wrapper (blog/node_modules/next/dist/lib/coalesced-function.js:1:330)

Error: Build failed with 1 error:
node_modules/esbuild/lib/main.js:863:33: error: [plugin: esbuild-xdm] Cannot read property 'start' of undefined
    at failureErrorWithLog (blog/node_modules/esbuild/lib/main.js:1443:15)
    at blog/node_modules/esbuild/lib/main.js:1125:28
    at runOnEndCallbacks (blog/node_modules/esbuild/lib/main.js:915:63)
    at buildResponseToResult (blog/node_modules/esbuild/lib/main.js:1123:7)
    at blog/node_modules/esbuild/lib/main.js:1230:14
    at blog/node_modules/esbuild/lib/main.js:606:9
    at handleIncomingPacket (blog/node_modules/esbuild/lib/main.js:703:9)
    at Socket.readFromStdout (blog/node_modules/esbuild/lib/main.js:573:7)
    at Socket.emit (events.js:315:20)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23) {
  errors: [
    {
      detail: TypeError: Cannot read property 'start' of undefined
          at onload (file://blog/node_modules/xdm/lib/integration/esbuild.js:87:32)
          at callback (blog/node_modules/esbuild/lib/main.js:863:34)
          at runMicrotasks (<anonymous>)
          at processTicksAndRejections (internal/process/task_queues.js:93:5)
          at async handleRequest (blog/node_modules/esbuild/lib/main.js:649:30),
      location: [Object],
      notes: [Array],
      pluginName: 'esbuild-xdm',
      text: "Cannot read property 'start' of undefined"
    }
  ],
  warnings: []
}

But everything seems to work fine without the remark plugin. Am I doing something incorrectly? Is it something to do with the first argument of xdmOptions being vfile? When options is the second argument, I'm getting the error TypeError: Cannot read property 'rehypePlugins' of undefined. (I'm following this section)
Solution:
Use a custom path for each mdx file. I've already made the change at https://github.com/ninest/next-mdx-bundler-images-bundling-issue/blob/main/lib/mdx.js#L42
In esbuildOptions, change
options.outdir = path.join(process.cwd(), `/public/generated`);
...
options.publicPath = "/generated/";

to
options.outdir = path.join(process.cwd(), `/public/generated`, filepath);
...
options.publicPath = filepath;

I am not sure why this fixes it, but I believe the explanation is

This prevents images from later builds overwriting earlier ones. You have to remember that each call to bundleMDX is isolated so esbuild can't tell if the image it wants to overwrite is from an another build or from the last time your site was built.

https://www.arcath.net/2021/04/images-with-mdx-bundler
Should the documentation be changed to show that the images for each mdx file should be at a custom path? I spent quite a while figuring this out since the error messages (shown under the What happened heading) weren't very clear

@ninest Each time you call bundleMDX a new build pipeline is created which has no knowledge of what other mdx files have done to the output dir.
Looks like with putting them all in the same directory the process of reading in and deleting the bundle is getting clobbered by async. It should work if you ran everything syncronously but that would ruin the performance of any site builder.
I'll look at the documentation as it probabbly should warn people about this effect.


Update exercise-tracker.md

fix: Incomplete argument in test #50135
Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

fix : Incomplete argument in test #50135
I have fixed an open issue.
I am a newbie in Open Source ,if there are mistakes please correct me.
I am open for learning.

Hi there,
Thanks for creating this pull request.
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
Since you are new here, please slow down and read our contributing guidelines, as we see that you may still need to catch up on a few things.

Here are some examples (expand)

Do not edit files directly on GitHub – while you can, it's not a good idea.
Typos and formatting errors can break the tests.

Use the correct way to link issues.
Add the issue number only in the description of the PR by updating the XXXXXX. Do not just add issue numbers everywhere and anywhere you feel like.

Keep mentions and review requests to a minimum.
We understand you are excited about contributing, and our maintainers will get back to you when they can.

Do not work directly off your main branch.
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.

Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
Happy Contributing.

@Anu790j, thank you for trying to solve the issue, the issue is solved by another PR, so I am closing this PR.


docs: Fixed API Playground button CSS

This fix will make the API Playground CTA in the docs render correctly. Based entirely on https://github.com/dagger/dagger/pull/4043
Signed-off-by: Vikram Vaswani<EMAIL_ADDRESS>

Fixed in #4043


Live Lambda Golang Context Deadline Issue

When using the lambda context.Context in the handler in a deployed environment there are no issues. However when running dev and leveraging live lambda I am getting a context deadline exceeded. Below is just a sample code.
func handler(
	ctx context.Context,
	request *events.APIGatewayProxyRequest,
) (events.APIGatewayProxyResponse, error) {
	isLocal := os.Getenv("IS_LOCAL")
	if isLocal == "true" {
		ctx = context.Background()
	}
	ctrl, err := controllers.NewUserController(ctx)
	if err != nil {
		return awsapigw.SendError(awsapigw.StatusServiceUnavailable, err.Error())
	}

	userID, err := awsapigw.GetParamPath("id", request)
	if err != nil {
		return awsapigw.SendError(awsapigw.StatusBadRequest, err.Error())
	}

	user, err := ctrl.GetUser(ctx, userID)
	if err != nil {
		return awsapigw.SendError(awsapigw.StatusBadRequest, err.Error())
	}

	return awsapigw.SendResponse(awsapigw.StatusOK, user)
}

func main() {
	lambda.Start(handler)
}

When leveraging the context from the handler in a deployed environment (non live lambda) there are no issues. I was able to get live lambda to work by essentially ignoring the context from the handler and just creating my own context. I am leveraging the "IS_LOCAL" environment variable to do a catch and create a context catch but seems less than ideal. Here is the error below i get when passing the context down to dynamodb. With the lambda context I get a context deadline exceeded error. However when using the background context it works just fine with the live lambda.

Issue fixed in 2.0.26 release


[Proposal] Add Math Node

While toying around with Material Maker, I noticed that there was no math node, something that I rely upon in blender.  It takes two grayscale inputs and produces one grayscale output, and has a dropdown for the different math operations.  Some (such as Square Root) only use one of the grayscale inputs, and hide the second.  There's also a Clamp checkbox, which causes it to constrain the value to a range of 0 to 1.0.
Screenshot of the node in blender, plus all the different operations it supports:

Link to documentation for the math node: https://docs.blender.org/manual/en/latest/compositing/types/converter/math.html

I often Use Blender's math node for masks and procedral noise so this is a very important feature in my opinion.

Blender's nodes and Material Maker are very different tools. I'm not sure all those operations can be useful to create textures.
Could you please describe a few uses of the operators that are not already in the Blend node?
This, of course, is be a piece of cake to implement as custom node(s), so I'd rather provide a simple node with only useful operations.

well math node is primarily used for BW inputs such as roughness and bump, for example getting the average of two greyscale inputs by using an add and a divide math node.

To calculate the average you can use the Blend node. Which does not mean there won't be a Math node (started adding it already). ;)

Main operations in the Math node that I usually wind up using outside of the basic ones (Addition, Subtraction, Multiplication, Division) are Square Root, Inverse Square Root, Absolute, Minimum, Maximum, Less Than, and Greater Than.


Support page skipping / page_index pushdown for evolved schemas

Which issue does this PR close?
Closes https://github.com/apache/arrow-datafusion/issues/5104
Rationale for this change
See https://github.com/apache/arrow-datafusion/issues/5104
I want to turn on page index pushdown for all queries. I can't do that if it causes errors for queries across parquet files where the schema is not the same
What changes are included in this PR?
Fix a bug (I will describe inline)
Are these changes tested?
Yes
IN PROGRESS -- testing against https://github.com/apache/arrow-datafusion/pull/5099
Are there any user-facing changes?
Less bugs

@Ted-Jiang  and @thinkharderdev  I think I have finally fixed the bug with page index pushdown.
I think @Dandandan  had asked about the status of this project as well

Can we enable evolved_schema_disjoint_schema_filter and other tests with this PR too?

@Dandandan, I apologize,  but I don't understand this request

Can we un-ignore evolved_schema_disjoint_schema_filter and other tests with this PR too?

That test does not appear to be ignored on master (nor in this PR):
https://github.com/apache/arrow-datafusion/blob/07ae738b48b6001498a4b10e9750422f9d8e1b7f/datafusion/core/src/physical_plan/file_format/parquet.rs#L1257-L1259
I only found one instance of this test in the repo:
https://github.com/search?q=repo%3Aapache%2Farrow-datafusion evolved_schema_disjoint_schema_filter&type=code
I couldn't find any other #ignore'd test elsewhere in the repo that looked relevant.

@alamb
Ah ok, I apologize, the tests are not ignored indeed.
"Improved" question, does it fix those tests when setting enable_page_index to true?
    physical_plan::file_format::parquet::tests::evolved_schema_disjoint_schema_filter
    physical_plan::file_format::parquet::tests::evolved_schema_disjoint_schema_with_filter_pushdown
    physical_plan::file_format::parquet::tests::evolved_schema_intersection_filter
    physical_plan::file_format::parquet::tests::evolved_schema_intersection_filter_with_filter_pushdown

"Improved" question, does it fix those tests when setting enable_page_index to true?

Yes! 🎉  I verified that all CI passes with page index pushdown enabled by default  (when this PR change is included). Check out https://github.com/apache/arrow-datafusion/pull/5099. I should have mentioned that. Sorry


Enable macOS CI testing

Pull Request Test Coverage Report for Build 565710619

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.5%

Totals

Change from base Build 563920127:
0.0%

Covered Lines:
7

Relevant Lines:
8

💛  - Coveralls

Pull Request Test Coverage Report for Build 565710619

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.5%

Totals

Change from base Build 563920127:
0.0%

Covered Lines:
7

Relevant Lines:
8

💛  - Coveralls

Pull Request Test Coverage Report for Build 565710619

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.5%

Totals

Change from base Build 563920127:
0.0%

Covered Lines:
7

Relevant Lines:
8

💛  - Coveralls


Issue 5 create submit repair request page

Change Summary
Created a basic layout for the submit repair request page. Added input fields for Item, Item Type, Description of Item and a field for users to upload an image.
Change Form
Fill this up (NA if not available). If a certain criteria is not met, can you please give a reason.

[ ] The pull request title has an issue number
[ ] The change works by "Smoke testing" or quick testing
[ ] The change has tests
[ ] The change has documentation

Other Information
[Is there anything in particular in the review that I should be aware of?]

I was going to upload some of my own code - wrong pull request made.


Add "Support Organization" to RAM Role Model

We should maybe add the support organization as a separate section to the IDS RAM to have a common understanding. Maybe adding it to the role model of the RAM?
Originally posted by @HeinrichPet in https://github.com/International-Data-Spaces-Association/IDS-RAM_4_0/pull/130#discussion_r814807809

Will be part of the Rules document.


mqtt-streaming unit tasts fail a lot

Other connector tests fail some times too but mqtt-streaming is causing biggest issues.
This test is failing the most:
[info] - should produce a duplicate publish on the server given two client connections *** FAILED *** (6 seconds, 82 milliseconds)
[info]   java.lang.AssertionError: assertion failed: timeout (6 seconds) during expectMsg while waiting for ByteString(32, 2, 0, 0)

So just as a heads up, even with https://github.com/apache/incubator-pekko-connectors/pull/196 merged the tests are still flaky so it looks like we have to go to the drawing board again


Customizing the DELAY and T_HOLD Parameters in Verilog

Hey!
I have generated the Dual port Sky130 buffer of size 512 bytes and facing the problem of reading data from Port-1 due to time miss-match. I wish to hold the output data for at least 1 to 2 cycles. So I have to change the DELAY and T_HOLD parameters in the Verilog file generated.  These things will obviously change the behavior of the GDS generated file. So, could anyone please tell what changing, I have to do in my python script file in macros to customize these DELAY & T_HOLD values.
Thanks
Reference parameters of the Verilog Generated;
parameter DELAY = 100 ;  // Original was 3
parameter VERBOSE = 1 ;  // Set to 0 to only display warnings
parameter T_HOLD = 0 ;   // Original was 1

If you want it to hold more than one cycle, you will need to add an external flip flop or latch to your design.
These values are just arbitrary non zero simulation values and don't correspond to an actual delay. Timing estimates are in the .lib file for synthesis but are not very accurate unless you perform simulation characterization which is quite slow and not the default.


[.dev] Clicking 'sign-in' displays two loading elements

When I click the sign-in button, it displays two loading elements. Not sure if this is really much of a problem, but it feels a little weird.

That is intended by design. The navbar is indeed a separate component. I would swap the button loader with a skeleton animation to make it nicer.

@moT01 Agreed. We are removing the "sign in" button from the navigation anyway so this shouldn't be an issue. I'm going to go ahead and close this issue.


Detroit: Update Verified to Confirmed

Acceptance Criteria
On the public side, update the Verified Label to say Confirmed by property
Notes

Don't worry about Partners for now, just the public side label

Designs https://www.figma.com/file/D2fNPS5Ucll8uz7hyMUQGB/bloom-public-single-listing?node-id=1207%3A16233

LGTM


Archives – consider adjusting Level terminology

Rob,
Our archives team are completely confused by the LUX terminology in use to designate archival levels (Work Class: Set, etc.)
Is there any scope for asking the Getty to adding terms to AAT? 'Official' ISAG(g) terms are:

3.1.4 Level of description
Purpose: To identify the level of arrangement of the unit of description.
Rule: Record the level of this unit of description.
Examples:

Fonds
Sub-fonds
Series
Sub-series
File
Item

Tom

Display labels adjusted. Proposal to Getty to be submitted via LUX team


Create implementation base for unit testing message handling entitites

This PR introduces base classes for implementing unit tests for aggregates, aggregate parts, process managers, and event subscribers.
Overview
The following base classes are available for the developer to implement:

AggregateCommandTest for testing a pair of a command handler and event applier in Aggregate;
AggregateEventReactionTest for testing a single event reactor in Aggregate;
AggregatePartCommandTest for testing a pair of a command handler and event applier in AggregatePart;
ProcessManagerCommandTest for testing a single command handler in ProcessManager;
ProcessManagerEventReactionTest for testing a single event reactor in ProcessManager;
ProjectionTest for testing a single event subscription in Projection;
SubscriberTest for testing a single event subscription in EventSubscriber.

Expected
Assertions are done via ...Expected classes. Usage example:
@Test
@DisplayName("should handle a command")
void testCommand() {
    TestAggregate aggregate = createTestAggregate();
    expectThat(aggregate).producesEvent(TaskCreated.class, event -> {
        assertEquals(event.getName(), expectedName);
    }).hasState(state -> {
        assertEquals(state.getDescription(), expectedDescription);
    });
}

All available assertions are:

ignoresMessage() to assert that message was ignored by the entity;
hasState(Consumer<S> validator) to check if the message handler changed the state of entity;
producesEvents(Class<M>... eventClasses) to check if the message handler produced multiple events.
producesEvent(Class<M>, Consumer<M> validator) to check if the message handler produced a single event and to check its correctness;
producesCommand(Class<M> commandClass, Consumer<M> validator) to check if the message handler routed a single command and to check its correctness;
producesCommands(Class<?>... commandClasses) to check if the message handler routed multiple commands;
throwsRejection(Class<? extends Message> rejectionClass) to check if the message handler generated a rejection.

@armiol PTAL

@armiol PTAL

@armiol PTAL

@armiol PTAL.

@armiol PTAL

@vlad-lubenskyi LGTM.


Locals problems

Other localizations, except English default, return {field} without translate for validation form.

I couldn't reproduce it.
I found only an error in the Russian translation file codeigniter4/translations#49

I couldn't reproduce it.
I found only an error in the Russian translation file codeigniter4/translations#49

Yes, this problem is due to incorrect localization.
I fixed this and added some missing files:

Email.php
Encryption.php
RESTful.php
https://github.com/testideah2/Codeigniter-4-Russian-localization


Android: Keyboard crash when using external keyboards on Samsung tablets, strange behaviout as well

Describe the bug
When using an external bluetooth keyboard on Samsung tablets the Samsung keyboard crashes repeatedly (which does not crash the app), and strange text bugs occur:

Text is updated with delays, the TextBox hangs for a moment and then adds several already typed characters
During (especially fast) typing the cursor jumps back to some characters earlier and adds the text in the wrong place
The message "Samsung keyboard stopped working" pops up

We heard this from several users now but could reproduce it as well. It doesn't happen always but most of the time.
To Reproduce

Use a Samsung device (S6, S8, S9)
Add a TextBox example project
Connect an external bluetooth keyboard
type away

Logcat of the example project when the keyboard crash happened
Expected behavior
Text is showing when typed and no error dialogs appear
Avalonia version
11.1.3 and Nightly (11.2.999-cibuild0052241-alpha)
OS
Android
Additional context
All problematic devices have Pen support. I'm not knowledgeable enough in Android internals to know if this could be the culprit but I saw some messages regarding this in the logcat.

See https://github.com/AvaloniaUI/Avalonia/issues/15903#issuecomment-2168223588

The mentioned flags ConfigChanges.Keyboard | ConfigChanges.KeyboardHidden | ConfigChanges.Navigation are already in the MainActivity of our app but they don't seem to make any difference also not when I add them to the sample code. The crash still occurs and the wild jumping around of the cursor as well. Sometimes you must type a while, sometimes it happens instantly.


Spam classification examples

Would like to add some spam classification examples using ML Pack. Would this be useful? Some related work here

@bkmgit absolutely great idea

Started on this, see #112
A related issue is https://github.com/mlpack/mlpack.org/issues/28

Oops, no need to close this until we get #112 merged. (Hopefully soon!) :)


Fixes jumping topology on status screen.

Status.fromjson recreates() the whole topology structure. This commit
calls Status.fromjson only when the application changes.
TODO: the new code may update other properties than status (e.g., module
urls).

Current coverage is 41.18%

Merging #293 into master will decrease coverage by -6.96% as of 058a505

@@            master    #293   diff @@
======================================
  Files          219     365    +146
  Stmts         9045   13212   +4167
  Branches      1322    1660    +338
  Methods          0       0
======================================
+ Hit           4355    5442   +1087
- Partial        355     430     +75
- Missed        4335    7340   +3005

Review entire Coverage Diff as of 058a505

Powered by Codecov. Updated on successful CI builds.

+1


Added MultiValidator recipe.

Description
Added MultiValidator recipe.
MultiValidator is a Validator class that can show all failing validations for a field at once instead of stopping at the first Validator that fails.
See Issue How do I display more than one validation message at a time?
Type of change

[ ] Bugfix
[x] Feature

Checklist

[x] I have read the contribution guide: https://vaadin.com/docs/latest/guide/contributing/overview/
[x] I have added a description following the guideline.
[x] The issue is created in the corresponding repository and I have referenced it.
[x] I have added tests to ensure my change is effective and works as intended. (in a different repo)
[NA] New and existing tests are passing locally with my change.
[x] I have performed self-review and corrected misspellings.

Additional for Feature type of change

[ ] Enhancement / new feature was discussed in a corresponding GitHub issue and Acceptance Criteria were created.

 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.

Thanks @joelpop!

https://cookbook.vaadin.com/multi-validator


Arcane Archives Issue

The "Radiant Trove" from arcane archives mod cannot be broken.
Steps to reproduce the behavior:

Go creative mode.
Place trove.
Try to break it.
It doesn't break.

nevermind, im dumb. you have to use a special item to break them

lol


Promise.then (async)
(anonymous) @ VM1111:1

Will fix this Monday first thing.

Fixed by b7ca2a0.


[17.1.5] allows for selecting client cert as webgui certificate

Resulting in a SEC_ERROR_INADEQUATE_CERT_TYPE error in firefox.
I saw it in the drop down, I know it was a bad idea but I wanted to see if we catch this.
We don't, this sucks.

#1347 will have a graceful way of recovering from this automatically so no need to overcomplicate the validation.


Toolchain prefix mappings for NetBSD

These prefixes are for toolchains created by NetBSD's build.sh tools.

Thanks!


Append Text actions don’t handle combined objects correctly

When you mix manually entered text objects with certain other objects using the comma trick, only the first object selected is passed to the action.
To reproduce:

Create ~/Desktop/Input.txt
Invoke QS in text-entry mode
Enter a string, like “test”
Hit ⎋ then ,
Select a file
Run Append To… Input.txt

The string “test” will be appended, but not the path to the file. If you select the file first, then hit , and . to enter a string, only the file’s path will be appended.
This definitely happens with file objects and tags (in the third pane). Combining text-entry objects with URLs appears to work as expected.

The reason for this is that the two objects (a text object and a file object) have no intersecting 'types'.
See -(QSObject*)objectByMergingObjects;
That's what needs fixing.


Updated Homepage Font and Alignment Improvements

Unable to fix login & sign-up button bug with the limited time that I had. I discovered that the default value of Tabs Shadcn JSX was not updated when pressing those buttons.


Interactive UI design

hello there 👋,
i have viewed the web page , its functioning is quite good and impressive. but the UI design of the web page is not much blending with the page.
so, as a UI designer and a Front-end Developer i would love to work on the user interface of the page.

Thanks for your feedback - of course you can work on it. What changes do you envision?

I've noticed that most of the main content is clustered in one area. I can either rework the UI layout or make subtle adjustments. Considering the current layout, I believe applying a glassmorphism effect would greatly enhance the page. You can check out similar effects on google like here 🔗

Yes - a Glassmorphism design for this website would definitely look great too!


Slug automatically changed for published entry

When opening published entry to edit - slug is changed to match title:

when slug is empty (eg homepage doesn't have slug) - it will be auto generated for default locale.
"Don't edit slug when entry is published" configuration doesn't have effect for default locale.

This has been fixed in the new App version  https://github.com/pauloamgomes/contentful-better-slugs-app/tree/V1.0.0


Add element form components

Added forwarding lines for input-textarea, checkbox-radio, select, file, and tools in the forms SCSS index file. This allows for enhanced customization and control over the form components in the project.

[x] Checkbox & radio
[x] Input & textarea
[ ] Select
[ ] File
[ ] Tools

Imported relevant shared components and variables for the new form select styling defined in the 'scss/forms/select.scss' file. Defined a default color setting for the select component using shared form colors.


Use the gist title as the snippet default title instead of the description

Currently, the title of the snippet is the description of the gist, need to manually put the title as [title] to change the title.
gist title is the name of the first file in the gist, so can we use that in [title] by default?

Thanks for the suggestions:)
There are some concernings about using the first file name as the gist title.

The files in a gist are sorted alphabetically. It's hard to know which file is the "main" file.

Taken this into consideration, using the description as the title is more informative. Feel free to put your thoughts here :)

Maybe add an option to choose option or the first file name?
The main file seems to be the first file after sorting them alphabetically.

@raphaelfeng
The .leptonrc file provides different configuration options. If you are interested, just have a look at https://github.com/hackjutsu/Lepton/commit/5902b3b53cb90e5a395b42e4820a8b605611ffaf, which add the option to make new gist private.


[Doc Improvement][Updated-Click-to-Select]

Changed the word in point number 4

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/resources/bot-v3/bot-authentication/auth-flow-bot.md
77
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 5daebee:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/resources/bot-v3/bot-authentication/auth-flow-bot.md
:white_check_mark:Succeeded
View

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