Testing/wrapper

Branch containing wrapper and basic method for mass-testing algorithms implemented according to OsipiBase.
The "standardized" algorithms are contained in the src/standardized folder. Apart from identification attributes and requirements, they consist of a single ivim_fit method which performs the fit according to the algorithm. These inherit from OsipiBase which is our default object that will be used for interaction. To run a fit, the OsipiBase.osipi_fit method should be called. This allows for mass-testing later.
The testing is performed in tests/unit_tests/test_ivim_fit.py

Can we make the tests in tests/unit_tests/test_ivim_fit.py pass? Currently 2 fail.
Also, how is tests/unit_tests/simple_test_run_of_algorithm.py supposed to be used? Currently I get a fixture error if I run pytest in that file.

Is it intentional to add the bytecode to the repo?

What is the difference between the ivim_fit and osipi_fit methods?

Can we make the tests in tests/unit_tests/test_ivim_fit.py pass? Currently 2 fail. Also, how is tests/unit_tests/simple_test_run_of_algorithm.py supposed to be used? Currently I get a fixture error if I run pytest in that file.

I believe the two that fail is due to flaws in the algorithm. For example, if you uncomment the lines that have to do with negative values, we only get one fail. In the results, we can see that it is the ETP algorithm that fails, while the IAR alorithm doesn't. The difference between the two is that ETP does a linear fit, while IAR is a simple bi-exponential NLLS fit. So if IAR passes, then it's probably something with the linear fit that can't handle those specific testing parameters. You can try to play around with the tolerances and see if you can get ETP to pass. In the end, I think Eric knows more about the issue than I do.
Regarding simple_test_run_of_algorithms, this is a simple "run" script, which initiates and performs a single fit for the algorithms implemented in OsipiBase. It was used when I wrote the standardized versions, just to see if they worked. I added it to the repo as it could be useful for doing similar test runs when we implement the rest of the submissions according to OsipiBase. So it is not supposed to be ran with pytest.

Is it intentional to add the bytecode to the repo?

Sorry about that, though I had them in git ignore. I think I've removed all of them now

What is the difference between the ivim_fit and osipi_fit methods?

My thinking is that osipi_fit should include checks, where inputs are compared to algorithm requirements defined as attributes in the algorithm subclass. So instead of calling the checks in all ivim_fit methods we write, they are instead called from the parent class. So it's more for future functionality.
Also, we may develop the testing further. Test for different fit settings, different dimensions, etc. By having a fit method that performs checks, we can quite practically just loop over them in testing, and run tests on methods that can take the inputs we provide.

Can we make the tests in tests/unit_tests/test_ivim_fit.py pass? Currently 2 fail. Also, how is tests/unit_tests/simple_test_run_of_algorithm.py supposed to be used? Currently I get a fixture error if I run pytest in that file.

I believe the two that fail is due to flaws in the algorithm. For example, if you uncomment the lines that have to do with negative values, we only get one fail. In the results, we can see that it is the ETP algorithm that fails, while the IAR alorithm doesn't. The difference between the two is that ETP does a linear fit, while IAR is a simple bi-exponential NLLS fit. So if IAR passes, then it's probably something with the linear fit that can't handle those specific testing parameters. You can try to play around with the tolerances and see if you can get ETP to pass. In the end, I think Eric knows more about the issue than I do.
Regarding simple_test_run_of_algorithms, this is a simple "run" script, which initiates and performs a single fit for the algorithms implemented in OsipiBase. It was used when I wrote the standardized versions, just to see if they worked. I added it to the repo as it could be useful for doing similar test runs when we implement the rest of the submissions according to OsipiBase. So it is not supposed to be ran with pytest.

Regarding the failing tests, I haven't looked closely at the code yet, but I think there are a few things we need to figure out.
First, I'm a little suspicious of the failures because isn't the same test data passing in main?
Regardless of the details though, I think this is showing that not all algorithms can handle all data to the same degree and we need to be flexible about that. I think the best approach would be to have some default test values for each algorithm that we can load and use for testing. That would preserve the unit testing we want to do and also allow customized bounds (or other customizations) for each algorithm. Failing that I think we'd just need to be too permissive on the testing side to generate data and the value of the testing becomes basically nothing.
I'm also OK just removing the linear fitting from the list to be tested and replacing it with another, more capable algorithm. IMO it would be interesting to include as a baseline reference algorithm, but if it's causing too much trouble then let's take the easy path for now.

Can we make the tests in tests/unit_tests/test_ivim_fit.py pass? Currently 2 fail. Also, how is tests/unit_tests/simple_test_run_of_algorithm.py supposed to be used? Currently I get a fixture error if I run pytest in that file.

I believe the two that fail is due to flaws in the algorithm. For example, if you uncomment the lines that have to do with negative values, we only get one fail. In the results, we can see that it is the ETP algorithm that fails, while the IAR alorithm doesn't. The difference between the two is that ETP does a linear fit, while IAR is a simple bi-exponential NLLS fit. So if IAR passes, then it's probably something with the linear fit that can't handle those specific testing parameters. You can try to play around with the tolerances and see if you can get ETP to pass. In the end, I think Eric knows more about the issue than I do.
Regarding simple_test_run_of_algorithms, this is a simple "run" script, which initiates and performs a single fit for the algorithms implemented in OsipiBase. It was used when I wrote the standardized versions, just to see if they worked. I added it to the repo as it could be useful for doing similar test runs when we implement the rest of the submissions according to OsipiBase. So it is not supposed to be ran with pytest.

Regarding the failing tests, I haven't looked closely at the code yet, but I think there are a few things we need to figure out. First, I'm a little suspicious of the failures because isn't the same test data passing in main? Regardless of the details though, I think this is showing that not all algorithms can handle all data to the same degree and we need to be flexible about that. I think the best approach would be to have some default test values for each algorithm that we can load and use for testing. That would preserve the unit testing we want to do and also allow customized bounds (or other customizations) for each algorithm. Failing that I think we'd just need to be too permissive on the testing side to generate data and the value of the testing becomes basically nothing. I'm also OK just removing the linear fitting from the list to be tested and replacing it with another, more capable algorithm. IMO it would be interesting to include as a baseline reference algorithm, but if it's causing too much trouble then let's take the easy path for now.

I think it's good to see some fails. It means that our tolerances are working. I don't know how it affects the results though. Can we still log the estimates, etc?

Can we make the tests in tests/unit_tests/test_ivim_fit.py pass? Currently 2 fail. Also, how is tests/unit_tests/simple_test_run_of_algorithm.py supposed to be used? Currently I get a fixture error if I run pytest in that file.

I believe the two that fail is due to flaws in the algorithm. For example, if you uncomment the lines that have to do with negative values, we only get one fail. In the results, we can see that it is the ETP algorithm that fails, while the IAR alorithm doesn't. The difference between the two is that ETP does a linear fit, while IAR is a simple bi-exponential NLLS fit. So if IAR passes, then it's probably something with the linear fit that can't handle those specific testing parameters. You can try to play around with the tolerances and see if you can get ETP to pass. In the end, I think Eric knows more about the issue than I do.
Regarding simple_test_run_of_algorithms, this is a simple "run" script, which initiates and performs a single fit for the algorithms implemented in OsipiBase. It was used when I wrote the standardized versions, just to see if they worked. I added it to the repo as it could be useful for doing similar test runs when we implement the rest of the submissions according to OsipiBase. So it is not supposed to be ran with pytest.

Regarding the failing tests, I haven't looked closely at the code yet, but I think there are a few things we need to figure out. First, I'm a little suspicious of the failures because isn't the same test data passing in main? Regardless of the details though, I think this is showing that not all algorithms can handle all data to the same degree and we need to be flexible about that. I think the best approach would be to have some default test values for each algorithm that we can load and use for testing. That would preserve the unit testing we want to do and also allow customized bounds (or other customizations) for each algorithm. Failing that I think we'd just need to be too permissive on the testing side to generate data and the value of the testing becomes basically nothing. I'm also OK just removing the linear fitting from the list to be tested and replacing it with another, more capable algorithm. IMO it would be interesting to include as a baseline reference algorithm, but if it's causing too much trouble then let's take the easy path for now.

I think it's good to see some fails. It means that our tolerances are working. I don't know how it affects the results though. Can we still log the estimates, etc?

All the tests should "pass". For example, if 3 are failing, who is tracking which 3 are failing? What if one starts working again, but a different one then starts to fail so we still have 3 failing? And who is tracking that it's just 3 failing? If we expect tests to fail then we should mark them as expected to fail, which in effect makes them "pass". https://docs.pytest.org/en/7.1.x/how-to/skipping.html That's a valid test, we just need to mark the ones that we expect to fail in some way.

Can we make the tests in tests/unit_tests/test_ivim_fit.py pass? Currently 2 fail. Also, how is tests/unit_tests/simple_test_run_of_algorithm.py supposed to be used? Currently I get a fixture error if I run pytest in that file.

I believe the two that fail is due to flaws in the algorithm. For example, if you uncomment the lines that have to do with negative values, we only get one fail. In the results, we can see that it is the ETP algorithm that fails, while the IAR alorithm doesn't. The difference between the two is that ETP does a linear fit, while IAR is a simple bi-exponential NLLS fit. So if IAR passes, then it's probably something with the linear fit that can't handle those specific testing parameters. You can try to play around with the tolerances and see if you can get ETP to pass. In the end, I think Eric knows more about the issue than I do.
Regarding simple_test_run_of_algorithms, this is a simple "run" script, which initiates and performs a single fit for the algorithms implemented in OsipiBase. It was used when I wrote the standardized versions, just to see if they worked. I added it to the repo as it could be useful for doing similar test runs when we implement the rest of the submissions according to OsipiBase. So it is not supposed to be ran with pytest.

