Update/fix README kustomize command

Before this patch always version v0.8.0 would be deployed when using the
kustomize command from the README. This patch adjust the kustomization
to not overwrite the version.
The build process is unaffected from this, since during the build script
the kustomize file is adjusted to adjust the version to the current
release. This means the build manifests for release will still have a
pinned version like before.
Reference:
https://github.com/rancher/system-upgrade-controller/blob/4eacc2dabbde943ee59dc7819ea0a04909b05b0f/scripts/package-controller#L36

One problem with the command and the new permissions is, that the controller will lack its crds and the permissions to deploy them itself. This is a result of my decision to not grant the controller full permissions to adjust CRDs.
It might be a good idea to revise this or figure out a better way to get the CRDs easily into the cluster.

I guess I could finally cave to long-standing requests to include the CRD manifest in the repo. I've been trying to keep the CRDs code-first, but since we're suggesting people deploy with kustomize, and the RBAC no longer allows the controller to install them itself, we might as well add it.

I think we should add the permissions to create CRDs. The checked in CRDs will age the same way the kustomiztation image replacements will age: poorly.

There we go, also added the missing permissions :)


remove the permutations calculations out of get_grad

fix #29

@baumeier @gtirimbo  do you know why the electron_phonon test is failing?

oh, I think when I changed the behavior of calculating the vib frequencies (throwing out anything <10cm^-1), this has changed the results, obviously. Forgot to take care of the test

@baumeier  shall we merge this one?

@felipeZ Yes, for the failing test, we need to update the reference data.


Support scheduled message processing (scheduled retry)

Having the ability to only process a message at a certain time, say for scheduling sending messages to users.
This could be quite easily achieved by extending the existing retry delay system - give the user function the ability to throw a "retry message X time" exception, the system will then use -this- as the retry delay, instead of the normal retry delay of a few seconds.
The record will then not be given back to a user function, until at least X time has passed.

Closing Issue


fix(qt): remove stretchers from Overview page when it's not needed

Issue being fixed or feature implemented
Overview page has strange stretching on sides, which make balance moving left-right when window is scalled.

What was done?
Removed stretches for Overview Page from the sides, it makes window a little more balanced. This PR lets to do backport of bitcoin-core/gui#176 which improves behavior further more be increasing size of "transaction list" part of window.
How Has This Been Tested?
See screenshot. Resized window with/without patch, in "Discreet mode" off and on. Both looks not perfect but better than before.
Breaking Changes
N/A
Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone

@knst knst force-pushed the fix-qt-overview branch from dd8b1ed to b9a2ce7

due to feature_proxy.py failed without IPv6. rebased on the top of develop


Some questions about the LCDMoire dataset.

I have recently been conducting research on image moiré demoiré removal. While collecting data, we found that the LCDMoire dataset download link in AIM2019 Challenge is invalid, and there are no other alternative download links available on the Internet, so we hope that you can share a new download link with us.

Hi,
Unfortunately, I don't have this dataset on hand currently, either. The
dataset was stored on the company's server which I already do not have
access.
Song Yan @.***> 于2024年9月6日周五 01:52写道：

I have recently been conducting research on image moiré demoiré removal.
While collecting data, we found that the LCDMoire dataset download link in
AIM2019 Challenge is invalid, and there are no other alternative download
links available on the Internet, so we hope that you can share a new
download link with us.
—
Reply to this email directly, view it on GitHub
https://github.com/CVMI-Lab/UHDM/issues/32, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPNNM3NLJTZ7K3S3OBKPHTZVFUOVAVCNFSM6AAAAABNYEMSW2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYDSOBYGQ4DAOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you very much for the reply. I wonder if there is any other way to get the dataset?


Allow line plugin calling scripts.

Need to export the runtime to plugins.

steam云存档api相关文档

WASMI blocking issue: https://github.com/paritytech/wasmi/issues/572


"Paper Lara" Bug - Lara Distorts Thinly when Rolling

When rolling, Lara gets really thin for some reason. I am 80% sure this behavior isn't vanilla.

I often saw this bug back in my childhood while playing tr2 and tr4 on ps1. This was happening in the moment when Lara inverts her horizontal rotation (back/forward jump with roll and rolling on land)

It really is an issue with CalcLaraMatrices, most likely a sign error somewhere but the actual bug has not been fixed yet, it's quite tricky to debug but I'm sure I'll think of something.

#240


The URL of an image in PaneGrid docs is broken

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
The URL of an image in PaneGrid docs is broken.

What is the expected behavior?
There should be an image.
Version
crates.io release
Operating System
Windows
Do you have any log output?
No response

This is fixed in master: https://docs.iced.rs/iced/widget/pane_grid/struct.PaneGrid.html


Improve Background Color Consistency

As reported in https://www.cyberbotics.com/forum?message=8739, due to the HDR rendering system the actual color vs the background color selected show some discrepancies.
This PR attempts to apply the inverse of the HDR formula to get as close a matching as possible between the selected and rendered colors (now the correspondance is exact).

test me

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/129/consoleText

test me

test me

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/130/consoleText

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/131/consoleText

test me

test me

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/133/consoleText

test me

test me

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/134/consoleText

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/136/consoleText

test me

Build Passed :ok_hand:
You can safely merge 'enhancement-accurate-background-colors' into 'master'.

👍


Extract Transaction_applied from Transaction_logic

Module is standalone and 200+ lines long.
Note for reviewer: it's the easiest to just copy-paste the same code piece to a separate file, format it and to compare to the new file of this branch.
Explain how you tested your changes:

[x] Code compiles

Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? None

!ci-build-me


UHF-8390 D10 depracation updates

Added access check to entity queries
Guzzle::jsonDecode to utils::jsonDecode
ProphesizeTrait for prophesize method

Codecov Report

Merging #114 (9ff5111) into main (337c800) will increase coverage by 13.39%.
The diff coverage is 80.00%.

:exclamation: Current head 9ff5111 differs from pull request most recent head 0722073. Consider uploading reports for the commit 0722073 to get more accurate results

@@              Coverage Diff              @@
##               main     #114       +/-   ##
=============================================
+ Coverage     49.23%   62.62%   +13.39%
+ Complexity      445      439        -6
=============================================
  Files            65       64        -1
  Lines          1570     1560       -10
=============================================
+ Hits            773      977      +204
+ Misses          797      583      -214

Impacted Files
Coverage Δ

src/Entity/Form/MenuLinkFormTrait.php
0.00% <0.00%> (ø)

src/Plugin/migrate/source/HttpSourcePluginBase.php
29.57% <0.00%> (+15.49%)
:arrow_up:

src/Environment/EnvironmentResolver.php
98.63% <100.00%> (+0.05%)
:arrow_up:

src/EventSubscriber/MigrationSubscriber.php
87.50% <100.00%> (+4.52%)
:arrow_up:

... and 17 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


AMD64 Arch Linux Asan Debug runs incomplete git clean before building

AMD64 Arch Linux Asan Debug runs git clean -f -f -d iso. git clean -fdx.

Seems like AMD64 Arch Linux Asan Debug is much happier now: https://buildbot.python.org/all/#/builders/586/builds/181

Thanks for the check and for #275!


KAFKA-16310 ListOffsets doesn't report the offset with maxTimestamp a…

add default implementation to Batch to return offset of max timestamp
copy ListOffsetsIntegrationTest from trunk branch

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@chia7712: Since the follower only maintains offsetForMaxTimestamp at the batch level, the listMaxTimestamp API was never implemented correctly. So, technically, there was no regression for listMaxTimestamp. It seems there is no need to fix this in the 3.6? We could just fix it in trunk.

Since the follower only maintains offsetForMaxTimestamp at the batch level, the listMaxTimestamp API was never implemented correctly.

I am not sure I understand this. All we need for this solution (or workaround) is the "max timestamp" of a segment, since we always iterate the batches (from the segment having the max timestamp) to find the "offset" of max timestamp when handling the ListOffsetsRequest.MAX_TIMESTAMP. Hence, we can correct the implement for all active branches (include 3.6.3) by this PR.

So, technically, there was no regression for listMaxTimestamp. It seems there is no need to fix this in the 3.6? We could just fix it in trunk.

BTW, I'm ok to keep the behavior for 3.6 as it is not a kind of "regression".

I am not sure I understand this. All we need for this solution (or workaround) is the "max timestamp" of a segment, since we always iterate the batches (from the segment having the max timestamp) to find the "offset" of max timestamp when handling the ListOffsetsRequest.MAX_TIMESTAMP. Hence, we can correct the implement for all active branches (include 3.6.3) by this PR.

Yes, I agree that we can fix this issue completely. I am just saying that we only need to fix this in trunk since the implementation was never correct in any previous branches, thus not a regression.

I am just saying that we only need to fix this in trunk since the implementation was never correct in any previous branches, thus not a regression.

got it. will open another PR for trunk


Shell script and gradle-profiler scenarios for memory restricted benchmarking

I've updated the PR accordingly, however this will not be merged for a while since Ivan (owner of the repo) is out of office. Feel free to use the fork directly: https://github.com/akerimsenol/android-extra-large-benchmark/tree/2022.9.bash


Confused in Distributed Training in Tensorflow

Hi,I have tried several methods to build my distributed training system , but the training speed is fallacious. As I want, several machines with one master and muti ps(3 ps),the training speed depends on the slowest one of the ps. But what I got it is almost 200s every 100steps in En-De training, I'm very confused about this. What's more ,the t2t defines the master and ps , but in conventional tensorflow distributed training tutorial, there should be worker and ps. The ps plays the role of updating variables like master in T2T , and the worker computes the gradients parallel like ps in T2T. This really makes me amazing! I have ask questions in gitter ,but no one answer me . I hope you can give me some advice !

I just want to seek the real comprehension among the tensorflow and tensor2tensor.

Nagging Assignee @yuefengz: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @yuefengz: It has been 46 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

