Incorrect version bounds

PyF <IP_ADDRESS> is the last version to work with base <4.11 (GHC <8.4), but the cabal bounds haven't been updated.
This problem also affects revisions <IP_ADDRESS> and <IP_ADDRESS>, I just point it out because they're not major version bumps from the last one that worked.
Pinning a dependency to ==<IP_ADDRESS> won't work on GHC 8.8+, since it requires template-haskell <2.15.

Similiarly, PyF <IP_ADDRESS> requires at least template-haskell 2.13 (maybe even newer?), but the constraint is only >=2.11.

Hi @sellout, thank you for the report.
Could you open an MR to fix the bounds? I'll approve it super quickly.
If you cannot, I'll do that in the future (but I don't know when ;)

That PR just adds bounds to the latest version (and makes some small changes to support GHC 8.6 through 9.2), rather than backporting the bounds or whatever. But I have another change coming that restores support for GHC 8.4 (and hopefully even older versions).


Rate Limit documentation is incorrect

Good day Sirs,
I read Rate Limit documentation that is published by the link https://www.getambassador.io/docs/emissary/latest/topics/using/rate-limits/#attaching-labels-to-requests And found that it is completely misleading.
First of all, all keys are described like
generic_key:
  key: mykey
  value: myvalue

or
request_headers:
  header_name: "header-name"
  key: mykey

If I paste such a value into emissary Mapping manifest:
apiVersion: getambassador.io/v3alpha1
kind: Mapping
metadata:
  name: mapping-my-top-level-domain
  namespace: emissary
spec:
  ambassador_id: [ "public" ]
  hostname: my.top.level.domain
  prefix: /api/v4
  rewrite: ""
  add_request_headers:
    Site-Enum:
      value: _HEADER_COM
      append: False
  service: service.namespace:8484
  labels:
    emissary:
      - request_label_group:
          - request_headers:
              header_name: "CF-Connecting-IP"
              key: remote_address
          - generic_key:
              key: endpoint
              value: api_v4

I am getting the next object in the cluster:
apiVersion: getambassador.io/v2
kind: Mapping
metadata:
  name: mapping-my-top-level-domain
  namespace: emissary
spec:
  add_request_headers:
    Site-Enum:
      append: false
      value: _HEADER_COM
  ambassador_id:
    - '--apiVersion-v3alpha1-only--public'
  host: my.top.level.domain
  labels:
    emissary:
      - request_label_group:
          - remote_address:
              header: CF-Connecting-IP
          - generic_key: api_v4
            v3Key: endpoint
  prefix: /api/v4
  rewrite: ''
  service: 'service.namespace:8484'

Looks very weird. I am stating that values are mangled.
Expected behaviour:

provide complete example of Mapping yamls in rate limit description

Hi @gecube , can you give us an example of the Mapping yaml you'd expect, so we can better understand how the values seem mangled?


[C++][Parquet] Exceptions thrown in some tests

Some tests (not all) throw a basic_string exception. Example:

$ ./debug/reader-test
Running main() from gtest_main.cc
[==========] Running 11 tests from 4 test cases.
[----------] Global test environment set-up.
[----------] 7 tests from TestAllTypesPlain
[ RUN      ] TestAllTypesPlain.NoopConstructDestruct
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestAllTypesPlain.NoopConstructDestruct (0 ms)
[ RUN      ] TestAllTypesPlain.TestBatchRead
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestAllTypesPlain.TestBatchRead (0 ms)
[ RUN      ] TestAllTypesPlain.TestFlatScannerInt32
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestAllTypesPlain.TestFlatScannerInt32 (0 ms)
[ RUN      ] TestAllTypesPlain.TestSetScannerBatchSize
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestAllTypesPlain.TestSetScannerBatchSize (0 ms)
[ RUN      ] TestAllTypesPlain.DebugPrintWorks
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestAllTypesPlain.DebugPrintWorks (0 ms)
[ RUN      ] TestAllTypesPlain.ColumnSelection
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestAllTypesPlain.ColumnSelection (0 ms)
[ RUN      ] TestAllTypesPlain.ColumnSelectionOutOfRange
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestAllTypesPlain.ColumnSelectionOutOfRange (0 ms)
[----------] 7 tests from TestAllTypesPlain (0 ms total)

[----------] 2 tests from TestLocalFile
[ RUN      ] TestLocalFile.FileClosedOnDestruction
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestLocalFile.FileClosedOnDestruction (0 ms)
[ RUN      ] TestLocalFile.OpenWithMetadata
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in SetUp().
[  FAILED  ] TestLocalFile.OpenWithMetadata (0 ms)
[----------] 2 tests from TestLocalFile (0 ms total)

[----------] 1 test from TestFileReaderAdHoc
[ RUN      ] TestFileReaderAdHoc.NationDictTruncatedDataPage
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in the test body.
[  FAILED  ] TestFileReaderAdHoc.NationDictTruncatedDataPage (1 ms)
[----------] 1 test from TestFileReaderAdHoc (1 ms total)

[----------] 1 test from TestJSONWithLocalFile
[ RUN      ] TestJSONWithLocalFile.JSONOutput
unknown file: Failure
C++ exception with description "basic_string::_S_construct null not valid" thrown in the test body.
[  FAILED  ] TestJSONWithLocalFile.JSONOutput (0 ms)
[----------] 1 test from TestJSONWithLocalFile (0 ms total)

[----------] Global test environment tear-down
[==========] 11 tests from 4 test cases ran. (1 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 11 tests, listed below:
[  FAILED  ] TestAllTypesPlain.NoopConstructDestruct
[  FAILED  ] TestAllTypesPlain.TestBatchRead
[  FAILED  ] TestAllTypesPlain.TestFlatScannerInt32
[  FAILED  ] TestAllTypesPlain.TestSetScannerBatchSize
[  FAILED  ] TestAllTypesPlain.DebugPrintWorks
[  FAILED  ] TestAllTypesPlain.ColumnSelection
[  FAILED  ] TestAllTypesPlain.ColumnSelectionOutOfRange
[  FAILED  ] TestLocalFile.FileClosedOnDestruction
[  FAILED  ] TestLocalFile.OpenWithMetadata
[  FAILED  ] TestFileReaderAdHoc.NationDictTruncatedDataPage
[  FAILED  ] TestJSONWithLocalFile.JSONOutput

11 FAILED TESTS

Reporter: Antoine Pitrou / @pitrou
Assignee: Antoine Pitrou](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=apitrou) / @pitrou
PRs and other links:

GitHub Pull Request #448

Note: This issue was originally created as PARQUET-1255. Please see the migration documentation for further details.

Uwe Korn / @xhochy:
This is the magic way of telling you to set PARQUET_TEST_DATA to the correct path to the data/ folder than contains the reference files.

Antoine Pitrou / @pitrou:
Hmm, yes, of course, it works once I set PARQUET_TEST_DATA... :-/

Uwe Korn / @xhochy:
Issue resolved by pull request 448
https://github.com/apache/parquet-cpp/pull/448


Health endpoints should be expvar (not prometheus) and use a scraper to get metrics out

If the loggregator system goes down, an operator would be forced to use its health endpoints to debug the issue. Therefore, we want to ensure that the metrics that loggregator emits are available on the health endpoint.
If we use the expvar forwarder, then we can ensure that every metric being emitted by loggregator is available on the health endpoints (for the synchronous data frame).

This would have been really useful the last couple weeks while we have been debugging a couple of large bugs. Having a single source of info for metrics would have been nice especially where there was some confusion about the values being emitted for some more metrics. I feel like this would have made it easier to track down the bad actors.

CLosing pending more customer evidence this would be worth the effort.


added build profile

this package was failing when I tried to include it in a dojo build
the dojo build was trying to process the test files as AMD modules
I've inlcuded profile.js to tell the dojo build to stop that nonsense.
thanks to @gavinr and @kfranqueiro for help w/ this.

Thanks @tomwayson


Enhancement: Migrate from firebase to postgreSQL

I'm planning to migrate backend from Firebase (Firestore) to PostgreSQL to improve data integrity, enhance querying capabilities, and better support structured relational data for Bharat Seva+.
Benefits of Migrating:
Advanced Querying Capabilities: PostgreSQL provides advanced SQL querying options, making it easier to handle complex queries

Fetching patient profiles based on multiple parameters (e.g., age, health conditions).
Running aggregation and trend analysis over time for personalized health insights.

Structured Data Management: With PostgreSQL it is better suited for storing structured data like

User profiles, settings, logs (where logged in), vaccination schedules.
Establishing relationships between tables such as providers and schemes.

Scalability: PostgreSQL supports large-scale deployments with options for table partitioning, indexing, and horizontal/vertical scaling, making it suitable for growing user bases and data sizes (this one is really important).
Cost Efficiency: Firebase's read/write costs can increase significantly with scale, especially when hosted on cloud providers like AWS RDS
Industry standard: PostgreSQL is the choice when we need a robust, scalable, relational database with strong querying, data consistency, and enterprise-level performance.
Impact:
All Firebase-dependent code will be refactored to work with PostgreSQL. This includes data models, querying mechanisms, and CRUD operations.
Next Steps:

Design PostgreSQL schema for structured data (patients, healthcare providers, appointments, logs).
Refactor backend code to integrate PostgreSQL.
Test migration for data consistency and ensure all critical functions (like appointments and health record logs) are unaffected.
Deploy the updated version on staging for testing.
Write test cases to test overall functionality.

Contributors: Please comment below if you're interested in helping with this migration or have suggestions on the process.

I can handle this issue. Please assign it to me


average unpatching on motion correction

I have implemented the left-one-out cross validation splitting (current we test on patient 01_ab).
As expected, we don't achieve good results as we do on training dataset.
I have also implemented the average unpatching method - it does have impact on removing the block-like artifacts, increase the SSIM and decrease MSE, but it also smoothen the image at the same time. (the center part will be averaged by at most 25 times, maybe I should try median later)
You can check the latest results with this result dropbox folder. Under the /Headcross/01_ab/4848/ there are two folders: average and unpatching, which specify two different unpatching methods.
Following is the training plot. I have simplified our network from 45 Million params to 18 Million params, currently the overfitting is not that obvious. (Not quite sure if the params are still too many?)

