3.3.7+ broken local hosting

[ ] This is a question about using the theme.
[x] I believe this to be a bug with the theme --- not Jekyll, GitHub Pages or one of the bundled plugins.
[ ] This is a feature request.
[ ] I have updated all gems with bundle update.
[ ] I have tested locally with bundle exec jekyll build.

Environment informations

Minimal Mistakes version: 3.3.7+
github-pages or jekyll gem version: github-pages 98
Operating system: OSX

Expected behavior
When making site.url empty, the links should be relative to localhost:4000.

Steps to reproduce the behavior

It looks like ca9ff32 changed this functionality, and perhaps I'm just missing something, but when running bundle install and then bundle exec jekyll serve it now makes all the links be relative to the github repo rather than localhost. How can I get back to running off localhost?

Easy solution is don't leave it blank and use url: "http://localhost" when testing locally. The better solution is to create a dev config, something like _config.dev.yml and add any dev environment overrides. In this case you would just need a single line:
url: "http://localhost:4000"

Then when you run jekyll locally you do:
bundle exec jekyll serve --config _config,yml,_confg.dev.yml

And all will be well with the world.


AMBARI-23184. Metrics Collector Install failed

Caught an exception while executing custom service command: <class 'ambari_agent.AgentException.AgentException'>: 'Script /var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_collector.py does not exist'; 'Script /var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_collector.py does not exist'
WARNING 2018-03-02 12:21:35,414 FileCache.py:183 - Error occurred during cache update. Error tolerate setting is set to true, so ignoring this error and continuing with current cache. Error details: ('Can not invalidate cache directory {0}: {1}', u'/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package', "[Errno 39] Directory not empty: '/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package'")
shutil.rmtree fails with the following: "Directory not empty", however it should empty all the dirs.
After some research I found out this can be the reason:

shutil.rmtree found A is a non-empty directory
shutil.rmtree try to remove all contents recursively
shutil.rmtree has finished remote all contents recursively
another process produces some file / directory in A
shutil try to remove A itself and failed
Another process can be possibly a status_commands executor which created *.pyc file and caused this.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1059/
Test FAILed.
Test FAILured.

The test failure here is not related. Seems like something during maven execution hangs. Ran tests manually and verified it's green.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1063/
Test FAILed.
Test FAILured.


Fix CI

Fix warnings clippy found after it updated
Fix version of wasm-bindgen-test and wasm-bindgen -- it seems that the newest minor versions of these are incompatible; we can investigate in another issue or wait for it to fix itself
For some reason that version of wasm-bindgen-test freaks out if a test returns Result

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT license.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.17%. Comparing base (cb25022) to head (1e456d0).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #223      +/-   ##
==========================================
- Coverage   90.17%   90.17%   -0.01%
==========================================
  Files         176      176
  Lines       31558    31571      +13
==========================================
+ Hits        28458    28469      +11
- Misses       3100     3102       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Remove: InfiniteRed.Reactotron.Pre-release version <IP_ADDRESS>0

The stable version has been released and the pre-release versions can be removed

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/infinitered/reactotron/releases/download/reactotron-app%403.0.0-alpha.17/Reactotron.3.0.0-alpha.17.msi
Response status code does not indicate success: 401 (Unauthorized).
(Automated message - build 656)


fix publishing to NPM

Coverage remained the same at 79.412% when pulling 8cbb184396edad9c4f001d165b9306d4e72b8cf1 on fix/fix-publish into 95beca1d8076f2f034a41ada2ceab5db884232f8 on master.


Blur outline on interior

Is your feature request related to a problem?
The OutlineEffect with blur: true smooths the outline on the exterior of the shape, but leaves the interior with aliasing. Would it be possible to blur the interior as well?
Describe the solution you'd like

In the image above, I would like a "smooth outline" all around the rock, with no aliasing.
Describe alternatives you've considered
Adding an anti-alias (e.g. SMAA) effect is something I'm trying not to do for the sake of speed.

Added an experimental multisampling setting to OutlineEffect in<EMAIL_ADDRESS>This can be used as a ctor parameter or via a property:
const effect = new OutlineEffect(scene, camera, {
	multisampling: Math.min(4, renderer.capabilities.maxSamples),
	...
});

effect.multisampling = Math.min(4, renderer.capabilities.maxSamples);

Requires three ≥ r138.


UNMET PEER DEPENDENCY Error occurred When I have use another module in my project

I have checked UNMET PEER DEPENDENCY related all issues and have tried as well but not found this issue.
UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>I have installed npm install -g @angular/cli

This is no issue regarding this repository.
You should try to update all your packages to more recent versions in your package.json. You can run npm outdated for a better overview to this. Then remove your node_modules folder and run npm install again.

@dahaupt I have tried to remove node_modules folder and run npm install but I can't found that issue.

@smartHasmukh Try to run npm update in the directory of your package.json file or update your dependencies manually. As said, if there are red entries in npm outdated you will get the problems I can see in your screenshots.

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


Error message with EGI token expiration: ERRORS.SERVICE-ERROR

Error message appears after coming back to Dashboard and EGI token has expired.

Already solved


awesome-list

Just an idea, maybe you want to make align your list with the many awesome-lists out there
https://github.com/traversaro/awesome-fmi
https://github.com/sindresorhus/awesome
It seems awesome-modelica is not yet taken...

hmmmmm.... not a bad idea...

alrighty. i am going to rename this repo now


Add auto collapse feature for all memos issue #1463

I added a auto collapse switch in preference setting,

By switching off, all memos will not collapse. If switching on, all memos that exceed certain words limit will collapse as usual.

Thanks for your reply! I have sorted out the style check :)


RequestHandler.reply's parameter data converted to function

Pull Request Template
Your checklist for this pull request
Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a feature/bugfix branch (right side). Don't request your main or develop!
[x] Make sure you are making a pull request against the develop branch (left side). Also, you should start your branch off our develop.
[x] Make sure that you add reviewers, assignees, labels, projects, milestones and linkes issues to the pull request as you see fit.
[x] Check the commit's or even all commits' message styles to match our requested structure.
[x] Check your code additions will fail neither code linting checks nor unit test.

Tip: Delete everything but the following section that contains the description of the pull request.

Description
For mock http request, not just for unit test. so RequestHandler.reply's parameter data should be function.
so when the real RequestOptions pass in ,the return data can be code with logic.
Please describe your pull request.
Thank you!

Thanks @wangdengwu for contributing and helping http-mock-adapter.
Looks good, but it seems some CI/CD tools is failing, including linter. Please fix that and we will re-review then.
@theiskaa Btw, have you a chance to test it on your device/simulator?

Thanks @wangdengwu for contributing and helping http-mock-adapter.
Looks good, but it seems some CI/CD tools is failing, including linter. Please fix that and we will re-review then.
@theiskaa Btw, have you a chance to test it on your device/simulator?

I'll do it now ... Sorry, I was confused, my fault :/

got it
i will clean the code then pull request again
thanks for review 🙂

@theiskaa What do you think about hard-coded return true expression I mentioned here?
Do you have any suggestions/solutions or should we merge? I will leave it up to you. ^_^

Thank you @GiorgiBeriashvili. I don't think it would make any problem. So, we should merge for now, as you mentioned it can be handled later if problems arise.


Homepage suggestion

A suggestion for the homepage, consisting of 2 parts:

A copy of the default cover block, with 1 change: removing a style class that breaks the background color
Three pointers to get started: getting started with Java & Python, and a plug for the community

Thank you, @opwvhk !


verify sshd config is good before restarting

If the sshd config is valid fail the chef run before restart sshd.
This allows the problem to be detected and fixed, which may be
difficult without ssh connectivity.
Man page quote for the extent of the validation:
-t Test mode.  Only check the validity of the configuration file and
sanity of the keys.  This is useful for updating sshd reliably as
configuration options may change.

I ran kitchen verify for about 30 minutes, but did not get through all permutations.  I didn't add a new test as I could not figure out a way to test that an converge failed.

Essential! At least this basic check, waiting for it to be merged.


Updated elasticsearch to always use version 2

root@ubuntu:/tmp# docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
kibana              latest              c0a1cf8843c3        2 days ago          289.8 MB
elasticsearch       2                   3ac9ed8ea311        2 days ago          346.6 MB
pureelk/pureelk     latest              cb88e3ecc2dd        3 days ago          522.3 MB
Confirmed that "elasticsearch:latest" is no longer pulled


Init release builds

this configuration of docker container is not work. That's why I create a pull request with acceptance tests

I will check docker container in another PR


The named pipe target process has ended | Compile-AppInNavContainer

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
A clear and concise description of what the issue is.
Scripts used to create container and cause the issue
New-BcContainer `
    -accept_eula `
    -imagename...

Full output of scripts
NavContainerHelper is version <IP_ADDRESS>
NavContainerHelper is running as administrator
Host is Microsoft Windows 10 Enterprise - 2004
Docker Client Version is 19.03.8
Docker Server Version is 19.03.8
...

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context

does it happen all the time?
did it use to work?

I assume this was wrongly created as it contains no info at all.

something went wrong with chrome


Break KnetminerRequest as and KnetminerServer.handle() as the catch-all receivers for all the API methods

