mangahub source(server) isn't working

i installed it by cloning the repo and using install.bash
but when I try to search for something the result is always like this:
--

oh wait, it is just the default server that was doing that.
it works fine with the -s flag, my bad.

Opening this issue as it is valid.

This has been fixed.

This has been fixed.


Change ockam identity commands to support multiple identities.

Currently:
ockam node create n1

creates a default identity for the newly created node
we can see it with
» ockam identity show --node n1
P7dc502c795201c2d816749ea45ff51a416dce16ef0fe1b65ab4a642899e3b4d8

Even thought we have an identity create command SHOW_HIDDEN ockam identity create --help
We can't create a new identity because a node configuration can currently only have one identity.
» ockam identity create --node n1
encountered an error in command handler code

We have to modify NodeManager and its configuration here to support multiple identities
https://github.com/build-trust/ockam/blob/83db24993f74af23adcee23228fdc10d3bb1fe68/implementations/rust/ockam/ockam_api/src/nodes/config.rs#L6-L15
The code for the identity commands is here
https://github.com/build-trust/ockam/tree/6093f3a77869738fb4417f5093e5fc7d00acdf8c/implementations/rust/ockam/ockam_command/src/identity
The code for identity apis that identity commands call are here
https://github.com/build-trust/ockam/blob/0c5a39891eddec31056b7838d9efac50d287185c/implementations/rust/ockam/ockam_api/src/nodes/service/identity.rs#L14
Once we have the ability to have multiple identities, we'll need other commands like identity show | list

What is the reasoning behind multiple identities?

Is it for multiple services (other nodes) to talk to the same node with their own unique ID?

Can Vec<Vec<u8>> be used for storing multiple identities? Is there a better way to store them?
How can identity be overridden? I couldn't find the command to do so.

@anuvratsingh thank you for looking into this.

What is the reasoning behind multiple identities?

The underlying ockam library supports the idea of a node/application using different identities in different privacy and authorization contexts. But we haven't surfaced that in ockam command yet. So I may communicate with remote service 1 using identity 1 and with remote service 2 using identity 2.

Can Vec<Vec> be used for storing multiple identities? Is there a better way to store them?

@SanjoDeundiak may be the best person to add some context here. The private information (like keys) of identities live in vaults. So we'll have to tackle that.

How can identity be overridden? I couldn't find the command to do so.

We'll need new options in various commands to indicate the --identity and the --vault
And maybe some new commands to create a pointer that points to the default identity and default vault of a node.

@anuvratsingh I think Vec<Vec> is good to store identities NodeManConfig, note that NodeManConfig is the format for NodeManager persistence. So, NodeManager fields should now instead of storing one Identity, switch to multiple identities, I would consider Map<IdentityIdentifier, Identity> + default IdentityIdentifier to indicate which one to use if no argument is provided to a command.
Identity override is a mechanism using which node instance can gain default identity that is shared among other nodes on the same machine for sake of simplification for running demos.
I would start that task with improving ockam identity create command, so it could add new identity if there was already one present in that node.

If noone's working on this, I'd like give it a try.

So I've create draft PR #3837
I'm not sure how to handle the default node Identity so for now I just use first Identity as a default and cache it's Identifier.
One thing I'm not sure how should be handled is the IdentityOverride could you please elaborate a bit more about that?
And if you could take a look and let me know if I'm going in the right direction that would be much appreciated.

@adrianbenavides with your comment in #3837 I take it that his issue will be closed as well as it is not wanted anymore?

@adrianbenavides with your comment in #3837 I take it that his issue will be closed as well as it is not wanted anymore?

That's right, thanks for the heads up @vildapavlicek !


How to set endpoint to Link plugin?

By analogy with the Image I did so:
<editor :config="config" />

<script>
    export default {
        data() {
            return {
                ...
                config: {
                    link: {
                        endpoint: 'https://localhost:8080/fetchUrl'
                    }
                }
            }
        }
    }
</script>

but it doesn't work.

It breaks before ^2.0.0, Please use link plugin with vue-editor-js ^2.0.0


Add USDM-USDC boost

They are matching rewards from our wstETH-USDM clm boost

https://github.com/beefyfinance/beefy-v2/pull/2313


fix: 调整存储容量后刷新调度缓存

这个 PR 实现什么功能/修复什么问题:
调整存储容量后刷新调度缓存
是否需要 backport 到之前的 release 分支:

release/2.10.0

/area region
/cc @swordqiu @yousong @zexi

Codecov Report

Merging #3773 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3773      +/-   ##
=========================================
+ Coverage    6.94%   6.94%   +<.01%
=========================================
  Files         499     499
  Lines       84252   84252
=========================================
+ Hits         5848    5850       +2
+ Misses      77907   77906       -1
+ Partials      497     496       -1

Flag
Coverage Δ

#aFlag
6.94% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/storages.go
1.12% <0%> (ø)
:arrow_up:

pkg/appsrv/response.go
69.23% <0%> (+3.07%)
:arrow_up:

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 2422880...520bddd. Read the comment docs.

/lgtm
/approve


Duplicate fbjs dependencies leading to "Error: Naming collision detected"