I think the question fits more on StackOverflow. To use multi-worker training with distribution strategies, you can take a look at our (documentations)[https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/distribute/README.md] and (examples)[https://github.com/tensorflow/ecosystem/tree/master/distribution_strategy].


Add check option to model

Currently, errors in the model file are not raised immediately, but only when properties are accessed. A way to check the model is to use the lint function but it is independent and possibly not up to date.
The proposal here is to add a check option to the Model constructor so that it tries to access all properties immediately and raise a syntax error if needed.

@sbenthall: this is related to https://github.com/EconForge/dolo/issues/180


Proposal vote note following correct type values

I tried voting no to a proposal but it voted as abstain. The vote message broadcasted is not following the vote option type values.

The correct values can be found from the following type file.
https://github.com/cosmos/cosmos-sdk/blob/a334a59df02fe1f227fbf2a9a1ae153323eb6f8b/proto/cosmos/gov/v1beta1/gov.proto#L17


Update HCI NodeSet with a pre/post Ceph Deployment example

Use servicesOverride feature of OpenStackDataPlaneDeployment to make HCI deployment examples more clear. Instead of having the human operator edit the services list before creating a second deployment, provide two deployment examples which each have the correct services list for before and after Ceph has been installed.
Jira: OSP-29040

/retest-required

/test dataplane-operator-build-deploy-kuttl

The job was previously killed during make ceph due to:
Error from server (InternalError): Internal error occurred: admission plugin "[security.openshift.io/SCCExecRestrictions](http://security.openshift.io/SCCExecRestrictions)" failed to complete validation in 13s

re-kicking to see if it's consistent.

The job was previously killed during make ceph due to:
Error from server (InternalError): Internal error occurred: admission plugin "[security.openshift.io/SCCExecRestrictions](http://security.openshift.io/SCCExecRestrictions)" failed to complete validation in 13s

re-kicking to see if it's consistent.


seq2ffv1 - completely rewrites script to use sipcreator, attempt at #198

Attempts to fix #198, but using seq2ffv1 instead of makeffv1 as a proof of concept. Functionally, this produces similar packages to the original seq2ffv1, except it uses sipcreator.py instead.
This also removes the CSV report for benchmarking.
A general losslessness report should be added somewhere, maybe mimicing masscopy. Filenames have trailing characters too, but overall, this should be an improvement.

i'll take a look at this soon, thanks, R

noice,
cd ifigit/ifiscripts && git checkout newseq2ffv1

and maybe an aul git pull right after just in case.

So there's some major changes to scripts here:
copyit now has a -move option, which uses shutil.move() to cut and paste files instead of copy/pasting. This makes seq2ffv1 much better as it:

Prevents 2 ffv1/mkv files from bein created - one in the output folder, another copy in the /objects folder'
much quicker as there really is no need to actually copy the files

This has the added benefit of being of great use to concat.py which suffers from duplicate files and redundant copy processes.

So - now all that's missing is a losslessness report that appears at the end of the script's processing.

Remaining todo:

move  log consolidation from concat.py into ififuncs.py so that seq2ffv1.py can share the function
more work needed on logging
uuids should be used for output filenames, along with identifier assignment eventType

Merging as there was some useful functionality in copyit.py and ififuncs that is needed in the master branch.


HDDS-8837. [Recon] Heatmap UI improvements

What changes were proposed in this pull request?
Ozone Recon has a Heatmap component which displays the heatmap of the access of the various buckets/volumes/keys.
This PR makes the following changes:

Change heatmap colour scheme to a more neutral and Ozone compliant theme
Fonts are changed to Roboto
Spacing and component layout is changed to better utilize the available space

What is the link to the Apache JIRA
HDDS-8837: [Recon] Heatmap UI improvements
How was this patch tested?
This patch was tested manually.

Screenshots
Description

Heatmap with custom select last 90 days time and Bucket type filter

Heatmap with Key type filter

Heatmap with custom select last 90 days time and Volume type filter

Heatmap Custom Select 90 days date picker

Can You remove Lock file as we are not updating any new package in package.json it will fail in Build.

Can You load updated screenshots

Updated video recording with the latest changes:
https://github.com/apache/ozone/assets/43001336/0ac3876a-26bb-44df-80af-1932e7f9e073


An option to set custom button outside the slider component to navigate

currently the way to customize the arrow is
function SampleNextArrow(props) {
   return ( arrow properties)
}
function SamplePrevArrow(props) {
	return ( arrow properties)
}
export default class CustomArrows extends Component {
	render() {
		const settings = {
			nextArrow: <SampleNextArrow />
			prevArrow: <SamplePrevArrow />
		};
	return (
		<Slider {...settings}>
		content
		</Slider>
	 );
	}
}

it would have been better to use buttons outside the  slider component to navigate through the slides. For example
export default class CustomArrows extends Component {
	render() {
		const settings = {
			nextArrow: navigatenext()
			prevArrow: navigateprevious()
		};
	return (
		<button onClick={navigatenext}>Next</button>
		<button onClick={navigateprevious}>Previous</button>
		<Slider {...settings}>
		content
		</Slider>
	 );
	}
}

You can achieve this by adding a ref to the slider and accessing available methods that will allow you to control the slider.
<Slider> </Slider>

Yes It works fine. Seems like the same was implemented in https://react-slick.neostack.com/docs/example/previous-next-methods example. Thank you for taking the time out to respond to this. I believe this issue can be closed now

it actually didn't work for me, the problem with this is whenever i refresh the slider disappears, here's my code, could youn tell me what i'm doing wrong :
`import React, { useState, useEffect, useRef, useCallback } from 'react'
import axios from "axios"
import { SERVICES } from '../../sevices/globalServices'
import { Link } from "react-router-dom"
import Slider from 'react-slick'
import ServicesSliderCard from './ServicesSliderCard'
import i1 from "../../assets/img/Services/i1.png"
import i2 from "../../assets/img/Services/i2.png"
import i3 from "../../assets/img/Services/i3.png"
import i4 from "../../assets/img/Services/i4.png"
import left from '../../assets/img/Services/left.png'
import right from '../../assets/img/Services/right.png'
class ServicesComponent extends React.Component {
constructor(props) {
super(props)
this.next = this.next.bind(this);
this.previous = this.previous.bind(this);
}
 next() {
      this.slider.slickNext();
 }
 previous() {
      this.slider.slickPrev();
 }

 state = {
      services: []
 }

 fetchData = async () => {
      const r = await axios.get(SERVICES())
      this.setState({ services: r.data.data })
 }

 componentDidMount() {
      this.fetchData()
      console.log(this.slider)

 }

 s = [i1, i2, i3, i4]

 render() {
      const settings = {
           centerMode: true,
           dots: false,
           autoplay: true,
           infinite: true,
           autoplaySpeed: 2000,
           slidesToShow: 2,
           slidesToScroll: 1,
           arrows: true,
           centerPadding: "12.6%",
      };

      return (

Our Best Tours

We can  take you to more then 400 destination

                          <Link to='/' >View All Tours</Link>

                     <Slider ref={slider => this.slider = slider} {...settings}>
                          {
                               this.s.length === 0 ?
Loading...
 : this.s.map(p => <ServicesSliderCard key={p} data={p} />)
                          }
                     </Slider>

      )

 }

}
export default ServicesComponent
`


Feature/resolver property name fallback

PR for issue #74

Hey @Hendy, I'm going to merge this in now... I'm aiming to get the 0.7.0 release out tomorrow, so gonna do some tidy up this evening.


Addressing Security Concerns Raised by OpenSSF Scorecard

Hey, I just made a Pull Request!
Added:

Pinned Dependency to SHA level
Permissions defined for GitHub Actions following PoLP

Note: This PR is modified version of #19249
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

cc/ @adamdmharvey @Rugvip

Nice one!
As you can probably see, numerous E2E failures for the pipeline.  I'm not familiar with the exact steps that the harden runner performs, but perhaps it's removing something the tests depend on?  I wonder if you want to try maybe removing the harden step (like commenting it out) for the E2E action maybe causes it to run clean? if so then you can at least identify the root cause of the failure to focus more on what it does. (and then potentially split the PR into one that just does the version pin/permissions and another for harden?  not sure!)

Cheers for the inputs @adamdmharvey - was stuck in travelling hell past few days!
I'll rebase with master and let's see how it looks.
Post that will comment out harden runners changes.

Wow! @adamdmharvey As soon as I tried commenting out the Harden runners, the docker registries are seemingly facing downtime!? 😭
Logs:

https://github.com/backstage/backstage/actions/runs/6344165810/job/17233682142?pr=20090
https://github.com/backstage/backstage/actions/runs/6344165814/job/17233682786?pr=20090

I'll recheck in a while!

Triggered a re-run of the failed actions; definitely passed the Docker step...

Triggered a re-run of the failed actions; definitely passed the Docker step...

Cheers, 5xx must have been resolved - I'll re-trigger all pipelines and take it from there.

@adamdmharvey Both E2E Testing failing due to this application level issue. This is outside scope of this PR as I've only updated the workflow files.
Any nudges on how to proceed?

took the liberty of rebasing to see if builds are happier

took the liberty of rebasing to see if builds are happier

Thanks @freben  - only 2 failures remain but I can't make sense of these logs. Can you nudge what shall I change to proceed?

We still have some remaining windows build issues, don't worry about those.
Why is the harden runner commented out everywhere?

We still have some remaining windows build issues, don't worry about those.
Why is the harden runner commented out everywhere?

Was just checking if the failed pipelines are caused by Harden Runner - not really so I will be uncommenting them now.
Will commit and leave it to you guys for best next steps :)

Looks like something has gone awry here with the rebase, could you rebase again to just have your commits in here @NishkarshRaj? :pray:

Looks like something has gone awry here with the rebase, could you rebase again to just have your commits in here @NishkarshRaj? 🙏

Oh snap! I am on it :)

@freben @benjdlambert : Fixed the stupid rebase mistake, hope this works now.

