ndb loads dev-tools window. But window stays empty and doesn't respond.

Tell us about your environment:

ndb version: v1.0.42
Platform / OS version: OSX 10.14.1
Node.js version: 8.11.1
using nodenv

Hey all 👋
After working with ndb successfully for a couple of months, it suddenly stopped working for me. running NDB loads the dev-tools screen, but then the window stays "empty": sources pane shows no files. Console tab shows flashing caret, but typing anything and pressing enter does nothing. The node program that is supposed to run in the BG does not run.
I've also tried with a simple "hello world" js file, results are the same.
After a few minutes, the process will emit the following :
<--- Last few GCs --->

[14076:0x103000000]   318621 ms: Mark-sweep 1506.9 (1604.5) -> 1506.9 (1565.0) MB, 2302.6 / 0.4 ms  last resort GC in old space requested
[14076:0x103000000]   320195 ms: Mark-sweep 1506.9 (1565.0) -> 1506.9 (1565.0) MB, 1574.6 / 0.3 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x3f62ebba57c1 <JSObject>
    1: /* anonymous */ [/Users/zappatta/.nodenv/versions/8.11.1/lib/node_modules/ndb/node_modules/chokidar/lib/fsevents-handler.js:~151] [pc=0x21b3e6e4ceb5](this=0x3f624758c571 <FSWatcher map = 0x3f62a00ae0a1>,watchPath=0x3f62c69c4d19 <String[100]: /Users/zappatta/Code/zencity-community/node_modules/es6-iterator/#/get.js/.npmignore/CHANGES/index.js>,realPath=0x3f62c6986929 <String[100]: /Users/zap...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 4: v8::internal::Factory::NewUninitializedFixedArray(int) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 5: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedObjectElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)2> >::GrowCapacity(v8::internal::Handle<v8::internal::JSObject>, unsigned int) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 6: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 7: 0x21b3e6d042fd

another weird but potentially useful information: During those few minutes, I'm seeing a process named ndb/file_system hogging CPU on my machine.
using nodenv to switch to node 10.12.0, ndb seems to work fine.
If there is any more useful information I can provide, please let me know.
cheers 🍻

It looks like you start ndb from the folder with huge amount of files, is it regular project folder?

It looks like you start ndb from the folder with huge amount of files, is it regular project folder?

It is indeed running from a fairly big project with a lot of files. Not sure how irregular it is. But definitely a big one.

I have the same problem. Own source code is < 10 files, but I have pretty fat node_modules folder.
node 8.10.0
osx 10.14.1
ndb v1.0.42
This is the dependency list
{
  "name": "root",
  "version": "0.0.1",
  "devDependencies": {
    "@babel/cli": "^7.2.0",
    "@babel/core": "^7.2.0",
    "@babel/preset-env": "^7.2.0",
    "@babel/preset-flow": "^7.0.0",
    "@babel/preset-react": "^7.0.0",
    "babel-core": "^7.0.0-bridge.0",
    "babel-jest": "^23.6.0",
    "google-closure-compiler": "^20181125.0.1",
    "gulp": "^4.0.0",
    "gulp-babel": "^8.0.0",
    "gulp-plumber": "^1.2.1",
    "gulp-shell": "^0.6.5",
    "gulp-sourcemaps": "^2.6.4",
    "gulp-watch": "^5.0.1",
    "jest": "^23.6.0",
    "regenerator-runtime": "^0.13.1",
    "through2": "^3.0.0"
  },
  "main": "gulpfile.js",
  "scripts": {
    "compile": "npx google-closure-compiler --js=target/bootstrap/index.js --js_output_file=target/out/main.js",
    "watch": "nodemon -x \"gulp watch\" -w gulpfile.js",
    "test": "jest"
  },
  "dependencies": {
    "flow-bin": "^0.89.0",
    "gulp-util": "^3.0.8",
    "immutable": "^4.0.0-rc.12",
    "module-deps": "^6.2.0",
    "multistream": "^2.1.1",
    "ndb": "^1.0.42",
    "react": "^16.6.3"
  }
}

Same here
node v8.15.0
Linux Mint v18.3
ndb v1.0.43
Thanks!

<EMAIL_ADDRESS>uses new version of chokidar. This version is much better optimized to work with huge file trees. Feel free to file another issue or leave a comment here if you still can reproduce this problem.


added new package: request-promise: Request library with promises support.

Why it should be added ?
For beginners, they can find request module in the list, But if they want the same request module with builtin promises support, then this is the package they should check for.
Link to the package: https://github.com/request/request-promise

Request is no longer actively maintained, so doesn’t make sense to add wrappers for it.

Thanks for letting me know. I've still using request module. @sindresorhus


Extend media embed syntax for link URLs

Currently this embed code:
[[http://example.com Caption text.]]

will create this HTML:

Caption text.

If you want to make the image a clickable link, you can't use the embed code and instead have to write this HTML manually:

Caption text.

Current idea for extending the [[ ]] syntax:
[[EMBED_URL OPTIONAL_LINK_URL Optional caption text.]]

This would require the implementation to inspect the second thing after space separation and see if it it looks like a URL. If so, treat it as a link and the thing after the next space as the caption. If not, treat it as a caption. Seems doable.
Where it gets more complicated is if the EMBED_URL or OPTIONAL_LINK_URL are actually paths instead of URLs. A little trickier to discern them from the optional caption text.

I'm open to other ideas.

@bookis @biofilo @guitsaru @faun @gesa @eliduke @carols10cents @astronaut-wannabe @withoutboats @steveklabnik @mutantmonkey

Have you looked at how commonmark or anything does this, if at all?

I just want to make sure I am understanding the terminology here. Is "media embed" specifically talking about 3rd party media (e.g. vimeo, youtube), or is this just going to be how authors type a clickable image into their markdown file?
will this eventually end up being rendered in /articles/embeds/_image.html.erb?
if this is just to let authors more easily include clickable images into their markdown without having to worry about manually typing the HTML for that, then I like your suggestion.

Where it gets more complicated is if the EMBED_URL or OPTIONAL_LINK_URL are actually paths instead of URLs. A little trickier to discern them from the optional caption text.

you could just go easy on yourself and make the syntax something like
[[EMBED_URL link:OPTIONAL_LINK_URL Optional caption text.]]
or
[[EMBED_URL path:OPTIONAL_LINK_URL Optional caption text.]]
to make the regex easier

@steveklabnik I've looked around some. AFAIK, this kind of this is much higher level than any of the Markdown flavors. Even the simple [[URL to heterogeneous media to embed]] is already higher level than what the Markdown flavors do.

@astronaut-wannabe This is what I'm trying to improve for our writers, most of which are not very technical.  Even it wasn't, it doesn't provide an answer for using
 and
 for captions on images.
Also, my [[ ]] media embed syntax addition (that gets processed before Markdown processing) supports more than just images:

audio
video
Tweet
Vimeo
YouTube

And I have plans for others.

Twitter video
Instagram
Vine
Facebook video
and others and necessary

I'm not looking for The Markdown Way™ of doing this thing, I'm looking to create a higher level (opinionated) way of doing this thing that supports our use case. Does that make sense?

@veganstraightedge got it 👍
in that case, I go with my original comment and say your idea seems like the nicest syntax to use while typing articles
I also thought about it more and I also don't think my suggestion of adding link: or path: really adds anything.
The format you suggested is already space delimited on the first 2 tokens

I just pushed #304 based on @veganstraightedge's original suggestion.

@guitsaru I appreciation your gumption! But I want to let this ruminate for a few minutes before deciding on a syntax. I don't want to introduce a syntax, have writers using, realize a change, then have to re-train writers AND change previously used instances of it.

@veganstraightedge I get that, I just happened to have it open and felt like trying.  It doesn't need to be merged yet.

Grool.

when i think about the custom Jekyll tags i've implemented in the past for non-programmers, something resembling html's syntax has been p succesful.  por ejemplo
[[ image=http://example.com/image.jpg link=http://example.com caption="This is a string that non-programmers are surprisingly good at recognizing needs to be in quotes" ]]

or
[[ video=https://www.youtube.com/watch?v=0MUsVcYhERY caption="This is literally the funniest video on the internet" ]]

or
[[ video=http://snaps.akibraun.com/lm54h.mp4 caption="As it turns out this might also be the funniest video on the internet" ]]

the idea being, our code can look at video and try to figure out is this something we already have boilerplate embed code for? ( /youtube\.com/, vimeo\.com ) or do we need to generate a
 with a <video> element? same for audio and soundcloud vs bandcamp vs <audio> and if there's a link param, wrap the whole damn thing in an anchor tag

@gesa I feel like that's too much syntax too.
While, I get it. But it's a lot of punctuation and attr names to remember.
Especially for non-technical folks and ESL folks.

how about
[[ http://object.source.url "Caption in quotes" http://optional.link.url ]]

and we just hold our breath and hope we can parse it?

That's not bad.

How important is backwards compatibility?  If we change how captions are parsed will we need to edit a bunch of articles?

Backward compatibility is not important. We've only used this [[ ]] syntax in a few articles so far. I'm fine with back-fixing them.

@gesa I've noodled on it some more and came to this (I think) conclusion.
[[ https://example.com/path/to/media Optional caption, but with no quotes. /path/to/link]]
[[ https://example.com/path/to/media Optional caption, but with no quotes. https://example.com/path/to/link]]

When parsing, we can still easily separate by space, then if if the thing after the last space looks like a URL or a path that must start with a slash, then we link it. Otherwise, its behavior works as it does today.
As it turns out, that also gives us backward compatibility. And that's a nice little bonus.
Any objections to this syntax?

@guitsaru Would you like to adjust your PR to work with this syntax?

@veganstraightedge Yup, updated #304.


fix: fix ineffectual assignments

Ⅰ. Describe what this PR did
Fix ineffectual assignments. As follows:

dfget/core/core.go
Line 118: warning: ineffectual assignment to port (ineffassign)
dfget/util/http_util.go
Line 140: warning: ineffectual assignment to err (ineffassign)
supernode/daemon/mgr/dfgettask/manager_test.go
Line 88: warning: ineffectual assignment to dt (ineffassign)
supernode/daemon/mgr/scheduler/manager.go
Line 196: warning: ineffectual assignment to err (ineffassign)
supernode/daemon/mgr/peer/manager_test.go
Line 131: warning: ineffectual assignment to err (ineffassign)
Line 133: warning: ineffectual assignment to err (ineffassign)
Line 142: warning: ineffectual assignment to err (ineffassign)
Line 144: warning: ineffectual assignment to err (ineffassign)
dfget/core/uploader/peer_server_executor.go
Line 106: warning: ineffectual assignment to n (ineffassign)
Line 107: warning: ineffectual assignment to portValue (ineffassign)
common/util/http_util_test.go
Line 71: warning: ineffectual assignment to code (ineffassign)
Line 71: warning: ineffectual assignment to body (ineffassign)
Line 86: warning: ineffectual assignment to code (ineffassign)
Line 86: warning: ineffectual assignment to body (ineffassign)

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Thanks for your work. @KevinBetterQ
Minor request there. PTAL

Thanks for @Starnop and @lowzj 's feedback. Things much more clear now. @KevinBetterQ

Thanks for @Starnop and @lowzj 's feedback. Things much more clear now. @KevinBetterQ

OK. I will commit another version as described above.

Codecov Report

Merging #519 into master will decrease coverage by 0.39%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master     #519     +/-   ##
=========================================
- Coverage   54.56%   54.16%   -0.4%
=========================================
  Files          83       82      -1
  Lines        4274     4233     -41
=========================================
- Hits         2332     2293     -39
+ Misses       1789     1786      -3
- Partials      153      154      +1

Impacted Files
Coverage Δ

supernode/daemon/mgr/scheduler/manager.go
25.4% <0%> (-0.82%)
:arrow_down:

dfget/util/http_util.go
0% <0%> (ø)
:arrow_up:

dfget/core/uploader/peer_server_executor.go
91.37% <100%> (-0.43%)
:arrow_down:

dfget/core/core.go
53.64% <100%> (-0.31%)
:arrow_down:

supernode/store/local_storage.go
71.22% <0%> (-3.63%)
:arrow_down:

supernode/store/store.go
58.13% <0%> (ø)
:arrow_up:

supernode/store/errors.go

Continue to review full report at Codecov.

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

LGTM, but I would like to invite @Starnop to take another look.

LGTM.


Closure sizes

This PR introduces changes to reduce the closure size of our deployments:

buildPursProject: npm dependencies are split into production and dev dependencies. The latter can be removed when deploying. This PR runs npm prune to reduce the node_modules folder to production dependencies. The playgrounds don't actually need the node_modules at all and the change removes the node_modules from the closure completely.
runtimeGhc closure: The closure of the server-invoker is gigantic. This PR changes the packages added via ghcWithPackages somewhat which reduces the scope.
haddock data: The plutus-playground tutorial contained the complete haddock site data even though it isn't viewable (and not supposed to be viewable) as part of the tutorial. This makes for a difference of 800mb+ in the closure

Notes:

Unfortunately i don't have figures available right now but there was a 1GB+ different in the closure size for initial deployments of the playground configurations.
For testing I started the playgrounds locally (npm start) and then ran the server-invoker and tried compiling all available examples

Pre-submit checklist:

Branch

[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] nix-shell shell.nix --run updateMaterialized to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[ ] nix-shell shell.nix --run fix-stylish-haskell to fix any formatting issues

If you changed any Purescript files:

[ ] nix-shell shell.nix --run fix-purty to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

I thought the haddock was accessible from the Playground, and linked to from the tutorial?

I thought the haddock was accessible from the Playground, and linked to from the tutorial?

I couldn't (easily) find a way to access it. From skimming over the tutorial there was no clear link to it either.
Considering the fact that the tutorial iltself is just a few MBs and haddock is like a GB it would actually nice if it does NOT have to be part of it :sweat_smile:  -- @j-mueller  ?

unless i'm misunderstanding @gilligan it's linked at the top of the page right next to the "tutorial"; it's the "API" link:

i believe these changes will definitely impact https://github.com/input-output-hk/plutus/pull/2858 but i can fix that after the fact
i did think we did want the haddocks available though?

@silky oh wow - how did I manage to miss that. Well in that case I suppose I will have to add back the haddock stuff but maybe rephrase my question:
@michaelpj @j-mueller The haddock weighs in with a whooping 845MB closure size ;( It doesn't only provide docs for plutus/marlowe internal packages but plenty of external packages also - I suppose we could limit it to Plutus/Marlowe packages?

We don't have any other location where the haddocks are hosted publicly, so I would like to keep them in the Playground.
Ideally we would link to hackage haddocks for all non-iohk packages, but this seems fiddly. Failing that, removing all those other packages from our haddocs is OK.
I am a bit surprised at the size though!

https://gist.github.com/gilligan/4b15a3022f8186a5adf0b82ae8e39d97
821MB in total.
I am pretty sure it would be much smaller if it was only for our packages. The haddocks stuff is created in https://github.com/input-output-hk/plutus/blob/closure-sizes/nix/lib/haddock-combine.nix. Looking at nix/pkgs/default.nix i see:
  # combined haddock documentation for all public plutus libraries
  plutus-haddock-combined =

which appears to be misleading because it does actually include all dependencies. From what I understand @silky is currently working on that. Maybe there is a way to fix that? I have no idea at all if this would be straight forward or super complicated.


Performance issues - FIFO / UDP streaming

Note: I've already posted this on Gitter, but I'm adding it here, so we can keep track of this issue.
Sometimes, artefacts are popping up in the video stream (FIFO & UDP). This is due to lost buffers, caused by a demanding / slow buffering mechanism.
I've profiled the application using Callgrind (QtCreator 4.0):
callgrind.zip
Problem seems to be std::vector, which dynamically allocates 16384 (DATA_BUF) elements per loop. Also, std::queue< std::vector > seems to have performance issues on several operations.
Possible fix: use static array std::array. Also, we might need to think about a new buffering mechanism aswell.
Cheers,
Tolga

Okay, I've worked on this a bit. std::array offers much better performance in our use case. Still not perfect for UDP mutlicasting, but much better than before. The artefacts are completely gone for FIFO; UDP unicasting is also near perfect.
Gonna push out the changes soon. I'm still not satisfied with performance, I'm leaving this issue open, until performance is perfect.

I was able to reproduce this error on my Mac machine, featuring an Intel Xeon E3-1225v3. This is not due to performance, but due to an unefficient writer / reader thread algorithm. I also saw performance issues on an system featuring the Intel Core i3-4005U CPU. Definitely needs further optimizations.
Writer thread is much faster than reader thread. While writer thread receives a series of data arrays from the device, it doesn't let reader get in between and read from the queue. This causes some queue items getting lost, leading to glitches / artefacts.
Maybe, we shouldn't use std::queue at all and keep things simple and fast, by just writing and reading from an array, using std::mutex, synching threads with a std::condition_variable and a bool newDataAvailable.
As thread programming is not the easiest thing in life, I'm thankful for any suggestions (like always).

I've came up with some ideas on this issue.
After installing the latest official Elgato drivers on my Windows machine and investigating USB traffic, I've noticed, that they've set up a higher buffer size. Instead of the former 16384 (0x4000), they're now using 61440 (0xf000). A quick test showed me, that getting 16384 bytes from the devices takes around 700µs, while getting 61440 bytes takes around 2000µs. This leads to less needed locks and less loops, thus beeing more efficient. Downside is of a greater buffer is more lag.
Also, instead of locking, reading and popping single elements from the queue, I came up with the idea of moving over the entire queue to the reading thread on thread wakeup, by swapping out the current queue with an empty queue (using std::queue::swap). This way, the reading thread will be able to process the whole queue, without requesting a lock for every single queue item.
While doing some research, I also read about an idea of "queue of queues", which I really liked. I'll look into that aswell.

Update on this: I'm now sticking with the old behaviour. However, peaks need to be taken care of. Sometimes, the reader slows down and we have new data arriving. There is need for some type of temporary bounded queue, so we don't get corrupted output / artefacts etc.
It's going to be a bit complicated, but I'm eventually getting it sorted out. Once this bug is fixed, I will update to version 0.2.0.

Commit 1b26b5dae2ca2dafb98f546723a62161e9dd12af should fix this issue.
I've completely redesigned FIFO handling. My personal tests were successful, but I need broader testing. Please checkout master branch, test and post your feedback here. Also, please post your system details (CPU, RAM, GPU, OS / Distro). I will mark 0.2.0 as soon as few people tried it out successfully.
Cheers,
Tolga

Commit 1b26b5dae2ca2dafb98f546723a62161e9dd12af totally breaks Mac OS X support. Guess, it's not going to be fixed this way...
Reimplementing the old behaviour, without polls and stuff will leave the device in an unresponsive state, as soon as the FIFO get's paused. Closing FIFO is no problem though. The official drivers are able to recover from such an unresponsive state - so we can reverse-engineer it in the future.
On the other hand, trying to workaround #13 created this issue, which is far worse than the original issue. So, the best thing to do is: reverting changes and reopening issue #13.


added cost function to minimize comddot

I added a cost function, i think this commit should be added to your current pull request, since it concern the same type of feature.

done


Fix Azure Core Http Sample Issue

Fixes https://github.com/Azure/azure-sdk-for-js/issues/20668
@xirzec, @deyaaeldeen, @jeremymeng for notification.

/check-enforcer override


add PlayerChatTabCompleteEvent

Use case:
conversation commands: using the chat as command and providing other than default player tab-completion

This issue was about tab-completion in chat.
The commit adds an event for tab-completion in commands.

@zml2008 while you added an event for command completion, @Faithcaio was asking for completion no matter the given text, meaning that he wanted to complete normal chat text that was not specifically a command.

I can add this event but need some details.
For starters, does hitting tab send your current chat text up to the server?


Port forward to a service instead of pod

@aseovic have tested this works fine. Much simpler :)
I also added --namespace sockshop to the operator install.
Let me know if ok.


Example apps are broken if they use the old version of settings.gradle

After https://github.com/flutter/flutter/pull/97823, some builds break if the app uses the older version of settings.gradle.
For example, webview_flutter_android:
 Where:
Script 'flutter/packages/flutter_tools/gradle/flutter.gradle' line: 509

* What went wrong:
A problem occurred configuring project ':path_provider'.
> Failed to notify project evaluation listener.
   > Could not find method implementation() for arguments [project ':path_provider_android'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
   > Could not find method implementation() for arguments [project ':path_provider_ios'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
   > Could not find method implementation() for arguments [project ':path_provider_linux'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
   > Could not find method implementation() for arguments [project ':path_provider_macos'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
   > Could not find method implementation() for arguments [project ':path_provider_windows'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

This can be fixed by updating settings.gradle to the latest version:
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/templates/app_shared/android.tmpl/settings.gradle
cc @GaryQian for the migration tool
cc @stuartmorgan

Migration tool will be able to handle this case.

Is this important enough to revert https://github.com/flutter/flutter/pull/97823 for now? It seems that it is more common for apps to use legacy settings.gradle than use iOS only plugins

yes, let's revert it for now, and reland after the migration tool lands.

than use iOS only plugins

It's more of an edge case than that; it's using a plugin that doesn't support Android but has an Android folder. (Most likely due to sloppy updating of a plugin that used to have a dummy Android implementation since that used to be required.)

The revert #98050 was landed. Is there still an open task that this issue is tracking?
(I see that when the revert landed, the issue was lowered in priority but kept open: https://github.com/flutter/flutter/issues/98048#event-6030507472 )


updated php phar file, so we can get those nice relations map, evalua…

updated phpmetrics.phar file, so we can get those nice relations map, evaluation, and so on :)
IMPORTANT
I've tested the new jar plugin on my machine, but unfortunately it doesn't work properly.
I haven't enough java skills to find and debug what is going on. But I sincerely expect that this pull request motivates you in order to make it work.

Hi,
I'm really sorry for the delay :( Please excuse me...
This repository is now managed by organisation, I hope that these problems will not occur henceforth.
I close this PR: PhpMetrics has a lot of changes between your PR.
Thanks a lot for your contribution !


Add RubyOnRails example

cc @bobvanderlinden

macOS:

/Users/runner/work/devenv/devenv/examples/rubyonrails/.test.sh: line 5: timeout: command not found

Ugh, maybe the tests should get a separate nix file that is used on top of the devenv.nix in the example. Include all of the environment that is needed for the test in there (bash, curl, etc)?

I've added a section that injects the packages.
Maybe we could also add helper functions for testing, but that's for later.


Multiple Bases

Installed via HACS, then when configuring the integration it only saw 1 of two bases. Went checked everything out all seemed to be good except the only seeing 1 of 2 bases. Tried reload on the integration and it added the 2nd bases, but now the 1st base entity shows as unavailable.
Thank you for developing this! If there is anything I can do to support the project please let me know!

Hi @Leko1933  - I've created version 0.0.3 that I believe fixes the issue and also adds some additional logging. Give this a try, if it does not work, please enable log level debug in your HA, remove the integration and re-add the integration. I am looking for lines that are like this:
2020-12-28 22:50:33 DEBUG (MainThread) [custom_components.tryfi.sensor] Adding Base: Last Updated - 2020-12-28 22:50:33.444726 - Base ID: FB19M56049 Name: Main Floor Base Online Status: True Wifi Network: ChelseaFC-Infra

Just updated and it looks like you got it! Both bases are showing same last updated now. Thank you!

Awesome. Thanks for confirming!


[formrecognizer] Build model update

TODO changelog

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-formrecognizer


NCU Reader Support for RAJA_CUDA and Lambda_CUDA

tldr:

Support Lambda_CUDA and RAJA_CUDA variants by using demangled kernel names.
Add debug flag to see detailed information about kernel matches, so we can preliminarily investigate future issues without editing the source code.
Support cub kernels via string similarity to compare function signatures.

Description
Enables support for reading NCU report profiles for RAJA_CUDA and Lambda_CUDA variants and cub kernels by using the demangled action name.
The current Thicket NCU reader matches nodes in a Caliper cuda_activity_profile (CAP) and NCU report file by checking if an action in the report has the name action.name(_ncu_report.IAction_NameBase_FUNCTION), which for Base_CUDA is the name of the kernel (e.g. daxpy, energy1, or energy2). This name can be found in the CAP node name kernel_name in node.frame["name"].
For RAJA_CUDA and Lambda_CUDA, the above assumption does not hold, as the values for action.name(_ncu_report.IAction_NameBase_FUNCTION) will not be the kernel names. However, the kernel names are still embedded in the action.name(_ncu_report.IAction_NameBase_DEMANGLED) demangled action name. This PR parses the demangled name to match the nodes in the CAP, which also works for Base_CUDA profiles.
For cub kernels, there may be kernels with the same name, but different function signatures. For example, matching the ncu kernel void cub::DeviceRadixSortDownsweepKernel<cub::DeviceRadixSortPolicy<double, double, int>::Policy700, false, false, double, double, int>(const T4 *, T4 *, const T5 *, T5 *, T6 *, T6, int, int, cub::GridEvenShare<T6>) to the first DeviceRadixSortDownsweepKernel in the following calltree:
nan RAJAPerf
└─ nan Algorithm
   ├─ nan Algorithm_SORT
   │  ├─ nan cudaLaunchKernel
   │  │  ├─ 1016096.000 void cub::DeviceRadixSortDownsweepKernel<cub::DeviceRadixSortPolicy<double, cub::NullType, int>::Policy700, **false, false**, double, cub::NullType, int>(double const*, double*, cub::NullType const*, cub::NullType*, int*, int, int, int, cub::GridEvenShare<int>)
   │  │  ├─ 1399520.000 void cub::DeviceRadixSortDownsweepKernel<cub::DeviceRadixSortPolicy<double, cub::NullType, int>::Policy700, **true, false**, double, cub::NullType, int>(double const*, double*, cub::NullType const*, cub::NullType*, int*, int, int, int, cub::GridEvenShare<int>)

We use similarity matching using the standard library difflib SequenceMatcher to match the two, after first narrowing the search down to the Algorithm_SORT part of the calltree.
NCU kernel support by variant:
This PR (#201)

Base_CUDA
Lambda_CUDA
RAJA_CUDA

rajaperf kernels
✓
✓
✓

cub kernels
✓
✓
✓

kernels with multiple instances
✓
✓
✓

Develop

Base_CUDA
Lambda_CUDA
RAJA_CUDA

rajaperf kernels
✓
x
x

cub kernels
x
x
x

kernels with multiple instances
✓
x
x

Changing this PR to "work in progress" because there are complications due to mismatches in demangled kernel names from Caliper and NCU.

See https://github.com/LLNL/thicket/tree/rajaperf-paper

Changing this PR to "work in progress" because there are complications due to mismatches in demangled kernel names from Caliper and NCU.

Addressed in new changes.

This PR supersedes https://github.com/LLNL/thicket/tree/rajaperf-paper branch used for the rajaperf paper.

Do you want to remove the rajaperf-paper branch on this repo?

This PR supersedes https://github.com/LLNL/thicket/tree/rajaperf-paper branch used for the rajaperf paper.

Do you want to remove the rajaperf-paper branch on this repo?

Done


[docs] Create How to Contribute page

We'll need a "How to Contribute" page. Should contain information for getting involved in the open source project on GitHub, whether through submitting an issue, developing features or fixing bugs, etc.
See #1150 for proposed outline / IA along with "Getting Started" section rewrite:

Contribute***

Overview
Bugs and requests
Documentation
Components
Icons
Patterns

Not sure how to tackle getting involved in the design. Possible a VPN handoff to an internal page?

[ ] Write content
[ ] Design page
[ ] Build page

Related: https://github.com/orgs/RedHat-UX/discussions/1150


Scope of receiving coins tab might not be obvious

On Reddit /u/JuicyGrabs wrote:

The Receive section also needs a remake. You can't have two Send Omni / Send Bitcoin tabs in Send area and just one Receive Bitcoin tab in the Receive area. It confuses the user.

You might want to consider new/different input fields in Receive menu. It's confusing to an average user to be able to send Omni coins or other coins and only be able to receive Bitcoin according to the interface.

Right now I'm not really sure how to tackle this, given that I personally never use the receive section, except for generating new addresses, but let's try to brainstorm a bit.

Interesting feedback, I'm the same I don't use the receive dialog, that's more for generating "requests for payment" I thought, but if it has the potential to cause confusion perhaps we should look at a way to do a request for payment in an Omni token - I'll take a look :)

I guess it's best to see things from the perspective of someone who's not in the know so to speak.
Imagine a user who just wants to use this wallet to store, send/receive and trade Maidsafecoin for example. Said user might not even own any Bitcoin and he's only interested in playing around with Maidsafecoin. When he opens up the wallet he will see the send tab which would probably include a list of all the coins available on Omni platform. Imagine the confusion if the receive address displays a receive Bitcoin address instead of a Maidsafe address. The user shouldn't know what's behind the hood so to speak and how the send/receive mechanics work. He would probably just think something along these lines : "WTF, I don't want to receive BTC. What is this shit?"

Very good points.

The send option should only display these two coins and perhaps also feature an expand button to reveal empty balances.

Agreed, this would be great.

Receive tab should only include coins currently held in the wallet.

receive address separately based on what coins the user holds

So basically you suggest that there should be some kind of categorization of the addresses generated via the receiving tab, like "Bitcoin", "MaidSafeCoin", ..., and when an user creates a new address, then he or she should be able to select a category (= the token to receive)?

Yes, something like that.

Say a user has 100 Maidsafecoins and 50 Omni/Mastercoins. The send option should only display these two coins and perhaps also feature an expand button to reveal empty balances.

The send option should only display these two coins and perhaps also feature an expand button to reveal empty balances.

Agreed, this would be great.

Can I just clarify something here guys, are you saying that you get a list of all tokens in the send dialog, even those where you don't have any balances?  If so that's a bug & shouldn't occur.
There is code within sendmpdialog.cpp that should ensure that tokens are added conditionally to the property selector, only if >0 balance for that property id...
if ((global_balance_money[propertyId] > 0) || (global_balance_reserved[propertyId] > 0)) {

Apologies if I've missed the point here, and the feedback regarding the receive tab is appreciated & will be addressed :)

Can I just clarify something here guys, are you saying that you get a list of all tokens in the send dialog, even those where you don't have any balances? If so that's a bug & shouldn't occur.

Correct, addresses with zero tokens are hidden. I could see some value to have a checkbox to hide addresses with zero BTC though, if this doesn't require endless wallet queries. I could be biased by the regtests though, given that a long list of addresses is usually the last state. On the other hand, if there were such a feature, addresses with tokens may be overlooked, only because the filter is active.

I could see some value to have a checkbox to hide addresses with zero BTC though, if this doesn't require endless wallet queries.

The difficulty here is that we don't maintain an internal tally of BTC balances per address, and the wallet maintains BTC balances by way of outputs, rather than by address.  What's the value of hiding addresses with zero BTC in the context of sending Omni tokens?  Just that an address without BTC doesn't have sufficient fees for a send?
I'm sure we could do it, especially since I want to take us in the general direction of BTC balances per address to enable the display of BTC as an entry in the "Balances" page (Bitcoin Core as of 0.11 still doesn't provide an easy to use method to get an address balance, so we could contribute something upstream at least on the RPC side) and simplify code around fee warnings and such, but I'm not sure I agree we should do offer filtering of empty BTC balances when looking at the context of Omni balances, mainly because of the potential for user confusion.


react-native package inside notifee/packages/react-native still contains old code.

I installed version 7.0.1 and was expecting to get features of Android 13 (sdk 33) . but after some compile issues found that it's using old unupdated code which is inside notifee/packages/react-native which is still not yet updated to support sdk 33.

Thanks @nateshmbhat for bringing this to our attention. This has been fixed in the latest release v7.0.3


ci(cypress): setup Cypress.io record key

Codecov Report

Merging #191 (f775984) into develop (7422cc2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #191   +/-   ##
========================================
  Coverage    98.09%   98.09%
========================================
  Files           85       85
  Lines          842      842
  Branches       167      167
========================================
  Hits           826      826
  Misses           9        9
  Partials         7        7

Continue to review full report at Codecov.

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


fix raidboss CN zoneRegex,update oopsyraidsy E2S mistake CN translation

I already submitted a fix for all the raids CN zoneRegex problem. Can you move the other updates to another commit?


prefer qmake-qt5 over qmake

Fixes build on systems where qmake belongs to Qt4 (e.g. openSUSE Leap 42.3)

Thank you for the patch.


Does LFS works with lua 5.2.3?

I installed LFS via luarocks, and then executed require 'lfs' on the interpreter, and that is what I got:
version mismatch: app. needs 503, Lua core provides 502
stack traceback:
    [C]: in ?
    [C]: in function 'require'
    stdin:1: in main chunk
    [C]: in ?

I don't know what these numbers mean, but the version mismatch struck a cord in my head. Does LFS works with lua 5.2.3?
I use Linux Mint 17.3.

Hi Rafael. It should work with no problems, yes. This is a mismatch between the Lua version used by LuaRocks and the Lua version of your interpreter.
By the numbers (502 and 503), it seems that you are mixing Lua 5.3 with Lua 5.2

Oh, Lua 5.3? That is weird...
lua -v
Lua 5.2.3  Copyright (C) 1994-2013 Lua.org, PUC-Rio

And luarocks says
LuaRocks 2.3.0, a module deployment system for Lua

...

CONFIGURATION
    Lua version: 5.2
...

Am I missing something?

What about your lua.h headers? Maybe you have a devel package for Lua 5.3 installed?
Check the version of Lua reported in your lua.h file.

The headers were really from Lua 5.3... I fixed it, and now it works. Thanks!


Thing

I actually started writing something EXACTLY LIKE THIS in python (AstroOrbis/PuzzleHacker)! I was just wondering if I should just implement my python code into pull requests here...

New contributions are welcome!🙂  Most of the code is in Javascript here, and you can checkout the issues to see specifically what needs implementing.

Thanks! I'll work on my python version on my repo...


Hyundai: Longitudinal support for CAN-based Camera SCC cars

openpilot longitudinal control support for CAN-based HKG cars that have the following messages send from the car on bus 2:

SCC11
SCC12
SCC13
SCC14
FCA11
FCA12

Currently with 2022 Hyundai Kona EV, without radar disable. As the messages send from the car on bus 2, we block the messages and send our own longitudinal commands to bus 0.
route:
Supported platforms:

2022 Hyundai Kona
2022 Hyundai Kona EV

Requires

https://github.com/commaai/panda/pull/1107

Thanks to community Kona EV 2022 owner Zack1010OP.

Will this enable longitudinal support for Sonata 2018? @sunnyhaibin

No, it does not. The Supported Platforms section in the description of this PR mentioned this.

@sshane Can we please add ignore-stale tag to this PR?

@sshane What else is needed for this PR? Multiple users have been using openpilot longitudinal with this change on sunnypilot and working as we expected.

We've moved the car interfacing code to our opendbc repository, which is now the new home for car ports and fingerprints. Please re-open your pull request against opendbc at your convenience by using this command below. This will transform all changes under selfdrive/car/ to opendbc_repo/opendbc/car/. Make sure you have initialized submodules beforehand and have checked out the latest opendbc commit.
PR_NUMBER=33045
curl -L https://github.com/commaai/openpilot/pull/$PR_NUMBER.patch | sed -e 's/selfdrive\/car/opendbc_repo\/opendbc\/car/g' | git apply -v --reject

Simply replace the PR number with your own. Once done, add the files, fix any conflicts, and open a new PR. Alternatively, you may start a new PR from scratch if that is easier for you.


Resnet50 performance failing

Re-enable the RN50 perf tests in CI.
Archive:
As title. After removing the 1x1s2 fallback to matmul path, the GS test is failing.
Arch: GS
Command:
pytest -ssv tests/ttnn/integration_tests/resnet/test_performance.py
pytest -ssv tests/ttnn/integration_tests/resnet/test_ttnn_functional_resnet50_new.py
pytest -ssv tests/ttnn/integration_tests/resnet/test_ttnn_functional_resnet50.py
pytest -ssv tests/ttnn/integration_tests/resnet/test_ttnn_functional_resnet.py

Error
Statically allocated circular buffers in program 18 clash with L1 buffers on core range [(x=0,y=0) - (x=11,y=7)]. L1 buffer allocated at 384000 and static circular buffer region ends at 435520

@tapspatelI resnet-50 with new conv API is passing (file "test_ttnn_functional_resnet50_new.py"). Are we still supporting old conv?

Old conv is still supported, but this issue can be closed now that it is good on GS.


Tobiasb/use branch from build for tests

DRAFT: IGNORE
What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall First build on tobiasb/use-branch-from-build-for-tests at 61.524%

Totals

Change from base Build<PHONE_NUMBER>:
61.5%

Covered Lines:
2560

Relevant Lines:
4161

💛  - Coveralls


Sort layers before the loop

Issue #34479, #32672
Layer names sometimes contain hierarchy char "/", e.g., "Layer1", "Layer1/SubLayer1", etc.. Since for each layer, we create a new group, so if we pass layers whose name like "Layer1/SubLayer1", it would create both "Layer1" and "Layer1/SubLayer1", afterwards, if we pass "Layer1", it will throw "Unable to create group (name already exists)" error.
This commit solves the issue by sorting the layers by name before the loop.

I've recently encountered described bug and found this way your commit. Shouldn't similar sorting be inserted in load_weights_XXX methods?

@fchollet Can you please take a look at this PR? Thanks!

@gekowa Can you please resolve conflicts? Thanks!

It has been 16 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!


pio: allow programs with 32 instructions

The PIO library currently errors when trying to find an offset for PIO programs with exactly 32 instructions.
I assume that this is a bug (?), because pioasm only errors (correctly) when a program has 33 instructions or more.

Needs to be PRed against the develop branch rather than the master branch, but this LGTM :+1:

Needs to be PRed against the develop branch rather than the master branch, but this LGTM

I see, done!


How to access shadow map in custom shader?

I want to access shadow map in custom shader to compute some materials'(such as marble, skin) thickness。But I found the obtained value is still > 1.0。 Here is my shader:
uint cascade = getShadowCascade();
float value = texture(light_shadowMap, vec4(base, cascade, position.z));
What's the correct way to access shadow map?

There is no "correct" way since shadow maps are not part of our public shader APIs. They may or may not be cascaded, they may be PCF or VSM, etc. The way we store shadow maps (currently in a 3D texture) is also subject to change and we make no guarantee about the stability of those APIs.
In your case what is position.z? The shadow map requires a depth value in the 0..1 range so you need the light space position. Note that we may also be using reverse Z.


kubecontext: fix context, namespace comparison

Maybe the original author happened to name their context k8s_namespace 🤔

Good catch @krmcbride !
Summoning @iScrE4m , @zikes and @captjt for better Review :)

Thanks for doing this, I was actually embarassed to fix it, hoping noone else was naming them the same. Now my shame every time I look at the prompt can go away.

LGTM :+1:
Slightly related, but I recently discovered https://github.com/jonmosco/kube-ps1 and it might be worthwhile integrating that somehow rather than "rolling our own" :thinking:

Thanks so much for the fix, @krmcbride, and thanks for the reviews @iScrE4m @zikes @captjt! Great work all around. Welcome to P9k @krmcbride :)
Interesting idea @zikes! I'll check it out.


[Bug]: node.data, node.ingest, and node.master deprecation

Describe the bug
Upon starting v1.0.0, depreciation warnings are generated for the node.data, node.ingest, and node.master configuration options although they appear in the current documentation.
{"type": "deprecation", "timestamp": "2021-10-05T11:26:37,811-07:00", "level": "DEPRECATION", "component": "o.o.d.c.s.Settings", "cluster.name": "T4", "node.name": "node1.0", "message": "[node.master] setting was deprecated in OpenSearch and will be removed in a future release! See the breaking changes documentation for the next major version." }
{"type": "deprecation", "timestamp": "2021-10-05T11:26:37,814-07:00", "level": "DEPRECATION", "component": "o.o.d.c.s.Settings", "cluster.name": "T4", "node.name": "node1.0", "message": "[node.data] setting was deprecated in OpenSearch and will be removed in a future release! See the breaking changes documentation for the next major version." }
{"type": "deprecation", "timestamp": "2021-10-05T11:26:37,814-07:00", "level": "DEPRECATION", "component": "o.o.d.c.s.Settings", "cluster.name": "T4", "node.name": "node1.0", "message": "[node.ingest] setting was deprecated in OpenSearch and will be removed in a future release! See the breaking changes documentation for the next major version." }

I did not see any mention of these in the release notes either.
To reproduce
Define the following in the opensearch.yml file:
node.master: false
node.data: true
node.ingest: true

Expected behavior
If these are in fact deprecated, the documentation should provide the replacement configuration options otherwise a warning should not be generated.
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
Ubuntu 18LTS
Additional context
No response
Relevant log output
No response

This issue is being tracked in the OpenSearch repository, see https://github.com/opensearch-project/OpenSearch/issues/1238 for the specifics


🚀 Feature: Make PostgreSQL search accent-insensitive

🔖 Feature description
Search should be able to match keywords regardless of accented characters.
🎤 Context
We have accented characters in the catalog. Entities that include accented characters are hard to find using search.
For example, an entity titled "Ömer" cannot be found when "Omer" is queried (or vice versa).
✌ Possible Implementation
We can use the unaccent extension while generating the body column in the documents table, and also while performing the query.

table.specificType(
  'body',
  'tsvector NOT NULL GENERATED ALWAYS AS (' +
    "setweight(to_tsvector('english', unaccent(document->>'title')), 'A') || " +
    "setweight(to_tsvector('english', unaccent(document->>'text')), 'B') || " +
    "setweight(to_tsvector('english', unaccent(document - 'location' - 'title' - 'text')), 'C')" +
    ') STORED',
);

tx.raw("documents, to_tsquery('english', unaccent(?)) query", pgTerm)
The unaccent extension is not installed by default, so we should execute CREATE EXTENSION unaccent to install it first. For PostgreSQL 12 and below, this command requires the user to be a superuser on the database, which might be a problem. This requirement no longer exists since PostgreSQL 13:

This module is considered “trusted”, that is, it can be installed by non-superusers who have CREATE privilege on the current database.

👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

@iamEAP Would you have any comments on this? If this is not possible, we will consider using Elastic search engine.

Hey!  Thanks for the tag @omerfarukdogan.
When one uses the unaccent extension (both at query/index time), does that actually affect the way the data is stored?  (e.g. if you searched for user Ömer, would it return the user entity, but with the title of the document showing as Omer?
Separately, I'm thinking we'd likely want to make this behavior configurable, rather than the default/only way (I can imagine locales/cases where users would not want this behavior).  If you can imagine a way to implement this where users could enable it via some kind of configuration (whether in config or code), I think we'd be open to it!
But otherwise, it might be easier for you to achieve this using the ES search engine + text analyzers + template / mappings.

Hello @iamEAP,
The data itself (stored in the document column) doesn't have to be affected by this. We can only change the way text search vectors (stored in the body column) are generated.
I am not familiar with Knex migrations. Is it possible to dynamically generate or apply specific migrations based on a parameter? We could ask the user during the project initialization (npx @backstage/create-app command) and modify how the body column is generated. Or is it possible to apply/rollback migrations conditionally during app startup so we can check a parameter in app-config?

@iamEAP Unfortunately I don't know.


How do I write a package that I can adjust the

Basically I would like to make my pre-processing of fastcache to be done so I can assign the size of the cache inside my program instead of directly on fastcache.
How do I do this?

import(
        "github.com/VictoriaMetrics/fastcache"
)
type Cache struct {
        Cache fastcache
}

func New(maxBytes int) *Cache {
        if maxBytes <= 0 {
                panic(fmt.Errorf("maxBytes must be greater than 0; got %d", maxBytes))
        }
        //      var c fastcache.Cache
        //      maxBucketBytes := uint64((maxBytes + bucketsCount - 1) / bucketsCount)
        //      for i := range c.buckets[:] {
        //              c.buckets[i].Init(maxBucketBytes)
        //      }

        Fcache = fastcache.New(maxBytes)
        return Fcache
}

func (*Cache) Set(k,v []byte) {
       //do something before fastcache.Set(k,v)
}

Just wrap fastcache.Cache into your struct. Something like the following:

import "github.com/VictoriaMetrics/fastcache"

type Cache struct {
        c *fastcache.Cache
}

func New(maxBytes int) *Cache {
    return &Cache{
        c: fastcache.New(maxBytes),
    }
}

func (c *Cache) Set(k,v []byte) {
    //  do something before fastcache.Set

    // Call fastcache.Set
    c.c.Set(k, v)
}

Thanks!

I have multiple packages trying to use this
myversion_cache package
How do I share the cache from multiple other packages?

Just initialize cache and store it inside mycustomized_cache package and then call wrapper functions from another packages for accessing the cache:
package mycustomized_cache

var cache = New(123456789)

// Set must be called from another packages
func Set(k, v []byte) {
    cache.Set(k, v)
}

Can I initialize the cache , var cache = mycustomized_cache.New(123456789) from
       package main

first?
then use it in other packages?

Yes, but in this case you should manually pass the initialized cache to all the packages that use it.

oic. I get it thanks.


Add docker file

Add a docker file to create an image of this repository. Refer this.

Hello! I'm interested in contributing on this issue, so I would like to ask for some details.
Are you guys planning on using the docker image for development or production, or both?
If it's for development, live-reload won't be available, so I'm thinking about using a docker-compose file to automate the processing of mounting volumes; is that something you guys are looking for?
Cheers

@poohcom1 Thanks for showing your interest, we want the docker image for development as well as production. Sure, we can go ahead by creating docker-compose file.

Hey @poohcom1 , are you working on this issue?

Hey @poohcom1 , are you working on this issue?

Yep, I was doing some final tests to make sure it works on both Windows and Linux. I'm about to raise the PR

Great! 💯


⚠ Bofrost.es has degraded performance

In d83b244, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1717 ms

Resolved: Bofrost.es performance has improved in 566ef5c after 309 days, 15 hours, 54 minutes.


Progress bar using terminal width

Progress bar use "tput cols" to determine term width.  Only merge if this progress bar does not need to support windows.

thanks @adamlerer !


Move getFileLocation function to CMakeBuilder class

Currently, the getFileLocation function is used by CMakeBuilder only and the logic was implemented for cmake errors logs as well. We should probably move it to the CMakeBuilder class, and implement separate methods for other builders if needed in the future.

could you give some examples for testing? @lingyuncai

Hi @sinapy, I changed this issue slightly as this is more suitable for good first issue. If you are still interested, please feel free to submit a PR :)

Close as fixed in #39.


Community Questions 1.x 08/31

Hello all,
Could you please help me with these community questions?
https://community.influxdata.com/t/how-to-enable-debug-log-level-using-influxd-command/15735/9
https://community.influxdata.com/t/optimum-influxdb-configuration-for-dell-server-with-64gb-ram-and-20-cpus/15678
https://community.influxdata.com/t/how-to-change-influxdb-system-internal-logs-to-any-timezone/15568
https://community.influxdata.com/t/https-cannot-be-setup-as-isolated-service-in-ubuntu/15612
Thank you!

https://community.influxdata.com/t/how-to-delete-data-within-a-time-period/15604/2
https://community.influxdata.com/t/is-there-a-preferred-ec2-class-when-using-tsi1/15758


chore: remove audit pre push

Changes

Remove the audit check on pre-push

Checklist

[x] Read the contribution guide and accept the code of conduct
[ ] Readme (updated or not needed)
[ ] Tests (added, updated or not needed)

Codecov Report

Merging #422 (c12d476) into main (47b25cf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #422   +/-   ##
=======================================
  Coverage   52.36%   52.36%
=======================================
  Files          65       65
  Lines        2049     2049
  Branches      385      353   -32
=======================================
  Hits         1073     1073
- Misses        914      972   +58
+ Partials       62        4   -58

Impacted Files
Coverage Δ

src/model/input.ts
92.61% <0.00%> (ø)

src/model/docker.ts
17.24% <0.00%> (ø)

src/model/system.ts
86.84% <0.00%> (ø)

src/model/cli/cli.ts
31.34% <0.00%> (ø)

src/model/image-tag.ts
54.44% <0.00%> (ø)

src/model/input-readers/git-repo.ts
47.36% <0.00%> (ø)

src/model/cloud-runner/cloud-runner.ts
79.31% <0.00%> (ø)

src/model/input-readers/action-yaml.ts
36.36% <0.00%> (ø)

src/model/cloud-runner/providers/aws/index.ts
16.66% <0.00%> (ø)

src/model/cloud-runner/providers/k8s/index.ts
12.00% <0.00%> (ø)

... and 13 more


Include links to more Zowe web information (forum FAQ and slack) from the zowe.org site

Is your request for enhancement related to a problem? Please describe.
The OMP has a useful faq site https://community.openmainframeproject.org/c/zowe that has some useful Zowe content and we want to encourage users to raise questions here and have FAQ answers posted.
Users visiting zowe.org don't know that this site exists
Describe the solution you'd like
In the zowe.org Documentation link it navigates to a portion of the page that has a button that opens the documentation link.
There could also be a button that opens a link to https://community.openmainframeproject.org/c/zowe that is labelled "FAQ Forum"
There could also be a button that opens a link to https://slack.openmainframeproject.org/ that is titled "Slack channels".
The idea behind this is to have more of the useful Zowe on the web links available from the front page.

@Joe-Winchester  PR is open here with some comments in-progress https://github.com/zowe/zowe.github.io/pull/68


Fix for routing table missing default route

This is the fix for missing default route in routing table when DHCP is triggered by maestro.

Since @cmonr is on vacation I'm going to take the liberty of merging this change.


WIP safekeeper walsender: read-write from single task.

Use postgres_backend_async throughout safekeeper.
Use Framed in postgres_backend_async, it allows polling interface and takes some logic.
Do read-write from single task in walsender.

The latter turned out to be more complicated than I initially expected due to 1) borrow checking and 2) anon Future types. 1) required SendRc<Refcell<...>> construct just to satisfy the checker; 2) is currently done via boxing futures, which is a pointless heap allocation in active path.
I'll probably try to workaround 2) with transmute, but it made me wonder whether socket split, like it was done previously, would be better. It is also messy though:

we need to manage two tasks, properly join them and should on exit/error should join pgbackend back to leave it in valid state; pgbackend itself must swell a bit to provide splitted interface.
issues with tls
tokio::io::split has pointless mutex inside

fixing walreceiver and proxy is not done yet

@funbringer this is a draft, as mentioned, but I'm interested in comments around send_wal.rs polling machinery: basically ReplicationHandler implementation. See also commit message.
CC @petuhovskiy

And here is the version without boxes:
https://github.com/neondatabase/neon/blob/asher/sk-walsender-framed-pg-read-write-single-task-no-boxes/safekeeper/src/send_wal.rs

And here is the version without boxes:

Haven't tested it yet, will try. But considering how unappealing it looks, I realized that I can attempt sitting on both chairs: split the stream (and postgres backend), but keep parts in the same task, polling both. No issues with TLS, no need to synchronize tasks, and using async fns shouldn't require squats. Will try.

Haven't tested it yet, will try.

Tested with pg_receivewal, it works. Nice!

The next version is at
https://github.com/neondatabase/neon/tree/asher/sk-async-pg-backend
I added split to postgres_backend_async, switching manual framing, and started adapting receive_wal.rs accordingly. I wanted to have proper error propagation, and in the process realized that it would be more natural and easier there to have two threads one of which fully does network IO, and the other one writes to disk -- not as currently, where one thread reads data from network, and another writes to disk and replies back. So will follow this approach.

closing in favor of
https://github.com/neondatabase/neon/pull/3576


Lime package installation  done, but not able to import module in jupyter notebook

The following things appear when i try pip installing lime on command prompt, but jupyter throws an error stating " No module found" when i try importing the lime module. Below is the output of the lime installation
C:\Users\TUSHAR\Anaconda3\anaconda_new>pip install lime
Collecting lime
Requirement already satisfied: scikit-learn>=0.18 in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from lime) (0.18.1)
Requirement already satisfied: scikit-image>=0.12 in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from lime) (0.12.3)
Requirement already satisfied: scipy in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from lime) (0.18.1)
Requirement already satisfied: numpy in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from lime) (1.11.3)
Requirement already satisfied: six>=1.7.3 in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from scikit-image>=0.12->lime) (1.11.0)
Requirement already satisfied: networkx>=1.8 in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from scikit-image>=0.12->lime) (1.11)
Requirement already satisfied: pillow>=2.1.0 in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from scikit-image>=0.12->lime) (4.0.0)
No metadata found in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages
Requirement already satisfied: dask[array]>=0.5.0 in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from scikit-image>=0.12->lime) (0.13.0)
Requirement already satisfied: decorator>=3.4.0 in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from networkx>=1.8->scikit-image>=0.12->lime) (4.0.11)
Requirement already satisfied: toolz>=0.7.2 in c:\users\tushar\anaconda3\anaconda_new\lib\site-packages (from dask[array]>=0.5.0->scikit-image>=0.12->lime) (0.8.2)
Installing collected packages: lime
Successfully installed lime-<IP_ADDRESS>
The output of the installation also shows that there was no metadata found, what could be the reason behind it ?

What was the issue. Though it appears to be a bit silly I am facing the same issue..


Oxedions/prometheus fix 1

Thanks a lot for reviewing the code !! 😊

README: what is data model 1.0.0, any link or spec?

I added a link.

README: typo: 'To set kerma username and password, use:'

Fixed

vars/main.yml should be bumped

Fixed

default/main.yml: prometheus_server_karma_password ...

What do you mean exactly ? I should not provide a default password ?

templates/prometheus.yml.j2 ':9093' 'localhost:9090' are hardcoded

I opened a feature request https://github.com/bluebanquise/community/issues/52

tasks/client.yml: tags: service should be added

Fixed

I think it is missing the instructions to set UI/API password somewhere in the doc (even a link to the official doc)

Same, opened a feature request https://github.com/bluebanquise/community/issues/52

Where is prometheus_ipmi_scrape_equipment_profiles defined? Is it worth adding an example in the README?

You mean, where the variables should be defined ? There is an example of the content of this variable in the readme, but indeed I did not defined where these variables should be defined.

Where is prometheus_ipmi_scrape_equipment_profiles defined? Is it worth adding an example in the README?

You mean, where the variables should be defined ? There is an example of the content of this variable in the readme, but indeed I did not defined where these variables should be defined.

Yeah, it wasn't immediately clear to me where prometheus_ipmi_scrape_equipment_profiles should be defined. I just wanted to check with you that the usage of this variable is documented somewhere.

Ok got it. I will improve the readme then.

I do not know if this is clear enough now. Basically, in this revision of the role, I tried to gather everything into a single file in the inventory.

Thanks a lot guys for the review 😊


Turn on iptables for flannel

Turn on iptables for flannel
Closes: #1135
Closes: #1026

LGTM

ci check this


Add margin:auto to .img-responsive to center it

Fixes #19318.

On-hold due to potential backward compatibility concerns being discussed in #19318.

Punting per https://github.com/twbs/bootstrap/issues/19318#issuecomment-189717652.


Add APIBroker services to APIGateway

Add APIBroker services to APIGateway

This was merged to Project-2 branch.


Split up talks in upcoming and previous talks

Right now, the talk list is one long batch.
Before adding pagination or similar, it'd be great to split it up in "Upcoming" and "Previous" talks

It would be great if it shows upcoming talks by default . But there should be a button which will show previous talks.
Can I work on this idea?

@kisharnath Hmm. maybe links to different URLs 🤔


Only shows loading screen

I tried to run this, and used a TMDB api key too, but all I get is this - no errors in the console, just that loading screen
Any suggestions?

hey @bradparks I can see how you may have gotten confused by the eternal loading screen 😄
Hopefully the extra explanation in the readme and first screen from PR #3 will avoid this in the future!
Closing this ticket as merged to master.


feat: add AES hardware acceleration for ARMv8

This PR adds AES hardware acceleration ARMv8. This is sometime called neon and has a significant speedup on ARM based machines.
Experimental results for my ARM based machine (DPF of size $N=1,000,000$):

Software AES: 9.23 seconds
Hardware AES: 0.49 seconds

Roughly a ~18x speedup with no performance degradation on non-ARM machines.

The PR adds a RUSTFLAGS to improve the out-of-the-box performance, which should be enabled by the aes crate.
But I doubt whether there is a high requirement to embed the flag in this library?
RUSTFLAGS is passed to dependencies so users can alternatively set the flags in their own project (in their .cargo/config.toml, or even setting the env when compiling), which provides more flexibility.
Moreover, RUSTFLAGS like CFLAGS, and unlike features, is harder to be composed. With the flag always on, users who do not want the ARMv8 part can not easily exclude it like --no-default-features.
Finally, the ARMv8 part requires Rust 1.61+, which can be a problem for some old distros, e.g., Debian Bullseye (which is at 1.48).
All in all, I think it is better to require users to set the flag when using the library as a dependency.
I can add some description in the readme to help it.

Very true, adding a comment in the docs is a better approach. I thought that it was worth bringing up it is significant performance improvement for ARM based users.


Extra white space in slicing

Operating system: Ubuntu 18.10
Python version: 3.7.3
Black version: 19.3b0
Does also happen on master: Yes
I was using black and I saw that flake8 is complaining about one correction which black did.
For example:
foo_a = [1, 2, 3]
foo_b = [4, 5, 6]

foo_c = [7, 8, 9, 10, 11, 12, 13]

foo_list = foo_c[foo_a[1]:foo_b[2]]

According to PEP8, this code is correct (If I am wrong please point me where I can find an explanation for it). However, black formatted it to:
foo_a = [1, 2, 3]
foo_b = [4, 5, 6]

foo_c = [7, 8, 9, 10, 11, 12, 13]

foo_list = foo_c[foo_a[1] : foo_b[2]]

with extra empty spaces in the slicing operation.

This is by design, please see: https://github.com/python/black#slices

Ok then! Because I was thinking that this case was slightly different. But thanks for your answer. I am going to close it then.

I can't see anything about this particular case in PEP8.
Also, this:
img[:shape[0], :shape[1]]

looks a bit better than:
img[: shape[0], : shape[1]]


chore: remove unused reference to THIRD_PARTY_NOTICES from "nightly"

Note: "nightly" build mostly just needed from API coverage now.
Hopefully fixes failing "nightly" on main.
🦕

>           raise self._exception

more_vert |   |   |   |   |   | E           google.api_core.exceptions.NotFound: 404 Not found: Dataset bigframes-dev:bigframes_testing was not found in location asia-northeast1

more_vert |   |   |   |   |   | E

more_vert |   |   |   |   |   | E           Location: asia-northeast1

more_vert |   |   |   |   |   | E           Job ID: 59cc54bd-164d-4df0-bda7-f65d073be012

more_vert |   |   |   |   |   | E            Share your usecase with the BigQuery DataFrames team at the https://bit.ly/bigframes-feedback survey.

more_vert |   |   |   |   |

>           raise self._exception
E           google.api_core.exceptions.NotFound: 404 Not found: Dataset bigframes-dev:bigframes_testing was not found in location asia-northeast1
E
E           Location: asia-northeast1
E           Job ID: 59cc54bd-164d-4df0-bda7-f65d073be012
E            Share your usecase with the BigQuery DataFrames team at the [https://bit.ly/bigframes-feedback](https://www.google.com/url?sa=D&q=https%3A%2F%2Fbit.ly%2Fbigframes-feedback) survey.

>           raise self._exception

more_vert |   |   |   |   |   | E           google.api_core.exceptions.NotFound: 404 Not found: Dataset bigframes-dev:bigframes_testing was not found in location asia-northeast1

more_vert |   |   |   |   |   | E

more_vert |   |   |   |   |   | E           Location: asia-northeast1

more_vert |   |   |   |   |   | E           Job ID: 59cc54bd-164d-4df0-bda7-f65d073be012

more_vert |   |   |   |   |   | E            Share your usecase with the BigQuery DataFrames team at the https://bit.ly/bigframes-feedback survey.

more_vert |   |   |   |   |

>           raise self._exception
E           google.api_core.exceptions.NotFound: 404 Not found: Dataset bigframes-dev:bigframes_testing was not found in location asia-northeast1
E
E           Location: asia-northeast1
E           Job ID: 59cc54bd-164d-4df0-bda7-f65d073be012
E            Share your usecase with the BigQuery DataFrames team at the [https://bit.ly/bigframes-feedback](https://www.google.com/url?sa=D&q=https%3A%2F%2Fbit.ly%2Fbigframes-feedback) survey.

Looks like maybe we have some flakiness with a global session object picking up the location from a different test.


How to Automate Python Tests with Travis CI

Topic Suggestion
Writing sample(s):
https://okteto.com/blog/develop-and-deploy-a-flask-and-reactjs-app-in-okteto/
https://adamtheautomator.com/docker-save-image/
Proposal Submission
Proposed title of article
How to Automate Python Tests with Travis CI
Proposed article introduction
In this article, you will learn how automated testing works; the reader will be able to differentiate between manual tests and automated tests, how to write unit tests for Python code with Pytest and how to automate running of those tests with Travis CI.
ONLY viable topics to pick from:

Languages

Key takeaways

How to write test for Python code
Difference between manual and automated tests
How to automate tests with Travis CI

Article quality
It is one of a kind.

Thank you for submitting your topic. @khabdrick
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentation.
We believe this is the best way for students to build a great portfolio (for potential employers) is by building what does not exist and what can provide the most value.
Please feel free to suggest an alternate topic to explore. 🚀


prometheus怎么发现k8s集群里的服务的？

As mentioned in Chapters 14 and 15 of the document, mysql, Prometheus and other middleware are deployed on the SRV-data.com server, which is independent of the K8S cluster. However, I saw that the promethean. Yml configuration file has the promethean port for each service exposure, such as
  `

job_name: 'order-api'

static_configs:

targets: [ 'looklook:4001' ]

labels:
job: order-api
app: order-api
env: dev
  `
So how does Prometheus find them, and how does this configuration change
如题，大佬，文档第14，15章写到，mysql、prometheus等中间件都是部署在srv-data.com服务器上，是独立于k8s集群的，但是我看到prometheus.yml配置文件里有写各个服务暴露的的prometheus端口，如
  - job_name: 'order-api'
    static_configs:
      - targets: [ 'looklook:4001' ]
        labels:
          job: order-api
          app: order-api
          env: dev

那prometheus怎么发现他们呢，这块配置该怎么改呢

一样的，可以用ip呀，比如你prometheus部署根k8s在一个 vpc下，你就可以通过内网通信


moving all existing docs/demo files into a building-a-geospatial-app …

…directory

iirc the  directives were to insert a react component. The list of these React components would be here: https://github.com/uber-common/vis-academy/blob/master/src/mdRoutes.js


ios: aborted upload disturbs increment_version_number

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

When an ios approval fails (due to missing strings in plist files) the faulty upload does not appear in teh "App Store Connect" list of builds. As a result the increment_version_number plugin can't see the build number of the faulty update and therefore calculated the next build number wrong.
In my case build 70 was ok, 71 was faulty and rejected by apple (but does not appear on the iOS builds page.
Complete output when running fastlane, including the stack trace and command used

22:21:24]: ERROR ITMS-90189: "Redundant Binary Upload. You've already uploaded a build with build number '71' for version number '1.0'. Make sure you increment the build string before you upload your app to App Store Connect. Learn more in Xcode Help (http://help.apple.com/xcode/mac/current/#/devba7f53ad4)."
Return status of iTunes Transporter was 1: ERROR ITMS-90189: "Redundant Binary Upload. You've already uploaded a build with build number '71' for version number '1.0'. Make sure you increment the build string before you upload your app to App Store Connect. Learn more in Xcode Help (http://help.apple.com/xcode/mac/current/#/devba7f53ad4)."
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.6

Ruby
2.5.8

Bundler?
true

Git
git version 2.24.3 (Apple Git-128)

Installation Source
~/.gem/bin/fastlane

Host
Mac OS X 10.15.6 (19G73)

Ruby Lib Dir
<EMAIL_ADDRESS>

OpenSSL Version
OpenSSL 1.1.1f  31 Mar 2020

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
12.0

System Locale

Variable
Value

LANG
en_GB.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

import "../../SharedFastfile"

default_platform(:ios)

platform :ios do
  desc "Push a new beta build to TestFlight"
  lane :beta do
    Actions.lane_context[SharedValues::FL_CHANGELOG] = prompt(
      text: "Changelog: ",
      multi_line_end_keyword: "END"
    )

    get_certificates( # Create or get certificate, and install it
      output_path: "./builds" # Download certificate in the build folder (you don't need to create the folder)
    )
    get_provisioning_profile( # Create or get provisioning profile
      output_path: "./builds",  # Download provisioning profile in the build folder
      filename: "provisioning.mobileprovision" # Rename the local provisioning profile
    )
    update_project_provisioning( # Set the project provisioning profile (related in Xcode to the General > Signing Release section)
      xcodeproj: "xxx.xcodeproj",
      target_filter: "xxx",
      profile: "./builds/provisioning.mobileprovision",
      build_configuration: "Release"
    )
    update_project_team( # Set the right team on your project
      teamid: CredentialsManager::AppfileConfig.try_fetch_value(:team_id)
    )

    cocoapods

    increment_build_number(
      build_number: latest_testflight_build_number + 1,
      xcodeproj: "xxx.xcodeproj"
    )

    #changelog_from_git_commits(
    #  commits_count: 10,
    #  date_format: "short",
    #  merge_commit_filtering: "exclude_merges"
    #)

    prepare_icons

    build_app(workspace: "xxx.xcworkspace", scheme: "xxx",
      clean: true,
      export_method: "app-store",
      export_options: {
        provisioningProfiles: {
          CredentialsManager::AppfileConfig.try_fetch_value(:app_identifier) => CredentialsManager::AppfileConfig.try_fetch_value(:app_identifier) + " AppStore" # Value of this parameter is the name of the Provisioning Profile. By default, it will be "{bundleId} AppStore"
        }
      },
      build_path: "./builds",
      output_directory: "./builds"
    )

    revert_changes

    testflight(
      groups: ["xxx", "yyyy"],
      distribute_external: true,
    )

    rocket_chat(
      message: "iOS app #{friendly_name} deployed to testflight :rocket:",
      username: "Walter's Toolshop",
      rocket_chat_url: "https://rocketchat.scoop-gmbh.de/hooks/hEnYukHtdpSSmFqhY/5eH4jdMqiCN6jbwjSee2z64bMX9LoSQhxXYcP5K4FYrgFMBc"
    )
  end
end

`./fastlane/Appfile`
app_identifier("xx.xxxxx.xxxx") # The bundle identifier of your app

itc_team_id("xxxxxxx") # App Store Connect Team ID
team_id("xxxxxxxxxxxx") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.160.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-badge
1.4.0
✅ Up-To-Date

fastlane-plugin-rocket_chat
0.1.1
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.2.0

bundler
2.1.4

rake
13.0.1

CFPropertyList
3.0.2

concurrent-ruby
1.1.7

i18n
0.9.5

minitest
5.14.1

thread_safe
0.3.6

tzinfo
1.2.7

activesupport
<IP_ADDRESS>

public_suffix
4.0.6

addressable
2.7.0

httpclient
2.8.3

json
2.3.1

algoliasearch
1.27.3

atomos
0.1.3

aws-eventstream
1.1.0

aws-partitions
1.371.0

aws-sigv4
1.2.2

jmespath
1.4.0

aws-sdk-core
3.107.0

aws-sdk-kms
1.38.0

aws-sdk-s3
1.81.0

babosa
1.0.3

curb
0.9.10

fastimage
2.2.0

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

dotenv
2.7.6

emoji_regex
3.0.0

excon
0.76.0

multipart-post
2.0.0

faraday
1.0.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

gh_inspector
1.1.3

jwt
2.2.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.1

signet
0.14.0

googleauth
0.13.1

mini_mime
1.0.2

declarative
0.0.20

declarative-option
0.1.0

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.38.0

digest-crc
0.6.1

google-cloud-env
1.3.3

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

google-cloud-storage
1.28.0

mini_magick
4.10.1

plist
3.5.0

rubyzip
2.3.0

security
0.1.3

naturally
2.2.0

simctl
1.6.8

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.18.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.0

badge
0.12.0

fuzzy_match
2.0.4

nap
1.1.0

netrc
0.11.0

ffi
1.13.1

ethon
0.12.0

typhoeus
1.4.0

cocoapods-core
1.9.3

cocoapods-deintegrate
1.0.4

cocoapods-downloader
1.4.0

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.1.0

cocoapods-trunk
1.5.0

cocoapods-try
1.2.0

escape
0.0.4

fourflusher
2.3.1

molinillo
0.6.6

ruby-macho
1.4.0

cocoapods
1.9.3

fastlane-plugin-badge
1.4.0

rocket-chat-notifier
0.1.0

fastlane-plugin-rocket_chat
0.1.1

This is still an issue with the latest fastlane version 1.264.0


[SDP-1035] Add "Secure Operation Manual" section and updated the code to enforce MFA and reCAPTCHA

What

Flip flag names ENABLE_MFA and ENABLE_RECAPTCHA to DISABLE_MFA and DISABLE_RECAPTCHA, because the default behavior is to leave them enabled.
If the network is set to pubnet and MFA or reCAPTCHA are disabled, return an error
Add a Secure Operation Manual section to the readme, with the following subjects:

MFA and reCAPTCHA
Approval flow
The importance of user management and using the right rolled (financial controller vs owner)

Why
To increase the security of hosts and operators.
Future Steps

[ ] Update Stellar Docs
[ ] Update Kube configuration

Checklist
PR Structure

[x] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR title and description are clear enough for anyone to review it.
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[x] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr150.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr150.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr150.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr150.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr150.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr150.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr150.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr150.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr150.previews.kube001.services.stellar-ops.com

Is SDP-1035 really the right ticket for this PR?

Good catch, TY! It's actually SDP-1032.
Fixed it in the title.

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr150.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr150.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr150.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr150.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr150.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr150.previews.kube001.services.stellar-ops.com


[Workflow] Improvements to Dapr Client APIs for Workflow

Describe the proposal
I'm proposing we make the following changes to the workflow management APIs in the .NET Dapr client. This is based on the feedback we got from the v1.10 alpha release of the workflow management APIs.

In StartWorkflowAsync, make instanceId and input parameters optional.

public abstract Task<WorkflowReference> StartWorkflowAsync(
    string workflowComponent,
    string workflowName,
    string? instanceId = null,
    object? input = null,
    IReadOnlyDictionary<string, string> workflowOptions = default,
    CancellationToken cancellationToken = default);

Replace GetWorkflowResponse with WorkflowState from the authoring SDK
Add WorkflowFailureDetails property to WorkflowState so that users can obtain more information about a workflow failure.

public record WorkflowFailureDetails(
    string ErrorType,
    string ErrorMessage,
    string? StackTrace,
    WorkflowFailureDetails? InnerFailure)

Add the following methods to DaprClient:

// Waits for a workflow to start running and then returns the state associated with that workflow
public WorkflowState WaitForWorkflowStartAsync(
    string instanceId,
    bool fetchPayloads = false,
    CancellationToken cancellationToken = default);

// Wait for workflow the workflow to run to completion, be terminated, or fail
public WorkflowState WaitForWorkflowCompletionAsync(
    string instanceId,
    bool fetchPayloads = true,
    CancellationToken cancellationToken = default);

/cc @nyemade-uversky

As part of this work, we should also update the console app sample to use the updated Dapr client instead of workflow engine client. That will help us be confident that the new API surface area is sufficient for real use.

I also added this issue in the Quickstarts repo https://github.com/dapr/quickstarts/issues/830


Wrong query detecting after reinitialisation in Angular App

I'm trying to implement css element queries in on of our Angular Apps.
Some element are not initially rendered, so i reinit ElementQueries after a <slide-in> component or <modal> is rendered.
This works in some way but not correct. At the first time the element queries are working correct, but if i close the slide in element and reopen it, there are only to element queries detected and not the fully list.
First:

Second:

Here is a short video example: https://streamable.com/z518j
My angular code looks like this:
I initialise ElementQueries after the app is loaded. And then I listen to simple changes, for example the slide-in opening, and reinit element queries to pass the new rendered html markup.
import {Component, OnChanges, Input, ElementRef, AfterViewInit, SimpleChanges} from '@angular/core';
import {ResizeSensor, ElementQueries} from 'css-element-queries';

@Component({
	selector: 'designer-element-queries',
	template: ''
})

export class ElementQueriesComponent implements OnChanges, AfterViewInit {
	@Input('active')active:boolean;

	constructor(
		private element:ElementRef
	) {
	}

	ngAfterViewInit() {
		ElementQueries.init();
	}

	ngOnChanges(changes: SimpleChanges) {
		ElementQueries.init();
	}
}

Maybe someone can give me a hint why this is causing?

Is this just hidden (using visibility or display css property) or is the DOM detached and re-attached of the watched element when you toggle the visibility?

The DOM is detached and attached.


HTTP interceptors should be able to indicate failure/stop processing

HTTP Interceptors should be able to indicate a failure and stop http request processing, this could take the form of throwing a specified checked exception, or returning null. I think the preferred option would be to allow returning null for now, and make the API breaking change to enable throwing exceptions as part of 2.0.

They already throw an unchecked com.cloudant.http.interceptors.HttpConnectionInterceptorException.

Ah okay, I guess this is where the difference between sync-android and java-cloudant come to bare.


WIP: Max log size config

This PR adds configuration for max log size.

What happens when the user specifies the log max size?  Should we document this in the man crio.conf man page?

@rhatdan We will truncate the file and start adding the newer entries. I will document this better.

[retest]

[retest]

CI is broken Dan, do not retest till @cevich figures the error out

[retest]

Pushed code to update conmon to handle this.

Travis's failing.

@mrunalp for the sake of coverage, could you add a basic smoke test for this feature by using a small size?

Travis is green. I'll add a test.

[retest]

/test all

/test all

/test e2e_rhel

/test e2e_rhel

@stevekuznetsov Seeing some issue in e2e_rhel before the tests are run.

Looks like EC2 dropped the other end of an ssh connection... unfortunately not much we can do about that other than retest.

Okay cool!
Sent from my iPhone

On Sep 25, 2017, at 9:30 PM, Steve Kuznetsov<EMAIL_ADDRESS>wrote:
Looks like EC2 dropped the other end of an ssh connection... unfortunately not much we can do about that other than retest.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

/test e2e_rhel

all good here


Idea/question: Single-instance localisation

This looks very promising! Thank you.
Would luminoth be suitable for the following single-instance localisation problem?
You have two images: A and B
Please check if there is something in image A that looks similar to image B.
If you find something that looks like it, tell me how similar it is and where it is.

I am looking for a smarter solution to a "template matching" problem where images can be rotated, scaled up or down, or even slightly different to the template.

Hi @pwichmann!
I'm not sure it would be suitable for Luminoth at this stage, do you have links to papers/articles describing possible models that solve this problem? We would love to take a closer look at how it would be implemented.
Thanks!


Cryptographic API Misuse Vulnerability

Description:
In the "padding-oracle/oracle.py" and "padding-oracle/generate.py", I have identified a security vulnerability about insecure cryptographic algorithm usage. AES-CBC with fixed or hardcode IV is vulnerable to the chosen-ciphertext attack. And "Random" package would generate predictable pseudo random number.
Location:
https://github.com/goreil/padding-oracle/blob/main/oracle.py#L6
__iv=b'\x07\xff@h\xf3\xde<D\n>\x92\x1b\x95*\xa8\xd6'
cipher = AES.new(key = __key, mode=AES.MODE_CBC, iv = iv)

https://github.com/goreil/padding-oracle/blob/main/generate.py#L8
random.seed(123)

Reference

CWE-330: Use of Insufficiently Random Values

Recommendations

Generate IV with cryptographic secure PRNG.

Thank you!
This is an educational Repository for the purpose of implementing a cryptographic attack. Therefore it doesn't need to be secure itself.
I will close the issue.


Order Status Domain

Referring to your example, the orders status page's domain would be something like https://shop.hull.dev/12345/orders/12345 yeah?
I'm pretty sure it isn't possible, but just wanted to confirm if it is possible to have it under https://hull.dev/12345/orders/12345?

Hey there @kkcy you are correct! The default order status pages generated by Shopify would be part of the domain attached to your native Shopify account, not your headless domain.


Cannot update nullable property to null

This is a blocking issue for me.
The following code:
[Entity]
public interface ITestEntity
{
    string Id
    {
        get;
    }

    int? Property
    {
        get;
        set;
    }
}

class Program
{
    static void Main(string[] args)
    {
        var connectionString = "type=embedded;storesdirectory=Stores;storename=Repro";
        var client = BrightstarService.GetClient(connectionString);

        if (client.DoesStoreExist("Repro"))
        {
            client.DeleteStore("Repro");
        }

        using (var context = new MyEntityContext(connectionString))
        {
            var entity = new TestEntity
            {
                Id = "id",
                Property = 10
            };

            context.TestEntities.Add(entity);
            context.SaveChanges();
        }

        using (var context = new MyEntityContext(connectionString))
        {
            var entity = new TestEntity
            {
                Id = "id",
                Property = null
            };

            entity.Context = context;
            context.SaveChanges();
        }

        using (var context = new MyEntityContext(connectionString))
        {
            var entity = context.TestEntities.Single();

            Console.WriteLine("Property Value: {0}", entity.Property);
        }

        Console.ReadKey();
    }
}

Outputs:
Property Value: 10

Hi,
This is to do with the way you are doing the update. Instead of creating a new TestEntity instance with the same Id property value, try instead retrieving the entity and setting its property to null. Code like this (untested) should work in your second using block:
using (var context = new MyEntityContext(connectionString)) {
  var entity = context.TestEntities.FirstOrDefault(x=>x.Id == "id");
  entity.Property = null;
  context.SaveChanges();
}

This way the code "knows" that you are actually updating the property of an existing entity rather than redundanty setting the property of a new entity to its default value.
That should fix the problem - if it doesn't feel free to reopen this issue!

Hi Kal,
The reason I was creating a new entity rather than retrieving the existing one has to do with my use case. I have some external code (add-ins, if you will) that provide my code with an entity (actually, they implement a contract and I have to convert that contract to an entity). Therefore, it made sense to me to just attach that entity to the context rather than looking it up and copying data from their entity to the resolved entity.
However, your comments pushed me in the right direction. I simply have to attach the context before setting the property to null. This works in as my second using block:
using (var context = new MyEntityContext(connectionString))
{
    var entity = new TestEntity
    {
        Id = "id"
    };

    entity.Context = context;

    entity.Property = null;
    context.SaveChanges();
}

But what confused me is the inconsistency with the treatment of null versus other values. For example, if I instead do this:
using (var context = new MyEntityContext(connectionString))
{
    var entity = new TestEntity
    {
        Id = "id",
        Property = 30
    };

    entity.Context = context;
    context.SaveChanges();
}

Then I do see 30 as the value! Since that was my starting point, I simply changed the 30 to null and expected it to work.


golang bom generation failed if there is 'build' substring somewhere in the project path

Issue: golang bom generation failed if there is 'build' substring somewhere in the project path
cdxgen version: 8.0.5
Ubuntu 20/22, golang 1.20.1
Steps:

Clone project https://github.com/jfrog/build-info-go
Try go generate bom file for it

git clone https://github.com/jfrog/build-info-go
cd build-info-go
cdxgen

incorrect bom generated, 0 deps found
rename project dir to any other, without 'build' word ==> cdxgen OK, deps found
The same problem happens if any other part of the project path contains 'build', like /home/user/dev/build_me/proj1

Thanks, @academic-sakharov, for reporting this issue. Please try 8.0.6, which should resolve this issue.

Thanks a lot for fixing this! Works fine in 8.0.6


Updates .NET SDK

Description
Updates the .NET framework to include .NET 9.
Related issue:
Fixes https://github.com/actions/runner-images/issues/10964
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

come on, let's go!

When should we expect this to be completed (at least on Ubuntu images)?

This PR would be very helpful as we are migrating to .NET 9. The agent's inability to build is the most challenging part of the process.

@frankgalindo-briteris you can install .net 9 manually via dedicated github action to mitigate this

When this PR is going to be merge?


Link hover style

This is just a quick followup based on @PaarthAgarwal's work on #143.
This is addressing the focus style mentioned in the #143 review and reduces the number of colors used as was discussed in #78
Closes #143
Closes #148
Closes #78
Closes #22

Looks good. Closing #143 in favour of this.

Looks good. Closing #143 in favour of this.

Thanks for teeing this up 👍


Incomplete signature for ParamSpec

Environment data

Ubuntu 22:10
Python 3.10.7

Language Server version: v2023.3.20
OS and version: Ubuntu 2022.10
Python version: 3.10.7 from OS, using a venv

Code Snippet

P = ParamSpec("P", bound=Sequence)

This produces the error: "bound" is an unknown parameter to ParamSpec. However, Paramspec has had an (undocumented) bound parameter since cpython 3.10.1.

ParamSpec is a special form that type checkers need to special case, which is why pyright (the static type checker that underlies pylance) is reporting an error here.
Do you happen to know why a bound parameter was added to ParamSpec? An upper bound makes no sense for a ParamSpec.

I suppose it was added because the specification demands it:
https://peps.python.org/pep-0612/#declaration

The runtime should accept bounds and covariant and contravariant arguments in the declaration just as typing.TypeVar does, but for now we will defer the standardization of the semantics of those options to a later PEP.

However, mypy currently doesn't implement anything either:
foo.py:3: error: Only the first argument to ParamSpec has defined semantics  [misc]