This issue has been reported in #5180, #5357, #5390 and #5412 (so it's a pretty visible one!). Consolidating here to have a place to discuss solutions.
The Issue
Errors are of the following form (although the exact file that collides isn't always the same):
Error building DependencyGraph:
Error: Naming collision detected: /Users/rreusser/project-name/node_modules/react-native/node_modules/react/lib/AutoFocusUtils.js collides with /Users/rreusser/project-name/node_modules/react/lib/AutoFocusUtils.js

It appears the problem is with the packager, which globally resolves @providesModule annotations, vs npm, which can install different versions of the same module at different points in the tree, leading to collisions. A lot of people are running into this now that react-native depends on react, which both depend on fbjs. It has also been reported with other Facebook dependencies including flux and fbemitter.
Current Workarounds

Delete node_modules, upgrade to npm@3, and reinstall everything. npm@3 makes an effort to dedupe dependencies if the accepted versions overlap.
Delete node_modules, install fbjs as a top-level dependency and manually delete all nested fbjs instances (https://github.com/facebook/react-native/issues/5390#issuecomment-172679236)

I think option 1 is cleaner, and we should update the docs to recommend npm@3 unless we find a better short-term solution to this issue.
Possible Solutions

It appears there's a file packager/blacklist.js, maybe this could be used to ignore the conflicting react/fbjs dependencies.
I don't know how much 'react-native' depends on fbjs, but if it isn't in many places it could be removed entirely.
fbjs could strip its @providesModule annotations in the version pushed publicly on npm and rely on relative require statements. Long-term I see this as being a more stable solution, because npm's nested dependencies will never play nicely with a parallel global system. I suspect we'll keep seeing issues about this pop up whenever someone includes two Facebook projects with different fbjs versions. But, this solution is probably impossible because of how widely used fbjs is with Facebook.

Other options?

According to https://github.com/facebook/fbjs/pull/97#issuecomment-173747938 having multiple copies of fbjs in a React Native project will be supported in 0.19. :+1:

great news :)

It'll probably be 0.20 since the patches haven't landed yet but yes support is coming.

I've had this issue before with facebook's flux library.
Before this fix comes out, you can either update every dependency you have so they're on the same version of fbjs, or downgrade your dependencies to when they didn't use fbjs yet (for flux this was 2.0.1)
Hope this helps

For people that are still facing this issue, a temporary can be to add fbjs as a dependency in your package.json, and then run a script in postinstall to remove the extra fbjs https://gist.github.com/jrichardlai/a6a36352e1b98eb2946a

@jrichardlai 's suggestion solved it!

Ran into this just now upgrading RN 0.17.0 -> 0.18.1. In case it helps anyone else, here's the error I got:
 Error: Naming collision detected: /Users/rettig/wip/breeze-react-native/Breeze/node_modules/fbemitter/node_modules/fbjs/lib/warning.js collides with /Users/rettig/wip/breeze-react-native/Breeze/node_modules/react-native/node_modules/fbjs/lib/warning.js
    at HasteMap._updateHasteMap (HasteMap.js:132:13)
    at HasteMap.js:103:28
    at tryCallOne (/Users/rettig/wip/breeze-react-native/Breeze/node_modules/promise/lib/core.js:37:12)
    at /Users/rettig/wip/breeze-react-native/Breeze/node_modules/promise/lib/core.js:123:15
    at flush (/Users/rettig/wip/breeze-react-native/Breeze/node_modules/asap/raw.js:50:29)
    at doNTCallback0 (node.js:428:9)
    at process._tickCallback (node.js:357:13)

And here's what fixed it:

rm -rf node_modules/
npm i fbjs
npm i
npm i fbjs (once more for good measure?) -- at this point I was still getting the error.
find . -name 'fbjs' -print and delete all but the top-level fbjs, in my case just one, ./node_modules/flux/node_modules/fbjs
rm -rf $TMPDIR/react-*
watchman watch-del-all
npm cache clean

I'm guessing some of these steps may be extraneous and order may not matter, but in any case this got me going again.
Thanks.

jrichardlai YOU DAHH MANN

CC @zpao
It gets worse. Upgrading to fbjs 0.7.0 (which was just released) causes react-native to fail every time I try to build anything. I guess fbjs 0.7.0 did something to keyMirror, which react-native depends on indirectly via fbjs (and there is no direct dependency). Downgrading fbjs back to 0.6.1 fixed this for me.
bundle: Created ReactPackager
uncaught error Error: UnableToResolveError: Unable to resolve module keyMirror from /Users/foo/foo/node_modules/react-native/Libraries/Utilities/MessageQueue.js: Invalid directory /Users/node_modules/keyMirror
    at ResolutionRequest.js:356:15
    at tryCallOne (/Users/foo/foo/node_modules/promise/lib/core.js:37:12)
    at /Users/foo/foo/node_modules/promise/lib/core.js:123:15
    at flush (/Users/foo/foo/node_modules/asap/raw.js:50:29)
    at doNTCallback0 (node.js:428:9)
    at process._tickCallback (node.js:357:13)
See logs /var/folders/rs/61p0bjp90ts_r161p5pystyh0000gn/T/react-packager.log
    at SocketClient._handleMessage (SocketClient.js:139:23)
    at BunserBuf.<anonymous> (SocketClient.js:53:42)
    at emitOne (events.js:77:13)
    at BunserBuf.emit (events.js:169:7)
    at BunserBuf.process (/Users/foo/foo/node_modules/bser/index.js:289:10)
    at /Users/foo/foo/node_modules/bser/index.js:244:12
    at doNTCallback0 (node.js:428:9)
    at process._tickCallback (node.js:357:13)
Command /bin/sh failed with exit code 1

Note -<EMAIL_ADDRESS>may be needed as latest fbjs doesn't export the necessary modules. As per https://github.com/facebook/fbjs/pull/95. I guess this will soon all be sorted out and these hacks won't be required.
Also, rather than removing files I used a project rn-cli.config.js that adds the fbjs paths to the blacklist.

@lrettig I used npm i<EMAIL_ADDRESS>on react 0.19
I'm using the latest node and npm (version 3.6)

@ide do you know if this landed in 0.20-rc? I didn't see a mention in the release notes.

Ok I tried to upgrade, but unfortunately I'm saddened to report that Error: Naming collision detected is still occurring with 0.20.0-rc1

The fix (https://github.com/facebook/react-native/pull/5084) is still pending (some internal FB issues).

Check here to solve this issue. :clap::+1::smiley:

@iTonyYo This not work at me.

I have tried again with 0.21-rc, still not working. It's been breaking every release since 0.18 for me.
Right now I have a naming collision between node_modules/fbjs/flow/include/CSSCore.js and node_modules/fbjs/lib/CSSCore.js. None of the proposed workarounds has been successful on my project.

I battled with this for a long time, and finally got it working by doing the folowing:

Adding fbjs (version 0.6.1) as a separate dependency in my package.json
Adding an exclude to my rn-cli.config.js file, so that the file looks roughly as follows:

'use strict';

const blacklist = require('react-native/packager/blacklist');

var blacklist = [
  /{root folder name}\/node_modules\/.+\/node_modules\/fbjs\/.*/
]

module.exports = {
  getBlacklistRE() {
    return blacklist('', blacklist);
  },
};

For those that don't already have an rn-cli.config.js file, this lives in the root directory, alongside the index.ios.js and index.android.js files.

I resolved it by updating fbemitter 0.9.1 to 0.9.2

npm ddp fixed the issue for me

This should be fixed in 0.22-rc.


Spelling error on line 2 of README

On line 2 there was a spelling error; files was spelt as fils.

Thanks for catching this


Hi, I got an error as below. how to solove it?

Forbidden
You don't have permission to access /installation/ on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

Hello,
These errors (permission and ErrorDocument) are related with configuration of your system.
You can solve permission issue by using chown and chmod command. For ErrorDocument issue, check your apache configuration.


feat: update network crd and controller

Fix #29
Signed-off-by: Abirdcfly<EMAIL_ADDRESS>

orderer enroll encountered some problems, will be fixed in the next pr.


Local storage based on Linux filesystem optimization

Something can improve optimization：
-aio/iouring (doing)

sharing
data compression

The final we will bypass file system,but above will benefit both block device and filesystem.


Replace Math.random to prevent duplicate event IDs

According to the definition of a V4 UUID, event_id is supposed to be unique for every event. Unfortunately we see the same event_id more than once in our collected data.
Our example data set has 13,406,731 events from which 13,235,475 have unique event_ids. This means that there are about 1.3% events that have duplicated event_id. These events may come in completely different times and from different ip's. As an example, there are 15 different events with event_id = "f2d4f27d-077a-4086-8cce-5789b10fbfda". See the graphics below.

We even have a larger data set with more recent JS tracker versions (2.5.x and 2.6.x), and the duplicate ratio is even worse ~= 1.8%

Are you running the event fingerprint enrichment? Could you reshare the above table with the event fingerprint output as well? Trying to understand what type of duplicates these are.

For this dataset, which is a bit older, we did not have that enrichment enabled. (If it even was available back then.) I'll check for the current SP stack, if we have it running.

Thanks @christoph-buente !

Looking at the user agent i came to the suspicion that the actual implementation of the uuid algorithm falls back to Math.random() in certain browsers. Can this be confirmed? That would be a bug in the underlying uuid npm module, right?

Hi @christoph-buente. This is an issue we have written about before: http://discourse.snowplowanalytics.com/t/de-deduplicating-events-in-hadoop-and-redshift-tutorial/248 (in case the solutions outlined there are useful).

@bogaert thx Chris, i read that article. But i hoped there is a chance to fix that issue instead of working around it later down the data pipeline.

@christoph-buente That makes sense. We'll look into it (cc @jbeemster).

Bump 😄

Hi @christoph-buente. It was good meeting in Berlin! This is something we'll keep investigating, but in the meantime we're also working on an improved deduplication step in the pipeline: https://github.com/snowplow/snowplow/issues?q=is%3Aopen+is%3Aissue+milestone%3A"R8x+[HAD]+Synthetic+dedupe"

See https://github.com/snowplow/snowplow/issues/2967

From @falschparker82:
Hi Snowplowers,
we've got heavy problems here due to some bots (especially Googlebot, googleweblight and others) apparently using a broken version of Math.random(), leading to duplicated event_ids. This gets especially annoying with the resulting huge cartesian joins resulting from significant context use.
I could track down the problem down into the uuid library of the implementation that the Javascript collector uses: https://github.com/kelektiv/node-uuid/blob/master/lib/rng-browser.js#L17 - which happens to fall eventually back down to Math.random() if no better randomness sources are available.
Unfortunately, the implementation of Math.random() is left to the JS interpreter, which is broken on several systems - sources:
http://stackoverflow.com/a/24224089/1281376
<EMAIL_ADDRESS>I'd like to propose the following solution for this problem:

Replace Math.random() with a seedable Mersenne twister: https://github.com/pigulla/mersennetwister (probably needs upstream patching of npm uuid package). While this is not suitable for cryptographic uses, all that's needed is good entropy here to prevent event ID duplication. Also, the cycle length of >2^19000 far surpasses the capacity of a UUIDv4 (2^128).

1a) Make it possible to seed the RNG by invoking sp.js with an additional parameter &rnd_seed=a4b120f48... (if the page isn't cached or served via CDN, this should be possible rather easily with templating from multiple languages) - which then gets inserted by a seed vector into the twister.
1b) Alternatively - or as a fallback to 1a) - generate the seed vector from the following entropy sources:

Hash of URL value
getHour(),getMinutes(),getSeconds(),getMilliseconds()
Additionally generated floating point entropy: https://github.com/keybase/more-entropy
Difference of Snowplow cookie date to current time
Injecting Math.random() at least can't hurt

Thoughts?
Right now I've got a little too much on my plate, so feel free to grab it - but if we happen to do ourselves eventually it we'd love to upstream in case you're interested.

Scheduling into 2.8.0 as this is important

re-hi!
(was a little confused at first since the issue link was cross-project, so #499 ended up linking to the wrong issue on snowplow/snowplow).
As said, so much for the thoughts, can't do it myself right now due to lack of time unfortunately. Just a quick clarification regarding:

I like 1b) - I have nothing against 1a) but I don't know of many (any?) users who don't serve sp.js via CDN...

I was actually thinking about templating the tag itself when rendering a web page, not the Javascript tracker. So more something along the lines of (thinking in PHP here for simplicity / demonstration purposes):
<script type="text/javascript">
    ;(function(p,l,o,w,i,n,g,r){if(!p[i]){p.GlobalSnowplowNamespace=p.GlobalSnowplowNamespace||[];
    p.GlobalSnowplowNamespace.push(i);p[i]=function(){(p[i].q=p[i].q||[]).push(arguments)
    };p[i].q=p[i].q||[];n=l.createElement(o);g=l.getElementsByTagName(o)[0];n.async=1;
    n.src=w;g.parentNode.insertBefore(n,g)}}(window,document,"script","https://static.justwatch.com/static/compile_jw/assets/sp-2.6.2.js","snowplow","<?php uniqid(); ?>"));
    </script>

Addendum: I'd be happy to review though - a few implementation hints:

First off, definitely needs to initialize the RNG via a larger vector/array, otherwise it's the same limited state problem all over again when using a single int
As the floating point entropy generation package seems pretty taxing on the CPU (especially on mobile) and thus increasing tracker latency, I'd go for not much more than 16 bits of entropy and use it only when needed (which is hard to prove)
I'd be a super happy camper if the fully initialized RNG or UUID functions could be somehow exposed from the module, as we've got some more things we need UUIDv4's, for example survey IDs (where we've got the same problem). Spares us initializing two different RNGs for doing the same.

Any update on this one? Can I help?

Hey @falschparker82 - we pushed it back because we are assigning a new (to Snowplow trackers) engineer to the 2.8.0 release and this is a complex ticket. To bring it back into 2.8.0 again, I think we would need a PR from you...

Unfortunately, we're super low on Frontend power right now and JavaScript isn't exactly my hometurf. I'll see if we can make a slot for that somewhere in the next weeks but no high hopes right now. Will touch base in a month at the latest.

@alexanderdean do you have capacity now, to tackle that issue? It did not dissapear, unfortunately. 😭

Potentially @christoph-buente - we should know within the next month how much bandwidth we have for JS Tracker work...

Much needed, any news on this issue?

For the record I've put a comment on the uuid package this repo uses to be able to create more secure id-s: node-uuid/issues#173

Thanks @anagytherealone !

Is there any more news on this issue? What's the plan? How are things progressing?
We've noticed the same thing- clashes in snowplow-generated ids. We've also seen clashes across ids: e.g. event_ids clashing with session_ids.
There seems to be a general feeling here that with a good enough random number generator you'll get an essentially unique UUID. While this is true when using a single stream of random numbers it is not true when you have several streams of random numbers not sharing state. Unfortunately, since there are many, many trackers running in parallel, any guarantees on the uniqueness of the ids falls over and is at the whim of how the seed is determined.
Bloating the codebase with a more sophisticated random number generator is overkill. Random number generators like the Mersenne Prime Twister are designed to be robust to a whole suite of statistical tests; the goal being that the generated random numbers will be used in simulations. For UUID, all that's needed is a long periodicity; even a basic random number generator would suffice.
In my opinion, the correct approach is to simply hash a whole bunch of context relating to the event, user, session etc. and also inject some randomness through a random number generator. Then, the only way the ids would be is if the random number clashed and the entirety of the context clashed. The chances of this are essentially 0.

