Package was working in 7.3 but its stopped working

Before i start - LOVE this package from what i've seen until it broke! Great job!!! :)
My issue is its stopped working...
What i did:
I added the package via NuGet and created a test doctype called InfoBlock containing:
Textstring
MultilineText
ImageCropper
ContentPicker
Then added the data type Info Blocks and linked to InfoBlock
Added a property to a page and set to InfoBlocks type
On going to the content node (was an existing page): All the properties rendered ok and allowed entering of content
When i output the content in a web page the ImageCropper didn't contain the src property but did have the coordinates for the focus point.
I wondered if an issue with 7.3 umbraco so I created an image cropper property on its own (rather than nested type ) and that renders out fine so appeared to be an issue with Nested Content.
I then went to create some new types for nested content and now nothing will display in the property pages for nested content when editing a content node.
I even started a fresh with a rollback of the db but im not getting anything. All i get is the add button and the label for Item 1 - and no properties.
Not sure whats gone wrong.
Any ideas?
Thanks
Damian

I have also tried with a basic text item doctype and I get the same issue.

Also appears the drag & drop to set sort order gets ignored so poss a js issue.

Hey @djomen. I can't say for sure what's wrong as I haven't tried Nested Content in 7.3 yet, but one thing's for certain: Image Cropper does not work with Nested Content (and neither does Upload - see #27). You'll have to use a media picker and add crops to your media instead.
Alternatively you could consider using Archetype. It supports Image Cropper and Upload. Just a heads up if you switch: There's a known 7.3 issue with RTE's in Archetype. It's been fixed and a new release is imminent, but it's not out yet.

@djomen As @kjac says, the ImageCropper doesn't play nicely with Nested Content.  That looks like the cause of the main problem.
As for using simpler doctypes and nothing else displaying, is the ImageCropper also on there?
Are you getting any JS errors in your browser's dev-tools console? It might give some hint to the underlying issue.
Thanks, Lee.

Hi - Thanks - Yeah i had seen the issue with the upload and cropper so had removed it but cant get even simple NC working now. Not getting any issues in the console apart from a browserlink error - but don't think this is related.
Btw - archetype just had a release to fix it for 7.3

No @leekelleher i have removed the cropper. I just created a basic type with just a textbox and getting the same behaviour as above.  I have tried removing and re-installing the package also and still the same.
Also no console errors apart from a browserlink error. Was going to disable browserlink and try again.

Just installed into a clean 7.3 install with nuget and getting same issue with only a textfield on the nested type.

Nailed it!
If you don't put the properties on the nested content docType onto a tab  - i.e. if you leave on general properties - it just doesn't work and you get the behaviour above - no matter what tabs/aliases you put on the data type or end use doc type. Moved the properties onto a tab and voila!
Is this a bug or have i not used it correctly?

@djomen Yes! The properties need to be on a tab, (and generic properties are ignored).  I didn't spot this on your screengrab, doh! :tired_face:
This is intended behaviour, as a feature is that a single doctype can have multiple tabs and be used as multiple Nested Content blueprints.
We'll update our developer's guide to make this clearer.
Sorry for any headaches caused by this.

No probs - was just glad to get it working. :)  maybe a UI hint would also be good.

:+1: (on UI hint) Thanks!

I know this issue is closed, but I've just installed Nested Content for the first time (which is the work of genius by the way) and I am having this issue.
Now down to testing a doc type which contains only a single field, which is of Text Area editor type and I can't get the fields to render on the content node.
I'm on 7.4.2, and I'm not seeing any console errors.
The one difference I see between my version and the documentation is that in the data type I have created, I don't have a drop down for tabs, I have a text field for tab alias. In here I've tried various things but I suppose it's possible the tab alias is wrong.
R


prod: add types

[ ] need to check if it's working

Connected to Issue#50

Two ways:
declare namespace SimpleScrollBar {
  export function initEl (element: Element): void;
  export function initAll (): void;
  export function moveBar (e: Event): void;
}

export default SimpleScrollBar;

or
export default interface SimpleScrollBar {
  initEl (element: Element): void;
  initAll (): void;
  moveBar (e: Event): void;
}

@buzinas what do you think about adding TS?

ping @buzinas what do you think?

Thanks for your contribution! Sorry for taking so long to merge this.


Icon component only accepts string

Overview of the problem
Oruga version: [m0.8.12]
Vuejs version: [3.2.3]
OS/Browser: Chrome
Description
This has been discovered upon upgrading from 0.6.0 => 0.8.7, whereas, previously exactly the same approach was used without the issue described below present
We're passing component to programmatic configuration as per the below code:
import { ConfigProgrammatic } from '@oruga-ui/oruga-next'

import AppIcon from '~/components/AppIcon.vue'

ConfigProgrammatic.setOptions({
  iconPack: 'material-symbols-rounded',
  iconComponent: AppIcon,
  statusIcon: false,
  useHtml5Validation: false,
})

In <o-icon> component String is expected:
https://github.com/oruga-ui/oruga/blob/c328380cfe1a0256307bd8d741a35ffff90439e1/packages/oruga/src/components/icon/Icon.vue#L26
However, types config accounts for other types:
https://github.com/oruga-ui/oruga/blob/c328380cfe1a0256307bd8d741a35ffff90439e1/packages/oruga/src/types/config.ts#L43
Actual behavior
As a result, receiving warnings as per the below screenshot

Expected behavior
It would be beneficial for component prop to allow whatever can be passed to :is within <component>, e.g. not just String, but also Object and potentially function for dynamically imported scenarios
Please note that in the current version utilising any other approach apart from String still works as expected, however, throws warnings

@Nik-Weightmans thanks for this hint. Yes it's only a type problem, and we can change the type to allow objects and component instances as well, like other component props.


Adds other build suggestions to the index.ts file

🤔 What's changed?

Added buildSuggestionFromCucumberExpression and buildSuggestionsFromRegularExpression to suggestions index in order to expose them directly from the package import.
⚡ What's your motivation?
Allows access to the buildSuggestionFromCucumberExpression  function directly.

🏷 What kind of change is this?

:bank: Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)

♻ Anything particular you want feedback on?

📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct

This text was originally generated from a template, then edited by hand. You can modify the template here.

Thanks for the feedback @kieran-ryan. Updated imports with es-lint and updated changelog
Regarding the use case, for my own case it provides better granular control on how to actually build out the suggestion based on the type of expression I know I am working with. It also just allows users of the service to be able to access these functions without directly referencing in the node_modules.
Would be happy to raise a separate PR for use case section around both functions also.


Add URL remote

I tested it with simple project: https://github.com/rominf/lazydata_test

@rominf Awesome! I'm travelling this whole week, but as soon as I'm back I'll review and merge. Looks good looking at it quickly now!

It looks good, I've just added the smart download library to setup.py as well so it gets installed with the package in f321d9aa226ba8bcccac8982cc1e635d76550372.

@rstojnic, thank you for merging! Sorry, forgot to add to setup.py myself.

@rominf no worries - this is awesome work!!


Port the array-<IP_ADDRESS> package

https://github.com/ghc/packages-array

The newer version (<IP_ADDRESS>) was ported successfully.


[azd pipeline config] [azdo] provider config from azure.yaml is ignored

When setting pipeline: azdo configuration in azure.yaml, azd should use this provider by default, but it is using github.
The only way to set azdo is currently by dong azd pipeline config --provider azdo.

Seems to be a regression. Marking it as a blocker. Is this a minor fix?


Remove logging pkg

Coverage increased (+0.9%) to 49.579% when pulling d59493824a4a6c5078711a755a53913f8002b5aa on move-logging into 991bfa5d540d13904cfd2aaff794c8b25a1c450a on master.


Update the game over message

Update the game over message so people know how to play again!

all comments reviewed


Insights for own Stories

It would be great have the regular insights for a self story, like the List of people that had seen it, those who give a like, in polls, the ones who votes every option and that

Thanks for your feedback, we will definitely look into this feature in the next release.


Some questions about asyncProducer.input

Versions

Sarama
Kafka
Go

1.27.0
2.12-<IP_ADDRESS>
go1.15.3 linux/amd64

Configuration
What configuration values are you using for Sarama and Kafka?
	conf := sarama.NewConfig()

	conf.ClientID = cfg.ID
	conf.ChannelBufferSize = 512
	conf.Net.MaxOpenRequests = 1000000
	conf.Net.SASL.Enable = false
	conf.Producer.MaxMessageBytes = 1000000
	conf.Producer.RequiredAcks = sarama.WaitForAll
	conf.Producer.Timeout = 30 * time.Second
	conf.Producer.Partitioner = newHashPartitioner
	conf.Producer.Compression = sarama.CompressionGZIP
	conf.Producer.Return.Successes = true
	conf.Producer.Return.Errors = true
	conf.Producer.Flush.Bytes = 0
	conf.Producer.Flush.Messages = 200
	conf.Producer.Flush.Frequency = time.Duration(1000) * time.Millisecond
	conf.Producer.Flush.MaxMessages = 100000
	conf.Producer.Retry.Max = 6
	conf.Producer.Retry.Backoff = 10 * time.Second

	addrs := strings.Split(cfg.Brokers, ",")
	producer, err := sarama.NewAsyncProducer(addrs, conf)

Logs
NA
Problem Description

When concurrently sending message to async producer, partial message can't be send into the channel. I know there are multiple level channels: top-level => topic-level => partition-level, but the top-level channel asyncProducer.input has no buffer.
Should the fail be caused by that? If yes, is it expected or by design? And is there any better usage for concurrently sending messages? In my code, sending message to kafka can't block the business logic.

select {
	case producer.Input() <- m:
	default:
		err = errors.New("queue_full_fail")
	}

After adding another buffered-channel before asyncProducer.input, submitting message to asyncProducer works well. Is it possible to make the asyncProducer.input with buffer?
Is there any proposal for my conf and creating-client code?
If there is one topic is blocked, like because of too many messages, all topics in the same asyncProducer will be blocked, right? Is it expected? Any proposal for the multiple topics use case? Any further improvement for asyncProducer?

@dnwe could I confirm if there is any plan for this thread?

