Build GraphHopper without unit tests and without API key

Fixes bug introduced by commit efc336e. Based on comment by karussell
https://github.com/graphhopper/graphhopper/issues/1373#issuecomment-389425697
Running ./graphhopper.sh --action build would fail with
[ERROR] Failed to execute goal on project graphhopper-web: Could not resolve dependencies for project com.graphhopper:graphhopper-web:jar:0.11-SNAPSHOT: Could not find artifact com.graphhopper:directions-api-client-hc:jar:0.11-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :graphhopper-web

Thanks! I will have to revert the commit as it also introduced other problems with IntelliJ. Sorry for the hassle!

You are free to close this pull request if you find another solution to fix it. :-)


storage/swift: possible to have partially uploaded corrupt file

In this case Funnel says the file ways successfully uploaded, but there are about ~5MB missing from the file.
Possibly an http chunk is being dropped.

The issue here was that two tasks were uploading the same file simultaneously. Not sure what swift can do to check this case and avoid it; problem is, the two tasks will both retry uploading continuously.
We should at least check whether swift is returning returning write conflict errors (e.g. http 409) that possibly we're ignoring client-side.


Factor pwm, psol and buzzer together

Build a generic pwm driven actuator for psol and blower
Buzzer is not really an actuator and stays a member of hal for now
Description
We basically had 3 modules that implemented the same functionalities of outputting a pwm signal to a GPIO pin. I factored those in together, and made it so we can instantiate and initialize those separately from hal.
This also addresses several todos and makes the instantiation of PWM driven actuators agnostic to hal.
A this point, we can probably create unit tests for actuators class, with a little mocking effort on the PWM and/or pinch valve side.
Please note:

One caveat of initializing pwm pins outside of hal is that if we never instantiate them (for example in an integration test), the pins will have a high output, making the actuators behave at their max setting.
I could not fully test psol output, as I don't have the hardware for it.

General checklist:

[x] I have performed a self-review, including - looked through the Files changed tab, browsed repository in my branch
[ ] I have made corresponding changes to the documentation - to reflect changes in code, electrical or mechanical design
[ ] All new documentation or graphics follow the documentation style guide
[ ] All new content is linked, easily discoverable, does not require too many clicks
[x] I have reviewed any other relevant parts of our contributor wiki to ensure that this PR conforms to the standards
[x] I have given the PR a descriptive name (prefixed with WIP if it is not yet ready for review)
[x] I have tagged relevant reviewers

Code checklist:

[x] All new code follows our code style
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have described tests I used to verify my changes, instructions for reproducing them and any relevant configuration details.
[x] I ran the unit test suite and verified that all tests pass - new and old, locally and on CI
[x] I performed a clean build and verified that there were no warnings
[x] I ran our static analysis tools and verified there were no warnings
[x] Any dependent changes have been merged and published in downstream modules
[x] All source files have license headers

Remaining comment addressed separately, in #1191


Parallel build option (yotta build -j )

The build process tends to be quite slow on Windows, so '-j' would help. I've looked at adding this, thinking that it's just a matter of passing the '-j' option to make, but it apparently involves some cmake magic instead.

Closing as this is possible with -- <generator-options> and by selecting a different generator


Need to recreate the cluster during every test run

Some changes force us to recreate the cluster we're using in the workflow test.
For example the recent change from kube-system to kctf-system. Not recreating the cluster will mean we're having stale resources that can make it misbehave (e.g. a 2nd copy of the operator kube-system).
When running a test on one cl on branch A and then another on branch B, the two branches might have conflicting cluster changes and the 2nd test might either be a cluster upgrade or a cluster downgrade.
It sounds we would have to delete and recreate the cluster with an option to skip the step if the cluster has a version from which we know how to upgrade.
Similarly, there might be other objects in GCE left over from a different run (service account, load balancer) that could lead to issues. But I don't know if there's a good way to completely clean the project. But this might be less likely to make issues (?)
@sirdarckcat thoughts? so far it was okayish to handle this manually. But it can lead to issues in the future especially if two people develop at the same time.

you mean if you two people develop on the same cluster at the same time? (like two sysadmins?) or you and me.
if it's you and me, I think this wouldn't be a problem if we run on our own fork?

If two kCTF devs work on different branches, the github workflow will use the same cluster to test both changes. For example, if you would push a change to alpha now, the tests will probably fail since the running cluster is created using the beta scripts.

Even if we recreate the cluster every time, that could lead to race conditions if the actions run in parallel.
I guess we would have to create a temporary cluster every time?

Right, could we do this on our own forks instead of branches?

You mean do a new fork for every change and set up a cluster for the workflow?

Yea, you would have a cluster and I would have one on our own forks. And we just keep our forks up to date to master.

That doesn't help if you want to make a change to alpha (e.g. an important
backport) while you're working on a beta commit.
On Fri, Dec 11, 2020 at 11:24 AM sirdarckcat<EMAIL_ADDRESS>wrote:

Yea, you would have a cluster and I would have one on our own forks. And
we just keep our forks up to date to master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/kctf/issues/163#issuecomment-743110782, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEM2JHRAC6V36BQ4EOFMFLDSUHXPBANCNFSM4UTTXJWA
.

Ah, we can make another project for alpha then. I don't think we need to maintain it for too long though, right?

Alpha is just an example. This happens for any cluster change that is
breaking either forward or backwards
On Fri, Dec 11, 2020 at 11:43 AM sirdarckcat<EMAIL_ADDRESS>wrote:

Ah, we can make another project for alpha then. I don't think we need to
maintain it for too long though, right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/kctf/issues/163#issuecomment-743119729, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEM2JHW6SCKMPTAGYB25MITSUHZVBANCNFSM4UTTXJWA
.

I mean, to solve this problem:

When running a test on one cl on branch A and then another on branch B, the two branches might have conflicting cluster changes and the 2nd test might either be a cluster upgrade or a cluster downgrade.

We could stop using branches for development and use forks instead. This would leave us with just two branches, alpha and beta, and for alpha, the proposal would be to create another project for it.
For solving the general problem of updates that make backwards-incompatible changes to the cluster, then we need to delete and recreate the cluster indeed. It would be nice if we had an upgrade path, but I think that's a lot of work and unlikely to be useful to maintain (because the normal usecase is people have a cluster for a CTF, and can create a brand new one with the next release of kCTF for the next CTF)

On Fri, Dec 11, 2020, 12:06 sirdarckcat<EMAIL_ADDRESS>wrote:

I mean, to solve this problem:
When running a test on one cl on branch A and then another on branch B,
the two branches might have conflicting cluster changes and the 2nd test
might either be a cluster upgrade or a cluster downgrade.
We could stop using branches for development and use forks instead. This
would leave us with just two branches, alpha and beta, and for alpha, the
proposal would be to create another project for it.

But you have the same problem just that you changed t the word branch to
the word fork/cluster. Unless if you spawn a new cluster for every workflow
run.

For solving the general problem of updates that make
backwards-incompatible changes to the cluster, then we need to delete and
recreate the cluster indeed. It would be nice if we had an upgrade path,
but I think that's a lot of work and unlikely to be useful to maintain
(because the normal usecase is people have a cluster for a CTF, and can
create a brand new one with the next release of kCTF for the next CTF)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/kctf/issues/163#issuecomment-743130437, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEM2JHUIAOWJIL2NBFAVMXDSUH4LVANCNFSM4UTTXJWA
.

Yes, if we don't support updates, we have to create a new cluster on every push :-). I imagine we need to have forks to support that dev workflow.

It's not just updates. You need to handle downgrades. See my initial issue description:

When running a test on one cl on branch A and then another on branch B, the two branches might have conflicting cluster changes and the 2nd test might either be a cluster upgrade or a cluster downgrade.
It sounds we would have to delete and recreate the cluster with an option to skip the step if the cluster has a version from which we know how to upgrade.

When running a test on fork A and then another on branch B, the two forks might have conflicting cluster changes but it doesn't matter because they run on different forks, and so, on different clusters. The 2nd test might either be a cluster upgrade or a cluster downgrade, which doesn't matter too much because they are running on different clusters.
When we commit these to github.com/google/kctf then we have to create a new cluster :)
It sounds we would have to delete and recreate the cluster every time.

Btw, how do you create a cluster for your fork? Isn't that lots of manual work? And keeping one cluster per fork running also seems a bit wasteful :)

I like your idea of just running tests in KIND on a push. And only run the full expensive test when merging to the main branch.
I think that's a good compromise between testing and speed.

you would have to generate a project, key and such "secrets", and then it uses that instead of yours. GKE_PROJECT, GKE_EMAIL, GKE_KEY, GCR_EMAIL, GCR_KEY, and GCR_PROJECT. you probably don't need the GCR ones, though (I think those are for pushing the canonical images)
it is wasteful, indeed.. and probably expensive for volunteers :/


Feature/improve perf

Minor performance improvement

Codecov Report

Merging #290 (026a192) into master (af40006) will increase coverage by 0.02%.
The diff coverage is 86.66%.

@@             Coverage Diff              @@
##             master     #290      +/-   ##
============================================
+ Coverage     62.26%   62.28%   +0.02%
  Complexity     1289     1289
============================================
  Files           185      185
  Lines          6150     6154       +4
  Branches        826      826
============================================
+ Hits           3829     3833       +4
  Misses         2054     2054
  Partials        267      267

Flag
Coverage Δ

unittests
62.28% <86.66%> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...render/elements/shapes/EllipticIconOnLayerShape.kt
0.00% <0.00%> (ø)

...r/bpmn/intellij/plugin/core/render/IconProvider.kt
97.40% <66.66%> (+0.14%)
:arrow_up:

.../valb3r/bpmn/intellij/plugin/core/render/Canvas.kt
61.03% <100.00%> (ø)

.../bpmn/intellij/plugin/core/render/CanvasPainter.kt
62.00% <100.00%> (-0.10%)
:arrow_down:

...j/plugin/core/render/DefaultBpmnProcessRenderer.kt
68.35% <100.00%> (+0.13%)
:arrow_up:

...ender/elements/shapes/AnyShapeNestableIconShape.kt
82.97% <100.00%> (ø)