Thanks for your comments @smalory
This is certainly on our radar still. We have a considerable release on the horizon in regards to v3. We're currently in the process of triaging open issues and identifying what we want to think about changing for v3 and I think this issue might make the cut in some shape or form.
Keep your eye on it and our milestones as we will be chopping and changing the milestones over the coming weeks as decide what our near term roadmap starts looking like.

Great; thanks for the info Paul!

I am investigating a similar issue. Has anyone tested if crypto.getRandomValues() works better for googleweblight or the googlebot? We also see an issue when the user agent is simply 'Mozilla 5.0' or contains adsbot

Time for an update on this one given v3 is now available. Unfortunately little has changed at the moment, the issue arises due to falling back to Math.random() when crypto.getRandomValues() isn't available. As we continued to support older browsers with v3, this fallback has stayed in place. Until we drop support for IE9 and IE10 then we can't do too much to fix this (unless anyone has any ideas that don't add too much bloat?).
As for dropping IE9 and IE10, they have a depressingly high level of events (particularly IE9) in the data we assessed. I'd hope we can drop them when v3 is mature and move to v4 - those that want IE9 and IE10 support can then stay on the mature v3.
For the time being, deduplicating the events downstream is the best solution for this (as described earlier in this issue).

Hi @paulboocock,
In light of your last comment from almost 1.5 years ago, is there nowadays still a need/requirement to support IE9 and IE10 (and even IE11)?
Are there already plans for the mentioned v4?
Alternatively, would it be an idea to offer the "older browsers" support as a separate NPM package that can be installed like the plugins when people have a need to support those older browsers?

Hi @schmkr, thanks for raising this question.

Are there already plans for the mentioned v4?

Yes. We have plans for the v4. Indicatively we plan to release the v4 before the end of the year.
That version will drop the support to IE10. Also we will take care to reduce the issues related to Math.random.

Hi @AlexBenny, since Version 3.9 was just released: are you still sticking to the plan that the Math.random issue will be addressed in Version 4.0 ?


Fix Julia 0.7 deprecations.

Fix remaining Julia 0.7 deprecations.

Keyword for digits argument of floor.
uninitialized → undef
endof → lastindex
contains → occursin

Codecov Report

Merging #52 into master will not change coverage.
The diff coverage is 87.5%.

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   85.43%   85.43%
=======================================
  Files           5        5
  Lines         302      302
=======================================
  Hits          258      258
  Misses         44       44

Impacted Files
Coverage Δ

src/bufferedoutputstream.jl
72.15% <100%> (ø)
:arrow_up:

src/bufferedinputstream.jl
96.93% <100%> (ø)
:arrow_up:

src/emptystream.jl
69.38% <100%> (ø)
:arrow_up:

src/BufferedStreams.jl
75% <50%> (ø)
:arrow_up:

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 78738df...4ebe43e. Read the comment docs.

Thank you very much! LGTM


Gravity not working in sony phone

Hello, i am using the latest version of material dialogs. I am having issue with setting content gravity. I tested my app in sony and samsung phones. For samsung(4.0.3) there is no any problem but for sony(4.4.4) gravity is not working. I have set title gravity center but title is at start in the sony xperia m2 kitkat 4.4.4
In samsung(4.0.3)

In sony(4.4.4)

Hmmm, setting center gravity to the title is working for me on 4.4.4:

This should hopefully be fixed now with the latest commits. It won't go live as a release until it's tested a bit more.

https://github.com/afollestad/material-dialogs/releases/tag/<IP_ADDRESS>

https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>


Add error routes into router

Present users with an error message when accessing urls that don't exist or the user lacks permission for.

deep sigh
One man's low-hanging fruit is another man's stretch, I suppose.
I spent a few hours fiddling with this and none of the following work'd:

Implementing according to the instructions here: https://github.com/meteor-useraccounts/iron-routing
Trying the recommendations on this SO thread: http://stackoverflow.com/questions/28379710/iron-router-not-displaying-notfound-page
This SO thread also didn't help: http://stackoverflow.com/questions/29906891/using-meteor-useraccounts-core-ensuresignedin-plugin-wont-except-route
It didn't matter if I made changes and setup routes in meteor-gazelle-core/lib/router/config.js or meteor-gazelle-accounts/lib/accounts.js

I get the feeling the router config in the core package isn't being read by Meteor at all, but honestly IDK what/where the problem is.  _(ツ)_/
Here's the Gist: https://gist.github.com/daveyshindig/f58fe3878cac9ea6d4da

@daveyshindig Thanks for looking into. There's overlap with some of the work I'm doing at the moment with this issue so I'll handle it.

@ajax-wcd Cool, I'm looking forward to seeing how it's fixed. Cheers :)


[feat][plugins/aws] Automatic AWS policy and CF template generator

Description
Adds an automatic AWS policy and CF template generator to the AWS plugin.
Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Codecov Report
Base: 89.92% // Head: 89.92% // No change to project coverage :thumbsup:

Coverage data is based on head (c4a3283) compared to base (284a521).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1404   +/-   ##
=======================================
  Coverage   89.92%   89.92%
=======================================
  Files          73       73
  Lines       11368    11368
=======================================
  Hits        10223    10223
  Misses       1145     1145

Flag
Coverage Δ

resotocore
89.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Update for Jetpack 6

Hello all,
I want to use this package for a Jetson Orin with Ubuntu 22.04, Jetpack 6 and Ros2 humble.
Any updates planned, and/or what is the roadmap for this project?
BR Franz

@franzrammerstorfer
Hi Franz!
While the default branch name is galactic, we've confirmed the code also works on ROS2 Humble because the code does not use galactic-specific functionality.
FYI: This project assumes some specific ECU as a working environment since the GPIO pin number differs depending on ECUs. We've confirmed on RQX-58G from ADLINK Inc. and Anill from ConnectTech Inc. If you would like to use this project on another platform, you may need to explore pin assign for your environment.
Thanks!

Hello,
thanks for your response. I think the problem is not galactic vs humble, but the different management of the gpio devices. For example, in jetpack 5 we use "sys/class/gpio" whereas in jetpack 6 we use "/dev/gpiochip0". Hence, the sensor_trigger software needs to be adapted.
BR Franz
BR Franz

@franzrammerstorfer
Hello,
Thank you for pointing that out. Regarding GPIO handling, we are working on the refactor/simplify-libgpiod-implementation branch to switch from sysfs to character device. So you may be interested in the branch if you would like to control GPIO via character devices, such as /dev/gpiochip0.
Best


Fix itemlist_formaction testing

Fixes issue 409 by ensuring each url opened by OP_OPENALLINBROWSER
or OP_OPENALLINBROWSER_AND_MARK is opened exactly once.
Fixes issue 410 by matching urls opened by OP_OPENALLINBROWSER
or OP_OPENALLINBROWSER_AND_MARK independently of the order they were
opened.

A few general remarks:

you can reference issues and PRs by typing # and their number. This works everywhere: comments, issues, PRs, even commit messages. One cool thing about this feature is that the issues you mention this way will be updated to show that you've referenced them—no need to go there and comment, it's all automated.

you can make GitHub automatically close issues when your PR is merged by saying things like "fixes #000" in your commit message.

Since I closed #410, you should remove it from the commit message. Thanks!

Coverage remained the same at 32.448% when pulling 0f3b1cf7c411e9efaf21a59e1ddd5ad7e7a2a06f on tkerdonc:itemlist_test-fix-409-410 into 3be85838ed491ac66fb0ced83796e8282c03f07e on akrennmair:master.

Thanks for the info, removing the redundant REQUIREs and resubmitting.

Coverage remained the same at 32.448% when pulling e47fc2947a3f966737a9e6a5ee7c8e8e54edaf53 on tkerdonc:itemlist_test-fix-409-410 into 3be85838ed491ac66fb0ced83796e8282c03f07e on akrennmair:master.

Coverage decreased (-0.07%) to 32.373% when pulling e47fc2947a3f966737a9e6a5ee7c8e8e54edaf53 on tkerdonc:itemlist_test-fix-409-410 into 3be85838ed491ac66fb0ced83796e8282c03f07e on akrennmair:master.

The code looks good to me. Will merge once the checks finish (one of the Travis workers failed for no obvious reason).

Thanks for fixing this!


[1.21.1 -> 2.0.3] Plugin version is displayed incorrectly.

[1.21.1 -> 2.0.3] Plugin version is displayed incorrectly.

[ ] Tested on Spigot
[ ] Tested with this plugin only

Description
The plugin version is displayed incorrectly.
Server Log
[ContainerView] Enabling ContainerView v${project.version}
Installed Plugins
AdvancedBan, AdvancedBanX, AntiSeedCracker, AntiSpammer, BetterNetheriteUpgradingReloaded, BetterRTP, Billboards, BungeeGuard, Chunky, ChunkyBorder, CMI, CMILib, Coins, ColoredSigns, CommandForward, ConsoleSpamFix, ContainerView, CoreProtect, CrazyAuctions, DeluxeMenus, Essentials, FallingSnow, FastAsyncWorldEdit, GroupManager, InteractionVisualizer, InvSeePlusPlus, ItemCommand, LightningBan, LockettePro, Matrix, MiniMOTD, MinerTrack, Multiverse-Core, Multiverse-NetherPortals, packetevents, Pl-Hide-Pro, PlaceholderAPI, PlayerDataRollback, PlayerReport, PlayerTitle, PlugManX, ProtocolLib, PvPManager, QuickShop-Hikari, Residence, SkinsRestorer, TAB, Vault, ViaBackwards, ViaRewind, ViaVersion, Vulcan
Plugin Version
2.0.3
Minecraft Version
1.21.1
Server Software
Leaf
How to reproduce

Install the plugin.
Start Server.

Thanks again, updated on spigot.


esv6-edsv6-series.md incorrectly lists Premium Storage Not Supported for Esv6

Need to set Premium Storage to Supported for the Esv6-series.

@misha-bansal
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thank you for contributing to this Azure documentation. Unfortunately, changes to this content set cannot be accepted this week. The Skilling Content group is migrating this content to a new repository: azure-compute-docs.
In the meantime, we are closing this PR and tagging it so that when the content is available in the new repo, we can follow up with new location information.
#label:"migrate-followup"
#please-close

@mvelikikh
We're happy to share that contributions to virtual-machines are once again possible at azure-compute-docs. Please open a PR in the new repo to submit your changes. We appreciated your patience during this migration.
#remove-label:"migrate-followup"


