And also occasional happens on the FreeBSD builder:
ok  	net	4.125s
unexpected fault address 0x30861d76
fatal error: fault
[signal SIGBUS: bus error code=0x1 addr=0x30861d76 pc=0x1278f0]

goroutine 157 [running]:
runtime.throw(0x43096e, 0x5)
	/usr/home/paulzhol/buildroot/freebsd-arm-paulzhol-8e6e9e838185/go/src/runtime/panic.go:566 +0x78 fp=0x309f5e2c sp=0x309f5e20
runtime.sigpanic()
	/usr/home/paulzhol/buildroot/freebsd-arm-paulzhol-8e6e9e838185/go/src/runtime/sigpanic_unix.go:21 +0x1b4 fp=0x309f5e58 sp=0x309f5e2c
net/http_test.testStreamingGet(0x30829480, 0x282e1601)
	/usr/home/paulzhol/buildroot/freebsd-arm-paulzhol-8e6e9e838185/go/src/net/http/client_test.go:599 +0x204 fp=0x309f5f8c sp=0x309f5e5c
net/http_test.TestStreamingGet_h2(0x30829480)
	/usr/home/paulzhol/buildroot/freebsd-arm-paulzhol-8e6e9e838185/go/src/net/http/client_test.go:580 +0x24 fp=0x309f5f98 sp=0x309f5f8c
testing.tRunner(0x30829480, 0x486d70)
	/usr/home/paulzhol/buildroot/freebsd-arm-paulzhol-8e6e9e838185/go/src/testing/testing.go:610 +0xa4 fp=0x309f5fbc sp=0x309f5f98
runtime.goexit()
	/usr/home/paulzhol/buildroot/freebsd-arm-paulzhol-8e6e9e838185/go/src/runtime/asm_arm.s:998 +0x4 fp=0x309f5fbc sp=0x309f5fbc
created by testing.(*T).Run
	/usr/home/paulzhol/buildroot/freebsd-arm-paulzhol-8e6e9e838185/go/src/testing/testing.go:646 +0x304

I suspect http://golang.org/cl/23393 is the cause because it looks like the first occurrence on the OpenBSD builder:
https://build.golang.org/log/b75786ad6add5fe0116889706211d1e8faea9df5
With the FreeBSD builder being a bit more flaky, it starts happening after the e9228dd commit.

CC @randall77

This is a problem at the intersection of tinyalloc, zeroing code, and alignment faults.
       0x005c 00092 (../test/fixedbugs/bug260.go:30)   MOVW    $type.[10]"".T1(SB), R0
        0x0060 00096 (../test/fixedbugs/bug260.go:30)   MOVW    R0, 4(R13)
        0x0064 00100 (../test/fixedbugs/bug260.go:30)   CALL    runtime.newobject(SB)
        0x0068 00104 (../test/fixedbugs/bug260.go:30)   MOVW    8(R13), R2
        0x006c 00108 (../test/fixedbugs/bug260.go:30)   MOVW    R2, R1
        ...
        0x0078 00120 (../test/fixedbugs/bug260.go:30)   MOVW    $0, R0
        0x007c 00124 (../test/fixedbugs/bug260.go:30)   MOVW.P  R0, 4(R1)
        0x0080 00128 (../test/fixedbugs/bug260.go:30)   MOVW.P  R0, 4(R1)
        0x0084 00132 (../test/fixedbugs/bug260.go:30)   MOVB.P  R0, 1(R1)
        0x0088 00136 (../test/fixedbugs/bug260.go:30)   MOVB.P  R0, 1(R1)

Those are 4-byte writes there, but mallocgc is returning something that isn't 4-byte aligned.  It is doing that because [10]byte is tiny-allocatable, so sometimes we get an allocation some way into a 16-byte tinyalloc chunk.
The fix should be to do zeroing correctly, respecting the possible alignment of the type.
Nagging questions TBA:
Why doesn't this error happen on linux/arm?
Why does this have anything to do with the live variable analysis change?

Why does this have anything to do with the live variable analysis change?

Before the liveness change, we relied on newobject to return zeroed memory, so the compiler did not generate code to zero it again.  After the liveness change, the compiler emits a useless zeroing.  Bad, but not fix-for-go1.7 bad.  The zeroing-generating code itself is to blame.

Why doesn't this error happen on linux/arm?

My understanding is Linux on ARM supports emulating unaligned memory accesses (to make porting programs from x86 easier), and it's possible the builders have that option enabled.
I don't believe OpenBSD implements that emulation, and it seems likely that FreeBSD doesn't either.

Fix mailed (CL 23587)
I added a test.  If anyone has access to a freebsd/arm box, please try the test without this CL and see if it breaks.  It should.  I'm kind of baffled as to how freebsd/arm ever used to work before the fix - I guess we just don't ever zero unaligned memory.

@randall77 I think only tinyalloc ever returns unaligned memory, and it's always zero'd.

Right, but see my test, it isn't just malloc where we zero memory.

@randall77 Hm, yeah, that is baffling.

Keith, Linux/arm doesn't fault on unaligned memory access, you just pay the
penalty for the double load silently. The only platform we had that
enforced this was the original arm5 builder that died last year.
On Wed, 1 Jun 2016, 08:08 Matthew Dempsky<EMAIL_ADDRESS>wrote:

@randall77 https://github.com/randall77 Hm, yeah, that is baffling.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/15902#issuecomment-222836296, or mute
the thread
https://github.com/notifications/unsubscribe/AAAcA8mA6Rutaq8FiRit9o72zaFoJ-wvks5qHLF0gaJpZM4IqnEU
.


Feature/Performance: Hash calculation should only occur on demand, and not at every startup, as this can greatly affect performance

Fixed by 2eeccfc commit


[bug]  c6 buff is being included in snapshots, when it should behave similarly to sara c6 and not snapshot - (Discord user: srl)

duplicate of #211


port: Allow sending GET requests with a body

The changes in Allow sending GET requests with a body may need to be ported to maintain parity with microsoft/botbuilder-dotnet.

#minor
Description
This PR allows sending GET requests by adding a body to the request's content.
Composer related issue: #9158.
Specific Changes

Modified the switch clause to move the GET request case, to allow the body to be added to the request content.

Testing
The following image shows the GET request sent with a body in the content.

These changes can't be ported because node-fetch doesn't support GET requests with body.
Related issue: https://github.com/node-fetch/node-fetch/issues/1728.
Closing issue.


Status Bar Color doesn't change in real device

Regards of my question in stackoverflow (https://stackoverflow.com/questions/60733747/annotatedregion-doesnt-work-on-real-device) by using setState and AnnotatedRegion to change status bar brightness.
Steps to Reproduce

A fresh flutter project
A simple setState and AnnotatedRegion<SystemUiOverlayStyle> value set toggled between
light and dark

This runs perfectly on iOS Simulator but doesn't work in real device
Previews
iOS Simulator

Real device (iPhone XR)

Hi @ampersanda
from your stackoverflow question I see you are using 1.12.13+hotfix.8. I checked, it's true for stable, but not for the current master (tried with v1.16.2-pre.41).
You can consider to use another flutter channel which can already have this fix.
Closing the issue since it's fixed, but not yet for stable.
if you disagree please write in the comments and I will reopen it.
Thank you


key information extraction with DonUT on hand-written documents?

Hi everyone,
Has anyone tried fine-tuning DonUT for key information extraction on a corpus with documents half-digital and half-handwritten? Specifically, I am wondering if anyone has any evidence on how it performs on handwritten text, given that all the suggestions on generating a synthetic dataset with SynthDoG for pre-training  point to selecting appropriate fonts of the digital text.
I have a private corpus of invoices similar to CORD in nature (with slightly more variability in shape, size and format), but some of them may have sections of handwritten text from time to time in addition to or in place of digital text.

I can confirm that it also picks up handwritten information.

I can confirm that it also picks up handwritten information.

Thank you @Toon-nooT,
Could you share one example document with handwritten text that you tested DonUT on?
No stress if it's not possible


zoxide and fzf

Support out of the box for something like zoxide and fzf
https://github.com/ajeetdsouza/zoxide
https://github.com/junegunn/fzf

So the first step would be to integrate pixi and make these easy to install with pixi global. Then we need to figure out if we need to do something special for autocompletion etc.!

I just tested the two they are available with pixi global. Do you use them a lot? Can you tell us if they work nicely with the shell?

See also https://github.com/prefix-dev/shell/issues/58.


Build failure: undefined reference to protobuf symbols #34117 closed issue still occurring on r2.1

Re: https://github.com/tensorflow/tensorflow/issues/34117
This issue is still occurring when I build r2.1 branch with bazel 1.1.0.
It has been fixed on head.  Would it be possible to implement the fix on build r2.1
Also the maximum bazel version needs to be increased to 1.1.0 in configure.py once the fix is implemented (in both head and r2.1).

We do not intend to change the Bazel version on r2.1 branch.
@mihaimaruseac as well to confirm.

We should only cherry-pick the fix from head but we are too late in the release process to do another bazel version switch.

@dbonner,
Hope the above comments answered your query. Can we close this issue if you have no further queries? Thanks!


Feat/u32 vectorized

Draft
TODO

[ ] U32xN
[ ] Reasonable tests
[ ] Figure out how to avoid overflow on U32x*::euclidean_inner
[ ] Benchmarks
[ ] finish writing TODO list

Why is your TODO list itself a work in progress? TODO: finish writing TODO list? ;-)
(also, 'version bump' should be in the TODO list)

Why is your TODO list itself a work in progress? TODO: finish writing TODO list? ;-)
Done!

(also, 'version bump' should be in the TODO list)

These are my “pre turning this into a real PR” TODO’s I typically delete them after converting this from a draft. I do this half to remember what I’m doing and half to give others an idea of how this PR is progressing.

We got a failure on c1cd79c on the randomized testing but I can't tell if that's because my local symagen was fixed when I pushed this or if there is actually an issue... 💀


Develop

All changes in User Guide. Fixed a typo on UG Home page, “Table of Contents” tab will not wrap with larger font sizes (up to about 16), increased size of small, base and large font sizes to 12px, 14px and 16px respectively. Fixed an issue where the breadcrumbs got resized from the original based on changing the size of the font in the TOC tab.

I did not make the changes to  as after making the font size changes in .less the code segments look great in my opinion. Let me know what you think and I hope I reverted all the changes correctly ;-)


GetTargetsByLevelForLogger - LoggingConfiguration.LoggingRules is not thread safe