...ij/plugin/core/render/elements/shapes/IconShape.kt
40.00% <100.00%> (ø)

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 af40006...026a192. Read the comment docs.


Move tests to test suite crate

Closes #68.
Also, removed travis-cargo now that docs are handled by docs.rs and
don't need to be uploaded from travis.
Minor update to the compiletest script to avoid issues with stale
artifacts left around after rustup update.
r? @dtolnay

This is green now - @dtolnay could you have a look?


new version broke

getting this error on some youtube videos, the video works as it usually does once I disable the script

Go back to 5.3 https://github.com/TheRealJoelmatic/RemoveAdblockThing/issues/460


parsing hh:ii dd/mm/yyyy on version 2.4.2

hi.
using version 2.4.2 this html did not parse and generates and error:
Uncaught TypeError: Cannot read property 'getTime' of undefined

and generates an error caused by:
getDate: function () {
var d = this.getUTCDate();
if (d === null) {
return null;
}
return new Date(d.getTime() + (d.getTimezoneOffset() * 60000));
},
where
getUTCDate: function () {
return this.date;
},
returns false not a date or null.
reverting to version 2.4.0 fixes the error for me.

Same issue on version 2.4.2 trying to parse HH:ii P. Time only.
if (new RegExp(this.hour_minute).test(date) || new RegExp(this.hour_minute + ":[0-5][0-9]").test(date)) {
date = this.getDate()
}
This at line 669 fails with error: Uncaught TypeError: Cannot read property 'getTime' of undefined
also.
Seems once it get to here the getUTCDate() function
getUTCDate: function () {
return this.date;
}
tries to return this.date which is undefined.

@davidpatters0n maybe you can have a look at this?


Fifeutil updated to v3_6_0 in all .ini

Hi @sophiemiddleton,
You have proposed changes to files in these packages:

CampaignConfig

which require these tests: build.
@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for 551b334f9c689524caabad3c62be4d5b60581753: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at 551b334f9c689524caabad3c62be4d5b60581753.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 551b334f9c689524caabad3c62be4d5b60581753 at 4da9811c467ad2bd57e07b2c1265d362794e292c

build (prof)
:white_check_mark:
Log file. Build time: 14 min 18 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 551b334f9c689524caabad3c62be4d5b60581753 after being merged into the base branch at 4da9811c467ad2bd57e07b2c1265d362794e292c.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

Yes, the moving out of my area is the next task once NERSC is working. I dont want to introduce new places for errors until then. It's not urgent, unless anyone else is using these scripts.

As for the multiple places. This could be removed, this is just how it was set up. In reality we dont need new login defs for each process

Yes, the moving out of my area is the next task once NERSC is working. I dont want to introduce new places for errors until then. It's not urgent, unless anyone else is using these scripts.

That time frame works for me.

As for the multiple places. This could be removed, this is just how it was set up. In reality we dont need new login defs for each process

I don't know POMS well enough to give concrete advice.  As you move forward look for ways to minimize multiple points of maintenance.


#147 Added dock collapse on meetup detail page

Fixes #147.

@n-d-r-d-g i think you linked the wrong issue in your PR description

@n-d-r-d-g i think you linked the wrong issue in your PR description

Apologies! I updated my comment above and closed #148 manually.
@MrSunshyne could you please reopen #147?


Use section that can be folded by the user

The package 'material ui' might help

@marcosantiagomuro started to test something with a package called split (might be better than simple collapsible section)


Update Netflix-Security-Automation.md

The content for this file is virtually identical to https://github.com/OWASP/owasp-summit-2017/blob/master/Working-Sessions/DevSecOps/Netflix-Resilience-Engineering.md. Can they be merged?

@Ambg05 yes please merge them (making sure the participants are also merged)


No Konami Code

This is very important. Comment what you think the Konami Code should trigger.

At this time, this is not a priority. You can encourage folks to brainstorm on the users forum or Twitter.


Alpha values within Color not working as expected

Had a look through the SDK sample application and can only find references to RGB and not RGBA, leading me to believe it only supports RGB.
Using alpha like so:
new Color(255,255,255,0.5f);

Results in the keys being set to black.
Within my own application, I am using the following to resolve this:
    Color RGBAFix(Color color)
    {
        var a = color.A;
        return new Color(
            (1 - a) * 0 - a * color.R,
            (1 - a) * 0 - a * color.G,
            (1 - a) * 0 - a * color.B
        );
    }

There is currently no Color constructor supporting (byte, byte, byte, float), so not sure what that's from.
The SDK docs say that alpha is supported "where applicable" (see screenshot below).

As for how they treat the alpha (0 transparent, or 0 opaque?) is unknown currently, we should contact them and ask.

This also references #25 where we had discussed similar things before.  I'll review my emails shortly to ensure I didn't get a response earlier in the year, and if not, I will ping an email off to Mark.

#25 was made before the note about alpha support appeared in the docs. Back then the discussion was about having Colore support alpha on its own, converting to RGB when passing to Chroma.

Ok, so I swapped it over to use floats, and it looks like only the Mousepad supports RGBA, and the alpha has been incorrectly implemented (0= opaque, 1 = transparent).
The above ensures support across all devices by converting them to RGB.

Interesting! So they did intend to support Alpha, but they just haven't done so consistently.  I'll enquire, Nico, would you like to make the bug fix for alpha implementation in Colore, or would you like me to?

More than happy to contribute. Will most likely do it tomorrow.

Cheers, that would be awesome, can review tomorrow.

As one might expect, other C# implementations of Alpha point towards 1 being opaque rather than transparent.  Colore currently treats 1 as opaque, as above, which in my opinion is correct.  Thoughts @njbmartin ?

@brandonscott when I said incorrectly implemented (0= opaque, 1 = transparent), I meant that is how Razer have implemented. The correct way is (1= opaque, 0 = transparent).

Yes, I thought you did also but @Sharparam confused me thinking it was a Colore bug!  No worries, I thought that was the case anyway and am just finishing up an email.

Engineer's response:

Transparency currently not supported at the moment.

Delaying this until v4.0 as bandwidth is limited until end of November.

I'll raise this problem again now CES is over with.

Closing this as Color will be needing a redesign that takes alpha completely out anyway.

^^ References 1.6.1 changes.


"Pros" played with himself

Yea I noticed that too, should be easy enough to filter this one out.


Add default.conf for nginx-alpha ingress controller

default.conf was previously missing and build (e.g. make container) fails without it.

Ah, nice catch @krancour


Add support for onePosition field type

Low priority, not needed for now

This datatype is actually used as a bitfield, where meaning of each bytes can be found in alarm.properties files in app


adding iuc microsatbed

Add microsatbed tool to annotation
Installation sequence for tool-installers

[ ] Test using @galaxybot test this
[ ] Inspect CI output for expected changes
[ ] Deploy using @galaxybot deploy this if test install was successful
[ ] Merge this PR

Now part of #786


Polyglot Error when selecting tokens

I don't know if this is an escape character thing but I get this whenever I click on one of my characters with Polyglot active and the polyglot language dropdown does not appear.
Error: The values of the provided object must be unique in order to invert it.
at invertObject (foundry.js:1129)
at Function.get defaultLanguage [as defaultLanguage] (polyglot.js:49)
at PolyGlot.updateUserLanguages (polyglot.js:175)
at PolyGlot.controlToken (polyglot.js:82)
at Function._call (foundry.js:2496)
at Function.callAll (foundry.js:2456)
at Token.release (foundry.js:11661)
at Token.release (overrides.ts:9)
at TokenLayer.releaseAll (foundry.js:12285)
at TokenLayer.releaseAll (foundry.js:40319)
Languages that appear in the character sheet as available:

Custom Languages that are currently active in the settings (I have not removed the defaults):
Ovidic,B.A.S.I.C,Fae,Stoutkin,Elfkin,Fiendkin,Greenkin,Moan,Old Heartlandic,Arborkin,Ancient Clont,Thieves' Cant,Draconic,Druidic,Abyssal,Celestial,Wildtongue
Default:
Ovidic.
I had a lot of dashes and parenthesis before which I've dropped, so I don't know if that is affecting things?
This is happening on 0.7.9 / Polyglot 1.4.0.
Any suggestions?

I've made some changes to the module that might have unintentionally fixed this, because I can't replicate it.
Check if that character is still bugged on the latest version.

Hey!  Yes, I updated and its fixed.  Thanks for looking into it.  Love the Alexstraza icon, btw.

Good to know. Thanks, haha.


Node TOO large - The Largest node in the world

Hello!
We have a massive issue with all versions of ord for our node.
We basically have hundreds of thousands of ordinals that we have accumulated since the inception of Ordinals while creating our ecosystem.
These ordinals keep getting airdrops.
We currently have over .4 BTC only in SATS padding these ordinals.
ORD BREAKS completely when trying to run anything.
We are not able to use any inscribe or send functions anymore, it times out.
And running commands like wallet balance or wallet receive will take about 30 minutes.
Many OG devs have looked into this and came to the conclusion that you guys would need to push a custom update to handle extremely large ord nodes.
What should we do? We are currently using custom bitcoin-cli functions to build commands to send ordinals but its getting weird when trying to send runes out of the node
HELP!

Hello!
We have a massive issue with all versions of ord for our node.
We basically have hundreds of thousands of ordinals that we have accumulated since the inception of Ordinals while creating our ecosystem.
These ordinals keep getting airdrops.
We currently have over .4 BTC only in SATS padding these ordinals.
ORD BREAKS completely when trying to run anything.
We are not able to use any inscribe or send functions anymore, it times out.
And running commands like wallet balance or wallet receive will take about 30 minutes.
Many OG devs have looked into this and came to the conclusion that you guys would need to push a custom update to handle extremely large ord nodes.
What should we do? We are currently using custom bitcoin-cli functions to build commands to send ordinals but its getting weird when trying to send runes out of the node
HELP!

Hello @btcmachineordinals
Thanks for posting the issue.
Your query would be best dealt with by the support team.
Please see the link below to our dedicated support line:
Support : Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation

Scammer @cryptoni9n

#3142 was merged earlier this year to deal with this type of an issue.  @btcmachineordinals what version of ord are you currently experiencing this issue with?  Can you paste the timeout message here so we can get more insight to the problem?