feat: Add extra param to waitForReact (#273)

This adds an extra param to the waitForReact function to directly input the path to the resq loader.  This solves the issue with Webpack and allows arbitrary loading of different module resolution.
Related issue #273

@abhinaba-ghosh This was really the only way I was able to get webpack to play nicely with loading module paths at runtime. The readme for this change isn't updated as it's really just an escape hatch for using webpack. It is backwards compatible though and completely optional for the user.

@ajhenry thanks for the PR. Amazing, that you have figured out the solution. 🏆
Would you mind updating the readme file with necessary details and this we back handling information as well?

I added a small note in the readme 🚀

Hi @ajhenry , the update is available in the version v2.3.15 🚀

Thanks a ton!


Feature request: create app from FS

In local development environment it's difficult to create apps from local source, i.e. I have a local project and I want to run it in Lattice. Instead of building an image and pushing it to registry I want to do something like that:
$ ls -l
Dockerfile
app.jar
$ ltc create app --from-fs .

Which will build an image from local file system.
Otherwise, you can just run repository inside lattice and then do something like:
$ docker build -t "<IP_ADDRESS>.xip.io/corp/sample-app" .
$ docker push <IP_ADDRESS>.xip.io/corp/sample-app
$ ltc create app <IP_ADDRESS>.xip.io/corp/sample-app

Lattice consumes and runs Docker images.  Not Dockerfiles.  To make the developer experience a bit more friendly we are considering running a private registry & docker daemon within Lattice to support your second workflow.  We would still defer to the docker CLI to build and push the images so developers will be required to install Docker.

@onsi as I said - private registry is totally ok to me and looks like a good solution not only for development, but for test, staging and even production environments.
Thanks!

Hey @bsideup,
Have you checked out our latest release, v0.3.0? In this release, Lattice now has Cloud Foundry Buildpack support, and stores the resultant 'droplet' on an internal blob store.
I think this more than addresses your suggestion. I hope you like what we've done. I know you were thinking in the context of Docker images, but we are planning to support extracting a Docker image from the 'droplet' even if they're not required to run on Lattice: #101094710. Lattice does not actually use Docker/dockerd to run our containers. Instead it takes a Docker image (and now a droplet) and submits it to Garden, which is our container execution component.
I'm going to close this ticket for now. Of course, if you think we've missed something, please feel free to re-open this issue or create a new one.
--
Marco Nicosia
Product Manager
Pivotal Software, Inc.


add tcell's dim text style

Closes #328 .
PS: Please note that this is my first golang contribution. Kindly, let me know if I left out any necessary changes. I am also new to testing. I simply ran go test in this case and it passed.

Thank you for the contribution @icy-comet. I apologize for the delay - I am currently traveling and won't have the means to review this until after 7/6.
Meanwhile, could you please acknowledge that you give me approval to also merge this code into the master branch when releasing the next version? This will be needed to pass the CLA check on the release PR.

Meanwhile, could you please acknowledge that you give me approval to also merge this code into the master branch when releasing the next version?

Yes. I have also signed the CLA @ cla.developers.google.com


feat: inspect container

Inspect a specific container on a node.

Codecov Report
Attention: 53 lines in your changes are missing coverage. Please review.

Comparison is base (4b1f9ea) 26.44% compared to head (93b1ae0) 26.30%.
Report is 2 commits behind head on develop.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #841      +/-   ##
===========================================
- Coverage    26.44%   26.30%   -0.15%
===========================================
  Files           70       70
  Lines         7290     7345      +55
===========================================
+ Hits          1928     1932       +4
- Misses        5211     5262      +51
  Partials       151      151

Files
Coverage Δ

golang/pkg/dagent/utils/docker.go
3.03% <0.00%> (-0.14%)
:arrow_down:

golang/internal/grpc/grpc.go
0.63% <0.00%> (-0.03%)
:arrow_down:

... and 2 files with indirect coverage changes

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


[BUG] horizontalBar chart with multiple axes not rendering correctly

Expected Behavior
The horizontalBar chart should plot the labels on the left with multiple scales/axes on the top and bottom (similar to the bar chart)
Current Behavior
Setting the position of the first yAxis in options to anything other than left causes unexpected behaviors with the data labels (which should be rendered on the left). The data in the second dataset is not bound to either axis.
Possible Solution
There may be an issue with how the horizontalBar is implemented - it appears the there is an issue when iterating the yAxisID property of the datasets which introduces a bug in binding to the data
Steps to Reproduce (for bugs)
JSFiddle example of bug
JSFiddle of working bar chart that should be plotted horizontally (with labels on the left)
Context
It would be nice if lengthy labels could be plotted on the left with differing bar scales that are plotted on the top and bottom showing related information where the scales may be vastly different
Environment

Chart.js version: 2.5.0
Browser name and version: Google Chrome Version 58.0.3029.110 (64-bit)

@ttpb2006 I think the issue here is that you've created 2 y axes, instead of 2 x axes. If I understand correctly, you want one set of labels on the left and then 2 horizontal axes (top & bottom). Creating 2 x axes will do this. See https://jsfiddle.net/1n78t6yy/1/

Closing as answered per the above comment

I have had a similar problem. @etimberg, if you use same example than you, but without next lines the example does not work:
 position: "top",
 type: 'linear',

https://jsfiddle.net/6xow357q/1/
I don't know why these lines are necesary only in second xAxes. Also if I add these lines in both xAxes you will get an error too.
Thanks!!


Export everything using the PreferredVersion

First PR for https://github.com/konveyor/crane/issues/128
Fixes https://github.com/konveyor/crane/issues/102 with an upcoming PR to crane-lib

/hold cancel


Name server mode fix

100% agree with all of this. Going to move into a different issue, very different part of code base affected and doesn't need to block this particular PR.


Spiky Bracers - How do they work with outlier cards?

Ok, problems with:

Doppelganger: if you spend 3 Energy, it does not cost 1-less.
Malaise: spent 6 Energy, nothing.
Force Field: a little OP since you can add Spiky Bracers effect BEFORE it costs 1-less, but honestly, it the player figured this out, the player can go for it with the card.
Reinforced Body: if you spend 3 Energy, it does not cost 1-less.
Tempest: if you spend 3 Energy, it does not cost 1-less.
Multi-cast: same as above.
Transmutation: as above...

So basically all X cost cards.


Establish initial setup with config.json and readme.md

To try out some initial fetch scenario's we need an initial setup with a valid config file and some readme instructions to try out.

When we get something checked in and can see how it looks, I have a feeling that some of the items in this readme need to be split out and put into other places. @kytrinyx I haven't really seen a clear recipe of what to put where - its seems a bit sprawling and almost trial and error to put the right docs in the right place. I don't mind per say - but it does make kickstarting a new track a bit trickier.

Not sure who is doing merging of PR's

I'd rather not be the sole person approving/doing merges as that gives our project a bus factor of 1 i.e. a single point of failure. @macta and @bencoman you both should be contributors by now. Do you have the ability to do merge PR's? If that is so that gives us three approvers and increases our bus factor. You've both been enthusiastically contributing so if you feel a PR meets acceptance criteria then go ahead and merge (that is if you can).

its seems a bit sprawling and almost trial and error to put the right docs in the right place.

@macta I think Pharo is different enough from other programming languages so that we will end up with a slightly unique repo when compared with other language tracks. In the short term when lacking better guidance follow your own intuition. I think a lot of our early work will still be a draft even after merging. This is fine as we can be flexible in these early stages as we find what feels right.

I've merged this one - but strangely the readme.md seems different than the one in the branch (possibly user error - but I'm trying to explain what happened - it seems to have lost 2 paragraphs)

Just removed the extra H2 - I think this was just overlooked and so no merge error


Add diagnostic and completion tags

These appear in the 3.15 spec, and provide a way to provide additional metadata about diagnostics and completion items. For instance, the "Unnecessary" tag says this diagnostic warns about unused code or definitions.
Example
Just demonstrating the "unused" tag being rendered by VS Code.

Thank you!


Exception being swallowed?

As of v1.3.0, when the js code throws an exception it seems to be getting swallowed by some top-level trap:
$ cat examples/exception/script.js

function greet() {
  throw new Error("I am a JS exception")
}
module.exports = { greet };

$ extism call examples/exception.wasm greet --input="Hello" --wasi
Error: Exception generated by QuickJS
returned non-zero exit code:<PHONE_NUMBER>

This exit code a bit bizarre also. I suspect this might be related to the rquickjs refactor but not sure. When we do figure it out we need to add a test for this.

I think i found where the exception is originating from at least:
https://github.com/DelSkayn/rquickjs/blob/6d8f612636c1a6d4b4acd7a78ce30063666a1b78/core/src/result.rs#L530
Maybe we need to refactor the error handling code.


Update AD-Forest-Recovery-Reset-Computer-Account-DC.md

The description of the 2. step is wrong and would therefor lead to wrong usage of the statement.

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


[BUG] longhorn-manager not starting due to poddisruptionbudget policy error