we've put a "merge after release" label on this so we can revisit merging it after the mainline release out of an abundance of caution against getting into release problems.


Correct a comment in the 'Objects vs Enums' sample

In the Objects vs Enums section there is a comment about needing an extra line to pull out keys from an object defined w/ as const. As far as I can tell, that line is actually for pulling out the values. This PR updates the comment.

ts playground example

You're right - thanks!


No mention of ProductID:LanguagePack to deploy language Packs

We where able in the past to use ProductID="LanguagePack" to deploy new languages. This was a conveniant way to add the languages to all C2R products without the need to specify the product exclusion used when we deployed OfficeProPlusRetail.
Do we remove this option, meaning we cannot use any more ProductID="LanguagePack" ?
Or do you just forget to mention it in the article "Overview of deploying languages in Office 365 ProPlus"?

Thanks for the feedback--I'll look into this and let you know.

This feature was included in the Overview of the Office Deployment Tool, but you're right that it wasn't included in the language overview (which is the first place someone would look). I just added it--thanks for the catch. https://docs.microsoft.com/en-us/deployoffice/overview-of-deploying-languages-in-office-365-proplus?branch=master#add-languages-to-existing-installations-of-office-365-proplus

Thank you. Impressive fast answer 😉
De : J Whitmarsh<EMAIL_ADDRESS>Envoyé : mardi 16 octobre 2018 00:14
À : MicrosoftDocs/OfficeDocs-DeployOffice<EMAIL_ADDRESS>Cc : TheBaban<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [MicrosoftDocs/OfficeDocs-DeployOffice] No mention of ProductID:LanguagePack to deploy language Packs (#129)
This feature was included in the Overview of the Office Deployment Tool, but you're right that it wasn't included in the language overview (which is the first place someone would look). I just added it--thanks for the catch. https://docs.microsoft.com/en-us/deployoffice/overview-of-deploying-languages-in-office-365-proplus?branch=master#add-languages-to-existing-installations-of-office-365-proplushttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-deploying-languages-in-office-365-proplus%3Fbranch%3Dmaster%23add-languages-to-existing-installations-of-office-365-proplus&data=02|01||d06b5c90b4bb46d64aa508d632eb7de0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636752384340472386&sdata=zJULZrnKBSV2Y6hxCaoDAIlCEonyvJBvf9498a7H2QI%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-DeployOffice%2Fissues%2F129%23issuecomment-430032915&data=02|01||d06b5c90b4bb46d64aa508d632eb7de0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636752384340472386&sdata=BwDPZ6cVuUXH4H6Cav5qQBghrR4SSMCAdDo6F0m0AIk%3D&reserved=0, or mute the threadhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcOf5c6ypl3tlMRG7kokmSovKBKJ19-iks5ulQifgaJpZM4XcL1q&data=02|01||d06b5c90b4bb46d64aa508d632eb7de0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636752384340472386&sdata=%2Bnm7Ru8GEF5rqy4TAmYyLmMQs08Sdy38vQGIRhbnJKM%3D&reserved=0.


Added rule for no duplicated props

Added rule that checks for duplicate props sent to a React component written in JSX.
Has the options of specifying whether casing should be ignored when comparing, via {ignoreCase: true}
Closes #143

Great! Thanks!


Added http route to client attributes

Added http route to client attributes

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7d71758) 79.79% compared to head (b5a8eac) 79.83%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #597      +/-   ##
==========================================
+ Coverage   79.79%   79.83%   +0.04%
==========================================
  Files          70       70
  Lines        5933     5936       +3
==========================================
+ Hits         4734     4739       +5
+ Misses        976      974       -2
  Partials      223      223

Flag
Coverage Δ

integration-test
69.48% <100.00%> (+0.06%)
:arrow_up:

unittests
44.76% <0.00%> (-0.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


SPIRV-Cross duplicates the continue construct, even when it has a barrier

This is prompted by the investigation into #1511
SPIRV-Cross will duplicate the continue construct.  But this can be invalid if the continue construct has a barrier in it.
Here's an example compute shader in GLSL.  The third clause of the for loop has a function call out to helper, which then has a barrier in it. (It's silly, but it's a reduced case for illustration).
#version 450

layout(set=0, binding=0) buffer ABuf { uint a; } A;

shared uint sa;

uint helper(uint x) {
   uint result = 99 + x;
   if (sa < 1000) {
    result = 999;
    sa = 1000;
   }
   barrier();
   return result;
}

void main() {
  uint i;
  sa = 0;
  for (i = 1 ; i < sa; i += helper(i)) {
    if ((i&1) == 1) {
      sa += 1;
      continue;
    }
    sa += 2;
  }
  A.a = sa;
}

When you compile this shader with Glslang, then inline the helper function, then you get this SPIR-V.  This particular example was generated with 'glslc -O' which is like gv -V, followed by spirv-opt -O (which inlines and does load/store and other scalar optimizations).
               OpCapability Shader
          %1 = OpExtInstImport "GLSL.std.450"
               OpMemoryModel Logical GLSL450
               OpEntryPoint GLCompute %4 "main"
               OpExecutionMode %4 LocalSize 1 1 1
               OpMemberDecorate %_struct_56 0 Offset 0
               OpDecorate %_struct_56 BufferBlock
               OpDecorate %58 DescriptorSet 0
               OpDecorate %58 Binding 0
       %void = OpTypeVoid
          %3 = OpTypeFunction %void
       %uint = OpTypeInt 32 0
    %uint_99 = OpConstant %uint 99
%_ptr_Workgroup_uint = OpTypePointer Workgroup %uint
         %17 = OpVariable %_ptr_Workgroup_uint Workgroup
  %uint_1000 = OpConstant %uint 1000
       %bool = OpTypeBool
   %uint_999 = OpConstant %uint 999
     %uint_2 = OpConstant %uint 2
   %uint_264 = OpConstant %uint 264
     %uint_0 = OpConstant %uint 0
     %uint_1 = OpConstant %uint 1
 %_struct_56 = OpTypeStruct %uint
%_ptr_Uniform__struct_56 = OpTypePointer Uniform %_struct_56
         %58 = OpVariable %_ptr_Uniform__struct_56 Uniform
        %int = OpTypeInt 32 1
      %int_0 = OpConstant %int 0
%_ptr_Uniform_uint = OpTypePointer Uniform %uint
          %4 = OpFunction %void None %3
          %5 = OpLabel
               OpStore %17 %uint_0
               OpBranch %33
         %33 = OpLabel
         %74 = OpPhi %uint %uint_1 %5 %55 %72
         %39 = OpLoad %uint %17
         %40 = OpULessThan %bool %74 %39
               OpLoopMerge %35 %36 None
               OpBranchConditional %40 %34 %35
         %34 = OpLabel
         %42 = OpBitwiseAnd %uint %74 %uint_1
         %43 = OpIEqual %bool %42 %uint_1
               OpSelectionMerge %45 None
               OpBranchConditional %43 %44 %45
         %44 = OpLabel
         %46 = OpLoad %uint %17
         %47 = OpIAdd %uint %46 %uint_1
               OpStore %17 %47
               OpBranch %36
         %45 = OpLabel
         %49 = OpLoad %uint %17
         %50 = OpIAdd %uint %49 %uint_2
               OpStore %17 %50
               OpBranch %36
         %36 = OpLabel
         %68 = OpIAdd %uint %uint_99 %74
         %69 = OpLoad %uint %17
         %70 = OpULessThan %bool %69 %uint_1000
               OpSelectionMerge %72 None
               OpBranchConditional %70 %71 %72
         %71 = OpLabel
               OpStore %17 %uint_1000
               OpBranch %72
         %72 = OpLabel
         %80 = OpSelect %uint %70 %uint_999 %68
               OpControlBarrier %uint_2 %uint_2 %uint_264           ;; only one barrier call.
         %55 = OpIAdd %uint %74 %80
               OpBranch %33
         %35 = OpLabel
         %61 = OpLoad %uint %17
         %63 = OpAccessChain %_ptr_Uniform_uint %58 %int_0
               OpStore %63 %61
               OpReturn
               OpFunctionEnd

This is the output from spirv-cross -V --es
#version 450 es
layout(local_size_x = 1, local_size_y = 1, local_size_z = 1) in;

layout(set = 0, binding = 0, std430) buffer _56_58
{
    uint _m0;
} _58;

shared uint _17;

void main()
{
    _17 = 0u;
    uint _68;
    bool _70;
    uint _74 = 1u;
    for (;;)
    {
        if (_74 < _17)
        {
            if ((_74 & 1u) == 1u)
            {
                _17++;
                _68 = 99u + _74;
                uint _69 = _17;
                _70 = _69 < 1000u;
                if (_70)
                {
                    _17 = 1000u;
                }
                barrier();
                uint _55 = _74 + (_70 ? 999u : _68);
                _74 = _55;
                continue;
            }
            _17 += 2u;
            _68 = 99u + _74;
            uint _69 = _17;
            _70 = _69 < 1000u;
            if (_70)
            {
                _17 = 1000u;
            }
            barrier();
            uint _55 = _74 + (_70 ? 999u : _68);
            _74 = _55;
            continue;
        }
        else
        {
            break;
        }
    }
    _58._m0 = _17;
}

This has duplicated the continue construct, including the call to the barrier.
A valid way to translate this is to:

generate the continue construct only once, at the top of the loop, but guarded by a 'not-first-iteration' flag.  This allows the control flow graph in the continue construct to be quite complex.
the challenge is that sometimes an SSA value generated in the first part of the loop iteration might be used in the continue construct.  To handle this, you have to hoist the value up, perhaps outside the loop, either as a variable or via an OpPhi.

This is how Tint translates it to MSL (I faked the barrier because Tint doesn't currently support barrier.):
#include <metal_stdlib>

struct S {
  uint field0;
};

kernel void main_tint_0(device S& x_57 [[buffer(0)]]) {
  uint x_73_phi = 0u;
  x_17 = 0u;
  x_73_phi = 1u;
  {
    bool tint_msl_is_first_1 = true;
    uint x_54;
    const uint x_73;
    const uint x_37;
    const uint x_48;
    for(;;) {
      if (!tint_msl_is_first_1) {
        const uint x_67 = (99u + x_73);
        const uint x_68 = x_17;
        const bool x_69 = (x_68 < 1000u);
        if (x_69) {
          x_17 = 1000u;
        }
        ///// barrier goes here, if Tint supported it already.
        x_54 = (x_73 +         select(999u, x_67, x_69));
        x_73_phi = x_54;
      }
      tint_msl_is_first_1 = false;

      x_54 = 0u;
      x_73 = x_73_phi;
      x_37 = x_17;
      if ((x_73 < x_37)) {
      } else {
        break;
      }
      if (((x_73 & 1u) == 1u)) {
        const uint x_44 = x_17;
        x_17 = (x_44 + 1u);
        continue;
      }
      x_48 = x_17;
      x_17 = (x_48 + 2u);
    }
  }
  const uint x_60 = x_17;
  x_57.field0 = x_60;
  return;
}

I believe this SPIR-V is still wrong. There is no merge when entering continue, so the implementation is free to assume that execution has not been merged. Also, moving the continue to the top is not a valid solution since we cannot store OpAccessChain to a temporary. The workaround that would work for that case would be to wrap the entire loop body in a do {} while(0) construct and then emit continue block once perhaps ...

There is no OpSelectionMerge to %36 here. I see no spec wording that this means execution has become dynamically uniform again. The wording is for merge targets, but continue is not a merge target I think.

If control flow is uniform upon entry into a structured loop or selection, and all invocations leave that loop or selection via the header block’s declared merge block, then control flow reconverges to be uniform at that merge block.

I believe this SPIR-V is still wrong. There is no merge when entering continue, so the implementation is free to assume that execution has not been merged, and thus executing a barrier will be undefined unless all threads entered continue the same way.

In this code example, all choices are uniform: all the invocations in the workgroup take the same branches and compute the same values. So execution is uniform.  So I think the barrier is valid to use where it is.
(Yes, all the invocations race on updating the 'sa' variable and the output result to the storage buffer. But I didn't want to make this any more complicated.)

Also, moving the continue to the top is not a valid solution since we cannot store OpAccessChain to a temporary.

You mean in the general case, since the only access chain in the example is in the last block in the function.  Yes, you can't store a pointer or put it through a Phi.  In that case you would have to sink the phi into the continue target, but hoist its indices.  If there are chained access chains, then you have to hoist them all, until you get to a variable declaration or to a root point that is early enough to dominate the hoisted continue target.

I don't see the problem if the control flow is uniform. All code paths will hit the same barrier if control flow is uniform.

In that case you would have to sink the phi into the continue target, but hoist its indices. If there are chained access chains, then you have to hoist them all, until you get to a variable declaration or to a root point that is early enough to dominate the hoisted continue target.

The complexity to implement that would be mind-boggling and I'd rather not go there.

The workaround that would work for that case would be to wrap the entire loop body in a do {} while(0) construct, translate continue to a break and then emit continue block once perhaps

We have to do something like that in spirv-opt's merge-return pass.  It ends up chaining the state of "I've broken out".
You'd have to track if the a 'break' in the new code was really an original 'continue' or actually  a 'break' in the original.

Yes, SPIRV-Cross needs to do this for switch blocks, since you can break out of a loop while inside a switch block in SPIR-V.

I don't see the problem if the control flow is uniform. All code paths will hit the same barrier if control flow is uniform.

Ha. Well that might wrap it up nicely.  :-)   I'll have to think if my example was too simple.

This interacts with subgroup operations as well FWIW (which invocations are active in a continue construct coming from divergent control flow?), so adding a workaround to force convergence might very well be a bug.

Yeah, if barrier is resolved in that tidy way, then I agree subgroup operations are the next thing to consider.  I haven't thought through the subgroup operation case.
The rules are less well specified with respect to what lanes are guaranteed to be active. So it's debatable one way or another whether some transformations are really wrong at all.
I don't have urgency for this issue, and like you say it's not a functionality bug for barriers at least.

Either way, this needs to be clarified in the SPIR-V spec somehow I think, otherwise I will assume my interpretation is correct.

Actually, if a workaround wraps the body in do { } while(0) then you can just continue out of that construct, no need for break shenanigans, and then emit the continue block, so a workaround won't be all that horrible, but ... ye ...


Break aggregate_status logic into own module

[ ] Move constants and aggregate status retriever to own service.
[x] Move lone test in dividend model also.

Done


can i init close the panel x_panel for default?

can i init close the panel x_panel for default?
I mean. Keep closed when load or reload or refresh the page
How can i do it?
I have the HTML template

Hii @residente007 you can add the below script to initially close the x_panel.

Hii @puikinsh please close this issue.


⚠ Bofrost.be has degraded performance

In f44bfcc, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 957 ms

Resolved: Bofrost.be performance has improved in a75ff88 after 6 minutes.


Create FAQs

Added in FAQ Section for additional assistance.

Thanks for opening these pull request. I do not think that these changes add any value at this time.


UPDATE ROT space URL

Hello, we decided to make the URL "rotten" instead of "rotten-swap". Apologies for the inconvenience. Thanks!

@wallbanger1 Looks like you made a clone of your space, you should rather edit the existing space.

@wallbanger1 Looks like you made a clone of your space, you should rather edit the existing space.

I changed the folder name and the class name in an effort to change the URL from https://snapshot.page/#/rotten-swap to https://snapshot.page/#/rotten

A subsequent change was dropping the proposal min to 10k.


Add Playwright e2e tests 🎭

Added 7 Playwright  e2e test cases that are executed in "podcast web CI/CD workflow", across chromium, firefox, and webkit. Base URL of the site under test is set via env variable BASEURL. For GHA, this value is constructed using WEBAPP_NAME variable.
GHA is configured to generate a test job summary and upload artifacts for HTML reports with video and trace files that can be downloaded to assist with post-mortem debugging.
Example failed test GHA run here: https://github.com/MarcusFelling/dotnet-podcasts/actions/runs/3055457978/attempts/1#summary-8358350472

@jamesmontemagno  - looks like creds are bad for az login.

Yeah that is fine @MarcusFelling  don't worry about it


Invalid address error when using injected provider

Over at MetaMask, we had an issue submitted by @drcode regarding MetaMask/browser-solidity compatibility, and I could use your help to track down.
The error thrown is Uncaught Error: invalid address(…), thrown from browser-solidity when the payload has an undefined from field.
For some reason it seems that browser-solidity is no longer successfully building its transaction parameters using the currently injected selected address at web3.eth.accounts[0] or web3.eth.coinbase.
In the Method.prototype.buildCall function, you can see this line:
var payload = method.toPayload(Array.prototype.slice.call(arguments));

The input arguments are very minimal, and the resulting payload value lacks a defined sender:
{from: undefined, to: undefined, data: "0x606060405234610000575b33600060006101000a8154817000816000905550600101610594565b5090565b50505b5056", value: "0x0", gas: 449552}

This makes it look like the method.toPayload() method is failing to pull out the current address from the injected web3.
Unfortunately, when I did a search of this repository, I saw no toPayload reference anywhere, so now I'm confused.
This seems to be a browser-solidity bug to me right now, but without the original source code to search & reference, it will be hard for me to track down.  Any clues?

@flyswatter  I think var payload = method.toPayload(Array.prototype.slice.call(arguments)); is in web3 and thats why you're not seeing it in this repo
an aside:
web3 has previously not allowed you to submit a tx without a specified sender. I don't know if they still enforce this but in my opinion they shouldn't, it can be autofilled by the user-agent (mist/metamask).

I agree it would seem reasonable & kinda cool to not require a specified sender.  Less code for dapp developers.  Let the provider throw an error if it can't fill a sender in.

Since that looks like it's web3, I'll continue exploring the stack fro where browser-solidity should be grabbing the from value...

The stack is simply too deep. I cannot find where browser-solidity is assembling the params. I could really use the help of a browser-solidity dev tracking this down.

I think it was broken by #335.

This error also happens without metamask, just using geth and the "Web3 Provider" mode of solidity.

This error also happens in Mist.

If axic is right, and #335 broke this, to check out a working version, you should git pull and checkout the version b4a512ddba1c71073afb12d44cf5c8b833baa0e2.

So, the production browser-solidity has been broken for a week now.
Who is the maintainer whose attention we need to get here?

I confirm that using version b4a512ddba1c71073afb12d44cf5c8b833baa0e2 works with MetaMask v2.13.11. Here is what I did:
git clone git@github.com:ethereum/browser-solidity.git
cd browser-solidity
git checkout b4a512ddba1c71073afb12d44cf5c8b833baa0e2
npm install
npm run build
npm run serve    # starts webserver on port 8080

Then I pointed Chrome to http://localhost:8080 to bring up my local browser-solidity, clicked the cube icon, and selected "Injected Web3" to use MetaMask.

@yann300 @chriseth ^ the PR  #335 broke this

This PR should fix it
https://github.com/ethereum/browser-solidity/pull/341
but it is not yet merged. @axic could we push that?

So do I understand correctly that this issue is fixed now?
I still have the same issue when I use the Solidity Browser web UI...

The issue is fixed on my side with this basic contract
contract intLocal {     address public _l;     function intLocal () {     _l = msg.sender;     }  }
Could you post the code of the contract here please, i will try to reproduce.

@megachucky perhaps try clearing the browser cache

I cleared the Chrome cache, deleted all cookies and tried @yann300 's contract example with the most recent compiler (0.4.7-nightly.2016.12.13+commit.9d607345.Emscripten.clang).
Still the same issue.
Does it  work for you with the "online version" at https://ethereum.github.io/browser-solidity, or are you using another Solidity Browser?

yes... you are using metamask right? on ropsten?

I am not even getting to that step with Metamask because I still get the exception of "address not supported for state ..." in the formal verification of Solidity Browser. You do not get this error anymore? Which compiler version do you use?
I might check this on another computer later today to doublecheck that it is not any kind of cache / cookie error in my Chrome browser...

The error "address not supported for state ..." is unrelated to this issue. Not all valid code is supported by the formal verification module.

It sounds to me like this bug has been fixed, thank you!!!

Finally, I could also try it out again. I also can confirm that it works again. I can successfully create contracts with Solidity Browser. Due to the "verfification error", Metamask complains that the contract has an exception, but it still executes the transaction successfully.

Can you help clarify what verification error is showing an incorrect warning on MetaMask?  Is there a better way we could handle it?

@megachucky it is not a "verification error". The Solidity compiler can output multiple artefacts, one of them is a Why3 Formal Verification source code. This is visible in the "formal verification" tab. That however doesn't support every feature of the language.
The warning provided by it can be ignored unless you need formal verification.
I am not sure how this is related to Metamask.

Ahh, well MetaMask uses the error-first syntax to identify errors, and uses that first argument's message in the UI. Sounds like the error argument of the callback is used for metadata, @axic?

Which callback are we talking about? This is the compilation process, that shouldn't have anything to do with Metamask.

I'm actually not 100% sure, but I believe they're talking about this publication error.

Just compile this code in browser-solidity and switch to the tab with the "tick" as an icon, that'll show why3 compilation errors (but that doesn't stop the rest from functioning):
contract A {
  address public a;
}

Ok, I've reproduced & logged the state, I'll be able to easily debug this tomorrow.

@flyswatter Yes, you are right (sorry for not being more clear). I meant exactly this error in MetaMask you linked to.
To summarize:
In Solidity Browser, the verification tab always shows an error regarding address not supported, like:
"Untitled:3:5: Error: Type "address" not supported for state variable. address public owner;"
Anyway, everything works as expected, I can compile and create the contract and run transactions.
When MetaMask pops up to confirm the transaction, I get this notifcation:
"Transaction Error. Exception thrown in contract code." - However, again, everything works fine.

This bug happens because we have this line in our tx response parser.
It says:
    // all gas used - must be an error
    if (estimatedGasHex === txData.txParams.gas) {
      txData.simulationFails = true
    }

It seems the assumption "all gas used is an error" is incorrect when using the compiler, for which browser-solidity seems to perfectly predict the correct gas usage for.
We could either entirely remove this block, and leave OOG error detection to the TxManager, or try to improve the conditions of the assumption.  I'm leaning towards the former for simplicity & nice abstraction.

@flyswatter yeah I agree, this should be handled externally, we dont have enough information here

Hi All, i am facing this issue.. so this is not yet resolved.
I am using browser solidity and meta mask, previously everything working properly. please let me know if someone has solution of it.

that stuff is another issue.
this is more related to https://github.com/ethereum/go-ethereum/issues/3653

@sagargohil i cant tell from your screenshot what the issue is


Build fails | 71fe525 - Merge pull request #973 from synthetichealth/thread-pool-sizing

I updated my master repo to the latest commit at master - 71fe525 - Merge pull request #973 from synthetichealth/thread-pool-sizing
The build fails with the following error.

Hi @eedrummer, build fails after updating master to the latest commit - 0f63ca4 - Merge pull request #970 from synthetichealth/java17
Please see the error below where 3 tests are failing.

Task :compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

Task :test

org.mitre.synthea.engine.FixedRecordTest > fixedDemographicsImportTest FAILED
java.lang.AssertionError: expected:<4> but was:<5>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.mitre.synthea.engine.FixedRecordTest.fixedDemographicsImportTest(FixedRecordTest.java:58)
org.mitre.synthea.export.CCDAExporterTest > testCCDAExport FAILED
java.lang.AssertionError: Validation of exported CCDA failed: Illegal operation (self.realmCode->isEmpty())|index=54, size=54|index=42, size=42 expected:<0> but was:<3>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.mitre.synthea.export.CCDAExporterTest.testCCDAExport(CCDAExporterTest.java:60)
org.mitre.synthea.world.geography.DemographicsTest > languageFromRaceAndEthnicity FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.mitre.synthea.world.geography.DemographicsTest.languageFromRaceAndEthnicity(DemographicsTest.java:78)
503 tests completed, 3 failed, 4 skipped

Task :test FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':test'.

There were failing tests. See the report at: file:///D:/Dev/GitHub/Synthea/synthea/build/reports/tests/test/index.html

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 6m 25s
15 actionable tasks: 15 executed

The org.mitre.synthea.world.geography.DemographicsTest > languageFromRaceAndEthnicity failure is transient. That test isn't great, to be honest, because

it is probabilistic, and the random number generator isn't seeded.
it defaults to Philadelphia, and we have been migrating tests to use default cities specified in src/test/resources/test.properties in the case of people using international demographics files:

test_state.default = Massachusetts
test_state.alternative = California

test_town.default = Bedford
test_town.alternative = South Gate

I can update the test to seed the Random and use the test properties demographics.
My goal with the test was to make sure we hit as much of the code as possible, as that method has a ton of different branches. That said, it can still be achieved by just seeding the random.

@eedrummer , @jawalonoski  - thank you for your notes.
Today the build is failing for only "testCCDAExport" test
100 warnings

Task :compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

Task :test

org.mitre.synthea.export.CCDAExporterTest > testCCDAExport FAILED
java.lang.AssertionError: Validation of exported CCDA failed: Illegal operation (self.realmCode->isEmpty()) expected:<0> but was:<1>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.mitre.synthea.export.CCDAExporterTest.testCCDAExport(CCDAExporterTest.java:60)
503 tests completed, 1 failed, 4 skipped

Task :test FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':test'.

@IoTFier yes. I have seen that fail intermittently too. I'll take a look.

@eedrummer , @jawalonoski -
I don't know what the new changes in the code are, but one good thing that I want to share is that -
On my new PC - [AMD 5950x and DDR4 3600 - 128gb RAM - Nvidia 3080 config] - it takes barely 57 seconds to generate 1000 records for a given city in a State. I am generating CCDA, FHIR, Notes, Text notes and Encounters.
The build is taking less than 2 mins.
So, thank you for this help.
Results -
Records: total=1172, alive=1000, dead=172
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 57s
4 actionable tasks: 2 executed, 2 up-to-date

@eedrummer - build is failing with today's update to master
org.mitre.synthea.export.CCDAExporterTest > testCCDAExport FAILED
java.lang.AssertionError: Validation of exported CCDA failed: Illegal operation (self.realmCode->isEmpty())|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS)) expected:<0> but was:<10>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.mitre.synthea.export.CCDAExporterTest.testCCDAExport(CCDAExporterTest.java:60)
503 tests completed, 1 failed, 4 skipped

