V2.0.8

Closes #11

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Looks like the compiler does not like values > 0 for USE_IPOLATES:
Config.c: In function 'f_config':
Config.c:83:18: error: operator '>' has no left operand
 #if USE_IPOLATES > 0
                  ^
make: *** [Config.o] Error 1
Traceback (most recent call last):

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

I attempted to debug this locally and could not reproduce the Azure failure.  Would setting #define USE_IPOLATES 3 in config.h be an acceptable solution hack around this problem?

I attempted to debug this locally and could not reproduce the Azure failure. Would setting #define USE_IPOLATES 3 in config.h be an acceptable ~solution~ hack around this problem?

Sure. Do you want to send a PR? And add yourself as a maintainer too ;-p
I'm slow to respond these days and I don't have much time for wgrib2. We added this for a 1-time project and people at my day job don't use it that much.


Defer ipv deter spellingsfoutje

https://github.com/CathelijneVisser/server-side-rendering/blob/4809f0e17a0d63583581d3299f7ef5c03cf8567d/views/partials/head.ejs#L8

Fixed it! thanks


Support entitlements configuration for MacOs

The user had an issue when an app binary built and signed on CI didn't run locally:

$ /Applications/MyApp.app/Contents/MacOS/MyApp
Error occurred during initialization of VM
Could not reserve enough space for code cache (245760K)

The original report:
https://kotlinlang.slack.com/archives/C01D6HTPATV/p1678957583077879?thread_ts=1678880842.552899&cid=C01D6HTPATV
Our options:

Add more info to the docs about entitlements configuration
Or try to configure them automatically with our gradle plugin
Or both

https://developer.apple.com/documentation/bundleresources/entitlements

And even more specifically, you need something to the effect of:
Create a file default.entitlements or whatever you want to name it
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>com.apple.security.cs.allow-jit</key>
    <true/>
    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
    <true/>
    <key>com.apple.security.cs.disable-library-validation</key>
    <true/>
</dict>
</plist>

In your build.gradle.kts file add
compose.desktop {
    application {
        mainClass = ""

        nativeDistributions {
            targetFormats(TargetFormat.Dmg, TargetFormat.Msi, TargetFormat.Deb)
            packageName = ""
            packageVersion = version as String

            macOS {
                bundleID = ""
                iconFile.set(project.file(""))
                entitlementsFile.set(project.file("default.entitlements")) // <----------- this line
            }
        }
    }
}

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Copy project into image instead of cloning to avoid stale images on Docker Hub

Docker RUN statements cache based on the text of the command executed,
not the content of what it does to the image.
Since the command was cloning the project, and the text didn't change,
building the image would not update the code if the image was already
cached. This lead to a stale Docker image distributed on Docker Hub.
This could also cause some confusion, as modified code would not show up
on the image during the build process.
This commit changes the build process to copy the content of the project
into the image. Whenever a file changes it will trigger a new updated
image.
IMPORTANT: Do not submit PRs with only formatting / PEP8 / line length changes, I will close them with great prejudice.  The PEP8 checks I don't follow are intentional. PRs for minor bugfixes, typos, etc are fine.
Changes these areas

[x] Bugfixes
[ ] Feature behavior
[ ] Command line interface
[ ] Configuration options
[ ] Internal architecture
[ ] Archived data layout on disk

Ah thank you so much, I was wondering why that was happening sometimes.
I think someone told how this worked long ago and I somehow forgot, but it makes total sense.


Ability to view and set team leads on itineraries

Fixes #1813
Initial basic implementation to allow setting a team lead / changing a team lead and displaying the current team lead on the itinerary details page.
A team lead dropdown is included when potential team leads are available...

Once submitted a success message is shown and the team lead is displayed in the list

There are some future enhancements / known issues with the current implementation which I will address as separate issues.

It would be useful to make the team lead stand out more in the lister - Opened #1833
If you add a team member to the team, the team lead dropdown is not shown/updated without a full page reload - this is because some of the page functions via ajax/js code. We need to either refactor to update the knockout model and code or remove the ajax code for now.
Currently I use an optional value on the details page querystring to show the success/failure message for adding a team lead. This would be better achieved using TempData which requires Sessions to be enabled.

thanks @stevejgordon hoping to get another set of eyes from @MisterJames or @mgmccarthy before we merge (or myself but time rarely permits such endeavors)


Added NanoPi NEO/NEO2 board support

This has been tested to work with FreeBSD 12 and current releases.
I will be happy to maintain these items going forward.

@nuxy Thanks for the PR!

It works .Thanks .


ascp command can not continue with -k 1 after transferring break

Ascp command on Linux system can not continue with -k 1 after transferring break.  If I rerun the command, ascp will always re-download. How can I continue downloading using the temporary file? (.aspera-ckpt).  My command is as follows.
ascp -QT -k 1 -l 500m -P 33001 -i ~/.aspera/connect/etc/asperaweb_id_dsa.openssh era-fasp@fasp.sra.ebi.ac.uk:/vol1/srr/SRR874/003/SRR8742453 0sra/SRR8742453

Hi,
This repo is about ascli not ascp. Although ascli uses ascp under the cover. So you are not in the right place to ask this.
The equivalent of -k 1 in ascli is --ts=@json:'{"resume_policy":"attrs"}'
ascp does not automatically resume a transfer, the user has to re-execute the command and have option -k different from 0.
ascli does resume automatically when using agent direct (i.e. local ascp) through a configurable scheme (for "retryable" errors).
if -k 1 is provided, resume shall be activated (it checks files attributes).
note that the .aspera-ckpt file (or .aspx depending on aspera.conf) is not a temp file, but it is a "checkpoint" file, it is typically 64 to 80 bytes and contains information like attribute/checksum to allow resume.
advice:

try -k2 instead of -k1
add -DDL- that will display debug info


Update the GitHub actions

Hi,
I have prepared the draft for the new pipelines format on GitHub actions for the stable/insiders version.
This update also includes standardization of the runner for both unit and UI tests between vscode-camelk, camel-lsp-client-vscode and camel-dap-client-vscode  projects
Questions/Issues:

I need help with sonar cloud scan steps: main, insider

Update on SonarCloud issue:  Test with CI pipline integrated in Main/ubuntu pipeline

Pros: Test coverage and default Quality Gate
Cons: Not possible to run scan on PR only on pushes with main due to github actions secrets limitations

Results: insiders, main
Please feel free to review and provide feedback.

Hi, sorry for the delay in updating!
I corrected everything we discussed.

test coverage is deleted -> will be part of the next iteration


Set Default Models page - Text Embedding - Not able is see full Model dropdown list when not in full screen mode.

Note - I am not seeing this issue reproduce always.
Have chrome browser not in full screen mode.
Steps to reproduce the problem:

Configure OpenAI model.
Go to "Set Default Models" page.
Tried to list all models for Text Embedding
Notice that the dropdown list is truncated at the top and not visible.

After I saw this issue , I have not been able to reproduce it since then.

Since this only happened once, can it be closed?

I am able to reproduce it again today with a smaller screen size.


Error while editing taxonomy terms or adding entity types

While editing https://de.serlo.org/taxonomy/term/get/160961 I get the error:
Array
(
    [query] =>             mutation setTaxonomyTerm(
                $id: Int!
                $trashed: Boolean!
                $alias: String
                $type: TaxonomyTermType!
                $instance: Instance!
                $name: String!
                $description: String
                $weight: Int!
                $parentId: Int!
                $childrenIds: [Int!]!
            ) {
                _setTaxonomyTerm(
                    id: $id
                    trashed: $trashed
                    alias: $alias
                    type: $type
                    instance: $instance
                    name: $name
                    description: $description
                    weight: $weight
                    parentId: $parentId
                    childrenIds: $childrenIds
                )
            }
    [variables] => Array
        (
            [id] => 160961
            [trashed] =>
            [alias] =>
            [discriminator] => taxonomyTerm
            [type] => topic-folder
            [instance] => de
            [name] => Aufgaben zu Rechengesetzen und Rechentricks der Addition
            [description] => {"plugin":"rows","state":[{"plugin":"text","state":[{"type":"p","children":[{}]}]}]}
            [weight] => 0
            [parentId] => 1292
            [childrenIds] => Array
                (
                )

        )

    [errors] => Array
        (
            [0] => Array
                (
                    [message] => Variable "$type" got invalid value "topic-folder"; Expected type TaxonomyTermType. Did you mean topicFolder?
                    [locations] => Array
                        (
                            [0] => Array
                                (
                                    [line] => 5
                                    [column] => 17
                                )

                        )

                    [extensions] => Array
                        (
                            [code] => INTERNAL_SERVER_ERROR
                        )

                )

        )

)

While adding an entity to a topic-folder I get the error:
Array
(
    [query] =>             mutation setTaxonomyTerm(
                $id: Int!
                $trashed: Boolean!
                $alias: String
                $type: TaxonomyTermType!
                $instance: Instance!
                $name: String!
                $description: String
                $weight: Int!
                $parentId: Int!
                $childrenIds: [Int!]!
            ) {
                _setTaxonomyTerm(
                    id: $id
                    trashed: $trashed
                    alias: $alias
                    type: $type
                    instance: $instance
                    name: $name
                    description: $description
                    weight: $weight
                    parentId: $parentId
                    childrenIds: $childrenIds
                )
            }
    [variables] => Array
        (
            [id] => 25673
            [trashed] =>
            [alias] => /mathe/zahlen-größen/grundrechenarten/addition/aufgaben-addition-natürlicher-zahlen
            [discriminator] => taxonomyTerm
            [type] => topic-folder
            [instance] => de
            [name] => Aufgaben zur Addition natürlicher Zahlen
            [description] =>
            [weight] => 1
            [parentId] => 1292
            [childrenIds] => Array
                (
                    [0] => 27591
                    [1] => 9741
                    [2] => 9549
                    [3] => 96143
                    [4] => 96155
                    [5] => 9757
                    [6] => 96181
                    [7] => 96113
                    [8] => 96165
                    [9] => 75513
                    [10] => 75517
                    [11] => 75523
                    [12] => 75542
                    [13] => 75532
                    [14] => 77659
                    [15] => 77812
                    [16] => 77819
                    [17] => 77660
                    [18] => 9743
                    [19] => 77839
                    [20] => 96170
                    [21] => 155284
                    [22] =>
                )

        )

    [errors] => Array
        (
            [0] => Array
                (
                    [message] => Variable "$type" got invalid value "topic-folder"; Expected type TaxonomyTermType. Did you mean topicFolder?
                    [locations] => Array
                        (
                            [0] => Array
                                (
                                    [line] => 5
                                    [column] => 17
                                )

                        )

                    [extensions] => Array
                        (
                            [code] => INTERNAL_SERVER_ERROR
                        )

                )

            [1] => Array
                (
                    [message] => Variable "$childrenIds" got invalid value null at "childrenIds[22]"; Expected non-nullable type Int! not to be null.
                    [locations] => Array
                        (
                            [0] => Array
                                (
                                    [line] => 11
                                    [column] => 17
                                )

                        )

                    [extensions] => Array
                        (
                            [code] => INTERNAL_SERVER_ERROR
                        )

                )

        )

)