Describe the bug
It seems that a cluster role/role does not permit longhorn-manager to start.
To Reproduce
apply  https://raw.githubusercontent.com/longhorn/longhorn/v1.1.0/deploy/longhorn.yaml to a cluster.
Expected behavior
Longhorn-manager starts.
Log
kubectl -n longhorn-system logs longhorn-manager-6nx65
time="2020-12-05T13:47:00Z" level=info msg="Start overwriting built-in settings with customized values"
W1205 13:47:00.260457       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2020-12-05T13:47:00Z" level=info msg="cannot list the content of the src directory /var/lib/rancher/longhorn/engine-binaries for the copy, will do nothing: Failed to execute: nsenter [--mount=/host/proc/1/ns/mnt --net=/host/proc/1/ns/net bash -c ls /var/lib/rancher/longhorn/engine-binaries/*], output , stderr, ls: cannot access '/var/lib/rancher/longhorn/engine-binaries/*': No such file or directory\n, error exit status 2"
I1205 13:47:00.310257       1 leaderelection.go:241] attempting to acquire leader lease  longhorn-system/longhorn-manager-upgrade-lock...
time="2020-12-05T13:47:00Z" level=info msg="New upgrade leader elected: worker4"
I1205 13:47:07.465005       1 leaderelection.go:251] successfully acquired lease longhorn-system/longhorn-manager-upgrade-lock
time="2020-12-05T13:47:07Z" level=info msg="Start upgrading"
time="2020-12-05T13:47:07Z" level=info msg="No API version upgrade is needed"
time="2020-12-05T13:47:08Z" level=info msg="Finish upgrading"
time="2020-12-05T13:47:08Z" level=info msg="Upgrade leader lost: worker1"
W1205 13:47:08.282022       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1205 13:47:08.300709       1 shared_informer.go:197] Waiting for caches to sync for longhorn datastore
E1205 13:47:08.565630       1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:longhorn-system:longhorn-service-account" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope
E1205 13:47:09.575754       1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:longhorn-system:longhorn-service-account" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope
E1205 13:47:10.578954       1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:longhorn-system:longhorn-service-account" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope
E1205 13:47:11.581827       1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:longhorn-system:longhorn-service-account" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope
E1205 13:47:12.585127       1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:longhorn-system:longhorn-service-account" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope
E1205 13:47:13.587970       1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:longhorn-system:longhorn-service-account" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope

Environment:

Longhorn version: v1.1.0/master

Kubernetes version:

kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.4", GitCommit:"d360454c9bcd1634cf4cc52d1867af5491dc9c5f", GitTreeState:"clean", BuildDate:"2020-11-11T13:17:17Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.4+k3s1", GitCommit:"2532c10faad43e2b6e728fdcc01662dc13d37764", GitTreeState:"clean", BuildDate:"2020-11-18T22:10:39Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/arm64"}

Node config

OS type and version
ubuntu 20.04 server on raspi4
CPU per node:
4
Memory per node:
8GB
Disk type
NVMe
Network bandwidth and latency between the nodes:
1Gb

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
baremetal on raspi4 cluster

Additional context
n/a

Seems related to #1818, but note, that this is not the chart deployment, but vanilla yaml

I applied the following change:

This seemed to fix the problem...

We haven't start the final release process yet, so the yaml in the longhorn/longhorn(even for v1.1.0) hasn't been updated. Before RC1, we recommend to use the tank at longhorn/longhorn-manager to deploy, which contains the latest master (and Pod Disruption Budget config etc)


[Bug]

What happened?
I am running boxbilling within a subdomain. It has its own path and I changed .htaccess.txt to .htaccess. This is not working and I still receive 404 errors when accessing any other page than index.php. I know FOSSbilling is the newer version, however, I found too many bugs in comparison to Boxbilling currently.
BoxBilling Version
v4.21
What version of PHP are you running?
PHP 8.0
Additional Notes
Additional notes

@waylenwasywas
FOSSBilling is not exactly a new version. It's a fork, so it is being developed separately. Right now they are very similar, but as time goes by they are likely to get further and further apart.
With that said, I am not aware of many bugs that are in FOSSBilling that are not also in BoxBilling, if you do find some then please report them in the FOSSBilling repository.
Regarding the 404 issue, is your server running Apache, nginx, or Litespeed?

With that said, I am not aware of many bugs that are in FOSSBilling that are not also in BoxBilling, if you do find some then please report them in the FOSSBilling repository.

When I engineered BoxBilling releases, I cherry-picked changes from the master branch and applied the changes to a sperate branch (you can find one for each release).
I did this, because there were quite a few changes that introduced regressions. Each release had one main focus: bug fixes and stability.
So there are quite a few bug that are missing in the BoxBilling releases that  still haven't been patched in our master branch. Because of this and new bugs introduced with the new admin theme, BoxBilling releases most definitely are more stable than FossBilling's master development branch


Add CORS policy support via OPTIONS method

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

19 of 20 (95.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.849%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/GraphQL.AspNetCore3/GraphQLHttpMiddlewareOptions.cs
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
1683

Relevant Lines:
1717

💛  - Coveralls


Add flow and b64_ocaml. [phab:D362]

Created by zarko at 2015-06-24 18:02:10:
This diff adds flow and b64_ocaml to third_party,
as well as stubs for a JavaScript indexer. Rather
than try to call into Flow, we instead initially plan to
add a new Flow command (dump-kythe) that makes use
of the existing client/server framework. Adding this
command requires applying a small patch to Flow proper
to register the client- and server-side code; we also
add symlinks to the Kythe stubs to make use of Flow's
existing ocamlbuild-based build.
This will be an optional feature. We will not
require Kythe users to install ocaml to build or
test Kythe.

fromberger wrote at 2015-06-24 18:46:04:
Will these be brought in along with the rest of Kythe when we import?
If so, we should probably make sure they're compatible with the third-party constraints (or omit them from the import script).
Otherwise this change seems fine.

fromberger wrote at 2015-06-24 20:02:31:
Per our offline discussion, looks good.

fromberger accepted this revision at 2015-06-24 20:02:31

jdennett accepted this revision at 2015-07-08 16:50:46

zarko closed via commit 40cceeb5330aea05ff4dc8fe2cc78c8076990259 at 2015-07-08 17:05:12


Update README on how to install additional deps

@spulec Introduces documentation for #3281
Fixes #3290

Coverage decreased (-0.3%) to 94.138% when pulling 2eae3996c0247932b5edd8ae4d92acfee602e9df on bblommers-readme-dependencies into 06d403d31309fe7174ea98b7d81d4b2db1fc6aaf on master.

Please include somewhere what packages are required byspecific featured. For example using SQS or SNS apparently requires the awslambda package, which is in no way obvious to a user and is not specified in this very unfulfilling addition.

Closing this - relevant changes are now part of #3314


Updated Project Portfolio

Coverage remained the same at 85.219% when pulling 1ea11c7233481c63a710936f2cb1dcbe5bd5ed3a on awarenessxz:v1.5_Others into a6bd1a12cfe4ad7710a5bcfa3add60b70b6de112 on CS2103AUG2017-W14-B2:master.


chore:foundry test for LineaWorldID

issue: #4
creating a comprehensive end-to-end test for the entire World ID state bridge system. to ensure that all components work together correctly and that the cross-chain functionality operates as expected.

still working on this would complete soon

Hi @Jemiiah! Could you please run forge fmt?

okay ser

i did that

i will close this one and create a new pr @kfastov


Add file/delete message

Pull Request Description

close #534
Important Notes

add file/delete message that asks the file manager to delete the specified file system object
add tests
update engine-services doc

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Scala, Java, Rust or Haskell style guides as appropriate.
[x] All code has been tested where possible.

@lolczak all review comments are fixed :tada:


Propagate Tracing information when consuming events

Is your feature request related to a problem? Please describe.
With the current implementation we are not re-initializing the Span Context properly and therefore loose the trace-id for the current flow.
Describe the solution you'd like
Introduce an extra module that would bring back the tracing information to the SpanContext once an event is read from Nakadi that transports this information.

see #359


Make kingress conformance amenable to KinD

Two main changes:

Use imagePullPolicy: IfNotPresent to support preloading the test images with ko + kind.local
Don't require the service exposed in the kingress status to have type LoadBalancer when we've been handed an --ingressendpoint.  This is indicative of local environments like KinD or minikube where the type: LoadBalancer service may have been changes to type: NodePort.

cc @nak3 @ZhiminXiang

I feel like --ingressendpoint is going to be inadequate because we won't hit the same port for both http and https.
Perhaps the proper fix would be to allow the service to be NodePort when an IP is specified via --ingressendpoint and select the appropriate node port from the service...

Here's a run of kingress conformance passing with this vendored: https://github.com/mattmoor/net-contour/runs/1079033774?check_suite_focus=true


Gc 1108 add status on mailpieces

GC-1108

Checklist

[x] Up to date with main
[x] All the tests are passing

[x ] Delete all resources created in tests

[x] Prettier
[x] Spectral Lint
[x] npm run bundle outputs nothing suspect
[x] npm run postman outputs nothing suspect

Changes
Areas of Concern (optional)

@bamohan  Good call! I will close this PR for now and move this task to backlog!  We can re-open when we are ready to release 😄


Setup cronjob to log output to STDOUT

Tried to modify crontab to following. It executes successfully, but doesn't seem to be piping to stdout.
*/1 * * * * su -c "/usr/local/bin/php /srv/www/update/cron.php" -s /bin/sh www-data > /proc/self/fd/2 2>&1
*/1 * * * * su -c "/usr/local/bin/php /srv/www/bin/magento-php cron:run" -s /bin/sh www-data > /proc/self/fd/2 2>&1
*/1 * * * * su -c "/usr/local/bin/php /srv/www/bin/magento-php setup:cron:run" -s /bin/sh www-data > /proc/self/fd/2 2>&1

Anyone know why? Fyi, /proc/self/fd/2 should be stdout; it's the same location used in php-fpm config https://github.com/mageinferno/docker-magento2-php/blob/master/conf/php-fpm.conf#L6

Got it! Seems the correct location for crontab output is /proc/1/fd/2.

Released in 5.6.23-fpm-3 & 7.0.8-fpm


Playing well, when root logger is initialized

Frontera is using native python logging module. When root logger is initialized with stdout handlers, frontera is adding it's own handlers and that leads to duplicate output.

Solved with https://github.com/scrapinghub/frontera/pull/143


added encode and decode methods to django cache session backend. ticket #23764

Merged cleanly locally

ticket #23764

Isn't this going to break when trying to decode already existing sessions that have not been encoded?

looking at the try within the decode, I think it would just return an empty session, essentially logging users out. After they log in again their new sessions would be encoded.

I think forcing all users to log out when Django is upgraded isn't acceptable. We've had similar fixes in the past where we've had to add a workaround to prevent it.


Cannot find Trainer when predicting with open source pre-trained model.

Hello, first of all, thank you for your excellent open source project, it helped me a lot. I encountered the following problem when using MultiTalent and I hope you can answer it. After downloading your open source pre-trained model, I got an error when predicting data: ‘RuntimeError: Could not find the model trainer specified in checkpoint in nnunet.trainig.network_training. If it is not located there, please move it or change the code of restore_model. Your model trainer can be located in any directory within nnunet.trainig.network_training (search is recursive).’ I looked at the code and this Trainer might be in the meddec package, but this package is your private one, so I can’t predict. Could you please tell me if there is an open source plan for this nnUNetTrainerV2_leBFnnUNet4_regions_forceBD_DDP_customSplit_sqrtDSSampling_2000epochs corresponding Trainer, so that I can continue to use this model to predict, thank you!

Hi, "nnUNetTrainerV2_leBFnnUNet4_regions_forceBD_DDP_customSplit_sqrtDSSampling_2000epochs" was an internal name and should not be used anymore. Could you give me your full error message and the command you used?


Sdio driver feature

Ignore #3. I replayed ARMmbed/mbed-os#10235 (without the mbed-os part that I put here).
With this PR, you can add a sdio-driver.lib in your project (+ a few tweaks to mbed_app.json) and use other for storage_filesystem.blockdevice:
#include "SDIOBlockDevice.h"
static SDIOBlockDevice bd;

BlockDevice *get_other_blockdevice()
{
    return &bd;
}

BlockDevice *BlockDevice::get_default_instance()
{
    return &bd;
}

I have created also another repository, to semi-automatically integrate the sdio-driver into MbedOS. It also documents how I have used it to test mbed-bootloader and mbed-cloud-client-example / pelion-example-common with DISCO_F746NG and LPC55S69_NS.

Sorry for the delay, I should have a look the upcoming week at this one.

@0xc0170: I think the idea with having DEVICE_SDIO_ASYNC is that the async drivers would not have to be duplicating some of the logic and putting the wait logic in control of SDIOBlockDevice. I think @orenc17 did that part. In my #3 version, I did add the timeout value to the HAL call and left the wait in the low-level part. Your call.
I will look into the other changes.

@ARMmbed/mbed-os-storage Could you please review?

What's the status of the sdio blockdevice feature? I have a need for one of my custom boards. I'd be interested in helping integrate this feature to mbed-os master!
@maclobdell

@AGlass0fMilk @mathias-arm as part of the silicon partner governance, a design document was proposed for official SDIO https://github.com/ARMmbed/mbed-os/pull/11847. There was some work initially but it seems to have stalled a bit. It would be great if you can review that document and provide your feedback and we can push it a bit closer to completion.


Error: invalid device symbol

When running in Ubuntu 20.04, Cuda 11.4

same error, what could be causing it?

same error, what could be causing it? version v7_gpu_trial
RTX3090

For me, it turned out to be a power problem causing PCI BUS instability. 8x 3090Ti


[Fix] Fix GPTBigcoder for distributed execution

Fix #488 and #487

@WoosukKwon This PR is ready to review!


Overhaul Cleanup methods, implement vm_creation_time, other.

There's a lot here.  Perhaps a meeting to review would be best.

Lint report for commit 49d17d115e655100cbd5dd6994ff2b0576357144:
mgmtsystem/azure.py:

:grey_exclamation: Line 212:69: S001 found % formatter
:bangbang: Line 382:45: E226 missing whitespace around arithmetic operator
:bangbang: Line 383:62: E226 missing whitespace around arithmetic operator
:red_circle: Line 385:21: F821 undefined name 'delete_vm'

Please, rectify these issues :smirk: .
Commit inspection report:
No commit flaws detected.
CFME QE Bot

Lint report for commit f8953eef9b8532c1dfcbf70fca010c8ca57d3ba6:
mgmtsystem/azure.py:

:bangbang: Line 154:9: E265 block comment should start with '# '
:grey_exclamation: Line 210:69: S001 found % formatter

Please, rectify these issues :smirk: .
Commit inspection report:
No commit flaws detected.
CFME QE Bot

Lint report for commit c7cc1a22a759b4a8b794ece898c1345de046dd4d:
mgmtsystem/azure.py:

:grey_exclamation: Line 210:69: S001 found % formatter

Please, rectify these issues :smirk: .
Commit inspection report:
No commit flaws detected.
CFME QE Bot

The %s lint issue can be ignored, date formatter.

Lint report for commit 3b7b2ce0be4732bd187a8259fcfd7282d5497dc9:
mgmtsystem/azure.py:

:grey_exclamation: Line 210:69: S001 found % formatter

Please, rectify these issues :smirk: .
Commit inspection report:
No commit flaws detected.
CFME QE Bot

Lint report for commit 77e49df5783147575b31811d51b3cb5a1254359a:
mgmtsystem/azure.py:

:grey_exclamation: Line 207:69: S001 found % formatter

Please, rectify these issues :smirk: .
Commit inspection report:
No commit flaws detected.


Bump dependencies

Signed-off-by: Daniel Egger<EMAIL_ADDRESS>

r? @ryankurte
(rust_highfive has picked a reviewer for you, use r? to override)

bors try

r? @burrbull

I'm planning on doing a release with the current version to get the latest benefits, especially the speedup out into the world.

bors r+


[BEAM-4077] Schema fields are non-null by default

Before this change, every field was explicitly called out as nullable or not. It was inconvenient. This makes them non-null by default.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

Actually this needs some deeper work.


[Moniker] not working for most videos

Most videos from allmyvideos.net and vidspot.net are not working. This long video works, but most other ones not, I picked some random videos: not working 1 not working 2.
Vidspot:
$ youtube-dl "http://vidspot.net/2/v-ywDf99" --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'http://vidspot.net/2/v-ywDf99', u'--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.10.18
[debug] Python version 2.7.6 - Linux-3.16.0-38-generic-x86_64-with-LinuxMint-17.2-rafaela
[debug] exe versions: ffmpeg N-75403-g3a8e447, ffprobe N-75403-g3a8e447
[debug] Proxy map: {}
[Moniker] 2: Downloading webpage
[Moniker] 2: Downloading video page ...
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 330, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1873, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python2.7/urllib2.py", line 410, in open
    response = meth(req, response)
  File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.7/urllib2.py", line 448, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

Allmyvideos:
$ youtube-dl "http://allmyvideos.net/v/v-HXZm5t" --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'http://allmyvideos.net/v/v-HXZm5t', u'--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.10.18
[debug] Python version 2.7.6 - Linux-3.16.0-38-generic-x86_64-with-LinuxMint-17.2-rafaela
[debug] exe versions: ffmpeg N-75403-g3a8e447, ffprobe N-75403-g3a8e447
[debug] Proxy map: {}
[Moniker] v: Downloading webpage
[Moniker] v: Downloading video page ...
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 330, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1873, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python2.7/urllib2.py", line 410, in open
    response = meth(req, response)
  File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.7/urllib2.py", line 448, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

i tried pinging it and it doesn't seem valid
ping: cannot resolve http://vidspot.net: Unknown host

FYI: ping vidspot.net is correct while ping http://vidspot.net/ is wrong.

Of course it is valid, just go to the website...

my bash script strips and formats any url to pipe into any command


Add a metric to provide missed events per type

Example:
$ curl localhost:2112/metrics 2> /dev/null | grep 'sent_events_total\|missed_events_total\|ringbuf_perf_event_lost_total\|ringbuf_queue_lost_total\|msg_op_total\|ringbuf_queue_received_total'
# HELP tetragon_missed_events_total The total number of Tetragon events per type that are failed to sent from the kernel.
# TYPE tetragon_missed_events_total counter
tetragon_missed_events_total{msg_op="13"} 73300
tetragon_missed_events_total{msg_op="23"} 28
tetragon_missed_events_total{msg_op="24"} 606
tetragon_missed_events_total{msg_op="5"} 20
tetragon_missed_events_total{msg_op="7"} 22
# HELP tetragon_msg_op_total The total number of times we encounter a given message opcode. For internal use only.
# TYPE tetragon_msg_op_total counter
tetragon_msg_op_total{msg_op="13"} 4.268532e+06
tetragon_msg_op_total{msg_op="23"} 12444
tetragon_msg_op_total{msg_op="24"} 2110
tetragon_msg_op_total{msg_op="5"} 11908
tetragon_msg_op_total{msg_op="7"} 12447
# HELP tetragon_ringbuf_perf_event_lost_total The total number of Tetragon ringbuf perf events lost.
# TYPE tetragon_ringbuf_perf_event_lost_total counter
tetragon_ringbuf_perf_event_lost_total 73976
# HELP tetragon_ringbuf_queue_lost_total The total number of Tetragon events ring buffer queue lost.
# TYPE tetragon_ringbuf_queue_lost_total counter
tetragon_ringbuf_queue_lost_total 0
# HELP tetragon_ringbuf_queue_received_total The total number of Tetragon events ring buffer queue received.
# TYPE tetragon_ringbuf_queue_received_total counter
tetragon_ringbuf_queue_received_total 4.307441e+06

This PR adds an eBPF map collector for getting metrics directly from a map. This map contains information about the return values of all perf_event_output calls (i.e. if it fails). This provides us the ability to determine missed events per type. Metric tetragon_missed_events_total contains such information.
Using the previous example, we can see that we lost 73976 events from the user-space (tetragon_ringbuf_perf_event_lost_total). This is the same as the sum of all tetragon_missed_events_total metrics gathered from the kernel.

I left some comments :) The most important one being that it looks like we want to expose two different metric names here.

