Add code splitting

I guess 404 pages are broken: https://app.petbook.lt/dont-exists.
Notice there is no content and error loading content is missing.

I guess 404 pages are broken: https://app.petbook.lt/dont-exists.
Notice there is no content and error loading content is missing.

I believe url for 404 is https://app.petbook.lt/not-found

I believe url for 404 is https://app.petbook.lt/not-found

yes, but when trying to load the page that it should show https://app.petbook.lt/not-found - instead of showing empty content: https://app.petbook.lt/aaa

yes, but when trying to load the page that it should show https://app.petbook.lt/not-found - instead of showing empty content: https://app.petbook.lt/aaa

@rikius  We don't have such route setup yet. We just showing it on particular /not-found page:
                            <Route                                 exact                                 path="/not-found"                                 component={React.lazy(() => import('./pages/PageNotFound'))}                             />

@rikius  We don't have such route setup yet. We just showing it on particular /not-found page:
                            <Route                                 exact                                 path="/not-found"                                 component={React.lazy(() => import('./pages/PageNotFound'))}                             />

If we would want to show PageNotFound for all not existing URL's, we should add
<Route component={React.lazy(() => import('./pages/PageNotFound'))} /> at the end of all routes

If we would want to show PageNotFound for all not existing URL's, we should add
<Route component={React.lazy(() => import('./pages/PageNotFound'))} /> at the end of all routes


improve profile page

give some margin top to this card and bring this in middle of the page

Please assign me this issue

@srivastavaritik I can try this . Please assign this to me as well.

@srivastavaritik I have made the required changes, Kindly look into my pull request.


Support "cargo release"

cargo-release is pretty awesome, and it seems github actions would be perfect to build releases across multiple operating systems.
Can we bake cargo-release into this workflow, or provide a way to use it?

Hey, @orf, release activities are discussed at the #6, let's group the collective ideas in a one place.
I'm going to close this one issue, but I would love to hear what are thinking about these questions specifically.


no attempt to apply QEMU patches?

For the last several ~days it seems like there are no reported success or failure in the application of project:QEMU patches.
I think patchew is a particularly handy feature but I have only used it occasionally.  So I don't know whether this is expected or not.  Does it just take a while sometimes?  Or are there times when it doesn't apply the patches and provide a git tree?

It seems it's back to work? Or is there anything still missing?

Looks like the applier is down, I'll take a look later today.


Portable fallback for the "raw memory provider" of ipc_test

Right now, the prototypical ipc_test is not portable, as we are using both unix domain sockets (kind-of portable, maybe excluding windows), and memfd for conveniently getting a mmap with huge pages enabled.
To make this portable, we could fall back to the shared_memory crate as a "raw bytes provider". The difference of their implementation is: they only need to pre-share a unique identifier between processes, whereas our code currently needs to have a unix domain socket server running in a background thread. The interface needs to account for both cases.

shared_memory: https://github.com/elast0ny/shared_memory

This should be fixed with #3 being merged now.


[BUG] Case sensitivity

Hi
This is not a bug rather a change request.
We have an ACME server product which expects case sensitive JSON fields like it is documented in https://tools.ietf.org/html/rfc8555
For example in chapter 7.3 Account Management, we expect the fields "contact" and "termsOfServiceAgreed". Your client sends us these fields with an upper case first letter: "Contact" instead of "contact" and "TermsOfServiceAgreed" instead of "termsOfServiceAgreed".
Expected behavior
We would expect that you send case sensitive field names as documented in https://tools.ietf.org/html/rfc8555.
This is not must change but would be good practice because URLs are often case sensitive.
Best regards

That is a bug.
ALL other functions will be nice and use lowercase except the New-Account function 🤔
I'll fix it and release 1.2.5 within the day.
-- OT --
May I ask what the acme-server is called?

Hi,
Thanks, that is good news. We have implemented ACME in our product true-Xtender Registration Authority (RA-ACME+) and customers are interested in ACME clients implemented in PowerShell.
Link to our product: https://www.keyon.ch/de/Produkte-Loesungen/Microsoft-PKI/index.php#anchor_de2e011d_Accordion-true-Xtender-Registration-Authority
I am therefore testing your client.
Best regards
Christoph

1.2.5 should fix that bug.


generate color palette

how to use randomColor to generate color palettes giving the base color (e.g. 'hue' option)
for example like these https://www.google.com/design/spec/style/color.html

Hi @alrz! This is not currently possible using randomColor and falls outside the scope of the library. It would be a neat and useful tool though!


Why are we throwing errors for parsers when things are not found?

If you look at the definition of build_InconsistentAssumptions it simply throws an error when run.
https://github.com/facebookexperimental/reason-native/blob/4cd16aafd09c76ed7c81baf137b2691c61a6c32a/src/refmterr/lib/parseError.re#L444-L445
This is true for many parsers, including

build_InconsistentAssumptions
type_RecordFieldError
type_FieldNotBelong

https://github.com/facebookexperimental/reason-native/blob/4cd16aafd09c76ed7c81baf137b2691c61a6c32a/src/refmterr/lib/parseError.re#L516-L527
Would it not be simpler to simply return None on no match?

Updated post as I realized this wasn't actually an error but rather a weird practice of returning None

Usually you don't want to throw exceptions to signify information. Save exceptions for things that are really failures of the app. The main exception is for perf critical code - which this is not.


repo.rb recipe

The repo.rb recipe fails in a amazon linux ami. This is because the 'node['platform_version']' return something like this '' 2015.09' and it fails when creating the varnish.repo file.

Hi @agutierrezl -- we're not currently testing on or supporting Amazon Linux, but we'd gladly review a PR or other enhancements to make this work on Amazon Linux. Thanks for the heads up!


Make it possible to detach also queries

Before I go too deep to code, may you explain what's the use of it?

I wanted to detach work-related queries while on vacation. It's like ignore with playback buffer. When I'm back to work, I can conveniently restore the discussion straight to my client by attaching the queries.


Populate Data.list name filter from File_Format.name_patterns

Values for name_filter come from File_Format.name_patterns
Data.list
    directory:File
    name_filter:(Text | Vector Text) = []
    -> Vector File

File_Format.name_patterns is a list of extensions and extension groups to each File_Format.
The patterns will include single extensions or groups of extensions, along with a GUI-friendly description.
File_Format.name_patterns
    -> Vector Text

Example:
file_format.name_patterns =>
[[[“csv”], “CSV Files”], [[“tab”], “Tab Delimited”], [[“csv”, “tab”], “Delimited Flat Files”]

Make sure name_filter works (tests)
Add name_patterns
Add widget for name_filter based on name_patterns


Navgraph viewmodels

for viewmodels that are bound to navgraphs instead of activities or fragments, how do we create the savedstateRegistryOwner?
as below
@Binds
    abstract SavedStateRegistryOwner bindSavedStateRegistryOwner(CommitListFragment commitListFragment);

Sorry for the long delay in my response.
It's not possible unfortunately. I updated my article to reflect that and I now recommend against using AssistedInject.
With the new Dagger Hilt, you no longer need to implement a ViewModel factory. Check out this PR for more details.

@Nimrodda thanks for your response, i actually did it like this, and it seems to work fine, with assistedInject. But i do agree that Hilt is a much cleaner simpler approach.
@Inject
lateinit var factory: DaggerViewModelFactory

private val viewModel: SomeViewModel
        by navGraphViewModels(R.id.some_navigation) {
            factory.create(findNavController().getBackStackEntry(R.id.some_navigation))
}


NotContainDocBlockLike matches not related classes

Feature Request

Q
A

New Feature
yes

RFC
no

BC Break
no

Summary
We want to be sure, no one throws a general Exception in functions:
	$rules[] = Rule::allClasses()
		->that(new ResideInOneOfTheseNamespaces('App'))
		->should(new NotContainDocBlockLike('@throws Exception'))
		->because('we don\'t want simple exceptions - use custom instead');

The rule also matches the case below, which is not useful:
	/**
	 * @throws ExceptionInterface
	 */
	public function doStuff(): void
	{
		doSomething();
	}

The violation:
Xxx has 1 violations
  should not have a doc block that contains @throws Exception because we don't want simple exceptions - use custom instead

Is there any possibility to use a regex?

Yes, it could be useful to accept wildcards!

@micheleorselli it makes sense...
So you would break backward compatiblity and transform NotContainDocBlockLike in an exact match when there are no wildcard?

Or we could add a new NotContainDocBlock and deprecate the usage of NotContainDocBlockLike

I prefer to add a new NotContainDocBlock rule.

Just brainstorming. Maybe it can be useful to add a specif rule for Exceptions. The rule ->should(new NotContainDocBlockLike('@throws Exception')) does not work well if the same Exception is used with a relative namespace (E.g. @throws Exception) or with the complete namespace (E.g. @throws \Exception)

I think I get what you mean... we should probably look into @throw tags and treat the m as dependencies


How to render 1 table instead of 2 tables - First Table(Header, Filter and Insert Row) and Second Table(Item Row)

@tabalinas
Help Request/Question:
A) As of now, JSGrid renders two tables at the HTML level.
How to render 1 table instead of 2 tables - First Table(Header, Filter and Insert Row) and Second Table(Item Row). It is impacting lot of the Alignment of Top Rows with the Item Rows. Somehow managing it with the Width but not working on properly on Desktop and almost all the other resolutions.
Below is the rendered code where RowRenderer function is already in use for rendering the data for ItemRow only but RowRenderer is not impacting on the Above Table Container.
NamePhoneTotal Red FlagsTotal Red Flags PointsStatus Jane Doe<PHONE_NUMBER>210In Progress Jane Doe<PHONE_NUMBER>00In Progress Jane Doe<PHONE_NUMBER>00In Progress Christine  15To Be Assigned null 15To Be Assigned Christine<PHONE_NUMBER>210To Be Assigned Christine<PHONE_NUMBER>360To Be Assigned Ankit Kumar<PHONE_NUMBER>931335To Be AssignedPlease, wait...
Please provide satisfactory solution for this problem.

@tabalinas
Any update on this? It is rendering 2 tables. One for header and one data which is disaligning the columns in the header with row data below.


The PowerShell script has wrong variable name for appying a per-uri policy