Regarding the failing tests, I haven't looked closely at the code yet, but I think there are a few things we need to figure out. First, I'm a little suspicious of the failures because isn't the same test data passing in main? Regardless of the details though, I think this is showing that not all algorithms can handle all data to the same degree and we need to be flexible about that. I think the best approach would be to have some default test values for each algorithm that we can load and use for testing. That would preserve the unit testing we want to do and also allow customized bounds (or other customizations) for each algorithm. Failing that I think we'd just need to be too permissive on the testing side to generate data and the value of the testing becomes basically nothing. I'm also OK just removing the linear fitting from the list to be tested and replacing it with another, more capable algorithm. IMO it would be interesting to include as a baseline reference algorithm, but if it's causing too much trouble then let's take the easy path for now.

I think it's good to see some fails. It means that our tolerances are working. I don't know how it affects the results though. Can we still log the estimates, etc?

All the tests should "pass". For example, if 3 are failing, who is tracking which 3 are failing? What if one starts working again, but a different one then starts to fail so we still have 3 failing? And who is tracking that it's just 3 failing? If we expect tests to fail then we should mark them as expected to fail, which in effect makes them "pass". https://docs.pytest.org/en/7.1.x/how-to/skipping.html That's a valid test, we just need to mark the ones that we expect to fail in some way.

Nice bit of background info Eric, was not really aware of this expected to fail functionality :).

Looks like it has conflicts. Otherwise good!

Looks like it's all ready to merge. Nice work!

Looks good! We should get this merged so the rest of the testing can be more easily based off of it.


Try to restore xvfb action

Codecov Report
Patch and project coverage have no change.

Comparison is base (84bf3ad) 86.65% compared to head (74ae0ca) 86.65%.

:exclamation: Current head 74ae0ca differs from pull request most recent head 509ecbd. Consider uploading reports for the commit 509ecbd to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #221   +/-   ##
=======================================
  Coverage   86.65%   86.65%
=======================================
  Files          50       50
  Lines        4712     4712
=======================================
  Hits         4083     4083
  Misses        629      629

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


(bug) dashmate : does not seem to be able to fetch Dashmate v0.24.20 and will not start Dashmate