Thanks for the review! I have made the changes that you proposed.

Thanks! I think this will be very useful to have, which is why I added a backport label for 1.0.

Backport PR: https://github.com/cilium/tetragon/pull/1702


Platform dapr integration

Issue #, if available:
Description of changes:
Platform dapr integration. to support

Dapr Implementation to Mgmt and Child clusters
Component based data store deployments to region specific data store setup
Resiliency Policies for Micro service to microservice communication
Resiliency Policies for Micro service to data store communication
Resiliency Policies such as Retries, TimeOuts, Circuit breakers

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

How are the apps deployed? Do we need to include a simple OAM manifest for these under deployment?

Apps can be deployed using the YAMLs present in deployment folder for demonstration purposes. Once we start working on implementing DAPR for Apps like Rust, .Net, the sample Node and Python App can be removed.


gostreamdeck: Still:Select pic index

There are only 31 slots
for stills (starts at Pic1
and goes up to Pic31)

Solved in commit 3811eaf55d66a94525ddadec780766a2e0c352ad


Failed to open the database(30)

Describe the bug
I have created a read only volume with a snapshot of the reth data directory with the intent of reading the db only.
When subsequently opening the DB from a volume mounted as read_only I get Failed to open the database(30)
Steps to reproduce

Run Reth in kube context with PVC
Create snapshot of PVC
Spin up readonly PVC of snapshot
Start workload in kube with volume mounted as read only
check logs and see unable to openDB

Node logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
reth version was 12 when snapshot was taken
What database version are you on?
reth version was alpha.12 when snapshot was taken
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

further context.
When this is done using a GCE PD mounted as read only(ro,noload) this works
When moved over to GKE and using a PVC mounted as read only and running from within a container error 30 is returned