@xqzhang2015 sorry for the slow reply, this old issue must have slipped through the cracks
The AsyncProducer top-level is unbuffered, but the per-topic input channels are buffered. So in your config you've set conf.ChannelBufferSize = 512 which means the AsyncProducer will have a buffered channel of size 512 for the Input channel for each topic:
https://github.com/IBM/sarama/blob/24f12491720ed7974c2f131dae192040f6722e86/async_producer.go#L485-L486
So if one of these topic channels is filling up and then the AsyncProducer dispatcher func is blocking attempting to direct a message to one of those topic channels then the dispatcher won't be reading from the top-level Input and because of your select { ... } around your write to the Input channel, it will execute the default case because it couldn't immediately write to the channel.
Do you need to have that non-blocking behaviour for your call to input, or could you change the default: queue_full_fail case to be some time.After timeout? If not, then bumping ChannelBufferSize to more than 512 to permit more in-memory storage would be your solution

@dnwe thanks for your reply so much.
Do you need to have that non-blocking behavior for your call to input, or could you change the default: queue_full_fail case to be some time.After timeout?
Yes, we need the non-blocking behavior.
time.After timeout is a graceful approach. But it will new timer when producing each message, which seems not efficient(performance view, right?).


Pipeline support multiple protocols

Background
Easegress leverages pipeline for traffic orchestration, but the current pipeline implementation only supports HTTP protocol.
Although we have added the support of other protocols like MQTT, TCP/UDP with a workaround solution, it is very hard(if not impossible) to reuse filters originally designed for the HTTP protocol in these protocols.
Objective
Redesign/refactor the existing pipeline implementation, make it possible to support other protocols, and make it possible to reuse one type of filter in different protocols.

#352 MQTT Pipeline Develop Guide #352 contain information about MQTT pipeline and filter development. Include example yaml.


Unsupported

please tell me how to solve this problem

/duplicate https://github.com/microsoft/vscode/issues/151104


Create a fresh working dir for each k8s waiter-app container run

Changes proposed in this PR

Create a fresh working directory for each run of a K8s pod's waiter-app container.
Update the log-directory / log-url logic accordingly.

Why are we making these changes?
This allows us to keep track of our Waiter service instance logs across container restarts within a given Waiter-manged K8s pod.

Waiting on green build.


UofT-DSI | SQL - homework 1

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Added logical diagram
What did you learn from the changes you have made?
How to define relationships between tables
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
N/A
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Not much
How were these changes tested?
Ran some queries and looked at the data
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[x] I can confirm that my changes are working as intended

HW1: can't view png file, please resubmit

Sorry about that. Just uploaded the png and pdf. Thanks


Add prometheus.io/scrape: 'true' annotation to the azure-cns Kubernetes workload

Component (Azure NPM or Azure CNI):
azure-cns
Describe in detail the feature/behavior/change you'd like to see:
The azure-cns DaemonSet definition doesn't include a prometheus.io/scrape: 'true' annotation in the Pod template metadata block.
Adding this annotation to the Pod template will make it much less of an ordeal to configure 3rd party tools to scrape the IP utilization metrics from the service's metrics server.
Orchestrator(e.g. Kubernetes, Docker):
Kubernetes
Operating System (Linux/Windows):
N/A

@jcleavel do you mean when CNS is deployed in AKS? if not, where is the ds spec you're referring to?

Yes @rbtr, this is in regards to the CNS workload that is automatically installed in an AKS cluster.

@paulgmiller any reason for us not to add this?

No reason not to add thought it won't get you scraped by our internal stuff. (there was a brief time whre aks.prometheus.io/scrape was respected but that seems dead.

The latest AKS release notes states that your team has enabled the default annotation on the managed Cilium workload:

In Azure CNI powered by Cilium clusters, AKS now sets prometheus.io/port and prometheus.io/scrape annotations on the cilium-operator deployment as well as the prometheus container ports on the cilium and cilium operator manifests.

Both of these tools seem to serve equivalent purposes. Why not keep this part consistent?

We could have customers who are running that default kube-prometheus config and scraping anything that has the prometheus.io/scrape=true annotation. I can't add that annotation to one of my system components and start sending my metrics to their Prometheus instance without making it, in some way, opt-in. A worst-case scenario could be that the additional load knocks over their metrics/alerting infrastructure and makes them blind to a production outage.
The Cilium scenario is still in Preview, and we don't have the same potential impact when making the change there.
If I could go back and add the annotation to CNS from the beginning, I would. But it's a bigger ask to add it now.

Is there a way for users to set this annotation on the workloads in our individual clusters in a reliable/safe manner?

No, any changes to the AKS-managed components will be reverted to our target state.
We do already have the prometheus.io/port: "10092" annotation on CNS for internal use; could you add a scrape-config targeting that annotation?

I can give it a try.
I'll go ahead and close this. I think that I can work with my monitoring tool's support to get this path to work.
Thanks!


Add contribution file

Cloudflare

👋 @ytbigvinny27 - Thanks for the feedback about how we can make improvements with developers.cloudflare.com documentation. Closing this as a duplicate of work already in-progress.


refactor(localization): remove unnecessary dependency in localization packages

Description
To minimize package dependencies, I removed unnecessary package dependencies from the package.xml.
The selection of packages to remove was based on https://github.com/autowarefoundation/autoware/issues/3468#issuecomment-2235846503

Related links
https://github.com/orgs/autowarefoundation/discussions/5007
In this discussion, it is mentioned that "slimming down the container image sizes is the next urgent task."

How was this PR tested?
I deleted the build/ and install/ directories and confirmed that the build was successful.
Notes for reviewers
None.
Interface changes
Does not change.

Effects on system behavior
Does not change.

@a-maumau maybe our works are conflicted.  sorry  :sob:

To the maintainers,
since @a-maumau  has conducted more detailed testing, I have asked him to review this and share his detailed analysis.
Please wait your reviews until he has completed his review.

I have updated the script for checking some autoware_* dependency and the result is following:

updated result
--- Checking src/universe/autoware.universe/localization/autoware_landmark_based_localizer/autoware_landmark_manager/package.xml ---

--- Checking src/universe/autoware.universe/localization/autoware_landmark_based_localizer/autoware_ar_tag_based_localizer/package.xml ---
ament_index_cpp should be rather be marked as either <build_depend> or <test_depend>, not <depend>
autoware_lanelet2_extension seems not to be used

--- Checking src/universe/autoware.universe/localization/pose_initializer/package.xml ---

--- Checking src/universe/autoware.universe/localization/ekf_localizer/package.xml ---

--- Checking src/universe/autoware.universe/localization/pose_estimator_arbiter/package.xml ---
pcl_ros seems not to be used
pluginlib seems not to be used
ublox_msgs seems not to be used
yabloc_particle_filter seems not to be used

--- Checking src/universe/autoware.universe/localization/yabloc/yabloc_pose_initializer/package.xml ---

--- Checking src/universe/autoware.universe/localization/yabloc/yabloc_image_processing/package.xml ---

--- Checking src/universe/autoware.universe/localization/yabloc/yabloc_monitor/package.xml ---

--- Checking src/universe/autoware.universe/localization/yabloc/yabloc_common/package.xml ---

--- Checking src/universe/autoware.universe/localization/yabloc/yabloc_particle_filter/package.xml ---

--- Checking src/universe/autoware.universe/localization/autoware_pose_covariance_modifier/package.xml ---

--- Checking src/universe/autoware.universe/localization/twist2accel/package.xml ---

--- Checking src/universe/autoware.universe/localization/autoware_stop_filter/package.xml ---

--- Checking src/universe/autoware.universe/localization/gyro_odometer/package.xml ---

--- Checking src/universe/autoware.universe/localization/localization_util/package.xml ---
autoware_universe_utils seems not to be used
fmt seems not to be used
nav_msgs seems not to be used
sensor_msgs seems not to be used
std_srvs seems not to be used
tf2_ros seems not to be used
tf2_sensor_msgs seems not to be used
tier4_debug_msgs seems not to be used
tier4_localization_msgs seems not to be used

--- Checking src/universe/autoware.universe/localization/ndt_scan_matcher/package.xml ---
std_msgs seems not to be used

--- Checking src/universe/autoware.universe/localization/pose_instability_detector/package.xml ---
ament_index_cpp should be rather be marked as either <build_depend> or <test_depend>, not <depend>
tier4_debug_msgs seems not to be used

--- Checking src/universe/autoware.universe/localization/localization_error_monitor/package.xml ---
diagnostic_updater seems not to be used

--- Checking src/universe/autoware.universe/localization/geo_pose_projector/package.xml ---

--- Checking src/universe/autoware.universe/localization/pose2twist/package.xml ---

At least for compiling, we can follow the above result for erasing the unused dependency except for autoware_universe_utils in localization_util.
It seems it will cause
fatal error: diagnostic_msgs/msg/diagnostic_array.hpp: No such file or directory
   20 | #include <diagnostic_msgs/msg/diagnostic_array.hpp>

for some reason.

I have updated the dependencies based on a-maumau's review.  :pray:
And, I have reconfirmed that all packages build successfully again.
Now, this PR is ready for review :bow:


Unit Test for Java Core 728 - Replicator should not stop by missing r…

…evisions

All new six tests for verifying java core 728 fix are in PullerInternalTest.java
Removed Replication2Test.java and moved the test into ReplicationTest.java

This PR is not mergable. Could you please fix the PR?

Needs to solve conflict.

@pasin, Please review this PR again?


Remove try/catch from checkbounds in Bilinear Interpolation

Coverage decreased (-0.02%) to 78.66% when pulling 4cd185c5d977dc0632239f9f62ca779f358f0640 on mronian:fixbilinear into ee27cfd283021ad4087d5870fbc0b8cd7f861721 on timholy:master.


The example for GetPathOfFileAbove is an example for GetDirectoryNameOfFileAbove

The example for GetPathOfFileAbove is an example for GetDirectoryNameOfFileAbove.

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

ID: 82a1a083-bea0-e53e-dc9e-78f201ac1314
Version Independent ID: 904dae68-65cb-ec55-2fb3-1075ceaf6f1c
Content: Property Functions - Visual Studio
Content Source: docs/msbuild/property-functions.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @ghogen
Microsoft Alias: ghogen

It looks like it's just saying that the GetPathOfFileAbove is functionally equivalent to the given call to GetDirectoryNameOfFileAbove, so I'm not convinced this is a problem.

@paulomorgado Thanks for filing this issue. Does my previous comment clarify? I think we can close this, unless I'm not understanding the problem.

I don't think most of the examples, if any, are any exemplificative.
Better exemples would show an example file/directory structure and would show the values returned for the functions in the examples.


Re-organising order of menu items (not by naming)

Ok - apologies if this is somewhere (I'm sure its somewhere in the hugo docs if not this theme docs.. but I'm "man" looking..) - how do I reorder the menu items - without putting numbers on my categories?
I figured it was something to do with weight but I can't figure out how you set a section weight.. any pointers? (Sorry!)

 Course. e.g. this