Task :test FAILED

FAILURE: Build failed with an exception.

Hello @eedrummer,
Since last few commits to master branch - I am seeing a consistent behavior where the first build after pull fails and the subsequent builds successfully.
For example, please see the build output after pulling today's commit - ( f1b56e2 - Merge pull request #1001 from synthetichealth/cvd-codes-fix)
Will you please help me understand the reason for this pattern?
Thank you,

Task :compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

Task :test

org.mitre.synthea.engine.FixedRecordTest > fixedDemographicsImportTest FAILED
java.lang.AssertionError: expected:<4> but was:<5>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.mitre.synthea.engine.FixedRecordTest.fixedDemographicsImportTest(FixedRecordTest.java:58)
org.mitre.synthea.export.CCDAExporterTest > testCCDAExport FAILED
java.lang.AssertionError: Validation of exported CCDA failed: Illegal operation (self.realmCode->isEmpty())|Illegal operation (self.realmCode->isEmpty())|Illegal operation (self.realmCode->isEmpty())|Illegal operation (self.realmCode->isEmpty())|Illegal operation (self.realmCode->isEmpty())|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS))|Cannot find operation (excluding(OclVoid)) for the type (Set(TS)) expected:<0> but was:<10>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.mitre.synthea.export.CCDAExporterTest.testCCDAExport(CCDAExporterTest.java:62)
org.mitre.synthea.export.CCDAExporterTest > testExportWithNoPreferredWellnessProvider FAILED
java.lang.AssertionError: expected:<0> but was:<1>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.mitre.synthea.export.CCDAExporterTest.testExportWithNoPreferredWellnessProvider(CCDAExporterTest.java:92)
507 tests completed, 3 failed, 5 skipped

Task :test FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':test'.

There were failing tests. See the report at: {file path}/Synthea/synthea/build/reports/tests/test/index.html

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 4m 52s
15 actionable tasks: 15 executed
{path}synthea  master    羽4m 53.134s    .\gradlew.bat build check test                                            pwsh  10:01:
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 4m 14s


build: push to new staging registry

/assign @hakman
Do we need to do this as part of getting our releases going, or is it just a matter of doing a new release?