It seems like even though the DB is being openned as read only the mdbx.lck is being written to. To test this out further I was able to setup some symlinks so the mdbx.dat was symlinked into a writable directory. upon opening the db as read only the directory had another file mdbx.lck

What's the right fix here @argakiig?
@shekhirin should we disable the creation of mdbx.lck on read? i think probably cannot?

I may be reading the docs wrong? https://erthink.github.io/libmdbx/group__c__opening.html

specifically, it seems like it should be able to open without touching the lock file if readonly

Bumping,  it seems to me from the documentation I linked it shouldn't matter if it can do anything with the lock file. If the filesystem is read only and you open it read only why does it touch the lck? Is this the intended mdbx behavior or is this a mdbx bug?


update to oscn v59, refactor using new event dict

Includes test for api views.  Breaks sms app.

Move my new tests to a directory.  Once merged, we can move the tests.py into the directory.

I merged with master (to run the tests from those newer commits), and they run fine, so it LGTM, but I'll let someone else push the button :grimacing:


Fix unhandled promise rejection error on failed persistent subscription on start

EventStorePersistentSubscriptionBase.prototype.start invokes a promise, but does not catch the error. This behavior is deprecated:

(node:15285) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

To resolve this, I passed the error along to the subscriptionDropped callback.

@nicdex please take a look. Thanks!

Sorry for the delay I've just been really busy lately. Will take a look this weekend.

Thank you for the pull request I really appreciate your interest in this project.
I've found a better way to fix the problem, I will change connectToPersistentSubscription to return a Promise instead.
This way the promise can be returned directly instead of invoking the dropped handler. It's also what the original client does, I try to keep the API/behavior close to the C# one.
Does this work for you?

Absolutely! Thank you. I strongly prefer promises all around.


"expect is not defined" when importing jest-enzyme in setup.js

I am using Jest 20 with Enzyme 2.8.0.
Importing jest-enzyme in my test files works, but as soon as I put it in my setup.js I am getting the following error:
    ReferenceError: expect is not defined

      at Object.<anonymous> (node_modules/jest-enzyme/lib/index.js:23:1)

Here's my setup.js file:
/* eslint-disable no-console */

require('jest-enzyme');
require('react-native-mock-render/mock');
const { jsdom } = require('jsdom');

global.document = jsdom('');
global.window = document.defaultView;
Object.keys(document.defaultView).forEach((property) => {
	if (typeof global[property] === 'undefined') {
		global[property] = document.defaultView[property];
	}
});

const { Response, Headers, Request } = require('whatwg-fetch');

global.Response = Response;
global.Headers = Headers;
global.Request = Request;

jest.mock('Linking', () => ({
	addEventListener: jest.fn(),
	removeEventListener: jest.fn(),
	openURL: jest.genMockFn().mockReturnValue(Promise.resolve()),
	canOpenURL: jest.genMockFn().mockReturnValue(Promise.resolve()),
	getInitialURL: jest.genMockFn().mockReturnValue(Promise.resolve()),
}));

jest.mock('react-native-snackbar', () => ({
	LENGTH_LONG: 1,
	LENGTH_SHORT: 1,
	LENGTH_INDEFINITE: 1,
}));

const originalConsoleError = console.error;
console.error = (message) => {
	// see https://github.com/Root-App/react-native-mock-render/issues/6
	if (message.startsWith('Warning: Unknown prop')) {
		return;
	}

	originalConsoleError(message);
};

I tried rolling back to Jest 19 and putting the import at the end of file, didn't help.
What could be the problem?

Could you try upgrading to 3.1.0?

I had 3.1.1, downgrading to 3.1.0 didn't fix the problem.

@andriichernenko did you figure this out? I honestly have no clue why your environment would be doing that.

@blainekasten no, I did not. I ended up not using jest-enzyme in my project. I guess this issue can be closed.

Ah, sorry about this. Wish I could help more!

Hey @andriichernenko, I stumbled across this myself trying to use the jest-glamor-react package. If you want to extend expect, you must do it in the file specified by setupTestFrameworkScriptFile in your jest config and not setupFiles. i.e:
// expect will not be defined in these files
"setupFiles": ["<rootDir>/config/polyfills.js"],
// but it will be defined in this file.
"setupTestFrameworkScriptFile": "<rootDir>/config/jest/setup.js"

Let me know if that helps.

If you're still having the issue after the above, try updating your node version. We were attempting against node 10, and it did not pass, but upgrading to 13 fixed.

I followed this guide and finally it worked:
https://medium.com/@hdsenevi/unit-testing-in-react-native-with-jest-and-enzyme-40cd7dabb6f1

I am facing the same issue:
jest.config.js
module.exports = {
  preset: 'react-native',
  collectCoverage: true,
  moduleDirectories: ['node_modules', 'src'],
  transform: {
    '^.+\\.js$': '<rootDir>/node_modules/react-native/jest/preprocessor.js',
  },
  setupFiles: ['<rootDir>setup-tests.js'],
  transformIgnorePatterns: ['node_modules/(?!(jest-)?react-native)'],
  coveragePathIgnorePatterns: ['/node_modules/', '/jest'],
  testEnvironment: 'jsdom',
};

setup-tests.js
import 'react-native';
import 'jest-enzyme';
import Adapter from 'enzyme-adapter-react-16';
import Enzyme from 'enzyme';

/**
 * Set up DOM in node.js environment for Enzyme to mount to
 */
const {JSDOM} = require('jsdom');

const jsdom = new JSDOM('<!doctype html>');
const {window} = jsdom;

function copyProps(src, target) {
  Object.defineProperties(target, {
    ...Object.getOwnPropertyDescriptors(src),
    ...Object.getOwnPropertyDescriptors(target),
  });
}

global.window = window;
global.document = window.document;
global.navigator = {
  userAgent: 'node.js',
};
copyProps(window, global);

/**
 * Set up Enzyme to mount to DOM, simulate events,
 * and inspect the DOM in tests.
 */
Enzyme.configure({adapter: new Adapter()});

Env.
   "enzyme": "^3.11.0",
    "enzyme-adapter-react-16": "^1.15.2",
    "babel-jest": "^24.9.0",
    "jest": "^26.0.1",
    "jest-enzyme": "^7.1.2",
    "jsdom": "^16.2.2",

Same issue, fixed by upgrading node v10.10 --> v10.15 (see original comment)


certain subcommands don't work

Might suggest removing them as they do not work today.
reckoner generate Stacktrace -- see below:
reckoner generate
2019-01-04 14:23:03 xps13-9370 root[16862] INFO Generating example course as course.yml
Traceback (most recent call last):
  File "/home/user/.pentagon/venv/bin/reckoner", line 11, in <module>
    sys.exit(cli())
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/reckoner/cli.py", line 62, in generate
    src = pkg_resources.resource_string("reckoner", "example-course.yml")
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1152, in resource_string
    self, resource_name
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1396, in get_resource_string
    return self._get(self._fn(self.module_path, resource_name))
  File "/home/user/.pentagon/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1519, in _get
    with open(path, 'rb') as stream:
IOError: [Errno 2] No such file or directory: '/home/user/.pentagon/venv/local/lib/python2.7/site-packages/reckoner/example-course.yml'

reckoner version
Traceback (most recent call last):
  File "/home/nhuanca/.pentagon/venv/bin/reckoner", line 11, in <module>
    sys.exit(cli())
  File "/path/to/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/path/to/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/path/to/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/path/to/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/path/to/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/path/to/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/path/to/reckoner/cli.py", line 72, in version
    print(reckoner.__version__)
NameError: global name 'reckoner' is not defined

#56

fixed in 1.0.0


Determine when task manager should start

When the app is started, it needs to somehow check if there is a game "in progress" or not. Basically, can we start the task-update loop, or do we need to create a new character?

Whose responsibility is this?
What is best practice apropos ngrx? Do we need events or something, or can we just start the task manager service and then have it subscribe to, say the curCharacter object in Store, and only start the loop once curCharacter is not empty?

TaskManagerService is now just subscribing to curCharacter and only acting when we have a new one.
The App component requires TaskManagerService, and thus a single instance is created when the app is started.


Pink line generated from the top left corner of the image

When I view the image, there is a pink line generated from the top left corner of the image. I tried to investigate the issue by printing variable "sc" from the file dataset_explorer.py, and I found a random value "6.91669498947497e-310, 6.91669498947497e-310" generated at the beginning. To overcome this issue, I added this line "sc = [x for x in sc if x > 0.1]" in the file dataset_explorer.py.
Screenshot:
Please refer to the attached screenshots for better understanding.

Expected Outcome:
The pink line should not be generated from the top left corner of the image.
Steps to Reproduce:

Run segment_anything_annotator.py.
Label any object.
Select the label name and click on the save button, then click on the add button.
The error will be found on the image.

I grappled with this for a few hours. I started with your suggestion sc = [x for x in sc if x > 0.1] but realized it handled some cases differently, specifically when the actual coordinate is 0 (i.e. along the top or left borders). Instead I handled the entries one pair at a time. I added these lines after L90:
tol = 1e-3
cleaned = []
for x, y in zip(sc[::2], sc[1::2]):
    if x > tol and y > tol:
        cleaned.append(x)
        cleaned.append(y)
annotation["segmenation"].append(cleaned)

It's not particularly compact but it seems to do the job.
The pair of coordinates at the origin appears to be an artifact of the call to simplify_coords_vwp and I'm not sure if it is consistently the first pair of elements, so best to go through the full list.

当我查看图像时，从图像的左上角生成了一条粉红色的线。我试图通过从文件dataset_explorer.py打印变量“sc”来调查这个问题，我发现开始时生成的随机值“6.91669498947497e-310，6.91669498947497e-310”。为了克服这个问题，我在文件dataset_explorer.py中添加了这一行“sc = [x for x in sc if x > 0.1]”。
截图：
请参阅随附的屏幕截图以更好地理解。

预期成果：
粉色线不应从图像的左上角生成。
重现步骤：

运行segment_anything_annotator.py。
标记任何对象。
选择标签名称并单击保存按钮，然后单击添加按钮。
将在图像上找到错误。

it is also have some problem


Text drop shadow

So, CSS has the ability to do drop shadows on text, making the text much easier to read.  When displaying text on a sign, this ability would help immensely.  Being that it's already a feature of CSS, is there a way we can implement drop shadows in our slide text?