KnetminerServer.handle() deals with all the API requests, via the @PostMapping("/{ds}/{mode} annotation. This forces us to have a single KnetminerRequest and a single signature for all the methods, which implies having all possible parameters for all the requests inside KnetminerRequest.
This is a poor design, which is tight to the idea of having multiple KnetminerDataSource-s  to serve in a single application instance, and we are now abandoning it. Normally, things would be arranged as separated service classes, and each API would have its own independent method, with its own parameters, without any need to cram everything into a couple of methods like said above.
Some of the new, non-core Knetminer services are arranged this way (eg, DatasetInfoService), but retrofitting this existing code is very hard, so, as an intermediate solution, it would be good to have the following. I'll make the case of /network, which has the specific parameter exportPlainJSON, probably there are other calls having similar specific parameters (eg, receiving listMode.

define: KnetminerNetworkRequest extends KnetminerRequest to add the exportPlainJSON parameter.

In KnetminerServer, a new Spring API call wrapper:
 @CrossOrigin
 @PostMapping("/{ds}/network") // note the fixed path tail, this overrides the general /{ds}
 public @ResponseBody ResponseEntity<KnetminerResponse> network (
   @PathVariable String ds, @PathVariable String mode,
   @RequestBody KnetminerNetworkRequest request, HttpServletRequest rawRequest) {
     // this method is here only to capture a different KnetminerRequest subclass
     // and there is general processing in handle() that we still need
     this.handle (...)
   }

In KnetminerServer.handleRaw(), in place of:
Method method = dataSource.getClass ().getMethod ( mode, String.class, KnetminerRequest.class );
use this form:
Method method = dataSource.getClass ().getMethod ( mode, String.class, request.getClass () );
this should be enough to get the right method and avoid the problem that getMethod() doesn't
consider overloading over subclasses.

Change the signature of KnetminerDataSource.network(), into KnetminerNetworkRequest request. This should be enough to make the above reflection-based call working correctly.

This ticket might be related to  #639.

Changes moved to 202206-graphexport in knetminer

The initial solution was incomplete /network needs to support GET mode too, see cf2b12d.
Moreover, the initial solution had ugly redundancy, see KnetminerServer.network()


Not found ubuntu 18.10 install instruct document

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: Linux Ubuntu 18.04
Not found ubuntu 18.10 install instruct document

@leecow it seems we have tutorial instructions only for Ubuntu 18.04, 16.04 and 14.04, while we support also 18.10 in .NET Core 2.2: https://github.com/dotnet/core/blob/master/release-notes/2.2/2.2-supported-os.md#linux
But only .NET Core 2.1 supports 14.04: https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1-supported-os.md#linux
It seems like the samples are refering to .NET Core 2.1 only ...
@netroby did you try to use Ubuntu 18.04 steps? Did they work?

Thanks for bringing this up. I have a PR out for the website to add 18.10 to the dropdown. In the meantime, 18.10 instruction can be found in the linux-setup doc.

See it，already had 18.10 list in the dropdown
Thanks for help.


test: add pod e2e testing

What type of PR is this?
test: add test codes
What does this PR do?
add pod e2e testing code
Which issue(s) does this PR fix?
Special notes for your reviewer:
Screenshots (if applicable):

Additional Comments:

@zhangyongxi
@zhouhaoA1    please help review.

@xyz2277 @duanmengkk @zhouhaoA1  Please help merge.


Redefine Foundry test for AMMWrapper and AMMWrapperWithPath contracts

To make the foundry test for AMMWrapper and AMMWrapperWithPath contracts more readable, these test codes have been changed and added to the hierarchy.
These test codes conform to the following specifications:

One file, one contract.
Test contracts are named with upper camel case.
Test functions are named with lower camel case.
Minimal import principle: do not import unused libraries.
Minimal using principle.
Minimal Test Helper functions principle.
Minimal Struct variable principle.
Use MIT SPDX-License-Identifier.
Takes the exact declared variable as the parameters of the functions.
Declare easily identifiable variables as function parameters for better readability.

Please use the following command to test:

Notice: Please replace your own Alchemyapi Secret Key.

% export MAINNET_NODE_RPC_URL="https://eth-mainnet.alchemyapi.io/v2/<YOUR_SECRET>"
% export FORK_BLOCK_NUMBER="14340000"
% echo ${MAINNET_NODE_RPC_URL} && echo ${FORK_BLOCK_NUMBER}

% forge test -vvv --fork-url ${MAINNET_NODE_RPC_URL} --fork-block-number ${FORK_BLOCK_NUMBER} --match-path "contracts/test/forkMainnet/AMMWrapper*/*.t.sol" --force

The execution result is as follows:

( Please click here to expand )

Running 2 tests for contracts/test/forkMainnet/AMMWrapper/SetAndCloseAllowance.t.sol:TestAMMWrapperSetAndCloseAllowance
[PASS] testCannotSetAndCloseAllowanceByNotOperator() (gas: 20186)
[PASS] testSetAndCloseAllowance() (gas: 41479)
Test result: ok. 2 passed; 0 failed; finished in 1.24s
Running 3 tests for contracts/test/forkMainnet/AMMWrapper/SetupTest.t.sol:TestAMMWrapperSetup
[PASS] testAMMWrapperSetup() (gas: 60516)
[PASS] testTokensAllowanceAmountWhenSetup() (gas: 34022)
[PASS] testTokensTotalSupplyWhenSetup() (gas: 25809)
Test result: ok. 3 passed; 0 failed; finished in 1.25s
Running 2 tests for contracts/test/forkMainnet/AMMWrapper/DepositETH.t.sol:TestAMMWrapperDepositETH
[PASS] testCannotDepositETHByNotOperator() (gas: 13130)
[PASS] testDepositETH() (gas: 46607)
Test result: ok. 2 passed; 0 failed; finished in 1.25s
Running 1 test for contracts/test/forkMainnet/AMMWrapper/Event.t.sol:TestAMMWrapperEvent
[PASS] testEmitSwappedEvent() (gas: 270632)
Test result: ok. 1 passed; 0 failed; finished in 1.27s
Running 3 tests for contracts/test/forkMainnet/AMMWrapperWithPath/SetupTest.t.sol:TestAMMWrapperWithPathSetup
[PASS] testAMMWrapperWithPathSetup() (gas: 62044)
[PASS] testTokensAllowanceAmountWhenSetup() (gas: 59010)
[PASS] testTokensTotalSupplyWhenSetup() (gas: 49113)
Test result: ok. 3 passed; 0 failed; finished in 1.29s
Running 1 test for contracts/test/forkMainnet/AMMWrapper/TradeCurveV1.t.sol:TestAMMWrapperTradeCurveV1
[PASS] testTradeCurveV1() (gas: 513354)
Test result: ok. 1 passed; 0 failed; finished in 1.33s
Running 1 test for contracts/test/forkMainnet/AMMWrapperWithPath/Event.t.sol:TestAMMWrapperWithPathEvent
[PASS] testEmitSwappedEvent() (gas: 534834)
Test result: ok. 1 passed; 0 failed; finished in 86.23ms
Running 1 test for contracts/test/forkMainnet/AMMWrapper/TradeSushiswap.t.sol:TestAMMWrapperTradeSushiswap
[PASS] testTradeSushiswap() (gas: 262598)
Test result: ok. 1 passed; 0 failed; finished in 81.82ms
Running 3 tests for contracts/test/forkMainnet/AMMWrapper/UpgradeSpender.t.sol:TestAMMWrapperUpgradeSpender
[PASS] testCannotUpgradeSpenderByNotOperator() (gas: 13388)
[PASS] testCannotUpgradeSpenderToZeroAddress() (gas: 10843)
[PASS] testUpgradeSpender() (gas: 17012)
Test result: ok. 3 passed; 0 failed; finished in 70.94ms
Running 3 tests for contracts/test/forkMainnet/AMMWrapperWithPath/TradeSushiswap.t.sol:TestAMMWrapperWithPathTradeSushiswap
[PASS] testTradeWithMultiHop() (gas: 372900)
[PASS] testTradeWithSingleHop() (gas: 302781)
[PASS] testTradeWithSingleHopIfOldEIP712Signature() (gas: 302867)
Test result: ok. 3 passed; 0 failed; finished in 98.65ms
Running 4 tests for contracts/test/forkMainnet/AMMWrapper/TradeUniswapV2.t.sol:TestAMMWrapperTradeUniswapV2
[PASS] testCannotTradeIfPayloadAgain() (gas: 286938)
[PASS] testCannotTradeWithInvalidSignature() (gas: 77402)
[PASS] testTradeUniswapV2() (gas: 254291)
[PASS] testTradeWithOldEIP712Signature() (gas: 254248)
Test result: ok. 4 passed; 0 failed; finished in 120.30ms
Running 1 test for contracts/test/forkMainnet/AMMWrapperWithPath/TradeCurveV1.t.sol:TestAMMWrapperWithPathTradeCurveV1
[PASS] testTradeCurveV1() (gas: 599033)
Test result: ok. 1 passed; 0 failed; finished in 119.38ms
Running 10 tests for contracts/test/forkMainnet/AMMWrapperWithPath/TradeUniswapV3.t.sol:TestAMMWrapperWithPathTradeUniswapV3
[PASS] testCannotTradeIfPayloadAgain() (gas: 356355)
[PASS] testCannotTradeMultiPoolWithInvalidFeeFormat() (gas: 227984)
[PASS] testCannotTradeMultiPoolWithInvalidPathFormat() (gas: 425799)
[PASS] testCannotTradeMultiPoolWithMismatchAsset() (gas: 441652)
[PASS] testCannotTradeSinglePoolWithInvalidPoolFee() (gas: 433596)
[PASS] testCannotTradeSinglePoolWithInvalidSwapType() (gas:<PHONE_NUMBER>696166191)
[PASS] testCannotTradeWithInvalidSignature() (gas: 81536)
[PASS] testTradeWithMultiHop() (gas: 391354)
[PASS] testTradeWithSingleExactInput() (gas: 309279)
[PASS] testTradeWithSingleHop() (gas: 343265)
Test result: ok. 10 passed; 0 failed; finished in 92.41ms
Running 5 tests for contracts/test/forkMainnet/AMMWrapper/Subsidize.t.sol:TestAMMWrapperSubsidize
[PASS] testCannotSubsidizeByNotRelayer() (gas: 215424)
[PASS] testCannotSubsidizeExceedMaxSubsidyAmount() (gas: 571390)
[PASS] testCannotSubsidizeIfSwapFailed() (gas: 220101)
[PASS] testCannotSubsidizeWithoutEnoughBalance() (gas: 315991)
[PASS] testSubsidize() (gas: 295864)
Test result: ok. 5 passed; 0 failed; finished in 1.40s
Running 3 tests for contracts/test/forkMainnet/AMMWrapper/CollectFee.t.sol:TestAMMWrapperCollectFee
[PASS] testCollectFeeIfReceivedMoreThanMinOut() (gas: 283906)
[PASS] testCollectFeeIfReceivedMoreThanMinOutButNotEnough() (gas: 283500)
[PASS] testCollectFeeIfReceivedSameAsMinOut() (gas: 262997)
Test result: ok. 3 passed; 0 failed; finished in 1.40s

Thank you very much!

I prefer splitting test cases by different external/public function and keep property check & assertion for specific function in one file as much as possible. For example now I have to check 2 files to make sure 1. the fee is collected properly and 2. the event is emitted as expected. These could be merged into one single case to me. We can further discuss what's the ideal granularity of separated files.


Support security OAuth2 scopes on operations

Operations may define the required OAuth2 scope. For example, in the example PetStore spec, to POST to the /pet endpoint to create a new Pet, it is required that the token have read and write permissions:
security:
  - petstore_auth
      - 'write:pets'
      - 'read:pets'

You can see from the demo that the required auth scopes are not shown for the operation.
Is it on the near-term roadmap to support rendering the required auth scopes for an operation? We are loving ReDoc, but this is a pretty big deal as users need to know the required auth scope.

If this is something that is agreed-upon as a good feature, I'm willing to help with a PR to get this in.

I have this working by showing any OAuth2 scopes beneath the responses for each operation (won't display if there are no oauth2 scopes for an operation):

There are other UX possibilities of course, like adding the security info all in a tip (for example with a little padlock icon that shows the security scopes when hovering over, next to the operation description).
I'll follow with a PR for what I've done if this looks like a good first step. Thanks!

@jimmyjames I would love to see it be associated with the request vs. the response personally.

Yeah @Schandlich I kind of agree. What about something like this, where there's a tooltip hint floated right of the operation (similar to Swagger UI):

@jimmyjames I think the location is right. I would use a different icon though. Excited for this!

@jimmyjames sorry for long reply!
This looks awesome. Proceed with PR please!

@RomanGotsiy will do, need to move it from proof-of-concept to PR-worthy (me no Angular so well 😄 ). I used a ! since I didn't find any imgs in the project, wasn't sure if that was just because there hasn't been a need yet, or due to a design/performance consideration. I can either stick with that or try and find some type of padlock icon to use instead...

Start with ! and then we will figure out how to add padlock icon in PR comments :)

Having OAuth2 scopes for API calls is a highly requested feature for us too.
I would love to see the scopes somewhere above call parameters listing, as this seems to be the best place for them:

I'm ready to contribute to make ReDoc even better. I really love this tool!

+1 this feature  will be awesome! I can help too

Would really like this,

+1 for sure!


perf(combine-api): improve production runner for combine-api

Ill deploy ghcr.io./biosimulations/combine-api:pr-4040 to dev and see if that helps. There might still need to be some more tweaks

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


[Feature Request] Add setting to not show media wallpaper on lockscreen

Please can you add a setting to show/hide media wallpaper in the lock screen, rather than it currently always showing it.

I think this may be outside of the scope of Romote because that setting cannot be controlled using ECP.


Qt6ct darker theme is partially broken and hard to read

When you run qt6ct and choose "darker" theme and then run any application that uses qt6, part of the texts are black. Which on a dark background is very hard to read, nearly impossible (depending on the app) and eye-straining:

This particular screenshot is from mkvtoolnix-gui but the same problem occurs with other applications as well, such as qbittorrent. The regular qbittorrrent uses qt6, so until this problem is resolved, I had to switch to qbittorrent-qt5. But mkvtoolnix-gui doesn't have a qt5 build, so fixing the reported problem would be much appreciated.
For comparison - there are no black texts in "darker" theme when the app is using qt5.

This seems familiar. I get black icons using the system theme setting on OBS Studio (and the system theme setting defaults to Fusion rather than user picked theme). It uses Qt 6 as well. Maybe there some kind of relation?

This seems familiar. I get black icons using the system theme setting on OBS Studio (and the system theme setting defaults to Fusion rather than user picked theme). It uses Qt 6 as well. Maybe there some kind of relation? Scratch that possibly? qgnomeplatform likes to meddle with colors.

Icons are easily fixable by the user. Download (if you don't have it, ofc) the same icons theme you're using for the system but make sure the name includes "dark" (like "breeze-dark", for instance), then go to ~/.local/share/icons and create a directory with the program name in it. Unpack the downloaded icons theme there and run OBS to see if it will change. If it doesn't, find the program's config file and edit it to include the new icons theme.
I can't give you details on what exactly to write in the config file bc I did that long ago and I simply can't remember the details.
Texts, however, can't be fixed that way and it depends on the qt6ct developer.

Hi,
I am having the same issue over here. With qt5ct things used to work. In case it is helpful, this is from a custom widget I had to code and exhibits the same issue:

The color of the ticks and text of that time slider is obtained programmatically from the current palette as this->palette().color(QPalette::WindowText);. Maybe qt6ct is failing to adjust the setting for QPalette::WindowText somehow?
Cheers

Okay, after playing around with qt6ctplatformtheme.cpp I found a workaround and also a very strange behavior.
It turns out that pure white (#ffffffff) is a color that Qt does not like. However: an imperceptibly darker tone of white (#fffefefe) works seamlessly. I changed the files darker.conf and dusk.conf respectively as follows:
[ColorScheme]
active_colors=#fffefefe, #ff424245, #ff979797, #ff5e5c5b, #ff302f2e, #ff4a4947, #fffefefe, #fffefefe, #fffefefe, #ff3d3d3d, #ff222020, #ffe7e4e0, #ff12608a, #fff9f9f9, #ff0986d3, #ffa70b06, #ff5c5b5a, #fffefefe, #ff3f3f36, #fffefefe, #80ffffff
disabled_colors=#ff808080, #ff424245, #ff979797, #ff5e5c5b, #ff302f2e, #ff4a4947, #ff808080, #fffefefe, #ff808080, #ff3d3d3d, #ff222020, #ffe7e4e0, #ff12608a, #ff808080, #ff0986d3, #ffa70b06, #ff5c5b5a, #fffefefe, #ff3f3f36, #fffefefe, #80ffffff
inactive_colors=#fffefefe, #ff424245, #ff979797, #ff5e5c5b, #ff302f2e, #ff4a4947, #fffefefe, #fffefefe, #fffefefe, #ff3d3d3d, #ff222020, #ffe7e4e0, #ff12608a, #fff9f9f9, #ff0986d3, #ffa70b06, #ff5c5b5a, #fffefefe, #ff3f3f36, #fffefefe, #80ffffff

[ColorScheme]
active_colors=#ff000000, #ff7f7f7f, #fffefefe, #ffcbc7c4, #ff7f7f7f, #ffb8b5b2, #ff000000, #fffefefe, #ff000000, #ff7f7f7f, #ff7f7f7f, #ff707070, #ff308cc6, #fffefefe, #ff0000ff, #ffff00ff, #ff7f7f7f, #ff000000, #ff7f7f7f, #ff000000, #80000000
disabled_colors=#ffbebebe, #ff7f7f7f, #fffefefe, #ffcbc7c4, #ff7f7f7f, #ffb8b5b2, #ffbebebe, #fffefefe, #ffbebebe, #ff7f7f7f, #ff7f7f7f, #ffb1aeab, #ff7f7f7f, #fffefefe, #ff0000ff, #ffff00ff, #ff7f7f7f, #ff000000, #ff7f7f7f, #ff000000, #80000000
inactive_colors=#ff000000, #ff7f7f7f, #fffefefe, #ffcbc7c4, #ff7f7f7f, #ffb8b5b2, #ff000000, #fffefefe, #ff000000, #ff7f7f7f, #ff7f7f7f, #ff707070, #ff308cc6, #fffefefe, #ff0000ff, #ffff00ff, #ff7f7f7f, #ff000000, #ff7f7f7f, #ff000000, #80000000

My bet is that the color representation #ffffffff is encoded as 0xffffffff at some point (which equals to -1 if treated as 32-bit int), and since this value is often used as some generic invalid / unset / sentinel valued, it is silently ignored. Nonetheless, this does not look much as a qt6ct issue but a Qt6 one. This is what my widget looks like now (and the comboboxes as well):

Unfortunately, I'm unable to reproduce this issue under latest Manjaro update (qt6ct + Fusion style + darker color scheme). See screenshot. Please, give me right direction.


Drop legacy PILOT_ENABLE_LEGACY_AUTO_PASSTHROUGH feature flag

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
e2fd67b00898dfb1df7c0719141ed59caa12a051
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Image Terminals are shut down even though "keep_terminals"-flag is set to True

The problem is located in idle_checker.py: https://github.com/aws-samples/sagemaker-studio-auto-shutdown-extension/blob/main/sagemaker_studio_autoshutdown/idle_checker.py
When the IdleChecker is shutting down any notebooks in its method "is_idle" because num_sessions > 0,
it does not check if any terminals are open and if the "keep_terminals"-flag is set to true.
As a result the whole application including terminals is shut down even though image terminals should have been kept alive.

Hi @belleny90, can you confirm you're using the latest version of the extension? We've tested this scenario and it works as expected. In idle_checker, line, we check for the flag. If this flag is not set, it goes to the other elif statements, including the one you mentioned. Let us know if you're still facing this issue.

Hi @durgasury, yes I am using the latest version. I've seen that the flag is taken care of in the line you mentioned. The problem is, that the if-statement in this line also assumes num_sessions < 1. Hence, if notebooks are running we have num_sessions >= 1 and it goes to the last elif-block - no matter of num_terminals and the flag "keep-terminals".
The last block does not contain the check for the flag or num_terminals and shuts down the application including image terminals after closing all notebooks.

Gotcha! When a session AND a terminal is open, seems to kill both. If only the terminal is open, it is retained. I'll check what the design is and update the extension accordingly. Thanks for clarifying.

Thanks @belleny90 , I've tested the code and merged it in the PR mentioned above. Closing this issue.


timeline_create: bootstrapping a timeline can block an executor thread for 1s

It is probably not the cause of long timeline_create requests we endure during startup, but it certainly is not helping.
This is in the class of bugs that could had been found with by running with current_thread executor only, but at the same time, this has been known for a long time.
In short, this needs to be async using https://docs.rs/tokio/latest/tokio/process/struct.Command.html instead of what is currently used (std::process::Command):
https://github.com/neondatabase/neon/blob/0d10992e463e9377d9791cdb90c5d13c452aa504/pageserver/src/tenant.rs#L3344-L3350
Async opens us up for cancellation, so we need to kill the process in case we are cancelled (which is not expected to be happening).

good_first_issue: duplication of setup code can be avoided using https://docs.rs/tokio/latest/tokio/process/struct.Command.html#impl-From<Command>-for-Command right before spawning and awaiting.

Part of the impl should be some sort of concurrency limit.
Also I'm wondering whether our initdb has fsync disabled.
It should.

I'm wondering whether our initdb has fsync disabled.

1s does not sound like it but there is at least the --no-sync, which is documented to give this.

As far as the next steps go, I was thinking the WalkDir usage together with tokio::fs for file accesses might not be healthy, but needle will move when #5446 is merged.
#5390 adds similar WalkDir and tokio::fs usage.


add hanxiaoshuai to reviewers

I am very interested in this project, apply for adding myself to the reviewers

/assign @m1093782566 @shivramsrivastava

/retest

/lgtm

/test ci-poseidon-e2e-gce

@hanxiaoshuai
I would say YES this time, but please keep in mind that you should take more responsibility once you become the official Reviewer.

/approve

/test ci-poseidon-e2e-gce

/retest

/retest

/test ci-poseidon-e2e-gce

/test ci-poseidon-e2e-gce

The test case
I0622 06:48:50.990] [Fail] Poseidon Poseidon [Pod Affinity and Anti-Affinity] [It] validates scheduler respect's a pod-anti-affinity with hard constraint and affinity soft constraint

keeps failing...
@shivramsrivastava

/test ci-poseidon-e2e-gce

/test ci-poseidon-e2e-gce

Looks like a random crash, it not a specific test case that is failing.

/test ci-poseidon-e2e-gce

/test ci-poseidon-e2e-gce

/test ci-poseidon-e2e-gce

/test ci-poseidon-e2e-gce


haskellPackages/pontarius-xmpp: dontCheck

cc @peti
I’m not sure where the hasktags came from. oO

You have to amend this commit to remove the hasktags override. That change would break the  build; we cannot merge it as is.

I wonder how that came in, I did a rebase on master and it somehow created that merge; maybe if we sorted it semi-alphabetically those conflicts wouldn’t happen?

okay


Lucky results seem hard to obtain

Thanks for implementing the awesome stable-dreamfusion project! Recently, I have tried quite a lot of prompts and trained them with stable-dreamfusion codes on a single A100 GPU card. I found the differences are quite obvious among the trained models from different random initializations.  BTW I use the default settings, e.g.,
python main.py --text "a pineapple" --workspace trial2 -O2

It is quite hard to obtain "lucky results". Is there any idea to improve the generation quality to match the README samples?
Here are some of my results, which are not similar to the samples shown in README:

a pineapple (training the model 5 times using the same prompt)

https://user-images.githubusercontent.com/13333802/219289370-aea55b4e-f2d2-45f6-a5a0-1b0896eb4abd.mp4
https://user-images.githubusercontent.com/13333802/219289488-0ce252c3-205e-4d93-ab6e-1e098dc39398.mp4
https://user-images.githubusercontent.com/13333802/219289567-e616536a-4acc-4cd6-94e6-5b882dcc886f.mp4
https://user-images.githubusercontent.com/13333802/219289761-f0f62390-c2c4-4596-a8a0-40b6264a1611.mp4
https://user-images.githubusercontent.com/13333802/219289733-82c7e2b6-5969-4f2b-a9f7-a5ec73dc92ee.mp4

a DSLR photo of a pineapple (training the model 5 times using the same prompt)

https://user-images.githubusercontent.com/13333802/219289870-224462d0-72c3-4d85-ae77-734e9eee0419.mp4
https://user-images.githubusercontent.com/13333802/219289885-9e20b498-2ad0-4805-a60c-42fc6b7447b3.mp4
https://user-images.githubusercontent.com/13333802/219289899-5cb43549-0ae3-4ca2-be17-78ef0f87ddd4.mp4
https://user-images.githubusercontent.com/13333802/219289945-63c8aec0-0fb8-4820-aaa5-9803a9ccad91.mp4
https://user-images.githubusercontent.com/13333802/219289925-eb4285bc-b48f-4e68-97cd-6da027d9c109.mp4

@zhaoyuzhi Hi, the -O2 mode is not working well currently, so I recommend you to try -O instead. All the examples are generated with -O.

Thanks for your suggestion @ashawkey
I can reproduce the pineapple sample shown in the readme now.


[WIP] XSD Import

Signed-off-by: Björn Müller<EMAIL_ADDRESS>

[ ] Ensure that you followed http://eclipse.github.io/winery/dev/ToolChain#github---prepare-pull-request. Especially, we require a single commit
[ ] Ensure that the commit message is a good commit message
[ ] Ensure to use auto format in all files
[ ] Ensure that you appear in NOTICE at Copyright Holders
[ ] Tests created for changes
[ ] Documentation updated (if needed)
[ ] Screenshots added (for UI changes)

Can one of the admins verify this patch?


subsetting lecture fixes

Slide 83 still has "BUYER_STATE" as the variable being relocated, but the dataset has been changed to CO_heat_ER_bygender

Slide 83 still has "BUYER_STATE" as the variable being relocated, but the dataset has been changed to CO_heat_ER_bygender

this appears to be fixed but there were some other issues with this slide that were addressed by PR #165


AMC saves collection in collection even if it's nil.

Subj.
Need to test against nil before processing any value.
TODO:

Add testCase, that fails with current AMC version.
Fix AMC - test should pass.

Changed to Defect - looks like there's no problem with that.


Fix flag for 'trim' modifier

Man page indicates 'q' instead of 't'

I saw the svn commit and checked this patch into the “develop” branch already:
   "t" == "trim" (typo) (cf svn commit: r290445 - head/contrib/libxo/libxo) (commit e2633606aff6737d787c2a025533b61c6e4e7f51)

https://github.com/Juniper/libxo/commit/e2633606aff6737d787c2a025533b61c6e4e7f51 https://github.com/Juniper/libxo/commit/e2633606aff6737d787c2a025533b61c6e4e7f51
Please use the develop branch for patches, since it’s where the magic happens.  master is used for releases.
Thanks,
Phil

On Nov 23, 2015, at 8:13 PM, Allan Jude<EMAIL_ADDRESS>wrote:
Man page indicates 'q' instead of 't'
You can view, comment on, or merge this pull request online at:
https://github.com/Juniper/libxo/pull/51 https://github.com/Juniper/libxo/pull/51
Commit Summary
Fix flag for 'trim' modifier
File Changes
M libxo/xo_format.5 https://github.com/Juniper/libxo/pull/51/files#diff-0 (2)
Patch Links:
https://github.com/Juniper/libxo/pull/51.patch https://github.com/Juniper/libxo/pull/51.patch
https://github.com/Juniper/libxo/pull/51.diff https://github.com/Juniper/libxo/pull/51.diff
—
Reply to this email directly or view it on GitHub https://github.com/Juniper/libxo/pull/51.


'RuntimeError('unable to open shared memory object </torch_175312_2031012121> in read-write mode')'

Hello, when i am running the train.py， there is a issue about "Reason: 'RuntimeError('unable to open shared memory object </torch_175312_2031012121> in read-write mode')' "
I dont know why,  the num_worker=0 is still no using. Cound you kindly give me a help.
Thank you

the log is     `Let's use 0 GPUs!
CONFIG:
{
"CTC": false,
"abspos": false,
"arMode": "LSTM",
"batchSizeGPU": 8,
"beta1": 0.9,
"beta2": 0.999,
"cpc_mode": null,
"debug": false,
"dropout": false,
"encoder_type": "cpc",
"epsilon": 1e-08,
"file_extension": "flac",
"hiddenEncoder": 256,
"hiddenGar": 256,
"ignore_cache": false,
"learningRate": 0.0002,
"load": null,
"loadCriterion": false,
"logging_step": 1000,
"max_size_loaded":<PHONE_NUMBER>,
"nEpoch": 200,
"nGPU": 0,
"nLevelsGRU": 1,
"nLevelsPhone": 1,
"nPredicts": 12,
"n_process_loader": 8,
"negativeSamplingExt": 128,
"normMode": "layerNorm",
"onEncoder": false,
"pathCheckpoint": "/data3/trx/CPC_audio/checkpoint",
"pathDB": "/data3/trx/dataset/LibriSpeech/train-clean-100",
"pathPhone": null,
"pathTrain": "/data3/trx/dataset/train-clean-100-set.txt",
"pathVal": "/data3/trx/dataset/dev-clean-set.txt",
"random_seed":<PHONE_NUMBER>,
"restart": false,
"rnnMode": "transformer",
"samplingType": "samespeaker",
"save_step": 5,
"schedulerRamp": null,
"schedulerStep": -1,
"sizeWindow": 20480,
"speakerEmbedding": 0,
"supervised": false
}
Ran in an error while loading /data3/trx/dataset/LibriSpeech/train-clean-100/_seqs_cache.txt: [Errno 2] No such file or directory: '/data3/trx/dataset/LibriSpeech/train-clean-100/_seqs_cache.txt'
Could not load cache, rebuilding
837it [00:00, 6894.27it/s]
Saved cache file at /data3/trx/dataset/LibriSpeech/train-clean-100/_seqs_cache.txt
Found files: 28539 seqs, 251 speakers
Loading audio data at /data3/trx/dataset/LibriSpeech/train-clean-100
Loading the training dataset
Checking length...
28539it [00:00, 1905918.99it/s]
Done, elapsed: 1.102 seconds
Scanned 28539 sequences in 1.10 seconds
2 chunks computed
Checking length...
28539it [00:00, 1902798.40it/s]
Done, elapsed: 0.234 seconds
Scanned 28539 sequences in 0.23 seconds
2 chunks computed
Joining pool
Joined process, elapsed=67.338 secs
Traceback (most recent call last):
File "cpc/train.py", line 494, in
main(args)
File "cpc/train.py", line 287, in main
MAX_SIZE_LOADED=args.max_size_loaded)
File "/data3/trx/CPC_audio/cpc/dataset.py", line 65, in init
self.loadNextPack()
File "/data3/trx/CPC_audio/cpc/dataset.py", line 129, in loadNextPack
self.nextData = self.r.get()
File "/data3/trx/anaconda3/lib/python3.7/multiprocessing/pool.py", line 657, in get
raise self._value
multiprocessing.pool.MaybeEncodingError: Error sending result: '[(242, '7264-92314-0020', tensor([-0.0010, -0.0009, -0.0011,  ...,  0.0015,  0.0016,  0.0019])), (230, '211-122442-0031', tensor([0.0061, 0.0146, 0.0129,  ..., 0.0163, 0.0156, 0.0262])), (59, '39-121914-0012', tensor([-0.0017, -0.0016, -0.0011,  ..., -0.0019, -0.0042,  0.0010])), (218, '7367-86737-0066', tensor([9.1553e-05, 6.4087e-04, 1.2207e-04,  ..., 5.1880e-04, 3.6621e-04,
....................................]'. Reason: 'RuntimeError('unable to open shared memory object </torch_175312_2031012121> in read-write mode')'`


#159758091 implement the logout functionality

What does this PR do?
This PR creates the logout functionality
How should this be manually tested?

Clone the repo

$ git clone https://github.com/asheuh/StackOverflow-lite
$ cd StackOverflow-lite

Create virtualenv

$ python -m venv venv

Run app

$ flask run

Then go to <IP_ADDRESS>:5000/api/v2

What are the relevant pivotal tracker stories?
159758091

Pull Request Test Coverage Report for Build 108

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 93.201%

Totals

Change from base Build 106:
0.0%

Covered Lines:
658

Relevant Lines:
706

💛  - Coveralls


Revert "[supply] Add check_superseded_tracks option (#9250)"

This reverts commit 73c75d2574ebbcc89046f40045d7f6b2d48a2d48. (https://github.com/fastlane/fastlane/pull/9250)
Caused a few issues:

https://github.com/fastlane/fastlane/issues/9442
https://github.com/fastlane/fastlane/issues/9441

and
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/specification.rb:2007:in `raise_if_conflicts': Unable to activate google-api-client-0.12.0, because addressable-2.3.8 conflicts with addressable (>= 2.5.1, ~> 2.5) (Gem::LoadError)
17:38:30     from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/specification.rb:1176:in `activate'
17:38:30     from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/specification.rb:1212:in `block in activate_dependencies'
17:38:30     from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/specification.rb:1198:in `each'
17:38:30     from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/specification.rb:1198:in `activate_dependencies'
17:38:30     from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/specification.rb:1180:in `activate'
17:38:30     from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_gem.rb:48:in `gem'
17:38:30     from /usr/local/bin/fastlane:22:in `<main>'

Hmm, is it possible to instead of reverting the commit actually just pin to google-api-client-0.11.0 (or even take it out since it wasn't really necessary).


Make std.encoding mostly @safe pure nothrow @nogc

When trying to make a format call pure, I noticed that all of the impure problems could be traced back to std.encoding, which is called by std.range.put. Most of the problems here are the result of not using template inference or missing attributes. There was one instance of accessing a mutable private member, which was made immutable.
Making these changes will make a lot of templates in other modules @safe pure as a side effect

Other than that, looks good.  Enabling more things in Phobos to be pure, nothrow, etc., is definitely a good thing.  Also, one nice side-effect of templatizing these functions is that if they're never actually used, they won't end up in the executable. Another plus in my book.

@quickfur fixed

Ping @quickfur @mathias-lang-sociomantic

@mathias-lang-sociomantic done

Ping @quickfur @mathias-lang-sociomantic

@JackStouffer : I don't usually LGTM Phobos P.R. because I neither have commit rights, use it at work, nor know enough about it to consider my LGTM worthwhile.
In this case it looks like you are changing a lot of method signature. AFAICS, it's a huge breaking change, which I would personally frown upon. But there is precedent so I let it up to a maintainer to decide.

@schveiguy Made some changes

This has to be one of the worst implementations I've ever seen of anything in D. The mixins where the parameter names come from the mixing-in function, but are assumed by the mixin, awful.
I'm just going to say LGTM, let's fix the issues, and think about how we can rewrite this mess.

I say std.encoding goes on the chopping block after std.xml and std.json.

Ping @quickfur
Ok to go?

I say std.encoding goes on the chopping block right after std.xml and std.json. This thing needs to be completely rethought/redesigned.

Yes please kill them with🔥.
That being said I don't know much about the hidden secrets of encoding.d, but as the other people on this PR already pointed out, templatizing brings a lot of benefits :)

Reping @quickfur though I guess we can go ahead and merge

Ping @quickfur @DmitryOlshansky

Auto-merge toggled on

Thanks


Deleting a Column Deletes Closed Tasks Too

Just made an awful error.......
The final column on my Board was named "Completed". Once a task was completed, it was moved to this column. After a review of Completed tasks, they were then closed.
It was felt that the Completed column was a bit of a waste of space, given a crowded board, and tasks should be directly closed when completed, and then the Closed Tasks list reviewed subsequently.
I therefore removed the Completed column. Unfortunately, this also deleted all the Closed Tasks, which had last been held in that column. The history of my project has now largely disappeared.
I feel that deleting a Column should not delete any Closed Tasks which may have been formally associated with it.

Sorry for your loss of data.
Still, you do get a warning - ref screeshot below - and if you've reviewed "Completed tasks" (in previous versions) or the "List" (in v 1 0 1 8) - with closed tasks, you know that the closed tasks are assosciated with the column they were in when they were closed.
If re-structuring an important board, perhaps a backup of the '\data' folder beforehand is appropriate.

Linking this ticket with #439

Could you please update the message, to mention the fact that also closed tasks will simply be deleted?
This is very unexpected.
When I needed to close 50 or more tasks, I always added a new column named "Close", added a new action named "automatically close tasks when moved onto a column", moved all the tasks, then i deleted the column.
As the old kanboard had no bulk closing option, this was the only way to achieve it in time.
Now I hear that all the closed task have been deleted, which is very unexpected because why should anybody think that a task could be still associated to a column when its closed?!
maybe in recent versions of kanboard this idea is logical, but in old versions, where closed tasks could only be seen in a special list, this is really not logical.
Yes - we have a daily or more often backup. Yes, we could restore this everything. But how could we get tasks from all the old backups back into the current and up to date kanboard.
This would take much longer than the benefits of having a history of closed tasks would probably save us.
I also do not at all understand why deleting a column needs to delete a task. whats the big problem of having a task with no column?
And if this is a big problem, whats the problem of assigning them all to another column or of just displaying a message like "This column contains xx closed (invisible) tasks, do you really want to delete them?"


Added SurrealDB Starter Project for Go

Refers #35

Hey @naisofly  - this can now be merged. I don't have permissions though.

Thanks @phughk!
@sbshah97 Thanks for your contribution & remember to include a GIF or screenshot showcasing the app's final result for developer reference, as mentioned in the Success Criteria in #35 ✌


C: Remove -lerl_interface

OTP 23 has removed the deprecated erl_interface library. All required
symbols are apparently provided by -lei, so just remove -lerl_interface.
Fixes #21

Thank you


Function hooking

Have you considered using https://crates.io/crates/retour instead of MinHook? It's essentially a maintained version of "detours".
Should also be easier to use than MH.

Hi!
Yeah, I've seen it. I decided against it because we don't need anything more than what minhook already offers, plus minhook is very minimal and stable, and its API is clean and makes FFI not really a problem at all.
On the other hand, hudhook's dependency tree has a history of small packages ending up abandoned in a broken state, someone forks them and the fork becomes abandoned as well shortly after. I actually empathize big time: maintaining stuff is hard, and this very repo and the paltry progress I've been able to do on it recently is a testament to that. 😅
detours is one of the crates that ended up not being maintained, and, while retour looks promising, switching over entails a maintenance burden that doesn't justify the value added to our use case.

Ah, makes sense. Good to know!


HomeBridge dimmables wrong values

In #12 @RonaldR and @martienvd pointed this out. In my case the following happens:

Dim a dimmable to 100% only goes to 39% as 100/255  = 39%
On max brightness, HomeKit shows a brightness of 255% instead of 100%

I'll wait and see if HomeBridge team fixes this. Please open an issue at their repo.

@youridijk is maxBrightness: 15 in https://github.com/youridijk/ICS-2000-NodeJS/blob/main/src/kaku/DeviceConfigs.ts not the issue?

Same issue here, I think that the issue indeed started when updated to iOS 17. I ordered ah older iPad today i hope it has iOS 16.x installed. I can try it out if its in iOS.
In Home it shows the correct value in the small overview after comparing it to the default KAKU app but when you open the dimmables to set the value it is shows very low values.
example: overview 40% open 6%
overview 47% open 7%
overview 13% open 2%
you can change it a bit but it falls back down but it will change. When I try to up the 13% / 2% it falls back stays on 11% and the overview shows 73%.

Yes, same problems here as you describe. Definitely an issues with homebridge, but can’t seem to find an issue about it on their GitHub or somewhere else. Feels weird, can’t be that it’s just us. Anyone experiencing same issues with other plugins?

I fixed the issue by manually convert the 0-100 brightness range from Homebridge to a 0-255 range KAKU uses. Don't really like the solution but works fine. Should be backwards compatible with previous iOS versions. I just released a new version of this plugin with the fix. If after the update the issue isn't gone, please empty your cache.

Works, great! Only thing now is that the value is wrong other way around. When open it is correct for example 30% closed 200% so that looks a bit weird but it works again and no flyback down.

thanks, works perfectly!

@rickklh  Hmm I'm not experiencing it after clearing the cache. Maybe it will help you too.

@rickklh Hmm I'm not experiencing it after clearing the cache. Maybe it will help you too.

I did that after the first post because after the update to 1.3.2 I didn’t work and cleared the cache of homebridge like you said. No issues again on iOS 16.4 only 17.
Tried rebooting the whole system, no succes but simply after rebooting my phone the issue was gone!
so for anyone else having this problem, reboot your stuff might be the solution.
Thanks for your response and great homebridge plug-in. Much appreciated.


Memory Leak in Godot C#

Godot version
4.1.1
System information
Windows 11
Issue description
I was working on porting over a game from GDScript to C# and noticed that when I was moving a character around the tile map the godot monitor showed objects and memory usage steadily increasing over time.
This issue did not exist in the GDScript version of the code.
Steps to reproduce
In the included project. Launch the game and move the blue square with WASD and watch the godot monitor. Objects will settle around 1305 at the start and, after some quick noodling left and right, will rise to 1500+ and not decrease after waiting for a minute.
Minimal reproduction project
MemoryLeak.zip

Most likely something in the input? IIRC it was reported a couple times

C# uses a Garbage Collector so objects won't be immediately disposed. To check if this is an actual memory leak, try adding this code and see if it makes a difference:
GC.Collect(GC.MaxGeneration, GCCollectionMode.Forced);
GC.WaitForPendingFinalizers();

If this fixes the issue then there is no memory leak, it's just the normal behavior of the GC.

C# uses a Garbage Collector so objects won't be immediately disposed. To check if this is an actual memory leak, try adding this code and see if it makes a difference:
GC.Collect(GC.MaxGeneration, GCCollectionMode.Forced);
GC.WaitForPendingFinalizers();

If this fixes the issue then there is no memory leak, it's just the normal behavior of the GC.

I added this to physics process and it does indeed seem to fix the issue. I am puzzled why these objects were lingering in memory for more than a minute in my unedited test project. At scale that will be unacceptable. How often does the c# GC run or is something not getting flagged correctly for deletion? It would feel hacky to force the gc to run every physics frame in order to keep memory from ballooning.

The GC is not time-based, collections are triggered when it runs out of memory. I wouldn't recommend triggering collection manually other than for debugging, if you need to dispose of the objects right away use Dispose (but keep in mind that disposed objects can't be used after they've been disposed).

Then we return to the original issue memory leak issue. Something about my fairly basic use case is creating memory and not freeing it and I don't know why. If you look at the code you will see I am not allocating something that I can really call dispose on each time the player moves.
private void Move(Vector2I targetTile) 	{ 		Game.Level.Tiles[Tile].Character = null; 		Game.Level.Tiles[targetTile].Character = this; 		GlobalPosition = Game.Level.GetGlobalFromTile(targetTile); 		Tile = targetTile; 	}

Something about my fairly basic use case is creating memory and the garbage collector is not freeing it unless I run your command and I don't know why.

The reason is likely that the GC has not decided that its worth collecting yet. A collection is performed when the allocated memory surpasses some threshold, so maybe you haven't reached it. The GC is a complicated topic, but if you want to learn more about how it works and how it determines when to collect, you may read the Fundamentals of garbage collection page in Microsoft's documentation.

Taking another look at my code I'm not seeing anything that I could call dispose on.

It's probably the InputEvent objects, but you don't have to, they'll eventually be released if they have to. If you do dispose them, be careful not to use them afterwards or it'll throw an exception. In general, I wouldn't bother disposing these events and just let the GC do its job.

This is like the third or fourth similar issue where InputEvents disposal is slightly problematic to people new to C# . Could this be better documented?

I think so, I mention a few ideas in https://github.com/godotengine/godot/issues/78065#issuecomment-1585564014. I'll close as duplicate to consolidate in https://github.com/godotengine/godot/issues/78065.


Demo can't launch on iPhone and simulator.

Tried many times. Demo can't launch at all.

is there any error?
also, please make sure you choose the correct target to launch: NgKeyboardTrackerDemo.

Thanks for your reply. You're right. I didn't choose the correct target.

:ok:


Output is noise

High, This job was very enlightening to me, but I encountered problems when trying to reproduce your code.
When I run bash demo_predict.sh, The result of the program output is noise. How to solve it?

left is input, right is output.
My Environment:
Keras==2.2.4
tensorflow-gpu==1.10.0
tensorboard==1.10.0
numpy==1.19.5
opencv-python==<IP_ADDRESS>
imageio==2.5.0
scikit-image==0.15.0
scipy==1.3.1
matplotlib==3.1.1

My file structure:

Sorry for the late reply. I didn't meet similar situation, but I think you can check if the pre-trained model was correctly loaded.


Bug:  UI Glitch - Indentation incorrect in Community Engagement box

Describe the bug
Indentation incorrect in Community Engagement box

Steps To Reproduce

Go to 'https://subhadipbhowmik.github.io/30-Days-Of-CPP/'
Scroll down
Hover on 'Community Engagement'

The word 'Participants' extrudes out of the box

The word 'Participants' should not extrude out of the box

Hi @ansh-h-mehta
Thanks for the heads-up! We'll get right on fixing the indentation glitch. Your input helps us keep our platform in top shape. Rest assured, we're committed to resolving this issue promptly.
Thanks for your patience, and stay tuned for updates!

Hi @subhadipbhowmik Yes, I am working on it


Self referencing datetime

// coverage:ignore-file
// GENERATED CODE - DO NOT MODIFY BY HAND
// ignore_for_file: type=lint, unused_import

typedef DateTime = DateTime?;
/// Typedefs can't reference themselves directly or recursively via another typedef.dart[type_alias_cannot_reference_itself](https://dart.dev/diagnostics/type_alias_cannot_reference_itself)

Schema
openapi: 3.0.0
info:
  title: Foo
  version: 1.0.0
paths:
  /foo:
    get:
      responses:
        '200':
          description: example
          content:
            application/json:
              schema:
                type: array
                items:
                 $ref: '#/components/schemas/Payment'
components:
  schemas:
    DateTime:
      type: string
      format: date-time
      example: "2019-01-01T00:00:00"
    # the following schema shouldn't be generated as model
    AllOfDatetime:
      allOf:
        - $ref: '#/components/schemas/DateTime'
      example: "2019-01-01 00:00:00"
    Payment:
      type: object
      properties:
        date:
          $ref: '#/components/schemas/AllOfDatetime'
        amount:
          type: number
          format: float
          example: 625.0

This is caused by the same problem with nameclashes with retrofit or dio.
Closing as duplicate


Fix 'use strict' declaration.

See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode

put the exact statement "use strict"; (or 'use strict';) in the function's body before any other statements.

(As far as the semicolon on the line, AFAIK, there's contention over whether a literal ; is required after the string (rather than an ASI-inserted semicolon). I'd include it to err on the safe side.)

I haven't actually tried running the tests, by the way! That needs to be done.


Ability to ban users from the platform

User story
As platform admins, we need to have a reliable way to prevent users from doing anything on the platform when we know for sure that they are spammers/malicious.
By "Ban", we mean:

Users should not be able to log in
Users should not be able to re-create an account with the same email
When possible, user-submitted data should be deleted (expenses, comments...etc)

Best solution for this problem
Should be an action in ForestAdmin.
MVP
The function to delete a user currently strips the email. We should be able to do the exact same thing without stripping it to ensure it stays blocked.
We also want to set a special flag for metrics, user.data.isBanned = true
Metrics

How many users are banned
Number of support requests for users spamming collectives

Documentation
The procedure to ban a user should be documented in https://docs.opencollective.com/help/internal/moderation

Updated https://docs.opencollective.com/help/internal/moderation with info about banning users/collectives


[BUG] Enhancement : Facilities section cards desaign

Description
Issue :

Alignment of title
Font sizes are greater than the heading

Proposed changes

BEFORE
AFTER

Screenshots
No response
Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

@agnyaatha It looks good and very nice to our side. I am closing the issue for now. Please raise another issue, which I am happy to assign to you, but make sure that the issue is valid and addresses something important on our website. Otherwise, invalid issues will be closed. Thank You!


3.5.32 is trying to go through internet proxy even on the open internet (home broadband)

3.5.32 is picking up machine office proxy from somewhere even on the open internet, and not able to connect to a local bot giving me error connect ETIMEDOUT Proxy IP : Port. Not sure what is the issue but I am unable to use emulator. Can you please help ?

This is resolved after restarting machine. Thanks


Failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers

What steps did you take and what happened:
We are having issues occasionally - once every few weeks - whereby pods on our single Windows node in an AKS cluster fail to start with MountVolume.SetUp failed for volume "secrets-store-inline" : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers.
What did you expect to happen:
Anything else you would like to add:
Following the troubleshooting guide the secrets store driver is successfully registered:
C:\Users\mihai.albert>kubectl get csidriver
NAME                       ATTACHREQUIRED   PODINFOONMOUNT   STORAGECAPACITY   TOKENREQUESTS   REQUIRESREPUBLISH   MODES                  AGE
disk.csi.azure.com         true             false            false             <unset>         false               Persistent             125d
file.csi.azure.com         false            true             false             <unset>         false               Persistent,Ephemeral   125d
secrets-store.csi.k8s.io   false            true             false             <unset>         false               Ephemeral              177d

Logs for the 3 containers inside the CSI driver pod are below.
C:\Users\mihai.albert>kubectl logs -n csi secrets-store-csi-driver-windows-xqpbr -c node-driver-registrar
I0214 22:14:48.843834   13304 main.go:164] Version: v2.3.0-0-gde03348b
I0214 22:14:52.463764   13304 main.go:165] Running node-driver-registrar in mode=registration
I0214 22:14:52.463764   13304 main.go:189] Attempting to open a gRPC connection with: "unix://C:\\csi\\csi.sock"
I0214 22:14:52.463764   13304 connection.go:154] Connecting to unix://C:\csi\csi.sock
I0214 22:14:53.585020   13304 main.go:196] Calling CSI driver to discover driver name
I0214 22:14:53.585020   13304 connection.go:183] GRPC call: /csi.v1.Identity/GetPluginInfo
I0214 22:14:53.585020   13304 connection.go:184] GRPC request: {}
I0214 22:14:53.632158   13304 connection.go:186] GRPC response: {"name":"secrets-store.csi.k8s.io","vendor_version":"v0.2.0"}
I0214 22:14:53.632158   13304 connection.go:187] GRPC error: <nil>
I0214 22:14:53.632158   13304 main.go:206] CSI driver name: "secrets-store.csi.k8s.io"
I0214 22:14:53.632158   13304 node_register.go:52] Starting Registration Server at: /registration/secrets-store.csi.k8s.io-reg.sock
I0214 22:14:53.637605   13304 node_register.go:61] Registration Server started at: /registration/secrets-store.csi.k8s.io-reg.sock
I0214 22:14:54.195782   13304 node_register.go:91] Skipping healthz server because HTTP endpoint is set to: ""