[CPU] Enable masking for '+v9a' Arm CPUs.

SVE is a mandatory feature of v9a Arm CPUs so even if we don't specify +sve in target features (becase we don't want to take the scalable path within IREE), masking is available in the backend so we want to take advantage of this when passing v9a.

We are not adding pipeline tests but happy to add something simple you can think about

I've made a small suggestion, wdyt?

The problem is that we need to pass +v9a or +sve to the LLVM backend while we still generate fixed-length (i.e., Neon) code within IREE. If we mix v9a and sve flag query, we would need another flag to say "disable scalable vectors"... So I'm not sure what is best here.

I've made a small suggestion, wdyt?

The problem is that we need to pass +v9a or +sve to the LLVM backend while we still generate fixed-length (i.e., Neon) code within IREE. If we mix v9a and sve flag query, we would need another flag to say "disable scalable vectors"... So I'm not sure what is best here.

There's also -sve and my suggestion could be updated as:
 return  (hasV9aFeature(targetAttr) && !hasFeauture(targetAttr, "-sve")) || hasFeature(targetAttr, "+sve") || hasFeature(targetAttr, "+sve2");

This way hasAnySVEFeature would return false for +v9a -sve. Is that what you are after?  I'm probably missing something 🤔

We can't use -sve because that would pass -sve to the backend and then mask instructions won't be generated. If we want to put v9a within the SVE flag query, we should then add a flag to disable scalable vectorization (i.e., --iree-llvmcpu-enable-scalable-vectorization) while still using +v9a` feature flag.


Disable psp switch

Towards https://github.com/giantswarm/giantswarm/issues/28337
This PR adds a new switch for PSP disablement to transition to PSS and adds a KyvernoPolicyException for the silence cronjob
Checklist

[x] Update changelog in CHANGELOG.md.

Fixed violations for the silence cronjob:
17m         Warning   PolicyViolation      job/silence-operator-sync-28270770                        policy disallow-capabilities-strict/autogen-require-drop-all fail: validation failure: Containers must drop `ALL` capabilities.
17m         Warning   PolicyViolation      job/silence-operator-sync-28270770                        policy disallow-capabilities-strict/autogen-adding-capabilities-strict pass: rule passed
12m         Warning   PolicyViolation      job/silence-operator-sync-28270775                        policy disallow-capabilities-strict/autogen-adding-capabilities-strict pass: rule passed
12m         Warning   PolicyViolation      job/silence-operator-sync-28270775                        policy disallow-capabilities-strict/autogen-require-drop-all fail: validation failure: Containers must drop `ALL` capabilities.
12m         Warning   PolicyViolation      job/silence-operator-sync-28270775                        policy require-run-as-nonroot/autogen-run-as-non-root fail: validation error: Running as root is not allowed. Either the field spec.securityContext.runAsNonRoot must be set to `true`, or the fields spec.containers[*].securityContext.runAsNonRoot, spec.initContainers[*].securityContext.runAsNonRoot, and spec.ephemeralContainers[*].securityContext.runAsNonRoot must be set to `true`. rule autogen-run-as-non-root[0] failed at path /spec/template/spec/securityContext/runAsNonRoot/ rule autogen-run-as-non-root[1] failed at path /spec/template/spec/initContainers/0/securityContext/
12m         Warning   PolicyViolation      job/silence-operator-sync-28270775                        policy disallow-privilege-escalation/autogen-privilege-escalation fail: validation error: Privilege escalation is disallowed. The fields spec.containers[*].securityContext.allowPrivilegeEscalation, spec.initContainers[*].securityContext.allowPrivilegeEscalation, and spec.ephemeralContainers[*].securityContext.allowPrivilegeEscalation must be set to `false`. rule autogen-privilege-escalation failed at path /spec/template/spec/initContainers/0/securityContext/
7m58s       Warning   PolicyViolation      job/silence-operator-sync-28270780                        policy disallow-capabilities-strict/autogen-adding-capabilities-strict pass: rule passed
7m58s       Warning   PolicyViolation      job/silence-operator-sync-28270780                        policy disallow-privilege-escalation/autogen-privilege-escalation fail: validation error: Privilege escalation is disallowed. The fields spec.containers[*].securityContext.allowPrivilegeEscalation, spec.initContainers[*].securityContext.allowPrivilegeEscalation, and spec.ephemeralContainers[*].securityContext.allowPrivilegeEscalation must be set to `false`. rule autogen-privilege-escalation failed at path /spec/template/spec/initContainers/0/securityContext/
7m58s       Warning   PolicyViolation      job/silence-operator-sync-28270780                        policy require-run-as-nonroot/autogen-run-as-non-root fail: validation error: Running as root is not allowed. Either the field spec.securityContext.runAsNonRoot must be set to `true`, or the fields spec.containers[*].securityContext.runAsNonRoot, spec.initContainers[*].securityContext.runAsNonRoot, and spec.ephemeralContainers[*].securityContext.runAsNonRoot must be set to `true`. rule autogen-run-as-non-root[0] failed at path /spec/template/spec/securityContext/runAsNonRoot/ rule autogen-run-as-non-root[1] failed at path /spec/template/spec/initContainers/0/securityContext/
7m58s       Warning   PolicyViolation      job/silence-operator-sync-28270780                        policy disallow-capabilities-strict/autogen-require-drop-all fail: validation failure: Containers must drop `ALL` capabilities.


Test: Pruning can you force things to break?

Lets talk to Alex and Justin about good things to try for it -- we should do a manual test of this to run through the UI.

N/A


Document how to bring back this service if required

What
Documents how we would bring back the EV service, if we are instructed to.
How to review
:ship: Since this service is continuously deployed, all testing must be done
before the pull request is merged. :ship:
Read over, check nothing has been missed.
Links
Trello

Codecov Report

Merging #458 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #458   +/-   ##
=======================================
  Coverage   99.29%   99.29%
=======================================
  Files          72       72
  Lines        2128     2128
=======================================
  Hits         2113     2113
  Misses         15       15

Continue to review full report at Codecov.

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


Create components for demoing the use-cases

Our useGitHub hook provides powerful functionality for interacting with GitHub data in React applications. To showcase its capabilities and provide clear examples for developers, we need to create a set of demo components that illustrate various use-cases. These components will demonstrate the hook's features and serve as a reference for developers integrating the hook into their own projects.
We propose creating a demo page with several mini-projects, each highlighting different aspects of the useGitHub hook. Here are some project ideas:

Developer Portfolio Showcase

Display user profile information, pinned repositories, and the profile README.
Useful methods: userInfo, getRepositories().pinned(), userInfo.profileReadme()

Repository Explorer

List user repositories with filtering and sorting options.
Show detailed information for each repository, including language breakdown.
Useful methods: getRepositories().all(), getRepositories().withLanguage(), getRepositories().top()

Language Proficiency Visualizer

Create a visual representation of the user's programming language usage across all repositories.
Useful methods: getRepositories().all().languageDistribution()

Follower Network

Display the user's followers and following lists with pagination.
Show basic information for each connected user.
Useful methods: userInfo.getFollowers(), userInfo.getFollowings()

Contribution Timeline

Visualize the user's contribution activity over time.
Highlight peak contribution periods and projects.
Useful methods: Various repository and commit-related data from getRepositories().all()

Collaboration Insights

Analyze and display information about the user's collaborations on various projects.
Show co-contributors and shared repositories.
Useful methods: Repository contributor data from getRepositories().all()

Each of these mini-projects should be implemented as a separate component, designed to be reusable and customizable. Developers should be able to easily adapt them for their own needs or use them as inspiration for their projects.
When implementing these components, we should focus on proper error handling, loading states, and responsiveness. Each component should gracefully handle different scenarios, including API rate limiting. We should also implement performance optimizations where appropriate, such as memoization for expensive computations.
Documentation is crucial for these demo components. We should add clear comments to each component explaining its purpose, the hook methods it uses, and any props it accepts. We'll also need to update the main README with information about these demo components and instructions on how to run the demo.
To consider this feature complete, all proposed mini-projects should be implemented and working correctly, with proper documentation and test coverage. The demo page should showcase all components effectively and be responsive across different device sizes. The README should be updated with relevant information, and all components should handle loading, error, and empty states gracefully.
By creating these demo components and mini-projects, we'll provide developers with a clear, practical guide to using the useGitHub hook, making it easier for them to integrate and leverage its functionality in their own projects. These examples will showcase the versatility of the hook and inspire developers to create innovative GitHub-integrated applications.

I'd like to volunteer to take on this task. I believe I can contribute effectively to creating these demo components.
In addition to implementing the proposed mini-projects, I think we could enhance the documentation by including short video demos for each component. These videos could showcase the functionality in action and provide a quick visual reference for developers.
Here's my proposed approach:

Implement each mini-project as a separate, reusable React component.
Create a main demo page that showcases all the components.
Implement error handling, loading states, and responsiveness for each component.
Add comprehensive comments and documentation within the code.
Update the README with information about the demo components and setup instructions.
Create short (30-60 second) video demos for each component, highlighting key features.
Implement test coverage for all components.
Ensure the demo page is responsive and works well on various device sizes.

I'll start with the Developer Portfolio Showcase and work through the list. I'll submit PRs for each component as they're completed, allowing for iterative review and feedback.
Let me know if this approach sounds good or if you have any additional suggestions or requirements. I'm looking forward to working on this!


icons too dark

The icons are too dark, if applied on Ubuntu 24.04. You could create a lighter version of the icons, to highlight them among so much darkness
thank you

I wouldn't call the reaction of one account which is otherwise completely unaffiliated with the project "offended."
If you want traction on the issue, though, you need to take it to the right repo and provide some more clarity about what "too dark" means. (It is a dark theme, after all.)

A fair problem, but one that should probably be discussed in the right place. Which application are you using with the problem?

I don't know, that's why I asked. Are you using https://github.com/dracula/gtk or something else?

@EliverLara Do you want to transfer this issue to https://github.com/dracula/gtk?


bug: cordova.file.dataDirectory issue

As discussed with @manucorporat:
I've downloaded a video to the device but with the wkwebview plugin installed the video does not play from the device... without the wkwebview the video plays.
I just downloaded an mp4 using the file-transfer plugin, put it in cordova.file.dataDirectory and reference it <video #vid1 [src]="video1" webkit-playsinline></video>
An example of a filepath for a downloaded file: file:///var/mobile/Containers/Data/Application/805D81A0-B66D-4738-8B8E-578D644B1390/Library/NoCloud/data/gulf_logo.mp4
Apparently the wkwebview does not like absolute paths.
Tested on iOS 10.1.

Or any path outside of the app root, so locations like dataDirectory will not work.  Something to give access to these standard Storage locations is needed before wkwebview is really usable for many apps.


Instructions to generate SSL keys aren't accurate

app.ini says:
; Generate steps:
; $ cd path/to/gogs/custom/https
; $ ./gogs cert -ca=true -duration=8760h0m0s -host=myhost.example.com

First: there is no ./gogs there. Should say ../../gogs (?)
Second:
# /usr/local/libexec/gogs/gogs cert -ca=true -duration=8760h0m0s -host=myhost
Incorrect Usage.

NAME:

But usage is the same as recommended!

Because you did not build with tags.
I'll fix docs in recent pushes.

'pam' tag was off, you are right.
Instead of "Incorrect Usage." please say "Not built with pam support."

'pam' tag was off, you are right.
Instead of "Incorrect Usage." please say "Not built with pam support."

Actually... I don't know what you're talking ... :sweat:

I meant: Instead of "Incorrect Usage." please say "Not built with cert support."
:-)

LOL. https://github.com/gogits/gogs/commit/8ecbf0f16d90ad63a3c3ddc856df7b76aa0c328f#diff-61a68e2ec3cfcbe7c16047bb4d7ee950R19


Make an ember-cli addon

We should make an ember-cli addon for easy install/upgrades

How can I use it without using ember-cli? Just find that my gulp-based build break after update from 0.4 to 0.5

Hey,
Never tried but once you build the addon manually it generates a js under the dist folder,
Can you try to include the built js into your app?
Let me know if it works
Thanks


Inform User if Code use too much RAM / CPU Usage / Startup Time

I have seen many threads like CPU usage reached 80% , Code is consuming too much RAM.
and Team members ask users to show the extensions and trying with disabling them.
I think there should be feature in code that should evaluate this performance and usage and should inform use in a message in announcements with the reasons Code is having trouble or using much RAM. If Code is intelligent enough then it should inform user that he can disable this extension to improve the Startup.
Or Code Provide APIs in order to let extension authors develop such extension and get stats generated in some HTML page.
Best way would be integration in Extension Manager so user can see rather then providing logs from the console

fyi @bpasero @jrieken

I have the same problem too

Provided by the process explorer: https://code.visualstudio.com/updates/v1_23#_see-the-running-visual-studio-code-processes


Make polar function part of V2 class

A little bit of bikeshedding.

Now polarV2 function is a static method polar.

Also replaced check for undefined with optional chaining operator.

@kolumb thanks for the contribution!


Suggestions for security on "delete" functionality

I'm going to implement some mechanism in the validateRequest function for controlling access to downloads.. however, if I have a delete functionality, I assume I also need to put something in place to prevent unauthorized "deletes" of uploaded files.  Do you have any suggestions? or should I do it the same way as the downloads, and pass through a token I can use to look up the user to see if their resume token is still present in the users collection..??
events on client:
Template.fileList.events({
    'click #deleteFileButton ': function (event) {
      Meteor.call('deleteFile', this._id);
    }
  })

method defined on server:
  Meteor.methods({
    'deleteFile': function (_id) {
      check(_id, String);

      var upload = Uploads.findOne(_id);
      if (upload == null) {
        throw new Meteor.Error(404, 'Upload not found'); // maybe some other code
      }
// NOTE: we should also validate here and make sure user is logged in by passing a token through??
      UploadServer.delete(upload.path);
      Uploads.remove(_id);
    }
  })

What you can do is use some kind of token which you issue on server for a specific user and pass it down to client. Then, when deleting the file, attach the token to the deletion request and compare on server if that given user has access to delete that file.
I hope this helped. Please reopen if necessary,

yes it helps, I'm going to do something like this for controlling access to downloads as well.


(fix) Unterminated JS statement in views/ErrorHandler/exception.php

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues

EN:
Added semicolon after javascript declaration because this can cause error for some browsers.
RU:
Добавлена точка с запятой в присвоении javascript-функции, потому как это может вызывать ошибку в некоторых браузерах.

https://stackoverflow.com/questions/11978698/do-we-need-a-semicolon-after-function-declaration
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/function#Syntax

Also... which browser has errors?

I don't remember what browser is - this fix was mad in our project year ago (or older).
Now I test in online-browser-shots without semicolon - all is ok.
So... this is stylish modification, if you want, you could close this request without acception.
PS: May be this fix was for JSLint, PhpStorm also mark this as warning.

PhpStorm doesn't complain about it but let's have it. Thanks.


[WEB] Sourcemaps not getting processed

Platform:

[ ]  Dart
[ ]  Flutter Android or iOS
[x]  Flutter Web

IDE:

[ ]  VSCode
[x]  IntelliJ/AS
[ ]  XCode
[ ]  Other, which one?

split-debug-info and obfuscate (Flutter Android or iOS) or CanvasKit (Flutter Web):

[ ]  Enabled
[x]  Disabled

Platform installed with:

[x] pub.dev
[ ] GitHub

Output of the command flutter doctor -v below:
❯ flutter doctor -v
[✓] Flutter (Channel stable, 2.2.2, on macOS 11.4 20F71 darwin-x64, locale en-IN)
    • Flutter version 2.2.2 at /Users/shripaljain/fvm/versions/stable
    • Framework revision d79295af24 (2 weeks ago), 2021-06-11 08:56:01 -0700
    • Engine revision 91c9fc8fe0
    • Dart version 2.13.3

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/shripaljain/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Ultimate Edition (version 2021.1.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 211.7233

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.23.0

[✓] Connected device (3 available)
    • POCO X2 (mobile) • be95071d • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos    • darwin-x64     • macOS 11.4 20F71 darwin-x64
    • Chrome (web)     • chrome   • web-javascript • Google Chrome 91.0.4472.114

! Doctor found issues in 1 category.

The version of the SDK (See pubspec.lock):
5.1.0

I have the following issue:
This issue started after migrating to null-safety and upgrading sentry SDK to v5.1.0 (together)
Sentry is not processing my sourcemaps properly. As far as I have observed, it only processes and traces the first issue/error for a release using the sourcemap and source files.
All other subsequent issues are traced to dart code, they just show stacktrace of main.dart.js
I use this script in GitHub Actions whenever a new version of my Flutter Web app is deployed. This script, nor the Action build workflow has been changed for the null safety migration.
# $1 = version
# $2 = env (dev/prod)

echo "Doing sentry release for version $1 env $2"
sentry-cli releases new "$1"
sentry-cli releases set-commits "$1" --auto
sentry-cli releases files "$1" upload-sourcemaps . --ext dart --rewrite
sentry-cli releases files "$1" upload-sourcemaps ../lms_content/ --ext dart --rewrite --url-prefix '~/lms_content/'
sentry-cli releases files "$1" upload-sourcemaps ./build/web/ --ext map --ext js --rewrite
sentry-cli releases finalize "$1"
sentry-cli releases deploys "$1" new -e $2

This script works properly without any errors even before and after null safety migration.
Point to note: Last proper Flutter version when sentry always processed the sourcemaps was: v2.0.3. After the migration, we upgraded to the latest flutter version v2.2.2.
Steps to reproduce:
I am not sure how you would be able to reproduce this, but the only thing which comes to my mind is the null safety migration. So you can try creating a non-null-safe project, create a release with sourcemaps on sentry, deploy it, produce a synthetic error. And then, do the same process after migrating the project to null safety.
Actual result:
As mentioned earlier, Sentry processed and traced only the first issue for this release, subsequent releases don't trace through the sourcemap and just refer to main.dart.js

Expected result:
Sentry should process all errors for a release, and not just the first one.

@shripal17 we'd need to investigate this, as we haven't spent much time on the web integration yet.
the issue's titles though should be because of https://github.com/getsentry/sentry-dart/issues/261#issuecomment-868265652

our test script is similar to yours https://github.com/getsentry/sentry-dart/blob/main/flutter/example/run.sh#L40-L53 so its probably a Dart/Flutter tooling issue (that may have changed) or the server-side symbolication.

it only processes and traces the first issue/error for a release using the sourcemap and source files.

All other subsequent issues are traced to dart code, they just show stacktrace of main.dart.js

can you link us if using sentry.io to some issues that exemplify the cases above? it'd be easier to understand and debug, thanks :)

can you link us if using sentry.io to some issues that exemplify the cases above? it'd be easier to understand and debug, thanks :)

These links are from the screenshot:

First issue/error which processed successfully:
https://sentry.io/organizations/i-am-in-world/issues/2474284909/?environment=dev&project=5751903&query=is%3Aunresolved+dist%3A119&statsPeriod=14d
Second issue/error which is fundamentally the same as the first one, but the sourcemap was not processed:
https://sentry.io/organizations/i-am-in-world/issues/2474304494/?environment=dev&project=5751903&query=is%3Aunresolved+dist%3A119&statsPeriod=14d

@shripal17 you are setting a dist to your events (options.dist during SDK init), but not passing it when uploading the source maps, so try to to call sentry-cli passing the --dist param and value too, that will match your events, your events contain dist=119 for reference.
so please try that, compile again with a new dist, upload source maps using the --dist param and give it a try.

@marandaneto

@shripal17 you are setting a dist to your events (options.dist during SDK init), but not passing it when uploading the source maps,
I am not passing dist to sentry sdk:

await SentryFlutter.init(
        (options) {
          options.dsn = 'dsn_here';
          options.environment = env;
          options.release = version;
        },
      );

version is for e.g. dev-v1.0.0, env is dev/prod

so try to to call sentry-cli passing the --dist param and value too, that will match your events, your events contain dist=119 for reference.
so please try that, compile again with a new dist, upload source maps using the --dist param and give it a try.

I am confused with this, which commands should I add this param to? Can you change it in the above mentioned script for me please?

@shripal17 dist is the equivalent of the builder number, its automatically set by the package_info_plus plugin if not set.
https://github.com/fluttercommunity/plus_plugins/blob/main/packages/package_info_plus/package_info_plus_web/lib/package_info_plus_web.dart
options.dist = '123'; // or let package_info_plus does the job.

@shripal17
every time you call sentry-cli releases files "$1" upload-sourcemaps
always append also the --dist param, eg.
sentry-cli releases files "$1" upload-sourcemaps . --ext dart --rewrite --dist "123"
the dist here should match either the one set automatically by the SDK via package_info_plus or set yours manually in the options callback as mentioned in the message above.

I've raised docs about it https://github.com/getsentry/sentry-docs/issues/4006
just tested everything and it works, please raise a new issue if you still face issues, thanks


Native DataChannel examples

Add examples on how to use DataChannel. Preferably for both iOS and Android.

Duplicate: https://github.com/EricssonResearch/openwebrtc-examples/issues/58


Vesting contract

How can i distrubite code for this feature?

Hey @zpano, we appreciate and are always open to contributions. Check our CONTRIBUTING guidelines as a reference, and feel free to open a PR any time.


01_deploy.sh script error

I had modified 01_deploy.sh,now it's work
01_deploy.txt

Hi @andyoulovexy,
The script works for docker compose v2.
Now the docker compose start with "docker compose" and not "docker-compose"
Thanks for your help. I will be more precise on the documentation of installation.


Does it support the option of customizing the tools toolbar?

I want to add a component to the rich text toolbar. Does it support the option of customizing the tools toolbar?

yes i managed to load some custom plugins with
CKEDITOR.plugins.addExternal
beware of the path where your plugin si stored


Can't install on Mac OS Monterey (Macbook Pro Mid 2015)

I've tried to install this but it's having none of it... there's a graphic overlayed onto yours as if to say it can't even attempt to install it (it isn't compatible with Monterey).

Can you try installing this version? https://github.com/erikrichardlarson/unbox/releases/download/10.0/unbox_mac_intel.zip


feat: migrate CLI to use cobra

Closes #112

This test case is returning exit status 1 instead of 0:
{"exclude file types set", []string{"--exclude-file-types=json", "."}, 0}
It is because in the "." path there is some "bad files", if I run the same command with the addition of --depth 1 it works fine, because in the folder with --depth 1 there is just "good files", what you guys think I could do in this case?

The lint job failed on the latest pipeline.  Need to fix.

@1garo Why was -search_path added back rather than treating them as positional arguments? Search path should remain a positional argument
To clarify, this now fails:
>> docker run -v $(pwd)/test:/test cfv:cobra /test
Error: unknown command "/test" for "validator"
Run 'validator --help' for usage.
unknown command "/test" for "validator"

and instead I have to do this:
docker run -v $(pwd)/test:/test cfv:cobra --search_path /test

@1garo Why was -search_path added back rather than treating it as a positional argument? Search path should remain a positional argument
To clarify, this now fails:
>> docker run -v $(pwd)/test:/test cfv:cobra /test
Error: unknown command "/test" for "validator"
Run 'validator --help' for usage.
unknown command "/test" for "validator"

and instead I have to do this:
docker run -v $(pwd)/test:/test cfv:cobra --search_path /test

fixed at fix: add search_path as positional argument


feat(v2): add icon to external navbar links

Motivation
For more consistency, we should probably add icon for external links in the navbar too. This was previously done for sidebar links (see #4261).
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Preview

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

I was inspired by VuePress as example that adds icon for external links to the navbar. Actually, end user can remove this icon via CSS attribute selector.
I suggest adding this icon without explicit customization for now, and just wait for feedback from users. As for me, it's not a big change, so I do not think that there will be a lot of dissatisfied with it.

Hmm why not.
I think for now they can also disable it by using to instead of href (even if I don't like that "API" much)
Should we keep the release item in our own site? We don't seem to have enough width to make it fit:

Yes, will remove this link, it was added just for demo purposes.
However, in Infima I previously opened PR that reduces current padding between navbar items. This seems to make sense to me, can you check this out?


Question: Missing UI, S Base Metric, Temporal and Environmental?

Howdy,
I'm looking through the Vulnerabilities sections and is the "User Interaction" (UI) and Scope (S) Base Metric fields missing?
I'm looking at https://www.first.org/cvss/v3.1/specification-document#2-3-Impact-Metrics (Section 2.1)
I see Privileges Required (PR) (which I'm assuming is the Authentication field), Attack Complexity (AC) and Attack Vector (AV).
Is the Scope Field, S (sec 2.2), Temporal Metric Group E, RL, RC (sec 3), and Environmental Metrics CR, IR, AR (sec 4 also missing?
I know the Temporal and Environmental Sections are optional, but they might be a nice inclusion.
Thanks again for the work your putting into this.
-Jake

Current setup is for v2. Hopefully we can get v3 info in the future.


MAINT: dogbox ensure x is within bounds closes #11403

#11403 has an issue where least_squares --> dogbox asks for evaluation of the jacobian with x values outside the lower/upper bounds of the problem. approx_derivative doesn't like that and raises an Exception. Whilst a problem for the OP it's not been possible to reproduce it on a maintainers computer, making it difficult to create a fix, or decide whether to close the issue.
In comparison to trf dogbox may not  fully ensure that x_new is strictly within bounds, although it does do something towards this.
This PR presents a pragmatic approach to this issue by simply clipping x to within the lb/ub, meaning that approx_derivative should never get sent an x outside the bounds.
The dogbox/trf code isn't easy for a non-original maintainer to keep up with, so it would be good to have experts look over this and confirm that the change is ok.

Thanks for looking into this.
I think this issues has a simple explanation - step is logically computed as not to violate bounds, however done in floating-point arithmetic x + step can violate the bounds slightly. I guess it might be considered as a small implementation flaw.
So I approve this change.


Mutating versions of removeDuplicates(keyPath:) and removeDuplicates() refactoring

🚀 Fixed #710. Refactored Array.removeDuplicates().
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 5.0.
[x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[x] I have added a changelog entry describing my changes.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 587 tests, with 0 failures (0 unexpected) in 11.513 (13.256) seconds

:book:
tvOS: Executed 562 tests, with 0 failures (0 unexpected) in 1.877 (2.313) seconds

:book:
macOS: Executed 421 tests, with 0 failures (0 unexpected) in 1.101 (1.447) seconds

  Generated by :no_entry_sign: Danger


Show a shared confirmation / cancel  toast

Hi, i would like show a  ToastAndroid message after the user successfully share something.
render Touchable icon code:
<View style={styles.iconContainer}>                 <TouchableOpacity onPress={()=>{Share.open(shareOptions);}}>                     <Icon name="md-share" size={30} color="#2ecc71" />                 </TouchableOpacity>                 <Text style={styles.count} >Share</Text>                 </View>
inside render i have my Share Function:
 render() { const {name,url} = this.props.artist let shareOptions = {         title: name,         url: url,         subject: "Share Link" //  for email             } //...
Hope than someone can help me.

Share.open(shareOptions)
      .then((res) => {
        console.log(res);
// wrong value when cancel or success, not fixed
      })
      .catch((err) => {
         if (err && err.error !== 'User did not share') {
           this._showToast(I18n.t('INVITE_FAIL'));
         }
       })

Sorry doesn't work for me, i just can catch the res but not the err to show the Toast.


Custom configuration isnt recognized by addon

Hey @fmartinou
i got an configuration problem with my Home Assistant.
ive changed the configuration via the HA frontend in your extension but it will use the default values instead of my given settings. Dont know whats wrong here. Can u pls give me a hint?
2023-03-12 13:35:10,066 - __main__ - INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-03-12 13:35:10,066 - __main__ - INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-03-12 13:35:10,067 - __main__ - INFO - STARTING TYDOM2MQTT
2023-03-12 13:35:10,067 - __main__ - INFO - Detecting environnement......
2023-03-12 13:35:10,068 - __main__ - INFO - /data/options.json detected ! Hassio Addons Environnement : parsing options.json....
2023-03-12 13:35:10,069 - __main__ - ERROR - Parsing error 'TYDOM_ALARM_PIN'
2023-03-12 13:35:10,071 - tydomConnector - INFO - Initialising TydomClient Class
2023-03-12 13:35:10,072 - tydomConnector - INFO - Setting local mode context.
2023-03-12 13:35:10,081 - __main__ - INFO - Starting main loop_task
/app/main.py:141: DeprecationWarning: There is no current event loop
  loop = asyncio.get_event_loop()
2023-03-12 13:35:10,085 - mqtt_client - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2023-03-12 13:35:10,086 - mqtt_client - INFO - Attempting MQTT connection...
2023-03-12 13:35:10,086 - mqtt_client - INFO - MQTT host : localhost
2023-03-12 13:35:10,087 - mqtt_client - INFO - MQTT user :
2023-03-12 13:35:10,109 - mqtt_client - INFO - MQTT connection Error : Multiple exceptions: [Errno 111] Connect call failed ('<IP_ADDRESS>', 1883), [Errno 99] Address not available
2023-03-12 13:35:10,109 - mqtt_client - INFO - MQTT error, restarting in 8s...```