All Outputs are above dust limit
note: run with "RUST_BACKTRACE=1" environment variable to display a backtrace
this is the error

Scammer @cryptoni9n

just banned Elsonbastey from the org

#3142 was merged earlier this year to deal with this type of an issue. @btcmachineordinals what version of ord are you currently experiencing this issue with? Can you paste the timeout message here so we can get more insight to the problem?

Yes, version would be great to know.
The problem still is that we build the whole wallet state with each wallet subcommand. A quick fix would be to increase the timeout limit and retry in the background. A proper solution would be to put the wallet state into the wallet.redb database and then only update values that have changed. This is what Sparrow and Bitcoin Core do with their respective wallet databases.

Could you also provide a bit more information on the size of the wallet, specifically how many outputs?

Could you also provide a bit more information on the size of the wallet, specifically how many outputs?

About 96 446

limiting outputs (<1000) per wallet helps

About 96 446

That is a lot of outputs.
This would probably require us to move forward with #3991. ord wallet would then work similar to Sparrow in that it manages a database that loads output information once and then either adds or invalidates outputs when new transactions come in. Tbh, this is not high priority for us at the moment. I can look into it tomorrow and see how much work it would be. If you find someone willing to take the lead on this I'd be happy to help and review PRs though!


Hopefully SwarmUI will be supported

Summary
I would like to be able to know the information about generating images in SwarmUI
Basic Example
Hopefully SwarmUI will be supported
Reference Issues.
No response

Absolutely! Thank you for letting me know about this new tool. Since it's an official tool from Stability AI, I'll definitely support the StableSwarmUI format. Currently, StableSwarmUI is still in its Alpha version. I will work on supporting the current format of StableSwarmUI asap. However, no one can guarantee that future versions of StableSwarmUI will not change the image format.

Wait! I just realised that StableSwarmUI writes both its own parameters and the backend parameters into the images. I tried it out just now, and if I use ComfyUI as the backend, the images are correctly processed just like images generated directly by ComfyUI.

https://github.com/receyuki/stable-diffusion-prompt-reader/releases/tag/v1.3.3-beta.2
I just released beta 2. Try it out.


Implementing GPT1 and GPT2

Hello!
Under the NLP Models, I noticed that GPT1 and GPT2 are unticked. Do you have a specific use in mind for these models? I would like to work with them as part of GSSOC 2021. Thanks!

Yeah please do Text Generation using GPT2 :) @kad99kev

Would you like me to fine-tune it on any particular dataset or only use the pretrained model?

Fine-tuning would be good on any dataset @kad99kev


panic: runtime error: index out of range。 cmd/link/internal/ld.decodetypeKind(...)

What version of Go are you using (go version)?

$ go version
go version go1.12.17 darwin/amd64
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/cc/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/cc/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/t3/21_3m2tj3yn846__rrn2nn1c0000gn/T/go-build740490844=/tmp/go-build -gno-record-gcc-switches -fno-common"
What did you do?
go build
panic: runtime error: index out of range
goroutine 1 [running]:
cmd/link/internal/ld.decodetypeKind(...)
/usr/local/go/src/cmd/link/internal/ld/decodesym.go:69
cmd/link/internal/ld.newtype(0xc00004e000, 0xc00e722660, 0xc01f5b2f40)
/usr/local/go/src/cmd/link/internal/ld/dwarf.go:423 +0x29e1
cmd/link/internal/ld.defgotype(0xc00004e000, 0xc00e722660, 0x3c)
/usr/local/go/src/cmd/link/internal/ld/dwarf.go:418 +0x1c9
cmd/link/internal/ld.dwarfGenerateDebugInfo(0xc00004e000)
/usr/local/go/src/cmd/link/internal/ld/dwarf.go:1810 +0x8ee
cmd/link/internal/ld.Main(0x1431f20, 0x10, 0x20, 0x1, 0x7, 0x10, 0x1278d61, 0x1b, 0x1275a70, 0x14, ...)
/usr/local/go/src/cmd/link/internal/ld/main.go:211 +0xb95
main.main()
/usr/local/go/src/cmd/link/main.go:65 +0x1d0
// Type.commonType.kind
func decodetypeKind(arch *sys.Arch, s sym.Symbol) uint8 {
return s.P[2arch.PtrSize+7] & objabi.KindMask //  0x13 / 0x1f
}

What did you expect to see?
go build success
What did you see instead?
panic: runtime error: index out of range
goroutine 1 [running]:
cmd/link/internal/ld.decodetypeKind(...)

go1.12 is no longer supported.

If I want to solve this problem, do I have to upgrade the go version?

go1.12 is no longer supported.

If I want to solve this problem, do I have to upgrade the go version?

@jxhb We don't know what the problem is.  When we say that Go 1.12 is no longer supported, we mean that we aren't going to investigate problems reported against it.  We don't have the time to look into problems with such an old release.  That is especially true since most likely our advice would be to update to a supported release anyhow.
So, yes, you should update to a newer version, but, no, we can't promise that that will fix the problem.  It probably will, but we don't actually know.  Sorry.


Incorrect Documentation for Rust Setup w VS Code