After stopping my Dashmate with command dashmate stop and then provide commands npm update -g dashmate
& dashmate update, Dashmate gives following error  :
Error: (HTTP code 404) unexpected - manifest for dashpay/dashmate-helper:0.24.20 not found: manifest unknown: manifest unknown
Same error when i then try to issue dashmate start.
Expected Behavior
Dashmate  should just show in dashmate update that it updated to Dashmate v0.24.20 successfully
Current Behavior
Throws error and won't allow dashmate start
Current config.json shows at very start
{
"configFormatVersion": "0.24.20",
"defaultConfigName": "mainnet",
"defaultGroupName": null,
"configs": {
"base": {
"description": "base config for use as template",
"group": null,
"docker": {
"network": {
"subnet": "<IP_ADDRESS>/0",
"bindIp": "<IP_ADDRESS>"
},
Possible Solution
If Dashmate itself is also updated through Docker, then maybe the solution is uploading v0.24.20 tag here --> https://hub.docker.com/r/dashpay/dashmate-helper/tags ? Latest version there seems to be still v0.24.19
See also forum : https://www.dash.org/forum/index.php?threads/dashmate-discussion.53951/#post-235667
Steps to Reproduce (for bugs)

While on Dashmate v0.24.19 issue dashmate stop
Issue npm update -g dashmate
Issue dashmate update

I tried installing dashmate again through command npm install -g dashmate and then update it again with command npm update -g dashmate --> same error & same problem (will not allow dashmate start).
I tried installing dashmate again through command npm install -g dashmate, without issuing npm update -g dashmate (hoping that would get me to an older Dashmate version) --> same error & same problem (will not allow dashmate start).
This needs urgent attention, as i can not start dashmate right now due to this error.

Dashmate v0.24.21 is released that fixes this error


PyTorch Smooth-Quant 3x API Implementation

Type of Change
Migration smooth-quant implementation to 3x API.
Description
Expected Behavior & Potential Risk
ut pass
How has this PR been tested?
Dependency Change?

resolved in https://github.com/intel/neural-compressor/pull/1568


[REVIEW] xerexcoded

GitHub Profile Link
https://github.com/xerexcoded

Hey, @xerexcoded! Thanks for sharing your profile with us! 😄
I have made a pull request for some minor
improvements in the README.md file. 🙂

GitHub Profile Link
https://github.com/xerexcoded

hey @xerexcoded ! Thanks for sharing your GitHub profile with us, I liked it :)
but you can also make use of  while raising issues or PR to make your link looks more attractive and understandable.

Looks great, some thoughts

Suggest having a profile picture of you
Too many titles with no content

Review live stream https://www.youtube.com/watch?v=NxxJ_5nyG9E


The article refers to an external video that is unavailable

The article links to a video that is not available (made private):
For example, the demo at the 37-minute mark of this presentation shows [various mixes achieving 46 percent, 54 percent, and 65 percent efficiency](https://www.youtube.com/watch?v=-LK2ViRGbWs&t=36m55s) with 12 servers.
Generally, it doesn't seem to be a good idea to use external sources in documentation. Furthermore, referring to a different type of media (a video from a text documentation) may be undesirable, i.e. for accessibility reasons.

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

ID: 6daf71fc-aa1a-9e6e-c939-23edeceec1f2
Version Independent ID: 8a69b399-3682-6767-4794-3cb81fcae479
Content: Fault tolerance and storage efficiency on Azure Stack HCI and Windows Server clusters - Azure Stack HCI
Content Source: azure-stack/hci/concepts/fault-tolerance.md
Service: azure-stack
Sub-service: azure-stack-hci
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

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

@JasonGerend
Can you please check and add your comments on this doc update request as applicable.
@VitalKoshalew
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

@VitalKoshalew Checking the article, this seems to be resolved now. #please-close


Revive docker.sh

I revived the file which was deleted in https://github.com/fluent/fluent-plugin-splunk/commit/07ad63f555bf1c77594334d36aa3fb554683079c and update README to catch up a present environment.
For now, I skipped to revived the CI file since it needs to build docker images and building them takes too much time.
I hope this change will help with https://github.com/fluent/fluent-plugin-splunk/pull/20
@repeatedly Can you review this?

Thanks!


[DOCS] Correct grammar on FrontendSetup.md

Description
In the FrontendSetup.md, the second item under tech overview is "We using CSS (Bootstrap v5) for the styling" instead of "We are using CSS (Bootstrap v5) for the styling". There is a missing "are"
Screenshots
No response
🥦 Browser
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)
[ ] I am a GSSoC23 contributor (blank for no).

can i do it?


Make the "auto-scaling" time formats use 24-hour hours

I'm not sure if it's worth making this an option; but if it's not then 24-hours really are more universally useful than 12-hours + am/pm.  :-)

As much as I prefer the 24-hour format, I feel it's best to stick with U.S. convention. If you're interested, a customizable multiscale time format that allows you to override formats for different intervals would be great.


Analysis server: NoSuchMethodError: The getter 'units' was called on null.

I pulled master from Flutter a few moments ago and opened the Stocks example app and got this crash.
Versions

Dart SDK 2.0.0-edge.0d5cf900b021bf5c9fa593ffa12b15bcd1cc5fe0
Flutter SDK 0.2.5-pre.46
Visual Studio Code 1.21.1
Dart Code 2.11.0

Analyzer Info
The analyzer was launched using the arguments:
/Users/danny/Dev/Google/flutter/bin/cache/dart-sdk/bin/snapshots/analysis_server.dart.snapshot
--client-id=Dart-Code.dart-code
--client-version=2.11.0
--preview-dart-2

Exception
Analysis failed: /Users/danny/Dev/Google/flutter/examples/stocks/test/locale_test.dart context: exception_20180327_192741_169
NoSuchMethodError: The getter 'units' was called on null.
Receiver: null
Tried calling: units
#0      Object.noSuchMethod (dart:core-patch/dart:core/object_patch.dart:46)
#1      LibraryElementInDependency._makeUnitElement (package:analyzer/src/summary/link.dart:4106)
#2      LibraryElementForLink.units (package:analyzer/src/summary/link.dart:3911)
#3      LibraryElementForLink.getContainedName.<anonymous closure> (package:analyzer/src/summary/link.dart:3950)
#4      _HashVMBase&MapMixin&&_LinkedHashMapMixin.putIfAbsent (dart:collection-patch/dart:collection/compact_hash.dart:277)
#5      LibraryElementForLink.getContainedName (package:analyzer/src/summary/link.dart:3949)
#6      TypeProviderForLink._buildInterfaceType (package:analyzer/src/summary/link.dart:5528)
#7      TypeProviderForLink.objectType (package:analyzer/src/summary/link.dart:5497)
#8      ClassElementForLink_Class._computeInterfaceType (package:analyzer/src/summary/link.dart:820)
#9      ClassElementForLink_Class.supertype (package:analyzer/src/summary/link.dart:734)
#10     InstanceMemberInferrer._inferClass (package:analyzer/src/task/strong_mode.dart:310)
#11     InstanceMemberInferrer.inferCompilationUnit (package:analyzer/src/task/strong_mode.dart:87)
#12     CompilationUnitElementInBuildUnit.link (package:analyzer/src/summary/link.dart:1433)
#13     LibraryElementInBuildUnit.link (package:analyzer/src/summary/link.dart:4063)
#14     LibraryCycleNode.link (package:analyzer/src/summary/link.dart:3799)
#15     LibraryCycleDependencyWalker.evaluate (package:analyzer/src/summary/link.dart:3721)
#16     DependencyWalker.walk.strongConnect (package:front_end/src/dependency_walker.dart:149)
#17     DependencyWalker.walk.strongConnect (package:front_end/src/dependency_walker.dart:115)
#18     DependencyWalker.walk.strongConnect (package:front_end/src/dependency_walker.dart:115)
#19     DependencyWalker.walk.strongConnect (package:front_end/src/dependency_walker.dart:115)
#20     DependencyWalker.walk.strongConnect (package:front_end/src/dependency_walker.dart:115)
#21     DependencyWalker.walk (package:front_end/src/dependency_walker.dart:168)
#22     LibraryCycleForLink.ensureLinked (package:analyzer/src/summary/link.dart:3764)
#23     Linker.link (package:analyzer/src/summary/link.dart:4288)
#24     relink (package:analyzer/src/summary/link.dart:132)
#25     link (package:analyzer/src/summary/link.dart:113)
#26     new LibraryContext.forSingleLibrary.<anonymous closure>.<anonymous closure> (package:analyzer/src/dart/analysis/library_context.dart:119)
#27     PerformanceLog.run (package:front_end/src/base/performance_logger.dart:34)
#28     new LibraryContext.forSingleLibrary.<anonymous closure> (package:analyzer/src/dart/analysis/library_context.dart:118)
#29     PerformanceLog.run (package:front_end/src/base/performance_logger.dart:34)
#30     new LibraryContext.forSingleLibrary (package:analyzer/src/dart/analysis/library_context.dart:56)
#31     AnalysisDriver._createLibraryContext (package:analyzer/src/dart/analysis/driver.dart:1375)
<asynchronous suspension>
#32     AnalysisDriver._computeAnalysisResult.<anonymous closure> (package:analyzer/src/dart/analysis/driver.dart:1204)
<asynchronous suspension>
#33     PerformanceLog.runAsync (package:front_end/src/base/performance_logger.dart:52)
<asynchronous suspension>
#34     AnalysisDriver._computeAnalysisResult (package:analyzer/src/dart/analysis/driver.dart:1181)
<asynchronous suspension>
#35     AnalysisDriver.performWork (package:analyzer/src/dart/analysis/driver.dart:1007)
<asynchronous suspension>
#36     AnalysisDriverScheduler._run (package:analyzer/src/dart/analysis/driver.dart:1896)
<asynchronous suspension>
#37     AnalysisDriverScheduler.start (package:analyzer/src/dart/analysis/driver.dart:1839)
#38     new AnalysisServer (package:analysis_server/src/analysis_server.dart:395)
#39     SocketServer.createAnalysisServer (package:analysis_server/src/socket_server.dart:79)
#40     StdioAnalysisServer.serveStdio (package:analysis_server/src/server/stdio_server.dart:37)
#41     Driver.start.<anonymous closure> (package:analysis_server/src/server/driver.dart:444)
#42     _rootRun (dart:async/zone.dart:1126)
#43     _CustomZone.run (dart:async/zone.dart:1023)
#44     runZoned (dart:async/zone.dart:1501)
#45     Driver._captureExceptions (package:analysis_server/src/server/driver.dart:484)
#46     Driver.start (package:analysis_server/src/server/driver.dart:443)
#47     main (file:///b/build/slave/Mac_Engine/build/src/third_party/dart/pkg/analysis_server/bin/server.dart:12)
#48     _startIsolate.<anonymous closure> (dart:isolate-patch/dart:isolate/isolate_patch.dart:277)
#49     _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:165)

Diagnostics requested after the error occurred are:
[
    {
        "name": "/Users/danny/Dev/Google/flutter/examples/stocks",
        "explicitFileCount": 15,
        "implicitFileCount": 829,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    }
]

@scheglov I seem to remember seeing a fix for this go by. Do you remember?

Hm... No, I don' remember fixing this.
@DanTup Could you please send me this exception_20180327_192741_169 from the analysis cache directory?

Sent via email!

Oh, we were not able to find TypeProviderForLink.objectType.
No SDK found, or something like this maybe?
I will try to test what happens when SDK libraries are not available.

Hmmm, I'm not sure what this means. I ran the analyzer from the SDK using the VM that was in it, so it should all be there :/

I can reproduce this issue in Analysis Driver tests:
    provider.getFile("$sdkRoot/lib/core/core.dart").delete();
    addTestFile('class C {}');

Don't know yet how this happens.

This most probably a race condition of some kind, or a temporary state.
I will add validation into Analysis Driver, we cannot analyze anything if dart:core and dart:async are not available. We should fail fast with a compilation error, instead of throwing an exception internally.

https://dart-review.googlesource.com/c/sdk/+/48703


Function for genome-set creation was added in NarrativeManager.

Just noticed this request- was this meant to pulled into narrative-dev or develop?  Is there any code that calls this new method?

Just checking up on this - does it need to go to the search branch or develop?

I'm not sure it's still necessary. I did for @mlhenderson actually. Matt?

Right, this was something I asked Roman to work on that didn't make it into
the Feb deploy.  I think this is useful to have generally, but Bill and I
should discuss this before merging to develop.
On Thu, Apr 30, 2015 at 1:53 PM, Roman Sutormin<EMAIL_ADDRESS>wrote:

I'm not sure it's still necessary. I did for @mlhenderson
https://github.com/mlhenderson actually. Matt?
—
Reply to this email directly or view it on GitHub
https://github.com/kbase/ui-common/pull/111#issuecomment-97963735.

I think (and I remember Mike thought so) it would be better to put it somewhere else. I just didn't find better place when I did this PR (it was Friday evening before code freeze? or close to it).

I think it's not necessary anymore. So I'll close this PR if there is nobody asking to not do it in an hour.


Make cacheTimeout == 0 equal to noCache being set to True

Current coverage is 65.93% (diff: 40.00%)

Merging #1680 into master will decrease coverage by 0.01%

@@             master      #1680   diff @@
==========================================
  Files            54         54
  Lines          6106       6109     +3
  Methods           0          0
  Messages          0          0
  Branches       1205       1206     +1
==========================================
+ Hits           4027       4028     +1
- Misses         1872       1873     +1
- Partials        207        208     +1

Powered by Codecov. Last update 2cc2a2a...d3293c1

Close/open to retrigger tests. Sometimes they're sporadically fails...

Just fyi, we (I?) can retrigger the tests on Travis anytime.

Ah, true, just find that. Thanks, @obfuscurity !

Looked through the impact on useCache, seems sane. 👍


{Core} Polish the help messages for Az login -p and Az ad --filter

https://github.com/Azure/azure-cli/issues/12332
https://github.com/Azure/azure-cli/issues/11985
History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)
[Component Name 1] (BREAKING CHANGE:) (az command:) make some customer-facing change.
[Component Name 2] (BREAKING CHANGE:) (az command:) make some customer-facing change.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

add to S167

Shit it!

Ship it!


Update git clone rmw_fastrtps command.

If you do not add the branch option to the git clone command, "Cannot locate Error" occurs when performing the command "rosdep install --from src -i"

@Mergifyio backport rolling foxy


Bug. AssetManager doesn't decrement the variable toLoad on asset load failed.

If I load a bitmap font that doesn't exist, the function handleTaskError from AssetsManager is called but the variable toLoad from AssetsManager is never decremented.
Also because cleanup occurred, unload will not fix this.
Example code:
assetsManager.load("ExampleFont.fnt", BitmapFont.class);
try {
    assetsManager.update(100);
}catch(GdxRuntimeException e) {
    // Exception is caught here but assetsManager.toLoad will remain 1 and assetsManager.loaded will remain 0.
}

https://github.com/libgdx/libgdx/wiki/More-Info


Support connecting to a local weaviate instance

fixes #235

@hsm207 Hi, will do today, thanks!

BTW, I didn't get any notification. Are you able to click the Review button and select me or not?

@pseudotensor no, I don't have that gear icon to add a reviewer:


[New Explainer Request] Home screen widgets

One of the feature that native apps have, but PWAs haven't, is home screen widgets.
E.g. it would be really nice to have a https://weather-pwa-sample.firebaseapp.com/final/ PWA as Android or Windows home screen widget.

This is in discussion. I commented on the W3C thread with some links for you.


Make URL fields clickable links

Let's create a functionality where we can mark certain fields as 'url_fields', and make those fields clickable links in the fronend. ElasticSearch does not have a native url_mapping, instead we store these as keyword fields usually. Tijmen and I think the easiest solution would be to add a parameter in the frontend for url fields.

Let's create a functionality where we can mark certain fields as 'url_fields'

Did you try display_type = 'url'?


⚠ PrivateHD has degraded performance

In 29cab53, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 17585 ms

Resolved: PrivateHD performance has improved in 912f541.


data-bs-theme="auto" does not work in 5.3.0-alpha1

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
I have been trying out the latest version of Bootstrap (5.3.0-alpha1) and in particularly playing with dark mode. Unfortunately, I have not been able to get data-bs-theme="auto" to work at all. It just always shows light mode.
I have taken the HTML code directly from the Getting Started documentation (https://getbootstrap.com/docs/5.3/getting-started/introduction/) and simply added data-bs-theme="auto" to the HTML tag:
<!doctype html>

    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <title>Bootstrap demo</title>
    <link<EMAIL_ADDRESS>rel="stylesheet" integrity="sha384-GLhlTQ8iRABdZLl6O3oVMWSktQOp6b7In1Zl3/Jr59b6EGGoI1aFkw7cmDA6j6gD" crossorigin="anonymous">

Hello, world!

I feel like I'm missing something though since it doesn't work. I have searched the docs for quite a while to try to find any information about the auto mode, but there doesn't seem to be anything other than that it exists. Of course, I've also found the recommended JavaScript for building a color mode toggle (https://getbootstrap.com/docs/5.3/customize/color-modes/#javascript), but that doesn't have any information about the auto setting.
Is this just missing documentation or is it actually a bug? I realize this version is still in alpha, which is why I thought I would report it.
Reduced test cases
CodePen only allows HTML within the  tag, so I can't post the example there.
What operating system(s) are you seeing the problem on?
Windows, macOS
What browser(s) are you seeing the problem on?
Chrome, Safari, Firefox
What version of Bootstrap are you using?
v5.3.0-alpha1

I think you have to use the javascript in order for the auto value to do anything.

Yes, you need to include the JS mentioned at https://getbootstrap.com/docs/5.3/customize/color-modes/#javascript. I've pushed an updated example to https://github.com/twbs/examples/tree/main/color-modes to show how this can be done.

Ok, perfect. I just wasn't sure whether it was a bug or if I just wasn't understanding the documentation correctly.
It might be nice though to have a quick blurb specifically about how to use auto since it appears in examples, but there isn't anything specific about the fact that you need to implement the logic for it. It's implied in the JavaScript example, but when you aren't planning on building a toggle switch and just want to rely on the browser's settings, you might not necessarily read through the example on how to build a toggle switch, as was in my case...


Adjust launcher pom as it is not built

Coverage remained the same at 33.686% when pulling 245fc9d9e4640ae86ebf7dd8a9e13b20b35cab09 on yqwang/dev2 into e7452afc715841b1d768affe16a71e8975a6c6b6 on master.


feat(core): notification hardening

Description
Refactor the notifications flow
Checklist before requesting a review
Issue ticket number and link

[X] This PR has a valid ticket number or issue: link

Testing & Validation

[X] This PR has been tested/validated in IOS, Android and browser.
[X] The code has been tested locally with test coverage match expectations.
[X] Added new Unit/Component testing (if relevant).

Security

[X] No secrets are being committed (i.e. credentials, PII)
[X] This PR does not have any significant security implications

Code Review

[X] There is no unused functionality or blocks of commented out code (otherwise, please explain below)
[X] In addition to this PR, all relevant documentation (e.g. Confluence) and architecture diagrams (e.g. Miro) were updated

rest of the notification stuff LGTM @Sotatek-TungNguyen2a - let me know when you've done all of your testing for KERIA going offline etc - this needs to be as solid as possible


[Snyk] Upgrade io.grpc:grpc-netty-shaded from 1.53.0 to 1.55.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade io.grpc:grpc-netty-shaded from 1.53.0 to 1.55.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released 24 days ago, on 2023-05-08.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Already fixed


Sample did not show camera information

Old output:
Python:       3.7.4
zivid-python: <IP_ADDRESS>.8.1
Zivid SDK:    1.8.1+6967bc1b-1

New output:
Python:       3.7.4
zivid-python: <IP_ADDRESS>.8.1
Zivid SDK:    1.8.1+6967bc1b-1
Camera Info:  { Camera info: { Model Name: Zivid One Plus M, Serial Number: 19200CB2, Hardware Revision: { Major: 3, Minor: 2 }, Firmware Version: 1.6.7, USB Path: na, Internal camera id: 0510737 } }

LGTM.
Should we consider upgrading this so that it can be easily imported and used in a other sample scripts?

In what way?

LGTM.
Should we consider upgrading this so that it can be easily imported and used in a other sample scripts?

In what way?

So that this would be possible:
from print_version_info import print_zivid_info
print_zivid_info()


Standard: Overview Blade identifier Unable to scroll Up/Down in Get started tab.

Describe the Bug with repro steps
1.Go to overview page of standard logic app.
2.Click on Get started tab
Actual: Unable to scroll Up/Down in Get started tab.
Expected: Should be able to scroll Up/Down in Get started tab.as expected.
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
No
Workflow JSON
No response
Screenshots or Videos
https://github.com/Azure/LogicAppsUX/assets/113517384/70a8a536-5169-44b2-930b-3e875ddf5b52

Browser
Edge
Additional context
Environmental Details:
URL: https://aka.ms/emastagiLong-flowstip1
Version: 2.30920.1.1
AB#25231133

fixed


Mavlink Default  Streams sent to QGC for REAL TIME PLOTTING  Not working

There are some default streams sent in "normal mode"
https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_main.cpp#L1638.
but all of them are not available in QGC. I changed mode and still i am not able to get the other streams in QGC .
i want to stream "ATT_POS_MOCAP" and stop streaming  VFR_HUD
where should i make changes in
https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_main.cpp
i tried extras.txt and rc.usb method but nothing is happening ......even i removed all steamings from rc.usb  but i am still getting the default streams.

Outdated.


[event-request]: 'OnAfterInvPostBufferPrepareXXX' on Table 49

Would be nice to have OnAfterInvPostBufferPrepareSales, OnAfterInvPostBufferPreparePurchase, and OnAfterInvPostBufferPrepareService that is called at the end of each of the respective functions in Table 49.

These events already existed. Please try bcsandbox-master Docker image


resume the training

when i resumed the trainval_net.py,with the args
args.resume=True
args.checksession=1
args.checkepoch=24
args.checkpoint=8958
but met the error below:
Expected object of type torch.FloatTensor but found type torch.cuda.FloatTensor for
argument #4'other'
my pytorch version==0.4.0  and python==2.7
i have change the pytorch version to 0.3.0 and 0.3.1,but it doesn't work.
Does anyone know how to solve it?

I think the model was trained using gpu but you are not using the gpu to continue training. Have you tried using --cuda option ?

i have set the option args.cuda=True,but it still not works.here is my option:
args.cuda=True
args.gpu_id=1
args.max_epochs=100
args.net='vgg16'
args.resume=True
args.checksession=1
args.checkepoch=24
args.checkpoint=8958
@cancam

How about trying mGPUs option? @vickersmith

i tried,it  still doesn't work.Also,by the way,the pytorch version==0.4.0 doesn't support muitiple gpus training by mGPU options. i tried and other issues in this github also showed that multiple gpus can not be run in the code.

Can confirm I'm having the same issue. Trained the model with
python trainval_net.py --net res101 --bs 8 --nw 1  --epochs 100 --cuda --dataset pascal_voc

which produces a file ./models/faster_rcnn_1_100_1251.pth
I then run
python trainval_net.py --net res101 --bs 8 --nw 1  --epochs 10 --cuda --dataset pascal_voc --r 1 --checksession 1 --checkepoch 100 --checkpoint 1251

and get the error
RuntimeError: Expected object of type torch.FloatTensor but found type torch.cuda.FloatTensor for argument #4 'other'

@vickersmith
did you try adding this in your train script?
import torch._utils
try:
    torch._utils._rebuild_tensor_v2
except AttributeError:
    def _rebuild_tensor_v2(storage, storage_offset, size, stride, requires_grad, backward_hooks):
        tensor = torch._utils._rebuild_tensor(storage, storage_offset, size, stride)
        tensor.requires_grad = requires_grad
        tensor._backward_hooks = backward_hooks
        return tensor
    torch._utils._rebuild_tensor_v2 = _rebuild_tensor_v2

I met the same problem,anybody can help me?

As suggested by @ssli23  and many others,  I have moved these two line above.


feat(pipelines): Add cargo build for rust packages

Produces and installs an auditable rust binary with an embedded dependency tree in its own dedicated linker section in JSON format. This simplifies the packaging processes for rust packages and ensures that all rust binaries we build are able to be audited for bugs/vulnerabilities in crates fetched during the build process
Melange Pull Request Template

Functional Changes

[x] This change can build all of Wolfi without errors (describe results in notes)

Notes:
SCA Changes

[x] Examining several representative APKs show no regression / the desired effect (details in notes)

Notes:
Linter

[ ] The new check is clean across Wolfi
[ ] The new check is opt-in or a warning

Notes:

related: https://github.com/wolfi-dev/os/pull/14537

I was about to do it :)


python310Packages.aioshelly: 1.0.10 -> 1.0.11

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.aioshelly is: "Python library to control Shelly"
meta.homepage for python310Packages.aioshelly is: "https://github.com/home-assistant-libs/aioshelly"
meta.changelog for python310Packages.aioshelly is: "https://github.com/home-assistant-libs/aioshelly/releases/tag/1.0.11"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.0.11 with grep in /nix/store/2qh47qfj93yhvm0nrmv28ydah903pzs2-python3.10-aioshelly-1.0.11

found 1.0.11 in filename of file in /nix/store/2qh47qfj93yhvm0nrmv28ydah903pzs2-python3.10-aioshelly-1.0.11

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.shelly
python310Packages.aioshelly
python39Packages.aioshelly

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2qh47qfj93yhvm0nrmv28ydah903pzs2-python3.10-aioshelly-1.0.11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.aioshelly https://github.com/r-ryantm/nixpkgs/archive/bb7a7dcfc49f0362cd39425e59e69f5fb6e320b8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2qh47qfj93yhvm0nrmv28ydah903pzs2-python3.10-aioshelly-1.0.11
ls -la /nix/store/2qh47qfj93yhvm0nrmv28ydah903pzs2-python3.10-aioshelly-1.0.11/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.shelly
python310Packages.aioshelly
python39Packages.aioshelly

Maintainer pings
cc @fabaff for testing.

Package is already updated on unstable


suggestion on wither skeletons

CAN WE HAVE A CONFIG ON WITHERS?
so everyone can change its difficulty by their desire?

Please explain. I do not modify Withers at all within the addon. I do make a wither skeleton golem multiblock that can be completely disabled though.

I want that ur wither golem be configure able cause every server economy is
different so people will need sth like this but not the way u imagined im
totally fine with this but a bit of configuration is needed for these
situations
On Mon, Nov 15, 2021, 3:20 AM ProfElements @.***> wrote:

Please explain. I do not modify Withers at all within the addon. I do make
a wither skeleton golem multiblock that can be completely disabled though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ProfElements/DynaTech/issues/124#issuecomment-968392765,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASHNDQAGHLLDVTNMODG5WRTUMBDLLANCNFSM5H7KIAMQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Learning Tracks

The exercises provided in this course can be used in different numbers/combinations to emphasise different topics.
e.g:

Ansible
CI
CD
CI/CD
TDD

Participants need guidance as to which exercises they should complete in order to achieve their learning goals. This is where Tracks come in.
Participants could be given a command as part of the courseware that they receive that against their fork:

creates a project
creates issues for each of the exercises they should complete
assigns those issues in the right order to the project.

This will provide them prioritised backlog for them to work through. They can then raise pull request against each ticket that they complete so that someone can review how they have done.

Reviewed and merged by @jimconner


Added the new section Duplicate_Question nlp

Description
classify whether the given questions are duplicates or not.
Algorithm - Random Forest and XGBoost
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

(Add x in the [] to mark as completed.)
Related Issues or Pull Requests
#70

I had completed the issues assigned to me
please kindly check and merge it with the main branch
@khusheekapoor


Load balancer stuck in "initializing"

Rancher Version: 1.1.0-dev3
Docker Version: 11.2.0
OS and where are the hosts located? (cloud, bare metal, etc): Ubuntu 14.04 on DigitalOcean.
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB): Single node, internal DB.
Environment Type: (Cattle/Kubernetes/Swarm/Mesos): Cattle
Started load balancer through UI. It's stuck saying "Initializing". Log from rancher/agent-instance:v0.8.1 container:
6/1/2016 11:48:44 PMINFO: ROOT -> ./etc/monit/
6/1/2016 11:48:44 PMINFO: ROOT -> ./etc/monit/monitrc
6/1/2016 11:48:44 PMINFO: ROOT -> ./etc/monit/conf.d/
6/1/2016 11:48:44 PMINFO: ROOT -> ./etc/monit/conf.d/logrotate
6/1/2016 11:48:44 PMINFO: Sending monit applied 1-c4113ae48035df162ff89a5d37af1545f002ee54e044535e42395bda7a29a953
6/1/2016 11:48:44 PMINFO: Getting haproxy
6/1/2016 11:48:45 PMINFO: Updating haproxy
6/1/2016 11:48:45 PMINFO: Downloading http://[...]:8080/v1//configcontent//haproxy current=
6/1/2016 11:48:45 PMINFO: Running /var/lib/cattle/download/haproxy/haproxy-2-6e0a8e0f43f312d19403952224ef2fb86918597c1f12ed0caa1499b8a6df968b/apply.sh
6/1/2016 11:48:45 PMINFO: ROOT -> ./
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/default/
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/default/haproxy
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/monit/
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/monit/conf.d/
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/monit/conf.d/haproxy
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/haproxy/
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/haproxy/certs/
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/haproxy/certs/certs.pem
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/haproxy/certs/default.pem
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/haproxy/haproxy.cfg
6/1/2016 11:48:45 PMINFO: Sending haproxy applied 2-6e0a8e0f43f312d19403952224ef2fb86918597c1f12ed0caa1499b8a6df968b
6/1/2016 11:48:45 PMINFO: HOME -> ./
6/1/2016 11:48:45 PMINFO: HOME -> ./etc/
6/1/2016 11:48:45 PMINFO: HOME -> ./etc/cattle/
6/1/2016 11:48:45 PMINFO: HOME -> ./etc/cattle/startup-env
6/1/2016 11:48:45 PMINFO: ROOT -> ./
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/init.d/
6/1/2016 11:48:45 PMINFO: ROOT -> ./etc/init.d/agent-instance-startup
6/1/2016 11:48:45 PMINFO: Sending agent-instance-startup applied 1-990795b955f78bee90c4b7ed42d55a16664cf3f6d716e68ffcc2198803411120
6/1/2016 11:48:45 PMmonit: generated unique Monit id 7262161aa76210e96bdeb824d45a0848 and stored to '/var/lib/monit/id'
6/1/2016 11:48:45 PMStarting monit daemon with http interface at [localhost:2812]

Log from rancher/agent:v1.0.1:
2016-06-02T03:48:43.744286372Z time="2016-06-02T03:48:43Z" level="info" msg="Assigning IP [<IP_ADDRESS>/16], ContainerId [c15dd300778b4608f4ab9bd67de34423199811d257161948dd142a75d0419322], Pid [25395]"
2016-06-02T03:48:43.759747200Z time="2016-06-02T03:48:43Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"c15dd300778b4608f4ab9bd67de34423199811d257161948dd142a75d0419322\", From:\"-simulated-\", Time:0}"

It has clearly started HAProxy:
root     27849  0.0  0.3 126988  6164 ?        Sl   23:54   0:00  |   \_ docker-containerd-shim c15dd300778b4608f4ab9bd67de34423199811d257161948dd142a75d0419322 /var/run/docker/libcontainerd/c15dd300778b4608f4ab9bd67de34423199811d25716194
root     27862  0.0  0.0   4924   804 pts/2    Ss+  23:54   0:00  |       \_ init
root     28449  0.0  0.1 104328  2188 ?        Ssl  23:54   0:00  |           \_ /usr/bin/monit -Ic /etc/monit/monitrc
landsca+ 28458  0.0  0.0  35192  1100 ?        Ss   23:54   0:00  |           \_ /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
ro

Server log doesn't say anything at all.

Some problem here.
Rancher v1.0.2, it happen only for a host with ubuntu 16.04 and docker 1.11.2, no problem with other two hosts with docker 1.11.1.
All Load Balancers on this host are working but it stay in "Initializing" state in UI.
In API the state of related services is "active" and the state of containers is "running".

Rancher currently only supports Docker 1.10.3 (all the docs point to that version right now), but that shouldn't be affecting your current issue.
When a load balancer is stuck in initializing, it typically means that the cross host communication isn't working as a health check is failing. Have you tried exec-ing into one of the network agents and pinging the network agent IP (10.42.x.x.) on another host to see if they can communicate?

@deniseschannon I tried to ping from the network agent of that host all others 3 network agents of other hosts and no problem, ping works as expected.
Load Balancers on that host works fine, i don't undestand why in UI they stay in "initializing" and in API the state is "active" instead.

Same issue with all my hosts with the ranchre server latest and v1.1.0-dev4.
Back to stable the local host (host AND rancher server container) still have this problem, but other hosts working again...

You shouldn't use rancher/server:stable... It doesn't work. Deleted all services and hosts, redeployed hosts / services with rancher:server:latest and all works fine again...?!

+1 - having the same issue. Using Rancher v1.1.0-dev4 and two hosts running on RHEL7 and boot2docker. docker version: 1.11.2

@atombender Were you able to confirm that your cross host networking is working?
@Leen15 Did your LB ever get out of initializing? It sounds like there was a sync issue between the UI and the API, but not sure if a refresh fixed it.
@pwFoo @alxndr13 Can you check your cross host networking as LBs will be stuck in initializing when health checks fail.

@deniseschannon No, I gave up on Rancher and migrated to Kubernetes, sorry.

@deniseschannon Yes, i updated to version 1.1.1, no problem for now with LBs ! ;)

Updated to Rancher Server 1.1.1-rc1 worked fine, Updated RancherOS 0.4.5 to 0.5 AND Rancher Server to final 1.1.1 and LB stucks again at the same host running LB and Rancher Server.
Hosts connected with openvpn tunnel to the rancher servers host. Connection is fine as I can see / have tested it.

@pwFoo How many hosts do you have? So the LB is on the host running rancher server and is stuck in initializing?

Hi @deniseschannon
It's a small setup with 2 (temp. 3) hosts. First host is running the rancher server too. That's the host with the LB stucks in initializing state.

@pwfoo Do you still have this issue? The load balancer will be stuck in initializing when the cross host communication is broken as the health checks fail. Please reopen if you still have issues.

problem still .
host: 1  mac , and 3  dockermachine .
rancher: version 1.1.3  with cattle
follow this guide
http://docs.rancher.com/rancher/v1.0/en/quick-start-guide/
load balance  initializing  forever ...
rancher/server logs
2016-09-20 23:49:38,981 ERROR [:] [] [] [] [cutorService-39] [o.a.c.m.context.NoExceptionRunnable ] Uncaught exception org.jooq.exception.DataChangedException: Database record has been changed
at org.jooq.impl.UpdatableRecordImpl.checkIfChanged(UpdatableRecordImpl.java:550) ~[jooq-3.3.0.jar:na]
at org.jooq.impl.UpdatableRecordImpl.storeUpdate0(UpdatableRecordImpl.java:291) ~[jooq-3.3.0.jar:na]
at org.jooq.impl.UpdatableRecordImpl.access$200(UpdatableRecordImpl.java:90) ~[jooq-3.3.0.jar:na]
at org.jooq.impl.UpdatableRecordImpl$3.operate(UpdatableRecordImpl.java:260) ~[jooq-3.3.0.jar:na]
at org.jooq.impl.RecordDelegate.operate(RecordDelegate.java:123) ~[jooq-3.3.0.jar:na]
at org.jooq.impl.UpdatableRecordImpl.storeUpdate(UpdatableRecordImpl.java:255) ~[jooq-3.3.0.jar:na]
at org.jooq.impl.UpdatableRecordImpl.update(UpdatableRecordImpl.java:149) ~[jooq-3.3.0.jar:na]
at io.cattle.platform.object.impl.JooqObjectManager.persistRecord(JooqObjectManager.java:223) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.object.impl.JooqObjectManager.setFieldsInternal(JooqObjectManager.java:130) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.object.impl.JooqObjectManager$3.execute(JooqObjectManager.java:118) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.idempotent.Idempotent.change(Idempotent.java:88) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.object.impl.JooqObjectManager.setFields(JooqObjectManager.java:115) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.object.impl.JooqObjectManager.setFields(JooqObjectManager.java:110) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.object.impl.AbstractObjectManager.setFields(AbstractObjectManager.java:135) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.process.common.generic.GenericResourceProcessState.setState(GenericResourceProcessState.java:85) ~[cattle-iaas-logic-common-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.AbstractStatesBasedProcessState.setTransitioning(AbstractStatesBasedProcessState.java:27) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.setTransitioning(DefaultProcessInstanceImpl.java:520) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runWithProcessLock(DefaultProcessInstanceImpl.java:291) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$2.doWithLockNoResult(DefaultProcessInstanceImpl.java:245) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:7) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:3) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.acquireLockAndRun(DefaultProcessInstanceImpl.java:242) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runDelegateLoop(DefaultProcessInstanceImpl.java:184) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.executeWithProcessInstanceLock(DefaultProcessInstanceImpl.java:157) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$1.doWithLock(DefaultProcessInstanceImpl.java:107) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$1.doWithLock(DefaultProcessInstanceImpl.java:104) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.execute(DefaultProcessInstanceImpl.java:104) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.engine.manager.impl.DefaultProcessManager.scheduleProcessInstance(DefaultProcessManager.java:60) ~[cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.object.process.impl.DefaultObjectProcessManager.scheduleProcessInstance(DefaultObjectProcessManager.java:47) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.object.process.impl.DefaultObjectProcessManager.scheduleStandardProcess(DefaultObjectProcessManager.java:40) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.object.process.impl.DefaultObjectProcessManager.scheduleStandardProcess(DefaultObjectProcessManager.java:34) ~[cattle-framework-object-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.activateServices(DeploymentManagerImpl.java:289) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.reconcileDeployment(DeploymentManagerImpl.java:134) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl$1.doWithLock(DeploymentManagerImpl.java:122) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl$1.doWithLock(DeploymentManagerImpl.java:116) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.activate(DeploymentManagerImpl.java:116) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.activate(DeploymentManagerImpl.java:99) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl$4.run(DeploymentManagerImpl.java:418) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.reconcileForClient(DeploymentManagerImpl.java:429) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.serviceUpdate(DeploymentManagerImpl.java:413) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_101]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_101]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_101]
at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_101]
at io.cattle.platform.eventing.annotation.MethodInvokingListener$1.doWithLockNoResult(MethodInvokingListener.java:76) ~[cattle-framework-eventing-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:7) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:3) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.eventing.annotation.MethodInvokingListener.onEvent(MethodInvokingListener.java:72) ~[cattle-framework-eventing-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.eventing.impl.AbstractThreadPoolingEventService$2.doRun(AbstractThreadPoolingEventService.java:135) ~[cattle-framework-eventing-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.NoExceptionRunnable.runInContext(NoExceptionRunnable.java:15) ~[cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:108) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_101]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_101]