(Also related: https://github.com/kubernetes/test-infra/pull/33399)

/lgtm
/approve


Expose DelimitedTermFrequencyTokenFilter

Description
This commit exposes Lucene's delimited term frequency token filter to be able to provide term frequencies along with terms.
Related Issues
Resolves #9413
Check List

[x] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@russcam  Thanks for the PR! There is a known compatibility issue. Meanwhile, could you fix gradle check please?
* What went wrong:
Execution failed for task ':modules:analysis-common:test'.
> There were failing tests. See the report at: file:///var/jenkins/workspace/gradle-check/search/modules/analysis-common/build/reports/tests/test/index.html

@russcam could you please add changelog entry under [Unreleased 2.x] section? thank you

@noCharger @reta addressed gradle check and added to changelog under 2.x

@msfroh @noCharger could you check this one please? looks pretty good to me

Overall the changes look good to me.
I'd still like to make the codecov/patch check happy with a unit test. I think if DelimitedTermFrequencyTokenFilterFactory gets some coverage, we should be good.
@russcam, are you able to add that unit test? If not, I think I can throw something together.

Failing test looks to be unrelated?

Task :server:internalClusterTest

Tests with failures:

org.opensearch.remotestore.RemoteIndexRecoveryIT.testRerouteRecovery

3015 tests completed, 1 failed, 36 skipped

Failing test looks to be unrelated?

Task :server:internalClusterTest

Tests with failures:

org.opensearch.remotestore.RemoteIndexRecoveryIT.testRerouteRecovery

3015 tests completed, 1 failed, 36 skipped

https://github.com/opensearch-project/OpenSearch/issues/9580

Failing tests loook to be unrelated to this change:
Tests with failures:
 - org.opensearch.index.shard.RemoteIndexShardTests.testNRTReplicaWithRemoteStorePromotedAsPrimaryCommitRefresh

12039 tests completed, 4 failed, 25 skipped

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/23938/
CommitID: a80e9a0
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

It's the same flaky test as in https://github.com/opensearch-project/OpenSearch/issues/9580. Other PRs appear to be skipping this test case and merging exactly where the auto cut occurred: https://github.com/opensearch-project/OpenSearch/issues/9631


python311Packages.mkdocstrings-python: 0.9.0 -> 0.10.0

Changelog: https://github.com/mkdocstrings/python/blob/0.10.0/CHANGELOG.md
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/)
23.05 Release Notes (or backporting 22.11 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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 230507 run on x86_64-linux 1

1 package marked as broken and skipped:

netbox_3_3

5 packages built:

netbox
python310Packages.mkdocstrings-python
python310Packages.mkdocstrings-python.dist
python311Packages.mkdocstrings-python
python311Packages.mkdocstrings-python.dist


Enable mask_rom and rom_ext boot in FPGA

This issue tracks the implementation and documentation of  local FPGA builds with mask_rom.

Consider enabling splice script with mask_rom to speed up local development.

Investigation on how to load ROM in to FPGA bitstream without requiring full synthesis: lowrisc/opentitan#5751

Running the following command, after following regular setup instructions:
readonly ROM_INIT=${REPO_TOP}/build-bin/sw/device/silicon_creator/mask_rom/mask_rom_fpga_nexysvideo.32.vmem
readonly OTP_INIT=${REPO_TOP}/build-bin/sw/device/otp_img/otp_img_fpga_nexysvideo.vmem

echo "configuring the build system"
. /tools/xilinx/Vivado/2020.1/settings64.sh
cd ${REPO_TOP}
./meson_init.sh -f
./hw/top_earlgrey/util/top_earlgrey_reduce.py

echo "building the software"
ninja -C build-out all

echo "building the FPGA image"
fusesoc --cores-root . run --flag=fileset_top --target=synth \
    lowrisc:systems:top_earlgrey_nexysvideo \
    --BootRomInitFile=${ROM_INIT} --OtpCtrlMemInitFile=${OTP_INIT}

Results in the following error:
INFO: [Designcheck 2-1] Checking if ROM memory is mapped to BRAM memory.
WARNING: [Vivado 12-180] No cells matched 'get_cells -hierarchical -filter { NAME =~  "*rom_rom*rdata_o_reg_0" && PRIMITIVE_TYPE =~ BMEM.*.* }'.
ERROR: [Designcheck 2-3] BRAM implementation not found for ROM memory.

Taking a look in Vivado next to check what primitive is being used for the ROM.

OK, it seems the issue is that the MaskROM is less that one BRAM block size, and thus /home/moidx/opentitan/hw/top_earlgrey/util/vivado_hook_opt_design_post.tcl fails to find *room_rom*rdata_o_reg_*. The design only has top_earlgrey/u_rom_rom/u_prim_rom/gen_generic.u_impl_generic/rdata_o_reg available in this case.
We should add mask_rom padding to the expected ROM size, and report utilization as part of the build flow.
We could argue that /home/moidx/opentitan/hw/top_earlgrey/util/vivado_hook_opt_design_post.tcl should also be updated.

As of lowrisc/opentitan#9722, FPGA splicing is enabled in CI. We also have bootstrap support in the production ROM to enable loading of ROM_EXT.


test: replacing toMatchObject with toStrictEqual

Issue #, if available:
Description of changes:
This PR changes currently used expect method toMatchObject to more preferred toStrictEqual.
Checklist:

[x] Have you successfully deployed to an AWS account with your changes?
[x] Have you written new tests for your core changes, as applicable?

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

Codecov Report

Merging #985 (0a80f6b) into develop (0b68cd5) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #985   +/-   ##
========================================
  Coverage    91.59%   91.59%
========================================
  Files          195      195
  Lines         6126     6128    +2
  Branches      1151     1153    +2
========================================
+ Hits          5611     5613    +2
  Misses         515      515

Flag
Coverage Δ

root
91.59% <100.00%> (+<0.01%)
:arrow_up:

swb-app
89.18% <ø> (ø)

swb-reference
94.41% <ø> (ø)

workbench-core-accounts
93.50% <ø> (ø)

workbench-core-accounts-ui
∅ <ø> (∅)

workbench-core-audit
95.00% <ø> (ø)

workbench-core-authentication
100.00% <ø> (ø)

workbench-core-authorization
100.00% <ø> (ø)

workbench-core-base
80.22% <ø> (ø)

workbench-core-datasets
?

workbench-core-datasets-ui
?

workbench-core-environments
?

workbench-core-environments-ui
?

workbench-core-infrastructure
99.36% <ø> (ø)

workbench-core-logging
100.00% <ø> (ø)

workbench-core-swb-common-ui
∅ <ø> (∅)

workbench-core-user-management
100.00% <ø> (ø)

Impacted Files
Coverage Δ

...ore/datasets/src/wbcDataSetsAuthorizationPlugin.ts
99.06% <100.00%> (+0.01%)
:arrow_up:


fastlane init error: app identifier is nil

I am having trouble getting fastlane init to complete successfully. I am using Ruby 2.3.5 and Fastlane 1.52.0. Here is the error number: 887107dd56d0a634cc837d23388297d4
When I run fastlane init, it asks for my Apple ID, and prints out the detected values. The App Id, and App Name are filled out but App Identifier is empty. I'm prompted with the message "This app identifier doesn't exist on iTunes Connect yet, it will be created for you" and "This app identifier doesn't exist on the Apple Developer Portal yet, it will be created for you". I confirm the above values and an error is thrown.
Looking at the log: "message": "TypeError: no implicit conversion of nil into String", and "culprit": "fastlane/setup/setup_ios.rb in gsub! at line 110"
I've opened the project in xcode, cleaned, built, and run with no errors. I've also confirmed that the bundle identifier is filled com.test.project.example. The project is originally an Ionic/Cordova hybrid project.
Attached is the json file zipped up.  Please let me know if there's any additional information you need.
(https://github.com/fastlane/fastlane/files/101217/sentry_887107dd56d0a634cc837d23388297d4.json.zip)
[sentry_887107dd56d0a634cc837d23388297d4.json.zip]

i think this might be a dupe of https://github.com/fastlane/fastlane/issues/1167 or will at least be addressed in the same fix. @jxbambrick if you don't mind, we can close this and track progress on the other issue?

That sounds good. I think I found #1167 shortly after posting this. Thanks for the support.


docs(recipe/magento2): fix typo in conccurent

[X] Docs added?

Thanks @SimJoSt!

It will be reverted by automation))

Hello it’s me! Stupid! 🤯


[daicard, node, client] 571 collateralization issues

The Problem
Fixes #571
Additionally, found a few other things:

addPaymentProfile was in the client API, meaning users could arbitrarily add their own profiles that would be honored when making a requestCollateral call (should be an admin function)
autoswap was being called twice, one right after the other at the end of autoDeposit and at the next line in the poller
autoswap was also not able to handle edge case where it has insufficient collateral to swap their entire eth balance (but will not add additional collateral following their profile)

The Solution

🔴  BREAKING CHANGE!! 🔴  addPaymentProfile removed from client API and modified to use admin auth
autoswap function cleaned up

Checklist:

[x] I am making this PR against staging, not master
[x] My code follows the code style of this project.
[x] I have described any backwards-incompatibility implications above.
[x] I have highlighted which parts of the code should be reviewed most carefully.
[ ] If my change requires a change to the documentation, I have updated it accordingly.

Note that backwards compatibility checks are being enforced, see PR #694 description for more info.


⚠ Processors has degraded performance

In ae1f18e, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 49 ms

Resolved: Processors performance has improved in 0fca37e.


Long running kernels silently hang up

Long running kernels (maybe longer than a few minutes) experiences silent connection termination while the notebook cell is still marked with an asterisk (*).
There is no explicit error messages neither in the web UI and nor in the console.
Reported by our precious beta user @badend.

Fixed regression in console (stdout/stderr) streaming in Sorna agents.
Now logging and continuous stdout streaming will work with Jupyter as well, which will makes it easier to debug when the program is abnormaly terminated.


fix: scrollbars not appearing in auth window

Summary
Closes #1765.
This was only a problem in Firefox, since it is the only one that actually accepts scrollbars=no.
Test plan
Tested desktop browsers:

[x] Chrome
[x] Opera
[x] Firefox
[x] Edge
[x] Safari

A picture of a cute animal (not mandatory but encouraged)

Deploy preview for netlify-cms-www ready!
Built with commit ad2c4c40614075cfadc4e99eba1aaa262ba851c0
https://deploy-preview-1766--netlify-cms-www.netlify.com

Deploy preview for netlify-cms-www ready!
Built with commit 87ea9da4c329ae1a73cd3ece32de1313aea02c58
https://deploy-preview-1766--netlify-cms-www.netlify.com

Deploy preview for cms-demo ready!
Built with commit ad2c4c40614075cfadc4e99eba1aaa262ba851c0
https://deploy-preview-1766--cms-demo.netlify.com