Well, there's not a lot to get wrong here, but they manage.  I've had Code installed for a long time (currently v1.59.0); I installed the rust installer for Windows (64 bit version) (cargo --version  --> cargo 1.54.0 (5ae8d74b3 2021-06-22); installed CodeLLDB, cargo'd up a new rustean Hello world!, set a break point and hit F5.
I get a dialog that says "Unable to find executable for '\my-first-rust<your program>.exe' with a nice "Open 'launch.json'" button to click.  (Never mind that the docs here say there will be an "OK" button.)  That opens the launch.json file with a "Launch" and a "Debug" sections boiler-plated out, but non-functional since ".exe" is not a valid filename.
I guess I'll sidetrack into CodeLLDB land to see how to config it up, but I was really hoping I could just get a down-the-middle-of-the-rode VS Code+rust environment up and running so I could focus on learning rust instead of focusing on how to drive CodeLLDB. (sigh)
Not that there's anything wrong with learning the lldb toolchain.  It's pretty clear I'll need to before producing anything meaningful.  I just had hoped I didn't need to do that before starting on rust.  (And, worse, I've been around long enough to be pretty certain CodeLLDB will have its own set of distracting sub-dependencies to pull me even deeper into the rat hole of just getting this simple environment up and running.)  (faceplam)

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

ID: 200916ea-06cb-d017-a9e8-18d2216c5bac
Version Independent ID: f872813c-0ab2-0f5a-45e0-e81e8479470b
Content: Set up your dev environment on Windows for Rust
Content Source: hub/dev-environment/rust/setup.md
Product: dev-environment
Technology: windows-rust
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Hi, @mmoo9154, and thanks for filing this issue. I can repro the error message you're seeing if I click "No" when the walkthrough indicates that I should click "Yes". See the section (in this topic) named "Hello, world! tutorial (Rust with VS Code)", and the Note for step 5.
Clicking "No" there will still generate a launch.json, but it won't have the right contents. Once you've generated that incorrect file, you won't be prompted to regenerate it.
I would suggest deleting \first_rust_project.vscode\launch.json and then hitting F5 again in VS Code. You should then get the series of message boxes described in that Note for step 5.
The other thing in the repro steps that you list, that doesn't match the steps in the topic, is step 2 of the "Install Visual Studio Code" section (in this topic).
Thanks!
Steve

I'll go ahead and close the issue since there doesn't seem to be an action necessary to change the content. You can still reply after the issue is closed.
Many thanks!
Steve


fix: upload emergency snapshots to CF rather than DO

Summary of changes
Changes introduced in this pull request:

If no Forest snapshots are upload, upload a FilOps snapshot to CloudFlare rather than DO.

Reference issue to close (if applicable)

Closes
Other information and links

we are not generating sha256sum file?

Right. We don't need the checksum files anymore.


Implement RepartitionQuantiles for set_index

This is a pre-cursor for set_index

This sits on top of https://github.com/dask/dask/pull/10391


travis-ci fails on master branch

currently all travis-ci builds fail
https://travis-ci.org/ansible/tower-cli/jobs/462856823
=================================== FAILURES =================================== _________________________ LoginTests.test_no_arguments _________________________ self = <tests.test_cli_misc.LoginTests testMethod=test_no_arguments>     def test_no_arguments(self):         """         Establish that if tower-cli login` is called with no arguments, it
complains
"""
# Invoke the command.
result = self.runner.invoke(login)
    # Ensure that we got a non-zero exit status
    self.assertNotEqual(result.exit_code, 0)

  self.assertIn('Missing argument "username"', result.output)

E       AssertionError: 'Missing argument "username"' not found in u'Usage: login [OPTIONS] USERNAME\nTry "login --help" for help.\n\nError: Missing argument "USERNAME".\n'
tests/test_cli_misc.py:293: AssertionError
===================== 1 failed, 358 passed in 3.74 seconds =====================
ERROR: InvocationError for command '/home/travis/build/ansible/tower-cli/.tox/py27/bin/coverage run -m pytest -v' (exited with code 1)
___________________________________ summary ____________________________________
ERROR:   py27: commands failed
The command "tox" exited with 1.`
Maybe there is a chance to fix that, since any PR will look not so nice and is hard to verify....
Cheers and thanks,
Matthias

I'm fairly sure it's passing again. There is some nastiness related to config management in the tests, but I don't think it's surfacing at this particular moment.


Support for RSA 3072 and ECDSA_P_384

Hi I see that in gnsi/credentialz/credentialz.proto the keyType supported are KEY_TYPE_ECDSA_P_256, KEY_TYPE_ECDSA_P_521, KEY_TYPE_ED25519,KEY_TYPE_RSA_2048, KEY_TYPE_RSA_4096.
Earlier there was no differentiation on the basis of bit size. This was brought in by @nmahabaleshwar commit for ecdsa.
I believe we are still missing support for RSA 3072 and ECDSA_P_384.

Hi Rohit, Feel free to create a PR to add the additional keys.  We can
review and approve
On Thu, Sep 19, 2024 at 3:57 AM Rohit @.***> wrote:

Hi I see that in gnsi/credentialz/credentialz.proto
https://github.com/openconfig/gnsi/blob/main/credentialz/credentialz.proto
the keyType supported are KEY_TYPE_ECDSA_P_256, KEY_TYPE_ECDSA_P_521,
KEY_TYPE_ED25519,KEY_TYPE_RSA_2048, KEY_TYPE_RSA_4096.
Earlier there was no differentiation on the basis of bit size. This was
brought in by @nmahabaleshwar https://github.com/nmahabaleshwar commit
https://github.com/openconfig/gnsi/commit/eb38162f1f5e5b36159a4f8810d98032f864fad8.

Can you guys help me know why RSA 3072 and ECDSA_P_384 were not included
in the proto
—
Reply to this email directly, view it on GitHub
https://github.com/openconfig/gnsi/issues/205, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMCGM7JIXTCNNLUOZGYLE3ZXKU2DAVCNFSM6AAAAABOPUU4TGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUZTKOJZHE2DMNY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks Darren

#206 was merged.


Warning "-s option given but default rule can be matched"

Building esp-idf hello-world template, after a "make clean", the first "make all" generates the
warning "-s option given but default rule can be matched" .
This warning appears as an error in Eclipse, even though the compilation succeed.
This warning is generated by flex :
flex -L -P zconf -o zconf.lex.c zconf.l
zconf.l:256: warning, -s option given but default rule can be matched.
I think it is because in esp-idf/tools/kconfig/zconf.l file, there is option nodefault on line 2 (which is the same as specifying "-s" flex command line option) :
Line 2 : %option 8bit nodefault perf-report perf-report
but there is also a defaut rule "." specified on line 97 :
.	{
unput(yytext[0]);
BEGIN(COMMAND);
}
The solution seems to be to suppress nodefault option on line 2 if a default rule is defined.
Line 2 : %option 8bit perf-report perf-report
This suppress the warning.

Hi @tdy91,
This warning was bugging me for several months on both Linux and Windows installation.
I also saw it in logs by some other people. Now I checked it on Linux and after applying your fix the warning does not show anymore. Later I will check my Windows installation.
Thank you for taking your time to troubleshoot it and  providing a fix :+1:
I am wondering if there is anybody else who can comment in this issue? I do not have experience with flex and can not comment on possible side effects on suppressing this warning. Depending on feedback I think we should apply it in master.

Hi @krzychb
I am just beginning on esp-idf and don't like to see an icon error in Eclipse, mostly on very simple Hello-World project; it was bugging me too !
I do not have experience with flex too, but with ANTLR with is another parser generator using a similar lexical analyzer.
Trying to find a solution, I found this answer to the same warning on another project :

Source : https://stackoverflow.com/questions/1622493/bison-build-warning-s-option-given-but-default-rule-can-be-matched
Answer : date : Oct 26 '09 at 4:37
Author : UncleO
The "flex" command on your system could have been aliased to be the flex command with an -s option. That could occur in any of several startup scripts.
The warning is telling you that there are some inputs that aren't matched by any of the rules in your input file. The warning is there to get you to make sure you have considered all cases in your regular expressions.
If you truly want the default rule to be used, then add it to the end of the rules in your input file. Try adding the rules
. ECHO;
\n ECHO;
Update: The input file you provide includes the %option nodefault, which is the same as specifying "-s" on the command line, so that mystery is solved. Also, the file does not have a rule for ".". There are some characters not covered, '@' for example.
I'm also suspicious of the "-" symbol in the character class. It is supposed to be a range operator, but it may work as a character in the first position as you have it. I don't know. It might be a good idea to use "-" instead.
You could change the last rule to
. { printf("lex Unknown character = '%s'", yytext); yyerror("lex Unknown character"); }
to get rid of the warning (and to prevent the resulting scanner from crashing).

My own analysis is following one :

Help of flex V2.6.4 used in esp-idf project gives :
flex --help
-s, --nodefault         suppress default rule to ECHO unmatched text
info flex
'-s, --nodefault, '%option nodefault''
causes the default rule (that unmatched scanner input is echoed
to 'stdout)' to be suppressed.  If the scanner encounters input
that does not match any of its rules, it aborts with an error.
This option is useful for finding holes in a scanner's rule set.

The flex default rule matches a single character and prints it on standard output.

The zconf.l file contains tokens and rules to produce sp-idf\tools\kconfig\mconf.exe, used to produce sdkconfig on "make menuconfig" command.
Today, in this file there is :

line 2  : nodefault option defined
line 97 : a default rule is explicitly defined by kconfig developper, so the flex default rule is not used.

So, from my point of view, to use flex, you have :

either write an *.l file which uses flex default rule (i.e. without defining in it an "." explicit default rule) and
use flex -s (or nodefault option) command line for syntax debugging purposes.
either write an *.l which defines an explicit default rule, and in this case, there can be no syntax hole in scanner rule set,  so -s (or nodefault option) command line is not useful, and this is the meaning of the warning..

In fact, this is just a flex warning, not an error, and as we are not debugging kconfig, but developping esp-idf projects, my own opinion is that suppressing "nodefault" option from zconf.l will have no side effects, but another feedback may be preferable before applying this solution in master.

Very nice explanation, thanks @tdy91 !
Sure enough Windows system is also cured with your fix :medal_sports:
For other people reading, this issue looks as below:

I found it very distractive to see an icon error in Eclipse, while actually there are no any errors! You can stop the build from Eclipse and start it again to remove it. The fix identified by @tdy91 does not require any artificial treatment like that.


Error when using upgrade_config_file.py on new dataset yamls in riboviz 2.0

Hi folks,
I've run into an issue when I've tried to run the upgrade config script on the Cryptococcus yaml files from example-datasets repo Cryptococcus branch.
I had cloned example-datasets into home (~/example-datasets), checked out the CryptococcusH99-3 branch & the yamls I wanted to upgrade were at ~/example-datasets/fungi/cryptococcus/.  I've tried the H99 .yaml first.
From the ~/riboviz folder:
I ran:
python -m riboviz.tools.upgrade_config_file -i ~/example-datasets/fungi/cryptococcus/Wallace_2020_H99_4-samples_10p_up12dwn9_CDS_120bpL_120bpR_config.yaml -o ~/example-datasets/fungi/cryptococcus/Wallace_2020_H99_4-samples_10p_up12dwn9_CDS_120bpL_120bpR_config_upgraded.yaml
(base) flic@circe:~/riboviz$ python -m riboviz.tools.upgrade_config_file -i ~/example-datasets/fungi/cryptococcus/Wallace_2020_H99_4-samples_10p_up12dwn9_CDS_120bpL_120bpR_config.yaml -o ~/example-datasets/fungi/cryptococcus/Wallace_2020_H99_4-samples_10p_up12dwn9_CDS_120bpL_120bpR_config_upgraded.yaml
Traceback (most recent call last):
  File "/home/flic/miniconda3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/flic/miniconda3/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/flic/riboviz/riboviz/tools/upgrade_config_file.py", line 60, in <module>
    invoke_upgrade_config_file()
  File "/home/flic/riboviz/riboviz/tools/upgrade_config_file.py", line 56, in invoke_upgrade_config_file
    upgrade_config.upgrade_config_file(input_file, output_file)
  File "/home/flic/riboviz/riboviz/upgrade_config.py", line 186, in upgrade_config_file
    upgrade_config(config)
  File "/home/flic/riboviz/riboviz/upgrade_config.py", line 161, in upgrade_config
    features_dir_file = os.path.split(features_file)
  File "/home/flic/miniconda3/lib/python3.7/posixpath.py", line 107, in split
    p = os.fspath(p)
TypeError: expected str, bytes or os.PathLike object, not NoneType

I'm not sure whether this is an issue with version 2.0 parameters being slightly different to the older upgrades noted in here, upgrade_config.py.
Another thing I wasn't sure about was whether the provenance header (brought in from #166 ) might not be handled correctly in the upgrade script now, since this is a new feature.  I tried running the script again after deleting these rows temporarily, but it gave the same error, so perhaps this section is ignored, but if the upgrade script was working, would these rows be left at the top of the file or reaarranged within the other parameters?
Checking through other issues, I noticed #172 which mentions a config checker, and @mikej888 seems to be working on a checker in example-datasets repo, so this may be duplicating issues @mikej888 has already picked up on in riboviz/example-datasets/#9?  This might make working on riboviz.tools.upgrade_config_file less important?

The code should be updated to handle updates to optional parameters. The updates to the relative paths in the vignette should not be done - these paths can be updated manually. docs/user/upgrade-1x.md recommends that users check any file paths anyway.

@FlicAnderson please try fix in branch optional-null-values-202-203.

Hi @mikej888 , branch works and upgrades the yaml!  Running nextflow --validate only validates it OK :+1:
It does rearrange the provenance section alphabetically into the parameters (though it keeps the block together), but that's that won't affect how it runs and can just be shuffled about manually.
Is there any way to make sure that if there is NO asite_disp_length_file, codon_positions_file and t_rna_file in the original yaml that these are set to null by default maybe, instead of set to the data/[filename] value? That might be more useful if most people aren't using Saccharomyces cerevisiae datasets? But equally we could just make it clear in the documentation that these should be removed or set to null if that's the case? @ewallace what do you think would be more universally useful?

Merged into "develop" branch.

Linking this fixed issue to example datasets issue #92


No support for split sourcesets

rendering is not split form the main package so its impossible (or at the very least really hard) to use geckolib in a project that has split sources

There is no planned support for this feature.


implement gofabric8 tenant update via calling the fabric8-tenant REST API

once this is supported
https://github.com/fabric8-services/fabric8-tenant/issues/222
we should be able to implement the upgrade tenant via invoking this REST API, passing in the current openshift token
the tricky bit is gonna be how to detect where the f8tenant endpoint is; we don't yet put any marker anywhere in the tenant namespace to know where things are yet so until there's a place to discover these (e.g. via an annotation on the main users Project) we'd need to have this defined in an env var or CLI argument
once this is implemented we can remove the fabric8-tenant go dependencies completely!

the tricky bit is gonna be how to detect where the f8tenant endpoint is; we don't yet put any marker anywhere in the tenant namespace to know where things are yet so until there's a place to discover these

What do you think about this implementation ? :
https://github.com/fabric8io/gofabric8/pull/596/commits/2107f474816aea5abe4e91c1e38a7e8ced70dc3b

LGTM :)


Added WordPress Gutenberg Project

Thought this would be a good addition to the list.

@RJ722 I think I've fixed it... This is actually my first pull request. haha Happy to have this resource to do more of them.


Make comparison operators multiversal instead of universal

Fixed by https://github.com/VirtusLab/iskra/pull/13


Lower shuttle time + recall turning point

About the PR
Adds a recall turning point, so after half of the shuttle time has elapsed it is considered 'in transit' and cannot be recalled thru a comms console. Also changes some UI update stuff cause I had to to make it work. Should be performant still and doesnt update when no one is subscribed anyway
Screenshots

Changelog

:cl:

tweak: Basic shuttle call time reduced from 20 minutes to 10 minutes.
tweak: The shuttle can no longer be recalled after half of the time has elapsed.

Great idea and should help counter jerks in situations where a shuttle is necessary.
Although, I feel like 5 minutes of time to recall the shuttle is a bit too little, as so very often people will spam the call. And while it usually gets recalled soon after, the sheer spam and LRP ignorance will often will allow it to go through. The shorter that window is the less chance the spam is noticed each and every(of the many) times.

Shuttle transit time is typically 3 minutes so I suggested after 7 minutes it cannot be recalled. MRP soon(TM)

Although, I feel like 5 minutes of time to recall the shuttle is a bit too little, as so very often people will spam the call.

5mins is consistent with SS13 i believe and seems to work there, we can see how it goes with our playerbase and decide if it needs tweaks later


[Android] React native 0.75.4 text number of lines not updating

Description
I found the issue when using text align justify and found out that the text has an extra one number of lines. After further investigating, while using a custom asset I found out that the number of lines stays the same when it first initialize from when it had Left text align.
Here is when it is has Justify and Left text align respectively:

It is worth noting that both width in the picture is the same. Furthermore, I also checked for the number of lines from onTextLayout, and the results shows that it remains having 6 lines instead of 5 (in my case previously shown).
Steps to reproduce

Initialize project
Install dependencies using 'npm install'
Add custom asset (.tff file)
Import Text component
Put text align justify as style
Use font family
Adjust random number of words until the issue is replicated

React Native Version
0.75.4
Affected Platforms
Runtime - Android
Output of npx react-native info
System:
  OS: macOS 13.0.1
  CPU: (8) arm64 Apple M1
  Memory: 80.97 MB / 8.00 GB
  Shell:
    version: 5.8.1
    path: /bin/zsh
Binaries:
  Node:
    version: 18.18.0
    path: ~/.nvm/versions/node/v18.18.0/bin/node
  Yarn:
    version: 3.6.4
    path: /opt/homebrew/bin/yarn
  npm:
    version: 9.8.1
    path: ~/.nvm/versions/node/v18.18.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.1
      - iOS 16.1
      - macOS 13.0
      - tvOS 16.1
      - watchOS 9.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2021.3 AI-213.7172.25.2113.9123335
  Xcode:
    version: 14.1/14B47b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Stacktrace or Logs
none

Reproducer
https://github.com/LunaticHero-Cyber/text_test
Screenshots and Videos
No response

I want to note that I also find this issue when working on a project with 0.74.3

@LunaticHero-Cyber Can you check this on New Architecture as well?

After checking, with newArch enabled, the issue seems to persist.

@LunaticHero-Cyber Can you check this on New Architecture as well?

After checking, with newArch enabled, the issue seems to persist. @shubhamguptadream11

That's interesting. The text is measured differently in TextLayoutManager.measureText  than what's actually being displayed. There is probably something wrong with how the StaticLayout is built. I am having a closer look on that.


modify dash-wind-streaming procfile

Fixed

Modify procfile

🎉 Please also make sure to add the change you made to the Procfile somewhere in the README instructions!


customizable Helm release name

@vyankyGH isn't this already merged into main? Should we close this PR?


Consolidate user input methods

use the same logic to gather user input for secure/default use modes

@yuval-k this mostly applies the interactive mode from kubesquash to the new secure mode
I intend to do another cleanup pass but I'm shifting focus to vs-code compatibility and unlocking the other languages at the moment


doom-retro: Improves the Notes section

The notes described the _doom dir as being under the DOOM Retro persist dir, which is not correct - so this corrects that.
It also inserts some space in the notes section to make it more readable and aesthetically pleasing.

Looks good to me.


Update release v0.2 branch with newer content from main

Done with a merge because we've done some builds already from release branch so we need to preserve the history.
Ref: EC-504

This PR is to merge a merge commit. Actually the only commit in the PR is the merge commit which is (currently) cafbf77.

We're going to end up with a patch number 45 or more...
$ git rev-list --merges --count v0.2.0..HEAD
45

We could figure out a way to bring that down, but I don't think it's worth the trouble.

Note to self: Don't use "release-" prefix on PR branches.. Because of that prefix the pre-merge build is compiling all the different arches, and the version number is bogus. No harm done but better to remember for next time.


Honor build.Context.BuildTags and build.Context.ReleaseTags (and possibly file suffixes)

Expected behavior

Build Godep with go1.6 (or earlier than go1.9).
Build a project that imports package that has a // +build go1.9 release tag.
Expect Godep to skip parsing the file, ignore parser errors, or at least print a warning.

Actual behavior
Godep fails with a parser.ParseFile error when trying to parse the "type alias" feature added in go1.9. I think this behavior was introduced in #529 which was mistaken about how build tags work. See this article for how they're really used.
Steps to reproduce behavior
Build Godep with 1.6 and import the package golang.org/x/net/context as a dependency. Run godep save ./... and it will fail with the error godep: $GOPATH\golang.org\x\net\context\go19.go:15:14: expected type, found '=' (and 1 more errors)
godep version output
godep v79 (windows/amd64/go1.6.4)
go version output
go version go1.6.4 windows/amd64
Contents of Godeps.json file
N/A

I'll create a test case for this and take a stab at fixing it myself, but wanted to write down what I had in mind so far.
First I think we should address BuildTags since it's an easier problem, I think a solution would look something like this:

Create a custom build.Context that contains user-specified fields to ignore/include files (context can be copied from build.Default). The user in #529 could have then specified mytag via a command-line flag to include files that have that specific build tag, and this could be saved into Godeps.json so it's also included in future runs.
Run (ImportDir)[https://golang.org/src/go/build/build.go#L436] using this Context and it will skip any files that don't match the build tags (as it used to). It should also skip // +build ignore flags.

It's a little more complicated for the ReleaseTags field since Godeps can be built with a version of Go other than what the project is using. I think there are two cases you would need to handle:

If (GoVersion > Godep version) then log a warning since Godep might not be able to parse project dependencies, the user should then update Godep to be able to parse files that are from a newer version, or lower the version specified in Godeps.json
Else if (GoVersion <= Godep version) then include all files that Godep can parse (using Default.ImportDir)

I created a short-term fix for my problem here if anyone needs it. I added a command-line flag to ignore parser errors (errors that won't come up at build due to release tags being used).
I'd like to help on a long-term solution but it seems like it will be very easy to break existing projects that rely on build tags being ignored, so before putting in too much work I'd like to hear other people's thoughts and if they're interested. Also not clear how long Godep will be needed if official language support for vendoring is added soon.
Also worth mentioning that issue #443 is also requesting that build tag exclusions work.

I encountered the same problem and you use your modified version, but this does not output an error message is not a good program and look forward to officially modify.

I am closing this issue because the repo is going to be archived.


Multisig transactions

Hi!
If i wanted to use multisig would I need to tweak the models myself or is it something that is already implemented?
Thanks

Hi!
No, multisig is not supported


Upgrade to RA v4 // MUI v5, improved styling, proper SemVer display, ...

feat: react-admin-v4
feat: mui v5
fix: new tree menu
feat: UI / style enhancements
feat: SemVerChip and SemVerTextField for #3
fix: TrimField for all long fields in table views
fix: true/1 vs false/0 handling on connection states for #2

Wow - thank you for the PR! I will review all of this ASAP, these all sounds like great fixes / enhancements.

@shaunco this is OUTSTANDING work - thank you for contributing it.  When I created this repo, I put it out to the community for this exact reason - with the hope that others would be just as passionate about this as I am, and help contribute to make it better.  This was exactly what I was hoping for.
Overall, I love all of these changes.  There were a few snags that I hit in testing, wondering if you could help with them:

The hot module replacement / auto reloading wasn't working in my local dev environment, is there something I need to do to enable this?  I'm running with NODE_ENV=development
The device connect (remote ssh) functionality doesn't seem to work from the main dashboard (but works fine in other places).  I get the error Cannot read properties of undefined (reading 'uuid') from the DeviceConnect endpoint, looks like it's not getting the device context properly?
The delete button on the releases page is disabled for releases where it should be enabled (i.e. releases with no devices running them)
In components/release.js, looks like line 44 needs to be changed from export const ReleaseList = () => { to export const ReleaseList = (props) => {

Otherwise I think this is good to go, clearly you guys have put a lot of time into testing this, it works great.

@julianocomg did all the heavy lifting here! We have more underway that we'll contribute back soon.
For your questions:

If you have a .env file in the root (next to .gitignore with NODE_ENV=development, you should be good to go through either running npm start devserver or by hitting F5 in VSCode. I'm not sure why else it might not work, but perhaps @julianocomg has some ideas
We were overly light on testing for remote SSH, as open-balena-remote doesn't work in our setup (we can't use ports 10000+ and need everything to go over 80/443. We're working to redo the remote stuff as websockets, but it will be a few weeks). The issue here is likely that ra-4 moves to react-router-v6, which drops all props support in favor of useParams(), useQuery(), and other hooks (see the Upgrade Guide). Chances are we missed one here, and thus uuid is undefined because we are missing a const { uuid } = useParams().
Will take a look
Will take a look

@shaunco all sounds great - thanks for the color.  Those changes to open-balena-remote will be a major improvement over the rotating port system used now, looking forward to that.  If you are running open-balena in a production environment, I'd encourage you to check out the helm charts that we created, they include a lot of other production-ready components that have been developed such as loki logging / grafana reporting, build servers, delta servers, and more.

@suaunco in the meanwhile I'll merge this in so I can help with a few other things, and update docs etc.

@shaunco @julianocomg quick update for you guys here, I've managed to work through most of the issues with the new code, and the fixes are included in this branch.  As of now, all remote device connectivity is working (including ssh, vnc and http) and the issues noted above (with the exception of the release deletion button) are fixed, among other small tweaks.  I should be able to get to the release deletion button soon as well.  We're also now using the new interface in our environment, so I'll continue to work in additional tweaks / fixes as they inevitably come in.


Interactive Window update

You need to add new assembly to setup authoring, see Assemblies.wxi in Setup project.

What is Microsoft.R.InteractiveWindow.dll? Where is the source code for it?

It is the most recent version of the interactive window, which is identical to the one used by python tools and roslyn. It was built out of the clone of roslyn here, https://github.com/zooba/VsInteractiveWindow

Ok, I'd like to get more details. Are we going to have 3 different assemblies of Interactive Window that will contain identical code that just sits in different namespaces?

Yes, that is correct.

One more thing: there is Setup.15.0 project and new assemblies need to be added to files.swr.

:+1:

Closing this pull request. Bad merge :(


[Snyk] Security upgrade electron from 22.0.0 to 31.4.0

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

package.json

⚠ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Use After Free SNYK-JS-ELECTRON-7577919
  214

Use After Free SNYK-JS-ELECTRON-7577921
  214

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free

@dependabot recreate


Updated sdk version

Prerequisites

[x] I have written a descriptive pull-request title
[x] I have verified that there are no overlapping pull-requests open
[x] I have verified that I am following the Nancy code style guidelines
[x] I have provided test coverage for my change (where applicable)

Description

The build scripts needs to be updated as well :smile: https://github.com/NancyFx/Nancy/blob/master/build.sh#L31-L32

So would the global.json in the other repos (bootstrappers etc)

@jchannon I saw that #2594  was merged. If this PR is dead I will close it

Apologies #2594 updated to latest sdk but also changed the build script quite a bit ❤

Apologies. 2594 changes the whole build script as well as add latest Sdk
On Sunday, 23 October 2016, Cemre Mengu<EMAIL_ADDRESS>wrote:

@jchannon https://github.com/jchannon I saw that #2594
https://github.com/NancyFx/Nancy/pull/2594 was merged. If this PR is
dead I will close it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NancyFx/Nancy/pull/2581#issuecomment-255578848, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGaptt33RAaSJRk9lkc6IwL5-wgJcARks5q2yzegaJpZM4KP8LV
.


Focused panel size is too narrow when using vertical-tabs

Editor-area is no longer visible when using https://atom.io/packages/vertical-tabs package.
I guess the problem can be fixed manually by setting a wider size, once you implement configurations, but I reckon it could be larger to begin with when certain conditions are met (such as having aforementioned package enabled).

Thank you for reporting! I'll publish a new release with configurations in the next minutes.

Fixed with v0.2.0 (2e143f6744abf6b4b97905bccbffe17a558c47c5). 🎉
I tested the new version with vertical-tabs, seems to work. Please reopen if this still causes some issues.


ImportError: cannot import name 'extract_text' from 'pdfminer.high_level' (D:\DEV\Python\PdftoXML\lib\site-packages\pdfminer\high_level.py)

Bug report
When i am trying to parse a pdf with image and table, i am getting this error.
ImportError: cannot import name 'extract_text' from 'pdfminer.high_level' (D:\DEV\Python\PdftoXML\lib\site-packages\pdfminer\high_level.py)
Looking forward for a quick help on this

Please ensure that you have the correct library installed (pdfminer.six) and try re-installing it.
Also, try importing it like this
import pdfminer
import pdfminer.high_level


Docs: logging level can be set to trace also

Pep8 doesn't like it 😋
.. |log_levels| replace::
    'trace', 'debug', 'info', 'warning', 'error' or 'critical'

or similar. You can test quickly on http://rst.ninjs.org

@KeyWeeUsr I hope this time pep8 will like it :)


hide zero balance

Pull request template
Checklist

[ ] I have read the CONTRIBUTING guide
[ ] branch rebased on develop
[ ] styleguide check npm run validate
[ ] good naming
[ ] keep simple
[ ] video or screenshot attached
[ ] testing instruction attached
[ ] check your PR once again

Description

Video or screenshot

What and how to test

https://drive.google.com/file/d/1TsPGhsrg_NVKB-ziijWPQSNGBIlPI6at/view


bad message when no main scene has been set

It seems it's been already fixed at master branch, but the binary from  has the bug.
I built the latest commit at master branch (last commit is 6a363ad4704cbfa916b0e10491855221a4680b8e).
The platform is x11.

Fixed by #12244


Added previous helper

User may enter the edit page for incident from statuspage

The cancel button shoud be back to where it come from.

Why are all those parameters needed? We never intend to actually use it like that.

Surely this would do:
    /**
     * Create a new back url.
     *
     * @param string $route
     *
     * @return string
     */
    function previous($route)
    {
        $url = app('url');

        $previous = $url->previous()

        if ($url->full() === $previous) {
            return $url->route($route);
        }

        return $previous;
    }

@GrahamCampbell
:+1:

No. What I wrote was fine. Don't write code that we don't use.

@GrahamCampbell
I think ** $route !== null ** is needed.
If use call previous(), obviously the route is null. then the statement of  ** $previous === $url->full() ** will not be executed, and the this statement takes more time.
Right?

I think $route !== null is needed.

No, it's not. Look at my code. I said that we don't allow passing null.

OK, thank you. I will change them.

The cancel button shoud be back to where it come from.

Honestly, I'm not convinced it actually should.

I think I'm actually :-1: here.

@jbrooksuk
What about you opnion?
Is it needed? if you give a :-1:  too. I will close this PR.

I'd much rather pressing back goes back to the dashboard.


Support pluggable auth plugin mechanism

@sidorares , I raise this issue to talk about the pluggable auth plugin mechanism design.
Your mysql2 have a design
const conn = mysql.createClient({
  authPlugins: {
    some_custom_plugin: (data, cb) => { /* ... * /},
    // mysql_native_plugin and sha256_password_plugin automaticlly merged to here unless you do something like
    // mysql_native_plugin: null
    // 'mysql_clear_password' not enabled by default:
    mysql_clear_password: mysql.authPlugins.mysql_clear_password
  },
  connectAuthPluginName: 'mysql_native_password' // this would be default, but if you need to start with sha256_password_plugin for example you need to put this option
})

Which describe in documented here: https://github.com/sidorares/node-mysql2/blob/master/documentation/Authentication-Switch.md
I also want to add the pluggable auth plugin mechanism, and want to let the API is same. What's your decision on mysql2? If you like, could we talk about the auth plugin mechanism design here?

Your mysql2 have a design

this is proposed design which I want to add. What is currently available documanted at https://github.com/sidorares/node-mysql2/blob/master/documentation/Authentication-Switch.md
Do you see any blockers implementing this @elemount ? I'll try to add same on my side on node-mysql2

@sidorares, I think this design is good. If you make sure that is your final design, I'll try to add same on the pr in mysqljs.
@dougwilson, do you have any additional concerns?

I think just copying the public API of mysql2 is good enough. There are other ways it could be done, but no real reason to implement it differently, I suppose.
The only other way I could think of is to add methods on the main export to register plugins, which should be OK to register globally, but the down side is that it removes the flexibility to disable at a per-instance unless a different thing is done, haha.

still not sure about connectAuthPluginName key. Maybe 'defaultPlugin' is better name

Or even just authPluginName , since that's what the docs call it? 🤷♂

for docs it's "name of auth plugin current packet talking about"
for api discussed it's "name of auth plugin to be used during initial handshake"


fix: added missing field "passwordOptions" to CasdoorOrganization model

Hi! In this PR I added missing field "passwordOptions" to CasdoorOrganization model for more convenient password complexity configuration

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@souress can you add all missing fields for organization or even for all objects (like users, applications)?

@hsluoyz added all missing fields for existing models


ISSUE: input_boolean showing up

Describe the bug
After following the installation via HACS and getting it working I noticed this in the "packages/keymaster/frontdoor/frontdoor_lovelace"
- input_boolean.frontdoor_garageacess_notifications
Environment (please complete the following information):

OS: HassOS
Type of system that HA is running on: RPi3
Home Assistant version: 2021.12.10
Hassio/Docker/Core?
Component version: v0.0.77
Z-Wave integration name: zwave_js
Lock make and model: Kwikset 910

Logs
NA
Screenshots
NA
Additional context
I do have garage door controllers setup with HA but nothing resembles garageacess.

I too am curious what the purpose of this input_boolean is.

+1
experiencing the same issue.
Describe the bug
In the 'badge section' of the auto-generated 'kwikset_basement_lovelace' files, there is what appears to be a strange entry on line 10

input_boolean.LOCKNAME_garageacess_notifications
Regardless of the name or function of the lock (I have several Kwikset units) - that line (referencing garageaccess_notifications) is always there.

This seems like a potential bug - or (if not...) what is it intended to show for each lock?
There are matching entities for each lock - but I can't figure out what it is supposed to indicate.
Thx!

You're referring to this line:
https://github.com/FutureTense/keymaster/blob/9e931b35cf8d875d713e02cb9b6897dc9855ce04/custom_components/keymaster/lovelace.head#L9
That'd be leftover code from an older iteration. You can remove the line.


Update libraries.md

Dead link for h3ronpy

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the fix!

Coverage remained the same at 98.513% when pulling 5de0971690212ee2bcefd952c35fd8393ecafb0c on sam-watts:patch-2 into 69bbe0fe87d2749c82de09b0edb4c8dc7a66b184 on uber:master.


Include encrypted data key in Kafka buffer message.

Coming from #3620, include metadata about encryption in the Kafka buffer message
message BufferedData {
   /* The format of the message as it was written.
    */
   MessageFormat message_format = 1;

  /* The actual data. This is encrypted if key_id is present. Otherwise, it
   * is unencrypted data.
   */
  bytes data = 2;

  /* Indicates if data is encrypted or not.
   */
  optional boolean encrypted = 3;

   /* The data key which encrypted the data field. This will be encrypted.
    * The consuming Data Prepper node must have the ability to decrypt this key.
    */
  optional bytes encrypted_data_key = 4;
}

This was resolved by #3976


what's the meaning of void VelodyneDriver::set_base_time_from_nmea_time in velodyne driver.cpp

I feel confused about the following code, Why does Apollo set the benchmark time like this?
Does this have a relation with the device's output?
VelodyneDriver::VelodyneDriver() : basetime_(0), last_gps_time_(0) {}

void VelodyneDriver::set_base_time_from_nmea_time(NMEATimePtr nmea_time,
                                                  uint64_t& basetime) {
  tm time;
  time.tm_year = nmea_time->year + (2000 - 1900);
  time.tm_mon = nmea_time->mon - 1;
  time.tm_mday = nmea_time->day;
  time.tm_hour = nmea_time->hour;
  time.tm_min = 0;
  time.tm_sec = 0;

  // set last gps time using gps socket packet
  last_gps_time_ = (nmea_time->min * 60 + nmea_time->sec) * 1e6;

  ROS_INFO("Set base unix time : %d-%d-%d %d:%d:%d", time.tm_year, time.tm_mon,
           time.tm_mday, time.tm_hour, time.tm_min, time.tm_sec);
  uint64_t unix_base = static_cast<uint64_t>(timegm(&time));
  basetime = unix_base * 1e6;
}

As I know it come here from ROS velodyne driver.

NMEA time is from the GPS receiver originally. It is passed to the Velodyne Lidar for time synchronization. Velodyne with re-broadcast the time information in its data and position packages.

@YangHan101 ，It is obvious, I know it. How to understand this
  time.tm_year = nmea_time->year + (2000 - 1900);
  time.tm_mon = nmea_time->mon - 1;

That is just conversion between the date format of the two kind of format. Please look into the details of the formats.


Favorited lists

Thanks for the great library!
It'd be nice to have a way to get favorited lists.

Hey,
sounds like a great idea!
I don't have much free time right now, I will try to have a more detailed look at this in the next weeks.

Favorites are stored in saved_views_json in settings, which you could get from https://workflowy.com/get_settings The format is pretty straightforward.


Unable to put SSL certificates

Hi! Could you please share the info on how to pass the SSL cert in order to produce messages on a secured kafka topic via Jmeter

@AnuradhaC were you able to set this one up?

https://github.com/EugeneYushin/new-api-kafkameter/issues/2


Spice

Run

    cluster/kubectl.sh spice testvm --details

to see the connection details.

Run

    cluster/kubectl.sh spice testvm

to start a remote session with "remote-viewer".

This change is

/cc @fabiand @stu-gott @admiyo

@fabiand could you have a look on the comments?

ping

+1
Code looks good and tests pass locally. I can verify the spice connection works. I'd still like buy-in from at least one other as this is such a large change.

 spice support

@fabiand with this patch we are using network namespaces. If we don't do that we can delete the port opening loop (since it does not make any sense then)
Further if you are not in the kubernetes cluster, you will not be able to connect to SPICE, we would also have to forward the proxy settings. I guess you are saying that because you want to use pure kubectl? Otherwise the spice endpoint is easy enough. Further when you think about implementing tls and password protection for spice, we will have to prepare even more than just the proxy. We will have to embed a password and tls keys, ... into the spice config.

Ran 10 of 10 Specs in 35.995 seconds
SUCCESS! -- 10 Passed | 0 Failed | 0 Pending | 0 Skipped PASS
ok  	kubevirt.io/kubevirt/tests	36.056s

Awesome.

@fabiand externalIPs is not an env var. It is part of the server spec, I guess that is the misunderstanding


Update the instructor guide

removed some outdated info
we don't need to deactivate/reactivate Travis anymore

Set to draft until I adjust also the template repo to use GH actions.

This is coupled with https://github.com/coderefinery/template-forking-workflow-exercise/pull/3.


Correctly handle config fields in multi component packages

Summary

Multi-component packages were breaking whenever the root package or one of its components contained spec.config in its manifest.yaml file.
This PR aims to fix the issue.
Change Type

Check List Before Merging

[ ] This PR passes all pre-commit hook validations.
[ ] This PR is fully tested and regression tests are included.
[ ] Relevant documentation has been updated.

Additional Information

Superseded by #568


Implement debug.List

Refers #9148
This PR implements debug.List method that uses reflect package to to list exported fields and methods names on structs/pointers and all keys in a map.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks, can you push the "sign CLA button" above?

I’ve completed the CLA Signing, but for some reason the bot thinks I have not.

I’ve completed the CLA Signing, but for some reason the bot thinks I have not.

You have probably a email mismatch between the mail address you used for the commit (as in: your Git user) and the email address registered on GitHub. You can fix this by adding email aliases in your GitHub profile.

Thanks for pointing it out, looks like CLA check passes now!

In case I need to add tests, please let me know. I looked around and could not find anything specific to add tests to apart from the init.go file, which I'm unclear on how to structure the example.

In case I need to add tests, please let me know.

We need some basic tests. Just create a debug_test.go file and put a basic TestList test with a simple test structs and a map. The init test you can ignore.

@bep I just added some basic tests, please have a look! Thanks.

I just noticed that the functions also returns fields that are not exported, let me fix that.

Fixed the issue, please review.
Thanks.

Thanks for this. I need to think a little before pulling this into the main branch. I have tested this a little, and while it does work great on technical level, I fear it may expose too much (deprecated and internal methods (not meant to be used in the templates, e.g. MarshalJSON) which I think may be more confusing than useful. I need to think about a way to filter out those.


Integrate confirmation ratio statistics on webinterface.

Code base for ratio checking per address is already present https://github.com/cwarner818/tt

Implemented in alpha9.


Fix scratchpad

#118
The problem is with the  functionality of smart focusing.
It  tries to not switch focus to a scratchpad, but instead of  seeing if  the window is currently a scratchpad,  it checks  if it was when it was focused.
I repaired this.
Now, if smart focusing is enabled, it will reopen any windows closed by a scratchpad's exclude rule once said scratchpad is closed.
I believe  this  extra functionality makes sense for smart focusing, but of course it is up for discussion.

This is now  just the bug fix, the "feature" will be put on a feature request and can be discussed there.


Skip some rrsets

Fixes #45

Codecov Report

Merging #46 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #46      +/-   ##
==========================================
+ Coverage   96.25%   96.26%   +<.01%
==========================================
  Files          73       73
  Lines        8644     8664      +20
  Branches      604      605       +1
==========================================
+ Hits         8320     8340      +20
  Misses        202      202
  Partials      122      122

Impacted Files
Coverage Δ

txaws/route53/tests/test_route53.py
97.8% <100%> (+0.5%)
:white_check_mark:

txaws/route53/client.py
100% <100%> (ø)
:white_check_mark:

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 52d2685...2bc18f4. Read the comment docs.


Limits in Agents DiscreteSpace

The Maze-Runner has an off-by one issue in its plotting.
Here's the discrepancy:
heatmap!(ax, walkmap(model); colormap=:grays)

ax.limits
#Observable{GeometryBasics.HyperRectangle{2, Float32}} with 4 listeners. Value:
#GeometryBasics.HyperRectangle{2, Float32}(Float32[0.0, 0.0], Float32[41.0, 41.0])

o, e = modellims(model)
#((0, 0), (42, 42))

modellims adds one to the bounding box. I believe we do this so that the markers have some breathing room: (0,0) also will not have any markers in it.
Should we do something about this margin when static_preplot! !== nothing, or just get the user to resize limits to their liking?

I believe we do this so that the markers have some breathing room: (0,0) also will not have any markers in it.

Yes.

just get the user to resize limits to their liking?

Yes, and they can even do this in the static_preplot function. However a quick PR should move these lines https://github.com/JuliaDynamics/InteractiveDynamics.jl/blob/9bec50bc87003bac83341cc2b94bc61fb23b9a1a/src/agents/stepping.jl#L67-L71  at the start of the function.


Generates quorum certificate even if a node hasn't submitted

Closes https://github.com/onflow/flow-core-contracts/issues/241
Ignores votes that have not been submitted and adds a test case for this

@joshuahannan did you mean to close this?

Yes, I included it in this PR so you could review both changes in one place: https://github.com/onflow/flow-core-contracts/pull/244


Create a prod namespace in the Kubernetes cluster

As a Developer
I need to add a prod namespace in the Kubernetes cluster
So that I can deploy the production versions of the Product Service
Details and Assumptions

The Kubernetes cluster is running

Acceptance Criteria
Given the cluster is running
When adding a prod namespace to the Kubernetes cluster
Then the service can be deployed in a prod environment


[system] Array reject on spacing transformation fixed

Other than adding and testing the correction purposed by @oliviertassinari, I had to add the following code stretch export * from './spacing'; in the file packages/material-ui-system/src/index.js in order to build the module.
It doesn't seem like a problem, but it seems important to quote those to avoid any type of side-effect.
Closes #19872

[x] I have followed (at least) the PR section of the contributing guide.

@weslenng I have updated the test case a bit to match the new logic. Thanks for the effort :)


PgData Type with drift files

Am I doing something wrong? I followed the documentation, my drift file looks like this:
CREATE TABLE [A] (
  "id" INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
  "created_on" `PgTypes.timestampWithoutTimezone` NOT NULL DEFAULT (strftime('%s', 'now')),
  "created_by" TEXT NOT NULL DEFAULT CURRENT_USER,
  "trn_dtl_guid" `PgTypes.uuid` NOT NULL,
  "updated_on" `PgTypes.timestampNoTimezone`  NOT NULL DEFAULT (strftime('%s', 'now')),
);

when i run the build_runner:
[WARNING] drift_dev on lib/src/tables/transaction_detail.drift:
line 11, column 25: Expected closing parenthesis
   ╷
11 │   "trn_dtl_guid" `PgTypes.uuid` NOT NULL,
   │                         ^
   ╵
[INFO] Running build completed, took 4.6s
[INFO] Caching finalized dependency graph completed, took 61ms
[INFO] Succeeded after 4.7s with 10 outputs (13 actions)

however the table does not get generated. I thought maybe i am using the wrong type for timestamp so I removed it and did this:
CREATE TABLE [A] (
  "id" INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
  "created_on" TEXT NOT NULL DEFAULT (strftime('%s', 'now')),
  "created_by" TEXT NOT NULL DEFAULT CURRENT_USER,
  "trn_dtl_guid" `PgTypes.uuid` NOT NULL,
  "updated_on" TEXT  NOT NULL DEFAULT (strftime('%s', 'now')),
);

srill got the same issue where the table does not generate
! drift 2.12.1 from git https://github.com/simolus3/drift.git at 6aa1a5 in drift (overridden)
! drift_postgres 0.1.0 from git https://github.com/simolus3/drift.git at 6aa1a5 in extras/drift_postgres (overridden)

Are you only overriding drift? Until the next release, you'd also have to add dependency overrides for drift_dev and sqlparser, since these packages are responsible for analyzing .drift files and this feature has not been released yet.

It should work with 2.13, let me know if you still have problems.


Response Layer -> OIPC Layer - Breaks Grouping of All Redactions

Describe the bug in current situation
When redactions are made on the Redline layer, the redactions show up in the Comments pane as being grouped, which is correct (i.e., the FOIPPA section number is the parent, with the redaction box being grouped with it as an annotation, or child).

However, when you change to the Response layer, this grouping broken, and the redaction box and FOIPPA section number are displayed as separate annotations:

Then, if you go to the OIPC layer from the Response layer, this grouping is broken:

This broken grouping is carried over to the Redline layer as well:

Link bug to the User Story
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
Medium
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Test-Marshal
Steps to Reproduce
Steps to reproduce the behavior:

Under the Redline or OIPC layer, apply a redaction w/ FOIPPA section number to a page (these will be grouped together in Comments pane)
Change to the Response layer, and see the error where the grouping is broken (these will show up as separate annotations in the Comments pane)
Change to the OIPC layer, and see the error where the grouping as now broken in this layer
If you made redactions in the Redline, change to the Redline layer, and see the error where the grouping as now broken in this layer

Actual/ observed behaviour/ results
When redactions are made in the OIPC or Redline layer, and you change to the Response layer the groupings are broken. Then, if you go to the OIPC layer next, it will permanently break the existing redaction's grouping in both the OIPC and Redline layers.
Expected behaviour
GIVEN a user has applied redactions to the Redline and/or OIPC layer
WHEN the layer is changed to the Response layer
THEN the redaction groupings are maintained in the OIPC and Redline layers
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

@divyav-aot - not specifically related to the 'Group' feature for the redactions (making free text parent of redaction boxes, and grouping them together), but it appears the addition of layers may have impacted the functionality of #4255

Standup 2023-08-29 - Response layer broken grouping  - to bring up in super user session, and create new ticket if action needed. Other bugs in this ticket, around other broken grouping in OIPC and Redline layer, will be handled in this ticket and QA'd.

Note: grouping is fine to break for response package as a possible fix, real issue is that the grouping breaks across all layers.

As per @KyEggleston 's comment ,grouping works good for other layers except Response package layer.


Different port each startup

Hi,
thank you for the plugin, I'm using it with a D301 and it works great.
Unfortunately the plugin is using a different port after each restart ("DoorBird is running on port ...", not the one it is listening on). Since my Homebridge is located in a docker container on a Synology NAS I have to re-configure the firewall each time to keep it working.
Is there a way to specify the port?
Another small issue, since the D301 doesn't support a camera I'm only using the lock, is there a way to delete/hide the camera and motion sensor devices in HomeKit but keep the lock?
Thanks in advance for the support.

As the port is a camera and your device does not support one, why do you need access to it?
Anyway, at the moment, the port given in videoconfig is used for the webserver. This could be changed to a new config value and the given port could be used for the camera.
Also, at the moment the camera is always created, but as the device type is a config value, this could be implemented with some if statements...
Are there any other doorbird devices without camera?

Thanks for your answer.
I don't know about other Doorbird devices without a camera other than the D301 at the moment but the updated D302 has been announced a while ago.
The plugin informs about two ports at startup: "DoorBird is listening on port XXXX" and "DoorBird is running on port YYYY"
I've managed to set the XXXX port (is that the webserver?) in the config but I haven't found a value to set the port YYYY the Plugin is running on. Each startup it states a different port.
My problem is that without the YYYY port accessible all 3 HomeKit devices (lock, camera and motion sensor) are marked as "not available" even if the webserver port XXXX is accessible.
Unfortunately I'm new at using homebridge, what do you mean with if statements?

The XXXX Port is the Webserver, which is used for forwarding the events and can be configured in the config file. The other Port (YYYY) is assigned by Homebridge dynamically at startup and afaik cannot be set to a fixed port.
Von meinem iPad gesendet
Am 08.08.2019 um 22:17 schrieb bleistift2 <notifications<EMAIL_ADDRESS>Thanks for your answer.
I don't know about other Doorbird devices without a camera other than the D301 at the moment but the updated D302 has been announced a while ago.
The plugin informs about two ports at startup: "DoorBird is listening on port XXXX" and "DoorBird is running on port YYYY"
I've managed to set the XXXX port (is that the webserver?) in the config but I haven't found a value to set the port YYYY the Plugin is running on. Each startup it states a different port.
My problem is that without the YYYY port accessible all 3 HomeKit devices (lock, camera and motion sensor) are marked as "not available" even if the webserver port XXXX is accessible.
Unfortunately I'm new at using homebridge, what do you mean with if statements?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbrownad%2Fhomebridge-doorbird%2Fissues%2F36%3Femail_source%3Dnotifications%26email_token%3DAGOOB2Z3S6YSQWHNYUF4OO3QDR5PBA5CNFSM4IKEG6M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD34ZAXA%23issuecomment-519671900&data=02|01||af092cdcc4de444b7bd308d71c3d7e0e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637008922735095207&sdata=wxM1qW8RLZkct6y5SYnQ9FHftuojKJHp2OOdJBcHlSI%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGOOB2YCU2API7RZSBWA4YLQDR5PBANCNFSM4IKEG6MQ&data=02|01||af092cdcc4de444b7bd308d71c3d7e0e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637008922735105218&sdata=s5yEdWx8546svwhv4mm5bSBaxEoBDbd0ub4%2BGmu8VGg%3D&reserved=0.

Fixed camera port is possible:
https://github.com/nfarina/homebridge/issues/927

BTW: "if statements" are not user related, this would have to be implemented in the source

Thank you for the link and the information.
Unfortunately I didn't manage to get it working so far.
server.js already had a port parameter, I nevertheless added another, so it looks like this:
hapAccessory.publish({       username: advertiseAddress,       pincode: accessoryPin,       category: accessory.category,       port: accessoryPort,       port: accessory.cameraSource.port,       mdns: this._config.mdns     }, this._allowInsecureAccess);
Since I don't have a camera and therefore don't have ffmpeg installed I didn't know where to add
ffmpeg.js -> this.port = cameraConfig.portc;
and added
"accessory.cameraSource.port": 5000
directly under the camera listening "port": 5001 in the config.js.
Since that didn't work, what's the right way to do it?
Are the 2 port parameters in server.js the problem?
How do I define the parameter in config.js?

Changing the config.js is not enough, all referenced issues refer to different versions of ffmges.js, so at first the latest version of ffmeg.js would have to be integrated.
What about just commenting out those three lines:
 // Setup and configure the camera services var cameraSource = new FFMPEG(hap, cameraConfig, self.log, videoProcessor); doorBirdAccessory.configureCameraSource(cameraSource);
But as the whole thing is added as a video doorbell, I do not know, how HomeKit reacts to this.

Unfortunately commenting out these lines results in the whole plugin refusing to start.
So it seems like in order to fix the port of the Doorbird plugin I'll have to install the otherwise not needed ffmpeg plugin and try the way suggested in the other thread. I'll try it some day next week, thank you.


Output Difference of two examples

Output Difference of two examples

{ "file.rs" | lines: 0 3 | code: rust }
{ "file.rs" | code: rust | lines: 0 3 }

file.rs:

fn main() {
    println!("Hello, World!");
}

Markdown Code 1: { "file.rs" | code: rust | lines: 0 3 }

Look at the following rust code:
<!--{ "file.rs" | code: rust | lines: 0 3 }-->
<!--{ end }-->
This will print 'Hello World' to the console.

Generated Code 1:

Look at the following rust code:
<!--{ "file.rs" | code: rust }-->
fn main() {
    println!("Hello, World!");
}
<!--{ end }-->
This will print 'Hello World' to the console.

Markdown Code 2: { "file.rs" | lines: 0 3 | code: rust }

Look at the following rust code:
<!--{ "file.rs" | lines: 0 3 | code: rust }-->
<!--{ end }-->
This will print 'Hello World' to the console.

Generated Code 2:

Look at the following rust code:
<!--{ "file.rs" | code: rust }-->
```rust
fn main() {
    println!("Hello, World!");
}
```
<!--{ end }-->
This will print 'Hello World' to the console.

The order of these is important

{ "file.rs" | lines: 0 3 | code: rust }
This will retrieve lines first, then surround that code with a rust code block

{ "file.rs" | code: rust | lines: 0 3 }
This will first surround the file contents with a code block and then retrieve lines 0:3 from that, which is probably not what you want.

Does that help? It looks like the generated code blocks you’ve posted don’t have the same command arguments as the markdown blocks you posted - am I missing something here?

I started to understand these two methods, they should output the same result. But the reality is different, in fact, it is also very good to meet different needs.

Im still not exactly sure what the issue you’re presenting is, but I’ve updated the documentation and made some changes. Let me know if that helps you at all.

Thank you very much for your reply. The tool you developed is great! I like it very much. I just want to give a hint.

Great to see this being used! Note, if you upgrade to v0.3.0 the line numbering system is 1-based instead of 0-based as this seemed more consistent with how we generally refer to line numbers.

Thank you!