@zk4 Your cross host communication isn't working. The error that you provided is benign.
Have you looked at the FAQs for this issue?
http://docs.rancher.com/rancher/v1.2/en/faqs/troubleshooting/#cross-host-communication
Also, you can confirm whether or not cross host communication is working by exec-ing into the network agent on one host and pinging the IP (10.42.x.x) of a different network agent. Depending on which version you are running, those containers may be hidden in the UI on the hosts page and can be shown be checking "Show System" in the upper right hand corner of the hosts page.

running the docker agent with :   "docker run  -e CATTLE_AGENT_IP=replacewithyourec2privateip ................... " worked for me, however using the LB as internal does not diplay ports/IP


chore(deps): update dependency @types/recompose to v0.30.6

This PR contains the following updates:

Package
Type
Update
Change

@types/recompose
devDependencies
patch
0.30.5 -> 0.30.6

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

:tada: This PR is included in version 2.126.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat(python): standardize Python headers in the changelog

Ported over existing entry from the Ruby-yoshi changelog updater. Only modifying for header changes and removing links in the version titles.
For any headers of size 2 or 3 for version change entries, they will be standardized to header size 2.
For any headers of size 2 or 3 for change type entries, they will be standardized to header size 3.
Fixes #1389 🦕

Thank you for taking a look! I think the inconsistent header problem would definitely benefit all users including non-Googlers.
As per dropping the version header link as well, that might be less desired for some folks but with the reasons I stated in the comments I think it is alright to drop the links to those. The information is still available on the GitHub page itself if folks were interested. But, if others feel strongly against this I'll be happy to drop it and only include the inconsistent header changes for all of Python.

