[Device Support Request] OTA update for Eurotronic Spirit Zigbee

Is your feature request related to a problem? Please describe.
Current Eurotronic Spirit Zigbee firmware is unstable, which leads to many issues. See these issues: https://github.com/search?q="spirit+zigbee"&state=open&type=Issues
Eurotronic recently started publishing firmware releases on github, together with a guide on how to OTA update using deCONZ.
Describe the solution you'd like
Support OTA update via ZHA using the firmware listed on https://github.com/EUROTRONIC-Technology/Spirit-ZigBee
ZHA already supports OTA updates for IKEA and LEDVANCE devices: https://www.home-assistant.io/integrations/zha#ota-firmware-updates
Device signature
{
  "node_descriptor": "NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4151, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=0)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0301",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x000a",
        "0x0019",
        "0x0201"
      ],
      "out_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0004",
        "0x000a",
        "0x0019",
        "0x0201"
      ]
    }
  },
  "manufacturer": "Eurotronic",
  "model": "SPZB0001",
  "class": "zhaquirks.eurotronic.spzb0001.SPZB0001"
}

for now you are probably better off downloading the firmware manually and placing it into ota folder

for now you are probably better off downloading the firmware manually and placing it into ota folder

https://github.com/zigpy/zigpy/wiki/OTA-Device-Firmware-Updates
The otau_directory and ikea_update_url is optional, and is the file provider for any firmware files you have locally on your system.

https://github.com/zigpy/zigpy/wiki/OTA-Device-Firmware-Updates
The otau_directory and ikea_update_url is optional, and is the file provider for any firmware files you have locally on your system.

This issue should probably be moved to the zigpy repository instead? -> https://github.com/zigpy/zigpy
@malfroid please note that "zha-device-handlers" now only handles "quirks" and currently does not handle OTA providers.
You can read https://github.com/zigpy/zigpy/issues/154 for more information on how 'OTA Provider' (OTAProvider) works in zigpy.

PS: Maybe it is a good idea if zha-device-handlers also provides custom 'OTA Provider' (OTAProvider) for Zigbee devices?

FYI, I started a new discussion about these specific questions/ideas here -> https://github.com/zigpy/zigpy/discussions/654


[Feature 1.3] Train, Plot, Station, Track classes

calculates the schedules based on train movement

Train modelling system already finished


fix: uninlined args, it's not well recognized and actually doesn't improve readability

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


Different versions of a package in requirements.txt and requirements-full.txt

What's the difference between requirements.txt and requirements-full.txt? The version of werkzeug in those two files is different.

Good catch. The proper version is the one from requirements.txt. This is now fixed.


feat: update to latest Zig

Thanks for this project! This might end up being useful for a project I'm working on, so I wanted to get it working on the latest master version of Zig; this is the result I came up with.

Thanks! I applied both requested changes 😄


Add Native and Extensibility maintainers to CODEOWNERS

And add any missing subprojects for other teams too.

@bot-gradle merge

I've triggered a build for you. Click here to see all failures if there's any.


Unwinding tutorial doesn't match actual behaviour.

The loop unwinding tutorial says at 11 I should still get the unwinding assertion, but I don't. At 12 or higher I don't see the second error, either.

Thanks for pointing this out! We've opened a PR to update the tutorial.


Bots: Add metadata scheme for bots.

Name & (short) description
Whether to use any default commands (default to enabled):
(about, '' (empty), usage [remove?], help/commands)
Provide a list of user commands, which help/commands uses