C:\Users\mihai.albert>kubectl logs -n csi secrets-store-csi-driver-windows-xqpbr -c secrets-store
I0214 22:14:14.334801    7960 main.go:99] Filtered watch for nodePublishSecretRef secret based on secrets-store.csi.k8s.io/used=true label enabled
I0214 22:14:15.295312    7960 exporter.go:33] metrics backend: prometheus
I0214 22:14:18.889502    7960 main.go:172] starting manager
I0214 22:14:19.421932    7960 secrets-store.go:74] Driver: secrets-store.csi.k8s.io
I0214 22:14:19.421932    7960 secrets-store.go:75] Version: v0.2.0, BuildTime: 2021-08-12-19:06
I0214 22:14:19.421932    7960 secrets-store.go:76] Provider Volume Path: C:\k\secrets-store-csi-providers
I0214 22:14:19.421932    7960 secrets-store.go:77] GRPC supported providers will be dynamically created
I0214 22:14:19.443409    7960 driver.go:80] "Enabling controller service capability" capability="CREATE_DELETE_VOLUME"
I0214 22:14:19.443409    7960 driver.go:90] "Enabling volume access mode" mode="SINGLE_NODE_READER_ONLY"
I0214 22:14:19.443409    7960 driver.go:90] "Enabling volume access mode" mode="MULTI_NODE_READER_ONLY"
I0214 22:14:19.530648    7960 reconciler.go:131] starting rotation reconciler with poll interval: 2m0s
I0214 22:14:19.764279    7960 server.go:111] Listening for connections on address: C:\\csi\\csi.sock
I0214 22:14:26.148721    7960 request.go:668] Waited for 1.0556426s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/templates.gatekeeper.sh/v1alpha1?timeout=32s
I0214 22:14:27.532110    7960 secretproviderclasspodstatus_controller.go:227] "reconcile started" spcps="<pod-name>"
<multiple reconcile messages show up here>
.................