thanks!

Hi,
Connect call failed ('<IP_ADDRESS>', 1883)

The container is running on the Docker bridged network.
That means that its IP address is not the IP address of your host machine.
So your mosquito broker cannot be reachable as <IP_ADDRESS>.
You need to change the MQTT_URL to indicate the real IP or hostname of your broker.
It depends on your setup but if you're using hassio, the homeassistant hostname should work.

Hi @fmartinou,
thanks for your hint. The problem that i have is that the configuration setted up in the UI isnt used within the plugin. So localhost is used every time. Can u tell me where the addon settings are stored? I setted up Homeassistant via Raspberry Pi 3 Image. Docker isnt installed on the Image.
Thanks

The configuration set from the UI is the one used by the container.
My guess is that you have 1 field which doesn't pass the validation so the entire configuration override isn't taken in account.
Probably the ALARM_PIN_CODE which is mandatory even if you don't have an alarm (that's a trap a need to fix from ages...)

hey @fmartinou that was the final hint. You have to set the ALARM_PIN_CODE
Thank you so much!! Works like a charme now. Is it possible to support the awning TYXIA 5731 as well?
Helped someone who developed the homebridge tydom. Here is the commit. Maybe the informations can be used as well for the home assistant implementation?
https://github.com/mgcrea/homebridge-tydom/commit/e1773cafb288110a258846bd9f0e7f924de97201
Best regards