This is an alternative/supplement/extension of #58, which would also resolv #55.
I also raised the idea of bot metadata in #integrations.
Currently this just provides default-commands which use the simple metadata and (optionally) a list of bot commands provided by the developer. It could allow the user to provide callbacks directly, with the handle_message in the bot only being used for more complex input (like zulip/zulip#5047)

Updated to reflect most review comments; pending are final if statement and linter (since code has changed).

@timabbott Changes made in a new commit to show the changes separately, though will squash or split as necessary.

Current status is: (copying from zulip, to keep the context)

I've mostly updated the metadata PR, and put the changes into a separate commit to be squashed in the final version, if that works.
The updated (simpler) updated_default_commands approach @timabbott hinted at leaves the functions (were lambdas) pointing at the old data (notably for help & commands), so listing them in commands actually shows them twice (old default_commands and bot-provided commands list). This could be solved by going back to one data structure, if that could work, or some other approach involving passing in default_commands (new version) to the functions? (the alternative solution would be to just make default commands be all-or-nothing, ie. default_commands_enabled = False and commands is ignored, or True and they're used?)

@neiljp I find this rather hard to review - it'd be awesome if you could split this in multiple, easily digestible commits; e.g. one for updating a bot with the feature, one for adding default commands, one for the core update command logic, etc.
Additionally, I think this would really profit from some unittests, which could for example be added in the updated bots themselves.

@derAnfaenger I've done a basic split into 3 parts. The last real commit may benefit from discussion/readjustment still, but the first two should be clear separate commits to review/apply as they stand.

@derAnfaenger Pushed updated commits based on your suggestions.
Thoughts:

'help' parts of the dict could be left out of the second commit (and the dict form), if wanted
bot testing & zulip_bot_output.py both miss out on the changes from using this code, as it stands, so all tests will pass for these changes, but primarily since the tests don't "see" the change in code.
the default vs extend vs overwriting of command (help) remains a little challenging, and could even be "simplified" by (optionally) allowing the lib to have callback functions for listed commands?

I merged the first commit.

I've refactored some of these commits to be smaller and clearer, and added some which amend the testing framework and zulip_bot_output.py to use the same logic as lib.py (before those commits, they provide different results from tests and running them, which indicates they should be in the same commit?).
I still would like to think/discuss about the way commands might work, but this is getting closer, I feel.

Currently the CI is failing, since I'm unsure whether to encode the complex default command responses in the tests, when they're so automated from the other data? That is, should I update the "help" text for the xkcd bot to ensure it passes, or remove that test?

Hi @neiljp Can you resolve the conflicts here?

The concepts here are pretty valuable, but the PR has become too stale. I think we can close it but it's definitely worth doing a follow-up on this.

@PIG208 This PR is very old now and out of date, but my recollection was of various driving elements:

Using the META tags to be able to not just know the user-name for a bot, but what bot code is running (if there is) behind it - by whatever method; some bots already have these added
Having a layer on top of the bots to make a standard set of commands, or at least simple ways of interacting with bots, easier; so eg. help, about, ... and these could use the META tags (or not)

Note that #169 takes forward one of these points forward.


port oidc customizations.

@anny1099, I don't think we need these OIDC customizations at all.
OIDC ATTRIBUTE MAPPING (feature/oidcAttributeMapping branch) have been taken upstream since 4.6.0. PR https://github.com/cloudfoundry/uaa/pull/598
OIDC WELL KNOWN ENDPOINT(fix/oidc_well_known_endpoint branch) have been implemented in the upstream also since 4.6.0
IMPLICIT OIDC FIX (fix/implicit_oidc branch) all the commits from the branch are merged into predix_extensions_4.10.0
Am I missing anything?
cc: @metacubed, @Bitty9

@anny1099, I don't think we need these OIDC customizations at all.
OIDC ATTRIBUTE MAPPING (feature/oidcAttributeMapping branch) have been taken upstream since 4.6.0. PR cloudfoundry#598
OIDC WELL KNOWN ENDPOINT(fix/oidc_well_known_endpoint branch) have been implemented in the upstream also since 4.6.0. Commit cloudfoundry@4b8e9a0
IMPLICIT OIDC FIX (fix/implicit_oidc branch) all the commits from the branch are merged into predix_extensions_4.10.0
Am I missing anything?
cc: @metacubed, @Bitty9

@irinaepshteyn , This story is for new branching model. anything has been merged into upstream is not picked, for example oidcAttributeMapping; I noticed fix/oidc_well_known_endpoint branch has additional changes not in upstream, so it is included here. When picking the changes from fix/implicit_oidc branch, also excluded the changes overlapped with brandhing.

since most of changes have been covered by upstream, this can be closed.


"go run ./update-urls/main.go" fails with "unhandled X receiver type: *ast.CallExpr"

While trying to follow the instructions in the header comments of update-urls/main.go:
// Usage (from go-github directory):
//   go run ./update-urls/main.go
//   go generate ./...
//   go test ./...
//   go vet ./...

I encountered the following error at the very first step:
$ go run ./update-urls/main.go
2021/08/20 23:06:44 processCallExpr: unhandled X receiver type: *ast.CallExpr
exit status 1

Tested with go1.15.15, go1.16.7 and go1.17.
Might be related to #2056?
Thanks in advance!

update-urls is a maintainer tool only.  Users of the repository are not expected to run it.
Thank you for the alert, though.
I will investigate.
Closing issue.


Ingest scanned maps w/o bibid

Ingest batch of maps
Extract metadata from records with FGDC.

Done.


VersionInfo.next_version() returns Union[VersionInfo, str]

VersionInfo.next_version() return type is uncertain because at line 463 of semver.py return version.replace(prerelease=None, build=None) returns a VersionInfo object, whereas in line 466 it is explicitly converted to str and at line 470, version.bump_prerelease() is documented with rtype: str.
This is problematic because if you call this on a version that has a prerelease or build number, you get a VersionInfo object, and otherwise you get a str, and these two types must be handled quite differently.
Personally, I would expect VersionInfo.next_version() to return a VersionInfo object in all cases, but I think the main problem here is the ambiguity of the return type.

Thanks @tlaferriere for your report! I think this is an oversight. From my understanding, the method should always return a VersionInfo object.
We should ask @gsakkis, I guess you've intended to return a VersionInfo object all the time, am I right with this assumption?

Thanks George for conforming! :+1:
I will create a 2.10.1 release soon.


Protractor test execution causes EADDRINUSE error

Hi!
I am getting error Error: EADDRINUSE connect EADDRINUSE <IP_ADDRESS>:60267 every time when I am running my UI tests in parallel.
Below are more details about conf.js and errorlog.
Bug report

Node Version: 4.5.0

Protractor Version: 4.0.14

Angular Version: 1.X

Browser(s): Chrome 2.29

Operating System and Version : Win server 2008 R2

Your protractor configuration file
// babel-register allows for ES6 in Protractor test scripts
require('babel-register');

exports.config = {
directConnect: true,
chromeDriver: './4_utilsObjects/chromedriver_2.29.exe',

allScriptsTimeout: 180000,

framework: 'jasmine',

specs: ['launcher1.js','launcher2.js'],

rootElement: '[ng-app="preApp"]',

capabilities: {
    'browserName': 'chrome',
    'chromeOptions': {
        // needed to disable saving passwords in account creation tests
        'prefs': {
            'credentials_enable_service': false,
            'profile': {
                'password_manager_enabled': false
            }
        }
    },
    shardTestFiles: true,
    maxInstances: 2,
},

// Jasmine timeout is defined here overriding default Protractor timeout
jasmineNodeOpts: {
    silent: true,
    defaultTimeoutInterval: 180000,
    // needed for jasmine-spec-reporter
    print: function () {
    }
},

onPrepare: () => {
    // here we're adding real time jasmine reporter that will display test steps
    // see https://github.com/bcaudan/jasmine-spec-reporter
    var SpecReporter = require('jasmine-spec-reporter');
    // add jasmine spec reporter
    jasmine.getEnv().addReporter(new SpecReporter({
        displayStacktrace: 'none',
        displaySuccessfulSpec: true,
        displayFailedSpec: true,
        displaySpecDuration: true,
        displaySuiteNumber: true,
        displayPendingSummary: false,
        displayPendingSpec: false
    }))

    // adding Jasmine JUnit reporter
    var jasmineReporters = require('jasmine-reporters');
    jasmine.getEnv().addReporter(new jasmineReporters.JUnitXmlReporter({
        consolidateAll: true,
        savePath: 'reports/JUnitReporter',
        filePrefix: 'testresults'
    }))

    // reporter for TeamCity, enabled only in CI
    if (process.env.TEAMCITY_VERSION)
    {
        jasmine.getEnv().addReporter(new jasmineReporters.TeamCityReporter());
    }

    // Disable animations so e2e tests run faster
    var disableNgAnimate = function () {
        angular.module('disableNgAnimate', []).run(['$animate',function ($animate) {
            $animate.enabled(false);
        }]);
    }
    browser.addMockModule('disableNgAnimate', disableNgAnimate);

    // reporter taking screenshots when failed assertion is spotted, comment out to speed up test run
    var Jasmine2HtmlReporter = require('protractor-jasmine2-html-reporter');
    jasmine.getEnv().addReporter(new Jasmine2HtmlReporter({
        savePath: 'reports/screenshotReporter/',
        takeScreenshotsOnlyOnFailures: true,
    }))
}

};

Output from running the test : Failed: EADDRINUSE connect EADDRINUSE <IP_ADDRESS>:60267
Error: EADDRINUSE connect EADDRINUSE <IP_ADDRESS>:60267
at ClientRequest. (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\http\index.js:381:15)
at emitOne (events.js:77:13)
at ClientRequest.emit (events.js:169:7)
at Socket.socketErrorListener (http_client.js:269:9)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at emitErrorNT (net.js:1269:8)
at nextTickCallbackWith2Args (node.js:442:9)
at process.tickCallback (node.js:356:17)
From: Task: Protractor.waitForAngular() - Locator: By(css selector, div.ng-hide[data-ng-show="spinner"])
at Driver.schedule (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:377:17)
at ProtractorBrowser.executeAsyncScript (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\built\browser.js:235:28)
at runWaitForAngularScript (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\built\browser.js:263:30)
at ProtractorBrowser.waitForAngular (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\built\browser.js:269:16)
at ElementArrayFinder.getWebElements (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\built\element.js:167:29)
at ElementFinder.isPresent (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\built\element.js:1037:46)
at C:\BuildAgent10-1\work\e307a028e92341bb\Cinema.Web\UIAutomation\4_utilsObjects\pageUtils.js:199:75
at C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:716:14
at TaskQueue.execute (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2913:14)
at TaskQueue.executeNext_ (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2896:21)
From: Task:
at null.pollCondition [as onTimeout] (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2359:16)
at Timer.listOnTimeout (timers.js:92:15)
From: Task:
at ControlFlow.wait (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2352:17)
at Driver.wait (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:712:29)
at ProtractorBrowser.to.(anonymous function) [as wait] (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\built\browser.js:62:29)
at PageUtils.waitForSpinnerFinished (C:\BuildAgent10-1\work\e307a028e92341bb\Cinema.Web\UIAutomation\4_utilsObjects\pageUtils.js:198:17)
at PurchasePage.clickOnContinueButton (C:\BuildAgent10-1\work\e307a028e92341bb\Cinema.Web\UIAutomation\3_pageObjects\purchasePage.js:584:15)
at Object. (C:\BuildAgent10-1\work\e307a028e92341bb\Cinema.Web\UIAutomation\2_testScenarios\purchaseFeature.js:663:30)
at C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:94:23
at new ManagedPromise (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:1082:7)
at controlFlowExecute (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:80:18)
at TaskQueue.execute (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2913:14)
From: Task: Run it("click on "continue" button to confirm the payment") in control flow
at Object. (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:79:14)
at attemptAsync (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:1916:24)
at QueueRunner.run (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:1871:9)
at QueueRunner.execute (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:1859:10)
at Spec.Env.queueRunnerFactory (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:697:35)
at Spec.execute (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:359:10)
at Object.fn (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:2479:37)
at attemptAsync (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:1916:24)
at QueueRunner.run (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:1871:9)
at C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:1898:16
From asynchronous test:
Error
at Suite. (C:\BuildAgent10-1\work\e307a028e92341bb\Cinema.Web\UIAutomation\2_testScenarios\purchaseFeature.js:662:13)
at addSpecsToSuite (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:833:25)
at Env.describe (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:802:7)
at jasmineInterface.describe (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:3375:18)
at purchaseFeature (C:\BuildAgent10-1\work\e307a028e92341bb\Cinema.Web\UIAutomation\2_testScenarios\purchaseFeature.js:282:9)
at Suite. (C:\BuildAgent10-1\work\e307a028e92341bb\Cinema.Web\UIAutomation\1_testLaunchers\desktopTestLauncher.js:32:21)
at addSpecsToSuite (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:833:25)
at Env.describe (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:802:7)
at jasmineInterface.describe (C:\Users\teamcity_build\AppData\Roaming\npm\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:3375:18)
------- Stdout: -------
[chrome #01-0]        [31mÃ— click on "continue" button to confirm the payment [39m (3 secs)
[chrome #01-0]          [31m-  [39m [31mFailed: EADDRINUSE connect EADDRINUSE <IP_ADDRESS>:60267 [39m
[chrome #01-0]
[chrome #01-0]

Are you sure the port is not already used? See also https://stackoverflow.com/questions/4075287/node-express-eaddrinuse-address-already-in-use-kill-server
By the way, you are using an old version of Protractor and an old version of NodeJS, have you also tried updating?

See #4091

Read the Oracle advise (click here)

Adjusting TCP Settings for Heavy Load on Windows
The underlying Search architecture that directs searches across multiple physical partitions uses TCP/IP ports and non-blocking NIO SocketChannels to connect to the Search engines. These connections remain open in the TIME_WAIT state until the operating system times them out. Consequently, under heavy load conditions, the available ports on the machine running the Routing module can be exhausted.
On Windows platforms, the default timeout is 120 seconds, and the maximum number of ports is approximately 4,000, resulting in a maximum rate of 33 connections per second. If your index has four partitions, each search requires four ports, which provides a maximum query rate of 8.3 queries per second.
(maximum ports/timeout period)/number of partitions = maximum query rate.
If this rate is exceeded, you may see failures as the supply of TCP/IP ports is exhausted. Symptoms include drops in throughput and errors indicating failed network connections. You can diagnose this problem by observing the system while it is under load, using the netstat utility provided on most operating systems.
To avoid port exhaustion and support high connection rates, reduce the TIME_WAIT value and increase the port range.
Note: This problem does not usually appear on UNIX systems due to the higher default connection rate in those operating systems.
To set TcpTimedWaitDelay (TIME_WAIT):
Use the regedit command to access the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters registry subkey.
Create a new REG_DWORD value named TcpTimedWaitDelay.
Set the value to 60.
Stop and restart the system.
To set MaxUserPort (ephemeral port range):
Use the regedit command to access the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters registry subkey.
Create a new REG_DWORD value named MaxUserPort.
Set this value to 32768.
Stop and restart the system.

Read the Oracle advise (click here)

Adjusting TCP Settings for Heavy Load on Windows
The underlying Search architecture that directs searches across multiple physical partitions uses TCP/IP ports and non-blocking NIO SocketChannels to connect to the Search engines. These connections remain open in the TIME_WAIT state until the operating system times them out. Consequently, under heavy load conditions, the available ports on the machine running the Routing module can be exhausted.
On Windows platforms, the default timeout is 120 seconds, and the maximum number of ports is approximately 4,000, resulting in a maximum rate of 33 connections per second. If your index has four partitions, each search requires four ports, which provides a maximum query rate of 8.3 queries per second.
(maximum ports/timeout period)/number of partitions = maximum query rate.
If this rate is exceeded, you may see failures as the supply of TCP/IP ports is exhausted. Symptoms include drops in throughput and errors indicating failed network connections. You can diagnose this problem by observing the system while it is under load, using the netstat utility provided on most operating systems.
To avoid port exhaustion and support high connection rates, reduce the TIME_WAIT value and increase the port range.
Note: This problem does not usually appear on UNIX systems due to the higher default connection rate in those operating systems.
To set TcpTimedWaitDelay (TIME_WAIT):
Use the regedit command to access the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters registry subkey.
Create a new REG_DWORD value named TcpTimedWaitDelay.
Set the value to 60.
Stop and restart the system.
To set MaxUserPort (ephemeral port range):
Use the regedit command to access the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters registry subkey.
Create a new REG_DWORD value named MaxUserPort.
Set this value to 32768.
Stop and restart the system.

with me it didn't work

Read the Oracle advise (click here)

Adjusting TCP Settings for Heavy Load on Windows
The underlying Search architecture that directs searches across multiple physical partitions uses TCP/IP ports and non-blocking NIO SocketChannels to connect to the Search engines. These connections remain open in the TIME_WAIT state until the operating system times them out. Consequently, under heavy load conditions, the available ports on the machine running the Routing module can be exhausted.
On Windows platforms, the default timeout is 120 seconds, and the maximum number of ports is approximately 4,000, resulting in a maximum rate of 33 connections per second. If your index has four partitions, each search requires four ports, which provides a maximum query rate of 8.3 queries per second.
(maximum ports/timeout period)/number of partitions = maximum query rate.
If this rate is exceeded, you may see failures as the supply of TCP/IP ports is exhausted. Symptoms include drops in throughput and errors indicating failed network connections. You can diagnose this problem by observing the system while it is under load, using the netstat utility provided on most operating systems.
To avoid port exhaustion and support high connection rates, reduce the TIME_WAIT value and increase the port range.
Note: This problem does not usually appear on UNIX systems due to the higher default connection rate in those operating systems.
To set TcpTimedWaitDelay (TIME_WAIT):
Use the regedit command to access the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters registry subkey.
Create a new REG_DWORD value named TcpTimedWaitDelay.
Set the value to 60.
Stop and restart the system.
To set MaxUserPort (ephemeral port range):
Use the regedit command to access the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters registry subkey.
Create a new REG_DWORD value named MaxUserPort.
Set this value to 32768.
Stop and restart the system.

with me it didn't work


Support UtMock for fuzzer tests

Description
Substitute this text with a concise description of the proposed change. Emphasize, why particular solution was chosen.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

Minor bug fix (non-breaking small changes)
Bug fix (non-breaking change which fixes an issue)
Refactoring (typos and non-functional changes)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Regression and integration tests
Please, provide regression or integration tests for your code changes. If you don't do that, the reviewer can and highly likely will reject the PR. It is the contributor's responsibility to provide such tests or to reason why they are missing.
Automated Testing
Specify tests that help to verify the change automatically.
Example: org.utbot.examples.algorithms.BinarySearchTest
Manual Scenario
Please, provide several scenarios that you went through to verify that the change worked as expected.
Checklist (remove irrelevant options):
This is the author self-check list

[ ] The change followed the style guidelines of the UTBot project
[ ] Self-review of the code is passed
[ ] The change contains enough commentaries, particularly in hard-to-understand areas
[ ] New documentation is provided or existed one is altered
[ ] No new warnings
[ ] New tests have been added
[ ] All tests pass locally with my changes

Could you please edit PR description - now it's just template


Brilliant!

https://github.com/foxdonut/meiosis/blob/e38b896afe72057ba88e9df767a3a5c5f9ddf276/helpers/common/setup.js#L37-L41
This solves a real headache!

@smuemd thanks!
I will change to named parameters, i.e. from:
export const setup = (stream, accumulator, acceptor, app) => ...

to:
export const setup = ({ stream, accumulator, acceptor, app }) => ...

Also I'm debating making acceptor optional, for when you don't have any acceptors in app.
Any thoughts and suggestions are welcome!

Also I'm debating making acceptor optional, for when you don't have any acceptors in app.

a good idea
Maybe also worth debating could be to rename app.actions to app.Actions, since it works a bit like a constructor and you have a name collision down the line, when passing bufferdUpdate

Maybe also worth debating could be to rename app.actions to app.Actions, since it works a bit like a constructor and you have a name collision down the line, when passing bufferdUpdate

Great idea, thank you :+1:

I really like this a lot.
Being able to call multiple updates in services is very liberating.
The setup script makes the pattern feel a bit more library like. But at the same time, it becomes a lot more approachable I think.
For consistency, I guess I'd also capitalize initial like so:
function setup ({ stream, accumulator, acceptor, app }) {
  app = app || {}

  const {
    Initial = () => ({}),
    Actions = () => ({}),
    acceptors = [],
    services = []
  } = app

/* ... */

}

Really happy to hear your positive feedback, it means a lot and I appreciate it.
I also agree that Initial makes this more consistent, I have made the change.
Thank you @smuemd !


Error fix

I want the functions to return to the step with the user input error (i.e. entering 3 when it only accepts 1 or 2) rather than having to start DINKcalculator() all over again.

I have submitted a pull request for this functionality. #2


Could Subscription filter message for consumer

Expected behavior
Subscription could filter message for consumer
Tell us what should happen
For example, certain user only care about message for himself, then he want filter all message and only get message specific for him based on one properties in the message, guess it's "user_id".
Actual behavior
Seems not support
Steps to reproduce
How can we reproduce the issue
System configuration
Pulsar version: x.y

@vincent-pli : currently it is not supported yet. One solution is to use pulsar functions. You can write a pulsar function to filter the messages by user_id and route the messages to user's own topic.

Thanks for your reply, I want to know if creating/delete topic in run time is expensive or not.
If it's cheap, I can adopt the pulsar function, thanks


Points deps update to release 0.2

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

none

is the same needed every other repo ?
can the tool know which branch it's running from so we don't have to change N files for each branch?

Totally agree.

/test istio-presubmit
Test are not properly triggered.

I just protected the branch when I saw this PR showing mergeable so maybe that's why the bot wasn't auto testing it

Thanks! And it's running tests now. I don't know, it shouldn't be. I looked at PRs merged to this branch, they all got triggered. Hmm, wired. And there is nothing wrong with Prow.

/subscribe

/approve


"More Articles" Repeats previous 3

Hitting "More Articles" at the bottom of the Magazine Homepage, repeats the last 3 before showing new ones.

@owendodd looking into this one andwondering if the "more" button's count is still supposed to be displayed on the magazine page?  The bug looks to be in this count, which is currently not displaying.

Figured this one out -- the count is showing after the first click


lastest commit requires new version of goimports.

I was a bit suprised when after updating last night go-mode in spacemacs suddenly started failing with an error from gofmt. Looking at the messages I saw:
Calling gofmt: goimports (-srcdir /Users/matthew/src/services/src/chgbuf/ -w /var/folders/hg/np4sqzds1h58hql8337fvn0r0000gn/T/gofmt4232TJr.go)

After digging around for a bit I saw that https://github.com/dominikh/go-mode.el/commit/8d1594fa56823300d36a45c3a483de3f0d503ff2 started magically detecting go-imports and adding the -srcdir arg which wasn't supported by older versions of go-imports. Updating go-imports fixed the issue, but it would have been a less frustrating experience if somehow I was warned that updating go-imports was required.

Do you have a suggestion for how we should warn/inform users?

Pop a dialog? I'm not that familiar with emacs internals so I don't know how practical that is. Another suggestion would be to not use this argument on a version of go-imports which does not support it.

Well, getting an error is your "dialog". We could theoretically detect the error output and re-run without the srcdir flag, but I'm not sure it is worth the extra complexity. I'd much rather people updated to the latest goimports. They really should, as they may end up with incorrect imports as soon as they work with vendoring if they don't update.

Perhaps the problem is mine, but I found it confusing to suddenly have saving files pop an error about -srcdir being an invalid argument especially when I didn't really remember updating last night before going to bed :)

I'll see if I can emit a nicer error when we detect goimports complaining about the flag.

We'll now print Your version of goimports is too old and doesn't support vendoring. Please update goimports! at the top of the gofmt error buffer if we detect that the error was due to -srcdir being unsupported. This should be good enough I think.

Sounds great!


[Inprovement] Allow to view shader resource view for Texture2d/Texture3d types.

For now only raw resource types can be displayed on editor.
This prevents to display Depth Stencils and any texture type that cannot have a default view.

Check if view is of Texture2d/Texture3d dimension
If yes, use it for display instead.
Make sure single channel resource are displayed as Black and White.

Sounds like an excellent proposal!

It would be awesome if you could submit a pull request...


Users able to change their passwords

Hi @vpp
Just a feature request. It would be good if we could allow users to be able to change their passwords once they are logged in.
Kind Regards,
Asim Pervez

I know users can simply reset their password using forgot password but maybe it would be a nice feature for a future update if they could update their password within their profile.

Hi Asim,
It is reasonable feature.
Let's have this ticket opened.

On 24 Feb 2017, at 16:15, AsimPervez93<EMAIL_ADDRESS>wrote:
I know users can simply reset their password using forgot password but maybe it would be a nice feature for a future update if they could update their password within their profile.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


KAS-4794 add extra submission status-activity with migration

https://kanselarij.atlassian.net/browse/KAS-4794
extra status change for submissions

PR review with TDN


CIF-1365 - Support product sorting

followup for product sorting to avoid major version increase

Related Issue
CIF-1365
How Has This Been Tested?
Manually.
Screenshots (if appropriate):
Types of changes

[] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[X] All unit tests pass on CircleCi.
[X] I ran all tests locally and they pass.

Closing this PR as agreed with the team.


heal network booting devices out of auth mode

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[x] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Z-Wave JS UI version
8.11.1
ZwaveJS version
?
Describe the bug
Context: Have a lot of nodes connected.  Mostly Inovelli. Most of them are connected with S2Auth.  They work well.
I added a few new hardwired nodes and was experiencing connectivity issues, so I ran a network heal.
It seems that it is booting all my previous nodes to Security: None.
After this heal finishes I plan on updating to latest and retrying the network heal.
This screenshot taken mid-heal.  The highlighted nodes previously popped up with the second sreenshot and are now connected without security.

Each node popped up with this:

To Reproduce
unclear.  I've run heals before and this never happened.
Expected behavior
Nodes previously connected with S2 Auth would remain so.
Additional context
No response

Original heal finished.
Updated to latest (8.23.0) and a second heal is not fixing this issue.

Something is totally foobared.  Since original post I have:

Updated to latest (8.23.0)
Healed - This was slow, kicked all my nodes to security: none and failed halfway through.
A few power cylces later, decided to:
Manually excluded everything. ~40 nodes
hard reset my controller (via the zwave-js-ui)
Re-included 7 hard-wired Inovelli nodes closest to the hub.  All with S2 Auth.
Healed.  This worked.
Tried adding 3 nodes a bit further way (but previously paired fine - for months and months, no issue).  Kept timing out.
thought it might be something with 8.23, so backed down to 8.14.2.  Why 8.14.2? Because it added the new Inovelli VZW31-SN (which I have, but isn't one of the 10 nodes above).
Excluded and added the same 3 nodes from (8) above. Finally got them added.  They identified as the correct device types too.
Tried healing again
see (2) above.  Everything fell off back to Security none.  And they're unuseable.  They look like they're borked in the UI.   There should be more options than Configuration here:

PLease attach logs

Please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

Unfortunately the time for that has come and gone.  I've forcibly excluded everything, deleted my zwave-ui-js configs and started fresh on the latest version.
Maybe this is a Feature Request to somehow halt the healing process mid-way if things start going poorly?  Not sure if that's entirely possible or not, but it would have been great to stop it after I noticed the first few nodes failing in this matter.
But as it went down there was no way to stop it and eventually all the nodes ended up listed as Security:None.  They were functionally unresponsive too as seen in my second screenshot.

@AlCalzone any clue?

There must have been something else going on. Healing just discovers neighbors and re-creates routes.
Unfortunately that something else cannot be debugged without driver logs.

Maybe this is a Feature Request to somehow halt the healing process mid-way if things start going poorly? Not sure if that's entirely possible or not, but it would have been great to stop it after I noticed the first few nodes failing in this matter.


Can't drag files over to a DAW

Description
This is when I drag files like MP3s into FL STUDIO, and this issue only started when I got your app, this may be a bigger issue beyond just DAW's
Steps To Reproduce

Download FL studio (free)
Get an audio file supported by FL Studio
Drag it from the file app to the midi region

Expected behavior
There will be a circle with a line in between or an "Invalid" sign and you will not be able to paste your file there
Files Version
Version: <IP_ADDRESS>
OS Version: 10.0.22000.856
Windows Version
Windows 11 21H2
Relevant Assets/Logs
Irrelevant as replicating the steps can produce the issue at hand

Can you report this issue to FL STUDIO? It might have something to do with their implementation of drop but we can't verify that without access to their code.

Can you report this issue to FL STUDIO? It might have something to do with their implementation of drop but we can't verify that without access to their code.

Yeah I'll report it over there too in the meantime

I have encountered this issue since v<IP_ADDRESS>.

This is known and currently intended for applications that use the "Storage" apis. We're actively working on solving this and it'll be fixed in the next major release.

FWIW this also happens with Ableton Live


velaux error

2022/03/10 03:15:58 [emerg] 1#1: host not found in upstream "apiserver.vela-system:8000" in /etc/nginx/nginx.conf:32
nginx: [emerg] host not found in upstream "apiserver.vela-system:8000" in /etc/nginx/nginx.conf:32

vela addon enable velaux repo=acr.kubevela.net domain=mydomain.doamin.com

k8s v1.20.15

2022/03/10 03:15:58 [emerg] 1#1: host not found in upstream "apiserver.vela-system:8000" in /etc/nginx/nginx.conf:32 nginx: [emerg] host not found in upstream "apiserver.vela-system:8000" in /etc/nginx/nginx.conf:32
vela addon enable velaux repo=acr.kubevela.net domain=mydomain.doamin.com

k8s v1.20.15

It looks that your server can not access addons.kubevela.net. Would you please ping or dig this domain?


Style the selected date in the datepicker

I thought this was implemented but it doesn't look like it is, how can I alter this line:
ng-class="::day.class"

To also add a selected class to the date that is selected? Not sure what the ::day.class does exactly or what condition to apply for the selectedclass.
I'd appreciate some help :)

Override the css class, css is a waterfall structure so if you redeclare new css for the day class it will be applied.

Well ye I know but the day that is currently selected looks no different from the other days that aren't. So how am I supposed to apply the necessary CSS to just the selected day?

there must be something wrong with your setup, because here: http://mobinni.github.io/material-date-picker/example/ you can clearly see a difference.

A selected day:
10
A non-selected day:
11
How is this clearly a difference? I think you're misunderstanding the issue :)

    else if newDate.format(scope.dateFormat) == moment().format(scope.dateFormat)
      day.isToday = true;
      day.isEnabled = true;
      day.class = 'day-item today';

when a day is today, it will get the today class, from the website
noselect ng-binding ng-scope day-item today

But I don't want the today class, because today might not be the date that the user has selected. I want the selected date, i.e. the date that the user clicked.

Ohh now I understand what you mean, yes that was not implemented. After a date is selected, the date picker closes. I did not see the need to implement a current_date class. Best would be to fork and implement it. A pull request would be appreciated.

Ye but if you open it again you basically have no idea what date you've previously selected, so it really is a necessity for a datepicker plugin. I tried to implement it but got some readonly assignment error, I'll try to make some viable solution but would be great if you could create a fix since you know more how it works than me and I'm on a limited development time.

Or you could just read the date in the input field? I would love to implement it, but as I said I'm too short on time :/ many projects

Found a really good solution actually, very performance effective. Will fork when I have some time left over :)


fix labels

Please fix conflicts

@anattzlil just wants to be sure you see you have conflicts. If you need help, please tell me.


Table with autowidth: Rename role "spread" to "stretch"

When the autowidth option is set on a table, the converter recognizes the role spread to mean "100% width" (Issue 519).
This role should be renamed to stretch to be consistent with the User Manual:

If you want each column to have an automatic width, but want the table to span the width of the content area, add the stretch role to the table or set the width attribute to 100%.

We'll continue to support the spread role since Asciidoctor PDF works with Asciidoctor >= 1.5.3.

Thank you!


peer-peer code review  module 2  week5

Hello @HenaryKhuraijam , everything seems very okay great work done so far. However, I would like to draw you to codes in your style.css line 27 and line 43,where  you repeated a semantic element repeated, I think you should consider making your code DRY.

Hello @HenaryKhuraijam  You have a great job building the UI of this project but I have some suggestions if they are implemented can make this project looks better :smile:

You can remove the margin on the recent-score section so that it will be in line with the main section
Kindly remove the text outline border that appears when a user starts to add names and scores


[BUG] Mortgage unit tests fail with RAPIDS shuffle manager

Nightly build failed in the unit tests across multiple Spark versions:
[2024-09-06T08:43:43.694Z] [INFO] --- scalatest-maven-plugin:2.0.2:test (test) @ rapids-4-spark-integration-tests_2.12 ---
[2024-09-06T08:43:44.255Z] Discovery starting.
[2024-09-06T08:43:44.255Z] Discovery completed in 286 milliseconds.
[2024-09-06T08:43:44.255Z] Run starting. Expected test count is: 12
[2024-09-06T08:43:44.512Z] MortgageSparkSuite:
[2024-09-06T08:43:44.772Z] RAPIDS SHUFFLE MANAGER ACTIVE
[2024-09-06T08:44:02.812Z] - extract mortgage data *** FAILED ***
[2024-09-06T08:44:02.812Z]   0 did not equal 10000 (MortgageSparkSuite.scala:65)

GpuSubstring is being invoked during the failing test, so this may be the same root cause as #11437.


Parse Server Shutting Down Frequently

After updating my parse server from 2.1.4 on Azure it seems that there is an issue with up-time. Frequently, my parse server is down. Every time it is down I can temporarily fix it by restarting the server at index.js and then everything works fine, however, after 5 minutes it shuts down again. Any ideas on how this issue could be resolved?

I am experiencing this same issue. For my case, rest calls to the express app in index.js work fine. Even calls to the Cloud Code main.js work IF they don't deal with the mongodb. Whenever a parse function is ran that requires db interaction, my requests will timeout and no data is served. Why is the express app running fine but the database connection lost? What can be done to keep the connection alive or will azure not be able to perform?

There's also a little tidbit to note: I am using parse server 2.1.4 and not this parse server azure library. Should I make the switch to this PS lib since I am using azure? Would it help with the server uptime?

Hey! Sorry that you're having trouble - and thanks for letting us know. We're taking a look right now, chances are that this is totally our fault, given that it sounds a bit like DocumentDB isn't responding quickly enough. I'll keep you posted :memo:!

Yeah no problem! & sounds good, definitely keep us posted.

Quick update: There are a bunch of fixes that should be deployed over the weekend - again, sorry for your trouble.

Thanks we appreciate it!

Where will those fixes be deployed? Is it with the behind-the-scenes Azure service and will be available immediately or will I need to update certain libraries?

Hopefully, it should all happen behind the scenes. Your app should simply stop restarting 👍

Alright thanks! Lastly, the Azure marketplace preconfigured setup for Parse Server comes with Parse's version of PS. Would you recommend sticking with that or switching it out for this parse-server-azure?

It's using the same stuff - this repo is just a "I want all the Azure things" collection of tools. You're running the same code 🏄

Cool cool. Ok! I'll wait for those fixes to be sent out and report back Monday about the status of the DocuDB responses. Thanks again!

No, thank you for reporting!

The db is working pretty smooth as of now thank you for patching it up!

Yup, it's a lot better now. There was occasional timeouts this morning, but that seems to have been removed as the day went on. Thanks!

Yeah, the database was working well for a week or so with no down time. Suddenly today its experiencing downtime again but this time restarting the server doesn't fix it.

My parse server keeps restarting on every invalid credential -_-


add static String.sum(), Float.sum(), and Integer.sum()

Currently there is no good way in the language module to sum() possibly-empty streams of Strings, Floats, or Integers.

Over to you @chochos!

Done, and I added some tests as well.

Excellent, thanks!

Done.


Invoke test_path and older_than_rails_5 methods explicitly in generators

The generators were failing in Rails 5.1 due to the implicit calls to test_path and older_than_rails_5?
This commit fixes the generators by making explicit calls to Versionist.test_path and Versionist.older_than_rails_5?

Thanks for this @archferns . Note that this is broken in general, not just in Rails 5.1.
> rails -v
Rails 4.2.4

> rails generate versionist:new_api_version v2 V2 --header=name:Accept value:"application/vnd.mycompany.com; version=2"Running via Spring preloader in process 16987
       route  api_version(:module => "V2", :header => {:name => "Accept", :value => "application/vnd.mycompany.com; version=2"}) do
  end
       exist  app/controllers/v2
   identical  app/controllers/v2/base_controller.rb
/Users/bploetz/.rvm/gems/ruby-2.2.2@versionist-test/gems/versionist-1.6.0/lib/generators/versionist/new_api_version/new_api_version_generator.rb:67:in `block in add_controller_base_tests': undefined local variable or method `test_path' for #<Versionist::NewApiVersionGenerator:0x007ffc84ecdc30> (NameError)

> rails -v
Rails 5.1.4

ails generate versionist:new_api_version v1 V1 --header=name:Accept value:"application/vnd.mycompany.com; version=1"
Running via Spring preloader in process 48302
       route  api_version(:module => "V1", :header => {:name => "Accept", :value => "application/vnd.mycompany.com; version=1"}) do
  end
      create  app/controllers/v1
      create  app/controllers/v1/base_controller.rb
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/versionist-1.6.0/lib/generators/versionist/new_api_version/new_api_version_generator.rb:67:in `block in add_controller_base_tests': undefined local variable or method `test_path' for #<Versionist::NewApiVersionGenerator:0x007fdafd8097f8> (NameError)

versionist 1.6.1 has been released with this fix.
Cheers.

Thanks, that's great news!


Fix documentation on default TaskExecutor

SimpleAsyncTaskExecutor -> ThreadPoolTaskExecutor
I have figured out that the default TaskExecutor is not SimpleAsyncTaskExecutor but ThreadPoolTaskExecutor by reading references:
SimpleAsyncTaskExecutor fires up only 8 threads - first answer
SimpleAsyncTaskExecutor fires up only 8 threads - second answer
Also, I have checked it out by myself through using demo code (environment: Kotlin 1.7.22, Spring Boot 3.0.5 & 2.5.13). Below are my codes for the test.
@Configuration
@EnableAsync
class SpringAsyncConfig {
}

@Service
class AsyncService(
) {
    @Async
    fun calculate() {
        TimeUnit.SECONDS.sleep(5)
        val currentThread = Thread.currentThread()
        println("@Async annotated method: ${currentThread.threadGroup}, ${currentThread.name}")
    }
}

@RestController
@RequestMapping("/demo")
class AsyncController(
    private val asyncService: AsyncService,
) {
    @GetMapping("/async")
    fun async() {
        asyncService.calculate()
        val currentThread = Thread.currentThread()
        println("Controller method: ${currentThread.threadGroup}, ${currentThread.name}")
    }
}

@Component
@Order(Ordered.HIGHEST_PRECEDENCE)
class ThreadPoolTaskExecutorBeanProcessor(
    @Autowired private val applicationContext: ApplicationContext
) : BeanPostProcessor {
    override fun postProcessBeforeInitialization(bean: Any, beanName: String): Any? {
        return bean
    }

    override fun postProcessAfterInitialization(bean: Any, beanName: String): Any? {
        return if (bean is ThreadPoolTaskExecutor) {
            createProxy(bean)
        } else bean
    }

    private fun createProxy(executor: ThreadPoolTaskExecutor): Any {
        val proxy: ThreadPoolTaskExecutorProxy = ThreadPoolTaskExecutorProxy()
        proxy.corePoolSize = executor.corePoolSize
        proxy.maxPoolSize = executor.maxPoolSize
        proxy.initialize()
        logg.info("create proxy:")
        logg.info("${proxy.corePoolSize}")

        return proxy
    }

    companion object {
        private val logg = LoggerFactory.getLogger(ThreadPoolTaskExecutorBeanProcessor::class.java)
    }
}

class ThreadPoolTaskExecutorProxy : ThreadPoolTaskExecutor()

I have called the api defined on the rest controller.
And the result is below. As you can see below, the thread's name is ThreadPoolTaskExecutorProxy which is a proxy for ThreadPoolTaskExecutor not for SimpleAsyncTaskExecutor. I have also defined a proxy for SimpleAsyncTaskExecutor but I don't think I have to add that code here. It is obvious that the default TaskExecutor is not SimpleAsyncTaskExecutor.
Controller method: java.lang.ThreadGroup[name=main,maxpri=10], http-nio-8080-exec-1
@Async annotated method: java.lang.ThreadGroup[name=main,maxpri=10], ThreadPoolTaskExecutorProxy-1

I am opening a different pull request. The file change in the documentation in this commit is wrong.


Mypy is locked; version solving is difficult

Poetry gives something like this
Because bumble[development,documentation,test] (0.0.198) depends on mypy (1.10.0)
 and no versions of bumble match >0.0.198,<0.0.199, bumble[development,documentation,test] (>=0.0.198,<0.0.199) requires mypy (1.10.0).
So, because your_project depends on both mypy (^1.11.2) and bumble[development,documentation,test] (^0.0.198), version solving failed.

Mypy appears to be locked at 1.10.0.

I'm pretty sure that this should be fine since it's probably caused by pulling in the [dev] optionals.

Yes, no need to cause conflicts over locked dev dependencies, simply require bumble without extras.


Update walkthrough-creating-a-code-snippet.md

The file format for snippets is .snippet it is not necessary to create an XML file and it lead to confusion.

@TerryGLee
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#hold-off

Reviewing.


Kernel dies at boost::numpy::initialize() with Anaconda / non-native python command

Running demo_gaussian.py with gaussian.so using the native python (in my mac the /usr/bin/python2.7 I get the example to work correctly.
However, reinstalling Boost.Numpy with Cmake while modifying
DPYTHON_LIBRARY=/<path_to_anaconda>/libpython2.7.dylib
DPYTHON_EXECUTABLE=/<path_to_anaconda>/python2.7
I get to crash the kernel any time I try to initialise boost::bumpy
However, it is still working fine with /usr/bin/python2.7 command

Please close the issue, it has been fixed since Numpy and Boost are built from the same python libraries version. Sorry for the inconvenience


TridentConfigurator CRD has persistent diff

Describe the bug
I just upgraded from Helm chart version 100.2402.0 to 100.2406.1. After the upgrade, I noticed that Argo CD still had a diff between desired state and live state, and it never goes away:

In the new CRD TridentConfigurator, there is a list additionalPrinterColumns where objects may set the field priority. Some elements in the list has priority: 0 according to the CRD applied by the Helm chart:
https://github.com/NetApp/trident/blob/722e7ef9e58b56fa5815af10c8794b0097ac8b9c/helm/trident-operator/crds/tridentconfigurators.yaml#L17-L42
It seems like they get modified, I'm guessing by the Trident operator, so the priority field gets removed if its value is 0. This causes a constant diff in tools like Argo CD. In the particular case of Argo CD, it is possible to ignore changes to certain object attributes, but I think this diff is probably unintentional and should be fixed.
Environment
Provide accurate information about the environment to help us reproduce the issue.

Trident version: 24.06.1
Trident installation flags used: helm template --include-crds trident -n trident trident/trident-operator --set 'tridentLogFormat=json' --version 100.2406.1 (this is similar to what Argo CD with Kustomize executes in my case)
Container runtime: containerd
Kubernetes version: 1.28.11
Kubernetes orchestrator: Rancher v2.8.5
Kubernetes enabled feature gates: default for RKE2.
OS: RHEL 9.2
NetApp backend types: ONTAP NAS
Other: null

To Reproduce

Install the Helm chart version 100.2406.1
kubectl get crd TridentConfigurator -o yaml and see that priority: 0 is unset.

Expected behavior
There should be no diff after apply.
Additional context
If I sync Argo CD so the priority field gets set, the trident-operator produces this log: trident-operator.log

Seeing the same with my argo deployment of trident-operator. I suspect k8s considers priority 0 as redundant and mutates it out.
Current workaround with ArgoCD is to utilize the ignoreDifferences feature of the Application: (https://argo-cd.readthedocs.io/en/stable/user-guide/diffing/)

We've just bumped into this as well. In case someone finds it useful, here's our change to Application/trident to address this:
--- all.yaml	2024-08-06 10:11:43.216415082 +0200
+++ all.new.yaml	2024-08-06 10:09:10.890141528 +0200
@@ -855,22 +855,29 @@
     helm:
       valueFiles:
         - values.yaml
         - values.eu-dev.yaml

   destination:
     server: "https://kubernetes.default.svc"
     namespace: trident
+  ignoreDifferences:
+    - group: apiextensions.k8s.io
+      jqPathExpressions:
+      - .spec.versions[]? | .additionalPrinterColumns[]? | .priority
+      kind: CustomResourceDefinition
+      name: tridentconfigurators.trident.netapp.io
   syncPolicy:
     automated:
       selfHeal: true
       prune: true
     syncOptions:
       - CreateNamespace=true
+      - RespectIgnoreDifferences=true
     retry:
       limit: 10000000
       backoff:
         # the amount to back off. Default unit is seconds,
         # but could also be a duration (e.g. "2m", "1h")
         duration: 30s
         # a factor to multiply the base duration after each failed retry
         factor: 2


Stop auto-configuring JacksonPubSubMessageConverter

Auto-configuring JacksonPubSubMessage converter based on the
presence of ObjectMappber bean in the application context
has turned out to be too magical and surprising.
This PR ensures that by default only the SimplePubSubMessageConverter
will be used.
Fixes #865, #863.
Supersedes #867 and #871.

@dmitry-s I believe this should also be applied to the 1.0.x branch, but I'm not sure why #863 is not an issue there?

@dmitry-s Never mind, I understand now why the Binder sample works in the 1.0.x branch. It's because by using the converter configured in the PubSubTemplate on the inbound side, it avoids the situation of having a different converter on outbound vs. inbound.
In master, we basically end up with JacksonPubSubConverter outbound, and SimplePubSubConverter inbound. Hence the issue.


Demo CSS

Seems like the Demo CSS is a little borked. Fix anytime soon?
Also - more details on installation?
Thanks!

Hi Taylor,
We're you having the same problem as me? Were you ever able to link the CSS and JS style sheets? I have hooked up the database but can't get the style sheets. Any suggestions?

Hi Robert,
I never installed it because I had low confidence (from the demo) that CSS would work properly and that I would probably would need to do some hacking to fix. Good luck!

Only works on root directory of domain or subdomain, if you want install on subfolder you must change Routes.yml and Resources paths of Config.php
Anyway, what's the problem from the demo? CSS works fine and its a simple bootstrap code, nothing special.


Add Material Design style animations

I want to use MDL on my new website but animations are not available, meaning polymer (or another Material Design framework) will need to be used.

When you say animations, can you go into more detail about what you're looking for? Material Design has delightful detail animations (smaller touches to icons/buttons), transitions between pages (things like what https://github.com/PolymerElements/neon-animation provides) and then animations on components. What do you need?

Delightful detail animations and page transitions

Those animations are highly complex and rather hard to abstract, especially if we want to stay light AND have support for IE10. This is one of the use-cases where Polymer really shines and I’d encourage you to take a look at the Neon elements, which have managed provide these kind of animations.
I don’t see a viable way we can add generic support for these kind of animations in MDL.


Add cert config for custom logging target

Problem:
support ssl config for custom config logging target
Solution:
add ssl fields to custom logging target
Types:
https://github.com/rancher/types/pull/702
Issue:
https://github.com/rancher/rancher/issues/17696

rebased

LGTM

@cjellick I rebase and remove todo code careless commit in last force push, thanks

LGTM


run litmus tests [basic http copymove props] in CI

run those tests of the litmus suite that are passing on the ownCloud webdav endpoints
running them in separate pipelines because of:

run tests in parallel
the tests seem not to clean up after itself in a way reva can cope with it. running the test the second time on the same instance fails

part of #884

CC @phil-davis

the most configurations have been shamelessly stolen from https://github.com/cs3org/reva/tree/master/examples/oc-phoenix

I raised PR #898 to fix a bunch of minor typos. Then people can copy-paste stuff in future without being pinged for typos in reviews ;) or if the code was DRY then we would not be copy-pasting chunks of stuff anyway :)

@butonic or @labkode or @micbar - review please.
If this looks OK, it would be nice to merge it so we can work on adding more test infrastructure without needing to work on top of this branch.

@individual-it rebase this to get up-to-date CI to be really sure nothing breaks?

@labkode what is the practice with this sort of CI test infrastructure stuff?
Are you the one who presses "Merge"? Or is it OK for us to press "Merge"?

@phil-davis I press.


Creating new repository fails occasionally

The issue happens occasionally and I am not able to reproduce it consistently.
Gogs Version: <IP_ADDRESS>0 Beta (Running from source)
git version: 1.9.5.msysgit.1
OS: Windows XP
Error message:
2015/08/27 09:30:58 [...routers/repo/repo.go:131 CreatePost()] [E] CreatePost: initRepository: git clone: fatal: destination path 'C:\WINDOWS\TEMP\203125000' already exists and is not an empty directory.

Like the message above says, the path already exists and it has a .git folder which seems to be a partially initialized git repo.
I am able to successfully create a repo after retrying the process without having to actually do anything on the server.

Thanks your report!
It looks like that somehow the temp dir for init a repository is being used by some other apps.
But should be straightforward to fix it.

Hi there, I've pushed fix to master, please help test!

I seem to face a different issue now, repo creation fails consistently.
Version: <IP_ADDRESS>9 Beta
2015/08/30 19:33:36 [...routers/repo/repo.go:121 CreatePost()] [E] initRepository: initRepoCommit: git push: remote: error: hook declined to update refs/heads/master
To d:\__ALL_DATA__\gogs-repos\tester\rep2.git
 ! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'd:\__ALL_DATA__\gogs-repos\tester\rep2.git'

2015/08/30 19:33:36 [...routers/repo/repo.go:91 handleCreateError()] [E] CreatePost: delete repo directory tester/rep2 failed(2): remove d:\__ALL_DATA__\gogs-repos\tester\rep2.git\objects\66\1ec2002ed247054eab6defcd68d50903cbdb47: Access is denied.
2015/08/30 19:34:17 [...routers/user/home.go:319 Profile()] [E] GetUserByName: user does not exist: [uid: 0, name: repo]
2015/08/30 19:36:29 [...routers/repo/repo.go:121 CreatePost()] [E] initRepository: initRepoCommit: git push: remote: error: hook declined to update refs/heads/master
To d:\__ALL_DATA__\gogs-repos\tester\rep3.git
 ! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'd:\__ALL_DATA__\gogs-repos\tester\rep3.git'

2015/08/30 19:36:29 [...routers/repo/repo.go:91 handleCreateError()] [E] CreatePost: delete repo directory tester/rep3 failed(2): remove d:\__ALL_DATA__\gogs-repos\tester\rep3.git\objects\09\98641d21b1dc069aebac78f8ee8f618284ed4a: Access is denied.

On more testing, the above issue seems to be a caused because of running the server as a service with Local System Account. Running it as a service with Administrator or running it in console didn't have any issues.
However I have a couple of concerns:
(1) The logic to construct temp dirname still has possibilities of duplicates

tmpDir := filepath.Join(os.TempDir(), "gogs", repo.Name, com.ToStr(time.Now().Nanosecond()))

Time.Nanosecond document says:

Nanoseconds returns the duration as an integer nanosecond count.

and this is what I got on my machine:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\gogs\repo6\812500000

(2) The temp directory is not deleted.

The logic to construct temp dirname still has possibilities of duplicates

It is certainly possible in very edge case, but is low enough that two person create exactly same repository at exactly same nano second.

The temp directory is not deleted.

Gogs does execute the delete commands, but as your error shows that Access is denied. So... I don't know how to help on this one.

The logic to construct temp dirname still has possibilities of duplicates

It is certainly possible in very edge case, but is low enough that two person create exactly same repository at exactly same nano second.

On other OS' I agree, but on XP it looks to be providing only millisecond resolution.

The temp directory is not deleted.

Gogs does execute the delete commands, but as your error shows that Access is denied. So... I don't know how to help on this one.

The access issue went away after I changed the service to run as Administrator however the issue with delete is that a directory hierarchy like tmp\gogs\repo6\812500000 is created but after deleting tmp\gogs\repo6 still stays. Instead I would suggest to create a temp directory like tmp\gogs-repo6-812500000.

On other OS' I agree, but on XP it looks to be providing only millisecond resolution.

Hmm... this is... I don't know what to do yet.

Instead I would suggest to create a temp directory like tmp\gogs-repo6-812500000.

OK, it's on develop now.

Tested it in Version: <IP_ADDRESS>3 Beta and it works great.
This issue can now be closed - thanks.

@vijairaj thanks your confirmation!


Remove custom nodes from Button+ flow

Remove custom nodes from Button+ flow to avoid confusion, but share anyways for inspiration

By means of splitting the JSN in two files: The core flow and the 'user configuration' part as a template with some examples.
Would be good idea to supply one with HA integration and one 'plain' node-red.
Basic thermostat and display temp iof internal temp sensor could be good examples


Docs: Revised CLI and configuration settings docs

Moved some documentation for the bigchaindb command (and sub-commands) from the "Configuring a BigchainDB Node" page to the page about the bigchaindb command.
Renamed the "Configuring a BigchainDB Node" page to "Node Configuration Settings". That page is now mostly a list of configuration settings, in logical groupings. Each one has an explanation, default values, examples, and how to set it via environment variables or a local config file.
The page "Node Configuration Settings" opens with a concise explanation of how each setting's value is determined.
Removed some complex examples in favor of a bunch of small examples and snippets.

@vrde I would especially appreciate your comments and suggestions on this PR. It's not urgent though.

[Current coverage][cc-pull] is 88.30%

Merging [#403][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #403   diff @@
==========================================
  Files            18         18
  Lines          1266       1266
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1118       1118
  Misses          148        148
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [7d3e74f...c54f3cd][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bigchaindb/bigchaindb/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bigchaindb/bigchaindb/compare/7d3e74f61337727a2aeeb433aea173c493cde126...c54f3cdac1c1b890c2fa1d73951d29469fe49b72
[cc-pull]: https://codecov.io/gh/bigchaindb/bigchaindb/pull/403?src=pr

I do like a lot the changes to the configuration settings docs but I still think that we should have a subsection with all the env variables like we add before for reference

Okay, I will add a list of all environment variables near the top.

:+1:


RT-486: Refactor SA.supporting_organisations field as charField

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@1135ef1). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #221   +/-   ##
==========================================
  Coverage           ?   97.37%
==========================================
  Files              ?       71
  Lines              ?     4464
  Branches           ?        0
==========================================
  Hits               ?     4347
  Misses             ?      117
  Partials           ?        0

Continue to review full report at Codecov.

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


Snowcrashdao

hi, Do you know that Snowcrashdao is still under development.
Looking forward to your reply
thanks

hi

hello

Hello
Yes, I know
On Wed, Sep 27, 2023, 3:28 AM luckyinghai @.***> wrote:

hello
—
Reply to this email directly, view it on GitHub
https://github.com/Ayomidegideon123/alx-files_manager/issues/1#issuecomment-1736573056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2O2AN6XKIHKORX55TD3353X4OFNPANCNFSM6AAAAAA47RCACY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you for your reply.
Is the project still under development?

It's been almost two years without any news

Can I contact you through email

Yes, of course you can.
On Wed, Sep 27, 2023, 8:21 AM luckyinghai @.***> wrote:

Can I contact you through email
—
Reply to this email directly, view it on GitHub
https://github.com/Ayomidegideon123/alx-files_manager/issues/1#issuecomment-1736842377,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2O2AN67LNFGIJ463JITSSDX4PHV7ANCNFSM6AAAAAA47RCACY
.
You are receiving this because you commented.Message ID:
@.***>

so, What is your email address?
thanks

@.***
On Thu, Sep 28, 2023, 6:51 AM luckyinghai @.***> wrote:

so, What is your email address?
thanks
—
Reply to this email directly, view it on GitHub
https://github.com/Ayomidegideon123/alx-files_manager/issues/1#issuecomment-1738514412,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2O2ANYG5A5Q5F3RRERUDQ3X4UF5PANCNFSM6AAAAAA47RCACY
.
You are receiving this because you commented.Message ID:
@.***>

@.***
can not see

hi can you contact me
email<EMAIL_ADDRESS>


Tested with Foundry VTT v0.7.7 and works

I've updated to Foundry VTT v0.7.7 and had no issues with encounter builder. Here's PR to bump the compatible version number. This closes #5.

Closing out old pull-requests. This one seems unlikely to get merged, and is now out of date with Foundry's major releases even if it did get merged.


[Suggestion] Option to disable shield with specific items

I am currently using kitbattle advanced, this uses mushroom soup to recover life, the thing is that this soup is drunk instantly, and if you quickly change your sword for a soup, you can not drink it until the shield disappears, so I would like it to work as with the potions (that the shield did not move to protect)

You can try adding the soup to the noBlockingItems: [] list under the sword-blocking header in the config.yml.

https://gyazo.com/1861252141dad8f92e26ed1875a0d2ce
With this gif maybe you understand better what I mean
https://i.gyazo.com/25a22938d4a1dec400c02102cf975d4b.png

In theory, one way to handle this would be to automatically cancel/remove the shield when you switched hotbar slots. Perhaps this should be moved to the todo list.

Possibly patched in 928b7ab9dff6b7378c376f5b6442fe9caa96367b, but I have yet to test the build. Since I am quite busy, I will most likely not have time to test this any time soon. However, if you would like to test it, here is a compiled JAR with the patch:
OldCombatMechanics-hotbar-patch-beta.zip
(GitHub required that the file be zipped first, but it just contains a JAR file)
Please let me know how it works out for you!
P.S. don't forget to remove the current OldCombatMechanics JAR file temporarily while testing the patched version :)

Now it works correctly, thank you very much.


tree - component not showing all children and not showing additional nodes

Hi
"angular-tree-component": "^7.0.2",
FF 59.0.1 (64-bit)
Chrome Version 65.0.3325.181 (Officiel version) (64-bit)
I am trying to show nodes and add further nodes from a service.
So initially I assign values to this.nodes - these do show up except for the children - 'child1' never shows up.
Any ideas what I do wrong with this simple code is appreciated?
Furthermore I try to add a node in the tree ('another node a') and this node never shows up either.
Thanks in advance
`import { Component, OnInit, ViewChild } from '@angular/core';
import { TreeComponent, TreeModel, TreeNode } from 'angular-tree-component';
// Bygget med https://angular2-tree.readme.io/docs
// usage:
@Component({
selector: 'treeapp',
template: '<tree-root #tree [nodes]="nodes" [options]="options">'
})
export class TreeAppComponent {
options = {};
nodes: any[];
@ViewChild(TreeComponent) private tree: TreeComponent;
constructor() {
this.nodes = [
{
id: 1,
name: 'root1',
children: [{ id: 2, name: 'child1' }, { id: 3, name: 'child2' }]
},
{
id: 4,
name: 'root2',
children: [
{ id: 5, name: 'child2.1' },
{
id: 6,
name: 'child2.2',
children: [{ id: 7, name: 'subsub' }]
}
]
}
];
this.nodes.push({ name: 'another node b', children: [{ name: 'child21' }] });
setTimeout(() => {
  this.nodes.push({ name: 'another node a', children: [{ name: 'child21' }] });
  console.log('nodes', this.nodes);
  this.tree.treeModel.update();
  this.tree.sizeChanged();
}, 3);

}
}
`

Hi,
Please reproduce in the plunkr from the issue template and reopen the issue.
Thanks


Bug Report: OptionsMenu:72

source/OptionsMenu.hx:72: characters 3-4 : Expected , or )
This is on the newest version of Kade. The code looks fine but it says this.

bru follow the line it easy


persistant notificatio

Dont know if this is a bug or what, but when i use this to create a persitant notification node red chrash when i dismiss it it hass.io
[{"id":"2a9636ce.c0ecba","type":"api-call-service","z":"6130676a.e4f1d8","name":"","server":"e893ec39.f42e","service_domain":"persistent_notification","service":"create","data":"{ "title": "test","message": "this is test" }","mergecontext":"","x":475,"y":501,"wires":[[]]},{"id":"e893ec39.f42e","type":"server","z":"","name":"Home Assistant","url":"removed","pass":"removed"}]

What do you see in the addon logs?


Add security support to the system

Login to see the app
Role for different domain object / operation combination
Data level visit control(better to have).

Close this issue by now and open another for task "Role for different domain object / operation combination"


Change dependency from node-uuid to uuid (project name changed).

https://github.com/tgriesser/knex/pull/1792


[HOLD #49539][Search v2.5] Remove special handling of policyID after navigation is merged

We need to remove this code once this navigation PR is merged.
@Kicu

Thanks for the issue.
Some extra context:
PolicyID (aka workspaceID) has a lot of special handling, as it comes from URLs but is also saved to workspaceContext. To avoid having multiple ways of accessing it, we try to access it from URL/route params whenever possible, and handle it on navigation actions.
In this specific case instead of overwriting workspace id, we can simply check if there is existing id during navigation and handle it.
That is already working in #49539

also please assign me, so I won't forget about this 🙏


apply a cache busting mechanism to vdc dashboard .js files

Description
When a user update the vdc dashboard, some js changes may not get reflected in his browser and cause the dashboard to malfunction.
The user had to manually empty the browser cache or hard reload the page, but this could be not obvious for a regular user and could cause some confusion.

Implementation
I'm not a js expert, but I know there is already few approaches to implement some mechanism to force the browser to invalidate its caches and reload it without user interaction Which called Cache Busting.
This will definitely improve the user experience.

edited vue file, updated dashboard, works as expected


Support for management APIs

Any chance you could expand your library to include support for the management APIs (such as personal, miner, etc.)? I see you support some personal APIs  but for example the "personal_newAccount" seem to be missing. Thanks a lot for providing this, it's very useful.

Don't see this coming soon. Currently only JsonRPC is on the roadmap.

I'm not sure I understand. These APIs can be accessed through JsonRPC, therefore my humble request.

You said it "can be accessed..." Please read http://ethereum.stackexchange.com/a/3201/852
I don't see personal API implementation even on the horizon. But you're very welcome to contribute.
Have a look at eth_sign in combination with a TX signer like Metamask. You may archive what I guess you intend to archive. At first I thought that I would need the personal API too.


Update ISA strings from Xbitmanip to XZb*

This allows us to model stuff more closely. This depends on Spike
version ibex-cosim-v0.2 (which is rebased onto a master branch commit
supporting these more specific ISA strings).

@hcallahan-lowrisc: Some of what I said this morning might make a bit more sense when you've seen this PR: I'd completely forgotten that it wasn't merged!


Generated routes are relative to project root

Hey there, trying to use this project but the routes seem to be generated relative to the root directory instead of the app directory. Not sure if I'm doing something wrongly here.
export const routes = {
  "src/app/[locale]/auth/password-reset": {
    "path": "src/app/[locale]/auth/password-reset",
    "params": {
      "locale": ""
    },
    "isDynamic": true
  },
  "src/app/[locale]/auth/password-reset-sent": {
    "path": "src/app/[locale]/auth/password-reset-sent",
    "params": {
      "locale": ""
    },
    "isDynamic": true
  },
  "src/app/[locale]/auth/unverified": {
    "path": "src/app/[locale]/auth/unverified",
    "params": {
      "locale": ""
    },
    "isDynamic": true
  },
  ...

My director structure is
src
  app
    [locale]
      foo
      bar
package.json
next.config.js

Hey @yangshun ! Have you tried using the second argument of the plugin in the next.config.js apparently there is an issue in the docs because you have to do something like this
import withRoutes from "@triyanox/next-routes";
import { cwd } from "process";

/** @type {import("next").NextConfig} */
const config = withRoutes(
  {},
  {
    appDir: `${cwd()}/src/app`,
  },
);

You can let me know if this worked for you I will fix the docs too thank you for opening this issue I will leave it open for now let me know if the fix worked for you !

Hey @yangshun I have published a new version with updated docs for simpler use the previous one didn't include an indication that all the paths are relative to the root directory.
Thank you for opening this issue much appreciated !


whatsapp share not working when using 'share' instance method

on sharing using social share plugin using share method, share via whatsapp is showing failed message, but share via all others are working.
My code is as give below,
this.platform.ready().then(() => {
SocialSharing.share("title", "test_subject", "test_subject", "link");
});

try this
SocialSharing.share("title", null, null, "link");
instead of
SocialSharing.share("title", "test_subject", "test_subject", "link");


Wrong or incomplete error message when using non-bors git commit as --start

$ cargo-bisect-rustc --preserve --start=e67f09ac799e4a6e4e90147d62c94c9ddcc94197 --end=7aa361390867181d225a7775340f50e8162e16a2
bisecting ci builds
starting at e67f09ac799e4a6e4e90147d62c94c9ddcc94197, ending at 7aa361390867181d225a7775340f50e8162e16a2
opening existing repository at "rust.git"
Found origin remote under name `origin`
refreshing repository at "rust.git"
remote: Enumerating objects: 209, done.
remote: Counting objects: 100% (180/180), done.
remote: Compressing objects: 100% (53/53), done.
remote: Total 209 (delta 148), reused 140 (delta 127), pack-reused 29
Receiving objects: 100% (209/209), 165.35 KiB | 2.71 MiB/s, done.
Resolving deltas: 100% (149/149), completed with 88 local objects.
From https://github.com/rust-lang/rust
   7aa36139086..7feb003882e  master     -> origin/master
fetching (via local git) commits from e67f09ac799e4a6e4e90147d62c94c9ddcc94197 to 7aa361390867181d225a7775340f50e8162e16a2
opening existing repository at "rust.git"
Found origin remote under name `origin`
refreshing repository at "rust.git"
looking up first commit
looking up second commit
checking that commits are by bors and thus have ci artifacts...
ERROR: failed during attempt to create/access local git repository

It should say what problem it caused the bisector to exit: a non-bors commit was specified as start.
(Or it could guess some appropriate bors commit to use in place of the one I specified.)
Version
cargo-bisect-rustc --version
cargo-bisect-rustc 0.6.4

on mac

I just spent too long debugging the same exact issue. The issue is in main they're Display printing the error, which shows the minimal amount of info instead of pretty-printing or Debug printing which shows the complete cause.

I think that between #103 and #237, this is resolved.
However, there is an issue with github access that causes it to panic. I have opened #318 to fix that.


Point is not visible when we zoom near the surface

Hi,
We used your example Geodata Basic (https://github.com/Melown/vts-browser-js/wiki/Examples) in order to display a point on the right lat, lon, altitude.
Our try is on: https://jsfiddle.net/alamR/jjynbpoL/13/
The problem is that the point is not visible when we zoom near the surface.
The real altitude of the point is 333m.
In our code we add this point:
geodata.addPoint([14.3836691, 50.0485568, 333],
'fix', { 'name' : 'Nice place'  }, 'some-place');
But it is not visible (when we zoom near surface)! When we change the altitude around 380m then we can see it.
Have we missed something?
Thank you in advance!

There are two kinds of heights. One which is over ellipsoid and one which over geoid. In this case you are using map where are coordinates provided in navigational spacial system which has heights over ellipsoid. You can take advantage that current map has public spacial system with heights over geoid and convert height by following function:
var newCoords = map.convertCoordsFromPublicToNav([14.3836691, 50.0485568, 333]);
I have modified your example which now gives more accurate results. Final result is also depended on the precision of the point coordinates and on the precision of the terrain geometry:
https://jsfiddle.net/mj26qkrw/
More about spatial coordinate systems in VTS can be found there:
http://vtsdocs.melown.com/en/latest/reference/concepts.html?highlight=reference

Thank you very much David!
Indeed this method solves the problem of the height mismatch.
However if you run this method again with the same arguments then the result of the conversion is different for the height!?
We have created this demo:
https://jsfiddle.net/alamR/9xr5tx63/22/
You could check the console and notice the different values of height every time you click the custom button 'Clickme'.

Sorry, I forgot that function for conversion has second parameter which defines whether height is 'fix' or 'float'. Default mode is 'float' and  height is computed from currently available data.  Usually available data are not best match so more detailed data are loaded on the background. That is reason different values. Fixed function call:
var newCoords = map.convertCoordsFromPublicToNav([14.3836691, 50.0485568, 333], 'fix');
Fixed demos:
https://jsfiddle.net/5n97gm3y/
https://jsfiddle.net/mj26qkrw/12/

Thank you so much David!!
Now it is working as expected 👍 👍


Bad format show style

Problem 1:
Code text isnt on one line. (with options "singleLine: true" too).
Missing effect as "white-space: pre;".
Problem 2:
And problem geting original style from highlight.min.js (font size and font-family).
Version 2.6.0
Do you can fixed, please?
Edit: Problem 1 has been fixed after add CSS this:
.hljs-ln .hljs-ln-line {
     white-space: pre;
}

Hi @truefriend-cz thanks for the feedback!
Could you provide more info (used snippet or screenshot) about your problems?

I’m closing this issue because it has been inactive for a few months. This probably means that it is not reproducible or it has been fixed in a newer version.
Please reopen if you still encounter this issue with the latest stable version. You can also contribute directly by providing a patch. :)
Thank you!


added filter for redirecting specific folders

Coverage decreased (-0.5%) to 56.785% when pulling 4f5ef19d7c3c20e798fd7af16965099d97d134fe on cseeger-epages:feature/issue-42-folder-filter into d338c4f49450b7ea62821b97e8424a043d2b971b on rodcorsi:master.

Coverage decreased (-0.5%) to 56.785% when pulling 4f5ef19d7c3c20e798fd7af16965099d97d134fe on cseeger-epages:feature/issue-42-folder-filter into d338c4f49450b7ea62821b97e8424a043d2b971b on rodcorsi:master.

Thank you @cseeger-epages! I'll make some tests

seems to work im running an instance productive using my fork to compile it, also added a systemd example on https://github.com/rodcorsi/mattermail/issues/65.
I tested the combination of Folder + Subject which worked for me, did not test any combinations with From configuration field yet but since its the same implementation it should work also.

Using a config with no Filter.
{
  "Directory": "./data/",
  "Profiles": [
    {
      "Name": "Orcamento",
      "Channels": ["orcamentos"],
      "MailTemplate":
        "\u003e:incoming_envelope: _De:_ **{{.From}}**\n_{{.Subject}}_\n\n{{.Message}}",
      "LinesToPreview": 10,
      "Email": {
        "ImapServer": "xxx:143",
        "Username": "xx@xxx",
        "Password": "xxx"
      },
      "Mattermost": {
        "Server": "http://xxx",
        "Team": "xxx",
        "User"<EMAIL_ADDRESS>        "Password": "xxxx",
        "UseAPIv3": false
      }
    }
  ]
}

Produces:
INFO Orcamento  09:48:26 Using Mattermost Api Version 4
DEBG Orcamento  09:48:26 Debug mode on
INFO Orcamento  09:48:26 Checking new emails
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x5690ee]

goroutine 19 [running]:
github.com/rodcorsi/mattermail/model.(*Filter).ListFolder(0x0, 0x6, 0xc04203e780, 0xc042094280)
        C:/GoPath/src/github.com/rodcorsi/mattermail/model/filter.go:98 +0x3e
github.com/rodcorsi/mattermail/mmail.(*MatterMail).checkAndWait(0xc04204ab80, 0xbdbfa8, 0xc04204aac0)
        C:/GoPath/src/github.com/rodcorsi/mattermail/mmail/mattermail.go:86 +0x4e
github.com/rodcorsi/mattermail/mmail.(*MatterMail).Listen(0xc04204ab80)
        C:/GoPath/src/github.com/rodcorsi/mattermail/mmail/mattermail.go:75 +0x13f
github.com/rodcorsi/mattermail/mmail.Start.func1(0xc04218f570, 0xc042190cc0, 0x85df01, 0xc04204f0b0)
        C:/GoPath/src/github.com/rodcorsi/mattermail/mmail/app.go:30 +0x5f
created by github.com/rodcorsi/mattermail/mmail.Start
        C:/GoPath/src/github.com/rodcorsi/mattermail/mmail/app.go:29 +0x104
exit status 2

The cache file is not created for the other folders, in this case, Mattermail will send the same email every time it is restarted.
You need to change UIDCacheFile to accept multiple folders.

Ah ok ill take a look at it

looks better now can you take a look ?

Thks I'll make some test 👍

I make some test and work normally to me. I change to branch release-4.1 because I need to terminate 4.0 beta issues

Great ! thx for your help @rodcorsi for testing the stuff.


DP-1.2: Fixing validation of non strict priority scheduler case for Juniper

DP-1.2: Fixing validation of non strict priority scheduler case for Juniper
Fixing scheduler priority state validation for non strict schedulers as per vendor support

Pull Request Functional Test Report for #3537 / 20bafa19a80bbf088c1c2b26a52ae2a987ca1a8f
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

DP-1.2: QoS policy feature config

Cisco 8000E

DP-1.2: QoS policy feature config

Cisco XRd

DP-1.2: QoS policy feature config

Juniper ncPTX

DP-1.2: QoS policy feature config

Nokia SR Linux

DP-1.2: QoS policy feature config

Openconfig Lemming

DP-1.2: QoS policy feature config

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

DP-1.2: QoS policy feature config

Cisco 8808

DP-1.2: QoS policy feature config

Juniper PTX10008

DP-1.2: QoS policy feature config

Nokia 7250 IXR-10e

DP-1.2: QoS policy feature config

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.268%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
1983

Relevant Lines:
3588

💛  - Coveralls

Hi @Swetha-haridasula,
Looks like the PR needs one more approval. Please check.
thanks!


Build: move Jasmine matchers and corresponding typings out of /src

Or find other ways of making sure that those are not deployed to npm. I'm not sure what we do for tests but should verify that those are not going to npm.

We can easily exclude with an .npmignore file.


Do not show error trace to the user

The bot currently is posting the full error context into a github comment. As an example see here: https://github.com/paritytech/substrate/pull/12723#issuecomment-1321700543
It should only post:
@bkchr ERROR: Error: Contributor did not properly post their account address.

Make sure the pull request description has: "{network} address: {address}".

@parutger was the fix for this issue already deployed?
Because I just got it again: https://github.com/paritytech/substrate/pull/12833#issuecomment-1435262834

@bkchr Thanks for the feedback, It wasn't deployed to production yet.


Updating an ID's volume

Hello!
I'm using this to back broad phase collision for a game I'm writing with Bevy. And have entities that frequently move (~30TPS).
I noticed there isn't a update() method, Should I just be remove()ing and then insert()ing every time an index's volume has shifted? Thanks!

I noticed there isn't a update() method, Should I just be remove()ing and then insert()ing every time an index's volume has shifted?

Yes. You remove and re-add.
We could technically implement an update method, but not worth it IMO, as it is kind of complicated especially if we want to keep the tree balanced, and remove + add work just fine. However, I should probably clarify that in the documentation.
With Bevy, what I find the best is to have a system that removes all entities that have moved, and then another system that re-add all of them (instead of add/remove per entity). That should should keep the bvh reasonably balanced without the need for a dedicated balance method nor any complicated logic.

Hm, I worry that splitting removing/adding entities into the BVH could introduce a state where another system gets ahold of an entity that lacks BVH backing because we're after the removal but before the add system.
Thanks for the info though!
As a random aside, have you ever considered collision masking? Or should that be carried out by narrow phase?

Hm, I worry that splitting removing/adding entities into the BVH could introduce a state where another system gets ahold of an entity that lacks BVH backing because we're after the removal but before the add system. So I'll probably do it in a single system for now.

Good point indeed! My point was mostly to remove all then add all (instead of add/remove on each). But a single system with two loops is probably better indeed, I agree.

As a random aside, have you ever considered collision layer masking? Or should that be carried out by narrow phase?

Currently, I am personally checking that between the broad and narrow phases. Sometimes, I also create multiple broad phase tracking structures to segregate entities that can never collide.
But yes, layer masking may be a legitimate feature for this project. I'd have to think more about it and come up with an idea for the interface. However, I don't know if I'll find time for that any time soon, as my current project is using a grid for the broad phase, not a bvh. But I am open to contributions :-)


[vcpkg manifest] Manifest Implementation

This is going to be quite large! Based on the RFC in #11203

Port-Version ? call a spade a spade? Patch-Version: 4

Major.Minor.Patch[-Suffix]

@voskrese that's not what this is, port-version is the version of the port, separate from the version of the package; i.e., LLVM might be at version 10.0.1, but we've had 3 updates to the port, so this is the 3rd port which is for LLVM 10.0.1.

NuGet 4.3.0+ supports SemVer 2.0.0, which supports pre-release numbers with dot notation, as in 1.0.1-build.23

Pre-release versions
Technically speaking, package creators can use any string as a suffix to denote a pre-release version, as NuGet treats any such version as pre-release and makes no other interpretation. That is, NuGet displays the full version string in whatever UI is involved, leaving any interpretation of the suffix's meaning to the consumer.
That said, package developers generally follow recognized naming conventions:
-alpha: Alpha release, typically used for work-in-progress and experimentation.
-beta: Beta release, typically one that is feature complete for the next planned release, but may contain known bugs.
-rc: Release candidate, typically a release that's potentially final (stable) unless significant bugs emerge.

Any of the package's dependency version ranges has a minimum or maximum version that is SemVer v2.0.0 compliant but not SemVer v1.0.0 compliant, defined above; for example, [1.0.0-alpha.1, ).

ok
Pre-release: 4
LLVM might be at version 10.0.1-alpha.4 ?

would like to follow the standards so that it is easier to import / export packages from repositories

I'm mostly 'request changes' over the

canonical call in vcpkgpaths.cpp since I think that's a bug
the 'doing lots of work in main'
missing tests (It's hard to evaluate correctness of parsers in code reviews, so I kinda lean on the presence of tests to indicate correctness)

I'd really like to see us not add another global but would not block over that.

I've fuzzed for >3M execs the new platform expression parser. There were two crashes, both stack overflow.

Lots of merges which broke my PR :P


Add mime type inference when uploaded images are missing mime type

#9 added error checking for file type, but did so using mime type. This means that uploads with missing mime type (mime type = None) will fail even if the image is valid. This was discovered and addressed by the web app in https://github.com/IBM/MAX-Image-Caption-Generator-Web-App/pull/39
As per discussion in #9 we should look into adding the mime type fix in the model as well. This can either be done using the same method as the web app or by using the more robust python magic library.

@ajbozarth should this be closed via #9?

No this is a follow up to #9 but as referenced there we can close this as "will not fix" if we would rather not spend the dev time. This is a minor edge case that can be worked around client side when encountered (like we did in the web app).

Yes, I agree. A properly written web application should send the correct mimetype instead of compromising the stability of this model.