At https://docs.microsoft.com/en-us/azure/web-application-firewall/ag/per-site-policies#apply-a-per-uri-policy
The gateway is selected with following line, and assigned to a variable "$Gateway":
$Gateway = Get-AzApplicationGateway -Name "myAppGateway"
However, the rule is applied with a wrong variable "$AppGw"
Add-AzApplicationGatewayRequestRoutingRule -ApplicationGateway $AppGw `
This script will not run as is. The variables have to match.

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

ID: 4e00000b-acb1-de7a-c5b0-272270297a12
Version Independent ID: e1d57940-ebb9-f8f4-de7e-a08a619f2557
Content: Configure per-site WAF policies using PowerShell - Azure Web Application Firewall
Content Source: articles/web-application-firewall/ag/per-site-policies.md
Service: web-application-firewall
GitHub Login: @winthrop28
Microsoft Alias: victorh

Hello @durayakar, Thank you for your feedback. I have made a PR to address this issue.


Error while updating property 'stroke' in shadow node of type: ARTShape

Throwing this error on Android in dev mode, but production mode seems to be OK.
Error while updating property 'stroke' in shadow node of type: ARTShape
java.lang.String cannot be cast to com.facebook.react.bridge.ReadableArray

Looks similar to this: https://github.com/oblador/react-native-progress/issues/179

any update for this issue??

I have a fix in https://github.com/brewskey/art. Waiting for it to be merged here https://github.com/react-native-community/art/pull/65

I am receiving this error when running application with expo. Its working fine with react-native init project.

Did u solve this problem ? @JeremyBradshaw7

@Mhmetengineer no not yet, but I haven't re-evaluated since I raised it.

facing same issue, any update on this?

facing same issue, any update on this?

Still an issue....


Fix ItOperator testDomainOnPvUsingWdt test on external Jenkins

and fix NPE when a test fails to start operator
testDomainOnPVusingWdt was failing on external jenkins, fixed it.
http://build.weblogick8s.org:8080/job/weblogic-kubernetes-operator-quicktest/754/

Why are u using the old branch you created for parallel test effort.

I can reuse the branch as long as I have the latest code from develop branch. Having a new branch makes sense. In this case, I have some previous changes in testsinparallel_vanaja branch that were not merged, so I just picked the same branch for this fix also.

@bhavaniravichandran Take a look at TestUtils.java change. I couldn't test this change on OpenImage, so adding you as reviewer.

There are too many commits in the PR. Please start with a different branch from develop and cherry-pick the necessary commits.

I see..Sure.


add Calibre proper

(SORRY I used the wrong template!)
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
We have Calibre-web, seems we should have Calibre proper to go with it!
(There, I spoke British!)
Describe alternatives you've considered
I'm a fan of Ubooquity...
Additional context
https://hub.docker.com/r/linuxserver/calibre
If no one else does it, I probably will even though I don't use it.

I month, no response. @davestephens?

Yes. I have a life other than Ansible-NAS, believe it or not. I will get to
this around my job, kids at home, paid projects etc, as time allows...
On Tue, 26 May 2020, 03:01 bcurran3<EMAIL_ADDRESS>wrote:

I month, no response. @davestephens https://github.com/davestephens?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/davestephens/ansible-nas/issues/297#issuecomment-633769664,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFDGMBDDQV65RSCDP3DRSLRTMPI7ANCNFSM4MRAUF7Q
.


proxy pass

hello,
it's possible to create an proxy_pass ?
for my exemple if i would like call https://domain/toto i would like to redirect to <IP_ADDRESS>:6789/toto
if yes, have you an exemple ?
thank you
regards

Hi,
This is already documented within the documentation.

ok thank you but it's to light
for exemple, i had this line but don't work
testRouter:
  rule: "Host(`hadomain.duckdns.org`) && Path(`/test`)"
  entryPoints: ["web-secure"]
  service: testService

testService:
  loadBalancer:
    servers:
      - url: "http://<IP_ADDRESS>:1234/test"

where i wrong ?
thank you


Add UUID headers to Glibc

Related to https://bugs.swift.org/browse/SR-83
Right now its seems impossible to link to the UUID library without this fix. Also note that it should be part of the standard library and is installed by default on Ubuntu and most POSIX OS.

uuid.h is not a part of Glibc.  Please create your own module map in a package instead.


Vigor fixes

In my recent playthrough I used the vigor spells from Co8 the first time. The Lesser Vigor (I didn't test other ones) spell did corrupt my save files. If I cast the spell on a party member, save the game while the spell is active, and loading the save afterwards leads to a game crash, making the save unusable. I can reproduce this behaviour.
Testing was done outside of combat, on different party members and in different locations. All tests did leave to corrupted save files.
I wanted to do the mass versions as part of the Spell Compendium anyways (the normal Vigor spells are part of the SC as well) so I redid the three single target spells as well as adding the new ones. They all use the same condition (sp-vigor_fast_healing), all spells only pass their fast healing amount to the condition.
Bonus side effects:

You can't stack different vigor spells anymore (which you shouldn't be able to do), only the highest fast healing effect will stick.
I added help file entries for all three existing Co8 Vigor spells as well as the two new ones
Vigor spells are now hyperlinked to help files in the History Window
All Vigor spells now have a new particle effect
All Vigor spells have a Vigor buff icon now
Buff icons shows correct duration
The Co8 spells now have a spell long description

Cons:
I have never replaced an existing spell from Co8. So I hope I did it the correct way.

I removed the Spell794 - Lesser Vigor.py as well as the other 2 scripts from Co8infra and did regenerate that file
I added the spells to my spell_compendium admin files with the exception of the sound file. Though I am unsure if you can actually use Temple+ without Co8. If not, not all admin file entries would be needed

Edit: These spells require my updated spell_utils

Cool stuff!

Cool stuff!

Removed the onRemove heal sum up again, it triggers on too many occasions that it's not worth to add the missing ticks on a rest trigger.
@anatoliy-savchak What did you comment why on? That I limited the history output to combat only or on the sum up?

Yes @Sagenlicht. As a Player I want to have all logs at least in some place. History pane should have as much as it can IMHO. But it's up to you.
Moreover being DM I always ask Players to show me heal wand dice rolls and account wand leftover. So personally I would love to see any healing rolls in my History pane.

Yes @Sagenlicht. As a Player I want to have all logs at least in some place. History pane should have as much as it can IMHO. But it's up to you.

I am unsure about this myself. I am a huge fan of verbosing the history myself, but Vigor ticks alot, Inside combat this is no problem, I agree, information is key here, but outside of combat it appeared a little bit spammy to me while I playtested Vigor in my current runthrough.
In addition I am not sure how confusing the new behaviour now actually is, when the history output suddenly stops...


[W6.1h][T10-B3]Xie Yu Heng

Implemented Printable Interface and modified Address, Email, Name and Phone classes to implement Printable

Great work!
check out how to write better commit messages


Model storage should support more frameworks/tools

Description
stock.model's high level functions such as stock.model.load_weights currently only support PyTorch & Keras models. It needs to support other frameworks such as

Native TF (<2.0)
scikit-learn
ONNX
TBD

Onnx-ML would be good as well.
https://onnx.ai/

Thanks Rick. Added ONNX to the list


test: Add inner key e2e test to aws

Adding one more test to aws to see things triggering and checking if ok-to-test is working properly

Yay!

Gonna close this one and test from a fork now


Update fails error 1

Build/Submit details page URL
billnbell
Summary
eas update
✔ Linked to project @billnbell/theclub (https://expo.dev/accounts/billnbell/projects/theclub)
✔ Which branch would you like to publish on? › feature/red - current update: N/A
✔ Please enter an update message. … New
✖ Failed to build bundle!
Error: /Users/bill/theclub/TheClub/node_modules/expo/bin/cli.js exited with non-zero code: 1
It errors. weird!
Managed or bare?
bare
Environment
npx: installed 1 in 0.71s
expo-env-info 1.0.2 environment info:
System:
OS: macOS 12.2.1
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
Yarn: 1.22.10 - ~/.nvm/versions/node/v12.18.3/bin/yarn
npm: 6.14.10 - ~/.nvm/versions/node/v12.18.3/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8193401
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
expo: >=44.0.0-0 <45.0.0 => 44.0.6
react: 17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
react-native: ^0.68.0 => 0.68.0
npmGlobalPackages:
expo-cli: 5.3.0
Expo Workflow: bare
Error output
No response
Reproducible demo or steps to reproduce from a blank project
/a

Please run EXPO_DEBUG=1 expo export --experimental-bundle and share the output.


libdrm: move dependency on nvidia-drm out of weston-init

The nvidia-drm kernel module and associated load config are needed by libdrm but were only getting picked up by weston-init.
There are valid configurations (headless, egl-only) that need libdrm but do not pull in weston, so the runtime recommendation is moved to the libdrm bbappend.

There used to be a conflict between enabling modesetting in the nvidia-drm driver and the nvidia_drv X server driver module, which is why we had it tied in with weston, despite that not being the true nature of the dependency. Is that conflict still there? If so, we'll need to come up with a different scheme here.

That makes sense - I didn’t check with the X server, so I’ll follow up here.

Interestingly, it is fine with this option in the linux-yocto kernel (doesn't matter one way or another there), but with jammy it's old problem with the modeset=1 parameter.
I'll change this to adjust that parameter if x11 is enabled and not xwayland.

I've updated this to RCONFLICT a ${PN}-modeset package against whatever is stated to be ${XSERVER} if the modeset parameter is 1. The main nvidia-drm-loadconf package will always be present and load the module, but only RRECOMMENDs the ${PN}-modeset part.


Added Test instructions to README.md

Hello guys, I just added the test instructions to README, please take a look to see if it is ok to merge. Thanks!

Looks good useful addition for the dev setup of the package :)


fix: #187 - adjusted sidebar height

Before fix -

After fix -

I adjusted the height of the sidebar from screen height to (screen height - navbar height), which solves the issue of not showing all the list items in sidebar in scrolling.
(Ignore the names on sidebar titles, they were all duplicated just to replicate the issue on local machine)

please add screenshots/description of the change

please add screenshots/description of the change

Hii Harkirat sir,
i edited the first comment by adding screenshots and changes. once please review.
Thank you


[Ready] KORD runways updated

KORD updated with runway 14L/32R removed and runway 14R/32L renamed to 15/33.  See
http://www.flychicago.com/SiteCollectionDocuments/OHare/AboutUs/Pilot Awareness/OMP-PilotAwareness_9.15.2016.pdf
This addresses issue #684.

I accidentally included a commit for issue #682.  I reverted those changes with commit d1ce46a.  I'm new to Git so I'm wrapping my head around all this.

Removed those commits you didn't want, and merged via e47e3415277b7498a94ba5d8f0ba4b62d1319f19.


Add a fix for intermittent failure in the ConditionalAuthenticationTestCase.

$subject.
Related to https://github.com/wso2/product-is/issues/11018.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/500688099

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/500688099

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/500688099
Status: failure

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/500688099
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/500700138

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/500700138

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/500700138
Status: failure

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/500700138
Status: failure

Any idea why the PR builder is failing for this PR

Any idea why the PR builder is failing for this PR

Any idea why the PR builder is failing for this PR

The build log says,
Error occured when processing the Feature Artifact: org.wso2.carbon.identity.inbound.auth.sts:org.wso2.carbon.mex.server.feature:5.6.6: ERROR: Could not find artifact org.wso2.carbon.identity.inbound.auth.sts:org.wso2.carbon.mex.server.feature:zip:5.6.6 in wso2-nexus

Any idea why the PR builder is failing for this PR

The build log says,
Error occured when processing the Feature Artifact: org.wso2.carbon.identity.inbound.auth.sts:org.wso2.carbon.mex.server.feature:5.6.6: ERROR: Could not find artifact org.wso2.carbon.identity.inbound.auth.sts:org.wso2.carbon.mex.server.feature:zip:5.6.6 in wso2-nexus

Any idea why the PR builder is failing for this PR

The build log says,
Error occured when processing the Feature Artifact: org.wso2.carbon.identity.inbound.auth.sts:org.wso2.carbon.mex.server.feature:5.6.6: ERROR: Could not find artifact org.wso2.carbon.identity.inbound.auth.sts:org.wso2.carbon.mex.server.feature:zip:5.6.6 in wso2-nexus

There is a release in the https://github.com/wso2-extensions/identity-inbound-auth-sts repo for v5.6.6 [1].
But in the nexus, v5.6.6 is not available. The latest one in the nexus is v5.6.5 [2]
@mefarazath
[1] https://github.com/wso2-extensions/identity-inbound-auth-sts/releases/tag/v5.6.6
[2] https://maven.wso2.org/nexus/index.html#nexus-search;quick~org.wso2.carbon.identity.inbound.auth.sts

Any idea why the PR builder is failing for this PR

The build log says,
Error occured when processing the Feature Artifact: org.wso2.carbon.identity.inbound.auth.sts:org.wso2.carbon.mex.server.feature:5.6.6: ERROR: Could not find artifact org.wso2.carbon.identity.inbound.auth.sts:org.wso2.carbon.mex.server.feature:zip:5.6.6 in wso2-nexus

There is a release in the https://github.com/wso2-extensions/identity-inbound-auth-sts repo for v5.6.6 [1].
But in the nexus, v5.6.6 is not available. The latest one in the nexus is v5.6.5 [2]
@mefarazath
[1] https://github.com/wso2-extensions/identity-inbound-auth-sts/releases/tag/v5.6.6
[2] https://maven.wso2.org/nexus/index.html#nexus-search;quick~org.wso2.carbon.identity.inbound.auth.sts

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/500817698

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/500817698

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/500817698
Status: success

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/500817698
Status: success


Regex Ignore

Is it possible to add words to our settings.json that are regex and it ignores words that match it?
For example new Guid("........-....-....-....-...........") or any regex that is desired.
So settings something like
"cSpell.words": [
    "new Guid(\"........-....-....-....-...........\")"
]

This may also be handy for another thing I was about to suggest. I don't want URLs to be spell checked. For example:

I am looking into a more general solution.  That would also solve #3 and possibly #24.

I also would like to have this feature to disable spell-checking for CSS colors like #cccccc.

With 0.14.0, it is now possible to define RegExp to be ignored:
"cSpell.ignoreRegExpList: [
    "0x[0-9A-F]+",
    "#[0-9A-F]+",
    "file:\\S+"
]

or you can add as a comment in the source file:
// cSpell:ignoreRegExp 0x[0-9A-F]+
// cSpell:ignoreRegExp #[0-9A-F]+

If you want enhancements to how this works, please open a new issue and refer to this one.

Really helpful! Thanks 😄

Is it possible to ignore anything starting with $?
I've tried a number of different regex options with no luck, even tried getting help on StackOverflow: https://stackoverflow.com/q/49386209/99401

I answered it on stackoverflow:
"cSpell.ignoreRegExpList": [
    "^\\$.+"
]

The .+ at the end of the string is necessary to match till the end of the line.

Thanks Jason...
That works...unless the line is indented, then it does not work.
$fullpath = $path . '/test/';
shows that fullpath is spelled wrong.
If I add what you recommended to my user settings file it works but if I
have
$fullpath = $path . '/test/'; (with a leading tab) it sill shows fullpath
as spelled wrong.
$fullpath = $path . '/test/'; (with one leading space) does the same.
I'm guessing it looks at the entire line...?
Jason
On Tue, Mar 20, 2018 at 12:02 PM, Jason Dent<EMAIL_ADDRESS>wrote:

I answered it on stackoverflow:
"cSpell.ignoreRegExpList": [
"^\$.+"
]
The .+ at the end of the string is necessary to match till the end of the
line.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Jason-Rev/vscode-spell-checker/issues/27#issuecomment-374653733,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB9yH6bH_mU9VPRGpIOTe6mZCbhXTvT3ks5tgSf6gaJpZM4KjuDY
.

Jason,
Perfect!  Thanks for the help on this.
J-
On Wed, Mar 21, 2018 at 1:29 PM, Jason Dent<EMAIL_ADDRESS>wrote:

I misunderstood what you were looking for. You want to ignore all words
starting with $.
"cSpell.ignoreRegExpList": [
"\$\w+"
]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Jason-Rev/vscode-spell-checker/issues/27#issuecomment-375028948,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB9yHyFkEXzGkQHYACdrQ67YXC6W6sgSks5tgo4MgaJpZM4KjuDY
.

Hello Jason,
I am trying to ask the spell checker to ignore the keywords Clarinox and Txts. In the code, with a case insensitive fashion, I have things like ClarinoxStructure or Clarinox_Variable.
So I add the following settings in the settings.json
"cSpell.ignoreRegExpList": [
        "(?i)(?<=\\s|^|\\W|\\w)(Clarinox|Txts)(?=\\s|$|\\W|\\w)"
    ],

But it seems the checker still can pick those keywords. Any suggestions?
Thanks


text_embed.weight mismatch after finetuning

I made sure to use the vocab.txt file that comes with the repo but I'm not sure why this error still occurs. I'm finetuning this on a single english speaker dataset.

could you provide us the vocab.txt you use
thought you have used a wrong vocab.txt, check if the path is correctly pointing to correct vocab.txt

could you provide us the vocab.txt you use thought you have used a wrong vocab.txt, check if the path is correctly pointing to correct vocab.txt

my bad, i was using a custom one - it works fine now

this ticket can be closed now :)


Rename magic_zone Smarty plugin + refacto

Fixes #15.
{magic_zone} is now deprecated  and should be removed in v2.0.0.
We can now use {prettyblocks_zone} instead.
@PrestaSafe we need to update documentation.

Thanks @micka-fdz  and @jf-viguier


Treasury fraction of distributed rewards not accurately described in monetary policy

For a span of over 200 epochs there has been far greater than 20% going into the treasury from the reserves. The documentation would lead one to believe that 80% of the per epoch reserves of ADA that is being minted would be going to the delegators and operators of the network. This is not the case and the documentation glosses over this reality.

The content from this documentation page eludes to τ (funds going into the Treasury) as being 20%. However review of Treasury, Circulation, Reserves and Rewards Allocations shows that this is actually greater than 30%.

The following Compound contribution to the Treasury from
the inefficiencies of the pools explains the compounding effect of inefficiencies, leading to much greater than 20% moving to the treasury.

The findings list 40% going to treasury from the per epoch reserves.

During epochs 213-223 the treasury exceeded 40%, and on occasion even 50%, averaging 43.2% of the per epoch reserves
During epochs 224-240 the treasury averaged 34.4% of the per epoch reserves
During epochs 241-388 the treasury averaged 31% of the per epoch reserves

An average of 31% is going into the Treasury per epoch for over 150 epochs. This in essence is either:

A reduction of the delegator fraction of rewards by 13.75%, conversely would increase rewards by > 15% per epoch.
A depletion of the reserves by an additional amount which goes to the treasury instead of being retained in the reserves.

The documentation does not address this and that seems like being disingenuous or intentionally withholding or obfuscating the truth from the participants. I suggest the documentation should explain the parameters setting of 20%. However it should strive to describe accurately the split the treasury actually receives per epoch, because it is clearly not 20% and has a real impact on the bottom line of the delegators compounded annual return on stake and the operators profit margins, or the length of time reserves will be available before the network needs to be fully self sustaining.

Hi Trevor, thanks for your work.
This issue was discussed here https://forum.cardano.org/t/double-treasury-taxation-of-40-and-possible-workarounds/41461 on the end of 2020.
The discussion generated a proposal, through a pre-CIP, to decrease rewards that flow to Treasury to an effective 20% on distributed rewards instead of the whole reward pot, but due to the lack of interest among both IOG and the Cardano community it was finally retired. The result is that around 40% of the reserve will sooner or later flow into the Treasury.
https://github.com/cardano-foundation/CIPs/pull/35/files

Hey @feqifei, thank you for the initial work and PDF. I'm familiar with the CIP (ie. PR #35). Without commitment to fix the issue you brought up I'm now hoping for a minimum of documentation clarification.
However, I'd also like to suggest reconsidering opening the CIP and seeing if we can gain consensus on the changes. I believe I actually recall when this was only worked on, the part of the community I recall debating the fix was catalyst participants who felt they didn't want the treasuries cut adjusted, although I did not agree with this viewpoint. I don't recall if others at the time voiced similar opinions, but I may have missed Twitter or other threads of discussion.
I feel the research that went into the p and t parameters should not be in vain. I don't feel accepting the resulting extra treasury funds due to inefficiencies should be the path forward, even if some disagree. If the CIP is not reopened I definitely invite your view of how this could be easily described in the documentation. I read your PDF and the forum threads, again, yesterday before opening the ticket. I was going to take another pass today before coming up with a suggested change for the docs. I suspect with your efforts and deep knowledge of the topic you may have a very succinct idea of what should change. However I will definitely advocate for the CIP if you are willing to reopen it for discussion, as I personally support it and wish I had been vocal in the past at trying to gather more support for it.
Thanks

Hi Trevor, the lesson my friends and I have learnt at that time is that it's a lost battle trying to change the protocol behavior if the people/organizations that have the power of taking the decision are the same that benefit of the current situation.
And I don't mean that those people/organizations are acting with bad intentions, not at all.
The thing is that I come from a country where government taxation rate on people and businesses is around 50% overall and those funds are so bad managed.
Watching at the Treasury taking almost 40% of Cardano reserves, officially for the "common good" of the community, is something that is hard to agree on from my viewpoint.
Moreover, most of community members think that only 20% go to the Treasury because there is no clarity at all.
Anyway, and I speak for myself only, after that experience I prefer not to be involved again in a process that at that time wasted several days and energy.
Maybe thank to CIP-1694 something could change in the future.
I think that your request of just more clarity in the official documentation is fair and maybe achievable and I'll fully support you

Hello @TrevorBenson & @feqifei ! Thank you for raising this issue, we'll address it to update the documentation.

We discussed this issue with Kevin Hammond, IOG's Head of Software Engineering. The treasury rate explanation has been updated to explain the observed difference in percentage.
If calculating actual rewards rather than the monetary expansion, you might get a higher percentage (up to 30%). Also, it's important to note that the rewards given to stake pools may be reduced under certain conditions, such as when pools are not saturated, not fully pledged, or fail to produce their allocated blocks. Any unclaimed rewards remain in the reserves for future allocation. This clarifies the observed difference.


toolchain: Add React fast-refresh for hot reloading

This upgrades React to 17 and adds React fast-refresh for hot reloading.
It is indeed fast:

@mzikherman @dzucconi - please keep a look out for that weird hot reload cache issue y'all were seeing...

@damassi I'm seeing the following type errors after pulling the latest from master :
src/v2/Apps/Artist/Routes/AuctionResults/ArtistAuctionResultItem.tsx:323:5 - error TS2345: Argument of type 'DateTimeFormatOptions' is not assignable to parameter of type 'LocaleOptions & DateTimeFormatOptions'.
  Type 'DateTimeFormatOptions' is not assignable to type 'LocaleOptions'.
    Types of property 'numberingSystem' are incompatible.
      Type 'string' is not assignable to type 'NumberingSystem'.

323     DateTime.DATE_MED
        ~~~~~~~~~~~~~~~~~

src/v2/Apps/Purchase/Components/OrderRow.tsx:94:44 - error TS2345: Argument of type 'DateTimeFormatOptions' is not assignable to parameter of type 'LocaleOptions & DateTimeFormatOptions'.
  Type 'DateTimeFormatOptions' is not assignable to type 'LocaleOptions'.

94             {orderCreatedAt.toLocaleString(DateTime.DATE_SHORT)}
                                              ~~~~~~~~~~~~~~~~~~~

src/v2/Apps/Purchase/Components/OrderRow.tsx:160:42 - error TS2345: Argument of type 'DateTimeFormatOptions' is not assignable to parameter of type 'LocaleOptions & DateTimeFormatOptions'.
  Type 'DateTimeFormatOptions' is not assignable to type 'LocaleOptions'.

160           {orderCreatedAt.toLocaleString(DateTime.DATE_MED)}
                                             ~~~~~~~~~~~~~~~~~

Found 3 errors.

I ran yarn type-check on the last coupe of commits to where it was introduced, and it seems to be in commit 0477657, but I can't figure out what change would affect this. Do you have any ideas?

Fixed in https://github.com/artsy/force/pull/7240, sorry bout that!

Thank you! 🙌


GLTF not displayed when OBJ file with normals converted

OBJ file gets converted to glTF and working correctly. But when an obj file have normals and we convert file to glTF then it wont get displayed in Cesium.
Any ideal?

Thanks for the report - can you send over the model you're converting?

obj.zip
here is my obj files,i used obj2gltf 1.2.0.
i have the same problem with bharatshiyani .
but when i use https://cesiumjs.org/convertmodel.html ,this webapi.it can displayed in Cesium,also with little gltf file size.
why?

Thanks for sending the model over, I'm looking into it.

This seems to work now on master, which is outputting glTF 2.0.
Feel free to reopen if there are still problems.


Failed precondition: HashTable has different value for same key. Key the has 9 and trying to add value 25

What is the cause of this problem? I am training Chinese to English

You may have a  word that exits in the vocabulary file more than once.

It is not the case in my problem. I have checked the vocabulary.
Is there anything else that may have caused this?

@ssokhey Same here. Have you found what is causing the issue? This is driving me crazy.

这个问题有解决吗？

@tslater I forgot to add the following at the start of vocab files for both languages.
<unk>
<s>
</s>

It worked for me after this.

@tslater I forgot to add the following at the start of vocab files for both languages.
<unk>
<s>
</s>

It worked for me after this.

Why we have to add these three lines?


make it work with the new SA Mod Manager in addition to SA2 Mod Loader / SA2 Mod Manager

At the moment the project is designed for SA2 Mod Loader but supporting SA Mod Manager instead shouldn't be too difficult... I hope.
The current possible problem lines in APSA2BHandler.ahk
88: MLConfigFile := SA2BInstall . "\mods\SA2ModLoader.ini"
118: Run, "%SA2BInstall%\SA2ModManager.exe"
Obviously I'm going to need to find some way to detect if the user is using SAModManager instead and change what we do based on what it finds.
I'll worry about this when I care to switch my mod loader to the new one.

Unfortunately it wasn't easy to instantly implement a solution, so in lieu of being unusable with current mod setups, I've just commented out the effected problem. #2 now exists to address the problem directly


⚠ ClamAV has degraded performance

In 849ce0e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in ab54708.


Support for gradient in line chart

Hi,
I was searching for the possiblity to apply a gradient to a line chart. I just implemented this in a fork. I will open up a PR if you are interested to include this feature into the main repository. Here is a screenshot of the current result:

Thank you very much for the ongoing effort keeping this project alive :)
Cheers,
David

Is it already possible to set gradient direction?
I have a line chart with temperature values on the vertical axis, so it would be nice to have cold colors for low values and warm colors for the higher ones.


Guidelines on using jquery promises returned by Xrm.WebApi methods

The Xrm.WebApi methods (like create, etc), all return a Jquery promise object. But then you have the guidelines of "Avoid using jQuery for form scripts". Also, in this posting (https://github.com/MicrosoftDocs/dynamics-365-customer-engagement/issues/150#issuecomment-406198868) there is the usage of JQuery $.when. I just want to make sure that I am writing forms code that will have the least chance of being broken/deprecated in a future CRM release.

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

ID: 40021a7c-b7bc-631f-a0c0-c23c75ec5c7a
Version Independent ID: 9c0b3dd8-2031-7a3c-ddf8-5a6760bb0b44
Content: Best practices: Client scripting in Customer Engagement
Content Source: ce/developer/clientapi/client-scripting-best-practices.md
Service: crm-online
GitHub Login: @KumarVivek
Microsoft Alias: kvivek

The guideline "Avoid using jQuery for form scripts" is more about DOM manipulation. The section says, that jQuery "...allows for easy cross-browser manipulation of the DOM. This is explicitly unsupported..." and then states that $.ajax is quite useful (I can confirm, it really is). Thus, using $.ajax and promises API is fine.
Also, please note, that Xrm.WebApi returns jQuery promise only in Web (refreshed) UI. In UCI, Xrm.WebApi functions return native JavaScript promises . Therefore, I recommend using:

.then() instead of .done() and .fail() to handle callbacks. .then() works with both jQuery and native promises.
jQuery version 3 - it supports handling jQuery and native promises in a transparent way. Older versions don't.

Thank you @valdik5379455, your answer was exactly what I was looking for. It probably should be included in the actual documentation


IPNFT as ERC721.

all tests green.

uses _mint and making Reservable:mintReservation external to avoid reentrancies.


The Indeterminate circular progress glitchy on firefox & IE

On firefox only the animation for the circular progress appears to studder quite a bit. Can be seen on the docs http://callemall.github.io/material-ui/#/components/progress. Seems like clicking on them appears to make them flicker to different states too for whatever reason.

This kind of illustrates the issue.

This also appears to be an issue on IE10/11

I think that it's link to the new auto prefixer we are using.

is there any progress on this?

@anthony-dandrea : This does not seem to appear anymore in firefox 45.0.1 MUI version : 14.4 and above. But the issue still exists on Microsoft Edge.

There are a few isues open for this across various browsers, so marking as a dupe of #707.


'methods' property not provided?

Usage example shows:
...,
methods: {
doSomething: function(){}
}
Methods not shown as a property of vue-formly -  https://matt-sanders.gitbooks.io/vue-formly/content/v/2.0/how_to_use/properties_and_options.html

Hey man, first of all sorry for the late reply!
That "methods" property that you referenced isn't actually part of Vue Formly, that's a Vue property. I've updated the usage example to make it clearer ( and I also noticed an error there too! ). So what's happening is that in that example you're creating a Vue instance. The methods property is part of Vue and that's got a function in it to execute when the form submits. You'll see now I've made it clearer by adding a form element with the submit method on it that is triggered ( by Vue ) when the form submits.
Hope that makes sense!


refactor: Update for service key name changes to remove edgex- prefix

closes #414

The following 2 places also need to be updated.

Prefix on TAF/config/device-modbus/configuration.py needs to be removed.
The line on TAF/utils/scripts/docker/get-compose-file.sh could be removed.

The following 2 places also need to be updated.

@cherrycl , I have addressed all remaining instances of edgex-device-modbus in this commit.
https://github.com/edgexfoundry/edgex-taf/pull/422/commits/c8c4eb1bb06ba0032dbec0903aa246b86708a15e


[Feature]  Request support for termux-app

希望能支持 termux 运行 , 目前运行报告以下错误
I hope to support termux running, currently the following error is reported when running
~ $ sshx
2024-11-26T07:16:17.347212Z ERROR sshx: transport error

Caused by:
    0: error trying to connect: dns error: failed to lookup address information: Try again
    1: dns error: failed to lookup address information: Try again
    2: failed to lookup address information: Try again
~ $

Duplicate of #102.


Android build fails on Master

Operating system or device - Godot version:
git / master
Issue description (what happened, and what was expected):
android compilation fails
Steps to reproduce:
pull latest code from repo and compile for android.
Link to minimal example project (optional but very welcome):

There are a couple of more errors even after this fix.

could be duplicated #6134

@volzhs I think, dupe of both :smile:


Improve error matching on missing EOF

Summary of the changes / Why this is an improvement
Changes how we heuristically match queries on missing error context.
Fixes #113

all green feelsgoodman

Maybe add a changelog item?

Thank you. Maybe add a changelog item?
yeah i kind of forgot haha


Rounds API not completing

Description
After removing collections, the Rounds API fails to return a response to the caller. Remains open until the process is killed. Kills any forward progress on creating a proposed block.
Steps to reproduce
(prereq - create grpc client from the proto, and make a release build of the node and move it into your path and change the name to narwhal_node)

Start up narwhal network stack with configurations contained in results.zip
Wait until start up is complete for all workers and primaries
Setup worker clients and primary clients for all nodes
Via round robin, cycle through all worker clients and submit 500 TXs with body (tx-0) through (tx-499) (in total)
Sleep 3 seconds
Chose a primary client and identify it as a proposer
Obtain oldest and newest rounds via Rounds API
Obtain collections for a proposal via node_read_causal API
Obtain TXs from collection of proposal via get_collections API
Print TXs, save to disk, etc (w/e floats your debugging boat 😄 )
Issue remove collections at proposer and all other primary clients
Pick a new proposer from the primary clients (I chose one round robin) and restart at step 6

the restart here will fail to complete, the connection never completes

Additional notes, I have been unable to obtain all 500 TXs I've submitted regardless how long I wait, or how big/small the batches/collections are.
The code to run these tests in an automated fashion can be found here, specifically in the narwhal_network_test.go file
Logs, db state, etc all included in results.zip
results.zip

@jsteenb2 following our conversation summarising the observations we had so far:

Try to set the batch_size to a higher value than 5 bytes (ex try with 50 or 100 to begin with and see the results)
Try to give some extra time before you start posting your transactions and after you finished posting them (maybe instead of 3 seconds give something like 6-7 and retry)
The reason your second rounds call never completes is because of an infinite loop issue within the DAG compression which we'll be looking to resolve here

@jsteenb2 it appears that the issue of the infinite loop is due to a refactoring in the DAG where a recursion call was changed to an iteration (thanks @huitseeker for discovering the root cause!). The change has been reverted here.
I've produced the binary from that commit and tried to re-run the tests. The issue seems to have been fixed and but another nasty bug got surfaced - you can see the details here. We'll need to look better into it to confirm and prioritise accordingly.


Ignore UTF BOM at the beginning of the stream

When the json file stream contains a BOM sequence at the begining, the parser throws an exception and cannot parse the file, even if the encoding is UTF-8.
With this change, the parser ignore the BOM sequence if found.
I included BOM sequences for UTF-16 (BE/LE) and UTF-32 (BE/LE) too.

That is really useful feature, thanks. Could you please add tests for all 5 BOM cases? Additionally, I am afraid that adding this many ifs might slow things down, as Lexer is performance critical part. What about just add the BOM bytes to an existing list of whitespace chars? That should be constant in speed.
        // Lexer.php, lines 39-42
        ${' '} = 0;
        ${"\n"} = 0;
        ${"\r"} = 0;
        ${"\t"} = 0;
        // add it here

True, it would ignore more than just BOMs, but I think we can safely accept that.

Thank you for your quick response and to maintain this project.
Firstly I removed UTF-16 and UTF-32 because with this charsets you cannot parse byte per byte to detect the char separators. Multiple bytes must be parsed even with ascii table chars. Sorry my fault.
Secondly we cannot check if a BOM is present because the BOM sequences are multi-bytes. We must use the buffer to compare with. I suppose the position number check do a quicker test than always comparing strings. It seems not to have a performance impact on the tests results.
Open to your suggestion for this point.

For the sake of code tree simplicity I'd prefer this way - treating the BOM bytes as whitespace. Would you agree?

Thanks

You're welcome. It would have been merged sooner but I was waiting for your response.

Sorry I forgot to respond. I'll try to be quicker next time.

No problem, just explaining :)

I am looking forward to next time.


Python 3.3 dropped, but still artifacts in setup.py

https://github.com/nvbn/thefuck/blob/master/setup.py#L37
extras_require = {':python_version<"3.4"': ['pathlib2'],

Is this line still required?

Python 2.7 needs pathlib2. It's already deprecated and when we will finally drop support of Python 2 we will remove this line.

Oh, duh, sorry I missed 2.7 support. I'll close this issue as I'm sure dropping Python 2 will involve much bigger cleanups.


Update Dockerfile

Changelog:

Update Yara and yara-python to v3.5.0
Resolve broken dependencies (including pefile and installing msgpack via pip due to issue with version from Ubuntu 14.04's apt repo)

Attempted to build on Ubuntu 16.04 and ran into an issue due to inability to retrieve libzmq3 from apt repo; need to test from pip or some other repo (possibly with libzmq3-dev or from source). Dockerfile works with no issues on versions up to Ubuntu 14.04.

Thanks as always @wzod !


Ingests that use symmetric edge_labels (like interacts_with) should assert edge in both directions

Describe the bug
Some ingests like IntAct and STRING use symmetric edge labels like interacts_with. These should assert in both directions:
if ingest asserts:
A interacts_with B
it should also assert:
B interacts with A
To Reproduce
Example, STRING has this edge:
ENSEMBL:ENSP00000256935	biolink:interacts_with	ENSEMBL:ENSP00000439601	RO:0002434
So it should also have:
ENSEMBL:ENSP00000439601	biolink:interacts_with	ENSEMBL:ENSP00000256935    RO:0002434
Expected behavior
See above
Version
Example above is for the Aug 17 build

This applies to at least 7 ingests currently:
grep -l interacts_with `find data/transformed/ -name "*edge*tsv" `
data/transformed//ttd/edges.tsv
data/transformed//drug_central/edges.tsv
data/transformed//pharmgkb/edges.tsv
data/transformed//zhou_host_proteins/edges.tsv
data/transformed//ChEMBL/edges.tsv
data/transformed//STRING/edges.tsv
data/transformed//intact/edges.tsv

Possibly would be worth considering adding this enhancement to KGX instead of adding this to each of the above ingests (I could help with this)


Add support for CSI metrics kubernetes sidecar is exposing

currently, in ceph-csi we are exposing the GRPC metrics, now Kubernetes sidecar is providing an option to expose the GRPC metrics from each sidecar container. we should drop the current support of exposing our own metrics  and start supporting the sidecar metrics

@agarwal-mudit would you like to take this up?

Sure, please assign.

@agarwal-mudit do we need it in release-3.0.0 milestone? or can we move it outside

We can move, I missed working on this and now it would be difficult to meet the timelines because it might need more testing. Will fix it in next release.

We can move, I missed working on this and now it would be difficult to meet the timelines because it might need more testing. Will fix it in next release.

Thanks, @agarwal-mudit moving it out of release-v3.0.0 milestone

We already deprecated the grpc metrics in cephcsi, I think now we can remove it. This will also solve the issue of port conflict when cephcsi is used with hostnetworking enabled.
cc @nixpanic

/assign


Fixes caffeine not hitting the web middleware

Fixes #89

I'll take a look at this as soon as I am able. Thanks for submitting!

@ItaloBC This shouldn't be necessary. The service provider should be taking appropriate action to register the middleware.


fix(walredo): walredo process that causes errors is never killed

Before this PR, if walredo failed, we would still update last_redo_at.
This means the maybe_quiesce() would never kill that process, although
clearly something is wrong.
However, we don't want to kill the process immediately on each redo failure,
because, the redo failure could be caused by corrupted or malicious
data.
So, change maybe_quiesce() to determine inactivity based on last
successful last_redo_at.
The result is that a transient redo failure won't cause a kill.
If there are only redo failures, we'll spawn & kill walredo process
at frequency 1/(10*compaction_period).

If I understand correctly, the intent here is to introduce a new behavior, to kill walredo processes if they haven't successfully handled a request in the last N minutes.  So it's not a bug fix, but a policy change: we used to trust that walredo failures were our fault, but now we're inferring from walredo failures that the walredo process might be bad, and re-using the maybe_quiesce machinery to kill such processes -- right?

Correct!

Won't have time to work on this for the next ~2 weeks, the change will bitrot in the meantime


DAWN-610 ⁃ Context Free Actions

Context Free Actions
Some computations necessary to build consensus are expensive from either a computational or block space perspective, or both.  For example, the proof for inter-blockchain communication (IBC) is large, and validating it can only pass or fail.  Once a block is irreversible, this code path and data is useless (unless someone is performing a verbose revalidation of the chain).
Witness Actions provide a means to perform intense checks in a way that the computation is cheaper during production/validation and both computation and block space are prunable.
This is conceptually equivalent to Segregated Witness for the EOS.IO blockchain.
Details
New Action Type
Witness Actions are a new type of action which may only read its own payload and a new section of transaction data referred to as "witness data".   They are otherwise identical to normal actions.
In the example of IBC this action's payload would be the provably retired action from the foreign chain and a block ID from the foreign chain whose state includes the transaction.
In an example of a document publication platform (PUB) this action's payload would be the hash of a document to publish.
Witness Data
Transactions will contain a new section of data that provides witness data.  Witness data is anything needed to process a witness action that doesn not need to persist if you can assume the action processed successfully.   This is a broader definition that most cryptographic witness data would include.
In the example of IBC, witness data would be the merkle proof that the retired action was present in a particular block on the foreign chain and the merkle proof that said block is included in the chain represented by the block ID listed in the action payload
In an example of PUB the witness data would be the plaintext document.
Witness Data Access API
Witness actions can only read their payload and the associated witness data.  They cannot write anything.  They merely succeed in whole or fail.  This makes them stateless or context-free and allows trivial parallel processing.
In the example of IBC, the WebAssembly code will use this API and the action payload to assert that the proof is correct.
In an example of PUB, the WebAssembly code will use this API and the action payload to assert that the hash of the document matches the hash in the payload
Sibling Action API
Non-witness actions will have access to a new API which allows them to assert that the transaction in which a current action is processing also includes another action.  Due to our processing model, the current action can then assume that the sibling action was also successful as any failure in any action is a failure of the transaction as a whole.
In the example of IBC, the normal action will assert that a sibling action existed routed to the proper action name, with a properly formed payload (the transaction and block ID of the foreign chain).  It can then proceed to do stateful processing based on the assumption that this sibling action succeeded and therefore the given action was included in the foreign chain
In the example of PUB, the normal action will assert that a sibling action existed with the given hash as a payload and proceed to mark the document as published based on the assumption that this sibling action succeeded and therefore the given hash IS the hash of the desired document.
Resource Accounting
As witness action processing will happen substantially in parallel, it becomes harder to account for in resource controls.  However, as it depends on no state data it should also be possible to compute, ahead of time and deterministically, what resources this will consume.
A transaction will commit to this resource usage, the same way it will commit to packed size as part of #1386
Note, this commitment will only cover the resources spent on retiring witness actions.   All normal actions are not deterministically billable ahead-of-time as they depend on state that is considered volatile until the precise moment a transaction is retired.   If a transaction fails, the resources billed to it ahead of time for witness data will be refunded.
Prunable Data
As part of this, the block structure (on disk and wire) will change such that all witness data and signatures are part of an explicit and well-contained section.  This section can be truncated off of blocks when they are considered irreversible and will remain replay/re-indexable as irreversibility proves that all dependent processing "passes" and can therefore be implied

Notes from Dan re: Sibling Action API

consider access based on ordinal and type instead of data-driven.  This allows actions to potentially explicitly reference other actions in their respective payloads for the cost of an ordinal if they can imply the type.
consider more than an assert which allows reading the given sibling action data directly so that data present on both a witness action and a dependent action is not duplicated, the dependent can read it from the witness action directly.

➤ Kevin Heifner commented:
From Bart:
We have a few tests (one?) that actually exercises apply_block .  I think we should add some context-free-action tests that generate a block on one tester and then push that block into another to exercise CFA on apply_block

Related PR is https://github.com/EOSIO/eos/pull/1678

ATC:

Verify tests/chain_tests for block_tests and api_tests/cf_action_tests pass

ATC passes


Add collection info - RPC call (WIP)

PR checklist

[ ] Describe the added/changed/fixed/removed behaviour
[ ] Tag related issue(s)
[ ] Add appropriate unit tests and/or integration tests to the integration test repository

Looking good, some fields I don't think are needed in this RPC call. I also think we should have a think about whether it would make sense to have one RPC for all information, or multiple RPC calls for each individual part. What do you think?

Thanks for your review.. I think the reason for this rpc call is, storage collection_info would fail, ownedTokens list if it is too huge, then the storage retrieval fails.. so an alternative to that without ownedTokens info


[Storage] Initial STG88 feature branch setup

This is the initial commit (changelogs, service versions, etc.)

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


fix:Resolve deprecation warning for klogr.New in Metrics Server

Metrics Server: klogr.New is deprecated use textlogger.NewLogger instead
Checklist

[x] When introducing a new scaler, I agree with the scaling governance policy
[x] I have verified that my change is according to the deprecations & breaking changes policy
[x] Tests have been added
[x] Changelog has been updated and is aligned with our changelog requirements
[x] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[x] A PR is opened to update the documentation on (repo) (if applicable)
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #5732

Relates to #

/run-e2e internal

/run-e2e internal


Add missing include

stdint is needed for uint64_t and friends. Discovered when testing pre-compiled headers, which disturbs usual include ordering.
The problem can be seen with the simple testcase:
#include "int_utils.h"
int main(){}

Ping @hebasto. Another one like https://github.com/bitcoin/bitcoin/pull/27192 and https://github.com/bitcoin/bitcoin/pull/27144 uncovered by playing with CMake :)


Enforce (case insensitive) email uniqueness in database

Add a case-insensitive uniqueness constraint to the email field on people. This means that we have to move to an SQL schema, which has knock-on effects on moj_peoplefinder.
Before running the migration, the people table must be clean, with no email addresses that would violate the new constraint.

What's the reason for changing db/schema.rb to a sql schema?


Set location for backup_configuration

Add ability to set "location" in mysql backup_configuration

@syedrakib thanks for the PR! Could you modify the examples where backup_configuration  is used like https://github.com/terraform-google-modules/terraform-google-sql-db/blob/295ca1842b4bd4121b0618fedf773c7e5363f40a/examples/mysql-ha/main.tf#L79
You can also run the lint tests locally by running make docker_test_lint. More details here.

Thanks for the advice @bharathkkb . I will fix these matters.

Fixed in #126


feat(python): add bridgehub support

Commits to docs need to be signed through GitHub's systems. You can refer to https://docs.zksync.io/build/contributing-to-documentation/contribution-guidelines#signed-git-commits on what you need to do to get verified/signed commits.
Once you've done so, you should be able to edit your commits or rebase to add the verified signature which will allow merging.


Add GSS-TSIG support

Here's another go at adding GSS-TSIG support.
Inspired by how crypto/ssh handles this I've defined a simple interface for an external GSSAPI implementation and added this to the Client and Conn structs. I've added two new internal tsigGenerateGSSAPI() and tsigVerifyGSSAPI() functions that are passed this interface and then refactored the original exported TsigGenerate() and TsigVerify() functions to use these, passing nil for the GSSAPI interface, so existing code using those will behave the same as before.
I've left the new functions unexported and I haven't touched the Server or Transfer structs yet. I've not added any tests either but that should be easy enough if you approve.

This idea looks reasonable enough (though I won’t review the actual implementation just yet), it appears entirely backwards compatible. Can you show an example of how the interface might be implemented?

To begin with you need to establish a GSSAPI context with the target server.
You're basically doing what is documented in RFC 2743 with GSS_Init_sec_context(). You first call it passing GSS_C_NO_CONTEXT for the input_context_handle with a NULL input_token. The result of this is an output_context_handle and an output_token the latter of which needs to be sent to the target server.
To do this you send a TKEY request with the target server, the TKEY name is generated with something like this:
dns.Fqdn(fmt.Sprintf("%d.sig-%s", rng.Int31(), host)) // this is what nsupdate uses

and the request is created something like this:
msg := &dns.Msg{
	MsgHdr: dns.MsgHdr{
		RecursionDesired: false,
	},
	Question: make([]dns.Question, 1),
	Extra:    make([]dns.RR, 1),
}

msg.Question[0] = dns.Question{
	Name:   keyname,
	Qtype:  dns.TypeTKEY,
	Qclass: dns.ClassANY,
}

msg.Id = dns.Id()

msg.Extra[0] = &dns.TKEY{
	Hdr: dns.RR_Header{
		Name:   keyname,
		Rrtype: dns.TypeTKEY,
		Class:  dns.ClassANY,
		Ttl:    0,
	},
	Algorithm:  "gss-tsig.",
	Mode:       3,
	Inception:  inception,
	Expiration: expiration,
	KeySize:    uint16(len(output_token)),
	Key:        hex.EncodeToString(output_token),
}

That is sent to the server which responds (hopefully) with a TKEY answer. The key payload is now the input_token which is then used to call GSS_Init_sec_context() again and hopefully you get GSS_S_COMPLETE. If you get GSS_S_CONTINUE_NEEDED you repeat the exchange.
At this point you have a negotiated context which you should store using the TKEY name you created. That TKEY name is the TSIG secret name however there's no secret to speak of, the context is the secret here.
So an implementation of the interface would look something like this:
type context struct {
	client *client.Client
	key    types.EncryptionKey
}

type Example struct {
	ctx map[string]context
}

...

func (e *Example) Generate(msg []byte, tsig *dns.TSIG) ([]byte, error) {
	if dns.CanonicalName(tsig.Algorithm) != dns.GSS {
		return nil, dns.ErrKeyAlg
	}

	ctx, ok := e.ctx[tsig.Hdr.Name] // this is where you retrieve your negotiated context
	if !ok {
		return nil, dns.ErrSecret
	}

	token := gssapi.MICToken{
		Flags:     gssapi.MICTokenFlagAcceptorSubkey,
		SndSeqNum: 0,
		Payload:   msg,
	}

	if err := token.SetChecksum(ctx.key, keyusage.GSSAPI_INITIATOR_SIGN); err != nil {
		return nil, err
	}

	b, err := token.Marshal()
	if err != nil {
		return nil, err
	}

	return b, nil
}

func (e *Example) Verify(stripped []byte, tsig *dns.TSIG) error {
	if dns.CanonicalName(tsig.Algorithm) != dns.GSS {
		return dns.ErrKeyAlg
	}

	ctx, ok := e.ctx[tsig.Hdr.Name] // retrieve the negotiated context
	if !ok {
		return dns.ErrSecret
	}

	mac, err := hex.DecodeString(tsig.MAC)
	if err != nil {
		return err
	}

	var token gssapi.MICToken
	err = token.Unmarshal(mac, true)
	if err != nil {
		return err
	}
	token.Payload = stripped

	// This is the actual verification bit
	_, err = token.Verify(ctx.key, keyusage.GSSAPI_ACCEPTOR_SIGN)
	if err != nil {
		return err
	}

	return nil
}

That example is based on using github.com/jcmturner/gokrb5 for the GSSAPI implementation, on Windows you would use github.com/alexbrainman/sspi instead which has a similar API but uses SSPI.
You would then use it something like:
host := "ns.example.com"

e := new(Example)
keyname := e.NegotiateTKEYRecord(host) // this does the TKEY exchange as documented above

client := new(dns.Client)
client.Net = "tcp"
client.GSSAPI = e
client.TsigSecret = map[string]string{keyname: ""} // doesn't matter what the secret is set to

// Use the DNS client as normal
msg := new(dns.Msg)
msg.SetUpdate(dns.Fqdn("example.com"))

insert, err := dns.NewRR("test.example.com. 300 A <IP_ADDRESS>")
if err != nil {
        panic(err)
}
msg.Insert([]dns.RR{insert})

msg.SetTsig(keyname, dns.GSS, 300, time.Now().Unix())

rr, _, err := client.Exchange(msg, net.JoinHostPort(host, "53"))
if err != nil {
        panic(err)
}

if rr.Rcode != dns.RcodeSuccess {
        fmt.Printf("DNS error: %s (%d)\n", dns.RcodeToString[rr.Rcode], rr.Rcode)
}

There's probably a bit more housekeeping but that's essentially it.

The server side would be similar however you would have to instead respond to any TKEY requests by calling GSS_Accept_sec_context() as per the RFC but once you've done that the TSIG generate and verify code would be similar, perhaps just swapping the key usage so you would generate the response signatures using keyusage.GSSAPI_ACCEPTOR_SIGN and verify using keyusage.GSSAPI_INITIATOR_SIGN continuing the gokrb5 example.

That doesn’t seem too unreasonable and likely useable in practice. Is GSS-TSIG the only TSIG-extension-type-thing out there or are there others?

I've not seen any other mechanisms other than GSS-TSIG, apart from the standard HMAC methods. Of course GSS itself stands for Generic Security Service so it is potentially a transport for any number of authentication methods although realistically it is just Kerberos.

this looks good IMO. Maybe a example on the code/documentation makes sense? (mustn't be too big though)

[ Quoting<EMAIL_ADDRESS>in "Re: [miekg/dns] Add GSS-TSIG suppor..." ]

@bodgit commented on this pull request.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
In client.go:

@@ -226,7 +228,7 @@ func (co *Conn) ReadMsg() (*Msg, error) {
return m, ErrSecret
}
// Need to work on the original message p, as that was used to calculate the tsig.

          err = TsigVerify(p, co.TsigSecret[t.Hdr.Name], co.tsigRequestMAC, false)

          err = tsigVerifyGSSAPI(p, co.TsigSecret[t.Hdr.Name], co.tsigRequestMAC, false, co.GSSAPI)

As it's an exported/public function so I didn't want to change the signature
and break backwards compatibility. If that's acceptable I can update the
original functions.

ah, right, missed the T -> t
yep, proceed :)

I think I've addressed all of the comments. I added an RFC mention to the list in the README, a skeletal example to doc.go and some basic testing of the interface with a dummy implementation.

I do seem to recall someone previously wanted to dynamically update or handle the TsigSecret field in the past, so perhaps making this a little bit more generic and allowing this to handle any algorithm including the HMAC ones if provided? Wdyt @miekg?

[ Quoting<EMAIL_ADDRESS>in "Re: [miekg/dns] Add GSS-TSIG suppor..." ]

I do seem to recall someone previously wanted to dynamically update or handle
the TsigSecret field, so perhaps making this a little bit more generic and
allowing this to handle any algorithm including the HMAC ones if provided? Wdyt
@miekg?

good plan!

@bodgit Would you be willing to update this PR to make it a more general mechanism as described in https://github.com/miekg/dns/pull/1201#issuecomment-751941255? We can always come back to how it is now if that doesn’t work out.

The interface itself can be made more general. All that is missing is to just include the key secret, (i.e. the value for the relevant TsigSecret key), in the two method signatures. The GSS code doesn't use it but the HMAC code would need that.
@tmthrgd Is that what you mean?

@bodgit Not quite, I mean for it to be an optional replacement for the current system. It might still be worthwhile passing in a secret if it’s configured, but I’m not sure. Does that make sense?

Not entirely, if I'm honest.
I think you'd still want to keep the TsigSecret map, but with an accompanying map[string]TsigGSS (with a rename of that interface) for mapping each algorithm to its implementation. So you'd end up with something like this in the Client:
map[string]TsigGSS{
        HmacSHA1:   tsigHmacSHA1,
        HmacSHA224: tsigHmacSHA224,
        ...
        GSS:        ...,
}

Although all of the HMAC algorithms can actually share the same implementation, you just switch based on the algorithm like the current code does.
Is that what you mean? Perhaps it's easier for me to grasp if you have an example

@bodgit No worries, I'll try to clarify. Basically I'm suggesting something like:
type Client struct {
	// ...
	TsigSecret map[string]string
	TsigProvider interface { ... }
	// ...
}

If TsigProvider (bikeshed away) is nil, everything operates as it does now, but if TsigProvider is non-nil, then the provided interface handles all of it. It can switch on the algorithm and select secrets however it pleases. The interface would probably look pretty much the same as the TsigGSS you suggested.

Oh I see, so this one interface gets called for any number of algorithms? In this case should the TsigSecret map be relied on at all or should the TsigProvider be expected to have that information itself?

Ok, I think I've done what you wanted. I've basically run s/GSS/Provider/g over the code and removed the various GSS mentions as there's no need for them. The TsigProvider interface is expected to have its own secret store (where applicable) which I think is what your intention is.

I realised that if the TsigProvider is expected to provide its own secrets, we don't need to pass the secret in the tsigGenerateProvider and tsigVerifyProvider functions so the signatures are simplified slightly. The tsigHMACProvider code is pretty simple as Verify is literally just Generate plus an equality check.

I realised that if the TsigProvider is expected to provide its own secrets, we don't need to pass the secret in the tsigGenerateProvider and tsigVerifyProvider functions so the signatures are simplified slightly. The tsigHMACProvider code is pretty simple as Verify is literally just Generate plus an equality check.

I have no idea "CIFuzz / Fuzzing (pull_request)" is failing and the failure message isn't remotely helpful. I don't think it's related to this PR though. I did try rerunning it, thinking it might just be ephemeral, but that didn't seem to help. Not sure if we should try and diagnose that or presume it's unrelated and merge anyway.

I have no idea "CIFuzz / Fuzzing (pull_request)" is failing and the failure message isn't remotely helpful. I don't think it's related to this PR though. I did try rerunning it, thinking it might just be ephemeral, but that didn't seem to help. Not sure if we should try and diagnose that or presume it's unrelated and merge anyway.

I noticed it was failing on some of the other PR's so I don't believe it was something I broke. I couldn't figure out what the immediate breakage was, looks like Python trying to reference a nonexistent dictionary key.

I noticed it was failing on some of the other PR's so I don't believe it was something I broke. I couldn't figure out what the immediate breakage was, looks like Python trying to reference a nonexistent dictionary key.

[ Quoting<EMAIL_ADDRESS>in "Re: [miekg/dns] Add GSS-TSIG suppor..." ]

@tmthrgd approved this pull request.
Thank you for addressing all the comments. This LGTM and I think it's a
worthwhile addition.

thanks all, I'll just merge then :)
/merge

[ Quoting<EMAIL_ADDRESS>in "Re: [miekg/dns] Add GSS-TSIG suppor..." ]

@tmthrgd approved this pull request.
Thank you for addressing all the comments. This LGTM and I think it's a
worthwhile addition.

thanks all, I'll just merge then :)
/merge


Nothing painted just on tap

Hi! Nice plugin, thanks a lot!
The only issue I faced: once you just tap on the canvas, nothing is painted, no dot. Only if you swipe for a short, then you get something.
Would it be possible to update the plugin in order to get "dots" just on tap? Would be really useful.
Thanks in advance!

By the way, I slightly modified the source code and got what I wanted - now the dot with R of 1 pixel will be drawn if user just taped the screen without moving his finger for a while.

Hello and sorry for the late reply.
Sure we can add that functionality to the lib!
If you already have it implemented, could you please send a pull request?

I will try - I've never done this before :) I also implemented "erase" function but it's a bit dirty - it erases complete path which is met on the way of the "eraser" - a square form.
Probably you can have a look on code and make it better :)

So, looks like, pull request is generated. Have a look :)

Thank you!
Will take a deep look at it when I have some time :)

Any news? :) I've just upgraded the lib a bit further to export Map of paths/paint in order to be able to re-load them into canvas for re-use.

Hey!
Sorry, i have had no time to look at this because of work. But i will take a look at it now as i'm on holiday :)
Wow, cool! Would you mind posting another PR with that functionality? That is something i wanted to implement here but i didn't have any time for it :(

Thanks for feedback! I think, I still need a bit of time to make it fully functionable. Hope to post in couple of weeks

Take your time. No need to hurry :)

By the way, I slightly modified the source code and got what I wanted - now the dot with R of 1 pixel will be drawn if user just taped the screen without moving his finger for a while.

hi, do you know how I can achieve this?
https://github.com/ja2375/painter2/issues/5


LCD Test System

Base working test system for the TeenyAT

The thing with the STR >= was not implemented by me. I didn't know
there was an error in regard to range checking.
On Sat, Dec 16, 2023 at 11:26 AM miniat-amos @.***>
wrote:

@.**** requested changes on this pull request.
There a only a handful of changes / questions that need to be addressed
before I can merge.
In teenyat.c
https://github.com/miniat-amos/TeenyAT/pull/6#discussion_r1428842725:

@@ -429,7 +429,7 @@ void tny_clock(teenyat *t) {
}
break;
default:

fprintf(stderr, "Unknown opcode (%d) encountered at 0x%04X on cycle %" PRIu64 "\n",

fprintf(stderr, "Unknown opcode (%d) encountered at 0x%04X on cycle  %" PRIu64 "\n",

Revert this, and be careful when committing in your local repos about
accidental changes in whitespace.
On tnasm/syntax.asm
https://github.com/miniat-amos/TeenyAT/pull/6#discussion_r1428842741:
This file shouldn't have been touched by the addition of the LCD system
In tnasm/syntax.asm
https://github.com/miniat-amos/TeenyAT/pull/6#discussion_r1428842747:

@@ -25,7 +25,7 @@
.var age 27
.variable count

-;--- Common Instruction formats
+;--- Common Instruction formats
Revert this, and be careful when committing in your local repos about
accidental changes in whitespace.
In teenyat.c
https://github.com/miniat-amos/TeenyAT/pull/6#discussion_r1428844052:

@@ -187,7 +187,7 @@ void tny_clock(teenyat *t) {
case TNY_OPCODE_STR:
{
tny_uword addr = t->reg[reg1].s + immed;

	if(addr > TNY_MAX_RAM_ADDRESS) {

	if(addr >= TNY_MAX_RAM_ADDRESS) {

I remember you'd thought you'd found a range checking error related to the
top of RAM, but I need a specific example or something to justify this
change, because I think the change is not correct, but I'm willing to
believe I could be missing something. TNY_MAX_RAM_ADDRESS is 32767...
(0x7FFF), and a STR to that address should still be in RAM, correct? Also,
if there really should be a change here, it should also change everywhere
(eg, on OPCODE_LOD).
On .gitignore
https://github.com/miniat-amos/TeenyAT/pull/6#discussion_r1428852921:
None of these modifications make sense. Remove.
On docs/ISO.md
https://github.com/miniat-amos/TeenyAT/pull/6#discussion_r1428853198:
While we do need to introduce some of our TeenyAT documentation to the
repo, it does not belong in a PR that introduces a new system.
—
Reply to this email directly, view it on GitHub
https://github.com/miniat-amos/TeenyAT/pull/6#pullrequestreview-1785203039,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN2ISXVV2FTFYRQFNNRKC2DYJXDTLAVCNFSM6AAAAABAVW37RKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOOBVGIYDGMBTHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Merged... I restored the last good version of .gitignore, too.


Suggestion: Application run properties

Hey Archi, idk if someone already suggested it, but maybe you can implement some run properties?
Ex.:
C:\ASF\ASF.EXE -minimized
This one is the only useful for me, but I think someone will continue the list.

https://github.com/JustArchi/ArchiSteamFarm/wiki/FAQ


Security of EIP-6963 proposal

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[ ] Payment details have been provided (Polkadot AssetHub (DOT, USDC & USDT) address in the application and bank details via email, if applicable).
[x] I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[x] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @thierrysans:matrix.org

I have read and hereby sign the Contributor License Agreement.

I have read and hereby sign the Contributor License Agreement.

Closed, see comment in the corresponding, private Element channel.


Replaces ocm install via go get with release binary

As of the creation of this PR, building the container image fails attempting to go get ocm-cli. This PR switches the ocm install to use the latest release binary, rather than the current main branch code, akin to using a container image tag rather than :latest.

/lgtm
/approve

/lgtm
/approve


Grab info on pull request creation date & ideally whether the pr has been approved yet

This info can be surfaced in any number of places. but I immediately imagine giving more information in the reflect command output. Earliest/latest/average creation of authored and review-requested PRs? break PRs down by whether approved instead of or in addition to whether open or closed?

Creation date is now parsed and available as of version 0.2.0.
I have not grabbed approval status as that does not appear to be explicitly stored on a pull request so presumably I would just need to loop over all reviews of a pull request to see which are approve/decline.

Going to call this one closed now that Harmony has a way to retrieve review information for PRs. The information is not attached to the PR type and must be pulled individually per PR, but it is being used roughly as imagined in the reflect command's output.


Only execute the backlight on/off switch once.

Fixes LukeSkywalker92#61

please tell me when this is ready to merge. I'm a little busy at the moment, so i don't have time to review every change.

trivial change for a nasty bug, tested in my setup: works
From my perspective ready to merge

Thanks :+1:


lbry: fix .desktop file

Motivation for this change
During testing the lbry package, I found that due to the use of single quotes in the substitution of the desktop file, the path for $out is never expanded, thus breaking the desktop file. I missed this because said desktop file was being overriden by a local one, which I was unaware of.
Things done

N/A Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

N/A Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
N/A Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
N/A Determined the impact on package closure size (by running nix path-info -S before and after)
N/A Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I went ahead and fixed some other related issues in https://github.com/NixOS/nixpkgs/pull/119699
Closing this one in favor of https://github.com/NixOS/nixpkgs/pull/119699


Update index.css & index.js

Fixed the responsiveness of the Navbar by adding some media queries in index.css.
#659  Fixes Issue
Changes proposed
Add a new file (index.css) in the Navbar folder in the component.
#Screenshots

hey could you pls sync your branch git pull origin main

Hey...your branch is giving conflicts..Could you pls sync your branch and update your PR?


IR Module

This PR adds a module to make working with MLIR more convenient. As an example, I added a simple conversion pipeline from Julia SSAIR to MLIR (which we might not want to keep as a test) for very simple scalar code using a subset of julia intrinsics. But is seems to produce valid code which can be tested using the execution engine!
This is a draft because it may be better to make the API look a bit more like LLVM.jl, notably regarding ownership which is currently modeled as an owned::Bool field on the relevant structs (Region, Block,...).
The code for the IR module mostly comes from Coil.jl.

@Pangoraw thanks! That looks like a great starting point.
@femtomc do you have some time to take a look if this jams with your understanding of things?

Thanks for the review @jumerckx!

I've written a patch to handle context the same way LLVM.jl does (I didn't touch the ownership stuff though). If desirable, I can make a PR to this branch, or include it in a new pr?

That means something like passing a function to the Context constructor like so (I am unfortunately not really familiar with LLVM.jl) ?
Context() do ctx
  # use ctx
end

Can you open a PR targeting this branch?

That means something like passing a function to the Context constructor like so (I am unfortunately not really familiar with LLVM.jl) ?
Context() do ctx
  # use ctx
end

Yes, and functions internally call context() to get the most recent context on a stack. (See here in LLVM.jl)

Can you open a PR targeting this branch?

Opened one here: #17 , but still a bit of work left to finish it completely (see notes in pr). Depending on if there's additional comments, I'll try to finish it up soon :)

I will land this PR and we can continue working on this on main?


Update main.py with some EDA and data  visualizations [GSSOC'23]

#108

Closes #108
Description👨💻
Added in some data visualizations to understand the dataset well :- have added pie charts , histograms and many more .
Type of change📄

[] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How this has been tested✅
Using the plt.show() to check if the visualizations are correct and fulfill the requirements of enhancing the data visualizations.
Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷

Really sorry , for the amount of delay caused in this @Rakesh9100
Kindly review this PR , Waiting for reply.

You took too many days to create the PR so closing this now as GSSoC 2023 is over @sahaycodes


Lazy loading / Iterating on parts of file

Referring to    f = EventioKaitaiParser.from_file(TESTFILE)
Checking the code of the generated python extension, this loads the whole file eagerly in __init__.
It seems also there is no way to do lazy loading / iterating over seq parts of the file.
Is this a limitation of kaitai in general or only of the generated python code?
Originally posted by @maxnoe in https://github.com/cta-observatory/eventio_kaitai/pull/1#discussion_r1389253418

This is only a limitation of the generated Python code. In our last Zoom call, this is what we were talking about that would have to change.
Some file formats have very natural breakpoints where eager-reading stops and waits for a user choice about what to read subsequently. For example, it's natural to read a ZIP or HDF5 file up to the point where you get a listing of what's in the file, then wait for the user to choose which subfile or Dataset to actually extract. ROOT files have that stopping point at the TDirectory and TTree metadata, and then you'd want to iterate through data in the TTree, because it is a kind of sequence. Some file formats are only for iteration, without any header/directory structure at all, like CSV or newline-delimited JSONs (or newline-delimited anything).
Kaitai is more wide-open about the kinds of files that it supports, so Kaitai itself doesn't have a concept of a directory or other stopping point. Everything is a sequence of data instances, but some of those sequences are headers that you want to read in their entirety while others are big-data payloads that you want to iterate over. Therefore, that information about the stopping point has to be injected somehow.
I don't think the Kaitai KSY language has a way to say "this is a point where eagerness processing ends" (although delimited structures might be part of a solution). For most targets other than the new Awkward one, the Kaitai developers expect users to write a main function in the target language, which is where choices like this would get expressed. Since the Awkward target aims to make a push-button Python module, this kind of choice would have to get configured in the production of that Python module.
As far as I can see, there are two kinds of stopping points:

We've read the header/metadata/column listing and now present the user with a choice of which nested objects to read. The structure that the load function returns is record-like, and we'd return it without some fields. Subsequent load calls (or maybe a different function name, like subload) either return the whole record again with the new field included or just the field value by itself.
The data that we're returning is a stream—i.e. list-like. The objects in the stream have delimiters between them and each batch contains a whole number of values. For instance, if it's newline-delimited JSONs, we don't stop reading in the middle of a JSON line. In Python, this would be more natural as a generator/iterator that yields data, rather than returning it.

ZIP is a format that only has stopping point (1); CSV is a format that only has stopping point (2) (because we wouldn't stop reading and return control to the user after only reading the one-line header—there would be no choice for the user to make, anyway). ROOT is a format that has both stopping points (1) (TDirectory and TTree metadata, and soon also RNTuple metadata) and stopping points (2) (iterating through TTree or RNTuple entries).
First question: what kinds of stopping points does EventIO have? If it has a header that requires the user to make a choice about what to read next, like ZIP or ROOT, where is that point? is there more than one? and how would we design an interface to Awkward-Kaitai to say where it should stop that is not EventIO-specific?
Here's an idea: there's no reason to avoid reading non-list-like data. If there's a header, we can read all of its scalar fields (I'm including records within records in the word "scalar"). Only list-like data can be potentially large. A rule like "Don't eagerly read any list-like fields" is too strict; in a domain-specific setting like EventIO, some lists are known to be small. For example, the shape of a NumPy array is small; the number of values in the array can be huge. The load function could take a list of paths, like "field_name.nested_field_name.innermost_field_name", to not read eagerly. Since they're lists, the load function can always return data of the same type by returning these lists as empty lists. The generic Awkward-Kaitai framework can consider these configurable, while an EventIO reader built on top of it can bake in those field names.
I know that EventIO has stopping points of the (2) type, so there would be a second function—actually, a generator/iterator—that yields batches of data from the list that was excluded from the first read. This second function would have to be configured by "How many entries per batch?", which even a domain-specific EventIO reader would expose to the user.
On the Zoom call, I was said that I was considering reintroducing virtual/lazy arrays into Awkward Array as a way to express these stopping points, but @agoose77 talked me out of it. (It would be very disruptive to the Awkward infrastructure, and you can get your laziness by having multiple functions in Awkward-Kaitai, as I've described above.) So Awkward Arrays, the return and yield values of these functions, would be eager, in-memory artifacts, though the whole file would not be represented by a single Awkward Array.
In what I described above, the two functions, "Load from the beginning of the file, but exclude a given set of nested field paths (that have list type)," and "Iterate over batches of a given nested field path (that has list type)" would be purely functional. After the first function returns data whose type is the whole file but has some list-like fields missing, it deletes all of the C++ class instances it used to produce the Awkward Array, closes the file, and returns just the Awkward Array (possibly ak.Record, rather than ak.Array). After the second function yields a batch of items from its list, the C++ instances associated with that batch get deleted, the Awkward Array is yielded, but the file remains open for more reading. There's mutable state in the iterator ("Where in the file are we?"), but it's the mutable state of a coroutine.

First question: what kinds of stopping points does EventIO have?

EventIO, the basic file format, has the "object" as only unit. Iterating over these objects is the basic interface.
It's made a tiny bit more complicated by the fact that some objects can be "containers", i.e. are known to be streams of objects. Since you can only read most compressed streams forward efficiently, we iterate depth first.
That's the basic interface I'd expect for a lazy loading eventio reader.
Then there is the question of specific data formats using eventio, we have the two variantes: output of the CORSIKA iact extension storing Cherenkov light on the ground and output of sim_telarray, storing telescope data.
These both consist of some header-like information in multiple eventio objects, followed by a sequence of air shower events, also consisting of multiple objects each. In the end, there is also some footer information, e.g. summary statistics about the simulation.
Depending on configuration of the software, the structure changes  a bit (more information can be saved, etc.).
Here, the natural interface is to read the header part when opening the file and offering iteration / lazy loading of the air shower events, providing the footer information once the loop has been exhausted.


Convert from HAR file

Is your feature request related to a problem? Please describe.
Similar to #51 , sometimes we may wanna generate request from a har file
Describe alternatives you've considered
dotnet-httpie convert <xxx.har>

http://www.softwareishard.com/blog/har-12-spec/
https://docs.fileformat.com/web/har/
https://github.com/ahmadnassri/har-spec/blob/master/versions/1.2.md
https://github.com/ahmadnassri/har-spec/blob/master/versions/1.3.md

what if there are multiple requests, should we execute them all in sequence?


ci: bump versions of K3s/RKE2

According to Rancher support matrix we should use K3s/RKE2 version 1.27 to 1.30.
Verification run:

CLI-K3s-OBS_Dev
CLI-RKE2-OBS_Dev - TO BE DONE
UI-K3s-OBS_Dev
UI-RKE2-OBS_Dev - TO BE DONE

Can't we parameterize the k8s version ? Touching 34 files for a (simple) version bump doesn't seem to be very effective.

Can't we parameterize the k8s version ? Touching 34 files for a (simple) version bump doesn't seem to be very effective.

It's already  parameterize, matrix and inputs in GitHub Actions cannot be parameterize more unfortunately... We cannot load a file with some parameters for example, which would have been more efficient yes.


[DNM] fix titan upgrade from 4.0 to 5.0

Signed-off-by: Yi Wu<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Proposal: xxx
What's Changed:
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Please add a release note.
If you don't think this PR needs a release note then fill it with None.

/release