add s1 photon detected

Before you submit this PR: make sure to put all XENONnT specific information in a wiki-note as the repo is publicly accessible
What does the code in this PR do / what does it improve?
Can you briefly describe how it works?
Can you give a minimal working example (or illustrate with a figure)?
Please include the following if applicable:

[ ] Update the docstring(s)
[ ] Bump plugin version(s)
[ ] Update the documentation
[ ] Tests to check the (new) code is working as desired.
[ ] Does it solve one of the GitHub open issues?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

22 of 26 (84.62%)  changed or added relevant lines in 1 file are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 71.67%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

fuse/plugins/detector_physics/s1_photon_propagation.py
22
26
84.62%

Files with Coverage Reduction
New Missed Lines
%

fuse/plugins/detector_physics/s1_photon_propagation.py
5
92.48%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
2120

Relevant Lines:
2958

💛  - Coveralls


Update author in manifest.json

I can't test this as I can't see the Author in the front-end. So for now it's KO to me...

we need to do a new release


Print with line break

Updated two of the iteration print statements that weren't to use linebreaks. Otherwise, the iterations get overwritten in a notebook and are jammed together in the terminal.

lgtm, thanks @jseabold


Bug: Failed to find assets path for "Frameworks/App.framework/flutter_assets"

Describe the bug
When I added all the firebase config for ios and run the flutter project. The error comes out.
Failed to find assets path for "Frameworks/App.framework/flutter_assets"
The project is still run but it is a white screen.

Expected behavior
The Flutter Project should run correctly and show the home page.

This link might be helpful: https://flutter.dev/docs/development/ios-project-migration

Solved using this link: https://flutter.dev/docs/development/ios-project-migration


Add ftdetect for org-mode filetype

Just a small PR that adds ftdetect for Emacs' orgmode filetype.
There are already various plugins for vim and neovim to get ormode working. Having the filetype natively recognized might help

Please add a test entry in src/testdir/test_filetype.vim


Simulation exit procedure

At the moment there is no graceful way to exit the simulator. Our CI essentially waits for content in the UART log file and then the process is killed. It would be nice to have a better way of doing this.
One way of doing this is implementing simulation control like we do in Ibex demo system: https://github.com/lowRISC/ibex-demo-system/blob/a1201cf2b99f8f4149c0971c04c655adbf1753c4/rtl/system/ibex_demo_system.sv#L404-L419
Anyone have any particular opinions on the best way of doing this?

After some discussions, it may be better to have a special UART sequence to exit the simulator to avoid having unnecessary differences between FPGA and simulation.

There's a proposal PR here: https://github.com/lowRISC/sonata-system/pull/368


Hardcode IP address in config.json

I wish to hardcore the (static) IP address to my Yeelight Color bulbs. My accessories now tend to be “Updating” more frequently and longer than before installing this plugin and perhaps it is because of finding the Yeelight. Could you please provide a config.json template for adding two or more IP addresses to the platform?
Thanks for writing this plugin!

Increase connection timeout to a higher value, e.g. from 100 to 250.

Have segmented LAN, with IoT in another LAN and standard discovery don't work.
I think, that the adding static IP to config.json will be excelent.

hi, is this implemented yet? it would be a nice addition

Not sure if this is all you need but you can set a custom interface in config.json for multicast, see readme.
      "multicast": {
        "interface": "<ip-addr>"
      },


[BUG]  Storageclass does not work when it has the parameter frontend:iscsi

Describe the bug

StorageClass.yaml

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: longhorn
provisioner: driver.longhorn.io
allowVolumeExpansion: true
parameters:
  numberOfReplicas: "3"
  staleReplicaTimeout: "2880" # 48 hours in minutes
  fromBackup: ""
  frontend: "iscsi"
  standby: "true"
#  diskSelector: "ssd,fast"
#  nodeSelector: "storage,fast"
#  recurringJobs: '[{"name":"snap", "task":"snapshot", "cron":"*/1 * * * *", "retain":1},
#                   {"name":"backup", "task":"backup", "cron":"*/2 * * * *", "retain":1,
#                    "labels": {"interval":"2m"}}]'

pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: longhorn-volv-pvc
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn
  resources:
    requests:
      storage: 2Gi

But it's still a Block Device

I found this bug

You're not dealing with parameters like frontend standy

Please repair it
https://github.com/longhorn/longhorn-manager/blob/master/csi/util.go

func getVolumeOptions(volOptions map[string]string) (*longhornclient.Volume, error) {
	vol := &longhornclient.Volume{}

	if staleReplicaTimeout, ok := volOptions["staleReplicaTimeout"]; ok {
		srt, err := strconv.Atoi(staleReplicaTimeout)
		if err != nil {
			return nil, errors.Wrap(err, "Invalid parameter staleReplicaTimeout")
		}
		vol.StaleReplicaTimeout = int64(srt)
	}
	if vol.StaleReplicaTimeout <= 0 {
		vol.StaleReplicaTimeout = defaultStaleReplicaTimeout
	}

	if numberOfReplicas, ok := volOptions["numberOfReplicas"]; ok {
		nor, err := strconv.Atoi(numberOfReplicas)
		if err != nil || nor < 0 {
			return nil, errors.Wrap(err, "Invalid parameter numberOfReplicas")
		}
		vol.NumberOfReplicas = int64(nor)
	}

	if fromBackup, ok := volOptions["fromBackup"]; ok {
		vol.FromBackup = fromBackup
	}

	if baseImage, ok := volOptions["baseImage"]; ok {
		vol.BaseImage = baseImage
	}

	if jsonRecurringJobs, ok := volOptions["recurringJobs"]; ok {
		recurringJobs, err := parseJSONRecurringJobs(jsonRecurringJobs)
		if err != nil {
			return nil, errors.Wrap(err, "Invalid parameter recurringJobs")
		}
		vol.RecurringJobs = recurringJobs
	}

	if diskSelector, ok := volOptions["diskSelector"]; ok {
		vol.DiskSelector = strings.Split(diskSelector, ",")
	}

	if nodeSelector, ok := volOptions["nodeSelector"]; ok {
		vol.NodeSelector = strings.Split(nodeSelector, ",")
	}

	return vol, nil
}

Hi @antmoveh
Storage Class doesn't support iscsi as frontend. Kubernetes should always use block device as the front-end. Our CSI driver wasn't designed to work with iscsi front-end. What's your use case for exposing the iscsi device to Kubernetes?

Hi @antmoveh
Storage Class doesn't support iscsi as frontend. Kubernetes should always use block device as the front-end. Our CSI driver wasn't designed to work with iscsi front-end. What's your use case for exposing the iscsi device to Kubernetes?

Now there's a problem with Block devices，
pvc.yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: longhorn-volv-pvc
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn
  resources:
    requests:
      storage: 2Gi

When deployment replicas=2, the following error is reported when mounting the PVC

Unable to create pv in ReadWriteMany mode
pvc2.yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: longhorn-volv-pvc2
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: longhorn
  resources:
    requests:
      storage: 2Gi

I want to know when the deployment replicas>1, how should it be mounted

Longhorn is a distributed block storage system. Like EBS, it doesn't support Read-Write-Many. So if you want to scale the deployment to more than one, you will need the deployment to be bind to one node.
Or you can use StatefulSet with VolumeClaimTemplate which will create a volume for each pod automatically and scales properly with Longhorn.

@yasker
Thank you for your answer, I know how to use it


chore: cleanup v5 beta changelog

Description
Clean up changelog until v5.0.0-beta.10:

removed small chore PRs
pushed breaking changes to the top
split by Features, Performance, Fixes, Cleanup

This is what we have been doing in previous releases, but now that we are spending more time on the migration guides we may want to discuss if it is needed and if these cleanups are helping users, or if it will be better to leave the history of each version as is (that would be useful to see that the rollup bump is in its own PR).

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[x] Documentation update
[ ] Other

Making this a draft, it is going to be useful for people to see the commits in each beta if they are debugging. I'll merge it with the final changes for the final v5 release.


Add double-faced cards as tokens?

Would it make sense (and be possible) to use the Token system to manage flip cards?
An example would be Huntmaster of the fells && Ravager of the Fells.
A way to get around the unique name problem is adding a space at the end of the name (already the case for alternative tokens).

Fixed with https://github.com/Cockatrice/Cockatrice/releases


multigpu agent57

I'm having issues running multigpu on Agent57 in the same way I run them on let's say R2D2.
Where I change
    actor_devices = [runtime_device] * FLAGS.num_actors
to
    actor_devices = [torch.device('cuda:0'),torch.device('cuda:1')....etc etc] * FLAGS.num_actors
So this works for R2D2 but not Agent57, howcome?
Thank you.

Hi,
There are more stuff involved in Agent57, as it uses RND networks and meta controllers. Unfortunately we don't have access to multiple GPUs on our side, so it's hard to debug this. And we don't plan to support this feature at the moment.
Thank you for reporting the issue.


Adding inter-channel corrrelations into obs errors for IR

Description
The inter-channel correlations are added into the obs errors for hyperspectral IR observations.
Dependencies

[ ] NA

Impact

[ ] Need further testing

I think this can be closed ... what's in develop already incorporates correlated R.

As we talked about Wei: the most important thing on this is make sure the obs counts make sense and that the proper changes are being used - there seems to be too much going on at high-levels ... way more than in a corresponding GSI run. And this I see independently of any corr(R)  stuff.
As we talked about: some of what might cause this could be associated w/ the geovals still not being quite right.


[Streaming][Kafka][SPARK-8127] KafkaRDD optimize count() take() isEmpty()

…ed KafkaRDD methods.  Possible fix for [SPARK-7122], but probably a worthwhile optimization regardless.

Can one of the admins verify this patch?

Jenkins, add to whitelist

ok to test

At a glance this makes sense to me. Let's see what tests say.

Merged build triggered.

Merged build started.

Test build #34181 has started for   PR 6632 at commit c3768c5.

Test build #34181 has finished for   PR 6632 at commit c3768c5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Can you make a JIRA for this and add it to the title of the PR (see other PR's formatting). And title of the JIRA and PR could be a little more obvious - KafkaRDD optimizations for count() and take()