Great! I'm glad to see that it's finally working 👍
Regarding adding new devices, I'm unfortunately not the most skilled; I took the lead of the project some times ago because the original creator hadn't time anymore.
I'm qualified for packaging, automation, HA integration... but I'm not so confortable with the Tydom protocol part 😞 .
If you want to contribute ; please, go ahead! 😃 .
I'll be pleased to review /release your enhancements.
Best regards.

Im also not the most skilled person with python and home assistant. I'm new in home assistant.
Maybe someone will add it, hopefully 😔


AttributeError: Can't pickle local object 'train_model..'

Hello!
I am trying to run the mnist_backprop.py and mnist_fwd_grad.py files on my local repository, But getting this error. If the same repo I run on Google Colab, I do not face the issue. I feel its mostly a version error and hence wanted to know more about the environment details.
The error details message:
d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\site-packages\torch_functorch\deprecated.py:97: UserWarning: We've integrated functorch into PyTorch. As the final step of the integration, functorch.make_functional is deprecated as of PyTorch 2.0 and will be deleted in a future version of PyTorch >= 2.3. Please use torch.func.functional_call instead; see the PyTorch 2.0 release notes and/or the torch.func migration guide for more details https://pytorch.org/docs/master/func.migrating.html
warn_deprecated('make_functional', 'torch.func.functional_call')
Error executing job with overrides: []
Traceback (most recent call last):
File "D:\Masters\Academics\Semester_2\DISML\Project\distributed_fwdgrad\src\fwdgrad\mnist_fwdgrad.py", line 60, in train_model
for i, batch in enumerate(train_loader):
File "d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\site-packages\torch\utils\data\dataloader.py", line 442, in iter
return self._get_iterator()
File "d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\site-packages\torch\utils\data\dataloader.py", line 388, in _get_iterator
return _MultiProcessingDataLoaderIter(self)
File "d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\site-packages\torch\utils\data\dataloader.py", line 1043, in init
w.start()
File "d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\multiprocessing\process.py", line 121, in start
self._popen = self._Popen(self)
File "d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\multiprocessing\context.py", line 224, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File "d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\multiprocessing\context.py", line 327, in _Popen
return Popen(process_obj)
File "d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\multiprocessing\popen_spawn_win32.py", line 93, in init
reduction.dump(process_obj, to_child)
File "d:\Masters\Academics\Semester_2\DISML\Project.conda\lib\multiprocessing\reduction.py", line 60, in dump
ForkingPickler(file, protocol).dump(obj)
AttributeError: Can't pickle local object 'train_model..'
Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