Close via 852f214a2ce16ff48106bf42cdf17e7f5ad18007 and b5f4bba29eb7068f85fe8d7fe71a2b9d1f295798


improve terminology, either text-marking or marking

I guess just marking is fine, in any case? Attempt refactoring and see how it turns out.

Refactored and everything seems fine. Closing...


More context in error emails

This comes from looking today at some error emails, particularly from log records without stack traces, and wishing I knew more about them -- for a start, what code logged them.
Most of the branch is a bunch of cleanups to this code that I spotted in the course of building that feature.

@gnprice this is already merged, right?  Closing.


v5 version not compiling using carthage

New Issue Checklist

[x] I have looked at the Documentation
[x] I have read the F.A.Q.
[x] I have filled out this issue template.

Issue Info

Info
Value

Platform
tvos

Platform Version
10.2.1

SnapKit Version
5.0.1

Integration Method
carthage

Issue Description
Does not compile for tvOS on carthage 0.33.0. Following is spit into logs:
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:49:37: error: 'firstAnchor' is only available on tvOS application extension 10.0 or newer
        areLayoutAnchorsEqual = lhs.firstAnchor === rhs.firstAnchor &&
                                    ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:49:37: note: add 'if #available' version check
        areLayoutAnchorsEqual = lhs.firstAnchor === rhs.firstAnchor &&
                                    ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:46:15: note: add @available attribute to enclosing operator function