C:\Users\mihai.albert>kubectl logs -n csi secrets-store-csi-driver-windows-xqpbr -c liveness-probe
E0214 22:14:26.306661    8212 processstarttime.go:43] Could not get process start time, could not read "/proc": CreateFile /proc: The system cannot find the file specified.
E0214 22:14:28.136104    8212 processstarttime.go:43] Could not get process start time, could not read "/proc": CreateFile /proc: The system cannot find the file specified.
I0214 22:14:28.966210    8212 main.go:149] calling CSI driver to discover driver name
I0214 22:14:28.974609    8212 main.go:155] CSI driver name: "secrets-store.csi.k8s.io"
I0214 22:14:28.974609    8212 main.go:183] ServeMux listening at "<IP_ADDRESS>:9808"

Logs for the Azure Key Vault provider pod:
C:\Users\mihai.albert>kubectl logs -n csi key-vault-provider-csi-secrets-store-provider-azure-window6pr7d
I0214 22:13:54.825807    5900 main.go:61] Starting Azure Key Vault Provider version: v0.2.0
I0214 22:13:59.012249    5900 main.go:72] construct pem chain feature enabled
I0214 22:13:59.012249    5900 main.go:75] secrets will be written to filesystem by the CSI driver
I0214 22:13:59.012249    5900 main.go:109] Listening for connections on address: C:\\provider\\azure.sock