I have also tried to integrate 3D Conv and inception layer to our network. But the result is not that good now. (3D Conv is really difficult to train - it will take more than one hour to train one epoch...) But I'm still looking into them though.
Do you have any suggestion to the current stage? What do you think of the current results? (Actually I'm quite doubt if there is still much room for improvement, because this original motion_affected images lose much high frequency information, which intuitively is difficult to recover)

I will reply to your questions in a separate mail...


net: explain why we ignore the first line of Plan 9 interface-status files

Updated to explain why we ignore the first line of Plan 9 interface-status files.


CMake will not detect a variable as empty string

Description
Testing it with CMake 3.12 it's not detecting that CUDA_TOOLSET is empty

LGTM


SupportedControllerType is not extendable

Describe the problem
I want to add a custom input controller. To propetly do that, I need to add/extend the Enum SupportedControllerType.
Until v2.4 I was manually changing the SupportedControllerType.cs file. Now with MRTK 2.5 I want to use the UPM, but then I can't change the file.
Describe the solution you'd like
I would like to have a profile or something similar, so I can easily add new enums (e.g. like we can do with Input Actions)
Describe alternatives you've considered
Currently, If I want to use MRTK 2.5, I need to go the old way with the .unitypackage which should be avoided.

I'm going to close this issue out in favor of using https://github.com/microsoft/MixedRealityToolkit-Unity/issues/4239 to track. I'm working on this for 2.6.

I'm going to close this issue out in favor of using https://github.com/microsoft/MixedRealityToolkit-Unity/issues/4239 to track. I'm working on this for 2.6.


Suggestion To Enable Your Customerrs

Why isn't there a simple Objective-C example on how to use the DFU/OTA Updates for iOS?
Same applies for Swift and Android.
You guys have all these complex examples but really we just need something simple to build off of. I rather not spend hours dissecting the pieces of your code that really have no relevance to the task I'm trying to accomplish. I'm confident all your developers have to go through this same struggle which impedes them from releasing something and puts a lot of work on you dealing with the customer support and confusion.
On the positive, you put out a great product that I'm sure entails lots of hard work. Just a suggestion to better enable your customers.

Hi,
The describing how to start dfu (including using O-C) is in the documentation on this GitHub repo. It can be stated with 3 lines of code, not counting dependency setup.
We have examples how to use it in the sample app here, in nRF Toolbox and Nordic Thingy app, although all of which are written in Shift. We have deprecated all our apps on O-C and migrated to Swift.

Thanks for your reply. I hear that. As you mentioned, you deprecated support for Objective-C. Some of your customers haven't made the same decision.  I understand maybe you don't have too but it would be helpful if you decided to support it again.
I also understand you have a variety of sample apps. Those apps have a lot going on. It would be nice if you had something simple. That demonstrated the core functionality with as few lines of code as possible. But not so-few that the code is cryptic.
Just a suggestion. I know you guys/gals work hard and ultimately create a great product. Always room for improvement and this is just a gentle suggestion which may be helpful to your customers and reduce workload from people asking questions about implementations in Objective-C. Particularly with some of the new features you released like the secure boot-loader.
All the best


Make the app icon colored on taskbar, not a monochrome outline

What feature or improvement do you think would benefit Files?
Installed version 3 and I think the new app icon with yellow shades is awesome, the best so far among all file managers, in my opinion! But I got frustrated when it showed as a monochrome outlined icon on the taskbar 😞
Requirements

This proposal will accomplish a more consistent and elegant UI and product design.

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.2506
Comments
No response

Thanks for the report. this has been fixed in <IP_ADDRESS>

@luckyscooby thanks for the report, this was indeed a bug with the icon in light mode. We already deployed a fix and it should be available in a couple of hours.


Add Sovryn multiprocessor

Context
This PR represents the same as #364
To-do list

[ ] Added tests
[ ] Tested on dev/sbx
[ ] Changelog was updated with current changes
[ ] Documentation or guides were updated (slab, readme)
[ ] Version was updated on package.json (releases/hotfixes)

Checklist before merge

[ ] there are no errors in logs in any workers
[ ] new blocks are being discovered and marked as finalized
[ ] foreign blocks are being dispatched
[ ] squash all commits before merging

Looks good to me! Just not sure if it will cause conflicts on that PR

Looks good to me! Just not sure if it will cause conflicts on that PR

@matheushahnn, thanks. I will close the old one, for whatever reason github didn't allow me to force push after rebasing develop. That is why I opened this new one including your suggestions.


Filter targets in zone for given models

https://bugzilla.redhat.com/show_bug.cgi?id=1223835
The old code used includes(:ext_management_system) to help the fetching performance. It only works for models that have an association with ExtManagementSystem. Storage is such an exception. It turned out there are other models that do not have the association.
This fix provides a general solution to first detect the existence of the association. It also tries two possible methods to get the zone.

@bzwei Would be good to add tests for the models we know are processed by this method.  Refactoring the new target += logic into a separate method should make it easier to test than trying to test the entire evaluate_hourly_timer method.

Yeah, I need to see specs.  In particular, I don't think you need the case for zone_name since it's an alias of my_zone, but I could be wrong.
If the goal is to have models describe their instances' zones, I feel like it seems better to have a method on all of the models we care about and just call that.

@Fryguy While looking into an enhancement a couple months ago I noticed that a few models defined zone_name method only and mentioned it to @bzwei when we were discussing this issue.  Searching for it again it looks like those models (CimComputerSystem, CimStorageExtent, SniaFileShare and SniaLocalFileSystem) are not currently processed here.

I added spec test. I did not remove zone_name method thinking of it does not hurt and we may need to add those models.

@bzwei I was discussing this issue more with @Fryguy and we were thinking it would be a better idea to delegate the selection of the zone instances to each model that is alert-able instead of trying to handle the different cases here using conditional logic.  We would need to add a class method like in_zone(zone) to Cluster/Deployment Role, Datastore, Host/Node, Provider, Server and Vm.

The solution with the latest commit is to utilize existing accessors in Zone class. The behaviors are a little different. The old code finds all instances of a model whose ext_management_system is in the zone, plus those don't have an ext_management_system assigned. The new code excludes instances that don't have an ext_management_system assigned. After some discussions we think this change is appropriate.

@bzwei It seems we do need to retain the old logic of including resources not directly associated with a zone through a provider.  There are a number of alerts that could be configured that do not require the provider relationship.  For example setting up a custom expression to check snapshot count, tagging events or even if the provider is still valid.
Ultimately it would make more sense to have an hourly timer run for these disconnected resources and allow to current runs to focus on the resources in their zone.  This would also remove the duplication we have today since each zone is processing the disconnected resources.
@bzwei @Fryguy thoughts?

With this latest commit, we I add a boolean flag to Zone's accessors to include disconnected resources. We can investigate later if we need to have a dedicated timer for disconnected resources only.

LGTM.  @Fryguy Anything else here?


Messaging: Restrict external datastore access

The external datastore on AWS DynamoDB needs the API to be locked down per user
Only allow authorized user to access their own profile

Ensure dynamodb is not exposed to be written to

Ready to deploy, closing.


Update OverlayContainer to work in SSR

Currently if OverlayContainer is rendered during SSR it would fail because of trying to access document.body. This ensures that the window APIs are only called on the browser during useEffect, and only attempts to render the portal when it has a container
Closes https://github.com/adobe/react-spectrum/issues/1055
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

Make sure SSR works when OverlayContainer is present.
Confirm that aria-hidden displays as expected with useModal

🧢 Your Project:

On behalf of chrisdmacrae.com

Please advise on tests and checklist

hey @chrisdmacrae! thanks for taking a go at this. in order to verify/test this, you can probably utilize our SSR tests see https://github.com/adobe/react-spectrum/blob/main/packages/%40react-spectrum/picker/test/Picker.ssr.test.js for an example
Right now all of our SSR tests are pretty basic, just check that the most basic set of props renders, but you might be able to toss an isOpen on the one i linked in a new it to check if your fix works.

Any progress here?

@sondretj however I cannot get the SLA to work

Any updates on this one? I'm facing this exact issue right now.

@flayner2 can't get tests to pass

I believe this issue has been fixed in the meantime. It now checks SSR during rendering.


modify test time requirements

modify test time requirements: isort to older version and add interrogate

Hi!
@SuX97
First of all, we want to express our gratitude for your significant PR in the OpenMMLab project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


Machine Details page not using base_domain

The newest feature for Machine Details is using .ts.net hardcoded as FQDN.
It should use the user set base_domain.
https://github.com/tale/headplane/blob/3ea5fed8f6879af9f0aff8edc1bce1c45379ec6d/app/routes/_data.machines.%24id.tsx#L135

Fixed in 08db192db1637e86f354e7e31fd8b093217472f1.
Available in 0.1.9


SelectSingleNode allays return TRUE

The "SelectSingleNode"  always return TRUE even if 'NodeName' does not exist.
If ParentNode.SelectSingleNode('NodeName',ResultNode) then
NodeValue := ResultNode.AsXmlText.Value;
ResultNode - is not initialed

I am looking at a test for exactly this case and it returns false. Could you post an XML doc that repros this?

GetPrice

20000
Customer

1
1

1896-S
PCS

nav

<?xml version="1.0"?> <Request> 	<Operation>GetPriceInfo</Operation> 	<Params> 		<AccountId>20000</AccountId> 		<AccountType>Customer</AccountType> 		<CurrencyId/> 		<MultiCurrency>1</MultiCurrency> 		<LoadRelatedSkus>1</LoadRelatedSkus> 		<Product> 			<Id>1896-S</Id> 			<UnitOfMeasureId>PCS</UnitOfMeasureId> 		</Product> 		<ExtraFields> 	      <field name="Product Group Code" />  	    </ExtraFields>  		<WebsiteId>nav2016</WebsiteId> 	</Params> </Request>

Thanks! Do you also have a query that fails on this?

Nope, just crashes doe to  ResultNode - is not initialed

If  CurrentNodeGlobal.SelectNodes(QueryString,ResultNodeList) then ..
The almost same behavior for "SelectNodes"  - return TRUE but QueryString does not exist in XML, the diffidence just that "ResultNodeList" stays initialized.
Check that please as well.

In the case of SelectNodes, the operation will only return false or fail if the xpath is invalid or if another error happens. If the xpath does not match any nodes, the list will be empty.
In the case of SelectSingleNode, I tested it with the following snippet and it works as expected.
pageextension 50100 CustomerListExt extends "Customer List"
{
    trigger OnOpenPage();
    var
        doc : XmlDocument;
        n : XmlNode;
    begin
        XmlDocument.ReadFrom('<root><book></book></root>', doc);

        if doc.SelectSingleNode('/something', n) then
            Message('Found ' + n.AsXmlElement.Name)
        else
            Message('Did not find something');

        if doc.SelectSingleNode('/root', n) then
            Message('Found ' + n.AsXmlElement.Name)
        else
            Message('Did not find root');
    end;
}

I get "Dit not find something" and then "Found root"

Yes it is, You have tried with XmlDoc, but in my case node is used.
ParentNode.SelectSingleNode('NodeName',ResultNode)
In the case it returns as TRUE and ResultNode - UNINITIALIZED

Ok. I will check with an XmlNode. Maybe that is the problem.

Second attempt below. I still get the expected behavior. If you can provide a full snippet with a small sample document that reproduces the error it would be of great help.
pageextension 50101 CustomerListExt extends "Customer List"
{
    trigger OnOpenPage();
    var
        doc : XmlDocument;
        root : XmlNode;
        book : XmlNode;
    begin
        XmlDocument.ReadFrom('<root><book></book></root>', doc);

        if doc.SelectSingleNode('/root', root) then begin
            Message('Found root');

            if root.SelectSingleNode('book', book) then
                Message('Found ' + book.AsXmlElement.Name)
            else
                Message('Did not find something');
        end
        else
            Message('Did not find root');
    end;
}

`CurrentNodeGlobal = '1111111110000Customer001Id19/18/2017 6:10:36 AMNAV2016'
QueryString = '//CurrencyId' - is not present in the xm;
Case true of
CurrentNodeGlobal.IsXmlElement :
begin
CurrentXmlElement := CurrentNodeGlobal.AsXmlElement;
IF CurrentXmlElement.SelectSingleNode(QueryString,ResultNode) then
case true of
ResultNode.IsXmlAttribute :
exit(ResultNode.AsXmlAttribute.Value);
ResultNode.IsXmlElement :
exit(ResultNode.AsXmlElement.InnerXml);
ResultNode.IsXmlText :
exit(ResultNode.AsXmlText.Value);
end;
end;
end;`

Still works as expected.
pageextension 50101 CustomerListExt extends "Customer List"
{
    trigger OnOpenPage();
    begin
        GetText();
    end;

    local procedure GetText() : Text;
     var
        doc : XmlDocument;
        currentXmlElementNode : XmlNode;
        currentXmlElement : XmlElement;
        ResultNode : XmlNode;
        book : XmlNode;
    begin
        XmlDocument.ReadFrom('<Params><VisibleOnly>1</VisibleOnly><LoadRelatedSkus>1</LoadRelatedSkus><LoadVisibilityRules>1</LoadVisibilityRules><CalculatePrices>1</CalculatePrices><CalculateInventory>1</CalculateInventory><CalculateSkuPrices>1</CalculateSkuPrices><CalculateSkuInventory>1</CalculateSkuInventory><CheckStock>1</CheckStock><AccountId>10000</AccountId><AccountType>Customer</AccountType><MultiCurrency>0</MultiCurrency><PageIndex>0</PageIndex><PageSize>1</PageSize><SortField>Id</SortField><SortAscending>1</SortAscending><ExtraFields /><Filter><for field="ModifiedDate"><LessOrEqual>9/18/2017 6:10:36 AM</LessOrEqual></for></Filter><WebsiteId>NAV2016</WebsiteId></Params>', doc);

        doc.SelectSingleNode('/Params/Filter', currentXmlElementNode);

        case true of
            currentXmlElementNode.IsXmlElement :
            begin
                currentXmlElement := currentXmlElementNode.AsXmlElement();

                if currentXmlElement.SelectSingleNode( '//CurrencyId', ResultNode) then begin
                    case true of
                    ResultNode.IsXmlAttribute :
                        exit(ResultNode.AsXmlAttribute.Value);
                    ResultNode.IsXmlElement :
                        exit(ResultNode.AsXmlElement.InnerXml);
                    ResultNode.IsXmlText :
                        exit(ResultNode.AsXmlText.Value);
                    end;
                end
                else
                    Message('Did not find root');
            end;
        end;
    end;
}

From my side Your example code does not work as well. Bellow You can find a screenshot.
As You can see after IF statement ResultNode  becomes "Uninitialized".
Dev environment on Docker, so the version of build should me latest, AL Language 0.9.12465 September Update (LATEST)

What might be wrong?

In the latest version, it works as expected. As soon as the October update gets pushed out, let me know if this still happens.

Could I know when October update will be available please?


Creating new tiles in mapping using shift or ctrl creates many new grids and lots of pain.

Description
A major regression occurred 6-8 months ago making it so see: title happens when trying to expand on grids. For a while this was not much of an issue as long as you were building off an existing tile or grid. But it has become increasingly difficult to not create rogue grids while mapping.
Reproduction
use ctrl or shift + tile drag. It's relatively random but can happen with as few as 5 new tiles.
Screenshots
n/a
Additional context
n/a

God, this is getting old. 😩


feat: Added Origin Access Control (OAC)

Description

Add support for Origin Access Control to replace legacy Origin Access Identity.
Motivation and Context

Origin Access Control improves upon Origin Access Identity by strengthening security and deepening feature integrations. Origin Access Control provides stronger security posture with short term credentials, and more frequent credential rotations as compared to Origin Access Identity.
Breaking Changes

How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

Hello @antonbabenko @bryantbiggs could it be possible to integrate this PR in the next release ? Thank you

This PR is included in version 3.2.0 :tada:


Fixed axis range and log scale

Hi,
Is there a way to constrain the range of an axis to a specific interval (so that it does not automatically update upon appending new data)? Also, is there a way to display data along an axis in log scale?
Thanks!

Hi @lozino - you can fix the axis by providing both xtickmin and xtickmax options to the plot (for the x axis for example). You have to provide both as plotly requires a range to display over. (If setting those initially is still updating the plot you may also need to provide these during your append as well, but I don't think that should be required.)
For log axis, you can supply direct plotly opts using the layoutopts option. The format for that will be a dict that contains a plotly key with the value being a dict of plotly options. The one for using log axis is here. Note that as this is directly overriding the axis options, the above note about specifying the range may be overridden. If it is, you will need to directly supply the range in the plotly dict as a range entry containing a two element array with the first being the min and the second being the max, as well as providing autorange: False.
Below is an example that both sets the range and the plot type to log:
opts = {
  'layoutopts': {
    'plotly': {
      'xaxis': {
        'type': 'log',
        'range': [0, 1000],
        'autorange': False,
      }
    }
  }
}

Perfect, thanks!


📖 Documentation

TODOs

[x] modal (dialog)
[ ] chips
[ ] cards
[ ] landing page
[ ] use transition API across documentation

https://www.youtube.com/watch?v=MJHO6FSioPI
PR 9605 in sveltekit repo

[ ] edit on github link
[ ] version and link to changelog and contribution instructions in navbar
[ ]  last updated date time (https://docs.github.com/en/rest/commits/commits?apiVersion=2022-11-28#list-commits-on-a-repository)

Getting Started

[x] installation
[ ] setup: presets, tailwind reset, import uno.css file (serves as a file that the css will be loaded into), etc.
[ ] template
[ ] transferring from Tailwind
[x] VSCode set up (install UnoCSS extension, disable other extensions, etc)

Shortcut Search

[x] search bar
[ ] filter buttons (button, gradient, spinners, background, light / dark, etc.)
[ ] explanation window

Buttons

[x] regular (one color)
[x] gradients (2 & 3) (mention opacity values and optional shades and so on)
[x] glass
[x] group (regular & outline)

Spinners

[x] mention how they can be customized

Inspiration

https://github.com/nuxt-themes/docus
https://unocss.dev/
https://vitepress.dev/

Code Blocks

see if we can add highlight lines to code blocks
add shiki-twoslash (https://github.com/shikijs/twoslash)
#74

Resources

https://github.com/vuejs/vitepress/tree/481a6e9cbd84068cc976db1e9adbc466b6e81ad9/src/client/theme-default/components
Components to help create our own:

https://www.shadcn-svelte.com/docs/components/accordion

Update the documentation navbar so that on mobile its at the bottom like in Svelte's documentation site.


Landing page formatting looks odd on some devices

Pulled up the landing page on my Pixel 2 XL and the formatting for the landing page looks funky and weird. This is in contradiction from when I view the page on chromes version of my phone, which shows it correctly. Picture attached to show what it looks like on my actual phone.

Maybe we need to test on more devices and fix the landing page.

Nvm, I think Jace already fixed this, will make sure this is fixed with him next time he's able to update the production Manifold.

Ya sorry I fixed that. I didn't make an issue, but it's been to committed to master.


[BUG REPORT]: NULL values in WPC grid results

Report from Ashley in SAW

Direct link of download: https://cumulus-api.corps.cloud/cumulus/download/dss7/download_a3bbd4f2-128b-45fb-8157-9fa4ce2480b8.dss

Keep in mind both the grib and tif file above are CONUS (not clipped).  The clipping occurs during the DSS packaging process.

Here are the stats (abbreviated) for the clipped (Cape Fear River) tif for the same hour as above.
 gdalinfo p06m_2022110112f018.tif -stats

...

Metadata:
    GRIB_COMMENT=06 hr Total precipitation [kg/(m^2)]
    GRIB_DISCIPLINE=0(Meteorological)
    GRIB_ELEMENT=APCP06
    GRIB_FORECAST_SECONDS=43200
    GRIB_IDS=CENTER=7(US-NCEP) SUBCENTER=5(Hydrometeorological Prediction Center) MASTER_TABLE=2 LOCAL_TABLE=1 SIGNF_REF_TIME=1(Start_of_Forecast) REF_TIME=2022-11-01T12:00:00Z PROD_STATUS=0(Operational) TYPE=1(Forecast)
    GRIB_PDS_PDTN=8
    GRIB_PDS_TEMPLATE_ASSEMBLED_VALUES=1 8 2 0 180 255 255 1 12 1 0 0 1 0 -1 2022 11 2 6 0 0 1 0 1 255 1 6 1 0
    GRIB_PDS_TEMPLATE_NUMBERS=1 8 2 0 180 0 255 255 1 0 0 0 12 1 0 0 0 0 0 1 0 128 0 0 1 7 230 11 2 6 0 0 1 0 0 0 0 1 255 1 0 0 0 6 1 0 0 0 0
    GRIB_REF_TIME=1667304000
    GRIB_SHORT_NAME=0--1-SFC
    GRIB_UNIT=[kg/(m^2)]
    GRIB_VALID_TIME=1667368800
    STATISTICS_MAXIMUM=0
    STATISTICS_MEAN=0
    STATISTICS_MINIMUM=0
    STATISTICS_STDDEV=0
    STATISTICS_VALID_PERCENT=100

@katfeingold and I found where the Infinity is coming from in GridInfoFlat.java
public boolean unflatten (int array[]) {
//....
 // deal with special cases of min, max, and mean values for all-null cases
    if (_minDataValue > _maxDataValue){
    	_maxDataValue = RMAConst.UNDEF_FLOAT;
    	_minDataValue = RMAConst.UNDEF_FLOAT;
    	_meanDataValue = RMAConst.UNDEF_FLOAT;
    }
// where: public static final float UNDEF_FLOAT = Float.NEGATIVE_INFINITY;

the Infinity is intentional, but we could change this if other programs don't rely on that behavior?

@adamscarberry can you share with me please the source grb files for the forecast timewindow 28July2022 throuhg 31July at least?
@ktarbet I believe the issue is not actually about the statistics reported in the Gridded DSS Record's header.  Rather it's about the array of values for grid cells, they seem to be coming out as -infiniti during conversion from original values of 0.

@katfeingold and I found where the Infinity is coming from in GridInfoFlat.java
public boolean unflatten (int array[]) {
//....
 // deal with special cases of min, max, and mean values for all-null cases
    if (_minDataValue > _maxDataValue){
    	_maxDataValue = RMAConst.UNDEF_FLOAT;
    	_minDataValue = RMAConst.UNDEF_FLOAT;
    	_meanDataValue = RMAConst.UNDEF_FLOAT;
    }
// where: public static final float UNDEF_FLOAT = Float.NEGATIVE_INFINITY;

the Infinity is intentional, but we could change this if other programs don't rely on that behavior?

@ktarbet I thought we found this about a month ago?  I remember some DSS6 code that computes stats again before this evaluation.
GDAL is used in tiffdss to get the data array.  Stats are computed in tiffdss with concepts taken from DSS6/7 code.  @ktarbet is correct that it's about the grid data array and not stats computed from that array.  Evaluate the grib, GeoTiff, and the clipped GeoTiff only pulling out the data array.

This is a sample data set (based on my stats output above) that I can get you quickly:
Archive.zip

@jeffsuperglide  Yes!   we recently had https://github.com/USACE/cumulus/issues/231 and  https://github.com/USACE/cumulus/issues/240
More details on what we saw yesterday in the debugger:
All the data in the grid-data-array was listed as missing.
Then the statistics were re-computed during the DSS7->DSS6 conversion which creates the Infinity values for (min,max,mean), using the java code block above.
We need to change either:

during the DSS7->DSS6 conversion
MetVue/other software needs to handle the grid with all missing data.

In a previous iteration, of this issue, we made a change to DssVue to handle this case better.
@FHanbali  Was there was a recent change to MetVue to handle this case?

Thanks Adam.  Geotiff sample shows all zero (valid) values.  Either Geotiff conversion to DSS7 or DSS7 to DSS6 conversion is causing null values to be stored in final DSS product.

This is a sample data set (based on my stats output above) that I can get you quickly:
Archive.zip

Two Tiff files are provided in the archive, conus_p06m_2022110112f018.tif and clipped_p06m_2022110112f018.tif.  conus has a no data value (nullValue) of 0 and the clipped no data value is -9999.  A no data value of 0 produces the following because all values == no data value.
Max Data Value: -2.0E38
Min Data Value: 2.0E38
Mean Data Value: NaN

Having -9999 (or != 0) results in zeros for stats.  The packager uses gdal.Warp() without defining the no data value; therefore, the no data value is taken from the source Tiff.  Packager writer dss7 could check for that no data value and set to some non-zero value.

:: draft in progress table of workflow,   input welcome

Step
file
description
range of data
no data value

1
raw grib file
has 6 hour precip data mm
0-30.5
not defined

2
TIf - unclipped
6 hour precipdata
0-24.9
not defined

2
TIf - clipped
6 hour precipdata
0-0
-9999

2
DSS v7
6 hour precipdata
n/a
-3.4028235E38

2
DSS v6
6 hour precipdata
n/a
-3.4028235E38

@jeffsuperglide and @brettpalmberg We ready for push to stable?

@jeffsuperglide and @brettpalmberg We ready for push to stable?

I say yes.

Let me know please if cu is ready to have folks try out the fix.

@FHanbali @jeffsuperglide's patch has been applied to stable.  Ready for final verification.

Kind ping 😃. This work is complete and awaiting final verification. Hoping we can officially close this issue.
@FHanbali @jeffsuperglide @adamscarberry @ktarbet

Excellent! No worries and good teamwork all. Closing this issue now.


Keep-alive connections keep threads occupied infinitely

As discussed in rustless/rustless#35, suggested by @reem, Hyper seems to be too "literal" about keep-alive, keeping threads in a keep-alive loop, essentially DDoSing a Hyper server. My temporary workaround is to use many threads to delay running out of threads for the time being.

I think that Hyper must have something like KeepAliveTimeout in Apache.

@andor44 I think that you may try to use nginx as a reverse proxy in front of Rustless/Huper to work-around the issue. Nginx could handle a big amount of connections without any issues and it has usable keep-alive settings.

@s-panferov I'll give that a shot.
Here's the relevant part of the code. I'm not sure how deep down the rabbit hole this should be handled though. Probably as deep as this though I'm not sure how easily you can specify a timeout in the current Hyper architecture.

The current IO doesn't provide a way to specify a timeout, which makes this harder.

@andor44 have you tried to use a reverse proxy already? Has it helped?

Yes. I am using nginx, and it uses HTTP 1.0 for reverse proxying requests, which doesn't have keep-alive as part of the spec, and it works perfectly.

When will this bug be fixed? timeout should be an urgent feature.

Timeouts won't be supported by TcpStreams until Rust 1.1, which would be
mid June. To support timeouts in hyper earlier, we'd need to explore using
an additional thread, but it's performance may suffer too much.
In the mean time, I suggest putting nginx in front of your server, which
handles this well.
On Sat, Apr 18, 2015, 10:24 AM Young Woo<EMAIL_ADDRESS>wrote:

When will this bug be fixed? timeout should be an urgent feature.
—
Reply to this email directly or view it on GitHub
https://github.com/hyperium/hyper/issues/368#issuecomment-94184696.

All right, thanks. But what about the client? Are there any good ways to
add timeout to a HttpClient？
On 2015年4月19日周日 上午2:15 Sean McArthur<EMAIL_ADDRESS>wrote:

Timeouts won't be supported by TcpStreams until Rust 1.1, which would be
mid June. To support timeouts in hyper earlier, we'd need to explore using
an additional thread, but it's performance may suffer too much.
In the mean time, I suggest putting nginx in front of your server, which
handles this well.
On Sat, Apr 18, 2015, 10:24 AM Young Woo<EMAIL_ADDRESS>wrote:

When will this bug be fixed? timeout should be an urgent feature.
—
Reply to this email directly or view it on GitHub
https://github.com/hyperium/hyper/issues/368#issuecomment-94184696.

—
Reply to this email directly or view it on GitHub
https://github.com/hyperium/hyper/issues/368#issuecomment-94188584.

This error is still apparent in v0.6. My server hangs sometimes and it is quite frequent, I know it's not my code because not even the Handler's handle is getting called for a HTTP request that I've just sent. It seems to not be an issue when hosting & requesting locally. I've switched to rust-http and my code works fine. This really needs to get fixed IMHO.

Is this issue the place to follow for updates on this bug?

FYI, for those who need a workaround for this issue while we wait for async:

Keep a count of how many worker threads are busy or waiting in the keep-alive loop.  The handler trait now has hooks (on_connection_start and on_connection_end) allowing you to increment/decrement your count of busy threads.  You'll need to use a Mutex or AtomicUsize or other sync primitive where you update the count.
Have your handler function check the count, and if the count is high enough (e.g. maybe all but 4 threads are occupied), set the Connection::close header (which hyper will notice and respect, closing the connection after the response).
I still recommend using the 'timeouts' feature and setting read and write timeouts on your server; but now those timeouts don't need to be super-short anymore.

This way you can still support keep-alive most of the time, but when things get really busy, your server won't "hang".  I've tested this and it works well.

I'm thinking of turning keep-alive off by default for hyper 0.6 servers, which is probably the right thing to do, and let people who have a solution turn it back on. However, that's a logical breaking change, even though code will continue to compile...
Thinking of adding something like this to keep the current behavior:
Server::http(addr).unwrap().keep_alive().listen(handler)

No solution for the problem itself?

@juanibiapina the best solution is asyncio, tracked in #395. With synchronous IO, your only options are  1) set a timeout, which can be done currently, but still means the connection could block to the full length of the timeout, or 2) don't try to read on kept-alive connections.

It feels a bit like sweeping it under the rug, but it's about as good as any other workaround. It may become a gotcha in it's own way, though. Probably less obvious, but still...

In iron at least I can attempt to implement the AtomicUsize-tracked-by-connecton_{start, end} solution, which may eliminate a lot of these issues.

I'm going to try the way Apache does it: if you want keep-alive, a timeout will be used when trying to read on the kept-alive connection. This is really the only thing that is possible on blocking sockets.
server.keep_alive(Duration::from_secs(5));
server.listen(...)

Of course, this will require activating the timeouts feature in hyper, and requires rustc v1.4 or greater.

I concur.  I think the number of people who find hyper "locks up" is sufficiently high to justify disabling keep-alive by default for 0.6.  It could be considered a DoS security vulnerability as it currently stands.   The performance benefit of keep-alive can't really be achieved under blocking I/O anyhow without an enormous number of threads, or being under very low load.

You could make a new release without the keep-alive, like you suggested, since this is still 0.x. Then you could implement the timeout when 1.4 comes out.
As a user of the lib, I don't mind because I would be actively upgrading a not 1.0 dependency.

@mikedilger you beat me to it xD

Doing the connection counting trick will at least let users choose a balance, but tune it the wrong way and your thread pool may be filled up with idle favicon connections and your server basically reverts to single thread mode. I implemented it in Rusful and it prevents lock-ups, but not much more. Disabling keep-alive may even be a better alternative, after all, since it will treat every connection equally. It's at least better than lock-ups.

A co-worker of mine wrote a tool to benchmark hyper-based servers, and which is annoying in just the right ways to inspect keep-alive related behaviour: http://github.com/alanstockwell/hyperspank  (shout out to @alanstockwell)

Proposed fix is in https://github.com/hyperium/hyper/issues/661

On IRC, @reem pointed out to me that it's possible to do a little more in this area. With the timeout solution, a scenario is still possible that all the threads are used to each deal with a connection that is using keep-alive, and even though they aren't blocked by a stalled connection, while they are active no other connections can be handled.
I'm not sure if this scenario should still be considered part of this bug, or more of a general improvement. Also, once non-blocking io is merged, this issue goes away automatically.
A solution here would be to have an acceptor thread, and a work queue. The acceptor would push all TcpStreams into the queue, and the workers would process 1 request/response pair. If keep-alive is true, that Stream could be placed at the back of the work queue.

How is going this feature?


Fix Issue #35 - ask for capability size. Too small size could cause errors

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Commenting on process rather than the change: I'd rather we don't merge new changes before we complete the migration to Github and before we port change from the private Khronos repo to this one.

I will close this PR and open new with review fixes. I have some issues with this branch while rebasing.


[Unit Test Failure] ServiceConfigTest.testDelayExport() and ServiceConfigTest.testExport() failing

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.5-SNAPSHOT
Operating System version: Max OS 10.14.5
Java version: Oracle jdk 1.8.0_131

Steps to reproduce this issue

checkout master branch
checkout HEAD 15d8084
run command: ./mvnw clean install -DskipTests=false & ./mvnw clean test-compile failsafe:integration-test

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps？
The build should run successfully
Actual Result
What actually happens?
Unit test failing
If there is an exception, please attach the exception trace:
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   ServiceConfigTest.testDelayExport:173
Expected: a collection with size <1>
     but: collection size was <0>
[ERROR]   ServiceConfigTest.testExport:155
protocol.export(
    <any org.apache.dubbo.rpc.Invoker>
);
Wanted 1 time:
-> at org.apache.dubbo.config.ServiceConfigTest.testExport(ServiceConfigTest.java:155)
But was 2 times:
-> at org.apache.dubbo.config.mock.MockProtocol2.export(MockProtocol2.java:36)
-> at org.apache.dubbo.config.mock.MockProtocol2.export(MockProtocol2.java:36)

[INFO]
[ERROR] Tests run: 557, Failures: 2, Errors: 0, Skipped: 2

Had already fix that,thx~


💾 Save Streams

Description
Related to this thread.
Currently it is not possible to receive data from multiple streams/branches into a single Blender document.
Expected Behaviour
A save option for streams as we have in other connectors (Revit, Rhino). Thus, more than one data can be received.
Steps to reproduce

Add below stream to Blender connector.
change branch to branch 1 and receive.
change branch to branch 2 and receive.

There is not other way but to update/overwrite previously received geometry. In other words, data cannot be received from 2 separate branches at the same time.
Streams/Commits Used
https://latest.speckle.dev/streams/8d4cd92914
Related Issues
#115

It will be covered under UI refactorment.


Update translation files after ID review and approval

Signed-off-by: 662962756<EMAIL_ADDRESS>

 review console locale files for all languages


Add tracking for two different anime in a single entry

Describe your suggested feature
To be able to add another anime to a single tracking service since in AniList (for example) entries that in aniyomi sources are as "...ovas" in AniList they are separately.
Example:
On aniyomi source: "Bleach: OvaS"
On AniList: "Ova 1" & "Ova 2"
Other details
It would be useful to not have to add more entries to the library, and if someone keeps an order (by date added to the library) so that it doesn't get cluttered when adding new entries just to add tracking to each episode that are like different entries in AniList.
Although, a solution for this would be to create a category just to add tracking to those "episodes" that are as different entries in AniList.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I will fill out all of the requested information in this form.

+1
This would be useful for entries with multiple seasons too.

+1
This would be useful for entries with multiple seasons too.

Exactly, like Yomiroll, in fact

Duplicate of #1351


Question about addition of an extra Potential in the HF calculation

Hi,
currently, I am working on a project that requires me to add a potential (constant initially) in the Hartree-Fock Hamiltonian. This means, that, I would like to have an Hamiltonian be composed by the sum of Core potential, Electronic Repulsion potential and My new Potential.
How can I add this feature safely into the code?
PS At the moment, I do not plan to add this feature to PySCF. I am planning to use it locally, since it would be a very niche application.

You can overwrite the get_hcore() function of the mf object to also include your custom potential, which must be expressed as a matrix of your potential in the AO basis. For an example with a completely custom Hamiltonian, see here.


Permission denied for cloning via git

Hello,
git clone git@github.com:themefisher/academia-hugo.git

results in:
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Cloning over https, i.e. git clone https://github.com/themefisher/academia-hugo.git, works fine.

This is most likely an issue with your ssh key.
Let me try to guess and say that you've recently added your SSH key into github and the added that same SSH key by using ssh-add, if yes, then what happens is that adding that SSH key isn't permanent and is removed after a while (don't ask me why), so as a workaround you must then create a file in ~/.ssh/config and write IdentityFile ~/.ssh/your_private_key_name_here to it.

I have no SSH keys associated with my account at all (never got round to it).
What is the advantage of cloning via the git protocol rather than over https?

For authentication, for example, if you clone one of your repositories throught HTTPS you have to provide username and password to verify your identity.
If you use add an SSH key to your github and then locally on your machine you can clone using SSH and each time you push to the remote origin it sees that it is in fact you and doesn't ask you for any credentials.
But from what I remember cloning with SSH even without keys should work, you simply wouldn't be able to push commits to github.

Thanks - but given that the majority of users will be in the same boat (won't have access to this repo), would it not be better for the instructions to suggest cloning via https instead of git?

Probably, yeah. Now that I think about it, if I'm thinking correctly, cloning through SSH, because it's git servers, would require you actually login their servers, which considering it's SSH I would assume it would be restricted, so the issue might come from there.
They probably have some information about it in their documentation somewhere, it's a matter of looking for it.
I don't think any problem can arise from using HTTP cloning, that's how it's done all the times anyways.


GNUStep stackAbove a window on _NET_ACTIVE_WINDOW

When a GNUStep App is stacked above, receiving _NET_ACTIVE_WINDOW as client message from a dock bar, the window is stacked above the others, the relative root window properties _NET_ACTIVE_WINDOW is updated, but the APP Menus is not showed, still showing the one of the previous app.
Probably fix:

Stack above all the windows of the app, when _NET_ACTIVE_WINDOW is received.
To do this is needed to get all the windows of the app. (From the leaded window?)

Solution was to focus the window with the method [XCBWindow focus] that updated the _NET_ACTIVE_WINDOW property too.

Solution was to focus the window with the method [XCBWindow focus] that updated the _NET_ACTIVE_WINDOW property too.


Updating the look of README

Proposed Changes

The license area needs to be written to align things at right place
The copyright position can be such that it is centered aligned and at the end of README
License file should be LICENSE.md and not LICENSE.txt
Add link to the discussion session in the readme section

Added labels, if anyone is interested to be assigned then just ask

I want to do it
assign it to me please @FireCubeStudios

I have assigned but there is a pr #48 that also has improvements for the pr. wait until it is merged then work on your improvements

Sure I will wait

On it


Support for dmenu

@notandy and me just talked and we need this for i3 & dwm, etc...

Maybe add gopass completion dmenu so we don't have to add another file.

Please elaborate why we need dmenu integration for a CLI application.

By utilizing dmenu one can copy a secret to the clipboard within dmenu without actually opening and closing a new terminal just to get the password. To support this just a few lines of code are necessary.

The origininal pass includes a script for that, it's called passmenu

@MazeChaZer Yes. I'm aware of that one.
Although we don't need everything it does.
Please take a look at #47 for a first draft of our fork.


create _preprare_fsdp to pre- prepare fsdp model training

Fixes #3209
Who can review?

Fully-Sharded Data Parallism: @muellerzr

@muellerzr have you any feedback?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@BenjaminBossan

You are right; the solution needs more thorough testing. I have conducted a small test in a multi-GPU environment, but it should be tested against other configurations and models.
Raising an error when the optimizer is initialized prematurely could be a solution, but two cases emerge:

If Accelerate initializes the optimizer internally, either it creates a default optimizer with limited flexibility, or the user provides optimizer specifications. This would require external special treatment for FSDP, causing Accelerate to lose its unified interface for distributed training.
If the user initializes the optimizer post-FSDP setup, Accelerate also loses generalization in this case.

For PEFT training, which involves mixing frozen and non-frozen parameters, use_orig_params=True must be used. This ensures non-flattened parameters, meaning no changes are needed in the optimizer (I assume).
The Transformers Trainer internally uses delay_optimizer_creation and creates the optimizer after FSDP wrapping.

The [PyTorch FSDP documentation](https://pytorch.org/docs/stable/fsdp.html) mentions that mixed frozen and non-frozen parameters are only supported when use_orig_params=True. I believe this is due to the flattening process — we cannot flatten parameters with gradients together with those without. My contribution does not handle the case where use_orig_params=False because, in that scenario, the parameters remain unchanged.
Another solution would be to adapt an approach similar to the DeepSpeed integration. This involves using a single model and optimizer, and after wrapping the model with model = FSDP(model), we create the optimizer as optimizer = optimizer_class(model.parameters(), **defaults). See #3255

The PyTorch FSDP documentation mentions that mixed frozen and non-frozen parameters are only supported when use_orig_params=True. I believe this is due to the flattening process — we cannot flatten parameters with gradients together with those without.

This is true but using the right FSDP auto wrap policy, trainable and frozen parameters should be prevented from being mixed.

Another solution would be to adapt an approach similar to the DeepSpeed integration.

If this is an option here, it sounds like the more robust solution to me. Let's wait for @muellerzr return to office and get his opinion on this.

This feels a bit overengineered and the commit to transformers broke a lot of users code with saving checkpoints. For now let's not move forward with this IMO, since otherwise this would imply that the prior change broke all FSDP code, which isn't the case.

@eljandoubi Could you please check if https://github.com/huggingface/transformers/pull/35212 solved the issue (installing transformers 4.47.1 should contain the fix)?

@BenjaminBossan Since the trainer delays the creation of the optimizer, this resolves the issue for transformers. On the other hand, the core concept of accelerate is to pass the model, optimizer, dataloader, and other components simultaneously.


Resource packs for specific worlds doesn't work

When selecting resource packs when selecting or creating world and select resource pack, it adds globally instead of being selected for specific world.

But if you want it to at least work like it did in Bedrock Edition or Legacy Edition, but that would simply involve the game making a "backup" of previously "globally" applied resource packs, and apply the selected resource packs

@Wilyicaro The problem is, is that when going into world and selecting a resource pack, and exit out of the world, it's still applied

@Wilyicaro sorry, but what i'm trying to say is, is that whenever you select the resource pack and load the world, and then when exiting the world, you'll see that it's still applied globally


Add support for immutable models

There should be a way to declare models to be immutable. Perhaps by adding a keyword to the model files:
class: MyModel
immutable: true
fields:
  myField:int

Then we can also support equality and hash.

Other existing issue: https://github.com/serverpod/serverpod/issues/1359

implementing a copyWith and (de)serialization would be good aswell

@dHanel That is already supported https://docs.serverpod.dev/concepts/models#copywith, serialization is also a core feature in Serverpod and has full support.

Closing as duplicate of: https://github.com/serverpod/serverpod/issues/1359


Handle quirks of ESTAT-operated sources COMP, EMPL, GROW

Closes #162.
PR checklist

[x] Checks all ✅
[x] Update documentation
[x] Update doc/whatsnew.rst

The codecov/patch check failure here is expected: there were added lines in data source tests that are not run on every PR commit, but only on main on a schedule trigger. These should be run the first time that happens after the PR is merged.


travel blog template not mobile responsive

will resolve this issue

https://github.com/Diptenusarkar/Website-Template/pull/85 pls merge the PR @Diptenusarkar


LANDrop on F-Droid

I sent the app for proposal on F-Droid so that it can be compiled and unstable from this repository.
If you don't want it I can delete the proposal!
Thanks for reading 😊

It seems source code for mobile is not available. Could you release it ?

Mmh according to comments here https://github.com/LANDrop/LANDrop/issues/23 open source is only for desktop.
This is not what I understood while browsing on your website.


Whitelisting

[Enter feedback here]
Please review the term "whitelisting" and it's appropriateness based on Microsoft's commitment to bias free communication (https://docs.microsoft.com/en-us/style-guide/bias-free-communication)

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

ID: c5b27433-167f-6e8e-75a9-2a30e08c94e5
Version Independent ID: 11a6383e-344c-07dd-307e-1c6c54ac8c03
Content: Azure AD Pass-through Authentication - Quickstart
Content Source: articles/active-directory/hybrid/how-to-connect-pta-quick-start.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@billmath
Thanks for your feedback! We will investigate and update as appropriate.

@SnyquistBG
Thanks for catching this.  This page has been corrected.
Thanks!
Bill
#please-close


A MultiProviderListener widget

Is your feature request related to a problem? Please describe.
Adding 2 or more nested  ProviderListeners to the code to listen to multiple providers is becoming too verbose.
return ProviderListener<T>(
  provider: provider1.state,
  onChange: (context, value) {},
  child: ProviderListener<T>(
    provider: provider2.state,
    onChange: (context, value) {},
    child: ProviderListener<T>(
      provider: provider3.state,
      onChange: (context, value) {},
      child: child,
    ),
  ),
);

Describe the solution you'd like
Would be useful to have the ProviderListener child property made optional and to provide a new SingleChildWidget that accepts an array of ProviderListeners, like this:
MultiProviderListener(
  listeners: [
    ProviderListener<T>(
      provider: provider1.state,
      onChange: (context, value) {},
    ),
    ProviderListener<T>(
      provider: provider2.state,
      onChange: (context, value) {},
    ),
    ProviderListener<T>(
      provider: provider3.state,
      onChange: (context, value) {},
    ),
  ],
  child: Scaffold(),
);

This way we can fold the array to focus on the child making the code easy to follow.

No
But https://github.com/rrousselGit/river_pod/issues/335 is in WIP and would lead to an even better solution.

Closing in favor of #335


Event indicators are not showing on the first render of the calendar on android

I dont know if android is actively being supported yet but the calendar appears to work well on android except the event indicators are not showing on the calendar until you select a date or change the month

How are you retrieving your events?
Can you log and make sure those are available on initial render?

Same Problem.Event will not show until I select a date.And when I change the month the first time,it acts like that I was in May but not July.

I guess it's the same issue as #43 that you should reopen there.


Mincer throws 'TypeError: Not a string or buffer'

Good day. I encountered an error(?) with mincer compiling scss assets.
When you add an empty scss file and start recompiling the assets, mincer throws 'TypeError: Not a string or buffer'.
It's not that critical, but I wonder why this error occurs. In my opinion mincer should return empty string instead of exception.

Thanks for report!

@ixti Sorry, I forgot to mention versions: node-sass: 2.1.1, libsass: 3.1.0, mincer: latest, OS: OSX 10.9.5.

Should be solved in latest release


Integration with drawings

Hi I find myself using foundry's drawings with the "@Trigger[click]" feature of the module Trigger Happy to create buttons, levers and other interactive things on the scene. If its possible can you add a feature to prevent that clicking interaction with drawings if the token is not in range of the drawing? trigger happy may need a hook for arms reach to intercept the trigger

I was unable to automate this function, what I did was add an API for calling features from a macro. See the README for some examples. Some feedbak is welcome

This looks like it will work, but i had some issues with it. The API for ReachableById works great, i was able to have the trigger happy trigger call an intercept macro like shown below, (i wasn't sure the best way to implement Token and userId so i just used what i thought it needed as seen below let me know if there are better ways of doing this.)
if (game.armsReach.isReachableByID(canvas.tokens.controlled[0],"lJaAThjw9LdjrOtE",game.user.id)){
    //run trigger macro here
    return "is reachable";
}else{
    //return without using macro
    return "not reachable";
}

I ran into an issue with the ReachableByTag feature. Tagger?.getByTag(tag) returns a promise and the result placeableObjects[0] can't be directly referenced as your code is written.

I also noticed all the GM configurable module settings are missing so i cant change the max distance anymore.

sorry for the delay , the getByTag method  should be fixed now, i didn't notice was a async method, The userID is a optional value, for now is not used from the api, i hope to add in the future some filter so a specific actor for a specific user has some limitation.

This feature feels good with my tests, nice implementation! I also saw today tagger was updated to change the getByTag function back to an array instead of a promise. I assume that will break this module again so i've not updated tagger yet.

Ty for notice that, should be fixed "again" with version 2.1.4


show: missing parenthesis around constructors

Right now, only constructors with one argument have parenthesis around them. Omitting parenthesis is ok for nullary constructors, but shouldn't be for n-ary ones (as the the output can no longer simply be pasted into the top-level):
type t = A | B of t | C of t*t [@@deriving show];;
show @@ A;; (* A *)
show @@ B A;; (* (B A) *)
show @@ C (A, A);; (* C (A, A) but should be (C (A, A)) *)
show @@ B (C (A, A));; (* (B C (A, A)) <- problem *)

@c-cube, I think you altered this last? https://github.com/whitequark/ppx_deriving/commit/8048cf70cb156a776744e14676e6b6610a41809a
I don't quite remember what was the motivation for the change.

Yes indeed, I changed it slightly (I think it was because I found Some (1) uglier than (Some 1)). I see the problem for nested constructors. A nice thing to have would be to use the old behavior for unary constructors when the argument's type requires it (e.g. another non-nullary constructor, functions, custom printer), but remove parenthesis if the argument doesn't need any (record, primitive).

Yes, that's probably better than adding them everywhere.

@c-cube So, would you fix this? If not I will revert your change.

This is still a problem :( :( :(

@jaredly can you fix @vogler's commit above?

Yeah, it works (after I updated it to the current source)

Thanks! I didn't update the tests tho :/ so there's still a bit of work to be done


Heroku

Hard-coded URL?

Fixed all bugs. Added in ruby version in the gemfile and fixed the user_mailer issues.


New version of pyspark mnist kmeans example notebook

Proposal for a new version and revision of the content for the pyspark mnist kmeans example notebook.
Main changes:

Included example of using Spark pipeline with hybrid or SageMaker-only pipelines
Showed how to create custom SageMakerEstimator in SageMaker-Spark SDK
Showcase re-use of endpoints, models, and training job data
Enhance clean up to clean up models in Pipelines

I also have a few diagrams for these that I can include. As they are images, it might increase the load time of the Jupyter notebook browser however.

Thanks @JonathanTaws !
The content is excellent. It might make sense to split this up into multiple notebooks, since the running time for the whole notebook is pretty long: one for hybrid pipeline, one for SageMaker-only pipeline, one for custom SageMakerEstimator. (I think it makes sense to keep re-using existing endpoints in this one.).
I think it's fine to include the images in the notebooks. The effect of reasonably sized images on notebook load time should be negligible.
Thoughts @djarpin ?

I went ahead and split up the notebookes, and included some diagrams. Any thoughts @andremoeller and @djarpin ?

I am really looking forward to trying out this set of sample notebooks after the PR is merged.

Thanks @djarpin for looking into this, I've taken into account all changes and they have been pushed into the PR.
Let's review exactly how we want to frame the PCA on Spark vs. PCA on SageMaker part.

Awesome! In that case we're good to go if there's nothing else to address.
Le lun. 30 avr. 2018 à 09:15, David Arpin<EMAIL_ADDRESS>a
écrit :

@djarpin commented on this pull request.
In sagemaker-spark/pyspark_mnist/pyspark_mnist_pca_mllib_kmeans.ipynb
https://github.com/awslabs/amazon-sagemaker-examples/pull/233#discussion_r184900444
:

"\n",

"In each row:\n",
"* The label column identifies the image's label. For example, if the image of the handwritten number is the digit 5, the label value is 5.\n",
"* The features column stores a vector (org.apache.spark.ml.linalg.Vector) of Double values. The length of the vector is 784, as each image consists of 784 pixels. Those pixels are the features we will use. \n",
"\n",
"\n",
"\n",
"As we are interested in clustering the images of digits, the number of pixels represents the feature vector, while the number of classes represents the number of clusters we want to find. "
]
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"### Create a hybrid pipeline with Spark PCA and SageMaker K-Means\n",
"To perform the clustering task, we will first running PCA on our feature vector, reducing it to 50 features. Then, we can use K-Means on the result of PCA to apply the final clustering. We will create a Pipeline consisting of 2 stages: the PCA stage, and the K-Means stage. \n",

This sounds good to me. Let's go with it. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/amazon-sagemaker-examples/pull/233#discussion_r184900444,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFS21hlFj1fRpjH4PF_shTLPonusXSQlks5ttleJgaJpZM4TI2sY
.


Restructuring the entry listing info endpoint

Fixes #70

I have merged this PR for now despite the ongoing discussion about endpoint list (by @CasperWA) and remaining constraints on IDs (by @rartino). I see both remaining issues as somewhat logically separate from what has been done in this PR. I will open a follow-up PR for clearing up things concerning IDs.


A new Cookiecutter community fork named Cookieninja

Unfortunately it seems that the Cookiecutter project is on hiatus, and new issues (including ones that are required by the cruft project) aren't being worked on.
We started working on a new community fork of the Cookiecutter project, named Cookieninja.
The fork is found at: https://github.com/cookieninja-generator/cookieninja
We have re-opened and merged the many of the PRs from the Cookiecutter project in Cookieninja, including the PR by @simonwardjones that fixes cruft issue #166 (the PR is at https://github.com/cookieninja-generator/cookieninja/pull/34)
We're trying to bring the life back to the Cookiecutter project.
We are committed to addressing each issue in up to 1 week from the day it's opened, and reviewing and merging each PR in up to 2 weeks from the day it's opened (if there are no issues with it).
We'd really like you to join the fork, star it, contribute to it and create new issues!
Thank you :)

Is that means you might build cruft functionality into cookie ninja instead of layering it on top?

Thanks for the informational issue. Given that Cookiecutter seems to be alive again, I'm closing this. We currently don't have plans on integration with alternative template generators.


Document use of Lability script with VMware Workstation

Specifically setting the OS configuration to "Hyper-V (unsupported)" and not "Windows 10 x64).

Thank you Greg!  I'm adding to documentation now

I'm going to leave this open for a while just in case no one reads the documentation ;)

Updated -- closing issue


disable half precision support properly

Nvidia GPU before compute capability 5.3 does not support IEEE FP16 (half) precision operation.
However, cuda 12.2+ relax these some limitation, so we still support these GPUs with GINKGO_ENABLE_HALF=ON after cuda 12.2.
We only support these GPUs with GINKGO_ENABLE_HALF=OFF before cuda 12.2

[ ] wait for the check on the real GPU below the requirment

Just a nit with the description: There is no 5.3, the next compute capability is 6.0.

I removed the last 5.2 device I had, because the system kept running into kernel panics. I would be fine if we didn't test this, or pushed the device requirements to 6.0, because that's the only architecture we actually have GPUs available for.

5.3 is listed in cuda 11.0

That's the Jetson Nano, I don't think we need to consider them.

The Tegra X1 and Jetson TX1 GPUs are 5.3. They officially do have half precision FP support, so technically with this PR we should be able to run on them. But I am not sure it is easy to confirm that, as we dont have access to those.

I was thinking earlier about the term "supported" - what does it mean when we state that we support certain versions? We still list classical Intel compiler support, but we no longer have pipelines for it. Does it mean it should work, so does it mean we will fix issues if it doesn't work, or does it mean we are actively monitoring it via CI?

I was thinking earlier about the term "supported" - what does it mean when we state that we support certain versions? We still list classical Intel compiler support, but we no longer have pipelines for it. Does it mean it should work, so does it mean we will fix issues if it doesn't work, or does it mean we are actively monitoring it via CI?

I think it means the first on. We also list GCC 7+, so we expect that all versions 7.0-14.? work, but of course we are not (and will not) testing every version in our CI.

Fixing issues means we should also be able to confirm when they are fixed. If we don't have the necessary hardware available, I would try to avoid claiming we can support them.

Some libraries split them into two: Minimum supported version (confirmed/tested with CI): x.x.x and Might work (untested with CI, but might work), but I guess we cant really call the latter "Supported", and can say that we support only versions/hardware we test on.

Yes, I was thinking along the same lines. If we split up the list of supported versions, we can be more explicit.

We have P100, Titan X, V100, RTX 2060, A2 (potentially A100 if we need it), L40S and H100 available, so we could cover the full range if we wanted to.

Also, I do not think additional claim on the testing hardware help anything.
Users run it with V100 or A100 for example and face issues. We will still need to fix it, right?

For CPUs: Contrary to SASS, x86_64 is stable between hardware architectures (we should likely add a variant of aarch64), and we don't compile with -march=native, so beyond CPU bugs, it is unlikely to lead to different behaviors between microarchitectures.


Rename installer-config.yaml to installer-channels.yaml

Resolves https://github.com/wildfly-extras/prospero/issues/188

@spyrkob Did you want to do something beyond renaming the constant name and related variable names?

Rebased...


Add nextBatch() method in ParquetRecordReader for MR based engine use

As discussed in #3 , add the method like ParquetReader does.
MR jobs need this reader to read batch. Currently we have ParquetReader to read batches, but ParquetInputFormat does not provide a similar reader for MR based engine like Hive to use.

@nezihyigitbasi , this is the added method in ParquetRecordReader as we discussed before. Could you please take a look? Thanks.
BTW, in PR #3 , the nextBatch() method of InternalParquetRecordReader changed, so I will update this implementation after that patch merged.
Anyway, the general idea here should be the same and can be reviewed.

@dongche added some comments. Can you please add a unit test for your changes?

Thanks for your review!
Sure, I am updating this API and Hive code based on your new code. Will update this patch after things go well.

Patch updated.

The implementation of nextBatch() in ParquetRecordReader is copied from ParquetReader and they has the same behavior.
Add unit test for this change.

Thanks @dongche this looks good, I only have a few minor comments. I now moved the vector branch to https://github.com/nezihyigitbasi-nflx/parquet-mr/commits/vector and rebased it to the latest parquet-mr master, I will continue making changes there. Can you please open a new PR against that branch?

Patch updated to address comments. Thanks! @nezihyigitbasi
Then a new PR https://github.com/nezihyigitbasi-nflx/parquet-mr/pull/1 is open to that branch.


add version for google operated bigtables

this one still needs an approval to be able to merge it.


NEW SearchableDropdownField

Issue https://github.com/silverstripe/silverstripe-admin/issues/1618
This PR is derived from silverstripe/tagfield
Note that it differs from tagfield in that it uses "ID" (int) for "Value" rather than "Title" (string) which was fine for simply creating tags, but not appropriate for regular relations. This means this field cannot be used for creating new objects like tagfield can, so it's not a full replacement for tagfield.
Admin PR

https://github.com/silverstripe/silverstripe-admin/pull/1625

For method signatures that don't match parent classes e.g. SingleSelectField it's because they now either have strong return types, or looser params defined in docblocks.  This is allowed in PHP via covariance (tighter return types on sublasses) and contravariance (looser param types on subclasses) - https://www.php.net/manual/en/language.oop5.variance.php

The problem mentioned in https://github.com/silverstripe/silverstripe-framework/pull/11057#issuecomment-1850952010 has still not been fixed

Not sure if this is an admin or a framework PR problem, but with a many_many list, the values aren't saved (or, if they are saved, they at least don't display in the field after saving)
Code:
use SilverStripe\CMS\Model\SiteTree;
use SilverStripe\Forms\SearchableMultiDropdownField;
use SilverStripe\Taxonomy\TaxonomyTerm;

class Page extends SiteTree
{
    private static $many_many = [
        'Terms' => TaxonomyTerm::class
    ];

    public function getCMSFields()
    {
        $fields = parent::getCMSFields();
        $fields->addFieldsToTab('Root.Main', [
            SearchableMultiDropdownField::create('Terms', 'Terms', TaxonomyTerm::get(), $this->Terms(), 'Name'),
        ]);
        return $fields;
    }
}

With a has_one relation, before trying to save any records, the first option is displayed as though it's selected:

(note that "a" here is the name of a taxonomy term in the db)
The has_one relation does correctly save when I select a different option and save the page, so that's good.

With a has_one relation, before trying to save any records, the first option is displayed as though it's selected:

That's the default behaviour of the existing Dropdownfield and I replicated it. It's a really obnoxious default behaviour IMO though can be switched off by just called ->setHasEmptyDefault(true);

the values aren't saved

Your code example worked fine on my computer, did you forget to dev build flush?

the values aren't saved
Your code example worked fine on my computer, the values saved, did you forget to dev build flush?

I did not forget - though clearly either I did something wrong, or the latest batches of changes fixed it, because it works now 👍

With a has_one relation, before trying to save any records, the first option is displayed as though it's selected:
That's the default behaviour of the existing Dropdownfield and I replicated it. It's a really obnoxious default behaviour IMO though can be switched off by just called ->setHasEmptyDefault(true);

That's not the expected behaviour in my mind. Just because DropdownField does that doesn't mean this field should. DropdownField isn't explicitly for working with relations. This field is explicitly for working with relations - and as such the expected behaviour changes a little. It should show that there is no relation stored in the field until such a time as the user stores a relation in the field.
My recommendation is to call $this->setHasEmptyDefault(true); in the constructor. This will preserve the functionality to allow the first item as a default value if people really want that, but requires developers to opt into that.

This still needs to be addressed: https://github.com/silverstripe/silverstripe-framework/pull/11057#issuecomment-1850952010

Have added the $this->setHasEmptyDefault(true) on the single dropdown contructor
Have rebased to get https://github.com/silverstripe/silverstripe-framework/pull/11073/files which solves the lazyLoad limit not being respected

As discussed in person, please set the default lazy-load limit to 100


shell: Fix thread priority

Removed kconfig option for setting shell thread priority and fix
it to K_LOWEST_APPLICATION_THREAD_PRIO.
Similar issue as in #11762. Kconfig default was -2 which was almost the highest priority.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

@carlescufi : This is quite urgent change and a low hanging fruit. When log and shell have different priorities I can see some artifacts when boot banner is printed.

Codecov Report

Merging #11862 into master will decrease coverage by 0.1%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master   #11862      +/-   ##
==========================================
- Coverage   51.43%   51.33%   -0.11%
==========================================
  Files         231      231
  Lines       28751    28751
  Branches     7152     7152
==========================================
- Hits        14789    14758      -31
- Misses      11144    11181      +37
+ Partials     2818     2812       -6

Impacted Files
Coverage Δ

subsys/shell/shell.c
31.36% <0%> (-3.76%)
:arrow_down:

subsys/shell/shell_dummy.c
37.14% <0%> (-8.58%)
:arrow_down:

Continue to review full report at Codecov.

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


[Startup] Fix Play services install and sign in flow

Replaces ephemeral navigation requests with a "main UI state" which gets applied at start up. This patch resolves existing issues, but there are likely several race conditions lurking due to complexity of the startup/install flow. We should revisit the design on this flow to make it easier to understand and to avoid cancellation exceptions or duplicate side effects (https://github.com/google/ground-android/issues/2923).
Fixes #2919 by restore UI state on on resume.
Fixes #2783

@shobhitagarwal1612 @anandwana001 This actually won't work - collecting the so-called "MainUiState" on resume will navigate the user away from their current screen in many cases (ToS, survey list, etc), since those screens are not represented in the UiState.
Filed https://github.com/google/ground-android/issues/2934 to track, moving back to Draft :/

TODO:

[ ] Move sign-in flow logic out of Main and into StartUp, SignIn and TermsOfService.
[ ] StartUp will direct to the Home is already signed in, SignIn if not.
[ ] SignIn will direct to TermsOfService if required, otherwise SurveySelector.
[ ] TermsOfService should direct to Home
[ ] Main should listen for sign out events and redirecting to SignIn if necessary.


Helm chart - imagePullSecrets are not applied to post-install-job and pre-delete-job

Bug description
To prevent external dependencies, we are replicating Capsule images to a private repo, for which we need to auth. However, we run into issues with the post-install-job and pre-delete jobs, as these don't have imagePullSecrets specified in the spec.

https://github.com/clastix/capsule/blob/master/charts/capsule/templates/post-install-job.yaml
https://github.com/clastix/capsule/blob/master/charts/capsule/templates/pre-delete-job.yaml

How to reproduce
Steps to reproduce the behavior:

Store kubectl and capsule images in a private repo
Specify imagePullSecrets in helm chart values and modify image source repository to private repo
Install helm chart using values

Expected behavior
imagePullSecrets specified via helm chart values should also be applied to post-install-job and pre-delete-job if specified.
Logs
If applicable, please provide logs of capsule.
In a standard stand-alone installation of Capsule,
you'd get this by running kubectl -n capsule-system logs deploy/capsule-controller-manager.
Additional context

Capsule version: 0.1.0
Helm Chart version: v0.1.3

Hey @slushysnowman, you're totally right: would you like to contribute to this?
Just let me know so I can track it properly!

Yep, I'll work on this, was literally about to start.

Chart has been released, update your local repository! 👀


Add support for using lazy types in generics

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

Add support for using lazy types inside generics.


this is just a test - don't approve

I just want to see how the checks work, please don't approve.

hmm I don't want the checks to pass so I'll try something


Client heartbeat is throwing incorrect ConnectionResetException

Hi,
Thank you for all your work on rabbitpy.
I think I have found a bug but I don't understand it fully.
First, it seems that a heartbeat is send by the server (v3.1.5) only if there is no exchanged message, so the current implementation will fail when a scenario like this occurs:

No message is exchanged for negotiated heartbeat interval => the server sends a heartbeat
rabbitpy answer and store it (Channel0._last_heartbeat)
Some message are regularly exchanged and the server doesn't send heartbeat
The heartbeat check is triggered and the heartbeat is too old since it was not refreshed: an ConnectionResetException is raised despite the connection is working perfectly

Moreover, in some case (but I don't manage to reproduce it everytime), when I launch a basic consumer, the ConnectionResetException is raised in the io-thread and not in the consumming thread leading the latter to hang forever (the corresponding io thread crashed).
Here is a stacktrace for the io thread in this case:
Exception in thread 0x7fb5a0015ad0-io:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.6/site-packages/rabbitpy/io.py", line 348, in run
    self._loop.run()
  File "/usr/lib/python2.6/site-packages/rabbitpy/io.py", line 190, in run
    self._poll()
  File "/usr/lib/python2.6/site-packages/rabbitpy/io.py", line 235, in _poll
    self._read()
  File "/usr/lib/python2.6/site-packages/rabbitpy/io.py", line 249, in _read
    self._data.read_callback(self._data.fd.recv(MAX_READ))
  File "/usr/lib/python2.6/site-packages/rabbitpy/io.py", line 386, in on_read
    self._channels[0][0].on_frame(value[1])
  File "/usr/lib/python2.6/site-packages/rabbitpy/channel0.py", line 110, in on_frame
    self._write_frame(heartbeat.Heartbeat())
  File "/usr/lib/python2.6/site-packages/rabbitpy/base.py", line 318, in _write_frame
    self._check_for_exceptions()
  File "/usr/lib/python2.6/site-packages/rabbitpy/base.py", line 218, in _check_for_exceptions
    raise exception
ConnectionResetException: No heartbeat in 1799.9976542 seconds

Here is the stacktrace for the running consuming thread:
Thread 4 (Thread 0x7fb5a4cde700 (LWP 56466)):
#2 <built-in function sleep>
#4 file '/usr/lib64/python2.6/threading.py', in 'wait'
#8 file '/usr/lib64/python2.6/Queue.py', in 'get'
#12 file '/usr/lib/python2.6/site-packages/rabbitpy/base.py', in '_read_from_queue'
#15 file '/usr/lib/python2.6/site-packages/rabbitpy/base.py', in '_wait_on_frame'
#19 file '/usr/lib/python2.6/site-packages/rabbitpy/channel.py', in '_consume_message'
#22 file '/usr/lib/python2.6/site-packages/rabbitpy/amqp_queue.py', in 'next_message'
#24 file '/usr/lib/python2.6/site-packages/rabbitpy/amqp_queue.py', in '__iter__'

I hope this will be enough for you to understand the problem, but if I can be of any help, I will be glad to help.

I saw this as a possibility when reviewing the implementation but was never able to fully reproduce it. Mostly as my understanding of the heartbeat mechanic is somewhat limited.

Thanks for the info, hopefully I can find the case where it's not working as expected.
re "Some message are regularly exchanged and the server doesn't send heartbeat":
You should always have a heartbeat frame sent by the server in the pre-negotiated interval.
Can you set logging to debug mode:
import logging

logging.basicConfig(level=logging.DEBUG)

and then connect to RabbitMQ with your problematic app and post the log lines from DEBUG:rabbitpy.channel0:Received frame: 'Connection.Start to DEBUG:rabbitpy.channel0:Connection opened?
Here's an example from my laptop:
DEBUG:rabbitpy.channel0:Received frame: 'Connection.Start'
DEBUG:rabbitpy.channel0:Server information: 'Licensed under the MPL.  See http://www.rabbitmq.com/'
DEBUG:rabbitpy.channel0:Server product: 'RabbitMQ'
DEBUG:rabbitpy.channel0:Server copyright: 'Copyright (C) 2007-2014 GoPivotal, Inc.'
DEBUG:rabbitpy.channel0:Server supports exchange_exchange_bindings: True
DEBUG:rabbitpy.channel0:Server supports connection.blocked: True
DEBUG:rabbitpy.channel0:Server supports authentication_failure_close: True
DEBUG:rabbitpy.channel0:Server supports basic.nack: True
DEBUG:rabbitpy.channel0:Server supports per_consumer_qos: True
DEBUG:rabbitpy.channel0:Server supports consumer_priorities: True
DEBUG:rabbitpy.channel0:Server supports consumer_cancel_notify: True
DEBUG:rabbitpy.channel0:Server supports publisher_confirms: True
DEBUG:rabbitpy.channel0:Server cluster_name: 'rabbit@gmr-mbp'
DEBUG:rabbitpy.channel0:Server platform: 'Erlang/OTP'
DEBUG:rabbitpy.channel0:Server version: '3.4.1'
DEBUG:rabbitpy.base:Writing frame: Connection.StartOk
DEBUG:rabbitpy.channel0:Received frame: 'Connection.Tune'
DEBUG:rabbitpy.channel0:Started a heartbeat timer that will fire in 1160 sec
DEBUG:rabbitpy.base:Writing frame: Connection.TuneOk
DEBUG:rabbitpy.base:Writing frame: Connection.Open
DEBUG:rabbitpy.channel0:Received frame: 'Connection.OpenOk'
DEBUG:rabbitpy.channel0:Connection opened

Also if you have an example that demonstrates the behavior that you can share, that would be helpful.

Here is a script and the logs to reproduce the first problem.
https://gist.github.com/paradis/615e3d5607aef2f93597
# rabbitmqctl status
Status of node '<>' ...
[{running_applications,
     [{rabbitmq_management,"RabbitMQ Management Console","3.1.5"},
      {rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.1.5"},
      {webmachine,"webmachine","1.10.3-rmq3.1.5-gite9359c7"},
      {mochiweb,"MochiMedia Web Server","2.7.0-rmq3.1.5-git680dba8"},
      {rabbitmq_management_agent,"RabbitMQ Management Agent","3.1.5"},
      {rabbit,"RabbitMQ","3.1.5"},
      {os_mon,"CPO  CXC 138 46","2.2.7"},
      {inets,"INETS  CXC 138 49","5.7.1"},
      {xmerl,"XML parser","1.2.10"},
      {mnesia,"MNESIA  CXC 138 12","4.5"},
      {amqp_client,"RabbitMQ AMQP Client","3.1.5"},
      {sasl,"SASL  CXC 138 11","2.1.10"},
      {stdlib,"ERTS  CXC 138 10","1.17.5"},
      {kernel,"ERTS  CXC 138 10","2.14.5"}]},
 {os,{unix,linux}},
 {erlang_version,
     "Erlang R14B04 (erts-5.8.5) [source] [64-bit] [rq:1] [async-threads:30] [kernel-poll:true]\n"},

Good news? I was able to reliably replicate this in production over the weekend.
I'm impacted time wise early this week and need to work on replicating it with debug logging turned on to figure out exactly what's going on. I'll try and address it by the end of the week.

I've just pushed a change that should address this, updating the client side heartbeat checker to get reset on every frame received from the server. This should prevent this from happening in the future.


Impl multiplication and division for frequency wrappers

This allows the following operations:

T * u32 (T)
T *= u32 (T)
T / u32 (T)
T /= u32 (T)
T / T (u32)

It's implemented for the following types:

Hertz
KiloHertz
MegaHertz
Bps

Sorry for the delay. Looks like a good change to me! Would you mind also adding an entry to CHANGELOG.md about it?

Ping @dbrgn, any chance to getting the request @TheZoq2 addressed?

Ping @dbrgn, any chance to getting the request @TheZoq2 addressed?

Yes, sure! Sorry, I somehow missed that comment.
PR is updated and rebased.

Thanks!


Update pub.dev

Can you please update the version on pub.dev to match GitHub?

Version 1.1.0 was published today


Added face recognition demo

Added interactive face recognition demo and its documentation. Implemented in Python. Tested on Windows 10, Ubuntu 16.04, OpenVINO R5, Python 2.7, Python 3.5, Python 3.6, in Docker. Supports both camera and video file input.
See discussions in #23.

@snosov1, rebased the branch.

Jenkins please retry build

Jenkins please retry a build

Jenkins please retry a build

There are still things that, I think, could be improved, but they are rather minor and we can work on this later. I want to, finally, merge this demo.
@vmatveic Slava, myself and @grib0ed0v have reviewed and approve the PR. Please, make a final review in terms of code/PR structure and merge or approve.

@vmatveic Slava, any news?

@zhiltsov-max Maxim, can you, please, check if it works with R1'2019? We'll merge if it's fine.

@snosov1 can this be closed? is it replaced by https://github.com/opencv/open_model_zoo/pull/151?

Superseded by #151


[webview_flutter] Add new entrypoint that uses hybrid composition on Android

Related Issues
Fixes https://github.com/flutter/flutter/issues/61133
Tests on stable will fail until hybrid views support moves to stable
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

When hybrid views support will move to stable? Thanks!

@pichillilorenzo It's on stable now

FYI, the documentation is available on https://github.com/flutter/flutter/wiki/Hybrid-Composition

This PR is waiting for dynamic thread merging. FYI @cyanglaz

@pichillilorenzo It's on stable now

So this PR has been released in 1.20.0?

@amirh would you mind reviewing this PR as well?
Here's what I had in mind so far:

Have this PR ready, and merge it when the 1.22 comes out.
Decide if a separate entrypoint or feature flag is preferred. I don't have strong preference, but Maurice said that a flag is easier to implement.
Follow up on each issue fixed by this PR.

This change worked well for my problem. When will the webview_flutter be updated? Thanks!

Offline chat: let's revert this PR and bump the Flutter SDK in pubspec.yaml to 1.22.

Moved to https://github.com/flutter/plugins/pull/3067