internal func ==(lhs: LayoutConstraint, rhs: LayoutConstraint) -> Bool {
              ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:49:57: error: 'firstAnchor' is only available on tvOS application extension 10.0 or newer
        areLayoutAnchorsEqual = lhs.firstAnchor === rhs.firstAnchor &&
                                                        ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:49:57: note: add 'if #available' version check
        areLayoutAnchorsEqual = lhs.firstAnchor === rhs.firstAnchor &&
                                                        ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:46:15: note: add @available attribute to enclosing operator function
internal func ==(lhs: LayoutConstraint, rhs: LayoutConstraint) -> Bool {
              ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:50:17: error: 'secondAnchor' is only available on tvOS application extension 10.0 or newer
            lhs.secondAnchor === rhs.secondAnchor
                ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:50:17: note: add 'if #available' version check
            lhs.secondAnchor === rhs.secondAnchor
                ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:46:15: note: add @available attribute to enclosing operator function
internal func ==(lhs: LayoutConstraint, rhs: LayoutConstraint) -> Bool {
              ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:50:38: error: 'secondAnchor' is only available on tvOS application extension 10.0 or newer
            lhs.secondAnchor === rhs.secondAnchor
                                     ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:50:38: note: add 'if #available' version check
            lhs.secondAnchor === rhs.secondAnchor
                                     ^
/Users/ckmilloy/Code/ibm/tvos/IBM/Carthage/Checkouts/SnapKit/Source/LayoutConstraint.swift:46:15: note: add @available attribute to enclosing operator function
internal func ==(lhs: LayoutConstraint, rhs: LayoutConstraint) -> Bool {

Can we get an update here?

I think the solution is just tagging a release here so we don't have to use "develop" branch in the cartfile.

Still looking for an update.

Hello @kylemilloy
What about Xcode 11?


Log Management

http://logstash.net/ seems nice
Idea is to have all logs (nginx, php, mysql, wordpress, postfix, system logs, etc, etc) manageable using web view!

Logstash, elasticsearch and kibana are the best tools for log management.

+1 for a (web view) admin tool to search/view/analyze server logs saving me from ssh'ing into the box to collect/grep/analyze.  I am currently using pimpmylog.com in the 22222 admin area for this, it's lightweight (a 700kb drop in) and can send notifications to your desktop.  I haven't used logstash and haven't seen the log tools/views/web interface it provides, but it seems more feature rich but heavier.

@cm896 thanks for http://pimpmylog.com/
At the moment, I just want to avoid anything JAVA based. Java is too resource intensive. May be there is a way to tweak java apps that I am not familiar with.

I agree, I avoid java like the plague.  Are we looking at the same package?
"Pimp my Log is a web app written in PHP."

I will check Pimp my log soon.
I am looking for something real-time. Maybe http://logio.org/ (haven't tested)

@rahul286 - I super appreciate your time and thank you for everything you have done and do for ee.  It's a great project.  Thanks for checking pml out.  I hope you find it as useful as I do.
I haven't tested logio either, but pml is near real time (with auto refresh set to 1s for a pushed update).  There is a manual refresh button, that will pull updates upon request too (I use this the most).  The notification to the desktop is useful for error monitoring while testing.
Using the demo here, you can see the status of the logs on the screen you are viewing.
Demo link: http://demo.pimpmylog.com/?tz=Europe%2FParis&l=en_GB&w=on&o=&p=-1&i=apacheaccess&m=10&r=0&s=&n=false
Status of what's on your screen is below - load more and export buttons.
10 logs displayed, no new log found in 1ms with 663B of logs, 1 skipped line(s), 0 unreadable line(s).
File /var/log/httpd/access_log was last modified on 2015/03/04 16:58:14 at Europe/Paris, size is 17M, log type is NCSA
You can switch between logs super easily php, nginx, sshd, syslog, etc...
I recently picked up a site that I put into an ee install that averages 500k impressions a day.  I needed to move from apache.  I needed the caching and pagespeed helped.  The tail'ed logs scream by so quickly that it's useless without a log viewing tool.  pml is very versitile.
Adding this light weight tool into the admin tools stack is lighter and easier than phpMyadmin, IMO.
For me it's a manual add, but I am sure it would be a value add for the community.  I am all for not bloating up the base tools, but in my experience, I need a good tool to view logs quickly when the client calls.  This tool does many log types out of the box, not just php, nginx, but also sshd, syslog and others.  I don't know python, but can't imagine it'd take an hour to add this to the tools stack and configure the log paths.  I hope others may benefit from this feature suggestion even if it's not incorporated.  While reading back through 2014 ee threads, I have found a few services and tools that I don't use.  So it's been a positive growth experience if nothing else.

How to Install/Setup Guide
ELK - https://miteshshah.github.io/linux/elk/
Logio.org - https://miteshshah.github.io/sysadmin/realtime-log-monitoring-in-your-browser/

An idea for viewing logs = https://github.com/allinurl/goaccess


[Feature Request]: Itens with shadowed borders

Contact Details
No response
Is your feature request related to a problem? Please describe.
Possibility to add shadows in borders of the itens
Describe the solution you'd like
Shadow in borders
Describe alternatives you've considered
Shadow in borders of the itens
Additional context
No response
Code of Conduct

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

Hi @marcoprodata,
Thank you for the suggestion! Adding shadows to the borders of the items can be customized directly within your project by wrapping the carousel items with a Container or BoxDecoration that includes a shadow. Since this can be achieved on your end, and I believe this feature might not be necessary for every user, I’ll go ahead and close this issue.
Feel free to reach out if you have any further questions!
Best regards,
Nikhil


[nrfconnect] Added support for user data in Factory Data parser

Factory data parser did not contain methods to obtain user data.

Added two methods: GetUserData to obtain raw user data and GetUserKey to obtain a single key.

Improved the FactoryDataParser to read and manage the user data field.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 31 committers have signed the CLA.:white_check_mark: ArekBalysNordic:x: mspang:x: tima-q:x: kurvaSai:x: s07641069:x: bzbarsky-apple:x: lboue:x: jtung-apple:x: wy-hh:x: Arkq:x: sreeramIfx:x: amitnj:x: andy31415:x: vivien-apple:x: TE-N-ElvenWang:x: yufengwangca:x: mrjerryjohns:x: woody-apple:x: pankore:x: jmartinez-silabs:x: jepenven-silabs:x: ATmobica:x: praveenCY:x: dependabot[bot]:x: sandeepmistry:x: ShubhamMalasane:x: sharadb-amazon:x: Damian-Nordic:x: mkardous-silabs:x: wqx6:x: manjunath-grlYou have signed the CLA already but the status is still pending? Let us recheck it.


quote database names before running a select

This should clean up some brakeman warnings (I think).  Also I removed
some code that supports SQLServer, and used public API for getting the
database name (rather than instance_variable_get)

@Fryguy updated! :)


'istioctl describe' support no-mixer config and name RBAC policies

Additional work for #15526 to find VirtualService if mixer config not present in Envoy dump.

@liamawhite I agree about the tests.  The previous PR, https://github.com/istio/istio/pull/15827 , included a minimal test.    It is straightforward to check in captures of :15000/config_dump and tests to recognize specific output.
Would that be sufficient?  I feel the only test that would be good enough for this tool is an integration test that spins up actual pods and processes a dump using the latest Envoy and the latest Pilot.  I had planned to follow-up quickly with an Integration test.  It is taking longer than I thought and I am not sure if it is wise to slow down the existing integration tests to test a debugging tool.
What do you think is the sweet spot between canned tests and live tests in the context of "istioctl x describe pod"?

@esnible Checking in config dump is fine as a unit test, but I agree we really need integration tests and those can come in follow up PRs.

4k+ lines!


[server] Closed/open reports

An open or outstanding report reflects on a bug which should be fixed.
If a report is marked as false positive or intentional, then those are
not open reports because they don't need investigation.
When a report is marked as false positive or intentional, then its
fixed_at date should be set, because we consider these as closed.
"open report date" filter member selects reports which are not fixed yet
or their fix date is later than the current time. By setting fixed_at
column when maring a report as false positive makes these reports as not
outstanding ones.

What is the issue we are trying to solve with this patch? Is it the listing of the reports (where the user can change the filters), or the statistics page (where, IIRC, the user can also set filters)? I think we are meddling with a state machine without having that state machine documented, and this is adding a lot of new error paths, and just weird new quirks where it will go sideways again...
Giving better default filters when calculating statistics, or giving better default filters when the user goes from the staticstics list to the bug report list is okay, but what is happening right now, is that we are assigning additional (and it seems conflicting!) semantics to the same column in the database.

When a report is marked as false positive or intentional, then its fixed_at date should be set, because we consider these as closed.

fixed_at had a well-defined semantics before: the timestamp when the bug report was no longer reported by the analysers stored. (I hope this is the meaning, I'm not sure how suppression comments and skipfiles and whatnot intermingle with this.) Anyhow, this is a piece of information (not a base piece per se, but derived from a binary state, but we say it's a ground truth (the fact that the report is or isn't there) just represented on a time axis) that does not (and most likely SHOULD NOT) care about the user's wishes after the analysis and the store call was made.
Now it is wanting to become Either<bugreport disappeared from analysis, user changed review status, ???>.
It could be that our data model was wrong, but I do not see that this is making it better. We are trying to put calculated information into the base data of the entities. This will always cause problems and mismodelling over and over again. Statistics should be either generated on the spot from proper queries (which could check from another table what the detection status is!), or we could trickle back to #2500, where we have the calculated stuff distinct from the user's input, with clearly defined semantics as to what and how creates the calculation.
I'm not sure if the problems outlied above can be fixed with the current data model AND adding this patch. We are overwriting information. Once the fix date is stamped with a different value because of a review status change, it's done and gone, no going back...

I think the best way for this would be introducing a new column. Make it explicit even in the data model that the users have the ability to override how the truth produced by the analysers is presented to them. If you want to care about what the user wants in this regard, make sure that this caring is visible in the data model already, and of course in the associated code. Maybe call it declared_fixed_at -- to show that this is a "fix time" which the user said it is fixed (even though the machine truth is not as such, of course that could be from a false positive!). And then the current fixed_at can be renamed to something else... reported_fixed_at. This is for the store command. What comes from the machine, not from the human.
And then the queries can be changed accordingly, we can have some invariants added with potentially related checks or TRIGGERs even.
But we won't be conflicting in overwriting this and that data point.

I close this PR, because the changes of this patch is now the part of #3580. The modifications suggested in this comments are also introduced in the other PR.


Minor performance improvement for SA1211

In case if aliases should be reordered, current implementation search in list of
processed aliases where current alias should be placed. Search begins from the
beginning of list. We can improve this search making lookup from the end.

I think the discussion of #828 applies here as well. In my opinion we should just report a generic message and leave the ordering to the user or the codefix in #650, thereby simplifying the code here a lot.

@sharwell thoughts?

Seems like we could make a base class for all the using declaration analyzers, which just asks the question:

Should the current using declaration appear after the next using declaration? If so, a diagnostic gets reported for the current using declaration.

Such a base class could easily handle the preprocessor conditions described in #866 by simply not calling the comparison method if a preprocessor line appears between the two.


Swagger specification and examples for Service Fabric Mesh 2018-09-01-preview release.

Swagger specification and examples for Service Fabric Mesh 2018-09-01-preview release.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[X] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] The spec follows the guidelines described in the Swagger checklist document.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Can one of the admins verify this patch?

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go


dmrconfig: 1.0 -> 1.1

Motivation for this change
Changes: https://github.com/sergev/dmrconfig/releases/tag/1.1
Also removed some half shady replacements and supplied arguments for the same purpose.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

LGTM, thanks!


👑 Readonly B-Tree SST index

Description
Implement a readonly B-Tree SST index instead of the current flat one.
This improvement opens us the possibility of not always needing to keep SST's indexes in memory. We will be able to store a large amount of "cold" data without dozens of compute nodes to load needed parts of indexes on demand. Also enhances stability of Shared Cache and removes (actually reduces) passive bytes segment.
As we write a SST during the compaction process, its indexes will be readonly. However, the B-Tree structure minimizes needed disk I/O operations.
Also we will extend the current index format with additional information about data size and erased row count which will allow us to navigate easily and count statistics without the need of fully loading the whole index into memory.
Internal design doc
Steps
1. Support simple flat index loading in all the usages
Instead of loading all SST's indexes on a tablet start, do it on the first usage. Before that loading keep memory free.

[x]  Add and implement an index IIndexIter interface that loads index on the first usage https://github.com/ydb-platform/ydb/commit/66a3bbb229cb89b2af275fd583259d3a47e215b4
[x]  Support index loading in TRunIt https://github.com/ydb-platform/ydb/commit/66a3bbb229cb89b2af275fd583259d3a47e215b4
[x]  Support index loading from IPages implementations https://github.com/ydb-platform/ydb/commit/aab08a6fe3bcdbe14fa7e61c38825fecd152b7a0 https://github.com/ydb-platform/ydb/commit/10fe9530d0a2328e2b7bd4c081dfaf58fc2ee525
[x]  Support index loading inTCharge https://github.com/ydb-platform/ydb/commit/55d8ae0f29a754250bb75958428dfe3b543cdaf9
[x] Support index loading in TKeysLoader https://github.com/ydb-platform/ydb/commit/0f2a2ff24b46998fe341a18f0ac90a2d722249fa https://github.com/ydb-platform/ydb/commit/bac30c7bd7a0129d6f9d8b76dfee813f615573fe
[x] Support index loading in BuildStats https://github.com/ydb-platform/ydb/commit/287b4bb4d2239bb7555407d03950d323ebf0edce https://github.com/ydb-platform/ydb/commit/a18f54585040aedbeeebd9d1cdcc1950146ae81a
[x] Support index loading in TForward https://github.com/ydb-platform/ydb/commit/5ad1dcc7936525dc6742bcbf855e291cc71dbda4 https://github.com/ydb-platform/ydb/pull/657
[x] Support index loading in TDump https://github.com/ydb-platform/ydb/commit/cc271cdcd8792ac27caefcbe45c7349ccd5b5765
[x] Remove the rest direct usages of index fields from TPart https://github.com/ydb-platform/ydb/commit/16b0f8d9f0fba37ed662509e8f20577aa073ca48
[x] Do not count flat index pages in transaction usage https://github.com/ydb-platform/ydb/commit/e4592d6bd86384da2667f8399b41ca65858f3ee8
[x] Do not load index on tablet start https://github.com/ydb-platform/ydb/commit/bcae19f0ae90c93d0ab978ef1b4e516053f19535

2. Implement readonly B-Tree index
Implement B-Tree data structure, build and write them with an SST, implement searches.

[x] Implement B-Tree node class with serialization and deserialization to binary pages format https://github.com/ydb-platform/ydb/commit/cf4d301c44398f63b387618472918acfff0dc87c
[x] Implement B-Tree builder that accepts data pages and writes B-Tree nodes online https://github.com/ydb-platform/ydb/commit/523950c2b381cefddbfee36b9d788ea420964b76
[x] Integrate B-Tree builder with TPartWriter https://github.com/ydb-platform/ydb/commit/1ccc8508988675ed855c7cf27474d5b660098822
[x] Optimize B-Tree node format for groups where all row records have the same size https://github.com/ydb-platform/ydb/commit/4c94e44e7808c0b62370bee78c216fd131216d8c https://github.com/ydb-platform/ydb/commit/ebe7a9b148efe82f86ed8ee5efbc3c3d40ef5833
[x] Implement search by row id https://github.com/ydb-platform/ydb/commit/402da95804025c14d23aef3aad037797381bed0d
[x] Implement search by key https://github.com/ydb-platform/ydb/commit/1eda4dd4f9ac1ba457c1b73a9ce9cb450f50b132
[x] Implement next and prev methods that can handle page faults https://github.com/ydb-platform/ydb/commit/2f7d8b6e692bd7584a66686b5504381631dd4522
[x] Integrate TRunIt with a new B-Tree index iterator (TPartBtreeIndexIt) https://github.com/ydb-platform/ydb/commit/2f7d8b6e692bd7584a66686b5504381631dd4522
[x] Add EnableLocalDBBtreeIndex setting https://github.com/ydb-platform/ydb/commit/ba6b7d6c666b8a304518ccc1c8e9a0daec8df47a
[x] Integrate TKeysLoader with a new B-Tree index iterator https://github.com/ydb-platform/ydb/commit/897ada7941ae63332514c27e676d2f70edc3c13b

3. Implement Precharge over readonly B-Tree index
Implement Precharge that works over tree structured index instead of the old flat one.

[x] Add ICharge interface and extract ChargeRange methods https://github.com/ydb-platform/ydb/commit/e7f64cc383ca087378ff3edb8b833360561445a7 https://github.com/ydb-platform/ydb/pull/682
[x] Charge main pages within given row id range https://github.com/ydb-platform/ydb/pull/754
[x] Charge main pages within given key range https://github.com/ydb-platform/ydb/pull/1102
[x] Charge groups pages https://github.com/ydb-platform/ydb/pull/1224
[x] Treat items limit https://github.com/ydb-platform/ydb/pull/1338
[x] Treats bytes limit https://github.com/ydb-platform/ydb/pull/1489
[x] Charge history pages https://github.com/ydb-platform/ydb/pull/1593
[x] Bugfix partially-loaded tree https://github.com/ydb-platform/ydb/pull/1674
[x] Check that Iterator and Charge behaviour are consistent (all needed pages are precharged) https://github.com/ydb-platform/ydb/pull/1869

4. Implement Build Stats over readonly B-Tree index
Implement Build Stats that works over tree structured index instead of the old flat one. We expect that it will no longer need to fully load index and only use upper-level B-Tree index nodes.

[x] Implement basic version https://github.com/ydb-platform/ydb/pull/1949 https://github.com/ydb-platform/ydb/pull/2136
[x] Improve it not to load all index nodes https://github.com/ydb-platform/ydb/pull/2177

5. Implement Scan over readonly B-Tree index
Implement Scan that works over over tree structured index.

[x] #2260

6. Make fixes
Manually check suspicious places and fix what is broken with B-Tree index.

[x] Fix sticky pages logic after table compaction https://github.com/ydb-platform/ydb/commit/dda26179eda44bc3694bcfe1e61554baa2f44b72
[x] Keep B-Tree index in memory after compactions https://github.com/ydb-platform/ydb/pull/1165
[x] Fix B-Tree index iterator behaviour with corner pages https://github.com/ydb-platform/ydb/pull/995
[x] Bugfix TSchemeShard::Clear method https://github.com/ydb-platform/ydb/pull/655
[x] Count flat or B-Tree index to index size depending on EnableLocalDBBtreeIndex setting https://github.com/ydb-platform/ydb/pull/653 https://github.com/ydb-platform/ydb/pull/671
[x] #2546
[x] #2547
[ ] TBD

6. Test
Verify that everything works together not dramatically worse than before. Make tests on a slice.

[x] Benchmark TRunIt over B-Tree index https://github.com/ydb-platform/ydb/pull/653
[x] Benchmark Charge over B-Tree index https://github.com/ydb-platform/ydb/pull/1869
[ ] Check large table with a small amount of Shared Cache
[ ] Check YCSB benchmark
[ ] Check TPC-C benchmark
[ ] Check that EnableLocalDBBtreeIndex and EnableLocalDBFlatIndex settings work
[ ] Check that our changes do not effect Hive balancing (in mem size)
[ ] ❗ Check that current Shared Cache behaviour is OK with B-Tree index nodes (if it isn't we have to mark them Sticky as before)
[ ] TBD

7. Make optimizations

[ ] Optimize Next and Prev methods short path when we already have requested page in a loaded node (and maybe Seek methods too)
[ ] ❓ Optimize page loading and copying TSharedData
[ ] ❓ Do not allocate in CreateIndexIter https://github.com/ydb-platform/ydb/pull/2514#discussion_r1519564636
[ ] Position to given PageId without multiple Next calls in Scan
[ ] Forward-load B-Tree index in Scan
[ ] TBD

8.


Remove failure from integration test

The failure crate has been deprecated and the integration failure no longer gets fixed, so removed.
This also clean-ups Git repo URLs in integration tests.
Signed-off-by: Yuki Okushi<EMAIL_ADDRESS>

Given that the failure README mentions Anyhow and thiserror as near drop in replacements do you think it would be best to replace checking failure with those crates instead of just removing failure?

If we accept a personal crate, I'm happy to! But the current list only contains rust-lang (previously) official projects, I guess?

@calebcartwright what are your thoughts on replacing the failure with Anyhow and thiserror in our integration tests?


Mautic.org site documentation UX scroll case (incorect scroll position).

@Techmind commented on Thu Dec 20 2018
Not sure, that this is the right place for this sort of issue.
Loom video explaining: https://www.useloom.com/share/207dd7c3cbde4f1d8f3e560698e57455
Bug Description
Text description:
Trying to read the documentation on site is irritating because then you click on the link at the side menu  (table of contents) scroll stays at the same height.
Browser: Chromium Version 67.0.3396.99
OS: Ubuntu 16.04
Steps to reproduce

Go to https://www.mautic.org/docs/en/index.html
Click '6.1.2. Bounce Management'
A page opens with scroll position at the middle of the page

Expected:
3. A page opens with scroll position at the top of the page

@npracht commented on Thu Jan 03 2019
@escopecz with beta of github you might be able to move the issue to mautic/documentation repo. Could you ? :)

This is still an issue and I think it's a quirk of Gitbook. I don't know enough about the current implementation of GitBook as to whether it's something we can address, but will do a bit of digging. It is indeed super annoying!

Closing this issue down as it's no longer relevant due to new docs portal :+1:


Smoke tests freetypeOnlyBundledOnWindowsAndMacOS failed with alpine jdk 16

Smoke tests freetypeOnlyBundledOnWindowsAndMacOS failed with alpine jdk 16
https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk16u/job/jdk16u-alpine-linux-x64-hotspot_SmokeTests/4/console
20:26:12  FAILED: freetypeOnlyBundledOnWindowsAndMacOS
20:26:12  java.lang.AssertionError: Expected libfreetype not to be bundled but it is. expected [0] but found [1]
20:26:12  	at org.testng.Assert.fail(Assert.java:96)

Is this expected @adamfarley

Same issue to jdk16 aix openj9:
https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk16u/job/jdk16u-aix-ppc64-openj9_SmokeTests/4/console
jdk11 aix openj9 passed.
https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-openj9_SmokeTests/4/console

@sophia-guo - We only expect freetype to be bundled on Windows and Mac, to my knowledge. I hadn't heard about alpine or aix bundling it.

Not sure about alpine, but the aix one looks like a genuine bug. Will investigate why we're bundle freetype there.
I mean, we don't bundle it on jdk11u for aix.

Odd. We specify --skip-freetype on both jdk11u and jdk16u, however...
On jdk11u we see this:
19:18:04  checking for FREETYPE... yes
19:18:04  checking for freetype... yes (using pkg-config)
19:18:04  Using freetype: system

And on jdk16u we see this:
00:36:16  Using freetype: bundled

Which is...odd.
Did the default behaviour change to "bundled" on JDK16? No, because then it's be happening on linux too, and it doesn't.
Could it be that the system freetype is missing on one of our aix machines, and we default to building our own "bundled" freetype when that happens? Unknown, will check build history and consult those with machine access.

Conclusions for the 2 platforms we're seeing this issue on:
**AIX (JDK16) **
For JDK13 and upwards, OpenJDK defaults to using a bundled freetype on aix builds (in addition to Windows and Mac).
Evidence: https://bugs.openjdk.java.net/browse/JDK-8218046
Unless we plan to override this, we'll need to update the test. I'll probably change the name too.
Alpine
Adopt requires a bundled freetype in the config args for Alpine builds.
This is because we don't specify the --skip-freetype option when calling makejdk-any-platform.sh, which (in turn) is because we don't include --skip-freetype in alpine-linux.sh.
So it could be a deliberate omission, or it could be accidental.
Based on [this comment}(https://github.com/AdoptOpenJDK/openjdk-docker/issues/529#issuecomment-811403244), I think it was an accident, as it seems to state that we shouldn't be bundling freetype on alpine.
Summary
I'm going to create seperate PRs for these issues, given the disparate nature of the fixes. Will update with links after my next meeting

AIX PR: https://github.com/AdoptOpenJDK/openjdk-build/pull/2585
Alpine PR: https://github.com/AdoptOpenJDK/openjdk-build/pull/2587
Also, in the process of handling this defect, I noticed that it's theoretically impossible to set the freetype lib directory manually on Windows. It's a simple fix, so I created a [PR for that too](Improvement PR: https://github.com/AdoptOpenJDK/openjdk-build/pull/2588). This isn't a priority though, and can wait till after the release. This issue can be closed before it's complete too, just mentioning it here to link things together.

Closing this as resolved.


Review of automatic MP2RAGE segmentation

After implementing a fix for #22, we need to identify what subjects need a manual segmentation:

sub-MPI1_UNIT1 has no visible contrast between the cord and the CSF, so I'm using the inv-1_part instead, with sct_deepseg:

I wanted to do the same strategy for sub-MPI2 but I ran into #48


Can not show toast on Android anymore...

As I tested lately, this lib can not show toast on android anymore, but iOS work ok.... With the newest flutter

@jinfagang Can you please let me know the flutter version and its channel

For sure:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v1.7.8+hotfix.4, on Mac OS X 10.14.6 18G71a, locale en-CN)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
[✓] iOS tools - develop for iOS devices
[!] Android Studio (not installed)
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

And my android version is android 7

I had met it before , caused by the Exception: MissingPlugin...
Finally I try to restart the project  and  it works.

@DMingOu  I can not seen any crash log, this plugin works perfect before, but broken when I upgrade my flutter. What do you mean restart project? It's cache problem?

@jinfagang I have tried to replicate your problem but its working fine myside
try these steps
uninstall your apk from device
flutter clean
flutter run -v

@PonnamKarthik I think it's mainly because of flutter version, did u tested with flutter version of master? (I posted above in flutter doctor)

@jinfagang I have tested it in beta version


mysql-async.js error on server

mysql-async.js error on server boot
Error: (node:19044) UnhandledPromiseRejectionWarning: Error: No valid connection string found
at parseConnectingString (mysql-async.js:5036:18)
at global.on (mysql-async.js:5043:18)
at citizen:/scripting/v8/main.js:193:28
Error: (node:19044) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
Error: (node:19044) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
need help to fix error
thank you
milo

Error: No valid connection string found

i fix the error.
i was using this in the server config
set mysql_connection_string “addr=<IP_ADDRESS>;uid=username;database=essentialmode;pwd=password”
and i changed to this code and all worked
set mysql_connection_string “server=<IP_ADDRESS>;database=essentialmode;userid=username;password=password”
thanks for the help i fix it my self


Only set data_div at the very end.

I'm trying to scratch my brain for the real reason I added the lock, I think it had something to do with the Lean 3 infoview being left in a stale state if a replay was interrupted, but I think the dummy div used when setting loading makes it unnecessary. So I suppose you can ignore all of my cries to revert<PHONE_NUMBER>aa3142a0b52d7dcae9c71c1d32b539 and we can do without the lock for now by simply avoiding concurrently modifying data_div :P
Should close #142 by fixing the race condition that I think caused it, but I'm pretty pinched on time this week so more a bit more testing would be appreciated!
Also something unrelated I noticed is that the blue highlights don't work anymore? Not sure if this was intentional.

This approach feels more reliable than the lock.  It is less likely to get into an unrecoverable crashed state, compared to the lock which needs to be released manually (and where the release could be prevented by an exception).

Lean 3 infoview being left in a stale state if a replay was interrupted

Why are we doing replays in Lean 3 in the first place?  The Lean 3 server keeps track of the widget state, so we shouldn't have to do anything there.

Also something unrelated I noticed is that the blue highlights don't work anymore? Not sure if this was intentional.

That's probably my fault.  The highlights didn't work in the GUI at all (because only terminal colors were specified), so I replaced them by similar-looking links: https://github.com/Julian/lean.nvim/commit/d364e021f9b279e1f4d8226836d44ab542fb2a73  (I am not sure if hardcoding the colors is a good idea in general, because they need to work with different light and dark themes.)
I did test the new highlights but I probably missed something then.  Which highlight is broken for you?

Why are we doing replays in Lean 3 in the first place?

Undo has three steps:

Remove the last item from the undo stack
Clear everything by triggering any clear events until none are left
Replay the undo stack

This was more useful particularly in Lean 3 when tooltips were still inline.

Oh wow.  It's amazing that you got this working at all.
Strategically, I think it's more useful to focus on Lean 4 functionality.  It's acceptable that Lean 3 undo is a bit brittle if it means that the Lean 4 infoview doesn't hang.


Ignore telemetry from Registry integration tests

/kind bug

Which area this bug is related to?

/area registry
What versions of software are you using?
N/A
Bug Summary
Describe the bug:

There are a number of events generated from an unknown "user".  We have CLI commands that can be invoked against our registry library I confirmed with John that the registry integration tests are the only ones using it.
To Reproduce:

Login to our Woopra account and note the events from a user called "user"
Expected behavior

We should not be collecting telemetry from our integration tests.  We should ignore them
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.

Additional context

Any workaround?

Suggestion on how to fix the bug

We should set the ENABLE_TELEMETRY environment variable to false

The ENV var is actually set to false by default.  The problem was our download test was being run against the prod registry which has telemetry enabled.  We should be running these tests against the staging registry server.


aks: drop x-ms-external settings

This pull request fixed the .NET SDK generation by renaming the pod identity provisioning error object to ManagedClusterPodIdentityProvisioningError. The definition of this object is identical to CloudError. This change unblocked the .NET SDK generation.

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

The .NET SDK generation failure here is due to another known issue, we could ignore.

As discussed, separate PR will be opened targeting main. The fixes will also be keeping the CloudError definition for the reference property but switch to common ErrorResponse definitions for all defaults. This way no service code would be impacted.


Internal server error: Header name must be a valid HTTP token [":path"]

Describe the bug
When using vite-plugin-ssl with server.proxy, the following error appears on the server:
Internal server error: Header name must be a valid HTTP token [":path"]

It seems to be a regression of #484, but not really: workaround for #484 is still there, and I can see clearly from error stack that node:https is being used as opposed to node:http2, but it STILL doesn't do the trick.
Reproduction
StackBlitz crashes with SSL repros :(
Steps to reproduce
import { defineConfig } from 'vite';
import basicSsl from '@vitejs/plugin-basic-ssl';

export default defineConfig({
  plugins: [basicSsl()],
  server: {
    proxy: {
      '/api': {
        target: 'https://example.com',
        secure: true,
        changeOrigin: true,
      },
    },
  },
});

System Info
System:
    OS: macOS 14.1.1
    CPU: (8) arm64 Apple M2
    Memory: 59.30 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.9.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-7e9663ff/node
    Yarn: 4.0.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-7e9663ff/yarn
    npm: 10.1.0 - /usr/local/bin/npm
    bun: 1.0.12 - ~/.bun/bin/bun
  Browsers:
    Chrome: 119.0.6045.159
    Edge: 119.0.2151.72
    Safari: 17.1

Used Package Manager
yarn
Logs
10:36:58 [vite] Internal server error: Header name must be a valid HTTP token [":path"]
      at ClientRequest.setHeader (node:_http_outgoing:654:3)
      at new ClientRequest (node:_http_client:286:14)
      at Object.request (node:https:378:10)
      at Array.stream (file:///node_modules/vite/dist/node/chunks/dep-T98iZFpD.js:56517:74)
      at ProxyServer.<anonymous> (file:///node_modules/vite/dist/node/chunks/dep-T98iZFpD.js:56831:22)
      at viteProxyMiddleware (file:///node_modules/vite/dist/node/chunks/dep-T98iZFpD.js:57133:23)
      at call (file:///node_modules/vite/dist/node/chunks/dep-T98iZFpD.js:42848:7)
      at next (file:///node_modules/vite/dist/node/chunks/dep-T98iZFpD.js:42792:5)
      at cors (file:///node_modules/vite/dist/node/chunks/dep-T98iZFpD.js:43320:7)
      at file:///node_modules/vite/dist/node/chunks/dep-T98iZFpD.js:43356:17

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@wojtekmaj Would you create a reproduction and create a GitHub repository instead of stackblitz?

Sorry, my bad - I dug deeper and found out it's actually a problem with a tool that builds on top of Vite. Apologies for the noise!


"Auto" set maxIOB for safety

From the early days of OpenAPS, we designed around making sure that no one would turn on a rig without knowing what they're doing and inadvertently cause themselves harm. This included setting maxIOB to 0, meaning the rig would essentially be in predictive low glucose suspension mode (and only high temp until maxIOB returned to zero).
However, there are two scenarios where this may be inadvertently causing worse outcomes:

New users will mistakenly not set maxIOB, wonder why BG is high and the rig isn't doing anything to help them.
Previous users, when running oref0-setup.sh, will forget to re-change maxIOB and go for several hours until they discover it's not high temping as expected based on settings from pre-runagain.

Proposal:
Upon initial setup and runagain, set maxIOB to be "auto", unless a value is otherwise specified (as usual) in preferences.json. The manually set value would override auto mode. "Auto" maxIOB would be equal to 1 hour of the current basal rate at any given time. (i.e. Basal of 0.3U/hr: maxIOB would be 0.3U. Basal of 1.2U/hr: maxIOB would be 1.2U.)

This is an excellent idea. I'd even have a 'preserve settings' option which would keep all settings in preferences.json provided they are compatible with the update.

I don't like it.  I think a reminder to verify that max_iob is set correctly at the end of oref0-setup.sh would be more appropriate, although I have definitely been bitten by the second bullet point before.  It feels like I would be less likely to notice in incorrect setting this way.  At the very least I'd like to see the fact that max_iob is being automatically determined indevicestatus.json's reason string for a little extra visibility.

Should we make max_iob a required field during oref0-setup?

I'd prefer that.  At least it would be explicit.

@scottleibrand @mgranberry - all the seconds possible on having it be in the setup script.

I'd be fine now having it asked & answered in setup script, too.

Ok, I think I'd be fine with that, too.  Maybe we can add some verbiage suggesting people start with max IOB equal to their normal basal or something like that, to discourage people from putting in a really high value that basically disables it...

@scottleibrand let's fold it in with the other de-advancing-features branch oref0-setup.sh to test them all together (vs the original separate branch we were intending)

This is ready alongside some other oref0-setup.sh changes that are awaiting some 👍's before merging to dev: https://github.com/openaps/oref0/pull/486

trying it... does this branch include oref1 stuff as well?

Yes, this branch is based off of dev, so you can enable oref1 features the same way you would there.

should the script have asked me for maxIOB?
I got a 0 value

@tomasboudr see https://github.com/openaps/oref0/pull/486#issuecomment-305347753

I used the de-advanced-features branch.. was that correct?

ha. nope. see this PR (https://github.com/openaps/oref0/pull/486) - it's the auto-maxIOB branch that I ended up doing all the work on. waiting to pull a few things from de-advancifying features branch in before deleting that. sorry for confusion!

Got it. Tested and it worked +1!
On Wed, May 31, 2017 at 7:40 PM, Dana Lewis<EMAIL_ADDRESS>wrote:

ha. nope. see this PR (#486 https://github.com/openaps/oref0/pull/486)

it's the auto-maxIOB branch that I ended up doing all the work on.
waiting to pull a few things from de-advancifying features branch in before
deleting that. sorry for confusion!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openaps/oref0/issues/475#issuecomment-305348482, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAJh282xrkVbCJBs_GtTOOFrFugtwSh8ks5r_fpjgaJpZM4Nhf2K
.

Implemented in dev with https://github.com/openaps/oref0/pull/486. Closing as an issue.


Windows 10 Exchange Error 502

I've tried for about a month now to make this transaction but it fails with this error 502 message every time.

we have improved the error messages for the exchange service. If this is still effecting anyone we can reopen


Global animation feature

About this, what I want is to be able to add multiple animation to a single entity.
Each animation would be identified by a String, and each animation would be composed of :
duration (total duration of the animation)
keyframe_number (number of desired keyframes)
vec (modifiers to apply to the current entity
cycle (whether or not this anim is a cycle)
The player would be able to launch any animation by requesting the component 'Animations' like this :
world.entry(hero).unwrap().get_component_mut::<Animations>().unwrap().start("run");


sample_weight taking long to initialize

Issue type
Performance
Have you reproduced the bug with TensorFlow Nightly?
No
Source
binary
TensorFlow version
2.12.0
Custom code
Yes
OS platform and distribution
Linux Ubuntu
Mobile device
No response
Python version
3.10.12
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
When training a keras model on in-memory data (e.g., numpy arrays or pandas DataFrames) and simultaneously providing the sample_weight parameter in fit, the initialization takes very long (ca. 5 minutes with 1 Mio. examples). This problem amplifies when the number of examples increases.
Standalone code to reproduce the issue
import tensorflow as tf
from tensorflow import keras
import numpy as np

x_train = np.random.rand(10000, 10)
y_train = np.random.rand(10000, 1)
w_train = np.random.rand(10000, 1)

def run(with_sample_weights=True):
  model = keras.Sequential()
  model.add(keras.layers.Dense(64, input_dim=x_train.shape[1], activation='relu'))
  model.add(keras.layers.Dropout(0.1))
  model.add(keras.layers.Dense(64, activation='relu'))
  model.add(keras.layers.Dropout(0.1))
  model.add(keras.layers.Dense(64, activation='relu'))
  model.add(keras.layers.Dropout(0.1))
  model.add(keras.layers.Dense(64, activation='relu'))
  model.add(keras.layers.Dropout(0.1))
  model.add(keras.layers.Dense(1, activation='sigmoid'))
  model.compile(loss='binary_crossentropy', optimizer='adam', metrics=['accuracy'])

  if with_sample_weights:
    model.fit(x_train, y_train, sample_weight=w_train)
  else:
    model.fit(x_train, y_train)

import time

start = time.time()
for i in range(10):
  run(True)
end = time.time()
print(end - start)

start = time.time()
for i in range(10):
  run(False)
end = time.time()
print(end - start)

Relevant log output
For 10,000 examples: 31s vs 14s
For 1,000,000: 1253.8s vs 17.1s

From own investigation (so far only tested on tf/keras in version 2.12.0), the implementation of handle_partial_sample_weights in training_utils.py is inefficient. In my case (sample_weight is a dense numpy array with shape (1000000,) and all entries filled/non-null) the following lines were causing the bottleneck.
I suggest exchanging lines 77-78 with any_sample_weight = sample_weights.numpy().any() and exchanging lines 79-80 with partial_sample_weight = sample_weights.numpy().all().
In my case, handle_partial_sample_weights was called from here.
Please let me know if this could have side effects in case of other usage patterns.

FYI: Issue was also discussed for standalone keras here and here.

@jubebo,
I tried to execute the mentioned code on tensorflower v2.17 which contains keras3.0, and observed that the time taking is lesser when compared to tensorflow v2.12. Kindly find the gist of it here.
Also please try to use the latest tensorflow v2.17 and as this issue is more related to keras, raise the issue in keras-team/keras repo for the quick resolution. Thank you!


Replace "time" references with self._dim in class TemporalAccessor

Description

This PR updates incorrect static references to "time" as the name of the time dimension with the dynamic self._dim dimension name.

Closes #311

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

If applicable:

[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass with my changes (locally and CI/CD build)
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

Codecov Report

Merging #312 (d60649b) into main (4c51879) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #312   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1170      1170
=========================================
  Hits          1170      1170

Impacted Files
Coverage Δ

xcdat/temporal.py
100.00% <100.00%> (ø)

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

Related #285, we might need to update how we get the dimension name for a time axis (self._dim) in TemporalAccessor().
Instead of getting the time dimension name from the dataset (which can have multiple time axis):
https://github.com/xCDAT/xcdat/blob/4c51879a65992e08b29eabd2d31f7332aca78e61/xcdat/temporal.py#L149
We can get the just the single time axis for the data variable that is being temporally averaged:
self._dim = get_axis_coord(self._data_var, "T").name


Tags translation

don't know if it's the place to say
but is there's a way to make an English translation beside every Japanese tag?

Added in v3.0.0


formTemplate option missing

I used this option to customize my button labels and placement, why not getting it back ?

Hi,
I am trying to change the label of the buttons( suppose 'cancel' -> 'clear'). Is there any way I can overwrite the labels. Also, does this support string externalization, meaning if I change the browser language to say french, the button label should change to that language.. currently it stays in English.
Thanks!


Deprecate HVPA and HVPAForShootedSeed feature gates

How to categorize this PR?

/area auto-scaling
/kind enhancement
What this PR does / why we need it:
This PR is a continuation of #10599 and deprecates the HVPA and HVPAForShootedSeed feature gates. Additionally, it also locks them to false.
The related code will be cleaned up when the feature gates are completely removed (planned for the v1.107 release).
Which issue(s) this PR fixes:
n/a
Special notes for your reviewer:
Release note:

The `HVPA` and `HVPAForShootedSeed` feature gates have been deprecated and locked to false. Disable the `HVPA` and `HVPAForShootedSeed` feature gates if you have them enabled before upgrading to this version of Gardener.

  [FAILED] Expected success, but got an error:
      <*errors.StatusError | 0xc001318a00>:
      Operation cannot be fulfilled on managedresources.resources.gardener.cloud "e2e-test-node-critical": the object has been modified; please apply your changes to the latest version and try again
      {
          ErrStatus: {
              TypeMeta: {Kind: "", APIVersion: ""},
              ListMeta: {
                  SelfLink: "",
                  ResourceVersion: "",
                  Continue: "",
                  RemainingItemCount: nil,
              },
              Status: "Failure",
              Message: "Operation cannot be fulfilled on managedresources.resources.gardener.cloud \"e2e-test-node-critical\": the object has been modified; please apply your changes to the latest version and try again",
              Reason: "Conflict",
              Details: {
                  Name: "e2e-test-node-critical",
                  Group: "resources.gardener.cloud",
                  Kind: "managedresources",
                  UID: "",
                  Causes: nil,
                  RetryAfterSeconds: 0,
              },
              Code: 409,
          },
      }
  In [It] at: /home/prow/go/src/github.com/gardener/gardener/test/e2e/gardener/shoot/internal/node/node.go:86 @ 10/16/24 14:03:35.928

/test pull-gardener-e2e-kind-ha-single-zone


Missing ToggleFullScreenButton ?

The Fullscreen button is missing and the file ToggleFullScreenButton.tsx has been removed.

Thanks for the issue @baj84!
The full screen button was intentionally removed from the app.
The app can still be run in a full screen window. You can press command + shift + F in MacOS, or F11 in Windows.
Alternatively you can click on this button in the Chrome menu:

Thanks @timmydoza - Can I check why it was removed? Getting users to click into a Chrome menu or use a keyboard shortcut unfortunately isn't an option.

It was removed to make room for other things - and because it's possible to make the app fullscreen using the methods I listed above.
Just curious - why is using the chrome menu or keyboard shortcuts not an option for you?

Ah! Do you know which commit it was removed from? I'd like to put it back in.
It's not an option purely because of the user experience. All our customers are non-tech (maybe even 60+), so trying to put instructions for shortcuts or chrome menus will be confusing to them. I'd much rather just a single icon they can click.


Intermittently lost HTTP/GRPC responses

Bug Description
This might be linked to a (somewhat) similar issue we're having, https://github.com/envoyproxy/envoy/issues/17722.
We are very occasionally seeing responses being dropped or lost(?) in our clusters. In the below screenshot you can see an HTTP request going from the Ingressgateway to one of our services.
For complete clarity, the headers you can see are the following from https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access_log/usage#command-operators:
start_time: %START_TIME%
path: %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%
duration: %DURATION%
request_attempts: %REQ(X-ENVOY-ATTEMPT-COUNT)%
reponse_flag: %RESPONSE_FLAGS%
reponse_code: %RESPONSE_CODE%
timestamp is when the log was emitted, so more or less the end of the request.

This is filtered on a particular request_id, and as you can see, the Ingressgateway thinks that the first request times out after 9 seconds (which is the configured per_try_timeout) and it retires to a different Pod (see pod_id). This request is also treated as if it timed out after 9 seconds. It then returns UT, URX and 504.
The service is a NodeJS express server. Normal HTTP, and looking at the bytes sent and response_code from the Istio-sidecar logs it's sending replies just fine.
We have seen similar things happen with GRPC-Web requests and assumed it was something related to the Envoy plugins or similar. But we are also seeing it happen for good old HTTP now. I am quite stumped as to what to do next.
Please let me know if you want any other information here as I don't really know what to provide and I can't attach the full istioctl bug-report as that contains a lot of internal information.
Version
Istio:
client version: 1.11.0
control plane version: 1.11.0
data plane version: 1.11.0 (68 proxies)

We are running on **AKS** in Azure.

Kubernetes:
Client Version: v1.20.0
Server Version: v1.19.11

Additional Information
Relevant config snippet from istioctl pc all -nistio-system istio-ingressgateway -oyaml this particular service and route:
        - decorator:
            operation: serviceA.default.svc.cluster.local:8880/accounts/.*/projects
          match:
            case_sensitive: true
            safe_regex:
              google_re2: {}
              regex: /accounts/.*/projects
          metadata:
            filter_metadata:
              istio:
                config: /apis/networking.istio.io/v1alpha3/namespaces/default/virtual-service/serviceA
          route:
            cluster: outbound|8880||serviceA.default.svc.cluster.local
            cors:
              allow_headers: authorization,content-type,r-p,r-cs,x-user-agent,x-grpc-web
              allow_methods: GET,POST,PUT,DELETE,HEAD,OPTIONS
              allow_origin_string_match:
              - exact: '*'
              expose_headers: grpc-message,grpc-status
              filter_enabled:
                default_value:
                  numerator: 100
              max_age: "7200"
            max_grpc_timeout: 20s
            retry_policy:
              host_selection_retry_max_attempts: "5"
              num_retries: 1
              per_try_timeout: 9s
              retry_host_predicate:
              - name: envoy.retry_host_predicates.previous_hosts
              retry_on: 5xx
            timeout: 20s

I'm not sure what config I can provide from the Service's side in regards to it connecting to the Ingressgateway.

This is continuing to happen in our production environment. We just had a ~20 minute window where a browser client got stuck in a "bad session" and was continuously getting 504'd despite the services responding within 10s of milliseconds.

As you can see in our logging system, it's all from the same Downstream IP (one user, one browser session) but the ports differ throughout. So the browser is presumably establishing new connections to the load balancer? But they're all still stuck in this way.
There were other users making calls at this time and they did not have this problem.

We get this problem too. But ours happens between services. Once we rollout client, it will recover temporarily.  :scream:


Implement type filter for show wallet detail

WHY
The type arg passed into showWalletDetails not in use, it will always show both ft and nft atomicals.
Consideration
A type filter could be very useful for user who rely on cli to display their large amount of atomicals. Implement the functionality for summary only output.
Highlighted it's not compatible with showExtra, showBalancesOnly

@atomicals 👀


[WIP][SPARK-22339] [CORE] [NETWORK-SHUFFLE] Push epoch updates to executors on fetch failure to avoid fetch retries for missing executors

What changes were proposed in this pull request?
When a task finishes with error due to a fetch error, then DAGScheduler unregisters the shuffle blocks hosted by the serving executor (or even all the executors in the failing host, with external shuffle and spark.files.fetchFailure.unRegisterOutputOnHost enabled) in the shuffle block directory stored by MapOutputTracker, that then increments its epoch as a result. This event is only signaled to the other executors when a new task with a new epoch starts in each executor. This means that other executors reading from the failed executors will retry fetching shuffle blocks from them, even though the driver already knows those executors are lost and those blocks are now unavailable at those locations. This impacts job runtime, specially for long shuffles and executor failures at the end of a stage, when the only pending tasks are shuffle reads.
This could be improved by pushing the epoch update to the executors without having to wait for a new task. In the attached patch I sketch a possible solution that sends the updated epoch from the driver to the executors by piggybacking on the executor heartbeat response. ShuffleBlockFetcherIterator, RetryingBlockFetcher and BlockFetchingListener are modified so blocks locations are checked on each fetch retry. This doesn't introduce additional traffic, as MapOutputTrackerWorker.mapStatuses is shared by all tasks running on the same Executor, and the lookup of the new shuffle blocks directory was going to happen anyway when the new epoch is detected during the start of the next task.
I would like to know the opinion of the community on this approach.
How was this patch tested?
Unit tests, tests in Yarn cluster

Can one of the admins verify this patch?

Jenkins, ok to test

Test build #83136 has started for PR 19583 at commit 7f538df.

Test build #83136 has finished for PR 19583 at commit 7f538df.

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

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83136/
Test FAILed.

how much benifit we can get here? By default the shffule block fetcher only retry 3 times, which won't be a lot of time. After shuffle block fetcher failed and we retry this task, we are fine.

Even though we only wait 5 seconds by default between retries, the retries themselves can take a lot of time. For example in a simple word count job where a node is lost during stage 1.0 I have seen the following logs for RetryingBlockFetcher:
17/09/13 23:34:23 INFO RetryingBlockFetcher: Retrying fetch (1/3) for 332 outstanding blocks after 5000 ms
17/09/13 23:34:23 INFO RetryingBlockFetcher: Retrying fetch (1/3) for 286 outstanding blocks after 5000 ms
17/09/13 23:34:23 INFO RetryingBlockFetcher: Retrying fetch (1/3) for 312 outstanding blocks after 5000 ms
17/09/13 23:34:23 INFO RetryingBlockFetcher: Retrying fetch (1/3) for 264 outstanding blocks after 5000 ms
17/09/13 23:34:23 INFO RetryingBlockFetcher: Retrying fetch (1/3) for 294 outstanding blocks after 5000 ms
17/09/13 23:34:23 INFO RetryingBlockFetcher: Retrying fetch (1/3) for 316 outstanding blocks after 5000 ms
17/09/13 23:34:23 INFO RetryingBlockFetcher: Retrying fetch (1/3) for 276 outstanding blocks after 5000 ms
17/09/13 23:34:23 INFO RetryingBlockFetcher: Retrying fetch (1/3) for 327 outstanding blocks after 5000 ms
17/09/13 23:36:28 INFO RetryingBlockFetcher: Retrying fetch (2/3) for 316 outstanding blocks after 5000 ms
17/09/13 23:38:28 INFO RetryingBlockFetcher: Retrying fetch (2/3) for 264 outstanding blocks after 5000 ms
17/09/13 23:40:28 INFO RetryingBlockFetcher: Retrying fetch (2/3) for 294 outstanding blocks after 5000 ms
17/09/13 23:42:28 INFO RetryingBlockFetcher: Retrying fetch (2/3) for 286 outstanding blocks after 5000 ms
17/09/13 23:44:28 INFO RetryingBlockFetcher: Retrying fetch (2/3) for 312 outstanding blocks after 5000 ms
17/09/13 23:46:28 INFO RetryingBlockFetcher: Retrying fetch (2/3) for 332 outstanding blocks after 5000 ms
17/09/13 23:48:28 INFO RetryingBlockFetcher: Retrying fetch (2/3) for 327 outstanding blocks after 5000 ms
17/09/13 23:50:28 INFO RetryingBlockFetcher: Retrying fetch (2/3) for 276 outstanding blocks after 5000 ms
17/09/13 23:50:31 INFO RetryingBlockFetcher: Retrying fetch (3/3) for 327 outstanding blocks after 5000 ms
17/09/13 23:50:34 INFO RetryingBlockFetcher: Retrying fetch (3/3) for 332 outstanding blocks after 5000 ms
17/09/13 23:50:37 INFO RetryingBlockFetcher: Retrying fetch (3/3) for 312 outstanding blocks after 5000 ms
17/09/13 23:50:40 INFO RetryingBlockFetcher: Retrying fetch (3/3) for 286 outstanding blocks after 5000 ms
17/09/13 23:50:43 INFO RetryingBlockFetcher: Retrying fetch (3/3) for 294 outstanding blocks after 5000 ms
17/09/13 23:50:46 INFO RetryingBlockFetcher: Retrying fetch (3/3) for 264 outstanding blocks after 5000 ms
17/09/13 23:50:49 INFO RetryingBlockFetcher: Retrying fetch (3/3) for 316 outstanding blocks after 5000 ms
17/09/13 23:51:07 INFO RetryingBlockFetcher: Retrying fetch (3/3) for 276 outstanding blocks after 5000 ms

where the job has the following stage submission and completion events
17/09/13 23:21:57 INFO DAGScheduler: Submitting ShuffleMapStage 0 (MapPartitionsRDD[2] at flatMap at WordCount.scala:64), which has no missing parents
17/09/13 23:31:34 INFO DAGScheduler: Submitting ResultStage 1 (MapPartitionsRDD[4] at saveAsTextFile at WordCount.scala:110), which has no missing parents
17/09/13 23:50:51 INFO DAGScheduler: Submitting ShuffleMapStage 0 (MapPartitionsRDD[2] at flatMap at WordCount.scala:64), which has no missing parents
17/09/13 23:52:19 INFO DAGScheduler: Submitting ResultStage 1 (MapPartitionsRDD[4] at saveAsTextFile at WordCount.scala:110), which has no missing parents

17/09/13 23:31:34 INFO DAGScheduler: ShuffleMapStage 0 (flatMap at WordCount.scala:64) finished in 575.500 s
17/09/13 23:52:19 INFO DAGScheduler: ShuffleMapStage 0 (flatMap at WordCount.scala:64) finished in 87.455 s
17/09/13 23:59:07 INFO DAGScheduler: ResultStage 1 (saveAsTextFile at WordCount.scala:110) finished in 408.167 s

This means that approximately 16 minutes of a 38 minutes job where spent in retries, which is 42% of the job time. This might impact applications that lose a node at a moment when a single action is running. For example applications with a single action at the end, for writing the application results to external storage.

instead of piggybacking the heartbeat, can we just let the driver send an event to all executors asynchronously about the node failure?

@cloud-fan I have added a new commit with a proposal to send an event with the epoch update. What do you think of that approach? Is that closer to your idea of avoiding  piggybacking the heartbeat?

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83419/
Test FAILed.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Add manual opt-out text to email template

Problem statement
Re: standup on 6/25, the automated opt-out process won't be set until we move to React. Set up a manual, email-us-to-opt-out process and update the template footer content to reflect.
To do

[ ] Re-build Foundation for Emails template
[ ] Add new html to SendGrid

Just a plug before I go to make sure it follows the RS style guide guidelines!

Template screengrab for reference:

Updated copy

ReportStream
PHD Name, State
COVID-19 test data is ready for download
View and download daily test results for Tuesday June 29, 2021 [link]
Data are available to download for 30 days after receipt of this email. Failure to download reports within 30 days may result in the loss of data.
Data aggregated with ReportStream may be subject to the Privacy Act of 1974, the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other laws, and requires special safeguarding.
Contact
<EMAIL_ADDRESS>Centers for Disease Control and Prevention
1600 Clifton Road
Atlanta, GA 30329
Unsubscribe
To unsubscribe from this list, email<EMAIL_ADDRESS>with the subject line "Unsubscribe from daily email."

Template screengrab for reference


feat(CX-2457): added myCollectionArtworkAbout context module

The type of this PR is: Enhancement

This PR resolves CX-2457
Description

Added myCollectionArtworkAbout context module
PR Checklist (tick all before merging)

[x] If I've added a new file to the tree I've exported it from the common index.ts
[ ] I've added comments with examples for any new interfaces and ensured that they're in the docs
[x] No platform-specific terminology has been used outside of click and tap (platform is inferred by the DB storing events)

I will merge this. Please, let me know some changes have to be made in this PR

:rocket: PR was released in v4.42.0 :rocket:

sounds good to me

@dariakoko I do believe you forgot to export here though https://github.com/artsy/cohesion/blob/8ca9d75f178f51d4fd3db1f59dd2efdc6f246bfb/src/Schema/Values/ContextModule.ts#L173

Hmmm, no, I didn't do this on purpose. I took the old module (sellFooter) as an example, it's not exported either.
@audrey-thenot could you take a look, please?


[SymbolGraph] Look for @_spi on extensions

Consider declarations inside @_spi extensions to be internal.
Clean up the "implicitly private" check to work for Decl and not just
ValueDecl, allowing it to be used directly on extensions instead of having to
look for extensions everywhere.
rdar://63361634

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test Linux Platform

@swift-ci Please smoke test

@swift-ci Please smoke test Linux Platform


Change way to get

Using http may call issue, changet to https. More https://getcomposer.org/doc/00-intro.md#installation-linux-unix-osx

Thanks!


Does Caduceus Support Variable-Length Inputs in Batches?

I would like to inquire whether Caduceus supports variable-length inputs within a batch. From my understanding, the original MambaBlock does not support variable-length inputs, and it seems that Caduceus continues this limitation.
For downstream tasks, such as the NT benchmark where each task sequence has different lengths, I want to confirm whether Caduceus simply models the pad tokens added by the tokenizer along with the sequences.

That is correct, variable length inputs in a batch would not work to the best of my understanding. You'd need to either truncate to shortest or pad to longest sequence in the batch.


cleanup security warnings

We can make use of pip-upgrader to fix the security warnings issued by github. This would be a one-of thing, so there's no need to include this package in the requirements.txt file. Instead, we'd manually do docker-compose up then go into the backend container, run pip install upgrader and let it do its magic with the project's requirements.txt file

looks like we're still missing some packages:

djangorestframework
urllib3
requests
django


Updated the readme image

@shaurya5 you'd have to make changes in the readme file as well and add that to your commit.


Implement insights core inside ROS

With this PR, ROS processor will be using insights-core spec and parsers for extracting performance profile data from tar archive

[x] Implement insights core in ros
[x] Change AWS sample archive

Thanks @patilsuraj767


✨ View Images and videos inside CodeEdit

Describe the solution you'd like:
Currently CodeEdit cannot open images, videos and audio.
This could be useful to many developers for logos and click sound effects. This is what happens:
https://user-images.githubusercontent.com/98705626/213851481-82ed4334-83d4-4606-9a3f-aa8489bde1db.mov
Describe alternatives you've considered
Instead of making an in-built video/image viewer there could be a setting for the preferred software to open images/videos. This could default to Quicktime Player or Preview.
Additional context
This could be a pretty easy thing to do as Swift has support to open files.

Related to #1026.
Note: the file is being opened standalone, not in a workspace.


ARROW-11547: [Packaging][Conda][Drone] Fix undefined variable error

@github-actions crossbow submit -g conda

+1


Run NixOS tests on Darwin

Issue description
It would be great to be able to run NixOS tests on Darwin. Right now building/running NixOS tests fails on Darwin when building the Linux VMs.
If one has a Linux builder available, it should be possible to:

Build the Linux VMs on the Linux builder.
Run the tests on Darwin as well as running the start scripts (for interacting with the VMs locally) using hvf instead of KVM.

My interpretation is that build-vms.nix should be tweaked. buildVM should take a Linux package set (pkgs with system = "...-linux"), and the rest of the build (driver, buildVirtualNetwork) should take a Darwin package set.
https://github.com/NixOS/nixpkgs/blob/93db55bde5ef7d405c45e76f7304eb3559e80fc4/nixos/lib/build-vms.nix#L30-L43
Then the qemu commands should be changed to use accel=hvf (instead of =kvm) on Darwin.
CC @basvandijk

You probably only need to do something like this:
         { key = "qemu"; system.build.qemu = (import pkgs.path { system = builtins.currentSystem; }).qemu; }

Everything else should be part of the actual image.

If you already have a Linux builder, then can't you just run the NixOS tests on the Linux builder?

For debugging purposes it would be nice if NixOS tests can be run interactively on darwin, i.e.:
$ nix-build my-nixos-test.nix -A driver
$ ./result/bin/nixos-test-driver

When you do this on NixOS you get a QEMU window per VM with which you interact with the VM. It would be great to have the same feature on OS X.

This would be great for testing arion on darwin.
The arion command should run on darwin but requires a linux builder and a docker host for a complete test. A NixOS test with a darwin test driver is perfect for this.

Still relevant. MacOS users should be able to interactively develop and debug NixOS tests.

One feature of Qemu that doesn't work on macOS is "virtfs" which the tests use to mount /nix/store onto the VM. We will need https://patchwork.kernel.org/patch/10468143/ to be merged to do this.

@matthewbauer I tried to apply that patch (see https://github.com/Infinisil/nixpkgs/commit/12da31367061012ba3af9e05433799386b4927eb), but the darwin build fails with that due to missing header files sys/fsuid.h, sys/vfs.h, linux/fs.h and cap-ng.h, which are probably linux specific. And of course I get compilation errors if I just try to remove those (see https://github.com/Infinisil/nixpkgs/commit/61aa1e1c4b1c0d71aefe302237e5d71b48a34d04):
fsdev/virtfs-proxy-helper.c:82:9: error: use of undeclared identifier 'CAP_CHOWN'; did you mean 'T_CHOWN'?
        CAP_CHOWN,
        ^~~~~~~~~
        T_CHOWN
./hw/9pfs/9p-proxy.h:53:5: note: 'T_CHOWN' declared here
    T_CHOWN,
    ^
fsdev/virtfs-proxy-helper.c:83:9: error: use of undeclared identifier 'CAP_DAC_OVERRIDE'
        CAP_DAC_OVERRIDE,
        ^
fsdev/virtfs-proxy-helper.c:84:9: error: use of undeclared identifier 'CAP_FOWNER'
        CAP_FOWNER,
        ^

@matthewbauer I tried to apply that patch (see https://github.com/Infinisil/nixpkgs/commit/12da31367061012ba3af9e05433799386b4927eb), but the darwin build fails with that due to missing header files sys/fsuid.h, sys/vfs.h, linux/fs.h and cap-ng.h, which are probably linux specific. And of course I get compilation errors if I just try to remove those (see https://github.com/Infinisil/nixpkgs/commit/61aa1e1c4b1c0d71aefe302237e5d71b48a34d04):
fsdev/virtfs-proxy-helper.c:82:9: error: use of undeclared identifier 'CAP_CHOWN'; did you mean 'T_CHOWN'?
        CAP_CHOWN,
        ^~~~~~~~~
        T_CHOWN
./hw/9pfs/9p-proxy.h:53:5: note: 'T_CHOWN' declared here
    T_CHOWN,
    ^
fsdev/virtfs-proxy-helper.c:83:9: error: use of undeclared identifier 'CAP_DAC_OVERRIDE'
        CAP_DAC_OVERRIDE,
        ^
fsdev/virtfs-proxy-helper.c:84:9: error: use of undeclared identifier 'CAP_FOWNER'
        CAP_FOWNER,
        ^

There's an initial prototype in #108984, so I'm closing this as a duplicate not to shut off the more recent discussion there.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/run-nixos-interactive-tests-on-aarch64-darwin/34534/1


Fix fmt:skip for function with return type

Summary
Fixes the : extraction for a function definition with a return type annotation.
closes https://github.com/astral-sh/ruff/issues/6726

Test Plan
Added a new test

Current dependencies on/for this PR:

main

PR #6733   👈

This comment was auto-generated by Graphite.


Output some query debug information

Utility functions for printing basic debug information about queries to the shell.
To use, attach a riak shell and call riak_kv_ts_util:explain_query_print/1 with a select query. The target table must exist and be activated.
Example output:
(dev1@<IP_ADDRESS>)36> riak_kv_ts_util:explain_query_print("SELECT * FROM table2 WHERE a = 1 AND b = 1 AND c >= 1999 AND c <= 5000 AND d = 'lol' AND e > 10 AND d = true").
SUB QUERY 1
>  1/1/1999/ FILTER d = 'lol' AND e > 10 AND d = true
<  1/1/2000/
SUB QUERY 2
>  1/1/2000/ FILTER d = 'lol' AND e > 10 AND d = true
<  1/1/3000/
SUB QUERY 3
>  1/1/3000/ FILTER d = 'lol' AND e > 10 AND d = true
<  1/1/4000/
SUB QUERY 4
>  1/1/4000/ FILTER d = 'lol' AND e > 10 AND d = true
<  1/1/5000/
SUB QUERY 5
>  1/1/5000/ FILTER d = 'lol' AND e > 10 AND d = true
<  1/1/5000/

I'd rather see it somewhere in riak_shell proper. Or if this needs to be in riak_kv_ts_util, it could decompose the WHERE parts into some abstract records and return that (for its callers in riak_shell to do the eventual io:format).

@hmmr I could see this be useful in other contexts as well and perhaps even introduce a QUERY PLAN-like directive

.. which is the other alternative I was suggesting: make it break down the WHERE parts and let the callers print it out directly (as riak_shell would) or process it further for other purposes.

I was thinking along the lines of an SQL EXPLAIN command. This could be extended to be an API with some riak_pb support.
For now I just need it for the dev work I'm doing though and can be deleted when proper support is available.

:+1: 57848bd

@borshop merge


adding API Version for snapshots

Which issue this PR addresses:
Relates to #1313 (quickfix, needs a proper solution for all resource types)
What this PR does / why we need it:
If List Azure Resources Geneva Action is run in a cluster which has VM snapshots in its resource group, the old code will fail due to API Version mismatch. This PR adds a snapshot specific API Version.
Test plan for issue:
I ran a List on snapshots with 2020-05-01 and it didn't fail.
also ((Get-AzureRmResourceProvider -ProviderNamespace Microsoft.Compute).ResourceTypes | Where-Object ResourceTypeName -eq snapshots).ApiVersions shows that the API version is available.
Is there any documentation that needs to be updated for this PR?
N/A - fixes issue with existing code.

/lgtm


Error with RealisticReactors

I'm pretty sure this is RealisticReactors' fault and already reported it on their mod page, but they don't seem very responsive, so I thought I'd report it to you also just in case you knew of the solution, because choosing between these is hard for me.  Sorry if I'm wasting your time.  Thank you for all your efforts.
The mod The Ruins Mod (1.1.6) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event AbandonedRuins::on_tick (ID 0)
The mod Realistic Reactors (3.1.4) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event RealisticReactors::script_raised_built (ID 79)
RealisticReactors/scripts/heat/buffer.lua:64: attempt to perform arithmetic on field 'y' (a nil value)
stack traceback:
RealisticReactors/scripts/heat/buffer.lua:64: in function 'vecadd'
RealisticReactors/scripts/heat/buffer.lua:69: in function 'for iterator'
RealisticReactors/scripts/heat/network.lua:488: in function 'add_entity_to_network_cell'
RealisticReactors/scripts/heat/network.lua:618: in function 'add_heat_pipe'
RealisticReactors/scripts/events/construct.lua:35: in function 'on_heatpipe_added'
RealisticReactors/scripts/events/construct.lua:104: in function 'entity'
RealisticReactors/control.lua:51: in function <RealisticReactors/control.lua:50>
stack traceback:
[C]: in function 'create_entity'
AbandonedRuins/spawning.lua:45: in function 'spawn_entity'
AbandonedRuins/spawning.lua:94: in function 'spawn_entities'
AbandonedRuins/spawning.lua:172: in function 'spawn_ruin'
AbandonedRuins/spawning.lua:184: in function 'spawn_random_ruin'
AbandonedRuins/control.lua:58: in function <AbandonedRuins/control.lua:53>

Yeah, that looks like RealisticReactors problem, it's just happening within the create event of the ruins mod placing heat pipes. I don't know a solution for the RealisticReactors mod, it's not as simple as the Factory Inspector crash.

Yeah, that looks like RealisticReactors problem, it's just happening within the create event of the ruins mod placing heat pipes. I don't know a solution for the RealisticReactors mod, it's not as simple as the Factory Inspector crash.

rip, thanks for taking a look at it.  ily <3


feat(tutorial): complete step 1

Closes #
Finished step 1
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

👍 Looks good - 🎉 You are now 1/5th of the way to completion of the Carbon React tutorial and earning the digital credential.