Deploy preview for cms-demo ready!
Built with commit 87ea9da4c329ae1a73cd3ece32de1313aea02c58
https://deploy-preview-1766--cms-demo.netlify.com


Stuck before training

Hi.
Thanks for sharing nice work.
I tried to train the model with original dataset (using your example set) or with my custom dataset.
But I got stuck when the number of gpus is larger than 1 (DDP setting)

I found that training with single GPU has no problem. But only multi GPU makes this problem.
How to solve this problem?
Thanks in advance.

Hi, I haven't encountered a similar problem. Do you have more detailed output or instructions?

Hi. I forgot to close this issue.
I solved this issue ; No code error
https://github.com/huggingface/accelerate/issues/2174
This repo is the key to solve.
I'll close the issue. Thank you for your answer.


Packit is not updating the GitHub PR status

I have submitted https://github.com/fedora-iot/zezere/pull/41, but even though the COPR build is marked as succesful, the Packit status is Pending.

We know about this, it's fedora-infra (fedora-messaging) issue and it's being investigated. Sorry

It should be resolved now. You can re-trigger it with /packit build

Closing, we have #334 to improve UX in such cases.


Add Sprint report - 32 (X-mas Sprint)

:christmas_tree:

@Ana06, is the best sprint report of this year :clap: :clap: :clap:

@DavidKang

@Ana06, is the best sprint report of this year :clap: :clap: :clap:

of the Chinese year? :unamused:

The pictures of the ruler are a bit to big. Though I only checked in GitHub

@bgeuken

The pictures of the ruler are a bit to big. Though I only checked in GitHub

they are 40%:
<img src="/images/posts/sprint_32-coolo-ruler.jpg" alt="Coolo's present" style="display:inline;width:40%">

Okay, then it probably is just a problem in markdown and no issue for us.


log_average_miss_rate wrong parameter name

miss rate is defined as 1 - recall  or FN / ( FN + TP ) so i guess tha naming of the parameter in the function
https://github.com/Cartucho/mAP/blob/92e6d334c903ab795fdae15d1a45730d768b4c08/main.py#L80
should be recall instead of precision since u send recall as a parameter in the function call
https://github.com/Cartucho/mAP/blob/92e6d334c903ab795fdae15d1a45730d768b4c08/main.py#L686

Thank you, yeah I just noticed this! I fixed it.


Make jpt the default cli - remove other entry point scripts

For multiple host inference, looks like we need to download model manually. Correct me If I'm wrong.

For multihost: either each host download their own copy; then discard the part that they dont need. OR, only the host number 0 downloads, then jax.device_put the shards to the other hosts. Both scheme should work but will be implemented separately.

For multiple host inference, looks like we need to download model manually. Correct me If I'm wrong.

For multihost: either each host download their own copy; then discard the part that they dont need. OR, only the host number 0 downloads, then jax.device_put the shards to the other hosts. Both scheme should work but will be implemented separately.

Thanks clarifying!


[DAGCircuit Oxidation] Refactor bit management in CircuitData

Summary
This is part of the work we're doing to port DAGCircuit to Rust. It's work I've pulled out of a local branch where I'm doing that port, in an effort to reduce the size of that eventual PR.
Details and comments

Added zero-cost struct types for our native Qubit and Clbit representation.
Added a new struct BitData which encapsulates maintaining a mapping between native Rust bit types and Python bit types. This significantly cleans up the code in CircuitData and makes it reusable for DAGCircuit.
Made InternContext into a generic SlottedCache data structure, which implements slotted caching for any T which is Hash and Eq. This is used to implement the new trait Interner<Vec<Qubit>> and Interner<Vec<Clbit>> for CircuitData.
Added Interner trait, for defining interner semantics for containers like CircuitData (and DAGCircuit).
Added PyNativeMapper trait, for defining a mapping between Python and native Rust types for containers like CircuitData.
Added trait InstructionPacker, implemented for containers which provide intern semantics for bit lists and mappings from Python bits to native bits. This allows us to share our instruction packing implementation between CircuitData and DAGCircuit.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

242 of 256 (94.53%)  changed or added relevant lines in 6 files are covered.
22 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.01%) to 89.615%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

crates/circuit/src/slotted_cache.rs
20
23
86.96%

crates/circuit/src/packed_instruction.rs
65
69
94.2%

crates/circuit/src/bit_data.rs
68
75
90.67%

Files with Coverage Reduction
New Missed Lines
%

qiskit/transpiler/passes/synthesis/unitary_synthesis.py
3
88.02%

crates/qasm2/src/lex.rs
7
91.86%

crates/qasm2/src/parse.rs
12
95.77%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
62232

Relevant Lines:
69444

💛  - Coveralls

I'm rethinking a bit of this PR (specifically the stuff with packing and interning) so I'm going to put this into draft for now.
The BitData stuff is likely to stay, but I'm likely to reduce the traiting stuff around packing and interning a bit.


Critical - the GTM template stopped working

Hi,
All of the sudden your GTM template stopped working. I have deployed your cookie consent on more than 10 websites and none of them displays the cookie consent modal window. I checked and re-checked offline cache and no luck

that was 0.5.0 template. I tried to deploy 0.5.2 but no luck either

Hi, Have you made the necessary changes?

maybe some certficate expired? I have no idea how developers publish their code into CDN network.

now it started working.. seems like some temporary downtime

We have it deployed on Datart.cz and it works there all the time. Try to use https://downforeveryoneorjustme.com/unpkg.com next time just like it would be great to have more debugging information so we can help you.
When I meet Vaclav, I'll say hello to him

Due https://github.com/68publishers/cookie-consent/issues/75#issuecomment-2397214641


[Feature] Add Complement Calculator

Description
The Complement Calculator takes a number and the base in which the number is written, and then finds the nth complement of the number as per the input.
Screenshots

Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

Go ahead @its-kumar-yash


error processing 3phase 1 angle 1 z stacks

I get this error when trying to recontract stacks with only 1 z-plane. No problems when z>1.
.., line 394, in get_current_p_stack
assert z_index < s[2], 'Please choose a valid z step for the selected stack'
AssertionError: Please choose a valid z step for the selected stack

Thanks @GiorgiaTortora, this is a problem that we had in the reshape function of the very first release (the one that you downloaded). It is now fixed. I close the issue


Refactor state into refs and tree.

This prepares the way for various state manipulations and introduces a top-level storage package that takes makes some steps towards Cosmos SDK compatibility. Changes included:

Prefix and KeyFormat types for handling prefixed lexicographic keys consistently
A CacheDB that wraps all changes within a block into a single DB transaction - i.e. Batch
A separate 'tree' and 'refs' storage in state. The former describes those values that contribute to the state hash and the latter does not - this gives us more latitude in disabling, for example, block storage or running nodes that opt to store somewhat different derived data whilst agreeing the the core account state.
Upgrade IAVL dependency to version including: https://github.com/tendermint/iavl/pull/107

Some changes that may follow in a future PR:

Content address account code for some deduplication
Content address blocks to allow their hash to be stored in main tree for consistency (not sure about this one)
Make block storage configurable
Consider using a Trie implementation in various places including caches for some reduced string -> []byte copying.

storage/cache_db.go line 45 contains a bug statement.
as @silasdavis is away let's merge anyway and I will fix up afterwards.


code explaination

Hai jeduan
I need to show the one view controller.......... like  image and crop option inside the popup u displayed in this plugin....how to do this? I analysis the ur code i thinks following line..
UINavigationController *navigationController = [[UINavigationController alloc] initWithRootViewController:cropController];
if (UI_USER_INTERFACE_IDIOM() == UIUserInterfaceIdiomPad) {
navigationController.modalPresentationStyle = UIModalPresentationFormSheet;
}
[self.viewController presentViewController:navigationController animated:YES completion:NULL];
but i don't know how to link with self.vieController.....
Please help me ya.. and send the step to do this please advice...........

how to link with self.delegate not found
how to use the following line
[self.delegate cropViewController:self didFinishCroppingImage:self.cropView.croppedImage];
Please advice......

Sorry, didn't understand the question. feel free to reopen.


MLSA Review

Describe the bug
MLSA
What happened?
The mlsa is very good and i don't have any bug in the mlsa training and submitting the feedbacks.
What did you expect to happen?
None
How would you reproduce the bug?
None
Did this happen via Desktop and/or Smartphone?
No response
Operating System
No response
What browsers are you seeing the problem on?
No response
Version
No response
Device
No response
What is your current role?
None
What technical topic is this bug related to?
No response
Relevant log output
No response

Hi @ArpitKhandelwal-developer Was this a bug or you forgot to submit the actual issue?


Add some code to show how to make a custom dataset

Or at least point to one of our examples, eg https://raw.githubusercontent.com/agile-geoscience/rocky-playground/master/data/dts.json
Code is in the Data_for_Playground notebook, I'll at least add that to this repo.

I added a notebook, that will do for now.


API: sparse.linalg.svds: transition to rng (SPEC 7)

Reference issue
Toward https://github.com/scipy/scipy/issues/21833
What does this implement/fix?
This allows for use of new keyword rng alongside random_state in sparse.linalg.svds to prepare for the deprecation and removal of random_state and its legacy behavior.
In short:
if you pass the RNG argument by position or keyword random_state, it should work however it did before
if you pass a value val by keyword rng, it should behave as if you had passed np.random.default_rng(val) into the function.

There's a doc_string test (line ~292 in scipy/sparse/linalg/_eigen/_svds.py ) that I've kept using kwarg random_state=rng because rng is set to be RandomState(0) and if I change that, the resulting values must be changed a few lines below.
    >>> rng = np.random.RandomState(0)
    >>> X_dense = rng.random(size=(100, 100))
    >>> X_dense[:, 2 * np.arange(50)] = 0
    >>> X = sparse.csr_array(X_dense)
    >>> _, singular_values, _ = svds(X, k=5, random_state=rng)
    >>> print(singular_values)
    [ 4.3293...  4.4491...  4.5420...  4.5987... 35.2410...]