Other than that this looks very promising.

Merged build triggered.

Merged build started.

Test build #34323 has started for   PR 6632 at commit 8974b9e.

Test build #34323 has finished for   PR 6632 at commit 8974b9e.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34348 has started for   PR 6632 at commit 253031d.

Test build #34348 has finished for   PR 6632 at commit 253031d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@tdas is there anything else you feel needs to be done on this?

I think its almost good to go. Few minor points.

Merged build triggered.

Merged build started.

Test build #35310 has started for   PR 6632 at commit f68bd32.

Test build #35310 has finished for   PR 6632 at commit f68bd32.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      //     class ParentClass(parentField: Int)
      //     class ChildClass(childField: Int) extends ParentClass(1)
          // If the class type corresponding to current slot has writeObject() defined,
          // then its not obvious which fields of the class will be serialized as the writeObject()
abstract class GeneratedClass
case class Bin(child: Expression)
case class Md5(child: Expression)

Merged build finished. Test PASSed.

Just a couple of more comments on the tests.

Merged build triggered.

Merged build started.

Test build #35329 has started for   PR 6632 at commit 5a05d0f.

Merged build triggered.

Merged build started.

Test build #35331 has started for   PR 6632 at commit 321340d.

Test build #35329 has finished for   PR 6632 at commit 5a05d0f.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      //     class ParentClass(parentField: Int)
      //     class ChildClass(childField: Int) extends ParentClass(1)
          // If the class type corresponding to current slot has writeObject() defined,
          // then its not obvious which fields of the class will be serialized as the writeObject()
abstract class GeneratedClass
case class Bin(child: Expression)
case class Md5(child: Expression)

Merged build finished. Test PASSed.

Test build #35331 has finished for   PR 6632 at commit 321340d.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      //     class ParentClass(parentField: Int)
      //     class ChildClass(childField: Int) extends ParentClass(1)
          // If the class type corresponding to current slot has writeObject() defined,
          // then its not obvious which fields of the class will be serialized as the writeObject()
abstract class GeneratedClass
case class Bin(child: Expression)
case class Md5(child: Expression)

Merged build finished. Test PASSed.

Merging this to master

Wait, oh, the title, please fix order :/

fixed title

Merging to master.

I forgot to say, thanks Cody! :)

Cheers :)
On Wed, Jun 24, 2015 at 2:06 PM, Tathagata Das<EMAIL_ADDRESS>wrote:

I forgot to say, thanks Cody! :)
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/6632#issuecomment-114982313.


Updated to latest dependency versions and Swift 4

This was quite a simple commit - basically just the package dependencies have been updated.
All tests are passing.

@Davidde94 Thanks for the PR! Before we can process the PR, can you go over the checklist below? We now have a PR template (when you opened the PR we did not have one in place). If you have contributed before our GitHub org, then you should have a CLA in place.
Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

In addition to the checklist above, a few more changes would be required:

We should upgrade to Swift 4.0.2 https://github.com/IBM-Swift/Kitura-redis before upgrading this repo to Swift 4.0.2 (see items below to see what the steps we take when migrating repos to Swift 4.x).
.swift-version should be updated to 4.0.2.
Compilation errors or warnings that result from moving to Swift 4.0.2 should be addressed.
Package.pins should be deleted.
.gitignore should be updated to include an entry for Package.resolved.
.travis.yml should be updated (as reference see https://github.com/IBM-Swift/CloudEnvironment/blob/master/.travis.yml
We should update the README accordingly to state that Swift 4.0.2 is required (instead of Swift 3)

If you have the bandwidth to tackle the above items, feel free to tackle them. Otherwise, we plan to upgrade these libraries at some point.

@rolivieri thanks for taking I look.
I signed a CLA today, just before sending this PR, and just emailed it to<EMAIL_ADDRESS>I'll also tackle the other bits on your checklist ASAP (hopefully today).

Codecov Report

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

@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   64.58%   64.58%
=======================================
  Files           1        1
  Lines          96       96
=======================================
  Hits           62       62
  Misses         34       34

Flag
Coverage Δ

#KituraSessionRedis
64.58% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Project should target lower NetStandard version

Hi!
Description
Currently AngleSharp 0.10.0 targets NetFramework 4.6 and NetStandard 2.0, but it can target lower version.
Background
As described in https://docs.microsoft.com/en-us/dotnet/standard/net-standard NS2.0 is supported only by newer platforms versions. But in real world there are cases, when we our applications have to support out of dated platfroms and we can't easelly use NS2.0 libralies.
In my case, I support UWP 14393.0, which allows to use only NS1.4 or lower.
Yes, you can say, that we should use also out of dated version of AngleSharp, but I don't think, that is good ending of problem.
What we can do
NetStandard 1.3
We can target NS1.3 with adding some official nuget packages, which is not included by default
<ItemGroup Condition="'$(TargetFramework)' == 'netstandard1.3'">
  <PackageReference Include="System.Net.Requests" Version="4.3.0" />
  <PackageReference Include="System.Reflection.TypeExtensions" Version="4.5.1" />
</ItemGroup>

NetStandard 1.1
As @tbolon described in https://github.com/AngleSharp/AngleSharp/pull/715#issuecomment-434459838 we can target NS1.1 if we replace HttpWebRequest with HttpClient.
I tried to target 1.1 and noticed at first look, that we also should write refrection polyfills to replace System.Reflection.TypeExtensions package and should found alternative for System.Text.Encoding.CodePages.
Thanks for AngleSharp :)
Best regards, Max Katz.

Hi Max - awesome PR. Definitely a sound request and 1.3 sounds fine to me!
Even 1.1 sounds fine; but maybe 1.3 is low enough. Let's just see if someone else really wants 1.1, otherwise I would just go with 1.3.

(We'll ship it in the v0.11, which will be the filler to v1.0 - taking into consideration all comments; suggestions, fixes etc. - time-boxed, i.e., to be released Feb '19 or earlier)


[Nacos] Support ServerIntrospector

Which Component
Nacos Discovery
Is your feature request related to a problem? Please describe.
refer https://github.com/spring-cloud-incubator/spring-cloud-alibaba/issues/649.

Thanks for your contribution, we will review it soon.


DT Create Help page for About the GRO

Needed for link in red band.

@PatReynolds to draft text, including an invitation to order certificates from the GRO.  Nb this is now the bottom PINK band