Hi @ChiragJRana, which operating system are you using? Everything i've tested was on Linux OS.
Can you also try out this branch please?

I was testing this out as well and apparently windows doesn't support the use of lambda inside of torchvision.transforms.Lambda()
You need to write a new function to replace the lambda function. This worked for me.
def fuc_flatten(x):
return torch.flatten(x)
and the use transform.append(torchvision.transforms.Lambda(fuc_flatten))


Can I use ZCU102 to develop FPGA instead of CW310?

Hi All
As I always encounted issues of transfering by using CW310, can I use ZCU102 to do the opentitan FPGA verfication ?
Any suggestion is welcome.

I can't answer your question, but because "any suggestion is welcome", I'll comment anyway, as I also had difficulties getting the board to work.
What exactly is not working? Loading the bitstream? Loading the firmware?
Loading the bitstream takes a while, a few minutes in my setup. Loading the firmware immediately after the bitstream (without disconnecting) seems to be a bit more stable to me.

Hi @nicolast0604,
Indeed it would be good to know a bit more about what exactly is not working.
You are welcome to use another FPGA board - but you would have to port OpenTitan over to that board yourself, since the ZCU102 is currently not among the FPGA boards we support and maintain.
CC @colinoflynn for CW310-specific questions.

Hi @nicolast0604 - The boards do get "opentitan specific tests" run (loading the bitstream + tests). Normally the loading time is ~60 seconds for the FPGA (I haven't timed recently), and the firmware is much faster after. There is a speed setting for how quickly the programming happens on the first stage, which you can also tune (it's set to a "mostly safe" default, there is some variation in practice).
If you aren't on the latest CW310 firmware that can also be helpful, you can drop a note here or reach out to<EMAIL_ADDRESS>for general CW310 firmware updates (that is - updating the firmware that power the actual CW310 USB interface, not the open-titan specific firmware).

Tagging this issue as closed / resolved. If there is anything to follow-up on please reference this in a new issue.


[v0.1.0] (Storage) Support loading from local disk

Testing results Aug 27, commit 0ffb869d
test_lmcache_local_disk.pdf
Problems and conclusions:

The first couple of requests are very slow in both TTFT and tokens per second
GPU memory overhead: ~6GB


Prior Preserving Loss

Have you implemented prior preserving loss? Can you direct me to the correct file?

Have you found it?


Fix Google Chrome script

Using an available Google Chrome NixOS package fixes the script!

Thanks for the PR. I decided to just fix the package name in https://github.com/ludios/nixos-playwright/commit/d7bda0a8f105009935eb36738e532b44d8c2da97 to refer to -dev. playwright downloads a recent Chromium and google-chrome-dev will be more similar to it than stable chrome. It usually won't matter, but I wanted to stay on the safe side. Let me know if this causes any issues.

:ok_hand:
I would have adjusted my pull request :smirk:


How to pass script parameters correctly?

I have read the examples for Scripts support, and through api.get_scripts(), I found that I have a script named "roop". The GitHub repository for the Roop extension is: https://github.com/s0md3v/sd-webui-roop. Here is my code:
`from PIL import Image
import base64
Timage = Image.open('/home/talks/Downloads/AI_3/11.png')
model = '/home/talks/stable-diffusion-webui-master/stable-diffusion-webui/models/roop/inswapper_128.onnx'
image_path = "/home/talks/Downloads/AI_3/11.png"
encoded = base64.b64encode(open(image_path, "rb").read())
encodedString = str(encoded, encoding='utf-8')
aimage = 'data:image/png;base64,' + encodedString
image_path = "/home/talks/Downloads/AI_3/8.png"
encoded = base64.b64encode(open(image_path, "rb").read())
encodedString = str(encoded, encoding='utf-8')
bimage = 'data:image/png;base64,' + encodedString
roopface = api.img2img(images=[Timage], seed=-1, cfg_scale=3, denoising_strength=0.3,
script_name="roop",
script_args=[
aimage,
bimage,
model
])
roopface.image`
And here is the response I received:
RuntimeError: (422, '{"error":"HTTPException","detail":"Script 'roop' not found","body":"","errors":""}')
Could you please guide me on how to correctly pass these parameters?

I got the same error but got it working by hacking a function and the payload.... i cant remember where I saw this. But anyway .. this works. The scripts are selected using an index... and the list will vary depending on your stable diffusion install so you will need to roll your own.
`script_name = "X/Y/Z plot"
def get_script_args():
XYPlotAvailableScripts = [
        "Nothing",
        "Seed",
        "Var. seed",
        "Var. strength",
        "Steps",
        "Hires Steps",
        "CFG Scale",
        "Prompt S/R",
        "Prompt order",
        "Sampler",
        "Checkpoint Name",
        "Negative Guidance minimum sigma",
        "Sigma Churn",
        "Sigma min",
        "Sigma max",
        "Sigma noise",
        "Eta",
        "Clip skip",
        "Denoising",
        "Hires upscaler",
        "VAE",
        "Styles",
        "UniPC Order",
        "Face Restore",
        "Token merging ratio",
        "Token merging ratio his-res",
        "[ControlNet] Enabled",
        "[ControlNet] Model",
        "[ControlNet] Guidance Start",
        "[ControlNet] Guidance End",
        "[ControlNet] Control Mode",
        "[ControlNet] Resize Mode",
        "[ControlNet] Preprocessor",
        "[ControlNet] Pre Resolution",
        "[ControlNet] Pre Threshold A",
        "[ControlNet] Pre Threshold b",
        "[ADetailer] ADetailer model 1st",
        "[ADetailer] ADetailer prompt 1st",
        "[ADetailer] ADetailer negative prompt 1st",
        "[ADetailer] Mask erosion / dilation 1st",
        "[ADetailer] Inpaint only masked 1st",
        "[ADetailer] Inpaint only masked padding 1st",
        "[ADetailer] ControlNet model 1st",
        ]
XAxisType = "Steps"
XAxisValues = "15, 20, 25"
YAxisType = "CFG Scale"
YAxisValues = "7,15,20"
ZAxisType = "Nothing"
ZAxisValues = ""
drawLegend = False
includeLoneImages = False
includeSubGrids = False
noFixedSeeds = True
marginSize = 1

return [
    XYPlotAvailableScripts.index(XAxisType),
    XAxisValues,
    "",
    XYPlotAvailableScripts.index(YAxisType),
    YAxisValues,
    "",
    XYPlotAvailableScripts.index(ZAxisType),
    ZAxisValues,
    "",
    drawLegend,
    includeLoneImages,
    includeSubGrids,
    noFixedSeeds,
    marginSize
]

result = client.txt2img(script_name=script_name, script_args=script_args, seed=seed, prompt=prompt,   sampler_name=sampler_name)`


Print-friendly docs

Would it be possible to auto-generate a consolidated PDF from the docs, or have a print-friendly version that includes all the guides?
So far I've gotten bitten a couple times by being too excited and lazy to read through it all before diving in - would be good to just force myself to sit down and read it all.
Personally, I prefer doing something like that with a hard copy.

If you clone this repo, you can run npm run docs:pdf to generate a print-friendly PDF. The docs are also print-friendly now.


Skip linking build actions

CodeChecker analyze should skip the linking actions unless CTU is used.
Fixes #1037

@Xazax-hun @dkrupp does the current CTU solution use the linking information?

No linking info is used currently. But we might use it in the future. I think it is ok to skip them for no-ctu.

The linking actions are allegedly filtered in a later step so probably this pull request is not needed. I put a WIP flag on it.

I think it is ok to close this PR for now to keep the number of open PRs in a reasonable limit. It it useful to keep the branch if we need something like this in the future.


Fixing deprecation/warning usage :

For issue #3
Redis#exists(key) will return an Integer in redis-rb 4.3. exists? returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set Redis.exists_returns_integer = false, but this option will be removed in 5.0.

This PL can be closed, because it's fixed  here https://github.com/ncbo/sparql-client/commit/a1e6beaf6790df68921cbed9bd1719299b9add3e


System management Agent

New system management agent service that serves as go between for micro services and management systems.  Attached to developer scripts for now.

This can be closed now I think since the SMA is in the delhi and later compose files.


Discussion on OSPP and channel of communication

描述你的问题（Describe your question here）

Hello, I am Rishabh Verma, an undergraduate CS student at UIET, India, Punjab University.
I have set up the project in my local system and am really interested in working on this project for OSPP'22.
Implementation of cross-end and cross-window file system service base on OpenSumi
However, I can't figure out how to communicate with you all as DingTalk always gives me a network error.
I would be really grateful if I could get some help on this and directions to work on this project.