Events for one of our pods that's using secrets from an Azure Key Vault is below. When the issue occurs, all the pods that need to be scheduled on Windows and need secrets injects from Azure KV are in the same state.
C:\Users\mihai.albert>kubectl get events -n dev --field-selector involvedObject.name=<redacted-pod-name>
LAST SEEN   TYPE      REASON        OBJECT                                 MESSAGE
49m         Normal    Scheduled     pod/<redacted-pod-name>   Successfully assigned dev/<redacted-pod-name> to akswinapp000004
18m         Warning   FailedMount   pod/<redacted-pod-name>   MountVolume.SetUp failed for volume "secrets-store-inline" : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers
4m22s       Warning   FailedMount   pod/<redacted-pod-name>   Unable to attach or mount volumes: unmounted volumes=[secrets-store-inline], unattached volumes=[secrets-store-inline kube-api-access-4pfdp]: timed out waiting for the condition
40m         Warning   FailedMount   pod/<redacted-pod-name>   Unable to attach or mount volumes: unmounted volumes=[secrets-store-inline], unattached volumes=[kube-api-access-4pfdp secrets-store-inline]: timed out waiting for the condition

I did look into this and this issue but the problems there seem different.
Which access mode did you use to access the Azure Key Vault instance:
[e.g. Service Principal, Pod Identity, User Assigned Managed Identity, System Assigned Managed Identity]
Using the instructions here we can see the cluster is using the System Assigned Managed Identity:
C:\Users\mihai.albert>az aks show -g <resource-group> -n <cluster-name> --query "servicePrincipalProfile"
{
  "clientId": "msi"
}