Hello Pat,
This comment of yours dropped into my email box a few hours ago, so I decided to comment.
Looking at the main Help page and the subsiduary pages hanging off it (and the same could be said for the About pages) there seems to a fair amount of close duplication of information (note: there is a distinction to be made between close duplication and the provision of additional information via a hyperlink); and that will need to be addressed fairly soon. So I though it might be useful now to discuss the scope of the new page.
Possibly, the most significant differences between FreeBMD and FreeCEN  /  FreeREG is that events are arranged by Registration District (bound into Volumes), the  (GRO) Page number and Date (Quarter / year) and not by County (event, date, etc). The county-search that is done on FreeBMD(1 & 2) is done by (in a black-box manner") by reverse mapping District / Volume No. onto County. So, there are various pages such as Districts in Counties and Districts-Volumes-Pages to try and explain this. There is another difference: FreeBMD and FreeCEN use centralised data (GRO / Registrar General  / ONS) , whereas FreeREG is local data created at the Parish level.
This is a draft page on test3 covering: Civil Registration Authorities (which has a paragraph on the GRO). and there are more specialised pages on Ordering Certificates and Understanding the GRO Index Page (plus the "Registration District" pages mentioned above).
It seem to me that there are several ways forward: one is to create a new page (as per this Issue) and to use it as a entry point for hyperlinking to these other pages that already exist in FreeBMD(1) and are also on test3 in Draft form. So, I would be interested in what you see as the main scope of this page .
Philip

This page is now being written, a early draft somewhat incomplete (an understatement) is on test3.

This is now, perhaps, half-written and I decided to move the draft to the Transcriptions Tab where it fits in with all those other draft pages I mentioned above. Many of these draft pages are called up from both Help pages and Transcriptions pages, so where it/they sits is probably not too important. However, the effect of researching the GRO is producing "ripples" which I may well add to  those draft pages I mentioned above, as well as the draft Transcriptions page which I am also working on.
County Boroughs and County Councils were created as late as 1888, so the area of a Superintendent Registrar was the area of the Poor Law Union (which did not respect county boundaries), but the GRO outlived the system of the workhouses (they often became hospitals and remained in use till almost now) and so RDs became more and more aligned with local council areas (which also changed over the last 135 years). But, workhouses becoming hospitals will be outside the scope of this page.

This is now, perhaps, half-written and I decided to move the draft to the Transcriptions Tab where it fits in with all those other draft pages I mentioned above. Many of these draft pages are called up from both Help pages and Transcriptions pages, so where it/they sits is probably not too important. However, the effect of researching the GRO is producing "ripples" which I may well add to  those draft pages I mentioned above, as well as the draft Transcriptions page which I am also working on.
County Boroughs and County Councils were created as late as 1888, so the area of a Superintendent Registrar was the area of the Poor Law Union (which did not respect county boundaries), but the GRO outlived the system of the workhouses (they often became hospitals and remained in use till almost now) and so RDs became more and more aligned with local council areas (which also changed over the last 135 years). But, workhouses becoming hospitals will be outside the scope of this page.

Hi @PhilipClarke712 that's a great set of pages!
On the 'Ordering Certifictes' page, I think the bottom section needs to be at the top - it's the "must have" information on this page.
For discussion:
How to order a transcription needs a direct  link from various pages in-page, I think the "Entry Information" page is most important.
Include the essential 'how to order certificates' section in the Help page with a link to the lower section of the 'ordering certificates' page?
Link from the Entry Information Page (location ? Between "Scans" and "Corrections"? or between "Next Record" and "Results"? Or Somewhere else?
It is noted elsewhere that this link is "In the footer" - definitely a good place for it to be, additionally.

Hi @PhilipClarke712 that's a great set of pages!
On the 'Ordering Certifictes' page, I think the bottom section needs to be at the top - it's the "must have" information on this page.
For discussion:
How to order a transcription needs a direct  link from various pages in-page, I think the "Entry Information" page is most important.
Include the essential 'how to order certificates' section in the Help page with a link to the lower section of the 'ordering certificates' page?
Link from the Entry Information Page (location ? Between "Scans" and "Corrections"? or between "Next Record" and "Results"? Or Somewhere else?
It is noted elsewhere that this link is "In the footer" - definitely a good place for it to be, additionally.

@PatReynolds,
Thanks for your comments. I've moved the "Ordering section(s)" to the top, renamed the previous first section to "Why get a Certificate?" and adjusted the side navigation panel accordingly; and left it at that.
Note: I need to rework some of the hyperlinks - but I'll do that anyway!
I think having done this change: the page needs reworking: I have a subscription to two of the commercial sites; and (if Covid-19 lockdowns were not in place) as an alternative I could go to my local library and use them for free (with a time limit: 55 minutes?). Birmingham for instance has put its parochial marriage records on one of those sites (up to about the 1910s) and the Welsh government makes them available free on a web site. So, should we not mention this (and other marriage records) rather than just sending people off to pay their £11/£12 to the GRO for marriage records, some of which might be commercial available (and the access fees already paid for by "someone" - me or my library) or free in the case of Wales?

@PatReynolds,
Thanks for your comments. I've moved the "Ordering section(s)" to the top, renamed the previous first section to "Why get a Certificate?" and adjusted the side navigation panel accordingly; and left it at that.
Note: I need to rework some of the hyperlinks - but I'll do that anyway!
I think having done this change: the page needs reworking: I have a subscription to two of the commercial sites; and (if Covid-19 lockdowns were not in place) as an alternative I could go to my local library and use them for free (with a time limit: 55 minutes?). Birmingham for instance has put its parochial marriage records on one of those sites (up to about the 1910s) and the Welsh government makes them available free on a web site. So, should we not mention this (and other marriage records) rather than just sending people off to pay their £11/£12 to the GRO for marriage records, some of which might be commercial available (and the access fees already paid for by "someone" - me or my library) or free in the case of Wales?

Decided that enough is on the website about the GRO so closing


node build ignores package.lock & doesn't work with vendored deps

The node runtime build copies over package.json but not package.lock to the build dir before running npm install  - this nixes any package locks on the project and gives you unpredictable builds.
also npm install  should be skipped if node_modules is already present in the build.
Expected behaviour:

If node_modules is present, skip npm install completely
if package.lock is present, copy it alongside package.json before running npm install

I believe this is fixed in https://github.com/fnproject/cli/pull/171, can we close this issue?

yep, fixed,


[camera] Fix example from README.md

This PR updates the outdated example code listed in the camera README.md file.

Resolves flutter/flutter#76537

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I signed the CLA.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

We'll be publishing camera soon for NNBD stable, so we can just push this fix out then.

Sure thing, that would be great. I will be converting camera to NNBD stable tomorrow morning.
By the way, it is Maurits van Beusekom from Baseflow (Maurits#7932 on Discord).


fix: remove export of OpenFeatureClient

This PR
As discussed here https://github.com/open-feature/js-sdk/pull/750#discussion_r1450896230, we should not export OpenFeatureClient from the server and web SDK. The type used outside the SDK should be Client, which is also used in the public APIs like OpenFeatureApi.
The question is, if we should mark this as breaking.
Technically it will break code that imports OpenFeatureClient instead of Client, but as @toddbaert said code using it  could also be seen as "used wrong" while being technically fine.
I am still leaning towards marking it as breaking, to be sure we are not breaking something that is technically fine, just because it is unintended use. But I could also live with non-beaking.

I think we can (debatabley) consider this non-breaking, since it's an export we didn't expect people to use... it really depends how strict we want to be.
In any case, I think it might be a good idea to discuss rolling together some upcoming breaking changes. I'd like to also include:

making it impossible to return an error resolution from providers (force them to throw if something goes wrong)
removing setProviderAndWait and just making setProvider async

What do you guys think?
cc @lukas-reining @beeme1mr @luizgribeiro @Kavindu-Dodan

I think we can (debatabley) consider this non-breaking, since it's an export we didn't expect people to use... it really depends how strict we want to be.
In any case, I think it might be a good idea to discuss rolling together some upcoming breaking changes. I'd like to also include:

making it impossible to return an error resolution from providers (force them to throw if something goes wrong)
removing setProviderAndWait and just making setProvider async

What do you guys think?
cc @lukas-reining @beeme1mr @luizgribeiro @Kavindu-Dodan

+1 for combining multiple breaking changes for the next release

I'd say it's a breaking change because if it's shipped as is since it would break minor upgrades in projects that are already using OpenFeatureClient. I also think bundling more breaking changes in one new major is a good alternative.
Maybe another way that might not be a breaking change is to expose OpenFeatureClient as an alias type to Client. I'm not a big fan of using Client as a type. Many different packages have a Client exported type and it would end up with an alias anyway.

I think it's OK to require people to alias things, but I would be up for changing the name to something more specific in a 2.0. I definitely don't want to alias the OpenFeatureClient though since it's a class. It's a good idea to export and reference interfaces instead of classes where-ever possible, or you can run into nasty things like this which can happen if people end up with multiple copies of a dep (we do our best to avoid that but it can happen).

I've opened this to record (small) proposed breaking changes in 2.0

@lukas-reining @luizgribeiro @beeme1mr I've rebased and resolved conflcits on this PR.
I also made the title non-breaking as we decided (though it's technically a break but not on an export we indented people to use).


Update autorest version to prerelease 3.0.0-alpha.20240426.6.x

Triggered from pull request: https://github.com/Azure/autorest.csharp/pull/4185

API change check
API changes are not detected in this pull request.

Close in favor of #43872


removeProxyHeaders should be optional

In case I want to chain proxies, this function just remove any authentication between me and the chained proxy server

@elazarl what do you think?

BUMP!

@AlmogBaku I don't think so. The proxy header should be added back by the transport, doesn't it?
Apologize for the delay, too busy lately.

@elazarl actually no, you removing these headers in the removeProxyHeaders() method in the goproxy package (proxy.go:74)

BTW, i'll appreciate your response in Slack.. trying to reach you there for a while

Currently there is a configurable option to not call it. Closing this issue.


Potentially Misleading Link warning doesn't deal with capitalisation in URLs (maybe iOS only?)

Describe the bug
See: https://bsky.app/profile/bossett.bsky.social/post/3kc7dpy3yqy2e - this link pulls up a malicious link warning, despite the URL matching the text.

To Reproduce
Steps to reproduce the behavior:

Make a post with http://tEsT.com/ or similar - the link in the post will be lowercased, but in the facet it will not be.

Expected behavior
No Malicious Link warning should appear
Screenshots

Details

Platform: iOS
Platform version: -
App version: 1.54.0 (1)

looks like this might be specific to React Native/Hermes because the URL API is expected to normalize the hostname for Chrome/V8 and Firefox/SpiderMonkey

Filed an issue with our polyfill: https://github.com/charpeni/react-native-url-polyfill/issues/462
Smoothed over this specific issue in #1980, but we should revisit.


Project logo and favicon.ico design

Design a logo for the project.
Then, create a favicon.ico file for the web server.

I will prepare some sketches. Would you prefer something similar to other Go libraries or something else, need ideas 🤯

Few ideas

@wralith these look amazing!
I like the one with the green car and the one below on the right with the gear.
The main idea of the app is to do things in Go automatically (not car-related), and quick development.
Here are some words if you'd need some more inspiration: fast, speed, robot, conveyor belt


Default browser arrows for a numeric input displayed in NumberInput component in Firefox

Detailed description

Describe in detail the issue you're having.

Default browser arrows are displayed in NumberInput component in Firefox.

Is this a feature request (new component, new icon), a bug, or a general issue?

Bug

Is this issue related to a specific component?

NumberInput

What did you expect to happen? What happened instead? What would you like to see changed?

Default browser arrows are not displayed as there already are + - - buttons displayed on hover.

What browser are you working in?

Firefox 119.0.1

What version of the WFP UI (Carbon Design System) are you using?

1.22.4

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

Partner Connect
Steps to reproduce the issue

Navigate to https://uikit.wfp.org/docs/index.html?path=/docs/components-forms-numberinput--regular in Firefox browser.

Additional information

Screenshots or code

Default:

On hover:

Hi @rstencel We have a newer version available (on Azure) which has a fix for that bug, but it also changes most of the look and feel. Would you like to try?

Hi @rstencel We have a newer version available (on Azure) which has a fix for that bug, but it also changes most of the look and feel. Would you like to try?

Sure, I'd love to try it out!


Color attribute not applying color to md-sidenav

Bug, feature request, or proposal:
Hey guys, so I am using angular2 + material to build a new idea I have and attempted to apply color to md-sidenav. It seems that the "color" attribute has no affect at all on the md-sidenav component.
What is the expected behavior?
I expect the background color of the md-sidenav component to change color when I add the "color" attribute. This color should reflect the value I pass in (color="primary" etc.)
What is the current behavior?
The background color is not changing at all. It is a white background as set by:
md-sidenav {
    background-color: white;
    color: rgba(0, 0, 0, 0.87);
}

What are the steps to reproduce?
Simply try adding a color to the md-sidenav component using the "color" attribute.
http://plnkr.co/edit/L01XgLc93vILoyRpPP7V
What is the use-case or motivation for changing an existing behavior?
The use-case would be to allow easy theming of the md-sidenav component.
Which versions of Angular, Material, OS, browsers are affected?
Here is the environment I am developing it (fresh install from earlier yesterday from NPM):
$ ng -v

                             _                           _  _
  __ _  _ __    __ _  _   _ | |  __ _  _ __         ___ | |(_)
 / _` || '_ \  / _` || | | || | / _` || '__|_____  / __|| || |
| (_| || | | || (_| || |_| || || (_| || |  |_____|| (__ | || |
 \__,_||_| |_| \__, | \__,_||_| \__,_||_|          \___||_||_|
               |___/
@angular/cli: 1.0.0-beta.31
node: 7.4.0
os: linux x64
@angular/common: 2.4.7
@angular/compiler: 2.4.7
@angular/core: 2.4.7
@angular/flex-layout: 2.0.0-beta.5
@angular/forms: 2.4.7
@angular/http: 2.4.7
@angular/material: 2.0.0-beta.1
@angular/platform-browser: 2.4.7
@angular/platform-browser-dynamic: 2.4.7
@angular/router: 3.4.7
@angular/cli: 1.0.0-beta.31
@angular/compiler-cli: 2.4.7

$ uname -a
Linux ***** 4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016 x86_64 GNU/Linux

$ google-chrome-stable --version
Google Chrome 55.0.2883.87

Is there anything else we should know?
  I think you would need to tell it which theme to use instead.

I think what @staticinteger is referring to is there is no way to set background color of sidenav component other than the default one.
@michael-lang do you know how to specify theme that should be used? I didn't find anything about theming sidenav, maybe I missed it...
Just adding .scss file with custom theme didn't work for me.

@zendist yes, there is an official way to create multiple themes and apply one to an element and descendents.  However,  there is an issue #4344 in applying it directly to a sidenav due to the html structure requirement.   See #4344 for temporary work-around and details why it doesn't work now.

Only certain components have a color property; these are components that specifically have some primary/accept/warn color associated with them in the spec. Sidenavs are just containers and don't have an associated color.


fix logic of the script

2 would never have been returned, because $status would not contain the
value which indicates healty, if $ret is not 0.

Thanks for your contribution. Can you confirm whether you've signed the Oracle Contributor Agreement: https://www.oracle.com/technetwork/community/oca-486395.html? If not, you'll need  review and submit a signed OCA before this pull request can be considered.

Closing due to lack of signed OCA.


Equipment items (tech/magic/hybrid/augmentations) missing actions

Currently tech/magic/hybrid/augmentations equipment items do not have an action section in the details.
Some items list an action associated with their use. As well as having such a function would allow more functional capacity usage. Such as tech items that use charges.

Closed by #1108


Bug - Content overflows in Mobile view

Description

[ ] Content to occupy full width in mobile view
[ ] Add ellipsis at the end of the main content
[ ] Change character limit to 1000

Screenshot

@jacobtyq Can elaborate on what scenario the ellipsis will appear?

@SheldonCheng probably when text cuts off like in this screenshot. But rethinking this now maybe it is not required as it is not a excerpt.
What do you think?

It shows the full content of the user's text, so I can see why an ellipsis is needed.
My guess for what happened above is that Andana just pasted a chunk of text in without realised it got cut off and just submitted.


feat:update-match

Changes:

When a match is updated to be over, it will send the winning team into the next match (not based on score, but based on WinningClubId; this is to account for possible additional complexity, away goal rules or penalties etc.)
Validation added to check if clubs are valid, if winningclubid is one of the two clubs

Issues:

It is assumed that a match in a later round (further into the tournament) can be updated even if its prior matches are not over, this is done for easier testing and to account for possible bye rounds
No logic currently to account for matches where there is only 1 or 0 clubs in the match

also authentication token is added to validate user can update tournaments


Remove an unnecessary call to then().

I see that this file has a little use of async/await and many uses of then().
Things would be much less verbose and much more linear if async/await were used throughout.
Would Atom be open to a PR that changes this?
For bonus points, we could also replace 'use babel' with /* @flow */ at the top of the file :)

Things would be much less verbose and much more linear if async/await were used throughout.
Would Atom be open to a PR that changes this?

We've had some concerns about the performance of the code Babel translates async/await into, so I'm a bit hesitant to translate it fully until that improves, or we have a better handle on how it performs in practice.

For bonus points, we could also replace 'use babel' with /* @flow */ at the top of the file :)

Maybe some day :sweat_smile:

Thanks @bolinfest!

@joshaber Thanks for taking the PR. Do you have any data to back up your performance concerns around async/await? I believe you would end up creating fewer closures in many cases.

Do you have any data to back up your performance concerns around async/await?

No, it was just something we talked about in chat. I'd love to be shown wrong.


Provider v3.0.0 allows project to look like it is created even though it pre-exists

When running terraform apply with a newly-defined resource "aiven_project" block, but where the block uses a project name which already exists elsewhere in the account, then instead of throwing a Project already exists error, the Terraform provider tells me that it has successfully created the project.
v2.7.3 gives me Error: 409: {"errors":[{"message":"Project already exists","status":409}],"message":"Project already exists"}

Looks like the new project create code is this:
aiven.CreateProjectRequest{
    Cloud:                        schemautil.OptionalStringPointer(d, "default_cloud"),
    CopyFromProject:              d.Get("copy_from_project").(string),
    Project:                      projectName,
    TechnicalEmails:              contactEmailListForAPI(d, "technical_emails", true),
    AccountId:                    schemautil.OptionalStringPointer(d, "account_id"),
    UseSourceProjectBillingGroup: d.Get("use_source_project_billing_group").(bool),
    BillingGroupId:               d.Get("billing_group").(string),
},

... whereas the older code is this:
aiven.CreateProjectRequest{
    BillingAddress:               billingAddress,
    BillingEmails:                contactEmailListForAPI(d, "billing_emails", true),
    BillingExtraText:             billingExtraText,
    CardID:                       cardID,
    Cloud:                        schemautil.OptionalStringPointer(d, "default_cloud"),
    CopyFromProject:              d.Get("copy_from_project").(string),
    CountryCode:                  countryCode,
    Project:                      projectName,
    TechnicalEmails:              contactEmailListForAPI(d, "technical_emails", true),
    AccountId:                    schemautil.OptionalStringPointer(d, "account_id"),
    BillingCurrency:              billingCurrency,
    VatID:                        vatID,
    UseSourceProjectBillingGroup: d.Get("use_source_project_billing_group").(bool),
    BillingGroupId:               d.Get("billing_group").(string),
},

However, from what I can tell, the error-handling is the same, so I wonder if the API is actually giving the wrong response for the different fields?

I've tried calling the API directly, with the same payload as the TF provider is calling, and it correctly responds with a 409:
{"project":"kbowman-temp-test","account_id":"a2********c4","add_account_owners_admin_access":false}

I think I've found the problem; in v2.7.3 when an API error happened on project create, the relevant function returned the error whereas in v3.0.0 the error handler doesn't return, and execution carries on as if the API call succeeded.


RHINENG-14556 remove old code to keep the new service independent

Why do we need this change? :thought_balloon:
Eliminating codes that are not necessary for the new backend.
Documentation update? :memo:

[ ] Yes
[X] No

Security Checklist :lock:
Upon raising this PR please go through RedHatInsights/secure-coding-checklist
:guardsman: Checklist :dart:

[ ] Bugfix
[ ] New Feature
[X] Refactor
[ ] Unittests Added
[ ] DRY code
[ ] Dependency Added
[ ] DB Migration Added

Additional :mega:
Feel free to add any other relevant details such as links, notes, screenshots, here.

/retest

@r14chandra I can see we have not touched the models, so with this pr my impression is we go with current models as is and later on tweak it as per requirements?

@r14chandra I can see we have not touched the models, so with this pr my impression is we go with current models as is and later on tweak it as per requirements?

Yes, that's true. It’s also possible that what I am removing right now may be needed later.


Debug "Add grape-jdk benchmark apps (#1019)"

What do these changes do?
This reverts commit 115ddf0b8a8b5da7900bec92e9aee707d24d1191.
Resubmission of #1019, for debugging issue imposed by #1019
Related issue number
Fixes #1019 and further fixes #1018

Just for debugging, this PR would be merged.

Closed as the issue has been fixed in #1044.


I want to scale the image of android Camera multiHandLandmarks. Where should I scale the model input?

I want to scale the image of android Camera multiHandLandmarks. Where should I scale the model input?

Hi @LMR2018,  The mediapipe models are limited to fixed-size input. So it is not recommended to scale the image. Doing it may or may not give you the appropriate results.

@sgowroji I want to convert camera frame data of camera mode in Android Hand_landmark model into bitmap data, and then deduce bitmap of the model. How should I convert it?


Array wrapped in Object when root array desired

Hi,
I stumped across this issue. When creating a root array with no name, I found that my RestTemplate couldn't understand the result generated from the WireMock server. I had a look at the response from the Wiremock server, and found this:
{"['']":[{"number":348572882,"name":"JbpmGypbDvMKtyHOylug","secret_identity":"jLhsuPPmVkjXHUiHZFgL","id":1534343303}]}
It looks as though it's trying to wrap the root array in another object. Here's my PactDslJsonBody
new PactDslJsonBody() 				.array("") 					.object() 						.id() 						.stringType("name") 						.stringType("secret_identity") 						.integerType("number") 					.closeObject() 				.closeArray();
Any ideas why this might be happening?

A friend of mine pointed me towards this: https://github.com/DiUS/pact-jvm/pull/103
This has solved the above issue.
The resultant code is:
new PactDslJsonArray() 				.object() 					.id() 					.stringType("name") 					.stringType("secret_identity") 					.integerType("number") 				.closeObject();


Specification code and metanode config file

Signed-off-by: awzhgw<EMAIL_ADDRESS>

Contains the following changes:

Synchronization config file from docs
Remove the word baundsage
3.rename storage.EveryTinyDeleteRecordSize  to storage.DeleteTinyRecordSize
4.metanode config file force check
5.The ChubaoFS Authors. rename to The Chubao Authors.


Add README note for Emacs integration

Hello! I created an elisp wrapper for deps-new and clj-new. I really like this project so I included it built-in command. This PR just shares a link to the project - feel free to merge this if you think it's worth mentioning. Thanks for creating the framework!

thanks!


Touch/Face ID prompt does not show on the Simulator.

Hello, the prompt for Touch/Face ID only works on a real device. On the simulator, the secure value is just directly read or written to without a prompt.
Googling, I found another user of this framework with the same issue here. So, my question is, how do I get the Touch/Face ID prompt to show on the simulator?

This may be unrelated response however, in the documentation for AuthenticationPolicy when interacting with TouchID / FaceID following the example here:
let keychain = Keychain(service: "com.example.github-token")

DispatchQueue.global().async {
    do {
        // Should be the secret invalidated when passcode is removed? If not then use `.WhenUnlocked`
        try keychain
            .accessibility(.whenPasscodeSetThisDeviceOnly, authenticationPolicy: .userPresence)
            .set("01234567-89ab-cdef-0123-456789abcdef", key: "kishikawakatsumi")
    } catch let error {
        // Error handling if needed...
    }
}

If you follow the .userPresence AuthenticationPolicy it says above this variable...
    /**
     User presence policy using Touch ID or Passcode. Touch ID does not
     have to be available or enrolled. Item is still accessible by Touch ID
     even if fingers are added or removed.
     */

Yes it uses Touch ID or Passcode but then goes on to say does not have to be available or enrolled.
Based on this, I have to ask the following:

Which policy are you using to add or remove an item?

perhaps the policy you are setting doesn't have the constraint of must have enrolled finger/face.

If you look at this policy however,
    /**
     Constraint: Touch ID (any finger) or Face ID. Touch ID or Face ID must be available. With Touch ID
     at least one finger must be enrolled. With Face ID user has to be enrolled. Item is still accessible by Touch ID even
     if fingers are added or removed. Item is still accessible by Face ID if user is re-enrolled.
     */
    @available(iOS 11.3, OSX 10.13.4, watchOS 4.3, tvOS 11.3, *)
    public static let biometryAny = AuthenticationPolicy(rawValue: 1 << 1)

It requires at least 1 enrolled item and enforces this policy

After making a toy app that integrates with KeychainAccess,
I've been able to reproduce the issue where the simulator does not show any Touch / Face ID prompts even though the policy is set explicitly to biometryAny
Here's a snippet of code that sets and gets the item
    func setSecureItem(with value: String) {
        DispatchQueue.global().async {
            do {
                try self.keychain
                    .accessibility(.whenPasscodeSetThisDeviceOnly, authenticationPolicy: .biometryCurrentSet)
                    .authenticationPrompt("Authenticate to set secure item.")
                    .set(value, key: "test_key_2")
            } catch let error {
                print(error)
            }
        }
    }

    func retrieveSecureItem() {
        DispatchQueue.global().async {
            do {
                let value = try self.keychain
                .authenticationPrompt("Authenticate to access secure item")
                .get("test_key_2")
                DispatchQueue.main.async { [weak self] in
                    self?.retrievedSecureItem = value
                }
            } catch let error {
                print(error)
            }
        }
    }


Ue crypto.randomBytes instead of crypto.pseudoRandomBytes

https://github.com/resin-io/resin-register-device/blob/master/lib/crypto.coffee#L21, is there a specific reason why we're using pseudoRandomBytes?
Using crypto.randomBytes would make the uuid a stronger (in case we ever use it for key generation or something like that) and would reduce the probabilities of collisions.

@pcarranzav Since the code was extracted with no modification from the supervisor, I ignore if there was a reason for using pseudoRandomBytes. Happy to patch.
Notice that this functionality was moved to the SDK, and other components use the functionality from there instead.
I think we should have a discussion about how to remove the duplication of this logic among various modules.

As discussed privately, we will expose the generateUUID functionality and will reuse this module to provide the respective functionality in the SDK.


Match Install Errors

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
When trying to distribute my project I'm getting errors in Match related to installing the cert and provisioning profiles it looks like. I'm not sure what is going wrong and how to fix it. I haven't changed anything that I can remember recently. Any ideas?
Complete output when running fastlane, including the stack trace and command used

[20:59:50]: -------------------
[20:59:50]: --- Step: match ---
[20:59:50]: -------------------
[20:59:50]: Successfully loaded '/Users/distiller/project/Code/fastlane/Matchfile' 📄
+---------+-------------------------------------------------+
|        Detected Values from './fastlane/Matchfile'        |
+---------+-------------------------------------------------+
| git_url | https://github.com/fishcharlie/test.git |
| type    | development                                     |
+---------+-------------------------------------------------+
+-----------------------+-------------------------------------------------------------------------------------------------------------+
|                                                      Summary for match 2.93.1                                                       |
+-----------------------+-------------------------------------------------------------------------------------------------------------+
| type                  | appstore                                                                                |
| app_identifier        | ["com.charliefish.testA", "com.charliefish.testB", "com.charliefish.testC"] |
| force                 | true                                                                                |
| force_for_new_devices | true                                                                                |
| git_url               | https://github.com/fishcharlie/test.git                                                             |
| git_branch            | master                                                                                |
| username              |<EMAIL_ADDRESS>                                                                                |
| keychain_name         | fastlane_tmp_keychain                                                                                |
| readonly              | true                                                                                |
| team_id               | 45RBPB2153                                                                                |
| verbose               | false                                                                                |
| skip_confirmation     | false                                                                                |
| shallow_clone         | false                                                                                |
| clone_branch_directly | false                                                                                |
| skip_docs             | false                                                                                |
| platform              | ios                                                                                |
+-----------------------+-------------------------------------------------------------------------------------------------------------+
[20:59:50]: Cloning remote git repo...
[20:59:50]: If cloning the repo takes too long, you can use the clone_branch_directly option in match.
[20:59:51]: 🔓  Successfully decrypted certificates repo
[20:59:51]: Installing certificate...
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
[20:59:52]: There are no local code signing identities found.
You can run security find-identity -v -p codesigning to get this output.
This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774.
(Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)
+-------------------+------------------------------------------------+
|                       Installed Certificate                        |
+-------------------+------------------------------------------------+
| User ID           | 45RBPB2153                                     |
| Common Name       | iPhone Distribution: Charlie Fish (45RBPB2153) |
| Organisation Unit | 45RBPB2153                                     |
| Organisation      | Charlie Fish                                   |
| Country           | US                                             |
| Start Datetime    | 2017-08-26 05:34:25 UTC                        |
| End Datetime      | 2018-08-26 05:34:25 UTC                        |
+-------------------+------------------------------------------------+
[20:59:52]: No matching provisioning profiles found for 'AppStore_ com.charliefish.testA'
[20:59:52]: A new one cannot be created because you enabled readonly
[20:59:52]: Provisioning profiles in your repo for type appstore:
[20:59:52]: - 'AppStore_ com.charliefish.testC.mobileprovision'
[20:59:52]: - 'AppStore_ com.charliefish.testB.mobileprovision'
[20:59:52]: - 'AppStore_com.charliefish.testA.mobileprovision'
[20:59:52]: If you are certain that a profile should exist, double-check the recent changes to your match repository
+---------------------------+--------------------------------------------------------+
|                                    Lane Context                                    |
+---------------------------+--------------------------------------------------------+
| DEFAULT_PLATFORM          | ios                                                    |
| PLATFORM_NAME             | ios                                                    |
| LANE_NAME                 | ios release                                            |
| ORIGINAL_DEFAULT_KEYCHAIN | "/Users/distiller/Library/Keychains/login.keychain-db" |
+---------------------------+--------------------------------------------------------+
[20:59:52]: No matching provisioning profiles found and can not create a new one because you enabled readonly. Check the output above for more information.
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | update_fastlane            | 0           |
| 2    | Verifying fastlane version | 0           |
| 3    | default_platform           | 0           |
| 4    | setup_circle_ci            | 0           |
| 5    | cocoapods                  | 8           |
| 💥   | match                      | 1           |
+------+----------------------------+-------------+
[20:59:52]: fastlane finished with errors
[!] No matching provisioning profiles found and can not create a new one because you enabled readonly. Check the output above for more information.
[20:59:52]: WARNING: fastlane requires your locale to be set to UTF-8. To learn more go to https://docs.fastlane.tools/getting-started/ios/setup/#set-up-environment-variables
Exited with code 1

@fishcharlie Heyyy 👋

It looks like you need to tell your console to be UTF-8 - https://docs.fastlane.tools/getting-started/ios/setup/#set-up-environment-variables
It looks like there are no valid provisioning profiles in your iOS Developer account and you have read_only: true so it is not allowed to create any

Let me know if my suggestions do or don't work 😊

@joshdholtz I probably want to create provisioning profiles locally tho right? I want to keep read only set to true on my CI system right? How can I do that?

@fishcharlie I don't always have read_only: true on CI because I don't want to have to manually reset them. So you could set it to false or run fastlane on your local machine to create them 😊

Yeah it's not working at all. I ran fastlane cert then fastlane sigh locally. Then try to run it again on my CI and it's not working.
What's strange is the problem seemed to start happening when moving from CircleCI 1.0 to CircleCI 2.0.

I'm actually back to square one. That original log is what I'm getting now, after adding the setup CircleCI part.
I have tried wiping everything out and recreating everything using match and it still isn't working. It looks like part of the problem could be because it's trying to add .mobileprovision to the end.

I'm also having this issue with CircleCI 2.0 (security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.).
I added a security command after match and I do get the expected results:
      - run:
          name: Codesign info
          command: security find-identity -v -p codesigning

results:
 1) XXX "iPhone Developer: Fieldmargin Testing (XXX)"
  2) XXX "iPhone Distribution: FIELD MARGIN LTD (XXX)"
     2 valid identities found

But the next step deploy_crashlytics returns Shell command exited with exit status 48 instead of 0. when trying to run setup_circle_ci .
I've also tried removing setup_circle_ci which runs the crashlytics lane correctly until it fails at the end:
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | default_platform           | 0           |
| 3    | changelog_from_git_commits | 0           |
| 4    | git_branch                 | 0           |
| 5    | gym                        | 1243        |
+------+----------------------------+-------------+

[15:14:46]: fastlane finished with errors
Too long with no output (exceeded 10m0s)

I've been running in circles (no pun intended) for days with this trying to move from Circle CI 1.0 to 2.0.

@fishcharlie can you close the issue?
My case might be different, will post separately. In short:
I call two lanes: match and deploy_to_crashlytics.
If I add setup_circle_ci to before_all it crashes on the second lane.
If I call it only on the match lane, deploy_to_crashlytics cannot find the signing certificate.

Ok, solved my issue. In my case the problem was setup_circle_ci on before_all meant that I called it twice on the same session. Leaving it here in case anyone is having the same issue, be sure to call it just once.


Upgraded gradle wrapper and shadowJar to support openjdk 11.0 on Ubuntu 16.04

A new unrelated pull request accidentally got appended here because I pushed both to my dev branch.

will follow up on this when i have a chance to review in more detail - need to give this some thought.  In general, if tool is going to integrate preprocessors, would like to allow for selection of type to be used and provide a general mechanism (and enable no preprocessing by default as this is current behavior and significant number of users are preprocessing externally).  Also, would be desired to have preprocessing apply to all input types, not just rdl as most are generally applicable.

That's OK. You can cherry-pick the Ubuntu upgrade. the preprocessor commit got into the pull request by mistake as I've used a single dev branch and had no idea a pull request would automatically pull the branch head.
If you want I can send a new pull request with a dedicated branch just for the gradle changes.

yes, pls create a clean pr with just the gradle mods (and confirm changes to gradle.bat are just the license header - think diff is picking up line end deltas).


Check auxpow PoW before the auxpow itself.

Upstream fix from Namecoin Core that reverses the order in which the auxpow structure and the PoW on it are verified.  By checking the PoW first, we make it harder for random nodes to pass data of their choosing into CAuxPow::check.
Cherry-picked from: namecoin/namecoin-core@b6e3241b

Merging after aforementioned hour of leave-open, and after a few testing runs.  Let's get this out there.


portable_formula: use<EMAIL_ADDRESS>on Linux

This PR should allow us to build the portable formulae on Linux runners with newer glibc.  We won't need to rebuilt the bottles since they are currently build against glibc 2.13 in the Wheezy container - the goal here is to make sure they work.

I'm a little unsure how to add the<EMAIL_ADDRESS>dependency here as on_linux is not defined in this class.

It'll need to be in self.inherited of PortableFormula, like the keg_only line.

Okay that got us past the first hurdle but now it's failing with this:
<EMAIL_ADDRESS>gawk 3.0 (or later) is required to build glibc.

I guess it's trying to build<EMAIL_ADDRESS>from source?  Is there a way to use the bottle or do we have to rebuild it here for the test?

You'll need to special case perform<EMAIL_ADDRESS>without the --build-bottle here: https://github.com/Homebrew/homebrew-portable-ruby/blob/master/cmd/portable-package.rb#L37-L40

I realized we needed to test this with Ubuntu 16.04, so I changed the Dockerfile to use that instead.  Now I'm stuck with
fatal: not in a git directory

Presumably I'm missing a step in the Dockerfile, though I'm not exactly sure what to change.

I realized we needed to test this with Ubuntu 16.04, so I changed the Dockerfile to use that instead. Now I'm stuck with
fatal: not in a git directory

Presumably I'm missing a step in the Dockerfile, though I'm not exactly sure what to change.

I'll take a look tomorrow but maybe try pass --debug for more information.

I added --debug to the output but it's still not clear to me what the cause of the problem is.

That error is really weird. The .git directory exists but git says we're not in a git directory? I'll see if I can try reproduce locally.

I can't reproduce it locally by just using docker run -it homebrew/ubuntu16.04:master, so I'm assuming there's something about the Dockerfile that's causing this problem.

Maybe it has to do with the way we mount the core repo.
What does ${GITHUB_REPOSITORY,,} do? Is that a typo? https://github.com/Homebrew/homebrew-portable-ruby/blob/master/.github/workflows/build.yml#L45

Maybe it has to do with the way we mount the core repo.
What does ${GITHUB_REPOSITORY,,} do? Is that a typo? https://github.com/Homebrew/homebrew-portable-ruby/blob/master/.github/workflows/build.yml#L45

That does look very odd, but I pushed a commit to change it and it didn't seem to help.  I'm still not sure how to try to reproduce this locally.  I think I have to run the Dockerfile locally with docker but I'm still figuring that out.

What does ${GITHUB_REPOSITORY,,} do? Is that a typo?

No that's intentional - it converts it to lowercase.
Really we can ditch the Dockerfile. I can push that change, though it would be nice to know how we're managing to get past the several git repo checks in brew as that seems like a bug.

Our "Test Portable Ruby" step apparently has never worked properly on macOS since it's impossible to specify an external Ruby to be used. It also didn't work on Linux because HOMEBREW_RUBY_PATH is ignored, but I've fixed that to use PATH now.

Ok overhauled the Docker side of CI so everything should be working there now.
Current status here is OpenSSL fails to compile:
<EMAIL_ADDRESS>file not recognized: File format not recognized
collect2: error: ld returned 1 exit status

Looks like GNU ld scripts do not like the @ symbol.

Since binutils 2.35 we can now make the linker script look relatively (https://sourceware.org/bugzilla/show_bug.cgi?id=25806), which should solve the issue.
Tehcnically it can work before if there isn't a libpthread.so.0 or libpthread_noshared.a elsewhere in the search path. Not sure if we want to force using our binutils as<EMAIL_ADDRESS>dependency or not as a result.

I think the way to do this properly would be to try to avoid using the system headers wherever possible (excluding compiler stuff).
Which would mean something like:
-nostdinc -isystem$(gcc-5 --print-file-name=include) -isystem$(gcc-5 --print-file-name=include-fixed<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>as a minimum. Though this sounds like it should be in the superenv layer rather than here.

I tried in binutils to use -nostdinc and then add back the GCC headers before and the superenv filtered out the GCC header paths.  So there may be work needed there to make sure we can add those paths as needed.

I did some local testing and I can confirm that setting the CFLAGS and CPPFLAGS as @Bo98 described above are sufficient for the portable-ruby build to work, though I had to tweak a few things.  I also went back to binutils and found that using a subset of those flags fixed the build there without having to pass any CFLAGS to define macros as I had done before, confirming that the root cause of the original build failures in both cases is mixing of system headers with brewed headers.  Here are my main conclusions so far:

We need to add a conditional to https://github.com/Homebrew/brew/blob/master/Library/Homebrew/shims/super/cc#L258-L282 so when we pass -nostdinc, all include paths are kept so that we don't filter out the paths we have to add for the GCC headers which are in /usr/lib/gcc/x86_64-linux-gnu/5/include and /usr/lib/gcc/x86_64-linux-gnu/5/include-fixed.  Currently these are stripped out by the superenv and will cause the build to fail, so I had to hack the filtering to not remove any flags for the build to work.
When<EMAIL_ADDRESS>is a dependency for a formula on Linux, the superenv should automatically add -nostdinc -isystem$(#{cc} --print-file-name=include) -isystem$(#{cc} --print-file-name=include-fixed) as include flags.  We need to do this in the superenv rather than passing these arguments in as CFLAGS because otherwise the CFLAGS get copied into rbconfig.rb and this breaks building native gems with the system glibc, which we want to be able to do after installing portable-ruby.
We need to add<EMAIL_ADDRESS>as a build dependency of any formula that also has<EMAIL_ADDRESS>as a build dependency.  I've already implemented this for portable-formula.rb and will push a commit for this, and we'll also have to change this for binutils and zlib.
Specifically in portable-ruby, we have to add LIBS="-lpthread" on Linux because some of the conftest binaries secretly have a run time dependency on libpthread.  If we don't explicitly declare the dependency then the linker finds system libpthread instead of the one from<EMAIL_ADDRESS>and the conftest binary is broken at run time because libpthread expects to find newer symbols from the other libc libraries, whose maximum symbol versions are set to 2.13.  Confusingly this does not cause configure to fail but leads to a bizarre build failure much later due to an undefined macro (yes this was as much of a pain to figure out as it sounds).

I will work on a brew PR to address points 1 and 2 as they are fairly straight forward, and will push a commit to this PR to address points 3 and 4, though it will still fail until the issues in brew are fixed.

I have opened https://github.com/Homebrew/brew/pull/13568 which adds -nostdinc when<EMAIL_ADDRESS>is a dependency, address point 2 I made above.  I crossed out point 1 because it is irrelevant if we are .  I have also pushed an update to this that address points 3 and 4, though the build still fails because https://github.com/Homebrew/brew/pull/13568 has to be merged first.

Specifically in portable-ruby, we have to add LIBS="-lpthread" on Linux because some of the conftest binaries secretly have a run time dependency on libpthread. If we don't explicitly declare the dependency then the linker finds system libpthread instead of the one from<EMAIL_ADDRESS>and the conftest binary is broken at run time because libpthread expects to find newer symbols from the other libc libraries, whose maximum symbol versions are set to 2.13. Confusingly this does not cause configure to fail but leads to a bizarre build failure much later due to an undefined macro (yes this was as much of a pain to figure out as it sounds).

This is because -L does not apply to indirect dependences and<EMAIL_ADDRESS>libraries do not specify RPATHs. So we are just defaulting back to the global system search path.
It's why I suggested<EMAIL_ADDRESS>

It's picking up pthread as a dependency to librt. The issue you are seeing is because -L does not apply to indirect dependencies and<EMAIL_ADDRESS>libraries do not specify RPATHs. So we are just defaulting back to the global system search path.
It's why I suggested<EMAIL_ADDRESS>
In that case should we add the RPATH with the superenv like what we're doing for the include dirs?  Or is it preferable to add it just for portable-ruby?  I'm slightly unsure of the potential ramifications of adding this universally whenever we build with<EMAIL_ADDRESS>

What -rpath-link does is changes where to look for libraries at link time. Given we want to avoid system glibc even being in consideration, I think the flag makes sense to add.
-rpath-link is not be confused -rpath. Nothing in the output binary changes with -rpath-link - it only affects where to find libraries at link time.

It's picking up pthread as a dependency to librt. The issue you are seeing is because -L does not apply to indirect dependencies and<EMAIL_ADDRESS>libraries do not specify RPATHs. So we are just defaulting back to the global system search path.
It's why I suggested<EMAIL_ADDRESS>
In that case should we add the RPATH with the superenv like what we're doing for the include dirs? Or is it preferable to add it just for portable-ruby? I'm slightly unsure of the potential ramifications of adding this universally whenever we build with<EMAIL_ADDRESS>
Thanks for explaining that, I think it's safe to add this as a linker flag.  I will update https://github.com/Homebrew/brew/pull/13568 to automatically add this to the ldflags.

Now that's a new error:
In file included from closure.c:1:
./fiddle.h:42:10: fatal error: ffi.h: No such file or directory
   42 | #include <ffi.h>
      |          ^~~~~~~

Does that mean we need to have a portable libffi?  Or alternatively that we need to disable libffi if it's optional?

Ruby ships with libffi 3.2.1 which is used if there is none available on the system. Looks like something has broke which makes it never used (finding something on the system maybe?).
Will need full logs to see.

Oh looks like you're not using the container anymore. I'll push a fix for that (though I feel something's not right for it to behave the way it is anyway).

Sorry for messing up the container usage, there was a merge conflict and I didn’t fix it correctly.
I’ll locally test a fix for the nostdinc issue in brew and open a PR if it works.

The Linux build finally worked!  I'm not sure what's up the ARM build now - it's failing to upload the build artifact.

How do we restart CI here?  I don't see a button like I've used with homebrew-core and brew.
Also the 10.11 build failed in the "Test Portable Ruby" step but didn't really output anything about why.

How do we restart CI here? I don't see a button like I've used with homebrew-core and brew.

I've rerun them. Presumably you don't have sufficient permissions.

Looks like HOMEBREW_USE_RUBY_FROM_PATH doesn't actually work on macOS. I can probably just make the step Linux only for now.

I made the "Test Portable Ruby" step Linux-only and 10.11 now works, but now ARM isn't.  I messed up pulling the other commits added here and overwrote some by accident and that may be why ARM isn't working, though I thought I managed to restore everything.

Sorry for the delay - I took the week off.
I think the proper fix is still on the brew side. Skipping tests is not really acceptable in the long term, even if it has always been an issue. I'll take a look later today.

Should we rerun this with testing of Portable Ruby enabled on macOS when https://github.com/Homebrew/brew/pull/13644 is merged?

Should we rerun this with testing of Portable Ruby enabled on macOS when Homebrew/brew#13644 is merged?

Did this now @danielnachun 👍🏻

10.11 works now. 11-arm64 however refuses to use the Ruby on the path:
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby

Looks like HOMEBREW_USE_RUBY_FROM_PATH doesn't actually prioritise from the user PATH as I thought - it prioritises /usr/bin over anything, and it just happens to work on 10.11 because that version is so ancient it can't run the version check script.

@danielnachun Is this needed for 3.6.0/the glibc changes?

This is only needed to deprecate the Debian 7 Docker image. No plans to ship a new version of portable-ruby - existing bottles should be fine.
This is ready to go, just need to fix HOMEBREW_USE_RUBY_FROM_PATH over in brew first.

This is only needed to deprecate the Debian 7 Docker image. No plans to ship a new version of portable-ruby - existing bottles should be fine.

Ok. Sounds like this may also be worth doing as part of 3.6.0.

It would be great to get this in with 3.6.0.  I've tried to look into this and haven't figure anything out yet.

Hurrah, thanks for getting this over the line, both!


Use seaborn in jet visualisation code

It would be able to do the nice visual plots but tbh the histograms won't take too much effort to make hopefully once all the correct quantities are calculated, esp for image generation


External references for raw binary

Describe the bug
Functions from external programs in raw binary file dispayed in decompiler as func_0x00009190 or func_0x1
To Reproduce
Steps to reproduce the behavior:

Load raw binary file (module of firmware), which contains calls of external functions.

Load additional raw binary file (shared library for modules of firmware) and set it as external program.

Open module of firmware in CodeBrowser and find undefined call of function

Add external reference for CALL

Name of function in decompiler:

or

Create new block of memory (addresses of shared library).

Create reference in called function.

Name of function in decompiler:

Expected behavior
Name of function in decompiler should be displayed as in external function.
Environment (please complete the following information):

OS: Linux
Java Version: 11.0
Ghidra Version: 9.0

Additional context
How can I create external reference in idiomatic way for raw binaries? Adding external reference for all CALL (JMP and others) is a very time consuming process. Can I automate it without script?
How can I export functions (signatures too) from Exports of shared library to Import of module of firmware and synchronize them in future? I do it manually now: reverse engineering functions in shared library, then changing signatures in functions of Imports in module of firmware.

I developed a script for temporary use. It find all references to functions from all external programs (shared libraries) and set external references, set name and prototype (signature) of functions.
script.zip

Could you make the script into a PR?

Could you make the script into a PR?

I developed the script in the context of the project at work (NDA). When I finish the project, I will make a PR. While you can use prototype.

As I promised, I'm publishing the script for finding external references in raw binaries. It's far from ideal, but you can use it as example for developing more complex scripts/plugins.

As I promised, I'm publishing the script for finding external references in raw binaries. It's far from ideal, but you can use it as example for developing more complex scripts/plugins.

Thank you very much for this contribution :)


Enable dev deploy for the CPG instance

We'll need to deploy the ci service, but also remove any watched GitHub branches (we don't want to deploy whenever we push to main).

We probably don't need a GitHub OAuth token and Zulip configs in ci/deployment.yaml, but the SQL config seems to be necessary:
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.7/dist-packages/ci/__main__.py", line 8, in <module>
    run()
  File "/usr/local/lib/python3.7/dist-packages/ci/ci.py", line 439, in run
    ssl_context=internal_server_ssl_context(),
  File "/usr/local/lib/python3.7/dist-packages/aiohttp/web.py", line 433, in run_app
    reuse_port=reuse_port))
  File "uvloop/loop.pyx", line 1456, in uvloop.loop.Loop.run_until_complete
  File "/usr/local/lib/python3.7/dist-packages/aiohttp/web.py", line 305, in _run_app
    await runner.setup()
  File "/usr/local/lib/python3.7/dist-packages/aiohttp/web_runner.py", line 232, in setup
    self._server = await self._make_server()
  File "/usr/local/lib/python3.7/dist-packages/aiohttp/web_runner.py", line 331, in _make_server
    await self._app.startup()
  File "/usr/local/lib/python3.7/dist-packages/aiohttp/web_app.py", line 389, in startup
    await self.on_startup.send(self)
  File "/usr/local/lib/python3.7/dist-packages/aiohttp/signals.py", line 34, in send
    await receiver(*args, **kwargs)  # type: ignore
  File "/usr/local/lib/python3.7/dist-packages/ci/ci.py", line 406, in on_startup
    app['dbpool'] = await create_database_pool()
  File "/usr/local/lib/python3.7/dist-packages/gear/database.py", line 29, in wrapper
    return await f(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/gear/database.py", line 91, in create_database_pool
    sql_config = get_sql_config(config_file)
  File "/usr/local/lib/python3.7/dist-packages/gear/database.py", line 64, in get_sql_config
    with open(config_file, 'r') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/sql-config/sql-config.json'

The SQL database doesn't seem to be required, but running into some permission errors now:
    "error": "Traceback (most recent call last):\n  File \"/usr/local/lib/python3.7/dist-packages/batch/driver/job.py\", line 350, in schedule_job\n    body = await job_config(app, record, attempt_id)\n  File \"/usr/local/lib/python3.7/dist-packages/batch/driver/job.py\", line 270, in job_config\n    name, namespace, KUBERNETES_TIMEOUT_IN_SECONDS)\n  File \"/usr/local/lib/python3.7/dist-packages/batch/driver/k8s_cache.py\", line 74, in read_service_account\n    _request_timeout=timeout)\n  File \"/usr/local/lib/python3.7/dist-packages/hailtop/utils/utils.py\", line 390, in retry_transient_errors\n    return await f(*args, **kwargs)\n  File \"/usr/local/lib/python3.7/dist-packages/kubernetes_asyncio/client/api_client.py\", line 166, in __call_api\n    _request_timeout=_request_timeout)\n  File \"/usr/local/lib/python3.7/dist-packages/kubernetes_asyncio/client/rest.py\", line 191, in GET\n    query_params=query_params))\n  File \"/usr/local/lib/python3.7/dist-packages/kubernetes_asyncio/client/rest.py\", line 181, in request\n    raise ApiException(http_resp=r)\nkubernetes_asyncio.client.rest.ApiException: (403)\nReason: Forbidden\nHTTP response headers: <CIMultiDictProxy('Audit-Id': '773434b6-3961-4092-8587-cd1e10654424', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'Date': 'Thu, 04 Feb 2021 23:23:48 GMT', 'Content-Length': '350')>\nHTTP response body: {\"kind\":\"Status\",\"apiVersion\":\"v1\",\"metadata\":{},\"status\":\"Failure\",\"message\":\"serviceaccounts \\\"admin\\\" is forbidden: User \\\"system:serviceaccount:default:batch\\\" cannot get resource \\\"serviceaccounts\\\" in API group \\\"\\\" in the namespace \\\"leonhardgruenschloss\\\"\",\"reason\":\"Forbidden\",\"details\":{\"name\":\"admin\",\"kind\":\"serviceaccounts\"},\"code\":403}\n\n\n",


Simplify the Getting Started documentation.

Reduce the level of entry to start gathering metrics with prometheus
by suggesting to just download pre-built exporters instead of requiring
the reader to download an entire Golang build chain and checkout a project.
Include examples for both *nix and Windows.

Fix #6956

I think the latest commit should be the last needed :crossed_fingers:

Thanks!


Placeholders

I added AFKPlusPAPI.jar from this link (https://github.com/Dart2112/AFKPlusPAPI/tags)
in papi expansions folder and they don't work.
What I did wrong?

Put it in the plugins folder


Renault API broken?

I think something changed on Renault server, breaking all 3rd party apps...

Kamereon API key changed?

No, the Kamereon API key isn't included in the JSON-files. It's hardcoded in the app if I remember correct.

Fixed in https://github.com/db-EV/ZoePHP/releases/tag/20220316

New Kamereon API key is:
VAX7XYKGfa92yMvXculCkEFyfZbuM7Ss

Thanks for the quick fix

Is there no API Key for switzerland?


Offset argument contained a NaN value - PieChart

Hey Guys,
found a little issue creating a PieChart. When creating PieChartSectionData and the value = 0 for all PieChartSectionDatas, I get the following error message. However If I set any of the three PieChartSectionData value to >= 1; than it works. This is the error message:
The following assertion was thrown during paint():
Offset argument contained a NaN value.
'dart:ui/painting.dart':
Failed assertion: line 43: ''
The relevant error-causing widget was:
When the exception was thrown, this was the stack:
#2      _offsetIsValid (dart:ui/painting.dart:43:10)
#3      Canvas.drawLine (dart:ui/painting.dart:3702:12)
#4      CanvasWrapper.drawLine (package:fl_chart/src/utils/canvas_wrapper.dart:54:62)
#5      PieChartPainter._removeSectionsSpace. (package:fl_chart/src/chart/pie_chart/pie_chart_painter.dart:165:21)
#6      ListMapView.forEach (dart:_internal/list.dart:242:8)
...
The following RenderObject was being processed when the exception was fired: RenderCustomPaint#71dd4
...  parentData:  (can use size)
...  constraints: BoxConstraints(w=130.0, h=130.0)
...  size: Size(130.0, 130.0)
RenderObject: RenderCustomPaint#71dd4
parentData:  (can use size)
constraints: BoxConstraints(w=130.0, h=130.0)
size: Size(130.0, 130.0)
...  child: _RenderLayoutBuilder#5d300 NEEDS-PAINT
...    parentData:  (can use size)
...    constraints: BoxConstraints(w=130.0, h=130.0)
...    size: Size(130.0, 130.0)
...    child: RenderConstrainedBox#30f98 NEEDS-PAINT
...      parentData: offset=Offset(0.0, 0.0) (can use size)
...      constraints: BoxConstraints(w=130.0, h=130.0)
...      size: Size(130.0, 130.0)
...      additionalConstraints: BoxConstraints(unconstrained)
This is the code:
Container(
                height: 150,
                width: 200,
                decoration: BoxDecoration(
                  color: Theme.of(context).cardColor,
                  borderRadius: BorderRadius.circular(
                    screenSizeFactor(
                      context,
                      10,
                    ),
                  ),
                ),
                child: Stack(
                  alignment: Alignment.center,
                  children: [
                    Padding(
                      padding: EdgeInsets.all(10),
                      child: AspectRatio(
                        aspectRatio: 1,
                        child: PieChart(
                          PieChartData(
                            borderData: FlBorderData(show: false),
                            sections: [
                              PieChartSectionData(
                                badgePositionPercentageOffset: 0,
                                showTitle: false,
                                color: Colors.blue,
                                radius: 5,
                                value: 0,
                              ),
                              PieChartSectionData(
                                showTitle: false,
                                color: Colors.red,
                                radius: 5,
                                value: 0,
                              ),
                              PieChartSectionData(
                                showTitle: false,
                                color: Theme.of(context).indicatorColor,
                                radius: 5,
                                value: 0,
                              ),
                            ],
                          ),
                        ),
                      ),
                    ),

Reproducible code should contain the main function.

I am having that error aswell.

Hi, at the moment, we have changed our draw approach. Now we use RenderObjects for drawing, sizing, and touches. (previously, we used CustomPainter).
RenderObjects is more stable and error-prone. Please check this issue with our new release 0.30.0. Let me know whether it has been fixed or not.

While I dont get a NaN error anymore there is still an issue :
[ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: 'package:flutter/src/rendering/box.dart': Failed assertion: line 2784 pos 18: 'transformed == position - childParentData.offset': is not true.
The error is thrown when tapping on the pie chart while all values are 0.

It should be fixed in our new version.
Please check 0.35.0, and verify it is working properly.


Committees: Update to FY19/20 members

There have been changes to two committees:
CONSTRUCTION COMMITTEE
Jaquelyn Dupont-Walker was added as a member.
EXECUTIVE MANAGEMENT COMMITTEE

Eric Garcetti is Vice Chair (was 1st Vice Chair)
Hilda Solis is a Board Member (was 2nd Vice Chair)

I've made these changes in the Legistar, could you make sure they're updated on the site?

Hi @shrayshray,
Both of those have been updated on their respective committee pages.


linux: Set CONFIG_NO_HZ_FULL=y.

CONFIG_NO_HZ_FULL=y should be set to enable the nohz_full= and rcu_nocbs= options. These carry no additional performance penalty compared to CONFIG_NO_HZ_IDLE and behaves like it by default, but allows disabling the tick interrupts on cores for power or performance reasons.
Debian also applied the change to all their kernels. Like the Kernel says: "If you're a distro say Y."
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Config help for reference:
config NO_HZ_FULL
	bool "Full dynticks system (tickless)"
	# NO_HZ_COMMON dependency
	# We need at least one periodic CPU for timekeeping
	depends on SMP
	depends on HAVE_CONTEXT_TRACKING_USER
	# VIRT_CPU_ACCOUNTING_GEN dependency
	depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
	select NO_HZ_COMMON
	select RCU_NOCB_CPU
	select VIRT_CPU_ACCOUNTING_GEN
	select IRQ_WORK
	select CPU_ISOLATION
	help
	 Adaptively try to shutdown the tick whenever possible, even when
	 the CPU is running tasks. Typically this requires running a single
	 task on the CPU. Chances for running tickless are maximized when
	 the task mostly runs in userspace and has few kernel activity.

	 You need to fill up the nohz_full boot parameter with the
	 desired range of dynticks CPUs to use it. This is implemented at
	 the expense of some overhead in user <-> kernel transitions:
	 syscalls, exceptions and interrupts.

	 By default, without passing the nohz_full parameter, this behaves just
	 like NO_HZ_IDLE.

I forgot to mention this issue comment on the Debian tracker.
From my understanding, there is no expected performance overhead compared to CONFIG_NO_HZ_IDLE=y, which is already set.

Hey @lovesegfault, nice of you to cherry pick this into your PR, but it seems you dropped it when you dropped the pahole revert. Any chance you could get this merged?

Thanks!

This broke i686 linux and is blocking nixos-unstable channel (from getting the openssl update BTW).

@vcunat Wow, this is... unexpected. This setting should not break anything. Is CONFIG_NO_HZ_IDLE=y set on the i686-linux kernels? Do you have anything I can look at to try to figure out why or what happened?


Set agent-id for steps

Save which agent is running a task. This is now visible in the admin UI in the queue and in the agent details screen.
changes

[x] save id of agent executing a task
[x] add endpoint to get tasks of an agent for #999
[x] show assigned agent-id in queue
[ ] show tasks of an agent in agent details
[x] (offtopic) use same colors for queue stats and icons (similar to the ones used by pipelines)
[x] (offtopic) use badges for queue labels & dependencies

Codecov Report
Patch coverage: 30.00% and project coverage change: +0.03 :tada:

Comparison is base (2337f18) 39.30% compared to head (e805d3c) 39.34%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1631      +/-   ##
==========================================
+ Coverage   39.30%   39.34%   +0.03%
==========================================
  Files         167      167
  Lines       10832    10828       -4
==========================================
+ Hits         4258     4260       +2
+ Misses       6300     6294       -6
  Partials      274      274

Impacted Files
Coverage Δ

server/grpc/rpc.go
0.00% <0.00%> (ø)

server/model/step.go
43.63% <ø> (ø)

server/model/task.go
0.00% <ø> (ø)

server/queue/persistent.go
0.00% <0.00%> (ø)

server/queue/queue.go
0.00% <ø> (ø)

server/queue/fifo.go
83.33% <100.00%> (+0.13%)
:arrow_up:

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

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

@lafriks Good point.


IGNITE-8571 IGNITE-8575 Ignite autoadjust alpha

The ticket is resolved, closing PR.
Please close PRs for your resolved tickets and other non-needed PRs.
Alternatively, ask a committer

to use GitHub UI (committer can associate accounts here: https://gitbox.apache.org/setup/ )
or /scripts/apply_pull_request.sh from Apache Ignite source.
or mention in commit message 'Fixes #(a number of PR)'.

These methods will automatically close PR.
Feel free to reopen this PR if it is actual.


This may be an issue with the path of the dataset

Hi, I run python train_stereo.py --logdir ./checkpoints/sceneflow, but there is something wrong:

This may be an issue with the path of the dataset, I set up the dataset directory the way you did, but the problem remains.

You need to set the dataset path (https://github.com/gangweiX/IGEV/blob/main/IGEV-Stereo/core/stereo_datasets.py) to your own. The '/data/sceneflow/' needs to be set to your own.

Thanks! I successfully solved this problem.


Tooltip is behind Popover

Describe the bug
I'm using a Tooltip inside a Popover component and the Tooltip is behind the Popover.
Not sure if this is intended - imo, tooltips should have the highest z-index.
To Reproduce
<Popover.State placement="bottom-start" gutter={16}>
  <Popover.Disclosure use={Button}>Click me</Popover.Disclosure>
  <Popover showCloseButton title="Hello">
    <Text.Block color="gray700" fontSize="100">
      Some information
      <Tooltip content="Will appear behind Popup" use="span">
        <Icon marginLeft="minor-1" icon="solid-info-circle" />
      </Tooltip>
    </Text.Block>
  </Popover>
</Popover.State>;

Quick fix
I was able to fix this by overwriting the Tooltip's z-index in theme.ts
const theme = {
  Tooltip: {
    Content: {
      styles: {
        base: {
          // needs to be a string or it won't work
          zIndex: `99999999`,
        },
      },
    },
  },
};

Ah yes – this is definitely a bug. Will have a look into it.

This should be fixed on 1.3.9


[Enhancement][Cherry-Pick] Upgrade Spark to 3.4.0 due to CVE-2023-22946

Fixes #22226

this PR need #13942 before merge


Fix textbox flickering

What does the pull request do?
Fixes #10006
Notes
Partially reverts #9962 but Dispose has been kept on TextLine: TextLineImpl has an empty implementation for now.

You can test this PR using the following package version. 11.0.999-cibuild0028772-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

Removing this line: https://github.com/AvaloniaUI/Avalonia/blob/master/src/Avalonia.Controls/Presenters/TextPresenter.cs#L591 solved the issue for me. This must be related to the new renderer somehow.

#10015 seems to fix the flickering as well and preserves the ability to dispose text related objects

#10015 seems to fix the flickering as well and preserves the ability to dispose text related objects

Perfect! Closing in favor of #10015