[xUnit.net 00:00:27.8269283]       System.AggregateException : One or more errors occurred. (Destination array was not long enough. Check the destination index, length, and the array's lower bounds.
[xUnit.net 00:00:27.8270756]       Parameter name: destinationArray)
[xUnit.net 00:00:27.8312139]         ----- Inner Stack Trace -----
[xUnit.net 00:00:27.8312708]            at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable)
[xUnit.net 00:00:27.8313274]            at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
[xUnit.net 00:00:27.8313899]         /home/travis/build/NLog/NLog/src/NLog/LogFactory.cs(855,0): at NLog.LogFactory.GetTargetsByLevelForLogger(String name, IEnumerable`1 rules, TargetWithFilterChain[] targetsByLevel, TargetWithFilterChain[] lastTargetsByLevel, Boolean[] suppressedLevels)
[xUnit.net 00:00:27.8314531]         /home/travis/build/NLog/NLog/src/NLog/LogFactory.cs(914,0): at NLog.LogFactory.GetConfigurationForLogger(String name, LoggingConfiguration configuration)
[xUnit.net 00:00:27.8315153]         /home/travis/build/NLog/NLog/src/NLog/LogFactory.cs(1218,0): at NLog.LogFactory.GetLogger(LoggerCacheKey cacheKey)
[xUnit.net 00:00:27.8315640]         /home/travis/build/NLog/NLog/tests/NLog.UnitTests/LogManagerTests.cs(572,0): at NLog.UnitTests.LogManagerTests.<>c__DisplayClass25_0.<ThreadSafe_getCurrentClassLogger_test>b__2(Int32 e)
[xUnit.net 00:00:27.8316180]            at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion)
[xUnit.net 00:00:27.8316537]         --- End of stack trace from previous location where exception was thrown ---

https://travis-ci.org/NLog/NLog/builds/303097933?utm_source=github_status&utm_medium=notification

guess we need a lock, ins't?


[Bug-RD][UI Next][V1.0.0-Alpha]Set parameters before timing Next five execution times is null

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
Set parameters before timing Next five execution times is null

What you expected to happen
The next five running times can be displayed to verify the correctness of the Settings
How to reproduce
Workflow on-line, click Set timing operation, set running rules
Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

I have checked this issue, the problem is no environment data in table t_ds_environment. I have copied one row data from 2.0.3database to dev env, please check again the array of the interface. Thanks!

Currently is okay, need to try the in newest version.


[1.21]Aquaculture 2 weight configuration compatibility？

When I installed Aquaculture 2 and this mod as well as I enable the weight configuration,I found that the fish I caught had no weight information.As soon as I removed this mod,it became normal.So I'd like to know if you are willing to manage to find time to consider the compatibility between the two mods?Thank you very much.
Aquaculture 2 mod version1.21-2.7.8
FishingOverhaul mod version1.21.0-1.0.0
Neoforge version 21.0.148

I'm planning on looking into a better way to do compat and Aquaculture is a mod that I will target. I will let you know when this is achieved


Issue when using Vertex Gemini - "undefined" JSON Error

Hi,
running into issues with any vertex:gemini models, other models work fine.
Have been using GOOGLE_APPLICATION_CREDENTIALS with the service account absolutely fine on Friday (07/06/2024) but same setup generates below errors today (Monday).
The credentials file is a valid json.
Running this within a Jupyter notebook using promptfoo@latest (i.e.!npx promptfoo@latest eval -c promptfooconfig.yaml --no-progress-bar --share)
SyntaxError: "undefined" is not valid JSON
at JSON.parse ()
at VertexChatProvider.callGeminiApi (/Users/xxxx/.npm/_npx/81bbc6515d992ace/node_modules/promptfoo/dist/src/providers/vertex.js:120:40)
at VertexChatProvider.callApi (/Users/xxxxx/.npm/_npx/81bbc6515d992ace/node_modules/promptfoo/dist/src/providers/vertex.js:103:25)
at Evaluator.runEval (/Users/xxxxx/.npm/_npx/81bbc6515d992ace/node_modules/promptfoo/dist/src/evaluator.js:273:62)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async processEvalStep (/Users/xxxx/.npm/_npx/81bbc6515d992ace/node_modules/promptfoo/dist/src/evaluator.js:601:25)
Any help with resolving this would be greatly appreciated!

Fixed in 0.63.1!


Benchmark cache refactoring; minimize regressions

Test the changes made in https://github.com/azavea/raster-foundry/pull/2296 with a repeatable set of requests via JMeter. Ensure that we see better performance with caching enabled. Ensure that there aren't any glaring regressions with existing projects.


Feature: add ability for checkbox element to comply with isRequired.

When a checkbox question is set as isRequired, user has to at least check one box for the question.

Our team was just having this conversation. We weren't 100% sure what the behavior for isRequired on a checkbox would look like, but assumed that it means that at least one box must be checked for it to validate.

Our team was just having this conversation. We weren't 100% sure what the behavior for isRequired on a checkbox would look like, but assumed that it means that at least one box must be checked for it to validate. We would maybe need to see how required checkboxes on the officially supported web frameworks behave and mimic this behavior.

This is probably best evaluated together with issue #33 . Here's what I've found out based on the JS version of survey.js:

When hasSelectAll is enabled, either this "select-all" choice is checked (which means all regular choices are checked) or any other choices are checked, the isRequired validation is passed;
When hasNone is enabled, either this "none" choice is checked (which means all regular choices are unchecked) or any other choices are checked, the isRequired validation is passed;
When hasOther is enabled, either this "other" choice is checked (which means a corresponding input box would show up) and additional input is provided, or any other choices are checked, the isRequired validation is passed;
When hasOther is enabled, and this "other" choice is checked, but the user hasn't yet provided additional text for the corresponding input box, the isRequired validation is not passed.

The core problem, I think, is with RequiredValidator from reactive_forms, which only marks null values and empty strings as errors, and would happily accept empty lists and maps. I've filed an issue over there https://github.com/joanpablo/reactive_forms/issues/377 . Until that gets resolved, we could have a workaround by leveraging a custom validator.
A PR is underway that provides this workaround. Next I'll see what to do with issue #33.

Currently the isRequired for checkbox element is effective in the sense that it will prevent the containing form from being submitted if the value is empty. Yet there isn't any errorText being displayed. The problem is likely due to the difference between standalone reactive form widgets and arrays of widgets. Maybe there is a way to wire up a errorText at the question level that is properly propagated by validators?


fix: eslint warning and remove dist added to eslintignore

What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix
[ ] New feature
[ X ] Other, please explain: eslint
What changes did you make? (Give an overview)
fix eslint warning and remove dist added to eslintignore
Which issue (if any) does this pull request address?

Is there anything you'd like reviewers to focus on?

@all-contributors add @niexq for infrastructure


Good information, but...

It doesn't belong here. The Azure AD join process is not unique to Hello for Business, and no one would ever look for it here. This belongs in a section dedicated to Windows (and Azure) authentication and user/device identity, such as https://docs.microsoft.com/en-us/azure/active-directory/devices/ , although that section is woefully incomplete as well. This should also be combined with the section on windows authentication here https://docs.microsoft.com/en-us/windows/win32/secauthn/authentication-portal and here https://docs.microsoft.com/en-us/windows-server/security/windows-authentication/windows-logon-scenarios, as well as a host of other tidbits you've got squirreled away, to make clear and complete description of how the components of authentication and credentialing work together in the modern age of Azure and Windows 10. It's a nice story. You're not doing yourselves any good by hiding it.

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

ID: 96185909-5825-db9a-cc04-4045f6dc577e
Version Independent ID: 9340a575-af61-9c73-7701-702fff99f524
Content: How Windows Hello for Business works - Device Registration - Microsoft 365 Security
Content Source: windows/security/identity-protection/hello-for-business/hello-how-it-works-device-registration.md
Product: w10
Technology: windows
GitHub Login: @mapalko
Microsoft Alias: mapalko

@upmyoung can you clarify your feedback on https://docs.microsoft.com/en-us/windows/win32/secauthn/authentication-portal and here https://docs.microsoft.com/en-us/windows-server/security/windows-authentication/windows-logon-scenarios? Is the ask to include general WHFB authentication information on these pages?
Those changes are unrelated from your feedback to move the device registration diagrams, correct?

@upmyoung Closing because there hasn't been any response from your side regarding details of the defect in the documentation. Feel free to re-open to follow up. Thank you, and stay healthy.


Extract install logic to a apache_org_install cookbook

The pattern of installing apache_org java apps should probably be extracted into its own cookbook so we can use it in other places like activemq.

Hi,
Sous-Chefs have just taken over this cookbook and are currently baselining issues, if you think this issue is still relevant please re-open it
Thanks!


Mobile app binary details

The app binary screen in openshift (where the user can download the binary) could should some extra details about the application binary, such as certificate info, alias, etc (some data are platform specific).
Android
Command:
unzip -p myapp.apk META-INF/CERT.RSA | keytool -printcert

The command's output should be something like this:
Owner: CN=asdf, OU=asdf, O=asdf, L=asdf, ST=asdf, C=asdf
Issuer: CN=asdf, OU=asdf, O=asdf, L=asdf, ST=asdf, C=asdf
Serial number: ...
Valid from: Mon Sep 11 17:46:20 BRT 2017 until: Sun Dec 10 18:46:20 BRST 2017
Certificate fingerprints:
	 MD5:  ...
	 SHA1: ...
	 SHA256: ...
	 Signature algorithm name: SHA256withRSA
	 Version: 3

Extensions:

#1: ObjectId: <IP_ADDRESS> Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
...
]
]

The most relevant fields in my opinion are: Owner, Issuer, Signature algorithm name, Valid from and Valid until.
iOS
Unfortunately this command has to be run in a mac machine:
codesign -vvvv -d somefile.app

The command's output should be something like this:
Executable=build_path/saml-ios-swift.app/saml-ios-swift
Identifier=com.feedhenry.saml-ios-swift
Format=app bundle with Mach-O universal (armv7 arm64)
CodeDirectory v=20200 size=1692 flags=0x0(none) hashes=45+5 location=embedded
OSPlatform=37
OSSDKVersion=656128
OSVersionMin=524288
Hash type=sha256 size=32
CandidateCDHash sha1=...
CandidateCDHash sha256=...
Hash choices=sha1,sha256
Page size=4096
CDHash=...
Signature size=4680
Authority=iPhone Distribution: Red Hat
Authority=Apple Worldwide Developer Relations Certification Authority
Authority=Apple Root CA
Signed Time=Sep 25, 2017, 11:45:26 AM
Info.plist entries=30
TeamIdentifier=...
Sealed Resources version=2 rules=13 files=49
Internal requirements count=1 size=180

I personally think the most important items are: Identifier (all of them), Authority, TeamIdentifier and Signed Time

@odra This information seems useful. However it seems like something that should be done as a step in pipeline on Jenkins? Once done this information could then be exposed in some manner to the MCP server. I think there is quite a bit to consider with this, but a good starting place would be how to get this info after a build as part of the normal build pipeline and then expose it from Jenkins (perhaps as a build artefact)?

I think we could add a step in the pipeline where it runs those commands saving the output to a file then this could could be archived as well once the build finishes to be later retrieved from jenkins by mcp.


Update MD file on new branch 2017-18-17_03-11-55

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

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


Failure on make command

When running make I get the following errors:
mkdir -p Obj
g++ -g -std=c++11 -c EGaussian.cpp  -o Obj/EGaussian.o
In file included from EGaussian.h:45,
                 from EGaussian.cpp:30:
solverstate.h: In member function ‘dret SolverState::has_backtracked()’:
solverstate.h:131:59: error: invalid conversion from ‘const clingo_assignment_t*’ {aka ‘const clingo_assignment*’} to ‘clingo_assignment_t*’ {aka ‘clingo_assignment*’} [-fpermissive]
         decision_level = clingo_assignment_decision_level(values);
                                                           ^~~~~~
In file included from solverstate.h:30,
                 from EGaussian.h:45,
                 from EGaussian.cpp:30:
/usr/include/clingo.h:930:90: note:   initializing argument 1 of ‘uint32_t clingo_assignment_decision_level(clingo_assignment_t*)’
 CLINGO_VISIBILITY_DEFAULT uint32_t clingo_assignment_decision_level(clingo_assignment_t *assignment);
                                                                     ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
In file included from EGaussian.h:45,
                 from EGaussian.cpp:30:
solverstate.h:145:40: error: invalid conversion from ‘const clingo_assignment_t*’ {aka ‘const clingo_assignment*’} to ‘clingo_assignment_t*’ {aka ‘clingo_assignment*’} [-fpermissive]
             clingo_assignment_decision(values, level, &decision_literal);
                                        ^~~~~~
In file included from solverstate.h:30,
                 from EGaussian.h:45,
                 from EGaussian.cpp:30:
/usr/include/clingo.h:955:80: note:   initializing argument 1 of ‘bool clingo_assignment_decision(clingo_assignment_t*, uint32_t, clingo_literal_t*)’
 CLINGO_VISIBILITY_DEFAULT bool clingo_assignment_decision(clingo_assignment_t *assignment, uint32_t level, clingo_literal_t *literal);
                                                           ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
In file included from EGaussian.h:45,
                 from EGaussian.cpp:30:
solverstate.h: In member function ‘dret SolverState::get_assignment(clingo_propagate_control_t*, PackedRow*, PackedRow*, std::vector<unsigned int>)’:
solverstate.h:171:58: error: invalid conversion from ‘const clingo_assignment_t*’ {aka ‘const clingo_assignment*’} to ‘clingo_assignment_t*’ {aka ‘clingo_assignment*’} [-fpermissive]
         is_total_assignment = clingo_assignment_is_total(values);
                                                          ^~~~~~
In file included from solverstate.h:30,
                 from EGaussian.h:45,
                 from EGaussian.cpp:30:
/usr/include/clingo.h:1000:80: note:   initializing argument 1 of ‘bool clingo_assignment_is_total(clingo_assignment_t*)’
 CLINGO_VISIBILITY_DEFAULT bool clingo_assignment_is_total(clingo_assignment_t *assignment);
                                                           ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
In file included from EGaussian.h:45,
                 from EGaussian.cpp:30:
solverstate.h:179:9: error: ‘clingo_assignment_trail_size’ was not declared in this scope
         clingo_assignment_trail_size(values, &new_trail_size);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:179:9: note: suggested alternative: ‘clingo_assignment_max_size’
         clingo_assignment_trail_size(values, &new_trail_size);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
         clingo_assignment_max_size
solverstate.h:184:17: error: ‘clingo_assignment_trail_at’ was not declared in this scope
                 clingo_assignment_trail_at(values, trail_at, &lit);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:184:17: note: suggested alternative: ‘clingo_assignment_is_total’
                 clingo_assignment_trail_at(values, trail_at, &lit);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~
                 clingo_assignment_is_total
solverstate.h:209:17: error: ‘clingo_assignment_trail_begin’ was not declared in this scope
                 clingo_assignment_trail_begin(values, level_at, &offset_start);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:209:17: note: suggested alternative: ‘clingo_assignment_truth_value’
                 clingo_assignment_trail_begin(values, level_at, &offset_start);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                 clingo_assignment_truth_value
solverstate.h:210:17: error: ‘clingo_assignment_trail_end’ was not declared in this scope
                 clingo_assignment_trail_end(values, level_at, &offset_end);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:210:17: note: suggested alternative: ‘clingo_assignment_size’
                 clingo_assignment_trail_end(values, level_at, &offset_end);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~
                 clingo_assignment_size
solverstate.h:223:21: error: ‘clingo_assignment_trail_at’ was not declared in this scope
                     clingo_assignment_trail_at(values, trail_at, &lit);
                     ^~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:223:21: note: suggested alternative: ‘clingo_assignment_is_total’
                     clingo_assignment_trail_at(values, trail_at, &lit);
                     ^~~~~~~~~~~~~~~~~~~~~~~~~~
                     clingo_assignment_is_total
solverstate.h:258:17: error: ‘clingo_assignment_trail_begin’ was not declared in this scope
                 clingo_assignment_trail_begin(values, level_at, &offset_start);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:258:17: note: suggested alternative: ‘clingo_assignment_truth_value’
                 clingo_assignment_trail_begin(values, level_at, &offset_start);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                 clingo_assignment_truth_value
solverstate.h:259:17: error: ‘clingo_assignment_trail_end’ was not declared in this scope
                 clingo_assignment_trail_end(values, level_at, &offset_end);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:259:17: note: suggested alternative: ‘clingo_assignment_size’
                 clingo_assignment_trail_end(values, level_at, &offset_end);
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~
                 clingo_assignment_size
solverstate.h:272:21: error: ‘clingo_assignment_trail_at’ was not declared in this scope
                     clingo_assignment_trail_at(values, trail_at, &lit);
                     ^~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:272:21: note: suggested alternative: ‘clingo_assignment_is_total’
                     clingo_assignment_trail_at(values, trail_at, &lit);
                     ^~~~~~~~~~~~~~~~~~~~~~~~~~
                     clingo_assignment_is_total
solverstate.h: In member function ‘bool SolverState::is_assignment_conflicting(clingo_propagate_control_t*)’:
solverstate.h:342:47: error: invalid conversion from ‘const clingo_assignment_t*’ {aka ‘const clingo_assignment*’} to ‘clingo_assignment_t*’ {aka ‘clingo_assignment*’} [-fpermissive]
         return clingo_assignment_has_conflict(values);
                                               ^~~~~~
In file included from solverstate.h:30,
                 from EGaussian.h:45,
                 from EGaussian.cpp:30:
/usr/include/clingo.h:935:84: note:   initializing argument 1 of ‘bool clingo_assignment_has_conflict(clingo_assignment_t*)’
 CLINGO_VISIBILITY_DEFAULT bool clingo_assignment_has_conflict(clingo_assignment_t *assignment);
                                                               ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
In file included from EGaussian.h:45,
                 from EGaussian.cpp:30:
solverstate.h: In member function ‘bool SolverState::add_initial_clause(std::vector<int>)’:
solverstate.h:444:14: error: ‘clingo_propagate_init_add_clause’ was not declared in this scope
         if (!clingo_propagate_init_add_clause(cpi, new_clause, 1, &result)) { return false; }
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:444:14: note: suggested alternative: ‘clingo_propagate_init_add_watch’
         if (!clingo_propagate_init_add_clause(cpi, new_clause, 1, &result)) { return false; }
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              clingo_propagate_init_add_watch
solverstate.h:447:14: error: ‘clingo_propagate_init_propagate’ was not declared in this scope
         if (!clingo_propagate_init_propagate(cpi, &result)) { return false; }
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:447:14: note: suggested alternative: ‘clingo_propagate_control_propagate’
         if (!clingo_propagate_init_propagate(cpi, &result)) { return false; }
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              clingo_propagate_control_propagate
solverstate.h:455:43: error: invalid conversion from ‘const clingo_assignment_t*’ {aka ‘const clingo_assignment*’} to ‘clingo_assignment_t*’ {aka ‘clingo_assignment*’} [-fpermissive]
             clingo_assignment_truth_value(values, *start_literal, &value);
                                           ^~~~~~
In file included from solverstate.h:30,
                 from EGaussian.h:45,
                 from EGaussian.cpp:30:
/usr/include/clingo.h:985:83: note:   initializing argument 1 of ‘bool clingo_assignment_truth_value(clingo_assignment_t*, clingo_literal_t, clingo_truth_value_t*)’
 CLINGO_VISIBILITY_DEFAULT bool clingo_assignment_truth_value(clingo_assignment_t *assignment, clingo_literal_t literal, clingo_truth_value_t *value);
                                                              ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
In file included from EGaussian.h:45,
                 from EGaussian.cpp:30:
solverstate.h: In member function ‘bool SolverState::make_unsat()’:
solverstate.h:481:14: error: ‘clingo_propagate_init_add_clause’ was not declared in this scope
         if (!clingo_propagate_init_add_clause(cpi, new_clause, 0, &result)) { return false; }
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:481:14: note: suggested alternative: ‘clingo_propagate_init_add_watch’
         if (!clingo_propagate_init_add_clause(cpi, new_clause, 0, &result)) { return false; }
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              clingo_propagate_init_add_watch
solverstate.h:484:14: error: ‘clingo_propagate_init_propagate’ was not declared in this scope
         if (!clingo_propagate_init_propagate(cpi, &result)) { return false; }
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
solverstate.h:484:14: note: suggested alternative: ‘clingo_propagate_control_propagate’
         if (!clingo_propagate_init_propagate(cpi, &result)) { return false; }
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              clingo_propagate_control_propagate
Makefile:57: recipe for target 'Obj/EGaussian.o' failed
make: *** [Obj/EGaussian.o] Error 1

I'm not sure how to proceed, any help is appreciated, thanks.

Hi,
It seems that it is not getting "clingo.h. Or the clingo version is not latest. We used clingo version 5.5.
Could you please check whether you can import library "clingo.h"? For example, we can try to run some examples from here.

Thanks! I installed clingo 5.5 but when I would run the example C programs, they would still use version 5.3 for some reason (gcc -o version version.c -lclingo still used version 5.3, though gcc -o version version.c L/usr/local/lib -lclingo used 5.5).  It turns out that when I called make, 5.3 was being used. Resolving this library issue fixed it.


Add Counter Groups for Sorting counted things by count

If a set of Counters belongs to a given "group" or "tag", then we can create an index of all the counts for the counters in a given group, and query the datastore for ordered lists of counters.  In this way, we can enable leaderboard-type activity.
For example, if there are N number of counters tracking follower counters (i.e., one counter per user being followed) then we could add each of these counters to the "follower" group.  Next, we could query the counter service for the "most followed" or "least followed" users by getting an ordered list of counters in the "follower" group.

See issue #3 when implementing this feature.  The CounterGroup contains a surrogate field for tracking the counter's counter in an "eventually consistent" manner.

This is implemented via the commits for issue #18.  See issue #19 for the final pieces to enable this feature.


Improve performance in FE

Check performance bottleneck - in FE.

@sa-lo-mon can you take this issue?


fix: worker-build not working on windows

I gave your change a whirl on my local as I'm a Windows user, and have been struggling to build a worker.
wasm-pack wouldn't install due to openssl, but I worked around that via the provided installer at https://rustwasm.github.io/wasm-pack/installer/.
Next up was worker-build not finding that version of wasm-pack. I tried this change, but it still doesn't manage to find it.
Since I know my local is installed, I ended up just forcing the function to return Ok(()) for now to get things rolling.

I gave your change a whirl on my local as I'm a Windows user, and have been struggling to build a worker.
wasm-pack wouldn't install due to openssl, but I worked around that via the provided installer at https://rustwasm.github.io/wasm-pack/installer/.
Next up was worker-build not finding that version of wasm-pack. I tried this change, but it still doesn't manage to find it.
Since I know my local is installed, I ended up just forcing the function to return Ok(()) for now to get things rolling.

Sadly OpenSSL's weirdness is out of scope for this PR, you probably need to use vc-pkg to get the OpenSSL headers so it can be build via Cargo. That's what I did and it was worked fine.

I agree that's out of scope, just wanted to voice that bit of frustration :)
But I did want to let you know that even with this change, worker-builder still cannot find wasm-pack on my Windows machine.

@devnought I'm having issues with this now. How did you manage to get it to work?


First time running tests.  Commented out lines that cause Cypress tes…

…ts to fail on unmerged Twilio code.
VA-66

Contributing to Twilio

All third party contributors acknowledge that any contributions they provide will be made under the same open source license that the open source project is provided under.

[ ] I acknowledge that all my contributions will be made under the project's license.

Pull Request Details
JIRA link(s):

AHOYAPPS-0000

Description
A description of what this PR does.
Burndown
Before review

[ ] Updated CHANGELOG.md if necessary
[ ] Added unit tests if necessary
[ ] Updated affected documentation
[ ] Verified locally with npm test
[ ] Manually sanity tested running locally
[ ] Included screenshot as PR comment (if needed)
[ ] Ready for review

Before merge

[ ] Got one or more +1s
[ ] Re-tested if necessary

@RPort71 did you mean to create a PR into eScribers:master instead of twilio:master?


Can you run multiple action groups with this solution?

It is possible to run multiple schedules, but is it also possible to create an action group for a specific schedule?
So for 1 set of VM's only the corresponding action group is triggered?

@arijnbeek - Currently 1 logic app is associated for 1 schedule and with 1 payload structure. If you need multiple then you can clone the logic app (probably rename it for better and easy identification) and configure the schedule with the different VM's.

Any further updates on this?

I managed to create 2 more action rules with custom query's and each there own action group and scheduled logic app.

Great. Glad that it worked for you!


RuntimeError: unscale_() has already been called on this optimizer since the last update().

I'm trying to train a lora with multiple embeddings, but I keep getting this error. I have tried to change a bunch of stuff in the YAML configuration to see if I could get any futher, but I haven't been able to get past this error. Any ideas on what is going wrong?
Contents of hcp-test folder: settings.zip

PS R:\lora-test\hcp-test> accelerate launch -m hcpdiff.train_ac_single --cfg .\lora_anime_character.yaml
bin F:\python\lib\site-packages\bitsandbytes\libbitsandbytes_cuda117.dll
The following values were not passed to accelerate launch and had defaults used instead:
--num_processes was set to a value of 1
--num_machines was set to a value of 1
--mixed_precision was set to a value of 'no'
--dynamo_backend was set to a value of 'no'
To avoid this warning pass in values for each of the problematic parameters or run accelerate config.
bin F:\python\lib\site-packages\bitsandbytes\libbitsandbytes_cuda117.dll
F:\python\lib\runpy.py:126: RuntimeWarning: 'hcpdiff.train_ac_single' found in sys.modules after import of package 'hcpdiff', but prior to execution of 'hcpdiff.train_ac_single'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
2023-11-13 01:24:24.563 | INFO     | hcpdiff.loggers.cli_logger:_info:30 - world_size: 1
2023-11-13 01:24:24.563 | INFO     | hcpdiff.loggers.cli_logger:_info:30 - accumulation: 1
You are using a model of type clip_text_model to instantiate a model of type . This is not supported for all configurations of models and can yield errors.
2023-11-13 01:24:28.321 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: black_san_magnolia, len: 4, id: 49408
2023-11-13 01:24:28.322 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: bloody_reina, len: 2, id: 49409
2023-11-13 01:24:28.322 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: blue_san_magnolia, len: 4, id: 49410
2023-11-13 01:24:28.322 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: formal_giad, len: 4, id: 49411
2023-11-13 01:24:28.322 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: neck_scar, len: 2, id: 49412
2023-11-13 01:24:28.323 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: personal_room, len: 4, id: 49413
2023-11-13 01:24:28.323 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: shinei_nouzen, len: 3, id: 49414
2023-11-13 01:24:28.323 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: undertaker, len: 4, id: 49415
2023-11-13 01:24:28.323 | INFO     | hcpdiff.models.text_emb_ex:hook:86 - hook: vladilena_millize, len: 3, id: 49416
A matching Triton is not available, some optimizations will not be enabled.
Error caught was: No module named 'triton'
2023-11-13 01:24:29.182 | INFO     | hcpdiff.data.caption_loader:load:18 - 144 record(s) loaded with TXTCaptionLoader, from path 'L:/waifu_diffusion/anime-tagger/out/86/512x512'
2023-11-13 01:24:29.183 | INFO     | hcpdiff.data.bucket:build_buckets_from_images:241 - build buckets from images size
F:\python\lib\site-packages\sklearn\cluster_kmeans.py:1412: FutureWarning: The default value of n_init will change from 10 to 'auto' in 1.4. Set the value of n_init explicitly to suppress the warning
super()._check_params_vs_input(X, default_n_init=10)
2023-11-13 01:24:29.632 | INFO     | hcpdiff.data.bucket:build_buckets_from_images:262 - buckets info: size:[512 512], num:144
2023-11-13 01:24:29.666 | INFO     | hcpdiff.loggers.cli_logger:_info:30 - len(train_dataset): 144
F:\python\lib\site-packages\diffusers\pipelines\stable_diffusion\pipeline_stable_diffusion.py:128: FutureWarning: The configuration file of this scheduler: PNDMScheduler {
"_class_name": "PNDMScheduler",
"_diffusers_version": "0.19.3",
"beta_end": 0.012,
"beta_schedule": "scaled_linear",
"beta_start": 0.00085,
"num_train_timesteps": 1000,
"prediction_type": "epsilon",
"set_alpha_to_one": false,
"skip_prk_steps": false,
"steps_offset": 0,
"timestep_spacing": "leading",
"trained_betas": null
}
is outdated. steps_offset should be set to 1 instead of 0. Please make sure to update the config accordingly as leaving steps_offset might led to incorrect results in future versions. If you have downloaded this checkpoint from the Hugging Face Hub, it would be very nice if you could open a Pull request for the scheduler/scheduler_config.json file
deprecate("steps_offset!=1", "1.0.0", deprecation_message, standard_warn=False)
2023-11-13 01:24:30.572 | INFO     | hcpdiff.loggers.cli_logger:_info:30 - ***** Running training *****
2023-11-13 01:24:30.572 | INFO     | hcpdiff.loggers.cli_logger:_info:30 -   Num batches each epoch = 144
2023-11-13 01:24:30.573 | INFO     | hcpdiff.loggers.cli_logger:_info:30 -   Num Steps = 1000
2023-11-13 01:24:30.573 | INFO     | hcpdiff.loggers.cli_logger:info:30 -   Instantaneous batch size per device = 1
2023-11-13 01:24:30.573 | INFO     | hcpdiff.loggers.cli_logger:info:30 -   Total train batch size (w. parallel, distributed & accumulation) = 1
2023-11-13 01:24:30.573 | INFO     | hcpdiff.loggers.cli_logger:info:30 -   Gradient Accumulation steps = 1
bin F:\python\lib\site-packages\bitsandbytes\libbitsandbytes_cuda117.dll
F:\python\lib\runpy.py:126: RuntimeWarning: 'hcpdiff.train_ac_single' found in sys.modules after import of package 'hcpdiff', but prior to execution of 'hcpdiff.train_ac_single'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
bin F:\python\lib\site-packages\bitsandbytes\libbitsandbytes_cuda117.dll
F:\python\lib\runpy.py:126: RuntimeWarning: 'hcpdiff.train_ac_single' found in sys.modules after import of package 'hcpdiff', but prior to execution of 'hcpdiff.train_ac_single'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
bin F:\python\lib\site-packages\bitsandbytes\libbitsandbytes_cuda117.dll
F:\python\lib\runpy.py:126: RuntimeWarning: 'hcpdiff.train_ac_single' found in sys.modules after import of package 'hcpdiff', but prior to execution of 'hcpdiff.train_ac_single'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
bin F:\python\lib\site-packages\bitsandbytes\libbitsandbytes_cuda117.dll
F:\python\lib\runpy.py:126: RuntimeWarning: 'hcpdiff.train_ac_single' found in sys.modules after import of package 'hcpdiff', but prior to execution of 'hcpdiff.train_ac_single'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
F:\python\lib\site-packages\hcpdiff\train_ac.py:425: FutureWarning: Accessing config attribute scaling_factor directly via 'AutoencoderKL' object attribute is deprecated. Please access 'scaling_factor' over 'AutoencoderKL's config object instead, e.g. 'unet.config.scaling_factor'.
latents = latents*self.vae.scaling_factor
F:\python\lib\site-packages\torch\utils\checkpoint.py:31: UserWarning: None of the inputs have requires_grad=True. Gradients will be None
warnings.warn("None of the inputs have requires_grad=True. Gradients will be None")
Traceback (most recent call last):
File "F:\python\lib\runpy.py", line 196, in run_module_as_main
return run_code(code, main_globals, None,
File "F:\python\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "F:\python\lib\site-packages\hcpdiff\train_ac_single.py", line 61, in
trainer.train()
File "F:\python\lib\site-packages\hcpdiff\train_ac.py", line 391, in train
loss = self.train_one_step(data_list)
File "F:\python\lib\site-packages\hcpdiff\train_ac.py", line 481, in train_one_step
self.accelerator.clip_grad_norm(clip_param, self.cfgs.train.max_grad_norm)
File "F:\python\lib\site-packages\accelerate\accelerator.py", line 1916, in clip_grad_norm
self.unscale_gradients()
File "F:\python\lib\site-packages\accelerate\accelerator.py", line 1879, in unscale_gradients
self.scaler.unscale(opt)
File "F:\python\lib\site-packages\torch\cuda\amp\grad_scaler.py", line 275, in unscale
raise RuntimeError("unscale() has already been called on this optimizer since the last update().")
RuntimeError: unscale() has already been called on this optimizer since the last update().
Traceback (most recent call last):
File "F:\python\lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "F:\python\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "F:\python\Scripts\accelerate.exe_main.py", line 7, in
File "F:\python\lib\site-packages\accelerate\commands\accelerate_cli.py", line 45, in main
args.func(args)
File "F:\python\lib\site-packages\accelerate\commands\launch.py", line 959, in launch_command
simple_launcher(args)
File "F:\python\lib\site-packages\accelerate\commands\launch.py", line 624, in simple_launcher
raise subprocess.CalledProcessError(returncode=process.returncode, cmd=cmd)
subprocess.CalledProcessError: Command '['F:\python\python.exe', '-m', 'hcpdiff.train_ac_single', '--cfg', '.\lora_anime_character.yaml']' returned non-zero exit status 1.

After upgrading the accelerate package (which didn't work), upgrading the hcpdiff package (which gave a new error), and running hcpinit again, it is now doing something.


Can't invoke addAction(_:style:handler) on ActionSheet instance

When trying to invoke addAction on ActionSheet class instance with parameters title, style and handler, Xcode reports:

Ambiguous use of addAction(_:style:handler)

ActionSheet().addAction("Test", style: .Default, handler: { _ in print("Test") }).show()
I've tried to use LKAlertController instance and it works:
LKAlertController(style: .ActionSheet).addAction("Test", style: .Default, handler: { _ in print("Test") }).show()

Thanks for creating the issue. I've added a test for this issue and updated the code handle it


Incorrect metrics when filtering certain page paths

I've noticed that selecting an index path without a trailing slash (e.g. /some-page) from the 'Pages' section, seems to always return 0 for all results even though the section shows views for that page:

From what I've seen so far, it looks as though the api returns valid results for requests where the url parameter points to a file or to a path with a trailing slash (e.g. /some-page.html, /, /some-page/).

Closing this. Will track in #606


Added the default transparent greyed out background to GuiScreen's.

Added the default transparent greyed out background to the
GuiPasswordEnter and GuiPasswordModify GuiScreen's.

@aidancbrady Did you understand what i meant here? Since the GuiScreen is the base class of GuiContainer which is used for every other GUI than GuiPassword* the GuiContainer class has this greyed out background, but this is because of this missing from the GuiPassword* classes that derive directly from GuiScreen.

Great, thanks.


Implement the Tudor crown in the Header component (v3.x)

Cherry pick the changes from #4278 onto the v3 support branch. See #4278 for a list of changes.

[!WARNING]
This PR should not be merged until we have approval to do so.

Merging in preparation for release w/c 15th January.


samples: subsys: usb: mass: add support for Adafruit feather nRF52840

Add configuration and overlay files for Adafruit feather nRF52840.
README has also been updated and improved. Documentation related to
littlefs has been moved to an independent section as it could apply to
any sample.
Signed-off-by: Gerard Marull-Paretas<EMAIL_ADDRESS>

This is just another combination.

I'm sympathetic to that view.  I decided that SPI+FatFs was likely more common that SPI+littlefs so it was worth adding it.  Also separating out the littlefs mount instructions from the board-specific sample makes sense and improves things.
There certainly should be a limit to how many variations are explicitly supported in a sample, but where that limit should be enforced is not clear.

@nashif @MaureenHelm @carlescufi @pabigot We already have an overlay for nRF (nRF52840) platform and SPI flash in the sample. This is just another combination. Do we really want to have overlays and a separate chapter in the documentation for all possible combinations? I think we should limit it, if it is not generic enough there should be only one example per platform.

I sort of disagree. This is all contained in a boards/ folder, and as far as the documentation goes, we can always try to find a format that is more compact to display all the pre-provided configurations for several boards.


Replace nipype ants interfaces with antspy?

I've recently had the pleasure of working with antspy. It's fast and the API is both straightforward and flexible. I wonder whether we should use this directly in the estimator module, instead of the nipype interface. Benefits include the fact that it's a pip install, so we would remove a pretty heavy dependency (and for many users, the docker dependency!).

This is a good place to start: https://github.com/nipreps/eddymotion/blob/main/src/eddymotion/estimator.py#L119


Cross Resource Referencing design doc

Signed-off-by: soorena776<EMAIL_ADDRESS>
Description of your changes

Fixes #707
Child of #631
Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[x] Updated any relevant documentation, examples, or release notes.
[ ] Updated the RBAC permissions in clusterrole.yaml to include any new types.

I'm really glad we are tackling this. On my first read of this, I'm not sure I follow why "resolving dependencies" is done at the golang interface level, vs. at the Kubernetes API level. Are we assuming that if r1 depends on r2, that the code for r1 and r2 live in the same stack?
I was assuming that dependency resolution would be done at the Kubernetes API level, similar to say how a Pod might depend on a Secret and the Pod will not be started until the Secret exists. This relationship is not handled through an interface between Pod and Secret but instead by the Pod controller watching for the availability ("resolution") of the Secret via watchers/informers.
Maybe I'm missing something fundamental here, but I think we would want to support dependency resolution across independently authored stacks.

@bassam TL;DR the golang interface mention is just an implementation detail, and this work is in Kubernetes API level.
Long version: we could have a meeting to discuss this.

On my first read of this, I'm not sure I follow why "resolving dependencies" is done at the golang interface level, vs. at the Kubernetes API level. Are we assuming that if r1 depends on r2, that the code for r1 and r2 live in the same stack?

I think it may not be clear that we are modeling dependencies at the Kubernetes API level, i.e. vpcIdRef is essentially (or perhaps exactly) a LocalObjectReference as is the common pattern in Kubernetes APIs. The talk of Go interfaces is because sometimes (assuming r1 is a managed resource and e1 is its external resource) we'll need to teach the controller for r1 to translate the referenced r2 resource into the field value e1 requires.
In most cases this interface would simply return the value of the one field of r2 we're concerned with. In others it might have to merge 2-3 fields of r2 to form the value expected by e1's API, for example /projects/projectname/regions/${r2-region-field}/widgets/${r2-widget-field}.

This relationship is not handled through an interface between Pod and Secret but instead by the Pod controller watching for the availability ("resolution") of the Secret via watchers/informers.

I imagine the Pod still needs some knowledge of how a Secret works in order to turn the reference into what it needs to know about the Secret.

https://crossplane.slack.com/archives/CKXQHM7U3/p1570225004276800
Quoting @soorena776  from the above Slack discussion:

I am thinking to modify the managed reconciler in crossplane-runtime, and add ResolveDep stage to the set of existing four stages, to have {Observe, ResolveDep, Create, Update, Delete} set. ResolveDep will check to see if any of the type fields are of interface type ReferenceResolver, and if so resolves them or gets rescheduled. Once a reference field is resolved, its value will be stored in the equivalent non Ref field, and reconciler proceeds to the next (e.g. Create) stage.

I like the idea of having a distinct 'resolve deps' stage, but on reflection I'm a little reluctant to make it part of the ExternalClient interface. The separation of concerns in the managed resource reconciler was designed such that the ExternalClient doesn't need a Kubernetes client, but rather takes a fully formed spec and acts on it. This separation is blurred only in the GCP GlobalAddress controller, whose ExternalClient includes a Kubernetes client in order to enable "late initialization" of spec variables.
If we do need to add a ResolveDep stage to ExternalClient I strongly encourage naming it Link or LinkDeps to fulfill my dream of the ExternalClient handling CLOUD operations (as opposed to CRUD operations. ;)

@negz
This morning when I started writing code in the managed reconciler, I realized such ResolveDep is really not necessary, if we could heavily rely on golang's reflect library.


Error response from daemon: manifest for fermenreq/docker-whale:latest not found

Hi all !
I'm trying to download an image that I have in Docker Repository, but I have a response error :
root@fernandotest:/# docker pull fermenreq/docker-whale
Using default tag: latest
Error response from daemon: manifest for fermenreq/docker-whale:latest not found
Im using an Ubuntu 14.04 Image Running on a fiware cloud VM. Requierements docker
I'm working on Windows 7 Enterprise and I connect to VM using cygwin.
Bests regards ! ****

Adding the tagname had no effect.  Same error.

As for me, there are a huge problem with registry, when it ghostly fails and you could only update it, clean up orphaned images or push fresh commit.


fix(cc): update SceneControllerConfigurationCC API for get / getLastActivated

This PR updates the SceneControllerConfigurationCC API to follow the decisions we made while working on the SceneActuatorConfigurationCC API.
I also applied a few of the other refinements:

Set no longer schedules a Poll.
PhysicalCCAPI was changed to CCAPI, because the Set command is allowed to be part of a Multicast. (and related changes)
Prevented Reports with groupId = 0 from being persisted.

1. Set no longer schedules a Poll.

Forgot to push that?

1. Set no longer schedules a Poll.

Forgot to push that?

I think I just missed that I was polling in both the SET_VALUE and set() functions.  I did an actual search this time.


fix(tokenize): fix list index out of range by swapping dataset

Fix #314 .
This is only a workaround. The other workaround is to point to the exact file path, but I find this solution a bit cleaner.
It's still unclear on why this problem exists for falcon+pythia, but ok for llama.

Should we just merge this? Teknium might be busy to fix his dataset. Using a simple 2k dataset also simplifies testing for others.

superseded by #395


Non-promise functions are not executed locally

When using functions invoke.

This is now fixed in the latest alpha.


remove unnecessary assert from scroll_view.dart

Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].

after migrating flutter to null safety there is no need to to assert if value of a parameter is null when the parameter have a defult value or  non-nullable !
also assert will work on debug only still there is no need for them any more

Thanks for the contribution. Some apps using Flutter have not migrated to null safety and that's why we want to keep these assertions around for the time being.


Integrate EIA 861 into PUDL ETL

861 is partially integrated into our output layer but should be integrated into our main ETL process. This is currently blocked by our Harvesting update.

Depending on what boundaries we put around it, this epic may be worth turning into a Project.

Can this be closed?

Probably this should be closed, but the EIA-861 remains incompletely integrated -- we haven't normalized the tables, harvested entities, or cleaned up a lot of the data, and there are definitely internal inconsistencies as a result.


Rendering components in loop severely impacts performance

Laravel Version: 9.25.1
PHP Version: 8.0.22
Database Driver & Version: MySql 8.0.27

Description:
Rendering components in loop severally impacts performance
To demonstrate this I have setup a simple test with two endpoints. They both render a list of 10000 book titles, generated from an array of strings. One endpoint uses a component to render each item in the list, the other uses a simple foreach loop on the data within the blade template.
php artisan optimize and php artisan view:cache have both been run.
Using XDebug's profiler to capture a snapshot of the requests to there two requests, I have observed the difference in time to render these is significant, with the component taking 20 times longer to render the same data;

Using component 4519ms
Using foreach 240ms

In the call stack of the component version, a huge amount of total time is spent in;
Illuminate\View\Component->resolveView() - 1251ms
Illuminate\View\Factory->renderComponent() - 1421ms
While this test is an extreme example, we are seeing in our production system a significant impacts of this slow rendering of component in a loop - which is further compounded due to nested components.
I think there probably needs to be some static caching introduced to help prevent the disk read of the component blade file on every loop, or a mention of this impact within the docs, to help guide people in when using a component is a good or bad idea.
Steps To Reproduce:

See https://github.com/AntonCooper/laravel-component-performance for test repo with the two test endpoints.
See my profiler snapshots attached
cachegrind.out.33270.gz
cachegrind.out.33269.gz

Hi there. Using loops to render components can indeed be performance intensive in some situations like your own. But view caching should greatly mitigate this. In general, only the first rendering should be an expensive operation. If you still have performance issues I suggest to look at other solutions like https://github.com/spatie/laravel-responsecache. Thanks

HI @driesvints, thanks for getting back to me so quickly.
Unfortunately the view caching does nothing to mitigate the slowness of the test I've outlined above. I can see from the stack trace that it is using the compiled blade template - but the slowness persists. It seems to be reading that rendered blade template from disk on every single loop. This seems to be the root cause of the slowness.
The test is extremely simplistic to try and demonstrate the internal overhead of trying to load components in a loop. I understand using components might have an additional overhead, but 20 times slower seems like pretty significant difference which at worst seems to be a performance issue. If it's working as designed I really feel that these performance overheads need to be stated in the docs as it will greatly influence the way which they're used within a project.

Just to add some more info to this, we saw a similar issue when using https://github.com/blade-ui-kit/blade-icons when using components.
Discussion and benchmarks here - https://github.com/blade-ui-kit/blade-icons/issues/190

Seems there is no good way of improving this. In these use cases it's probably best to use something differently than components.

Same problem here.
I have always not used components too much except in few cases, but since I've decided to use Tailwind in my new project, I thought it would be better to make components for different pieces on the website then use those components without rewriting the classes and styles everywhere again and again, but I've noticed that the performance is very bad even I'm still building the front-end, no DB queries or business logic has been written yet.
So nothing to blame except the components, then after I saw how blade compiled the views with the components, then I knew why the performance dropped to this level.
Of course I've removed most of already created components and have to copy and paste the repetitive HTML code again and again, yes bad thing to do but performance wise waaaaaay better.
I think we need a way to flatten the views not to create component instances and render them inside the compiled version, it makes no sense.

See #44480


++#[LIVE~STReam]]*OKTAGON 63: BUCHINGER vs NAFUKA LIVE  On TV Channel, 09 November 2024

FightBook MMA
OKTAGON 63 Weigh In Results: Buchinger vs. Nafuka Headliner Officially Set
Get ready for OKTAGON 63! Weigh-in results are in for Buchinger vs. Nafuka headliner. Exciting matchups await in Bratislava, Slovakia.
Oktagon MMA - Oktagon 63: Buchinger vs. Nafuka
Oktagon MMA - Oktagon 63: Buchinger vs. Nafuka pits Ivan Buki Buchinger vs Hafeni The Namibian Nightmare Nafuka fight in Tipos Arena, Bratislava,...
Ivan Buchinger
Ivan Buchinger breaking news and and highlights for Oktagon MMA fight vs. Hafeni Nafuka, with official Sherdog mixed martial arts stats, photos, videos,...
FightBook MMA
Buchinger collides with Nafuka in ‘Battle of the Generations’ at OKTAGON 63 on Saturday
Get ready for an epic 'Battle of the Generations' at OKTAGON 63 as Ivan Buchinger takes on Hafeni Nafuka in an MMA lightweight showdown.

hjh

trgytr

nmn


software template has irrelevant conditional

https://github.com/research-software-directory/frontend/blob/842ca9005e59efd67ed92d50ff5c37438613bc4e/templates/software_template.html#L158

something like a canCite: bool property seems a useful alternative.

The task that fetches the citation data from Zenodo/GitHub/cff will set this boolean in the software_cache collection..

Currently In v2 the conceptDoi is used to determine whether software is citable.

@sverhoeven: you say "Currently In v2 the conceptDoi is used to determine whether software is citable." but that should not be the case. The conceptDOI is at the beginning of the pipeline, at that point you do not know whether a software item is in fact citable. Based on the concept doi, the following happens:

get_citation_data task (either this one, or something like it) resolves the conceptDOI
verifies that is in fact a concept DOI, not a version DOI
compiles a list of github releases that existed at the time the Zenodo entry was made based on e.g. https://github.com/research-software-directory/tasks-nlesc/blob/a885f81c71bfb0bfc19fd44eb2cf55a16ce0f0ce/get_citation_data.py
culls that list by only including releases that currently exist
and cull THAT list by only including releases that have a CITATION.cff that is valid (while ignoring the commit, date-released, and doi keys found in the CITATION.cff because of reasons).

Only at the end of this processing pipeline can you determine whether the conditional (canCite or isCitable or something) is true or false.

issue is being worked on here https://github.com/research-software-directory/tasks-nlesc/commit/c2667c069bc7c3818817c0430ecbc1c1da864402


Default build failure 'copy:index.html' errored

I'm submitting a ...  (check one with "x")
[ ] Regression
[X] Bug report
[ ] Support request
[ ] Feature request
[ ] Documentation issue or request

Current behavior

Default build fails
Expected/desired behavior

Default build succeeds
Minimal reproduction of the problem with instructions

git clone https://github.com/ng-seed/universal;
cd universal;
npm install;
--yarn fails, see note below
npm run clean
--task rimraf .cache .server/server .temp public* fails to complete on its own, press enter to complete
npm run build:universal-dev
--Please see attached for full output.
Error: OpenError: IO error: /home/d/Files/Tutorial/universal/node_modules/.cache/hard-source/5a3fcea02cdebde00314c327bc24e178f36a95488abf2cff76d1c00fecbb340e/module-resolve: Invalid argument
[13:44:05] Starting 'copy:index.html'...
[13:44:05] 'copy:index.html' errored after 53 ms
[13:44:05] Error: File not found with singular glob: /home/d/Files/Tutorial/universal/public/assets/index.html
Note:
In the above, npm install was used instead of yarn as documented. This is because yarn fails with:
Error: Failed to find Electron v1.8.0 for linux-x64 at https://github.com/electron/electron/releases/download/v1.8.0/electron-v1.8.0-linux-x64.zip
This is a known issue with Electron.
What is the motivation / use case for changing the behavior?

Execute default build
Environment

Angular version: 4.4.3

Browser:

[X] Chrome (desktop) version XX
[ ] Chrome (Android) version XX
[ ] Chrome (iOS) version XX
[ ] Firefox version XX
[ ] Safari (desktop) version XX
[ ] Safari (iOS) version XX
[ ] IE version XX
[ ] Edge version XX

For Tooling issues:

Node version: 6.11.3
Platform: Linux

Others:

Operating System: CentOS Linux 7.3.1611 Core (x86-64)

In this case /home/d/Files is a CIFS mount to a Samba share with UNIX extensions enabled. Running on this share was the problem. Repeating the same steps on the local FS was successful.


process_exception method execute twice

version: 0.17.1
server code:
from django_socio_grpc.exceptions import NotFound
raise NotFound()

client result:
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNKNOWN
	details = ""
	debug_error_string = "UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:50052 {grpc_message:"", grpc_status:2, created_time:"2023-02-02T16:33:15.958708+08:00"}"

reason: process_exception repeated execute
other: version 0.16.16 is ok

Hello @ChouBaoDxs
Just to be sure. Can I reproduce this by a unit test that check that in a service after a raise NotFound() the RPC error status should be not found ?
You think the issue come from process_exception being called twhice ? Are you in sync / async ? Unary or stream ?

@ChouBaoDxs Okay so the issue was only available outside unit test and I was able to reproduce it. It come from the middleware support.
https://github.com/socotecio/django-socio-grpc/pull/137 will fix it. We just need a little bit time to understand what will be implication in potential edge case.
Will be merged soon.

@ChouBaoDxs new beta version 0.18.0b8 available with the fix.


Make subscriber to work with interface instead of traits for sortable model

TBH. what's the point of spliting properties & methods? This leads IMO to more problems than it solves...

@stloyd Well, the problem is that PHP allow override trait's methods and don't allow to override trait's properties. So when I want to redefine trait's properties, for example, to change or add some extra annotation I have a fatal error.

:+1: :+1: :+1:
@bocharsky-bw Thanks for this PR. Like said by stloyd, can you remove comments on top of traits and interfaces, or add more details in it (to make them real phpdoc) ?

@NiR- Done! Added some description in https://github.com/bocharsky-bw/DoctrineBehaviors/commit/6987d04c6b1d9eca49ae1e90c2d8330abe537c6f to all sortable traits

Seems some checks has error and I have no idea why... but it's not my fault, isn't it?

@bocharsky-bw Nope, it does not seems to be your fault :) But it will need another PR to fix those errors: some builds seem to fail due to a higher php constraints on doctrine/common:dev-master, and others due to too many requests to github API.

OK, when it'll be fixed I could rebase this PR to ensure all checks passed.


Add organizational docs

This adds the code of conduct, contributing guidelines, and organizational model to the repository. I've also added a couple of badges to the README, for flare.

Two nitpicks below. Also one possible question. Do we want to stick with markdown or switch to sphinx rst and a github pages hosted readthedocs page? The latter is pretty easy to set up.
We can also do both or transition more slowly. We have ZERO docs at the moment, so a RTD page probably doesn't make a lot of sense.

I would love to get started with sphinx RTD, I've just never set it up myself so I don't know the process. Having something available might lessen the barrier to writing docs.

I would love to get started with sphinx RTD, I've just never set it up myself so I don't know the process. Having something available might lessen the barrier to writing docs.

We can copy the setup from parthenon... I can get it set up when I have a spare moment, or I can walk you through it. Main pieces are:

Set up a bare branch in the repo to host the generated html
Turn on github pages. We'll get the url lanl.github.io/phoebus
We can blindly copy the docs github workflow from parthenon, as well as the build script and directory structure
Then we add our files and make sure they're listed in the index file at the top level of the source directory of the docs.

to be clear, this MR doesn't need to wait on that. We can migrate these into RTD later.

Although this would be a good time to do it. ;)

Yeah, I think this is the right spot to set up a minimal RTD

When folks have time, I would appreciate another look through this. cc: @brryan @curiousmiah

Thanks @brryan! I'm going to merge this today if there are no other immediate concerns (cc: @Yurlungur ) so that this is live when the methods paper hits the arxiv tomorrow. I'll open an issue for further thoughts / planning for docs related things.


Added layoutpanel.body and padding

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/test all

/retest


Update several images from various areas

How to categorize this PR?
/kind enhancement
Release note:

The following images are updated:
- registry.k8s.io/metrics-server/metrics-server: v0.6.3 -> v0.6.4
- registry.k8s.io/cpa/cluster-proportional-autoscaler: v1.8.8 -> v1.8.9
- registry.k8s.io/coredns/coredns: v1.10.0 -> v1.10.1
- quay.io/prometheus/blackbox-exporter: v0.23.0 -> v0.24.0
- quay.io/prometheus/node-exporter: v1.5.0 -> v1.6.1
- ghcr.io/credativ/plutono: v7.5.22 -> v7.5.23
- ghcr.io/prometheus-operator/prometheus-config-reloader: v0.61.1 -> v0.67.1
- registry.k8s.io/dns/k8s-dns-node-cache: 1.22.20 -> 1.22.23

cc @istvanballok @rickardsjp in case you want to double-check the monitoring related version updates

/retest

Thank you @istvanballok for double-checking.

Just for consistency, we could update the metrics server version that is used for the kind cluster in example/gardener-local/metrics-server/kustomization.yaml, otherwise it looks good to me!

I think it is already updated in https://github.com/gardener/gardener/pull/8324/commits/615976a60bc50a76376157103f708b93d6380713.

/retest


Benchmarks, and 'interface' traits?

I've been beavering away learning rust by working on omnikron13/braid, another generic rope implementation.
I'm wondering what benchmarks you might have that would be worth stealing? I already lifted more or less any of the ones from cessen/ropey that I was able to apply to my codebase. =P
Although useful, they don't seem to blend in much unicode, and they're definitely pretty artificial, being composed of Lorem Ipsum text (v.s. for example source code, presumably a primary target for a rope implementation). I'd be very interested, and much appreciative, for extra and perhaps more 'realistic' benchmarks you might be able to propose?
On an only partially related note...  Do you think it would be worth attempting to abstract out any 'interface' traits related to accessing these string+ data types? I've been thinking of maybe trying some other 'text editor buffer' type string implementations too at some point, and looking at the few ropes that exist already and such, I wonder if trying to standardise something for plug-n-play use, and benchmarking efforts, might work? Idk, just an idea, lemme know your thoughts.

Although useful, they don't seem to blend in much unicode [..] being composed of Lorem Ipsum text

When benchmarking it really doesn't matter what the contents of the text you're editing are, you're usually only interested in figuring out how long each rope.insert or rope.delete takes. The main variable is how long the text is, not what it is. A wall of Lorem Ipsums is just as good of a data set as a bunch of emojis.

they're definitely pretty artificial

Yes, but that's because of the editing pattern. The positions of the insertions and deletions in those benchmarks are usually randomly generated: you insert a character here, then delete some there, and so on.
This is not how humans actually edit text. We usually insert or delete entire runs of characters before moving the cursor to another place in the document. We might jump around occasionally, but most of the edits are localized.
If a rope is designed with this assumption in mind (and both crop and Jumprope are) it's nice to have benchmarks that don't make you ping-pong around.
Luckily the author of Automerge (a CRDT library) and the author of Jumprope recorded several character-by-character editing traces of them typing out a document in real time. You can find those traces here.

I wonder if trying to standardise something for plug-n-play use, and benchmarking efforts, might work?

I already did something along these lines in this repo. There you can find a bunch of benchmarks, including those editing traces I mentioned. You can clone that repo, add your rope to the dependencies, implement the Rope trait on it and add it to this list. Then just run cargo run --release -- --bench <your_rope>.

Although useful, they don't seem to blend in much unicode [..] being composed of Lorem Ipsum text

When benchmarking it really doesn't matter what the contents of the text you're editing are, you're usually only interested in figuring out how long each rope.insert or rope.delete takes. The main variable is how long the text is, not what it is. A wall of Lorem Ipsums is just as good of a data set as a bunch of emojis.

Is that strictly true, given that rust strings are stored as vectors of bytes/u8, encoded as UTF-8? A string entirely composed of ASCII characters could be indexed just by the byte position in O(1) time, but a string composed of a completely random mix of characters would require checking every character width to compute the indices and result in O(n) time, surely?
I've personally been playing around with indexing various things about the character composition of the strings (character widths, positions of newlines, etc.) to improve performance of certain operations, but this then does mean the distribution affects the actual times.
It's in testing how successful strategies I'm experimenting with here that purely ASCII benchmarks (or ones with a non-representative distribution of newlines) aren't likely to give me particularly useful results.

they're definitely pretty artificial

Yes, but that's because of the editing pattern. The positions of the insertions and deletions in those benchmarks are usually randomly generated: you insert a character here, then delete some there, and so on.
This is not how humans actually edit text. We usually insert or delete entire runs of characters before moving the cursor to another place in the document. We might jump around occasionally, but most of the edits are localized.
If a rope is designed with this assumption in mind (and both crop and Jumprope are) it's nice to have benchmarks that don't make you ping-pong around.

Hm, might this assumption be missing some things? I've not thought too deeply on this yet, but alongside adding or removing a line (for example), operations like find/replace which could be operating across an entire document aren't all that uncommon, just as an example.
I'm not sure how best to create benchmarks/test data to cover different types of edits, so that's just something I'm pondering on...

Luckily the author of Automerge (a CRDT library) and the author of Jumprope recorded several character-by-character editing traces of them typing out a document in real time. You can find those traces here.

I wonder if trying to standardise something for plug-n-play use, and benchmarking efforts, might work?

I already did something along these lines in this repo. There you can find a bunch of benchmarks, including those editing traces I mentioned. You can clone that repo, add your rope to the dependencies, implement the Rope trait on it and add it to this list. Then just run cargo run --release -- --bench <your_rope>.

Ah, I think these are exactly the sort of thing I'm thinking about, thanks. =)
I may try modifying this to use some rough unicode test files too, actually...

A string entirely composed of ASCII characters could be indexed just by the byte position in O(1) time, but a string composed of a completely random mix of characters would require checking every character width to compute the indices and result in O(n) time

Yes, but that time complexity is set at "design" time, not at runtime. If you design your rope to work with byte offsets then indexing is O(1), Unicode or not. It's the user's responsibility to make sure that the byte offsets they provide are valid. And if you instead design it around char offsets then it's always O(n), ASCII or not.
As an aside, I would advise against choosing codepoints as the indexing metric. Like you said it brings a performance penalty over bytes, and it doesn't provide any advantages over it. The fundamental unit of text in a real editor is not a Unicode code point, it's much closer to an extended grapheme cluster. Imo Bytes and ECGs are the only two sensible metrics to choose from, and (for reasons that I won't go over here) using graphemes doesn't work.

Hm, might this assumption be missing some things? I've not thought too deeply on this yet, but alongside adding or removing a line (for example), operations like find/replace which could be operating across an entire document aren't all that uncommon, just as an example.

Well it's a general rule-of-thumb, not a theorem ;) There are definitely cases where it breaks down, e.g. find&replace and multiple cursors, but it's still a useful insight. As a piece of anecdotal evidence supporting this, after reimplementing crop's leaves as gap buffers instead of simple Strings I saw performance improvements of 10-20% on the editing traces.

I'm not sure how best to create benchmarks/test data to cover different types of edits

The traces already contain find&replace and all other kinds of edits, so I wouldn't worry about that. Of course you could record your own trace if you really wanted to. I think there's a vscode plugin for it but I'm not sure.


Cannot dynamically change controls' disabled background color, all though you can do it statically through custom dictionary.

Describe the bug
Not so much a bug as missing functionality.
Most controls can have their disabled background color statically set via a custom dictionary, by using an entry such as

( See https://github.com/microsoft/WindowsAppSDK/issues/4702 where custom dictionary entry does not work )
My problem is that the user can change the background color of the container the control is on, so I need to dynamically change the Control's disabled background color.
Ideally, this could be done by exposing the controls disabled background color, the way it is currently done for background color.
In the meantime, in the following link, someone showed me how to access the elements of the Visual Tree for a check box
https://github.com/microsoft/microsoft-ui-xaml/issues/9236
Could something like this be done for TextBox type controls (AutoSuggestBox, NumberBox, PasswordBox and TextBox) and the Button type controls (Button, HyperlinkButton, RadioButton, RadioButtons, RepeatButton, SplitButton, ToggleButton and ToggleSplitButton)?
Thank you in advance!
Steps to reproduce the bug
No control property to dynamically change the disabled back ground color.
Ideally the code would look similar to
    private void SetButtonBackGroundDisabledColor(Windows.UI.Color color)
    {
            Button.DisabledBackground = new SolidColorBrush(color);
    }

Can only do it statically in a custom dictionary by adding following line:

Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.6.0: 1.6.240829007
Windows version
Windows 10 (21H2): Build 19044
Additional context
No response

You can do :
private void SetButtonBackGroundDisabledColor(Button btn, Windows.UI.Color color)
{
    btn.Resources["ButtonBackgroundDisabled"] = new SolidColorBrush(color);
}

Thanks for the reply!
I verified this works.
I also like the methodology and can use it elsewhere in my code.
Will close this ticket

Will use suggested code to achieve what I need


Biweekly events can end up in the wrong week if start date of the RRule and the RRule set differ

I've written a test-case that triggers this bug:
#[test]
fn weekly_with_interval_3() {
    let rrule_dt_start = ymd_hms(2022, 10, 19, 18, 30, 0);

    let mut rrule = "FREQ=WEEKLY;INTERVAL=2"
        .parse::<RRule<Unvalidated>>()
        .unwrap();
    rrule.count = Some(2);

    let rrule = rrule.validate(rrule_dt_start).unwrap();

    let rrule_set_dt_start = ymd_hms(2022, 10, 24, 18, 30, 0);
    let set = RRuleSet::new(rrule_set_dt_start).rrule(rrule);

    test_recurring_rrule_set(
        set,
        &[
            ymd_hms(2022, 11, 2, 18, 30, 0),
            ymd_hms(2022, 11, 16, 18, 30, 0),
        ],
    );
}

The RRuleSet should report the dates 2022-11-02 and 2022-11-16 as the dates of the next events. However, it reports 2022-10-26 and 2022-11-09, which is offset one week by where the events should be.

One should only use one specific start date when working with a RRuleSet, meaning that the date used in rrule.validate and RRuleSet::new should be the same. We should really try to make the API design of the library better to make it impossible to use multiple start dates for an RRuleSet.

Is there a way of retrieving the next event of a rrule starting from a given DateTime other than iterating over all the past events? That's what I was trying to accomplish with this code.
Btw. thanks for making this library. It saved me a lotnof headache.

Yeah, there is RRuleSet::after and RRuleSet::before to support those use-cases.
So your code should be:
#[test]
fn weekly_with_interval_3() {
    let rrule_dt_start = ymd_hms(2022, 10, 19, 18, 30, 0);

    let mut rrule = "FREQ=WEEKLY;INTERVAL=2"
        .parse::<RRule<Unvalidated>>()
        .unwrap();
    rrule.count = Some(2);

    let rrule = rrule.validate(rrule_dt_start).unwrap();

    let rrule_set_dt_start = ymd_hms(2022, 10, 24, 18, 30, 0);
    let set = RRuleSet::new(rrule_dt_start).after(rrule_set_dt_start).rrule(rrule);

    test_recurring_rrule_set(
        set,
        &[
            ymd_hms(2022, 11, 2, 18, 30, 0),
            ymd_hms(2022, 11, 16, 18, 30, 0),
        ],
    );
}

I was ignoring after so far, since I'm accessing the generated times through the Iterator, where after doesn't work. However, I think I may be able to modify my code to use the all endpoint instead, though it's not a perfect fit.
Thanks for you assistance and feel free to close the issue.

I will take a look into how we can design the API to ensure that only one start date is being used. Thanks for reporting, will close this issue for now.


Feature request: Add "ToTop" button on the home page.

On the Home page of the doc2pen website add a "to top" button in the bottom right corner of the page

I want to work on this.
will complete this in a day!

I want to work on this.
will complete this in a day!

you both can work on this and collaborate within yourself for it.

you both can work on this and collaborate within yourself for it.

Sir i have completed this yesterday

Sir i have completed this yesterday

i just need to open up a pr

i just need to open up a pr

okay then you both can give PR by that time which UI is better will merge that

okay then you both can give PR by that time which UI is better will merge that

sir please review my PR

sir please review my PR

okay then you both can give PR by that time which UI is better will merge that

ok sir 👍

okay then you both can give PR by that time which UI is better will merge that

ok sir 👍


record_indexer template update

https://github.com/ucldc/rikolti/blob/main/record_indexer/index_templates/record_index_config.py
media and thumbnail path/filepath updates.

Thanks!

From: christine @.***>
Sent: Tuesday, March 19, 2024 1:51 PM
To: ucldc/rikolti
Cc: Barbara Hui; Assign
Subject: [ucldc/rikolti] record_indexer template update (Issue #832)
CAUTION: EXTERNAL EMAIL
https://github.com/ucldc/rikolti/blob/main/record_indexer/index_templates/record_index_config.py
media and thumbnail path/filepath updates.
—
Reply to this email directly, view it on GitHubhttps://github.com/ucldc/rikolti/issues/832, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AACII2KKBKVEHZAXQ37AIWLYZCQLTAVCNFSM6AAAAABE6JV4HOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4TKOJZGMZTEMA.
You are receiving this because you were assigned.Message ID: @.***>


Mac_android android_semantics_integration_test and Mac_android run_release_test failing with "NO_RESOURCE" infra error

Both tests started consistently failing in the devicelab a few hours ago:
https://chromium-swarm.appspot.com/task?id=576bafbbd738c910&o=true&w=true
https://chromium-swarm.appspot.com/task?id=576bafc358349410&o=true&w=true
Both are marked flaky, so the tree is not closed.

/cc gardener @mdebbar /cc @godofredoc

This is my fault, all the mac staging configs were updated to use mac 12.0.1 but the mac_android machine was not updated.

Will mark these tests as unflaky since they have been fixed, which will move them back into the prod pool.

Just FYI: the Mac_android run_release_test has been highly flaky.

@mdebbar are these flakes? It seems like  a real failure as it's pointing to iOS Podfile.lock does not contain expected pods

@mdebbar are these flakes? It seems like a real failure as it's pointing to iOS Podfile.lock does not contain expected pods

What I meant is they fail frequently, and pass upon retries. I don't know the actual cause of the failures.

@mdebbar are these flakes? It seems like a real failure as it's pointing to iOS Podfile.lock does not contain expected pods

@CaseyHillers  Are you sure you were looking at run_release_test?  That error looks like https://github.com/flutter/flutter/issues/94372 from another test, and would only happen on iOS.
The run_release_test failures look like:
Task failed: flutter run --release had output on standard error.

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8829305881020289153/+/u/run_run_release_test/test_stdout

Reopened https://github.com/flutter/flutter/issues/91625 to track the actual test flake.

\cc @gspencergoog

I can reproduce the flakiness locally with the latest master version of flutter/flutter and TalkBack version is 9.0.0+316804458.
11561 [android_semantics_integration_test] [STDOUT] stdout: [+1837 ms] 00:22 ^[[32m+7^[[0m: AccessibilityBridge Popup Controls Dropdown Menu has correct Android semantics^[[0m
11562 [android_semantics_integration_test] [STDOUT] stdout: [+3109 ms] 00:25 ^[[32m+7^[[0m^[[31m -1^[[0m: AccessibilityBridge Popup Controls Dropdown Menu has correct Android semantics ^[[1m^[[31m[E]^[[0m^[[0m
11563 [android_semantics_integration_test] [STDOUT] stdout: [        ]   Expected: AndroidSemanticsNode with className: android.view.View with actions: [AndroidSemanticsAction.accessibilityFocus, AndroidSemanticsAction.click] with flag isChecked: false with f      lag isEnabled: true with flag isFocusable: true
11564 [android_semantics_integration_test] [STDOUT] stdout: [        ]     Actual: AndroidSemanticsNode:<{flags: {isEditable: false, isEnabled: true, isDismissible: false, isCheckable: false, isChecked: false, isFocused: true, isLongClickable: false, isFocusa      ble: true, isPassword: false}, id: 73, text: null, rect: {height: 144, width: 330, bottom: 344.0, top: 296.0, left: 109.0, right: 219.0}, actions: [16, 128], className: android.view.View, liveRegion: 0, contentDescription: Item 1}>
11565 [android_semantics_integration_test] [STDOUT] stdout: [        ]      Which: Expected actions: [AndroidSemanticsAction.accessibilityFocus, AndroidSemanticsAction.click]
11566 [android_semantics_integration_test] [STDOUT] stdout: [        ]             Actual actions: [AndroidSemanticsAction.clearAccessibilityFocus, AndroidSemanticsAction.click]
11567 [android_semantics_integration_test] [STDOUT] stdout: [        ]             Unexpected: {AndroidSemanticsAction.clearAccessibilityFocus}
11568 [android_semantics_integration_test] [STDOUT] stdout: [        ]             Missing: {AndroidSemanticsAction.accessibilityFocus}
11569 [android_semantics_integration_test] [STDOUT] stdout: [        ]   Dropdown Item 1 doesn't have the right semantics


How to create a deformable object in your customized enviornment

Hi Matas,
After I ran through the code, I found that the environment only create box-shape objects to grasp.
What about deformable (soft) objects like those in your video? How to create target deformable object.
Thanks

I have encountered a similar problem.
As far as I can see, there is no description of deformable objects in this code.

I am also wondering, how the deformable object is built.


Update Ukrainian (dict_uk#6.1.5)

used last version dict_uk + used all dictionary
../../gradlew hunspellFull

Sorry, I’m a bit swamped currently with other OSS work.
I’ll get to it in a couple months.
There are scripts in this repo to update things automatically, which I’ll use :)

Sorry, maybe you just merge it now before you update automatically in future?

Hey, thanks for your patience!
Hmm, what good would that do? Merging this doesn’t release it?

I use https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker-ukrainian
this extension uses this package

Does it pull from Git instead of npm?

npm https://github.com/streetsidesoftware/cspell-dicts/blob/main/dictionaries/uk_UA/package.json#L46C14-L46C14

Terribly sorry, I really don‘t have time to investigate this repo and cut a release here the coming weeks. Could you ping me again in a month? Sorry, thanks!


[3.8.0] Multi-step Achievements Not Maintaining Progress

General information:
Project issue is for:
Server, maybe Module?
Expected result:
Traveler achievement maintains progress between raids.
Actual result:
Traveler resets its progress to 0 after exiting a raid with any status.
How to reproduce:

Enter Factory raid
Earn enough XP to achieve survived status
Exfil and check "Traveler" acheivement progress

Log files:
Attached below
Profile:
Attached below
Notes
Worth noting that achievements which are completed in a single raid are tracked, get the pop-up, and persist after raid end. This can be noted with things like finding the crashed plane on woods, killing any boss for the first time, surviving your first raid, etc.

Attachments

log_2024.01.09_10-44-01_<IP_ADDRESS>.28375.zip (21 KiB)
LogOutput.log (53 KiB)
server-2024-01-09.log (628 KiB)
659d09c20000221809b7248a.zip (34 KiB)

Originally written by PhantomInTime

Testing and confirmed working:

Attachments

image.png (789 KiB)

Originally written by chomp


Searchable snapshots are GA

Searchable Snapshots have reach GA in 2.7
https://github.com/opensearch-project/opensearch-build/blob/main/release-notes/opensearch-release-notes-2.7.0.md
https://opensearch.org/docs/latest/tuning-your-cluster/availability-and-recovery/snapshots/searchable_snapshot/
We will need to update the code to not apply the experimental flag if cluster version is 2.7 or above
Ref: https://github.com/Opster/opensearch-k8s-operator/blob/main/opensearch-operator/pkg/builders/cluster.go#L180

PR Raised https://github.com/Opster/opensearch-k8s-operator/pull/504

Closing this issue as it was implemented with PR #504.


README.md: Remove codacy badge, Add travis badge

This removes Codacy badge and adds Travis badge to README.md file.
Closes https://github.com/NITSkmOS/Algorithms/issues/209

By submitting this pull request I confirm I've read and complied with the
below declarations.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the commit guidelines for this project.
[x] My code follows the standard code structure.
[x] This pull request has a descriptive title. For example, {Tag}: Add {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.
[x] This pull request shall only be reviewed and merged once all the checks passes. No maintainer or supporter shall be obliged to review it before this condition is met.
[x] I have mentioned the issue number correctly (with hyperlink) in this pull request description.

After you submit your pull request, DO NOT click the 'Update Branch' button.

@sangamcse rebase

Hey! I'm GitMate.io! This pull request is being rebased automatically. Please DO NOT push while rebase is in progress or your changes would be lost permanently :warning:

Automated rebase with GitMate.io was successful! :tada:


Deprecation warnings

After scaffolding a new app with latest Flask-Diamond (0.5.1), I get these deprecation warnings when running any of the make commands:
SETTINGS=$PWD/etc/conf/testing.conf $(which nosetests) soundtracks -c etc/nose/test.cfg
/Users/ehsan/.virtualenvs/soundtracks/lib/python3.6/site-packages/flask/exthook.py:71: ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use flask_sqlalchemy instead.
  .format(x=modname), ExtDeprecationWarning
/Users/ehsan/.virtualenvs/soundtracks/lib/python3.6/site-packages/flask/exthook.py:71: ExtDeprecationWarning: Importing flask.ext.script is deprecated, use flask_script instead.
  .format(x=modname), ExtDeprecationWarning
/Users/ehsan/.virtualenvs/soundtracks/lib/python3.6/site-packages/flask/exthook.py:71: ExtDeprecationWarning: Importing flask.ext.admin is deprecated, use flask_admin instead.
  .format(x=modname), ExtDeprecationWarning
/Users/ehsan/.virtualenvs/soundtracks/lib/python3.6/site-packages/flask/exthook.py:71: ExtDeprecationWarning: Importing flask.ext.babelex is deprecated, use flask_babelex instead.
  .format(x=modname), ExtDeprecationWarning
/Users/ehsan/.virtualenvs/soundtracks/lib/python3.6/site-packages/flask/exthook.py:71: ExtDeprecationWarning: Importing flask.ext.restful is deprecated, use flask_restful instead.
  .format(x=modname), ExtDeprecationWarning

Is it because the latest Flask is not being used?

Those deprecation warnings came with the 0.11.x flask updates.  They indicate that some extension is still using the old style of importing, which was import flask.ext.whatever but is now flask_whatever.
I've fixed this almost everywhere, but as your comment demonstrates, there are still remaining old-style imports.  I'm honestly not certain where those deprecation warnings originate from, and I'd like some help getting to the bottom of it.

I'm honestly not certain where those deprecation warnings originate from, and I'd like some help getting to the bottom of it.

It's a bit difficult to trace these, with flask.exthook hiding the offending importing module when printing the deprecation warning...
I modified my local flask.exthook to add raise RuntimeError(modname) immediately after it prints the deprecation warning, so I get a full stack trace for every offending import, which makes it feasible to trace these.
My partial results are:

Zero issues with Flask-Diamond itself.
~Gazillion issues with flask_admin, importing flask.ext.admin instead of flask_admin
A bunch of issues with a few other packages - flask_sqlalchemy, flask_assets, flask_restful

I guess the proper strategy would be to submit issues (and pull requests) to each individual package...


New examples for DomainAuthorizationPolicy and ElytronAuthorizationPolicy

New examples for DomainAuthorizationPolicy (using legacy Wildfly security) and ElytronAuthorizationPolicy (using Elytron security). They are the same just separated for the two use cases.
Any comments are welcome.
!!! Depends on https://github.com/jboss-fuse/wildfly-camel/pull/580 (and of coure new wildfly-camel build) !!!

This needs a rebase

LGTM - examples are working

Thanks