I definitely defer to @bcoe on changes that could affect a large number of users.

Please take a look again!

FWIW, the default changelog contents is being generated by conventional-changelog-writer. It's unclear from their docs and examples whether this is a feature or a bug.
cc @bcoe

I've been talking to @dandhlee, we're working on an upstream fix.


Reader not valid from construction

Issue summary
All objects, such as the CSV Reader class, must be valid from construction. However, it is possible to create readers for nonexistent files without incurring any indication nor exception at construction time.
League\Csv\Reader::createFromPath('nonexistent file');

object(League\Csv\Reader)

This code should throw an exception, such as FileNotFoundException.

This issue as already been reported and explained in issue #254

That issue does not match this one; it claims that either:

The wrong exception is thrown, or
A fatal error is encountered.

As this ticket reports, neither actually happens: the Reader object is created successfully with no exception or error raised.

@Bilge correct me if I'm wrong but it is the same code right ? So it should fall in the same category since this code is covered by the same test in the test suite like explained in #254


fix the language names

they appear as ISO only, which looks ugly.

I'm on it.

Commit  a300cff fixes this, as well as reporting ISO code and family name in CLDF languages and fixing the missing Glottolog mapping for Buryat.


impossible to launch app after install

When i install the module witn npm install or yarn add, when i launch my app i got the error :