C:\Users\mihai.albert>az aks show -g <resource-group> -n <cluster-name> --query "identity"
{
  "principalId": "dfcd54e3-5dd2-4651-9d56-31c8ff2e3a8a",
  "tenantId": "bce02b33-298d-4c84-8712-e25caaf73bda",
  "type": "SystemAssigned",
  "userAssignedIdentities": null
}

Environment:

Secrets Store CSI Driver version: (use the image tag): mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.3.0
Azure Key Vault provider version: (use the image tag): mcr.microsoft.com/oss/azure/secrets-store/provider-azure:v0.2.0
Kubernetes version: (use kubectl version and kubectl get nodes -o wide): 1.21.2
Cluster type: (e.g. AKS, aks-engine, etc): AKS

Deleting the secrets store CSI driver pod doesn't have any impact on the problem. However, deploying the Helm chart and then deleting the secrets store CSI driver - and waiting for a new one to be automatically created - was found to be an effective temporary workaround.
The logs for the node-driver-registrar container look to slightly change once things start working again. There's extra text at the end referring to a "Kubelet registration probe":
C:\Users\mihai.albert>kubectl logs -n csi secrets-store-csi-driver-windows-p8lbk -c node-driver-registrar
I0215 05:11:00.213354   11600 main.go:164] Version: v2.3.0-0-gde03348b
I0215 05:11:05.455237   11600 main.go:165] Running node-driver-registrar in mode=registration
I0215 05:11:05.455237   11600 main.go:189] Attempting to open a gRPC connection with: "unix://C:\\csi\\csi.sock"
I0215 05:11:05.455237   11600 connection.go:154] Connecting to unix://C:\csi\csi.sock
I0215 05:11:07.765693   11600 main.go:196] Calling CSI driver to discover driver name
I0215 05:11:07.765693   11600 connection.go:183] GRPC call: /csi.v1.Identity/GetPluginInfo
I0215 05:11:07.765693   11600 connection.go:184] GRPC request: {}
I0215 05:11:08.330472   11600 connection.go:186] GRPC response: {"name":"secrets-store.csi.k8s.io","vendor_version":"v0.2.0"}
I0215 05:11:08.330472   11600 connection.go:187] GRPC error: <nil>
I0215 05:11:08.330472   11600 main.go:206] CSI driver name: "secrets-store.csi.k8s.io"
I0215 05:11:08.330472   11600 node_register.go:52] Starting Registration Server at: /registration/secrets-store.csi.k8s.io-reg.sock
I0215 05:11:08.332130   11600 node_register.go:61] Registration Server started at: /registration/secrets-store.csi.k8s.io-reg.sock
I0215 05:11:08.447802   11600 node_register.go:91] Skipping healthz server because HTTP endpoint is set to: ""
I0215 05:11:10.836387   11600 main.go:100] Received GetInfo call: &InfoRequest{}
I0215 05:11:10.838386   11600 main.go:107] "Kubelet registration probe created" path="C:\\var\\lib\\kubelet\\plugins\\csi-secrets-store\\registration"
I0215 05:11:11.689962   11600 main.go:100] Received GetInfo call: &InfoRequest{}
I0215 05:11:11.689962   11600 main.go:107] "Kubelet registration probe created" path="C:\\var\\lib\\kubelet\\plugins\\csi-secrets-store\\registration"
I0215 05:11:11.718140   11600 main.go:118] Received NotifyRegistrationStatus call: &RegistrationStatus{PluginRegistered:true,Error:,}