I could change the first line I've shown here to use default_rng, change the kwarg and change the values printed. But IIUC its better to leave random_state in order to minimize these changes. We'll deal with them upon removal.
Do I understand correctly? Let me know if I should change the test from using RandomState to using default_rng.

Do I understand correctly? Let me know if I should change the test from using RandomState to using default_rng.

Please do change it, actually. It is good to do it now because we want new users who refer to the examples to use rng. And if it were not done now, it would need to be done in two versions when the decorator begins to emit warnings about use of random_state.

I think this addresses all points brought up -- and lead to a couple others which were easy to fix.
One last point is that if random_array PR gh-21888 gets merged first, this one could change quite a few random_array calls to use rng= instead of random_state=.  Both should work during the transition, so I think that's OK... but if we switch them now it makes the next transition simpler.

I made all all svds tests deterministric and all propack tests that directly call _svpd deterministic.
The number of changes to make the tests deterministic is fairly large.
Every function call to _svdp now specifies rng. It is still an "optional" argument though, so I added code to normalize the input rng inside _svpd unless it is a RandomState. I could put back the check_random_state code if that is preferred.

Oops.. somehow I didn't commit my last set of changes.
pushed before committing i guess.
_svdp should work without any normalization because everything that calls it has already normalized it.  That said, if someone has been using it on their own despite it being private, if/when they don't provide an rng arg is defaults to None, which creates a strange error message. So, I put code to check if rng is None and raise a ValueError if that happens. But it would only happen if someone if directly using the private function.


CI: Runtime Test (privileged) TestSharingKey

CI failure

Copy-paste the output the test failure.

--- FAIL: TestSharingKey (1.11s)
    lbipam_test.go:669: Expected service status to be updated

Upload the zip file generated from that test failure.

cilium-junits.zip

Copy-paste the link of the CI build where that test failure has happen.

https://github.com/cilium/cilium/actions/runs/7107632741

another similar failure:
--- FAIL: TestRequestIPs (1.11s)
    lbipam_test.go:1907: Expected service status update

https://github.com/cilium/cilium/actions/runs/7107632741
cilium-junits.zip

--- FAIL: TestRequestIPs (1.11s)
lbipam_test.go:1907: Expected service status update

One more https://github.com/cilium/cilium/actions/runs/7114285658/job/19368045143


Editing a session hostname/ip adress does not change tooltip

What steps will reproduce the problem?
1. Edit a session
2. Change hostname/ip address and save
3. Hover over the session until the tooltip appears.

What is the expected output?
The new saved hostname/ip address

What do you see instead?
The old hostname/ip address is displayed.

What version of the product are you using? On what operating system?
<IP_ADDRESS> on Windows 7

Please provide any additional information below.
Restarting SuperPuTTY fixed the issue.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 11 Dec 2014 at 2:04

Closing this issue but all hope is not lost! We still want to help.
See: https://github.com/jimradford/superputty/wiki/Legacy-Imported-Issues on how to help us to help you!


Publish 7.1.1-20210708021503+0000

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Possible bug implying meta is present

I didn't have much time to analyze this, but I think meta should not be mandatory for simple posts of single resource. It leads to error in my case.
https://github.com/jsonapi-suite/jsonapi_errorable/blame/master/lib/jsonapi_errorable/serializers/validation.rb#L136

@klobuczek what's the error? The meta this is referencing is something the deserializer class in compliable sets, it is not part of the payload you send to the server.

@richmolj I think payload[:meta] is nil in my case. The error I got was no [] method on nil. This does not happen in 0.7.0

@klobuczek could you paste the payload you are sending? I am not sure how that would be the case.

@richmolj it was a customization problem in our code. Sorry for the false alarm.


Cleanup enforce_infinite_rlimits

Closes #240

removed getrlimit()
Added error description using strerror()

I didn't think adding errnum would be of any use. Let me know, if needed.

thanks!


ngf-thumbnail crashing IE11

When using ngf-thumbnail in IE11 once you try to upload around 100 MB of images the operation fails with a "Not enough storage is available to complete this operation".  (You may need to do one upload of images & reload the page and try again).
See fiddle: http://jsfiddle.net/nwy08oak/32/
I was attempting to get an example danialfarid posted in a separate issue (https://github.com/danialfarid/ng-file-upload/issues/1307) working with thumbnails & resize, but as you can see in the fiddle the upload chunk resizing code is being commented out.
I'm running on a machine with 32 GB Ram & quad core i7 as well.  I notice chrome seems to have no issue, but IE11 (and likely other versions) can't handle it.
It appears changing Upload.defaults.blobUrlsMaxMemory by an order of magnitude in either direction has no impact.
Any suggestions (I know, other than not to use IE)?

Use 'ngf-src' instead.

Thanks for the suggestion.  It works with ngf-src, but with no resizing after.  It crashes when you enable the compression piece (in IE11)
http://jsfiddle.net/nwy08oak/35/
Any ideas on how to solve?

It appears I wasn't setting the Upload.defaults.blobUrlsMaxMemory low enough.  The default is 268435456 and decreasing it by two orders of magnitude 2684354 appears to work (at least with ~ 100 MB of files)
That seems really low -- 2.6 MB?  Could you elaborate a little more on what that variable is actually setting?  Is it the total size of all blobs or just the data urls related to the blobs?
Thanks for all of your work on this library.

Dataurls are cached for faster access and avoiding recalculation for different validation sand resizing. That variable sets the maximum cumulative size of data urls that should be cashed. If you set it very low or set the number of dataurls to be cached to zero it will not cache any dataurls allowing more available memory for js engine.


ToCode Solution: תרגול פונקציות

03: please, spaces around operators. This isn't golf.
04: 'dict' is a keyword in python, please avoid using it as a variable.
Otherwise 👍


tester loadstring(game:HttpGet("https://raw.githubusercontent.com/lerkermer/lua-projects/master/SwagModeV002"))()

Are you okay?


Refactoring with Nextjs

This will make it easy to deploy your own version, see screenshot-to-code-next.
And add some new features:

Gemini model (gemini-pro-vision)
canvas drawing (excalidraw)
i18n
One click deployment to Vercel

Fork from  screenshot-to-code, ant-codeAI

Thanks for sharing this! Will incorporate some of this into the main repo.


Accent doesn't work

React-simple-keyboard version
^3.4.19
Describe the bug
When you press shift, any accent key and a letter, the letter does not acquire the desired accent. I didn't find anything in the documentation about this.
Expected behavior: shift  +  ^  +  e = ê
Received behavior:  shift  +  ^  +  e = ^e
Thanks in advance

Hello @henriquematiasb, this is not something supported by default. To support this, I recommend using unicode combining characters in your layout: https://en.wikipedia.org/wiki/Combining_character
Another option is to configure layout candidates with your desired combos.
Regards,
Francisco Hodge


module: Added flawfinder checker for finding security flaws

Fixed issue #522.
This module is to examines C/C++ source code and reports possible security weaknesses.
Flawfinder  searches  through C/C++ source code looking for potential security flaws. It examines
all of the project's C/C++ source code. It's very useful for quickly finding and removing some
security problems before a program is widely released.
Flawfinder produces a list of ``hits'' (potential security flaws), sorted by risk; the riskiest
hits are shown first.  The risk level is shown inside square brackets and  varies  from  0,
very little risk, to 5, great risk.  This risk level depends not only on the function,
but on the values of the parameters of the function.  For example, constant strings are often less risky
than fully variable strings in many contexts, and in those contexts the hit will have a lower risk level.
Hit descriptions also note the relevant Common Weakness Enumeration (CWE) identifier(s) in parentheses.

Wiki page for this module: https://github.com/nnsuite/TAOS-CI/wiki/TAOS-CI-Plug-in-Modules

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>

:memo: Version: 1.20190225. Thank you for submitting PR #546. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

Wiki Manual:

Output after this PR:

To Reviewers,
This PR required the reviews from the below developers.

Mandatory: @jaeyun-jung , @dongju-chae
Optional: @wooksong , @myungjoo , Others

Changelog

Version 2:

Added annotation for the module maintenance.
Improved the code readability.

Version 1:

Added new module (e.g. flawfinder) for scanning security flaws.
Added configuration varaibles.
Added document.
Added installation step of "flawfinder" package for users.

Changelog

Version 3:

Added source code formats (e.g., .cc and .c++)

Version 2:

Added annotation for the module maintenance.
Improved the code readability.

Version 1:

Added new module (e.g. flawfinder) for scanning security flaws.
Added configuration variables.
Added document.
Added installation step of "flawfinder" package for users.


There is no alternative.

Or is there?

This is not intended to suggest that any alternative to TailLoop exists right now. But I discussed a while back with @ss2165 how there are a great many alternative forms that we could have - typically, these allow to express more loops than TailLoop (loops that would otherwise have to be built as Cfg nodes), but are more complex to use.
I think we will only really see the motivation for this when we have a decent body/corpus of programs written in the Hugr, so it's not a decision we can take right now. @ss2165 agreed? But perhaps the doc just needs to be clearer that it's a note for the future rather than a description of the present - before we switched to .md it used to be "boxed out" so is there anything like that we can do in .md?

I wonder if it might be left as an issue for the future rather than a discussion in the spec?

Yeah I'm happy to create an issue for this. I think there is benefit to making this document a concise description of our current proposal. @acl-cqc would you be OK with moving it out to a separate issue?

Yes, absolutely. (An issue or a discussion? - neither of which were being used when we wrote this in the spec)

Yes, absolutely. (An issue or a discussion? - neither of which were being used when we wrote this in the spec)

Probably a discussion actually.

#216

Ok, thanks!


Fix tag link

fixed a bug in a tag link on tag page

Didn't want to add categories to the meta but thanks for noticing the jekyll update messed with the relative paths.  I just made the quick fix.