Task :rnmapbox_maps:compileDebugRenderscript NO-SOURCE
Task :rnmapbox_maps:generateDebugResValues FAILED

and the build fail

@Survivor2302 hi sorry we don't provide Support. See https://github.com/rnmapbox/maps/wiki/Support For more info.


Agent import and OpenAIModel import (from pydantic_ai.models.openai) do not contain keyword arguments for store and metadata

https://platform.openai.com/docs/guides/distillation
A little while back openai added the keyword arguments for their api use called "store" and "metadata"
Store high-quality outputs of a large model:
import OpenAI from "openai";
const openai = new OpenAI();

const response = await openai.chat.completions.create({
  model: "gpt-4o",
  messages: [
    { role: "system", content: "You are a corporate IT support expert." },
    { role: "user", content: "How can I hide the dock on my Mac?"},
  ],
  store: true,
  metadata: {
    role: "manager",
    department: "accounting",
    source: "homepage"
  }
});

console.log(response.choices[0]);

This is how they can be added and these completions are then stored in the openai dashboard at a location for finetuning and monitoring in their platform.
I would like if these keywords could be added to the Agent or OpenAIModel. 'store' is a boolean by default set to false. And 'metadata' is an object which you can freely choose the arguments and the values for.
I could also create this:
metadata: {
function: "pydanticOpenAI"
folder: "introduction"
file: "RouletteWheel.py"
}

If it appears that this had already been included then I'm sorry for this issue post.

No problem, we intend to add support for customizing all models, see #71. I'll add a summary of the plan for what you want to that issue now.


feat: move segment persister to batch service