Hi, @Rispectech I will create a discussion about Implementation of cross-end and cross-window file system service based on OpenSumi today, maybe we can talk there.

@Rispectech I create a discussion here #1086, if you are interested in it, you can show your ideas or other question.
I will close this issue cause it is duplicated.

hey, @erha19 thanks for the head-ups.  I have started researching the vscode methods.


Modify Space.seed such that the return can be used as seeding values

Description
Updated all composite and the Space seed functions that the following code will work
seeding_value = space.seed(None)
samples = [space.sample() for _ in range(3)]

reseed_values = space.seed(seeding_value)
resamples = [space.sample() for _ in range(3)]

assert samples == resamples

Previously, this wouldn't work as spaces returned a list of ints which for Box or dictionary space doesn't work
Solution for Proposal #1032

In principle we should support low income sky with box, Since it is mathematically valid
realistically If all the elements of low and high are equal It does not have a practical usage. , But some elements being equal might happen.


RecurringPayInRegistration tag not properly saved

See code below

card_id = ""
wallet_id = ""

card = Card.get(card_id)
wallet = Wallet.get(wallet_id)

funds = Money(1_00, "EUR")
fees = 0 * funds

reg = RecurringPayInRegistration(
    author=card.user,
    card_id=card.id,
    credited_wallet_id=wallet,
    fixed_next_amount=True,
    frequency="Daily",
    first_transaction_debited_funds=funds,
    first_transaction_fees=fees,
    next_transaction_debited_funds=funds,
    next_transaction_fees=fees,
    tag="some tag",
)
reg.save()

assert reg.tag == "some tag" # True
reg = RecurringPayInRegistration.get(reg.id)
assert reg.tag == "some tag" # False

Hello @villqrd, thanks for your message, we are looking into it

Hello @villqrd ,
As per API documentation, the Recurring PayIn Registration object does not contain "tag".


[Feature Request] Transaction generator support vector arguments

🚀 Feature Request

Motivation
The script and script function arguments support vector now, such as vector, vector<vector>, but the transaction generator does not implement it.
pub(crate) fn mangle_type(type_tag: &TypeTag) -> String {
    use TypeTag::*;
    match type_tag {
        Bool => "bool".into(),
        U8 => "u8".into(),
        U64 => "u64".into(),
        U128 => "u128".into(),
        Address => "address".into(),
        Vector(type_tag) => match type_tag.as_ref() {
            U8 => "u8vector".into(),
            _ => type_not_allowed(type_tag),
        },
        Struct(_) | Signer => type_not_allowed(type_tag),
    }
}

Is your feature request related to a problem? Please describe.

Pitch
Describe the solution you'd like

Describe alternatives you've considered

Are you willing to open a pull request? (See CONTRIBUTING)
Additional context

@tzakian Does this overlap with any of our planned work on generated bindings?

Oh wait, I just read this more closely and see that it is about expanding from vector<u8> to arbitrary vector<T>. I think this may go beyond just the transaction generator....

I think this definitely overlaps with our planned work on generated bindings to some extent. I agree that to do this in generality goes beyond the transaction generator IMO. For example, how (/if we want) to encode abilities for the T type in the language being generated, what type of restrictions need to be placed on these generic type parameters etc.
One possibility could be to recursively resolve these types as long as they are non-struct/signer types. However, I'm not sure how easy it will be for users to construct these vectors from the generated diem_types file for the given language. We might also need to relax restrictions in the VM to permit this as well.


Data-only hotspot assert location fails

Describe the bug
Assert location for data only hotspot fails
To Reproduce
Steps to reproduce the behavior:

Click on Manage Hotspot and Click on Assert Location.
Select IoT.
Select location on map and click Assert Location button.
Select Gain and Altitude and click Assert location button.
See the error: Update metadata requests failed: Cannot read properties of null (reading 'publicKey')

Expected behavior
A success assertion.
Screenshots
Smartphone (please complete the following information):

Device: iPhone 14
OS: iOS 17.4.1
App Version: 2.7.8

Additional context
Need to change it to change Lorawan region due country change.

Having the same issue, any luck?

Having the same issue, any luck?

Don’t think they have fixed it yet. You can try using cli wallet, that will work. More info at discord #cli-wallet-development


eSteem 1.4.6 (iOS) - Error while pasting images

User aft3rd4rk on Steemit reported a problem about pasting images via eSteem 1.4.6 app for iOS. Not sure if this is only a iOS problem but I confirm it's happening:

I have experimented on a iPhone 6.

Fixed confirmed.


Add Item Gravity

Just got some spare free time to help @craftablescience.

 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.

 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.

I think this should be in the Addon-API repo, but this is genius
Thanks for saving me

I think this should be in the Addon-API repo, but this is genius
Thanks for saving me

Oh okay, will do!

Oh okay, will do!


Add quick_collection function and revise docs.

The quick_collection function is essentially a port of the functionality provided by @lelongg's https://github.com/lelongg/geo-geojson crate: it accepts an arbitrary geojson::GeoJson object, and produces a geo::GeometryCollection for users who just want to process their geometries using geo's functionality (I suspect this is the primary use case for a lot of users).
The docs have been revised to add more detail about the structure of the crate, how to get started etc, and details about what quick_collection does and how it works. They now explicitly point out that you must enable the geo-types feature in order to use the conversion traits and quick_collection – I'm on the fence as to whether this should all just be enabled by default.
As I point out, quick_collection potentially sacrifices a little performance due to the use of clone() and creating new Vecs. I don't think we can do much about the latter, but if anyone wants to have a look at the clone() stuff feel free.

bors r+


Add macos default path

Codecov Report

Merging #10 into master will decrease coverage by 0.02%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage   78.44%   78.42%   -0.03%
==========================================
  Files          17       17
  Lines         566      570       +4
==========================================
+ Hits          444      447       +3
- Misses        122      123       +1

Impacted Files
Coverage Δ

lib/support/osx.js
80.24% <83.33%> (-0.28%)
:arrow_down:

Continue to review full report at Codecov.

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


[BUG] IndicesQueryCache$CachingWeightWrapper#count should delegate to internal weight

Describe the bug
Currently, IndicesQueryCache$CachingWeightWrapper#count does not delegate to internal weight object and keeps returning -1 from the Weight#count implementation. Due to this leaf counting cannot be done even when it is supported by Weight implementations like PointRangeQuery#createWeight
Expected behavior
Instrumenting the code for FiltersAggregator and observing with and without the change:
Without this change:
Original Query : class org.apache.lucene.document.LongPoint$1
Rewritten Query : class org.apache.lucene.search.IndexOrDocValuesQuery
Original Query : class org.apache.lucene.document.LongPoint$1
Rewritten Query : class org.apache.lucene.search.IndexOrDocValuesQuery
Wrapper class type : class org.apache.lucene.search.LRUQueryCache$CachingWrapperWeight
Aggregation count from the filters : 0  value : -1 class type : class org.apache.lucene.document.LongPoint$1 : class org.opensearch.indices.IndicesQueryCache$CachingWeightWrapper
Wrapper class type : class org.apache.lucene.search.LRUQueryCache$CachingWrapperWeight
Aggregation count from the filters : 1  value : -1 class type : class org.apache.lucene.document.LongPoint$1 : class org.opensearch.indices.IndicesQueryCache$CachingWeightWrapper

With the change:
Original Query : class org.apache.lucene.document.LongPoint$1
Rewritten Query : class org.apache.lucene.search.IndexOrDocValuesQuery
Original Query : class org.apache.lucene.document.LongPoint$1
Rewritten Query : class org.apache.lucene.search.IndexOrDocValuesQuery
Wrapper class type : class org.apache.lucene.search.LRUQueryCache$CachingWrapperWeight
PointRangeQuery#count method was invoked
Aggregation count from the filters : 0  value : 4349068 class type : class org.apache.lucene.document.LongPoint$1 : class org.opensearch.indices.IndicesQueryCache$CachingWeightWrapper
Wrapper class type : class org.apache.lucene.search.LRUQueryCache$CachingWrapperWeight
PointRangeQuery#count method was invoked
Aggregation count from the filters : 1  value : 5981766 class type : class org.apache.lucene.document.LongPoint$1 : class org.opensearch.indices.IndicesQueryCache$CachingWeightWrapper