This would definitely be possible through CSS but unfortunately there's currently no way to style LibreSignage slides using CSS. Slide styling via CSS is a feature that has been requested before, though, so I'll keep this in mind.


cache: Synchronize downloading

This commit adds code to synchronize downloading files to the cache. Before, requests that came in for files currently downloading would fail because the file was not completed in the cache. Now, the code waits until the download is completed.
Closes #1278

Codecov Report

Merging #1279 into master will decrease coverage by 0.26%.
The diff coverage is 23.91%.

@@            Coverage Diff             @@
##           master    #1279      +/-   ##
==========================================
- Coverage   52.34%   52.08%   -0.27%
==========================================
  Files         135      135
  Lines       12954    12994      +40
==========================================
- Hits         6781     6768      -13
- Misses       5344     5401      +57
+ Partials      829      825       -4

Impacted Files
Coverage Δ

internal/restic/snapshot.go
42.72% <0%> (ø)
:arrow_up:

internal/cache/cache.go
29.87% <100%> (-2.63%)
:arrow_down:

internal/cache/backend.go
36.49% <22.72%> (-6.06%)
:arrow_down:

internal/checker/checker.go
68.19% <0%> (-3.84%)
:arrow_down:

internal/archiver/archiver.go
65.36% <0%> (+0.16%)
:arrow_up:

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 bff1039...1aeccce. Read the comment docs.


adapter - make modbus driver

[ ] handle uint16 and uint32 values
[ ] handle different enddiannesses with a property, eg endian: little, default to most common

sencon pdf didn't mention endianness of the partcounts, so need to detect it or google it.
some discussion on endianness - https://wingpath.co.uk/modbus/modbus_extensions.php


Warp Coils

Hello ... I have an enhancement which would make the warpship even more StarTrek-like.
Did you ever thought about Warp Coils?
Warp Coil is an object... usually hiding in your nacelles (The long things at the back of a star trek ship)

The faster ship you want the more coils it needs.
Well in AdvancedRocketry it could be like this:
You need certain number of Coils on your ship, all facing the corect direction to be able to travel certain distance. And all has to be powered.
The number of Coils per distance unit or consumed dilithium can be configurable and so can be the required power input into one coil.
What do you think?

Taking enhancement out of the title as i gave it the tag.

The ship shouldn't be faster for having more coils, but it should be able to warp further.
I kinda like the idea of a customizable multiblock like this, with a balance between efficiency and travel distance. (Not travel time, though. I don't like waiting for long periods of time with nothing interesting to do in-between.)

I agree... it should influence definitely distance, not time.
Other idea is to make the diffrence between distance and number of coils non-linear... so it would not be such a greate difference between travel to next planet and travel to next star. But right configuration parameters could easily make this work.
Example of distances: If you have distance between stars 100 and differene between planets also 100, let's expect alpha centauri (5 LY = 2.5MLmin) and the second earth (10Lmin)... So let's say we can set that with every coil your ship can travel a distance with next power of 10 of light minutes. So...
1 coil = 1Lmin = 10 distance in-system
2 coils = 10Lmin (sun-earth) = 100 distance in-system
3 coils = 100 Lmin (entire solar system) = 1000 distance in-system
4 coils = 1'000 Lmin = 0.6 Lday
5 coils = 10'000 Lmin = 6 Lday = maybe a very close-by star (0.6 on the galaxy map)
6 coils = 100'000 Lmin = 2Lmonths = 6 on the galaxy map
7 coils = 1'000'000 Lmin = 20Lmonths = 60 on the galaxy map, a decent range.
The math:
So I see here a working example, where the coils create a distance A*(B^(count)) in the case above A = 1, B = 10. This should make it configurable enough even for the hardcore map creators who want to make their player's lives hell.

I agree. I also came up with an idea for an alternative fuel system Alternative Fuels Maybe it could include other types of matter on planets. (Leaving comment there with more info)

Higher tier coils should cut down on fuel cost.


Use Case: Describe/include software containers

As an open science researcher, I want to provide Docker/Singularity container images so that others can reliably reproduce my results or reuse the same software.
This implies that the container images and their recipes (e.g. Dockerfile) should be included in the RO-Crate and typed as such, so users know they can be executed.
It is desirable also to use tooling to expand the description with a list of dependencies installed in the container this will help provide light-weight software citations.
Related efforts to align with:

https://openschemas.github.io/specifications/
https://openschemas.github.io/schemaorg/
https://github.com/openbases/extract-dockerfile
https://sci-f.github.io/

Example descriptions generated by extract-dockerfile
From a Dockerfile we describe a ContainerRecipe (specializes SoftwareSourceCode
{
    "@context": "http://www.schema.org",
    "@type": "ContainerRecipe",
    "name": "vsoch/salad",
    "description": "A Dockerfile build recipe",
    "containerImage": "gliderlabs/alpine:3.4"

    "labels": [
        [
            "MAINTAINER toasterlint<EMAIL_ADDRESS>        ]
    ],
    "environment": [
        "RPCPORT=4000"
    ],
    "entrypoint": [
        "/entrypoint"
    ],
}

(see openschemas/specifications#10)
From a Docker image we describe a ContainerImage:
{
    "environment": [
        "SRC_DIR=/go/src/github.com/vsoch/salad/"
    ],
    "entrypoint": [
        "/code/salad"
    ],
    "description": "A Dockerfile build recipe",
    "name": "vanessa/sregistry",
    "ContainerImage": "iron/go:dev",
    "operatingSystem": "linux",
    "softwareVersion": "sha256:8d1e7f244db9e7cb85d5867bb3230f756460900e5801ff2303e44a79369640f4",
    "identifier": [
        "vanessa/sregistry:latest"
    ],
    "url": "https://hub.docker.com/r/vanessa/sregistry",
    "alternateName": "Singularity Registry",
    "softwareHelp": "https://singularityhub.github.io/sregistry",
    "citation": "http://joss.theoj.org/papers/050362b7e7691d2a5d0ebed8251bc01e",
    "license": "https://github.com/singularityhub/sregistry/blob/master/LICENSE",
    "keywords": "container, containers, singularity, singularity registry",
    "softwareRequirements": [
        "Pip > xmlsec==1.3.3"
    ],
    "@context": "http://www.schema.org",
    "@type": "ImageDefinition"
}

(however this type called ContainerImage rather than ImageDefinition so some stability with upstream specs would be needed.

See discussion in https://github.com/openbases/extract-dockerfile/issues/6 - there was some discussion over the name, my preference is for what is represented in https://openschemas.github.io/specifications/ because (as you correctly bring up) an ImageDefinition could refer to other kinds of images, but ContainerImage is more clear.

This is interesting! Would this need to be related to cwl as well? (which defines how to invoke the image as opposed to the definition of the image itself)
In Dockerpedia they have done a thorough extraction of images, although it's not aligned with schema. Maybe we can use their service for extraction too. An example:  https://dockerpedia.inf.utfsm.cl/resource/SoftwareImage/dockerpedia-pegasus_workflow_images_latest

I don't think it would be wise to "hard code" (so to speak) any particular workflow manager or description (e.g., cwl, snakemake, nextflow) directly into the specification. On the other hand, if there is an appropriate field to describe this same entity, it would be logical to include (e.g., if I find that it's snakemake, I should look for a Snakefile somewhere...)
For CWL, is there a definitive specification for interaction? For example, for a scif container, you can be absolutely sure how to discover applications inside (singularity run container.sif apps) and then how to run / inspect / shell / otherwise interact with an application you just found (e.g., singularity run container.sif run <app>.

CWL has a field for pulling from a docker container. Maybe that could be the hook.
My point is not necessarily to use a particular workflow spec. What I want to record is how the app in the container is supposed to be invoked and how to pass on the files. Since cwl describes this, it could be a starting point

Yes, understood! To be more clear, there are many different tools that describe in a structured way how a container (or app inside) is supposed to be invoked. Actually, those two things are different - cwl could describe an app in a container (and it would have to be provided via the entrypoint so the user could run it to find it) while SCIF describes how to invoke the container itself (of which cwl could be one or more entrypoints).
But from how you describe it - that there is a field for pulling the container, this sounds like it would need to be stored outside of the container, which is another point to discuss. SCIF is a specification that describes standard interaction with a container, and is installed inside the container, along with the SCIF filesystem and other metadata files that are defined for each app.

This is a necessary use case for Whole Tale. A few questions:

What about RO-Crates with repo2docker compatible configurations?
In the case of a Docker image, is the idea that the RO-Crate would contain a tar archive of the image or a reference to the image in a registry (or either)?
While not containers in the same sense, sciunit and reprozip also produce re-executable packages that could be parts of RO-Crates. Are these in scope?

Having a repo2docker configuration is an interesting and useful idea, but I think it would be done in addition to a container recipe - repo2docker in and of iteself doesn't translate to reproducibility - it just means that (assuming a version of repo2docker is available) you could build a container for it. You can think of it like an extra layer to essentially create a Dockerfile (that could be built). It also assumes a user "joyvan" that when converted to Singularity (e.g., for use on HPC) makes things a bit challenging because of the cardinal rule "the user inside the container is the user outside the container."
Re-reading what @stain mentioned - it sounds like he wants the full container, in which case Docker wouldn't be as feasible as it means layers that need to be assembled and require the Docker daemon. A Singularity (sif) binary would be more reasonable, albeit large, and still require Singularity to run. It's really the case that any level of recipe without the container runs the risk of not being able to be built, so probably providing the container somewhere is needed. In the case of Singularity, the recipe file is kept inside the container as well. In the case of Docker, the recipe (and other metadata) would serve as an external way to peep inside without invoking the container.
I'm not super familiar with RO-crates, but reading the description:

RO-Crate is a community effort to establish a lightweight approach to packaging research data with their metadata.

it does sound like a wrapper (with metadata) to a container is wanted? The container, considered as some kind of data, could also fit into the specification, and as @stain showed, metadata could be extracted for the jsonld.

Re-reading what @stain mentioned - it sounds like he wants the full container, in which case Docker wouldn't be as feasible as it means layers that need to be assembled and require the Docker daemon.

Indeed, you can generate with docker save a tar file with the different layers from one or more tagged  docker images, which can be used later to generate a singularity image with singularity import.
I also agree the container recipe is worth to be saved (or referenced plus a fingerprint), as the base image of the recipe could contain a bug, and you would like to re-create it.