Hey @luckerby We are tracking an issue https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/639 for windows node. Basically node driver registrar on windows nodes is not working as expected.
Meanwhile could you do couple things:

Since you are on AKS are you using managed AKS add-on for the same? It's the preferred way for using Secret Store CSI driver on AKS cluster.
If not, could you upgrade the provider to stable v1.0.0 release?

@nilekhc We've looked at using the managed add-on, but in terms of actual code it appears to be the same thing we're running now.

Sure.. in terms of code they are same. But with managed add-on you get additional benefit like MS support, use of latest version etc.
Nonetheless, did you try running with latest version of driver?
Also issue https://github.com/kubernetes/kubernetes/issues/104584 related to node driver registrar on windows is still being investigated in upstream k8s.

@nilekhc As for #639, the liveness probe workaround referenced there isn't working for us - as in there's nothing restarting the node-driver-registrar once it "stalls".
As for upgrading, I've noticed v1.1.0 is now available for the provider for a few days now. But given that the underlying kubernetes/kubernetes#104584 is with the Kubernetes repo - as you very well pointed out - wouldn't we have to wait for that to be fixed first? Or is there some workaround that made it in v1+ of the driver that would bypass that problem?

No. For now there is no workaround other than liveness probe.

It turns out that the liveness probe wasn't defined as we were using the wrong Helm chart version as per https://github.com/kubernetes-sigs/secrets-store-csi-driver/issues/911.
I'll close this as it doesn't add any value at this point.

I faced the similar issue in linux nodes, but issue resolve after using the workaround suggested by luckerby https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/798#issuecomment-1039878360.  I think it must be in code to unregister the old  driver and register the new one when we deploy the new version of the csi driver.
Warning  FailedMount  13s (x6 over 28s)  kubelet            MountVolume.SetUp failed for volume "secrets-store-inline01" : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers


Database v2