This PR will move the feature-segment-persister to the batch service. Additionally, it will add support for custom Processor parameters in the multi pubsub architecture.
Key changes

Create a new json configmap for the Processor: [1] [2]
Parse Processor json config: [1] [2] [3]
Modify the Processor interface to grant it complete control over the message channel: [1]

domainEventInformer: [1]
segmentPersister: [1]

Add worker number params for subscriber: [1] [2]

@Ubisoft-potato, can you update the persister according to these changes?
https://github.com/bucketeer-io/bucketeer/pull/898

@Ubisoft-potato, can you update the persister according to these changes? #898

Sure!

@Ubisoft-potato, can you update the persister according to these changes? #898

Updated, you can check this commit.


Incorrect transfer of SPI packets with BitOrder LSBFIRST when count is >= 4

When using void transfer(void *buf, size_t count); of the SPI Class, with BitOrder LSBFIRST, group of 4 bytes are reversed.
It seems to be here because of the optimization to handle arrays 4 bytes by 4 bytes (then byte(s) left), but it reverse the whole DWORD, not only bits of the byte.
Captures
MSBFIRST - OK

(left is using void transfer(void *buf, size_t count); right is multiple transfer(uint8_t data);)
LSBFIRST - KO

(left is using void transfer(void *buf, size_t count); right is multiples transfer(uint8_t data);)
Remarks:

Problem is not present on R3, only on R4 ;
LSBFIRST is not very common, but NXP PN532 is using it by eg ;
I'm not sure about this issue, it's too big to have been missed by real users more advanced than me - do not hesitate to close this issue if I'm totally wrong!

Did not check on the receive side (but lots of chance it can be the same)

ping @RudolphRiedel

I took a brief look at this and I have an idea what is causing it and how to fix it.

I can confirm the issue, looks like so far nobody tried to use LSBFIRST with buffer transfers.
And well, that includes me, sorry.
I fixed it here and this is how I currently have it up and running, MSBFIRST:

LSBFIRST:

Note, I am using two decoders to not switch between readings, the top is configured for LSBFIRST, the bottom for MSBFIRST.
I changed line 447 of SPI.cpp from
_spi_ctrl.p_regs->SPDCR2_b.BYSW = 1;
to:
_spi_ctrl.p_regs->SPDCR2_b.BYSW = ~bit_order;
This one does a byte-swap for the 32 bit transfers that happen as optimization when doing buffered transfers.
And for the background, while I was happy to see that Renesas finally released new versions of the datasheet and user manual back in September 2023, the user-manual is at Rev.1.10 now, for the SPI they only fixed the issue that in register SPDCR the bit SPBYT was not documented.
The register SPDCR2 is still not mentioned in the user-manual.
Please fix @Renesas.

Thank you for this quick & efficient analysis @RudolphRiedel !
I can confirm LSB is now ok :)

Will continue to test against real device.
BTW, any reason to use ~bit_order instead of !bit_order for a on/off value ?

BTW, any reason to use ~bit_order instead of !bit_order for a on/off value ?

No, I just wanted to inverse the value after I saw that SPCMD_b[0].LSBF needed a 1 to activate LSBFIRST.
And bit_order is not a boolean, it is spi_bit_order_t which is a typedef for an enum, so this is of type int (at least).
I just checked, !bit_order does also work.
And what would be more confusing, "bitorder + 1" and "bitorder - 1" also do work. :-)
Now I am not sure what the most appropriate variant is, especially in the C++ context.

Just my vision of target bitfield :')
Anyway, I'm now still stuck because Elechouse's PN532 module is a little bit too low for the R4 logic level :( - R3 was fine

3.1V needed to be considered as a 1 on GPIO

I can't imagine what can be the result on MISO :'), but that's another story...

Anyway, I'm now still stuck because Elechouse's PN532 module is a little bit too low for the R4 logic level :( - R3 was fine

3.1V needed to be considered as a 1 on GPIO

I has been a while since I used something like this so I just checked the datasheet for the NXP PN532.
It has a supply voltage range of 2.7V to 5.5V and Elechouse have "VCC: 3.3V~5V" in their documentation.
At 3.3V the required minimum level for the SPI pins for high is 2.31V.

Thank you for help :) I feel lucky on the PN532, it is very tolerant.
I'm more worried on the Arduino R4 side : I was unable to read a logical value of 1 on a GPIO before reaching >3.1V
And the PN532 is more around 3.0V output...
I don't think I will be able to do without a fast level shifter this time :')

TXS0108EPWR looks cool :) - https://www.ti.com/lit/ds/symlink/txs0108e.pdf

Oh, the R4 is actually a 5V  design, so that would be 3.5V for high.
I did not even consider that because it is an ARM and very few run at 5V.
But since SPI is uni-directional a simple buffer such as 74HCT1G125 should work as "amplifier".

Thanks for your report @gentilkiwi and to @RudolphRiedel for your pull request.
Although it is very interesting, I would appreciate it if we can keep this discussion tightly focused on the original subject matter. Discussion of @gentilkiwi's project is off topic for this issue and for this repository.
You are welcome to continue the conversations on Arduino Forum:
https://forum.arduino.cc/


NullReferenceException in SqlORchestrationService

Hi there!
We currently are evaluating durabeltask-mssql since we are not happe with the default storage provider and Netherite seems to have issues with our scenario.
Thinks look good with mssql so far :)
But we have many exceptions in our log. We are not sure if this is a problem, since at the end of the message there is stated: 'Backing of for 1 seconds until 5 sucessful operations'. This sounds for me, like there is a retry mechanism which will resolve the problem.
Could you please confirm, that this exception can safely be ignored?
If so, would it be possible to catch this exception or prevent that it's logged?
Here the exception:

Category
DurableTask.Core

Event name
ProcessWorkItemFailed

Formatted message
TaskOrchestrationDispatcher-2d2b9b07130949b3a02e825caa30d54a-0: Unhandled exception with work item '@calculator@S300L160371': System.NullReferenceException: Object reference not set to an instance of an object.at DurableTask.SqlServer.SqlOrchestrationService.CompleteTaskOrchestrationWorkItemAsync(TaskOrchestrationWorkItem workItem, OrchestrationRuntimeState newRuntimeState, IList1 outboundMessages, IList1 orchestratorMessages, IList1 timerMessages, TaskMessage continuedAsNewMessage, OrchestrationState orchestrationState) in /_/src/DurableTask.SqlServer/SqlOrchestrationService.cs:line 342
at DurableTask.Core.TaskOrchestrationDispatcher.OnProcessWorkItemAsync(TaskOrchestrationWorkItem workItem) in /_/src/DurableTask.Core/TaskOrchestrationDispatcher.cs:line 611
at DurableTask.Core.TaskOrchestrationDispatcher.OnProcessWorkItemSessionAsync(TaskOrchestrationWorkItem workItem) in /_/src/DurableTask.Core/TaskOrchestrationDispatcher.cs:line 211
at DurableTask.Core.WorkItemDispatcher1.ProcessWorkItemAsync(WorkItemDispatcherContext context, Object workItemObj) in /_/src/DurableTask.Core/WorkItemDispatcher.cs:line 373Backing off for 1 seconds until 5 successful operations

I just realized that this exception always comes together with several warning logs (warnings come first).

Category
DurableTask.Core

Event name
DiscardingMessage

message
{entityId}: Discarding [EventRaised]: Received work-item for an invalid orchestration

details
Received work-item for an invalid orchestration

Ah, another info: we are using in-process functions, with .NET 6

Glad to hear that the MSSQL package is mostly working well for you. :)
The NullReferenceException makes me think there is a bug in our code that's somehow specific to @calculator@S300L160371. For example, maybe there's some unexpected or missing state in the database. Because this exception is going unhandled in the SQL provider code, it's resulting in throttling by the Durable Task Framework, which will impact the throughput of the entire VM.
I think we need to look at this more closely to understand what's causing the null-ref and try to fix it. Which versions of the DurableTask nuget packages are you using?

@gha-zund with the information you provided above, I was able to locate your Durable Entity instance and see this exception and the warnings you mentioned. I suspect that there's some error case that results in storing invalid state into the database. Corrupt state in the database will trigger the warning you're seeing, and I suspect that warning is what leads to the exception.
I'm not sure if it's related to concurrency - the SQL backend has strong transactional consistency which should make it more resistant to state corruption. However, we can't completely rule it out yet.
To root cause this, I'll need to see what data you have in your database. Are you able to run the following query against your SQL database and share the results (feel free to scrub out any data that can't be shared publicly):
DECLARE @EntityID varchar(50) = '@calculator@S300L160371'
SELECT * FROM dt.Instances WHERE InstanceID = @EntityID
SELECT * FROM dt.History WHERE InstanceID = @EntityID
SELECT * FROM dt.NewEvents WHERE InstanceID = @EntityID

Ideally this would be captured when the errors are ongoing for a particular entity, and you can change the entity ID used in the query if needed. If the problem self-heals, then the result may not contain anything useful. The most important result would be the data in the dt.History table, which would give us a clue about whether there is corruption.

Alright, thanks for the hints!
I fear the data will not be available anymore, since we purged all the history for all entities to get a clean state for further evaluation...
The warnings did not occur the last 24h anymore, so maybe the problem is gone too.
We will keep the eyes open and provide the data in case the warnings appear again!