Additional context
Instrumentation Code
diff --git a/server/src/main/java/org/opensearch/search/aggregations/bucket/filter/FiltersAggregator.java b/server/src/main/java/org/opensearch/search/aggregations/bucket/filter/FiltersAggregator.java
index 84e0218d8ea..b54b46a8254 100644
--- a/server/src/main/java/org/opensearch/search/aggregations/bucket/filter/FiltersAggregator.java
+++ b/server/src/main/java/org/opensearch/search/aggregations/bucket/filter/FiltersAggregator.java
@@ -175,6 +175,7 @@ public class FiltersAggregator extends BucketsAggregator {
         Weight[] filters = this.filters.get();
         final Bits[] bits = new Bits[filters.length];
         for (int i = 0; i < filters.length; ++i) {
+            System.out.println("Aggregation count from the filters : " + i + "  value : " + filters[i].count(ctx) + " class type : " + filters[i].getQuery().getClass() + " : " + filters[i].getClass());
             bits[i] = Lucene.asSequentialAccessBits(ctx.reader().maxDoc(), filters[i].scorerSupplier(ctx));
         }
         return new LeafBucketCollectorBase(sub, null) {
diff --git a/server/src/main/java/org/opensearch/search/aggregations/bucket/filter/FiltersAggregatorFactory.java b/server/src/main/java/org/opensearch/search/aggregations/bucket/filter/FiltersAggregatorFactory.java
index 8741213f988..be96c0505b2 100644
--- a/server/src/main/java/org/opensearch/search/aggregations/bucket/filter/FiltersAggregatorFactory.java
+++ b/server/src/main/java/org/opensearch/search/aggregations/bucket/filter/FiltersAggregatorFactory.java
@@ -32,10 +32,7 @@

 package org.opensearch.search.aggregations.bucket.filter;

-import org.apache.lucene.search.IndexSearcher;
-import org.apache.lucene.search.Query;
-import org.apache.lucene.search.ScoreMode;
-import org.apache.lucene.search.Weight;
+import org.apache.lucene.search.*;
 import org.opensearch.index.query.QueryShardContext;
 import org.opensearch.search.aggregations.AggregationInitializationException;
 import org.opensearch.search.aggregations.Aggregator;
@@ -102,7 +99,9 @@ public class FiltersAggregatorFactory extends AggregatorFactory {
                 IndexSearcher contextSearcher = searchContext.searcher();
                 weights = new Weight[filters.length];
                 for (int i = 0; i < filters.length; ++i) {
-                    this.weights[i] = contextSearcher.createWeight(contextSearcher.rewrite(filters[i]), ScoreMode.COMPLETE_NO_SCORES, 1);
+                    System.out.println("Original Query : " + ((IndexOrDocValuesQuery)filters[i]).getIndexQuery().getClass());
+                    System.out.println("Rewritten Query : " + contextSearcher.rewrite(filters[i]).getClass());
+                    this.weights[i] = contextSearcher.createWeight(((IndexOrDocValuesQuery)filters[i]).getIndexQuery(), ScoreMode.COMPLETE_NO_SCORES, 1);
                 }
             } catch (IOException e) {
                 throw new AggregationInitializationException("Failed to initialse filters for aggregation [" + name() + "]", e);

Code change:
diff --git a/server/src/main/java/org/opensearch/indices/IndicesQueryCache.java b/server/src/main/java/org/opensearch/indices/IndicesQueryCache.java
index 2669da3f417..97718aeca34 100644
--- a/server/src/main/java/org/opensearch/indices/IndicesQueryCache.java
+++ b/server/src/main/java/org/opensearch/indices/IndicesQueryCache.java
@@ -186,6 +186,12 @@ public class IndicesQueryCache implements QueryCache, Closeable {
             return in.bulkScorer(context);
         }

+        @Override
+        public int count(LeafReaderContext context) throws IOException {
+            System.out.println("Wrapper class type : " + in.getClass());
+            return in.count(context);
+        }
+
         @Override
         public boolean isCacheable(LeafReaderContext ctx) {
             return in.isCacheable(ctx);

Related to #9310


run with usbmuxd

I try to find way to launch peertalk ios with linux server backend.
I try to understand, is there any way to replace peertalk mac os with usbmuxd ( libimobiledevice )
Can I ask for some hint?

https://github.com/davidahouse/peertalk-python
https://makezine.com/2013/04/22/peertalk-beaglebone-and-raspberry-pi/
https://github.com/chid/tcprelay/blob/master/usbmux.py
all this together gives me communication from linux server to iphone.
Thanks!


(Webpack) Replace piping with Webpack HMR

Discussion started here: https://github.com/RickWong/react-isomorphic-starterkit/issues/36#issuecomment-103816919 with @ericfong
The idea is to bring back webpack.server.js (watch & production builds) and use Webpack's Hot Module Reload mechanism for watching changes on the server-side. If it's faster then it will be a more consistent and widely supported replacement for piping.

+1

Tiny update at https://github.com/RickWong/react-isomorphic-starterkit/issues/41#issuecomment-107740396

:+1:
@RickWong, what was the reason for moving away from webpack.server.js in the first place?

+1

What are your ideas on this?
As I understand it, Webpack HMR works by running a small script in the browser that receives updates from Webpack and applies them.
My research so far suggests we would need webpack-dev-middleware along with webpack-hot-middleware. At least it seems that gaeron is heading in that path.
Closest I've come to seeing a working setup for this is this project: glenjamin/ultimate-hot-reloading-example. In his server.js, he does this:
// Do "hot-reloading" of express stuff on the server
// Throw away cached modules and re-require next time
// Ensure there's no important state in there!
var watcher = chokidar.watch('./server');
watcher.on('ready', function() {
  watcher.on('all', function() {
    console.log("Clearing /server/ module cache from server");
    Object.keys(require.cache).forEach(function(id) {
      if (/\/server\//.test(id)) delete require.cache[id];
    });
  });
});

I am not that into all this stuff, but from what I can gather from this snippet, it seems he is wiping the require.cache, meaning the code will be reloaded when it's next required.
In my normal coding style that would be never, but I think this explains why in the snippet just above he is doing the require call inside app.use:
// Anything else gets passed to the client app's server rendering
app.get('*', function(req, res, next) {
  require('./client/server-render')(req.path, function(err, page) {
    if (err) return next(err);
    res.send(page);
  });
});

This seems to work quitte nicely. I do see two problems:

This approach is quite blunt. It would probably perform a lot better if he could somehow only blow out the cache for those modules that have actually changed.
He is requiring babel-register at the top of the file, which hooks babel into the require mechanism... This is great for being able to use es6/7 features in Node, but it also means that on every reload, all these modules are transpiled all over again... Which sounds expensive, especially considering that Webpack is already doing exactly the same for the client bundle.

If only we somehow could use the same code that webpack emits on the Node JS side as well that would be fantastic. But I have no idea whether that is possible and/or if someone is working on it.
Any ideas?

Relevant info:

webpack/docs - hot module replacement with webpack
webpack/docs - How to HMR on server side? #45
jiyinyiyong/webpack-backend-HMR-demo

I've been studying this one by @jlongster: https://github.com/jlongster/backend-with-webpack Though it does not support every type of exported module, because it uses monkey-hot-loader that only updates the changed file. I believe in one of the above articles it says that full webpack HMR bubbling changes up the require-chain is also possible, but I haven't seen that in the wild.
We actually do need Babel's require-hook if we want to support css-modules and other non-JS imports.
So Webpack HMR is optional (as proven by @glenjamin's example) but I do think their HMR API is more battle-tested than a DIY one. And Babel is mandatory.
I'm having a hard time trying to find time to experiment with these set-ups. Would love to get help on this! Anything is appreciated.

It took a while but the server-side now uses Webpack too. That means many webpack loaders should work on the server as well including url-loader and css-loader. (Piping is also gone, the server gets instant code updates from Webpack HMR!)
So please try release ^5.0.0.

Cool! I just got server-side Webpack working yesterday as well, but will def. check this out. Thank you!

@RickWong What are your thoughts on https://github.com/webpack/docs/issues/45#issuecomment-149793458?

You can't use existing HMR loaders like react-hot-loader or style-loader because they make no sense in a server environment. Just add manuall replacement code at the correct location (i. e. accept request handler like in the example)

Is it too much overhead to just include react-transform-hmr and be done with it?

You don't need React HMR because Webpack HMR is enough for the server. The reason React HMR exists is because on the client, you want to keep the rendered components' states (this.state and this.props), but update their logic (render). That's what React HMR does. On the server each http request is preferably stateless. Webpack HMR replaces the components entirely without keeping state, and that's just fine!
For style, I have tried to use style-loader but it stupidly attempts to put <link ...> in a DOM. But there's no DOM on the server. It should rather give us a string "<link ...>" that we can serve out ourselves. I may fork style-loader myself to do this.


fix: file upload not working

File uploads were not working in staging.

Could you explain this change, please? 🙏

Could you explain this change, please? 🙏

What was happening was that axios was formatting the formData object as JSON, and JSON.stringify(formData) equals "{}".
To fix it, this changes the content type of the request so Axios formats the body properly


Get docker

Closes #185
I've included two things:

How to run curl inside docker
How to create an alias in bash to use it seamlessly

Didn't want to get into much detail (like working with files or using named containers to avoid creating a new one each time) because I feel like those things should be documented by the image or even docker itself.

Thanks!


Thesis Document

Thesis Document is under OneDrive: Thesis.docx
All the related assets can be found on OneDrive
The document should include:

[x] State the issue
[x] Related research (existing)
[x] Related research results (outcome from my research)
[ ] CodeTour tool demonstration
[x] Contributing on CodeTour
[x] Vision and future research

For demonstration, a project having CRUD operations and business logic is going to be implemented in order to help others evaluate the CodeTour's effectiveness to onboard to such a project


Adding --line-number ?

Grep has this option :

-n, --line-number
Prefix each line of output with the 1-based line number  within  its  input  file.   (-n  is
specified by POSIX.)

This is useful when you would like to know the line the user selected, for example if multiple lines have the same content but the position in the file matters (which could be useful for a log searcher I am writing).

http://superuser.com/questions/10201/how-can-i-prepend-a-line-number-and-tab-to-each-line-of-a-text-file
Does this help?

Indeed, that does the trick combined with --delimiter and --nth


Pol 134 migration recos

Description
Initial Release of App Migration Recos
Contribution Check List

[x ] All tests pass.
[ x] New functionality includes testing.
[x ] New functionality has been documented in the README if applicable
[ x] New functionality has been documented in CHANGELOG.MD

@cdwilhelm
Incident: https://governance.rightscale.com/org/6/projects/7954/policy-incidents/5db72b29077efb00892dae6e


Fix pickling for instances of classes created using make_class()

Currently, trying to pickle an instance of a class created using attrs.make_class fails (tested on Python 2.7 and 3.5):
>>> import attr
>>> import pickle
>>> C = attr.make_class('C', ['x'])
>>> obj = C(1)
>>> pickle.dumps(obj)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
_pickle.PicklingError: Can't pickle <class 'attr._make.C'>: attribute lookup C on attr._make failed

It has something to do with pickle looking for the class/type in the wrong module. I was curious how collections.namedtuple solves this and found this (also present in Python 2.7):
https://github.com/python/cpython/blob/v3.5.4/Lib/collections/__init__.py#L436-L445
This PR adds the same code (with comment) verbatim to attrs, to make pickling work. As a side effect, the repr of classes created this way now also contain name of the module where make_class() was called instead of "attr._make". I'm not sure if this needs a Changelog/Documentation update?
I also noticed that Python 3.6 added an explicit module parameter to collections.namedtuple, to allow manually overriding the module name to fix issues with pickling on other Python implementations such as IronPython (https://bugs.python.org/issue17941). Maybe this would also be useful to add to attrs in the future.

That looks like a good last-minute change for 17.3 (famous last words).
Would you mind completing coverage and add a changelog entry?  There’s a bunch of cosmetic problems but I can deal with them myself once it’s merged.
Thanks!

That would be awesome.
I've added a changelog entry. I'm not sure what do do about the coverage though, other than using # pragma: no cover. The line that is missing coverage is only there to silence exceptions on more "esoteric" Python interpreters (IronPython, Jython) where sys._getframes is not available or works differently than in CPython, according to the comment from collections.namedtuple.

Maybe try monkeypatch.delattr(sys, "_getframe)"?
If that doesn’t work because it’s too invasive, just add a no cover and call it a Saturday.

Ah yes, that should work. TIL about pytest monkeypatch :)

Wonderful, so you got something out of it too. ;)  Thank you for your contribution!