(See also #313, #161.)
The current database: on naic-monitor, we receive JSON from the network, parse it, flatten it into Sonar-compatible free CSV form, and then append it to a file appropriate for the cluster, the host, and the date.  The data are not augmented or even checked (very much) at this stage.
Advantages of the current database:

tools do not care whether we are operating on locally obtained sonar data (as with sonard) or data ingested by naic-monitor
resilient: problems in the data files can be fixed with a text editor
resilient: files can be moved freely and excerpted easily
testable: it's easy to construct test data

Disadvantages of the current database:

information about the origin of the data is external to the data (namely, the cluster name)
it is complex to "join" the data with the database of system configuration information since the config info is not linked from the data
the data contains redundancies / unused fields (number of cores, amount of memory)
the data are not checked, but have to be checked every time we read them
we have to recompute information every time we need it
data can be corrupted with a text editor
data can be lost: there's no locking, and if we make a mistake in the setup it's possible for two processes to write to a file at the same time

It would be sensible to try to quantify the disadvantages and perhaps look for a different structure that alleviates the problem without getting rid of the advantages.  Even something as simple as a database management process (that can handle locking, caching, annotation) might be appealing.  For simple uses on local data the DB agent could be run synchronously from whoever needs it, while on naic-monitor it would be a process proper.  It would insulate clients from the structure of the database, too.  But I don't want to bias the discussion: we want data first.

While we're thinking about data we should also think about how we want to process it, see #386: Reading everything in the time window we care about into memory and then processing it is not sustainable.  We want a database that is structured enough to allow it to be streamed through a processor.  For this, we need to remove some flexibility, for example, the promise that it's OK for any file to contain data for any host at any time.  (And that's not quite true anyway - we filter based on filename.)  Since everything goes through the ingestor now we can ensure that everything ends up in the correct bucket.  (Existing data can be replayed past a better ingestor, if necessary.)  Data logged to file by sonard might be different but then we can add components to that pipeline instead, because that's a secondary pipeline.

In addition to this, we should think about the data store as a more uniform thing, probably.  Consider that now we have a ClusterConfig which contains only node configuration data, but this object should hold also other things:

post-hoc data filters could go here (for example, older Saga data don't filter properly b/c older Sonar can't do it)
metadata too
clearly the cluster-aliases config file belongs here, not in the separate .js file it is in right now
the state directory could move back into the data store proper (a little trickier but doable, esp with a representational change)

There's a work branch for this, larstha-379-new-sonalyzed, that has some sketches that are very obsolete, but there are comments there that might be useful.
I think that with the closing of #435, the simplest architecture that emerges is:

sonalyzed is folded into sonalyze as a verb server or daemon, this is not much work
naic-monitor runs sonalyze daemon instead of sonalyzed, but the external behavior of that process is otherwise the same as sonalyzed.
the new daemon will serve both ingestion and query, as now, and nginx will forward to it in the normal manner, but since it is always running it can make sure that log files are single-writer-multiple-readers locked, and no separate sonalyze process is spun up for each request
sonalyzed disappears entirely (moves to attic/)
if data caching is necessary (currently the perf w/o caching is pretty good, but if query volume increases that may no longer be so) then caching data in memory and transparently can be done in that process.  there will be a cold-start penalty but that's likely ok.

Meanwhile, sonalyze retains all of its current functionality - it responds to all verbs - and can be run against local and ad-hoc data stores on VMs etc.

Very long discussion with Øystein today.  We're going to implement the architecture that is described in the previous comment, adding in-memory caching and indexing as necessary to serve a high query volume, as he sees a high query volume with a fair amount of redundancy as a likely usage pattern for (un-optimized, but cheap) scripts.  I will spin this off as separate bugs.

We're done here, file separate bugs for followups and link from #517 as necessary.


App Version MisMatch

Please check versioning on your plugin.  Says that <IP_ADDRESS> is installed and the latest is 1.2020.8.5.  I have tried multiple times and it never removes from the list of plugins that need to be upgraded.  I have seen this and experienced with my own connector.  There is a mismatch between versions in the connector, nuget and app assembly.

@JamesStuder ,
Thanks for pointing out this issue, I have released a new version that fixes it


Rules about Epoch start/end times are unclear

The current rules around how a Deme/Epoch's start_time is obtained are fairly clear currently, but it's not obvious to me what we're supposed to do with end_time. Are we assuming that end_time should always be specified for an Epoch, and it's only start_time that can be omitted?
It's not obvious why we would allow for start_time values to be filled in, but not end_time values, since they're equally redundant in either direction. Suppose we have the intervals
[(a, b), (b, c), (c, d)]

Then in principle we have stuff like the following without amibiguity (where X is "null")
[(a, X), (b, X), (c, d)]
[(a, b), (X, X), (c, d)]
[(a, X), (b, X), (c, d)]
[(a, X), (b, c), (X, d)]

Should we allow any mixture of missing values? If so, how do spell out what the rules are? I'm generally finding it a bit icky trying to nail down what the semantics are here on how time "flows" though the epochs and graph nodes.  I'm not a huge fan of the redundancy, but I'm not really seeing a better way to do it. The only thing that occurs to me is to store just the list times=[a, b, c, d] as an attribute of Deme, but that has a whole bunch of its own issues.

Yeah, this has ended up being a bit awkward. I think at different times we've had demes-python accept either missing start_times or missing end_times (or both?). The idea being that we could propagate values starting from the oldest time, or alternately starting from the youngest time. Probably we would encourage users to specify times as either [(a, X), (b, X), (c, X)] or [(X, b), (X, c), (X, d)]. There was some discussion of this in #10. But your examples certainly suggest there are other possibilities.
But isn't the rule just that we need each time in times=[a, b, c, d] to be defined (at least) once?  Concretely, it's something like the following. For [(a, b), (b, c), (c, d)], we first resolve a and d during graph construction (root demes shall default to a=inf; leaf demes shall default to d=0; demes with one ancestor shall have a=ancestor_end_time, with the constraint that a!=0; in all other cases a and d must be supplied by the user). Finally, each of b and c must be supplied by the user at least once.

leaf demes shall default to d=0

I'm not sure this is correct. I think right now we have all demes defaulting to deme.end_time=0. Does this seem appropriate?

That sounds about right @grahamgower.
What would you think about making (say) start_time and attribute of Deme and end_time and attribute of Epoch? So, then there would only be one way of specifying a time for an Epoch, and describing/implementing these rules would be much easier (the alternative might be more appropriate, e.e., making end_time and attribute of Deme, I haven't thought it through).
I'm worried that it's quite easy to mix-up start_time and end_time when you're writing Epoch descriptions, and it could be a source of subtle bugs, as well being a bit of a mess for parser writers.

I don't quite follow. Surely the epoch would still need start_time and end_time attributes. We actually still have both deme.start_time and deme.end_time attributes, but a couple of weeks ago we decided these were redundant with the epoch attributes (and @apragsdale has an open PR to remove the deme attributes, among other things: https://github.com/popsim-consortium/demes-python/pull/172).

Oh, now I see what you mean! I'm not sure if we want that though... let me think about it a while...

So to be concrete, I'm suggesting:
defaults:
    epoch: {initial_size: 1}
demes:
  start_time: a
  epochs:
   - {end_time: b}
   - {end_time: c}
   - {end_time: d}

I don't know if it's a good idea, but it'd be good to explore.

@apragsdale @moldpopgen, any thoughts here? I'm worried that by having both a start_time and and end_time on each of the n epochs, we're then specifying 2n bits of information when we only need n + 1. This leads to a perl-like situation in which there's lots of different ways of specifying the same set of time intervals, when really there should only be one. (This is a good principle from the Zen of Python, I think).
My suggestion is that we resolve this by giving Epoch (say) just a start_time so we can uniquely specify the n time points, and then given Deme an end_time, which specifies the final, bracketing time point (if needed). We could equally do it the other way around like my suggestion above.

So, the concrete proposal seems sensible, and matches up with how some of the exiting examples are written.  For the Gutenkunst model, only the end times are specified.

Sorry for slow replies this week..
Currently, I've got an open PR that made the specification very flexible, where either start or end times can be specified and the function just figures it out how to fill it all in or raise an error for inconsistencies. I'm not a huge fan of what I did there, for the reasons you've mentioned, and I think your example of setting start time for a deme (unless it's inherited from its ancestor, or omitted to default to inf with no ancestors), and epochs just have end time. That means that epoch start times internally inherit from the previous epoch's end time. I think this is the right way to go, where more recent demes and epochs inherit start times from their predecessors.

I still have reservations, but there's certainly multiple appealing reasons to go with this. So lets do it.

@grahamgower would you rather specify that first epoch's start time within the epoch level, instead of the deme level?

Well, yes. But doesn't that defeat the goal of only being able to specifying one time per epoch "boundary", as the start_time could then be given for any epoch?

OK, great, looks like we're converging. The main question is: should an Epoch have a start_time or an end_time? Everything else follows from this.

I think that I prefer end times.  I'm trying to work out (in my head) if one of the other is more/less natural for "ghost" demes that don't make it all the way to the present day sampling time?

just read through this issue-- another vote for explicitly specifying end_time.

Sounds like we're going with end_time!

Would we require that the last epoch has an end_time, or allow something like the final epoch's end_time defaults to zero if not give. Meaning, is this a valid demes description for a single deme that exists for all time with size 100?
demes:
- id: a
  epochs:
  - initial_size: 100

Yeah, I think we still want this. It's a very neat simplification which will be very common in real-world demographic models.

Ok, looks like that's a decision then. I'll implement this in the reference implementation and report by ack.


"DataPeriod":"Minute"  is error

Hi,
I want get a chart with five minute intervals.
http://dev.markitondemand.com/Api/v2/InteractiveChart/json?parameters={"Normalized":false,"NumberOfDays":10,"DataPeriod":"Minute","DataInterval":5,"Elements":[{"Symbol":"AAPL","Type":"price","Params":["c"]}]}
But, this returns null.
{"Labels":null,"Positions":null,"Dates":null,"Elements":[]}
please check it.
thanks.

@vmvz This API is not entitled to intraday data, so your request for a 10 day, 5 minute chart isn't permitted. Try an interday request.

Hi Mark,
Can you elaborate on what you mean by that? In the documentation for InteractiveChart, it explicitly states that you can change the "DataPeriod" parameter to "Hour"/"Minute" and further separate these with intervals using the "DataInterval" parameter. If the API doesn't support this (which is how I interpret your answer), how come it says so in the documentation?
Thanks in advance for helping out!

@markhealey can you show an example URL that would result in minute data (5 minutes)? I've not been able to access intraday data.

Looks like I misunderstood this whole bit about intra and interday! Thanks for the info @markhealey


Block Diagram of how to functionalize SS notebook

DIdn't end up needing to do block diagram because Prof. Brown wrote initial notebook functionally.


Problems with building Docker image

I am building my rails (+ember-cli-rails) app with Docker and having a problems with the bower.
Here is my Docker filer
FROM rails:onbuild

RUN apt-get update -qq && apt-get install -y build-essential nodejs npm nodejs-legacy
RUN npm install -g bower
RUN npm install -g phantomjs-prebuilt

RUN bundle exec rake assets:clean
RUN bundle exec rake assets:precompile

CMD ["unicorn", "--config-file", "./config/unicorn.rb", "--host", "<IP_ADDRESS>", "--port", "3000"]

And when I try to build a docker image (with docker build -t my-app .), I'm getting the following error:
Step 5 : RUN bundle exec rake assets:clean
 ---> Running in 92dc716f9bb0
 ---> 840a3e952f4e
Removing intermediate container 92dc716f9bb0
Step 6 : RUN bundle exec rake assets:precompile
 ---> Running in 8552bb411e37
          ERROR: Failed command: `/usr/local/bin/bower prune && /usr/local/bin/bower install`
          OUTPUT:
            bower ESUDO         Cannot be run with sudo

Additional error details:
Since bower is a user command, there is no need to execute it with superuser permissions.
If you're having permission errors when using bower without sudo, please spend a few minutes learning more about how your system should work and make any necessary repairs.

http://www.joyent.com/blog/installing-node-and-npm
https://gist.github.com/isaacs/579814

You can however run a command with sudo using --allow-root option

The command '/bin/sh -c bundle exec rake assets:precompile' returned a non-zero code: 1

I tracked it down and the command is executed in Shell
https://github.com/thoughtbot/ember-cli-rails/blob/6eceea8a9321e3c38e2425e5f39124912ad297af/lib/ember_cli/shell.rb#L44-L45 but I do not see I can provide --allow-root option to the command.
I also tried changing the bower_path to bower or /usr/local/bin/bower --allow-root but then bower method fails in PathSet (https://github.com/thoughtbot/ember-cli-rails/blob/f510fe8df8ecaf6f50f9b20f8fb02a1263eef9f8/lib/ember_cli/path_set.rb#L65) and it complains that there is no bower installed.
How can I pass this problem? Thanks in advance

I found a solution. I need to execute:
RUN echo '{ "allow_root": true }' > /root/.bowerrc

before RUN bundle exec rake assets:precompile
It is bower issue with docker (https://github.com/bower/bower/issues/1752)


feat(accountLinking): adapt code to support the Account Linking policy

closes AM-653

@tcompiegne , I have approved this PR as it works as expected. One observation is the account link itself. For an example, the following user's idp is the default one. A linked account entry is created once the user logged in successfully.


Add ENV variable ES_MULTILINGUAL_INDEX to default ENV variables

1. Why is this change necessary?
This ENV variable is required to use Advanced Search 2.0, see installation requirements at https://developer.shopware.com/docs/products/extensions/advanced-search/installation.html
2. What does this change do, exactly?
It adds ENV variable ES_MULTILINGUAL_INDEX to default ENV variables
3. Describe each step to reproduce the issue or behaviour.
Run fully licensed Shopware <IP_ADDRESS> with Shopware Commercial installed but no ES_MULTILINGUAL_INDEX set.
The config settings for Advanced Search do not appear in the Administration settings.
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[x] I have written or adjusted the documentation according to my changes

Hey @M-arcus thank you for your contribution. Unfortunately, we have to reject it due to the existing feature flag. We try to offer only a standard setup with a minimum of predefined changes to ensure that it works with every project.

@jinnoflife I will add a feature flag and open a new PR


MF-1361 - Add StringValue and DataValue comparison filters

What does this do?
This pull request adds le, lt, ge, and gt comparators for StringValue and DataValue.
Which issue(s) does this PR fix/relate to?
Resolves #1361, and continues work on #1573.
List any changes that modify/break current functionality
N/A
Have you included tests for your changes?
Yes.
Did you document any new/modified functionality?
Yes.
Notes
N/A

Codecov Report

Merging #1714 (92de296) into master (ada5813) will increase coverage by 0.26%.
The diff coverage is 94.94%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master    #1714      +/-   ##
==========================================
+ Coverage   70.32%   70.58%   +0.26%
==========================================
  Files         148      148
  Lines       11501    11533      +32
==========================================
+ Hits         8088     8141      +53
+ Misses       2745     2733      -12
+ Partials      668      659       -9

Impacted Files
Coverage Δ

readers/api/requests.go
100.00% <ø> (+11.76%)
:arrow_up:

readers/influxdb/messages.go
84.15% <93.02%> (+7.12%)
:arrow_up:

consumers/writers/influxdb/consumer.go
95.45% <100.00%> (+15.86%)
:arrow_up:

readers/api/transport.go
70.49% <100.00%> (-0.24%)
:arrow_down:

readers/cassandra/messages.go
82.40% <100.00%> (+0.33%)
:arrow_up:

readers/mongodb/messages.go
87.34% <100.00%> (-0.32%)
:arrow_down:

readers/postgres/messages.go
85.71% <100.00%> (+0.42%)
:arrow_up:

readers/timescale/messages.go
85.14% <100.00%> (+0.30%)
:arrow_up:

consumers/writers/influxdb/fields.go
100.00% <0.00%> (+35.29%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hello @AryanGodara
I hope the following suggested changes in consumers/writers/cassandra/init.go will fix the problem
At this line Existing Code :
https://github.com/mainflux/mainflux/blob/a039a5d14e18929215c5ea119fbff29d7a8fa830/consumers/writers/cassandra/init.go#L23
Replace with following  :
        PRIMARY KEY (channel, time, id, publisher, name)

At this line Existing Code :
https://github.com/mainflux/mainflux/blob/a039a5d14e18929215c5ea119fbff29d7a8fa830/consumers/writers/cassandra/init.go#L34
Replace with following  :
        PRIMARY KEY (channel, created, id, created, publisher)


Build: Misc. improvements

Removes tests from publishing. #683

Uses new strategy to validate binary after
the download.
Moves mocha under dev-dependencies in
package.json.

Truncates the forth portion from v8 version
as discussed in #710.
Moves pangyp from dev to main dependencies in
package.json.

@andreitognolo, does SnapCI actually build and run the tests? It never fails (even when we have something broken) and reports back success in like 5 seconds! Are we missing something here?


Add XVim2

Add XVim2: Vim key-bindings for Xcode 9
Project URL
https://github.com/XVimProject/XVim2
Category
Extensions (Xcode 8+)
Description
Vim key-bindings for Xcode 9
Why it should be included to awesome-ios (optional)
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

2876
302
http://www.ios-blog.co.uk/ redirects tohttp://www.ios-blog.co.uk/cgi-sys/suspendedpage.cgi

  Generated by :no_entry_sign: Danger