OK, no worries. I'll close this issue in the meantime but ping me if you see it again and we can reopen.


Activate package development

Thanks for the awesome package ! :+1:
I'm trying to integrating this in my workflow.
Running into some issues while trying to activate package for development

Command used
ion dev $package_path

Expected result
Package is compiled for development

Actual output

ERROR: could not load library "/home/user/.ion/bin/ion.so"
/home/user/.ion/bin/ion.so: undefined symbol: jl_f__apply_latest
ERROR: failed process: Process(`/home/user/.ion/bin/julia -Cnative -J/home/user/.ion/bin/ion.so --compile=min -g1 -e 'using Pkg; pkg"dev --shared /home/user/Documents/codes/julia/BlockingMC" '`, ProcessExited(1)) [1]

Stacktrace:
 [1] pipeline_error at ./process.jl:525 [inlined]
 [2] run(::Cmd; wait::Bool) at ./process.jl:440
 [3] run(::Cmd) at process.jl:438
 [4] (::IonBase.var"#5#6"{Cmd})() at /home/runner/.julia/packages/IonBase/cqJsJ/src/command/pkg.jl:87
 [5] withenv(::IonBase.var"#5#6"{Cmd}, ::Pair{String,String}) at env.jl:161
 [6] dev(::String; shared::Bool, glob::Bool) at /home/runner/.julia/packages/IonBase/cqJsJ/src/command/pkg.jl:86
 [7] command_main(::Array{String,1}) at /home/runner/.julia/packages/Comonicon/6OS1s/src/codegen/ast.jl:202
 [8] command_main() at /home/runner/.julia/packages/Comonicon/6OS1s/src/codegen/ast.jl:46
 [9] julia_main() at /home/runner/.julia/packages/Comonicon/6OS1s/src/parse/cast.jl:316
 [10] julia_main() at none:32

Hi this is deprecated in favor of https://github.com/Roger-luo/Ion.jl also this is highly unstable don't depend on it, unless you are confident with revising the implementation.

OK perfect ! Thanks.


Is there an operator to translate the stressess or nodal displacements to a local coordinate system?

Discussed in https://github.com/ansys/pydpf-core/discussions/1560

Originally posted by viks4mech May 13, 2024
Hi,
I would like to obtain the stress at nodal location with respect to local coordinate systems?
is there already an operator to perform this task?

@viks4mech Are you trying to get stresses in local esys?


fix: fixed executeShellScript utility and saveLog function

Intent

Fix executeShellScript utility for Windows.
Fix saveLog function for Windows.

Implementation

Add sh prefix executeShellScript utility for Windows.
Replace path.sep with /.

Checks

[x] Code is formatted correctly (npm run lint:fix).
[ ] Any new functionality has been unit tested.
[ ] All unit tests are passing (npm test).
Mocked:

Server:
[ ] All CI checks are green.
[ ] JSDoc comments have been added or updated.
[x] Reviewer is assigned.

Server tests failed:


Custom haproxy config fix: Exclude backend configs for targets that do not exist

Do not include the backends in the custom config, if they are not found in the loadbalancer backends.
This happens if some target services are stopped, the config related to these
stopped targets should not be added to haproxy config even if they are mentioned in custom config, else they cause haproxy reoad to fail.
https://github.com/rancher/rancher/issues/8424

@alena1108 @cjellick please review

LGTM


Add defer to uncached filestore (resolves #1189)

resolves #1189
Add defer functionality to the uncached file store.

This is incomplete and currently only addresses the abstraction of the file store.

Jenkins, test this please.

@hannes-ucsc i implemented the suggested changes

I had started a review a long time ago, didn't finish it and never clicked submit. I submitted it just now but still need to finish the review. Doing that right now.

@hannes-ucsc this is ready!

Once those nits are fixed, I will merge.

Jenkins, test this please.

Failure in ba620bc is not a problem. The test is being discarded in the next commit anyway

Jenkins, test this please.

@hannes-ucsc could you please look at this? I will squash after I implement all your feedback since your feedback will be binned into one of the 4 final commits
1. Fix bug in NonCachingFileStore regarding local files
2. Add an abstract file store and refactor accordingly
3. Refactor filestore tests
4. Implement Defer in NonCachingFileStore (resolves #1189)

@hannes-ucsc @cket this is ready

We should probably squash this down on merge.
Leaving final decision to @cket.


MedGAN on PyTorch?

Apologies if this question does not belong in this repo, but this seems to be the only place where MedGAN is being discussed.
Does anyone know of any implementations of MedGAN for PyTorch? I am considering doing it myself but it will be quite a challenge.
Thank you.

Or can anyone print the model summaries of the generator and discriminator?


[HOLD for payment 2024-07-10] [$250] Login - "Chat and split expenses" option is truncated on the onboarding modal

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

issue found when executing #43479
Version Number: 1.4.84-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:
Action Performed:

Open the app
Log in with a new Gmail account

Expected Result:
"Chat and split expenses" option should be fully visible.
Actual Result:
"Chat and split expenses" option is truncated on the onboarding modal.
Workaround:
visual
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/38435837/680b5ce8-cce2-46a7-be2d-f03d9830ac41

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c02ce36ab64ecdf6
Upwork Job ID:<PHONE_NUMBER>422060262
Last Price Increase: 2024-06-21
Automatic offers:

allgandalf | Reviewer | 102851828
nkdengineer | Contributor | 102851830

Issue OwnerCurrent Issue Owner: @OfstadC

@OfstadC FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
The number of lines for menuitem titles is set to 1 by default
https://github.com/Expensify/App/blob/75c104bfe009ef937bcd129a35bb5a2e52f4339d/src/components/MenuItem.tsx#L308
This restricts the titles to only 1 line in narrow screens
What changes do you think we should make in order to solve the problem?
We will pass number of lines for the title as 2 to make sure text gets rendered properly for smaller devices
We will add numberOfLinesTitle: 2 here:
https://github.com/Expensify/App/blob/75c104bfe009ef937bcd129a35bb5a2e52f4339d/src/pages/OnboardingPurpose/BaseOnboardingPurpose.tsx#L91-L93
Alternatively
We can pass this by adding a prop in MenuItemsList

I'm not able to reproduce 🤔

Okay - I tried on about 6 android devices, 3 of which google said had smaller screens and the only one I was able to reproduce on was Samsung S24 😅 .

Hi @Julesssss ! New to BZ here so just want to make sure I take the next steps. I see you self assigned, so should I add the internal label - or do we still want to create an external posting?

Hey @OfstadC, I assigned just because I was interested in seeing the solution to the bug. So we can follow the normal process 🙂

Discussed in Slack - The solution should ensure we aren't truncating when viewing or selecting the menu item. We'd want to let any device/width use as many lines as needed

Proposal
Please re-state the problem that we are trying to solve in this issue.
"Chat and split expenses" option is truncated on the onboarding modal.
What is the root cause of that problem?
By default, the title of MenuItem will have 1 as numberOfLinesTitle https://github.com/Expensify/App/blob/b021195b864211efbaaefe188226b2830b91b7d8/src/components/MenuItem.tsx#L320.
Therefore, when the text is long such that it should span 2 lines, it will be truncated.
What changes do you think we should make in order to solve the problem?

The solution should ensure we aren't truncating when viewing or selecting the menu item. We'd want to let any device/width use as many lines as needed

This is the requirement. We need to make sure the numberOfLines here is not set. One way to do it is to add numberOfLinesTitle: 0 here so no truncation will occur in any circumstance.
We use the same method in other locations like in https://github.com/Expensify/App/blob/b021195b864211efbaaefe188226b2830b91b7d8/src/components/ReportActionItem/MoneyReportView.tsx#L88 where no-truncation behavior is needed.
FYI any hardcoded value like 2 will not work reliably because there could be very small devices that will require 3 lines to display the item, or the copy of the title could be changed such that it needs more than 2 spaces in smaller devices.
What alternative solutions did you explore? (Optional)
Set the default numberOfLinesTitle here to 0 (and maybe the numberOfLinesDescription too). Truncating texts should be a conscious decision and should only be done intentionally, not accidentally just because the default value is set that way.

SOlution is simple and makes sense

I'll raise PR soon

@allgandalf this PR is ready for review

@allgandalf Could you please update this today based on the checklist? Thank you! 😃

Payment Summary:
Contributor+: @allgandalf paid $250 via Upwork
Contributor: @nkdengineer  paid $250 via Upwork

Leaving this open until regression testing is complete

Same - waiting on regression testing

I'm actually going to close this out. but I'll note here if the regression test yields anything 😄


Implement C++ JitInterface wrapper

Implement C++ JIT interface wrapper that will catch the managed exception and re-throw it as unmanaged exception so that we can throw managed exceptions from JitInterface and not crash afterwards on Linux.

Fixed via 8b4cc05.


[matlab] support feature extraction

add MXPredCreatePartialOut in c_prediction_api to allow specifying the output layers. note that we cannot reuse MXPredCreate by adding optional argument int num_output_nodes = 0 since matlab doesn't support it..

updated matlab/mxnet/model.m to support gpu and feature extraction

add titan-x performance numbers on image-classification

consider merge some superficial commits via http://mxnet.readthedocs.org/en/latest/contribute.html#how-to-combine-multiple-commits-into-one


Use go 1.6 on appveyor

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass

Seems the default has switched to 1.7, but we still use go 1.6.

Merging to get CI passing again.