New User Email Notification

🗣 Description
Add Env variables for new user registration email notification
💭 Motivation and context
Allow the admins to be notified when a new user has registered with the application.
✅ Checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.

@dylanj1752, in the PR description the checkboxes should look like [x] when checked (no spaces).  GitHub Markdown renders them nicely when you do that.  I made the change here already, but please try that going forward.

@dylanj1752, in the PR description the checkboxes should look like [x] when checked (no spaces). GitHub Markdown renders them nicely when you do that. (You can alternatively just click on the unchecked boxes and they will automatically change state.)
I made the change here already, but please try that going forward.


Support SkRegion for flutter engine

Hi,
I want to obtain a visible Path intersection with another path.
Problem is when I want to compare path with users gesture hit point. The path is Even-odd or Nonzero rule so when I draw a path on canvas with stroke PaintingStyle visible result is different from a path region.
Example: add circle or rect to the path, draw it with stroke painting style hit any position inside the path and check that path contains a point. The result always is true, so there are no possibilities to check that users click on path contour or inside a not visible path region.
SkRegion describes the set of pixels, so there are real pixels drawn on the device on this region and when I want to compared hit point with path only path contour will be taken
Maybe there is some other way to resolve this problem?

After longer tests, I think that it is not required to achieve the desired effect.
This is what I'm looking for https://docs.flutter.io/flutter/dart-ui/PathMetrics-class.html


swift 3.1 support?

When will it support swift 3.1?

Alamofire requires no changes to build without warnings under Swift 3.1.


No Trailing Whitespace

Source rule with the addition of a parameter to ignore whitespaces on empty lines

Fixed by #215


Pinger timeout should return an error

If the pinger reaches timeout, no error is returned from OnFinish() and it makes it seem like the probe finished successfully, even if nothing was returned from the ping job.
https://github.com/prometheus-community/pro-bing/blob/0999adf48b00a72b9ce152a562e2585ac986a6f6/ping.go#L538-L539
I believe this should return an error indicating the timeout was reached before the ping job finished fully. Happy to make the PR if this sounds good

Adding a +1 for this. Given that an unreachable host will block on .Run() without a timeout, it would be great to have some way to determine whether the pinger timed out.

indeed. Especially since one specifically has to set the timeout (which I initially did not do and wondered why my pinger go routine sometimes would not properly return).
Does it make sense to also set a timeout by default when the pinger is initialized?

indeed. Especially since one specifically has to set the timeout (which I initially did not do and wondered why my pinger go routine sometimes would not properly return). Does it make sense to also set a timeout by default when the pinger is initialized?

I tried running with pinger.Timeout = 1000 but the result is that it exits and returns like it responded to the ping (which is not true)

I may not understand, but a RunWithContext function exists, I'm using that to check for a timeout.
ctx, _ := context.WithTimeout(context.Background(), deadline)
err = client.RunWithContext(ctx)
	if err != nil {
		if errors.Is(err, context.DeadlineExceeded) {
			// Timeout
		}
		...
	}

Does this not work for your situation?


Fix user missing in detail view context

Fix bug #119
I am wondering if it could be better to use a helper function to find user instead of duplicate the code.

Code is already a bit factorized by the use of pytitionuser = get_session_user(request) but I'm open to suggestions.


Investigate adding embedded videos of pitches where they exist

Look at the SSI you tube channel:

https://www.youtube.com/@SoftwareSaved

This appears to work, see:

https://softwaresaved.github.io/CW-ideas/cw22-r-lessons-bug-tracking/


15 MAR 2021 - Product Control Common Template Meeting Minutes

Date
Monday, MAR 15 2021 - 10am ET / 2pm GMT
Untracked attendees

Fullname, Affiliation, GitHub username

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] Equity option template model discussion
[ ] Alternative solution - RVS
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

WebEx info

Meeting link: https://finos.webex.com/finos/j.php?MTID=m6e9255a2368279a9f1857f176cbf2c1a
Meeting number:<PHONE_NUMBER>
Password: J2SqF2Kp5X2
Call-in:

Join by video system: Dial<EMAIL_ADDRESS>You can also dial <IP_ADDRESS> and enter your meeting number.
Join by phone: +1-415-655-0003 US Toll | +44-20319-88141 UK Toll | Access code:<PHONE_NUMBER>

Attending from Skylight IPV:
@ashleymercer
@NigelHyde
@Richard-Cade-SkylightIPV
@Adam-McIlroy-Skylight

hi

Hi

hello

Hello, Rama and Carol from RVS

Hi, Carrie from MS here

hi


[BUG]: 안드로이드 지도 제스쳐 동작 안하는 현상

Is there an existing issue for this?

[X] I have searched the existing issues

Version of @mj-studio/react-native-naver-map
1.5.9
Version of react-native
0.73.2
What os are you seeing the problem on?
Android
What device types are you seeing the problem on?
Physcial Device
What architecture types of react native are you seeing the problem on?
Old Architecture(Bridge)
Version of device(android API, iOS OS version, etc...)
No response
Expo App

[ ] I am using Expo

What happened?
안드로이드에서 지도뷰에서 아무런 제스쳐가 먹질않습니다.
드래그해도 화면이움직이지 않습니다.
다만, 버튼들은 정상작동합니다. (  줌 조정, 현재위치, 옵션 등 .. )
IOS는 기가막히게 잘돌아갑니다.


Select: Comparison by reference

Bug, feature request, or proposal:
Bug, feature request
What is the expected behavior?
Select should have trackBy property as input. Sometimes complex objects can be used as a value of the options (country in my case). In this case comparison by reference can lead to false negatives.
What is the current behavior?
Comparison of values is done with === operator
What are the steps to reproduce?

Use reactive forms
Create select with few options which have complex objects as value
Set the value of the select to the copy of one of the objects.

What is the use-case or motivation for changing an existing behavior?
More use-cases covered, more accurate, and faster
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: 4.2.6
Angular Material: 2.0.0-beta.8
OS: Windows 10
Typescript: 2.4.3
Browsers: all

Duplicate of https://github.com/angular/material2/issues/2785


Update to newest valibot version

This is one of my first contacts with Valibot, so I am not very familiar with the library.

Thank you 👯

Releasing tomorrow.

Releasing tomorrow.

You sould probably update the playground :)


Rethink internal API for starting animations

Atm it's quite cumbersome to start a new animation, it requires the developer to manually create their own react instance and then mount in the DOM themselves in the animation hooks.
Wouldn't it be nice if we had some way of doing this generically, instead of each animation doing it themselves?

I'm thinking something like returning JSX from the appropriate hooks (beforeAnimate, animate, afterAnimate).
Something like this:
(data: AnimationData, onFinish: Function) => React.ReactNode;

There is also the case though for animations which want to affect the child component.
Perhaps we can have two type signatures, one for creation of custom content, and the other for pass props down to the child?
Create new markup
(data: AnimationData, onFinish: Function) => React.ReactNode;

Reuse children
(data: AnimationData, onFinish: Function) => ???;


Add Known Limitation for github.dev exceeding GraphQL rate limits

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
the-githubdev-web-based-editor.md
What part(s) of the article would you like to see updated?
Known Limitations don't list the exceeding of the github GraphQL Rate Limit.
This often happens when intesively write documentation on the web-editor or write code.
Additional information

the result is that sometimes commits can't be done and a fix is to wait a few minutes for the api rate limit to reset

@1fabi0 Thank you for opening this issue! I'll get this triaged for review ✨

Thanks for this issue! You or anyone else is welcome to open a PR to add this to the "Known limitations" section.

Thanks for this issue! You or anyone else is welcome to open a PR to add this to the "Known limitations" section.

Hi @skedwards88! :) I just made a PR for this. It's #33140.


modify ... LOG  for CC-RX

RENESAS CCRX can not support ##VA_ARGS

 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.gilbert168 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 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.gilbert168 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 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.gilbert168 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Export reqwest crate for easier usage of SlackWebRequestSender impl

Trying to use a 'directly imported' reqwest::Client with slack-rs-api might fail if your reqwest version doesn't match the one used by slack-rs-client (see also slack-rs/slack-rs#81). Re-exporting should help with that.

Thanks for the PR! The use-case makes sense to me, but I'm not sure about re-exporting the entirety of the reqwest crate. I like the approach used in rusoto where they export a default_client() function that creates the "default", but users still have the flexibility to implement the trait themselves if they have a newer version. I'd also be fine with just re-exporting reqwest::Client, though that's harder to document the usage of properly.

I had already changed it to only export reqwest::Client, but then noticed I needed another part of reqwest in my bot (reqwest::header::{Authorization, Bearer};, to download slack files). With the full export I can drop reqwest from my Cargo.toml.
I'll have a look at rusoto.

I needed another part of reqwest in my bot (reqwest::header::{Authorization, Bearer};, to download slack files

Can you expand a bit more on that, perhaps with some sample code of what you're doing? I'm interested if this is a use-case that isn't supported very well in the library or if it's outside the scope of the library.

My bot is listening for FileShare messages, downloading the file, processing it and posting a "summary" to another channel. Here's a condensed snippet from my code:
        if let Message::FileShare(MessageFileShare { file, text, .. }) = message {
            let file = file.unwrap();
            let response = self.reqwest_client.get(&file.url_private.unwrap())
                .header(Authorization(Bearer { token: self.token.clone() }))
                .send();
            let mut contents = String::new();
            response.read_to_string(&mut contents));
            // ...
        }`

Downloading the file works differently than the rest of the API as far as I see, it needs an Authorization header (docs). Might actually be nice to add this to the library.

Ah, I see, so it's not actually going through the API. In that case, I'd suggest that your code having a dependency on reqwest is entirely justified.
The default client here (which I agree with it getting exported!) is mostly just to help with the "simple" case where a user just wants to send Slack messages without having to think too much about setting up an HTTP client. If you want to share a client for sending other requests, I'd suggest implementing SlackWebRequestSender for your reqwest version's Client.
I think I did a poor job of documenting that. I'll open an issue to improve documentation around using clients.

If you want to share a client for sending other requests, I'd suggest implementing SlackWebRequestSender for your reqwest version's Client.

I'm not sure that's possible - I tried that before finding the mismatching version, but I got
impl doesn't use types inside crate

note: the impl does not reference any types defined in this crate
note: define and implement a trait or new type instead

Argh, yeah, that's a good point. You'd have to wrap the client in a newtype in order to implement it. It's kind of a pain... but it's a problem any library is going to have that wants to let users provide their own clients.
Here's a hypothetical. Say you wanted your bot to now integrate with AWS, so you pull in rusoto as a dependency. You'll probably want to use the same request sender with rusoto. If this exported the reqwest crate and rusoto did the same, which one do you use? Presumably whichever exports the later version, then you'd implement the trait from the other crate for the exported client. However, now you need to wrap the exported client in a newtype in order to implement the other trait, then you end up back at this same issue.
I guess what I'm saying is, there's really only two scenarios that are reasonable to support: the simple "I just want something that works" option (default client) and the "I want to use this client for other things as well" option. Re-exporting the crate only helps with one specific scenario of the latter, where you want to send your own requests + send Slack requests, but falls apart pretty quickly once you bring in other things that also want to send requests generically.

I added the default_client() function and changed the exports (I pushed a few intermediate versions so I could test with my bot and the slack-rs example in case you wondered). Wasn't sure how to deal with the error type - I think it has to be exported too so it can be matched against.

Looks good to me. Thanks!


UnityEngine.UnityException: GetNativeISpatialCoordinateSystemPtr can only be called from the main thread.

Describe the bug
I think the problem that there is no video displayed while running on the HL2 is regarded to this exception here:

It happens at this point inside LocatableCamera.cs:

What can be done to solve this issue?
To Reproduce
Steps to reproduce the behavior:

do every step described in the readme
run on HL2

Expected behavior
Running camera and tracking objects

Inside the constructor the LocatableCamera gets created which leads to this error:


Reuse Test and Lint workflows

The release workflow defines it's own test and lint steps: https://github.com/PyTemplate/python_package/blob/main/.github/workflows/release.yaml#L9-L51
Instead, the release workflow should reuse the test.yaml and lint.yaml. Possible help - https://docs.github.com/en/actions/using-workflows/reusing-workflows

Closing for too much effort. Might not be possible.
Cannot be reused in steps: https://github.community/t/actions-reusable-workflow-failing-to-find-action-yml-that-does-exist/231258/2


Add repo form is allows https, but stores it as undefined

When a user adds a repo using the full URL, it works but it saves the name as undefined.
The expectation is that undefined should be saved. Perha
Steps to fix:

[ ] write a test that ensures that only the save data can only be the owner/repo format.
[ ] add a sanitizer to properly remove the https://github.com/

Line that should be fixed is: https://github.com/bdougie/open-sauced/blob/master/src/components/AddRepoForm.js#L20

PR #357 created


Create a compiled version

I can't figure out how to compile this. May you please make a compiled version where I can run it in CMD and see a key (and for which edition its for maybe) or make a GUI where you can select the edition and then generate a key.

Hello,
I just found a way to build it.
First, you should download MinGW-32 from the official site, http://mingw.org/
You should select two packages in the installer, (in basic setup category), mingw32-base-bin and mingw32-gcc-g++-bin
After everything installed, you should add the MinGW bin folder to the path
Then, download OpenSSL Library on https://curl.se/windows/ (32-bit recommanded)
Open the zip, copy include and lib directory to the MinGW root directory, and copy
libcrypto-1_1.dll and libssl-1_1.dll to the keygen sources directory.
Open cmd in the keygen sources directory and execute:
g++ main.cpp -lcrypto -lssl -o winxp_keygen-bin
Finally, you only have to launch winxp_keygen-bin.exe in a cmd to generate a product key !
Good afternoon
PS: I confirm that this program works


feat: implement automated database backups

It should be possible to configure the bot to perform automated database backups.

Included in https://github.com/DarkAtra/v-rising-discord-bot/pull/125


[proof] converting vectors of F to single F element

This PR removes vectors from several proof structs (e.g. ProofEvaluations). The vectors were initially used because some of the evaluations were "chunked", but we don't do this anymore. Proof:
[kimchi/src/verifier.rs:483] proof.evals[0].w[0].len() = 1
[kimchi/src/verifier.rs:484] proof.evals[0].z.len() = 1
[kimchi/src/verifier.rs:485] proof.evals[0].s[0].len() = 1
[kimchi/src/verifier.rs:486] proof.evals[0].generic_selector.len() = 0
[kimchi/src/verifier.rs:487] proof.evals[0].poseidon_selector.len() = 0
[kimchi/src/verifier.rs:488] proof.evals[0].[lookup.as](http://lookup.as/)_ref().unwrap().sorted[0].len() = 1
[kimchi/src/verifier.rs:489] proof.evals[0].[lookup.as](http://lookup.as/)_ref().unwrap().aggreg.len() = 1
[kimchi/src/verifier.rs:490] proof.evals[0].[lookup.as](http://lookup.as/)_ref().unwrap().table.len() = 1
[kimchi/src/verifier.rs:491] proof.evals[0].[lookup.as](http://lookup.as/)_ref().unwrap().[runtime.as](http://runtime.as/)_ref().unwrap().len() = 1

The changes are pretty straight forward: I simply change things like Vec<F> to F and remove code that's not relevant anymore.
There's one thing that seems like a logic change (but is not): I do not include a polynomial in the evaluation proof if its associated commitment in the verifier index is empty. This is because of the following:

so, ran into an interesting edge case in our codebase, for committing to the zero polynomial we just have an empty commit (literally an empty vec), and when we do the evaluation proof we just omit such zero polynomials from the combined inner product. So for example, if you don't use poseidon in your circuit, the poseidon selector will be all zero and we will not add it to the aggregated evaluation proof. It also means we can't hide such a polynomial commitment.

It sounds sensible since pedersen commitments work by doing an inner product of a polynomial coeff with the URS' generators, and so we would get the point at infinity (and we can't encode that since we're in affine coordinates). But that also means we have some issue if a private polynomial evaluates to all zeros (I think the codebase doesn't address that edgecase). Would a private polynomial ever evaluate to all zeros? I'm guessing not at least due to the random rows (the probability would be very low).

Note that it would be nice to have two follow up to this PR:

refactor of the combine inner product function: https://github.com/o1-labs/proof-systems/pull/448
make absorb_evaluations less error-prone by using a macro https://github.com/o1-labs/proof-systems/issues/221

I think I narrowed the issue:
other:
[Fp256(BigInteger256([0, 0, 0, 0]))]
[Fp256(BigInteger256([0, 0, 0, 0]))]
orign:
[]
[]

the PCS doesn't like it when I pass [0] instead of []

closes https://github.com/o1-labs/proof-systems/issues/231

added an AbsorbableScalarField trait in the last commit (for lack of a better name)

sounds like I can't get consensus on this PR. I still believe it's the best route, but at the very least I'll leave this open for when I have time to submit smaller PRs that implement some of the ideas here.


Ziptype num:59 for header ##DZ

Hi, I transfered to some others projects in the past month. Recently I get some free time and try to optimize this MDF file project.
I download the dev branch source code and try to analyze some source code.
I am using this code to iterate groups and iterate each signals values.
	for gid, gp := range mdfFile.DataGroups {
		for _, cg := range gp.ChannelGroup {
			//fmt.Printf("gid[%d]: gp[%v], id[%d], cg[%v], Data[%v] \n", gid, gp, id, cg)
			var i int = 0
			fmt.Printf("group: %d, rowSize: %d cycleCount: %d \n", gid, cg.Block.RowSize(), cg.Block.Data.CycleCount) //**
			if cg.Block.Data.CycleCount <= 0 {
				continue
			}
			var chid int = 0
			for cn, ch := range cg.Channels {
				fmt.Println()
				fmt.Println("\t", "new channel:", chid, cn)
				chid++
				sam, er := ch.Sample()
				if er != nil {
					fmt.Println("\t", er)
					continue
				}
				fmt.Println("\t\t", len(sam), sam)
			}

			i++
		}

	}

Issues will happen when header is "##DZ" and zipType is 59, which is not supported in your code.

Use the sample code meet panics. So I try to iterate group and channls comparing with Python asammdf result. Python asammdf is OK to read the signal values.
In my MDF file, not all groups meet errors. The first several groups from the beginning have error. When meet header "##DZ" not all the result recognized as wrong zip type.
When reading groups and channel, the error looks like these log:
header is:  ##HL
header is:  ##DL
header is:  ##DZ
ziptype: 0
header is:  ##DT
dt, pos: 4317 4365 47250
... some value
header is:  ##DZ
ziptype: 0
header is:  ##DT
dt, pos: 4317 4365 47250
... some value
header is:  ##DZ
ziptype: 0
header is:  ##DT
dt, pos: 4317 4365 47250
... some value
header is:  ##DZ
ziptype: 0
header is:  ##DT
dt, pos: 4317 4365 47250
... some value
header is:  ##DZ
ziptype: 0
header is:  ##DT
dt, pos: 4317 4365 47250
... some value
header is:  ##DZ
ziptype: 59
         invalid decompress type 59

I will try to use MDF validator and give you the feedback later.

Thanks for your feedback. I will take a look into the code to see if I can found the issue.
"I will try to use MDF validator and give you the feedback later."
It would be great! Thanks

Hi @sccds
Please try the development branch
Use channel.PrintProperties()  to debug
	for index, channel := range channels {

		fmt.Println(index, channel.Name)
		samples, err := channel.Sample()
		if err != nil {
                        channel.PrintProperties()
			panic(err)
		}
		.....
	}

I changed the way the parameters are loaded from DZBlocks to see if that fixes your problem.
I fixed some bugs and found a weird comportament in the transpose decompress functions that I couldn't fix yet.
Also note that ASAMMDF ignores if the zypType is greater than 1.

So I remove the error and treat in same way of ASAMMDF to see if works in your code
let me know the results

Hi, I've added a few more debug messages to the development branch, could you run them and send me the errors?
Please send all the error messages so I know where exactly the code is failing.

0 time
&{Header:{ID:[35 35 67 78] Reserved:[0 0 0 0] Length:160 LinkCount:8} Link:{Next:4496 Composition:0 TxName:4152 SiSource:4344 CcConvertion:4400 Data:0 MdUnit:4184 MdComment:4216 AtReference:0 DefaultX:[0 0 0]} Data:{Type:2 SyncType:1 DataType:2 BitOffset:0 ByteOffset:0 BitCount:64 Flags:2048 InvalBitPos:0 Precision:0 Reserved:0 AttachmentCount:0 ValRangeMin:0 ValRangeMax:0 LimitMin:0 LimitMax:0 LimitExtMin:0 LimitExtMax:0}}panic: invalid block ID: expected ##DZ, got: ##DT. Read block: {ID:[35 35 68 84] Reserved:[0 0 0 0] Length:4749 LinkCount:0}

goroutine 1 [running]:

Added some changes to the code, check if this fix. Added some debug messages too

there are errors:
0 time
LOAD ADDRESS: 1819792
DZ BLOCK: data address 46003888
DZ BLOCK: BLock {ID:[35 35 68 90] Reserved:[0 0 0 0] Length:915 LinkCount:0}
DZ BLOCK: zip type 0
DZ BLOCK: BLock ##DT
DZ BLOCK: data address 46004808
DZ BLOCK: BLock {ID:[35 35 68 90] Reserved:[0 0 0 0] Length:844 LinkCount:0}
DZ BLOCK: zip type 0
DZ BLOCK: BLock ##DT
DZ BLOCK: data address 46005656
DZ BLOCK: BLock {ID:[35 35 68 90] Reserved:[0 0 0 0] Length:247 LinkCount:0}
DZ BLOCK: zip type 0
DZ BLOCK: BLock ##DT
DZ BLOCK: data address 46005904
DZ BLOCK: BLock {ID:[35 35 68 90] Reserved:[0 0 0 0] Length:253 LinkCount:0}
DZ BLOCK: zip type 0
DZ BLOCK: BLock ##DT
DZ BLOCK: data address 46006160
DZ BLOCK: BLock {ID:[35 35 68 90] Reserved:[0 0 0 0] Length:253 LinkCount:0}
DZ BLOCK: zip type 0
DZ BLOCK: BLock ##DT
DZ BLOCK: data address 1820040
&{Header:{ID:[35 35 67 78] Reserved:[0 0 0 0] Length:160 LinkCount:8} Link:{Next:4496 Composition:0 TxName:4152 SiSource:4344 CcConvertion:4400 Data:0 MdUnit:4184 MdComment:4216 AtReference:0 DefaultX:[0 0 0]} Data:{Type:2 SyncType:1 DataType:2 BitOffset:0 ByteOffset:0 BitCount:64 Flags:2048 InvalBitPos:0 Precision:0 Reserved:0 AttachmentCount:0 ValRangeMin:0 ValRangeMax:0 LimitMin:0 LimitMax:0 LimitExtMin:0 LimitExtMax:0}}panic: invalid block ID: expected ##DZ, got: ##DT. Read block: {ID:[35 35 68 84] Reserved:[0 0 0 0] Length:4749 LinkCount:0}

I found what I my mistake, it should be fix now. If you encounter more errors, add slog.SetLogLoggerLevel(slog.LevelDebug) in the beginning of your code to debug .

Hi, more signals are able to get the value. There are still some meet panic.
if I use channel.Sample() the program will stack with panic:
2024/11/07 16:54:05 DEBUG Block read:##HL
2024/11/07 16:54:05 DEBUG Block read:##DL
2024/11/07 16:54:05 DEBUG Block read:##DZ
2024/11/07 16:54:05 DEBUG Block read:##DT
2024/11/07 16:54:05 DEBUG Block read:##DZ
2024/11/07 16:54:05 DEBUG Block read:##DT
2024/11/07 16:54:05 DEBUG Block read:##DZ
2024/11/07 16:54:05 DEBUG Block read:##DT
2024/11/07 16:54:05 DEBUG Block read:##DZ
2024/11/07 16:54:05 DEBUG Block read:##DT
2024/11/07 16:54:05 DEBUG Block read:##DZ
2024/11/07 16:54:05 DEBUG Block read:##DT
2024/11/07 16:54:05 DEBUG Block read:##DT
panic: runtime error: index out of range [0] with length 0

If I use channel.RawSample() it can scan all the channels. There is another type of the errors as below:
2024/11/07 16:58:00 DEBUG Block read:##HL
2024/11/07 16:58:00 DEBUG Block read:##DL
2024/11/07 16:58:00 DEBUG Block read:##DZ
2024/11/07 16:58:00 DEBUG Block read:##DT
&{Header:{ID:[35 35 67 78] Reserved:[0 0 0 0] Length:160 LinkCount:8} Link:{Next:133784 Composition:0 TxName:133256 SiSource:133456 CcConvertion:44520000 Data:0 MdUnit:133288 MdComment:133320 AtReference:0 DefaultX:[0 0 0]} Data:{Type:0 SyncType:0 DataType:0 BitOffset:0 ByteOffset:273 BitCount:24 Flags:2 InvalBitPos:184 Precision:0 Reserved:0 AttachmentCount:0 ValRangeMin:0 ValRangeMax:0 LimitMin:0 LimitMax:0 LimitExtMin:0 LimitExtMax:0}}err:  not enough data to read uint64

The different values you found are probably related to the problem I mentioned earlier about "I found a weird comportament in the transpose decompress functions that I haven't been able to fix yet".
I'm working to fix it :)
about the gp.ChannelGroup, now it fixed.

Upload the MDF validator screenshot, you can let me know what information do you need.

Ok, I identified the problem with wrong values and I will work to fix it

Hi @sccds, Could check if the issues with differents values persist ?

different values issue still exists
python result for a signal
	samples=[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
	timestamps=[ 0.  1.  2.  3.  4.  5.  6.  7.  8.  9. 10. 11. 12. 13. 14. 15. 16. 17.
 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35.
 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50.]
	invalidation_bits=[ True  True  True  True  True  True  True  True  True  True  True  True
  True  True  True  True  True  True  True  True  True  True  True  True
  True  True  True  True  True  True  True  True  True  True  True  True
  True  True  True  True  True  True  True  True  True  True  True  True
  True  True  True]

Go result, different signal values and wired time
time
[0 -1e-09 0 0 8.590963187128025e+09 0 1.6137212833950002e+09 0 0 0 0 0 0 0 -1e-09 66679.36728592501 0 0 0 0 0 0 0 0 0 0 0 -1e-09 0 0 0 0 0 0 0 0 0 0 0 0 -1e-09 0 0 0 0 0 0 0 0 0 0 0 0 -1e-09 0 0 0 0 0 0 0 0 0 0 0]

signal
 [0 255 0 0 57 0 35 0 0 0 0 0 0 0 255 0 0 0 0 0 0 0 0 0 0 0 0 255 0 0 0 0 0 0 0 0 0 0 0 0 255 0 0 0 0 0 0 0 0 0 0 0 0 255 0 0 0 0 0 0 0 0 0 0 0]

There are also panic:
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
github.com/LincolnG4/GoMDF/blocks/CC.(*ValueText).Apply(0x140000f69a0, 0x10?)
        //GoMDF/blocks/CC/conversion.go:417 +0x358
github.com/LincolnG4/GoMDF.(*Channel).applyConversion(...)
        /GoMDF/channel.go:505
github.com/LincolnG4/GoMDF.(*Channel).Sample(0x14001f69680)
        /GoMDF/channel.go:376 +0xf0
main.main()
        /mdf_main.go:62 +0x1f4
exit status 2

Could you share the signals information in the mdf vector ? at least one panic and other with wrong values ?
e.g

I iterate groups and channels, meet panic:

panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
github.com/LincolnG4/GoMDF/blocks/CC.(*ValueText).Apply(0x14000182cb0, 0x30?)
        /GoMDF/blocks/CC/conversion.go:417 +0x358
github.com/LincolnG4/GoMDF.(*Channel).applyConversion(...)
        /GoMDF/channel.go:505
github.com/LincolnG4/GoMDF.(*Channel).Sample(0x140001e3680)
        /GoMDF/channel.go:376 +0xf0
main.main()
        /mdf_file_worker/mdf_workder_go/mdf_main.go:87 +0x3bc
exit status 2

wrong value

python result
samples=[-1.50000000e+02 -1.50000000e+02 -1.50000000e+02  1.00010474e+07
  1.00010474e+07  1.00010474e+07  1.00010474e+07  1.00010474e+07
  1.00010474e+07  1.00010474e+07  1.00010474e+07  1.00010474e+07
  1.00010474e+07  1.00010474e+07 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02
 -1.50000000e+02 -1.50000000e+02 -1.50000000e+02]

go result
 [-150 -150 -150 -150 -150 -150 -150 -150 -150 -150 8.201573855e+06 -72.375 38917.175 1.0776335415000001e+07 -150 -150 -150 -150 -150 -150 -150 -150 -150 2.1474686475e+07 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 2.1474686475e+07 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 2.1474686475e+07 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 -150 2.1474686475e+07 -150 -150]

It seems some value related to integer overflow?

The problem is some of the channels have invalidation bit that need to be filter. To be honest it was scheduled to be implemented in the future because I don't have samples of this type of file. But since you can support I will put it in the first of the queue :) . Btw, I will be travelling next days I will not work on it until I back.  But after I back I will work this and the new features and start the optimization of the package to be much faster :)


[stable/mongodb] Authentication failed with root password

I have installed mongodb without replica set & set root password as well as custom user
## MongoDB admin password
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#setting-the-root-password-on-first-run
##
mongodbRootPassword: admin123

## MongoDB custom user and database
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#creating-a-user-and-database-on-first-run
##
mongodbUsername: my-user
mongodbPassword: my-password
mongodbDatabase: my-database

Tried authentication for root user & it failed.

use admin
switched to db admin
db.auth('root','admin123')
Error: Authentication failed.
0

Authentication worked for custom user (my-user)

db.auth('my-user','my-password')
1

Troubleshooting -> Secrets are getting created with the values set as part of values.yaml
kubectl get secret --namespace default my-release-mongodb -o jsonpath="{.data.mongodb-root-password}" | base64 --decode
admin123

mongodb Pods are in running state
[mongodb]# kubectl get pod
NAME                                  READY   STATUS    RESTARTS   AGE
my-release-mongodb-6b7c6d989b-fdbvp   1/1     Running   0          79m

mongodb nodePort service is in running state
[mongodb]# kubectl get svc | grep mongo
my-release-mongodb                  NodePort       <IP_ADDRESS>    <none>                                                27017:30000/TCP

Hi, @modassarrana.
I'm not able to reproduce your issue. I'm using this values.yaml file:
$ cat values.yaml
## MongoDB admin password
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#setting-the-root-password-on-first-run
##
mongodbRootPassword: admin123

## MongoDB custom user and database
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#creating-a-user-and-database-on-first-run
##
mongodbUsername: user
mongodbPassword: password123
mongodbDatabase: database

Then I install the chart with the following command:
$ helm install stable/mongodb --namespace amoreno-mng --name mongo -f values.yaml

Run a client as instructed in the NOTES.txt file:
$ kubectl run --namespace amoreno-mng mongo-mongodb-client --rm --tty -i --restart='Never' --image bitnami/mongodb --command -- mongo admin --host mongo-mongodb --authenticationDatabase admin -u root -p $MONGODB_ROOT_PASSWORD

If you don't see a command prompt, try pressing enter.

>
>
> use admin
switched to db admin
> db.auth('root', 'admin123')
1

Can you share the full command you are using to install the chart and the options you are changing from default?
Regards,
Alejandro

Hello,
Do you have attached persistent volume ? If yes please remove it and recreate the cluster. I had same issue and it seems that an old password remained in that storage so when db was starting it would load that password from storage not the new one that I've provided in the configuration file.

Yes i have attached persistent volume. I have created a local storage , persistent volume before installing mongodb chart. As you have mentioned , it could be an issue. I have uninstalled the chart & deleted PV . Re-create pv & installed again. Its the same issue. Please find the persistent volume & storage class below thati am using :
------------
kind: PersistentVolume
apiVersion: v1
metadata:
  name: pv-vol
  labels:
    type: local
spec:
  storageClassName: local
  capacity:
    storage: 8Gi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: "/bitnami/mongodb"

cat sc.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: local
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"
provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer

Enabled persistenccy in values.yaml
persistence:
  enabled: true
  accessModes:
    -  ReadWriteOnce
  size: 8Gi

Even set storage class as local in values.yaml
 mountPath: /bitnami/mongodb
 storageClass: "local"

Hi @alemorcuq ,
Command to install mongodb chart
helm install --name my-release -f values.yaml stable/mongodb
Values that i have changed are
volumePermissions:
  enabled: true
usePassword: true
# existingSecret: name-of-existing-secret

## MongoDB admin password
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#setting-the-root-password-on-first-run
##
mongodbRootPassword: admin123

## MongoDB custom user and database
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#creating-a-user-and-database-on-first-run
##
mongodbUsername: my-user
mongodbPassword: my-password
mongodbDatabase: my-database

service:
  ## Specify an explicit service name.
  # name: svc-mongo
  ## Provide any additional annotations which may be required.
  ## The value is evaluated as a template, so, for example, the value can depend on .Release or .Chart
  annotations: {}
  type: NodePort
  # clusterIP: None
  port: 27017

  ## Specify the nodePort value for the LoadBalancer and NodePort service types.
  ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
  nodePort: 30000

persistence:
  enabled: true
  accessModes:
    -  ReadWriteOnce
  size: 8Gi
  storageClass: "local"

I have shared persistent volume & storage class that i have created in my earlier comment as well.
mongodb root password ->
[root@svpod mongodb]#  export MONGODB_ROOT_PASSWORD=$(kubectl get secret --namespace default my-release-mongodb -o jsonpath="{.data.mongodb-root-password}" | base64 --decode)
[root@svpod mongodb]# echo $MONGODB_ROOT_PASSWORD
admin123

command to test the connectivity with root user
[root@svpod mongodb]# kubectl run --namespace default my-release-mongodb-client --rm --tty -i --restart='Never' --image bitnami/mongodb --command -- mongo admin --host my-release-mongodb --authenticationDatabase admin -u root -p $MONGODB_ROOT_PASSWORD

MongoDB shell version v4.0.13
connecting to: mongodb://my-release-mongodb:27017/admin?authSource=admin&gssapiServiceName=mongodb
2019-12-12T02:35:31.410+0000 E QUERY    [js] Error: Authentication failed. :
connect@src/mongo/shell/mongo.js:344:17
@(connect):2:6
exception: connect failed
pod "my-release-mongodb-client" deleted

As i have mentioned , its working fine with custom user i.e. my-user , my-password
pod default/my-release-mongodb-client terminated (Error)

Please find attached bellow my configuration file.

Remove volumes
Use my config values (values-production.yml)
Login withL user root -> password dan -> collection admin
Please provide feedback

## Global Docker image parameters
## Please, note that this will override the image parameters, including dependencies, configured to use the global value
## Current available global Docker image parameters: imageRegistry and imagePullSecrets
##
# global:
#   imageRegistry: myRegistryName
#   imagePullSecrets:
#     - myRegistryKeySecretName
#   storageClass: myStorageClass

image:
  ## Bitnami MongoDB registry
  ##
  registry: docker.io
  ## Bitnami MongoDB image name
  ##
  repository: bitnami/mongodb
  ## Bitnami MongoDB image tag
  ## ref: https://hub.docker.com/r/bitnami/mongodb/tags/
  ##
  tag: 4.2.2-ol-7-r2
  ## Specify a imagePullPolicy
  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
  ##
  pullPolicy: IfNotPresent
  ## Optionally specify an array of imagePullSecrets.
  ## Secrets must be manually created in the namespace.
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
  ##
  # pullSecrets:
  #   - myRegistryKeySecretName

  ## Set to true if you would like to see extra information on logs
  ## It turns on Bitnami debugging in minideb-extras-base
  ## ref:  https://github.com/bitnami/minideb-extras-base
  debug: false

## String to partially override mongodb.fullname template (will maintain the release name)
##
# nameOverride:

## String to fully override mongodb.fullname template
##
# fullnameOverride:

# Add custom extra environment variables to all the MongoDB containers
# extraEnvVars:

## Init containers parameters:
## volumePermissions: Change the owner and group of the persistent volume mountpoint to runAsUser:fsGroup values from the securityContext section.
##
volumePermissions:
  enabled: false
  image:
    registry: docker.io
    repository: bitnami/minideb
    tag: stretch
    pullPolicy: Always
    ## Optionally specify an array of imagePullSecrets.
    ## Secrets must be manually created in the namespace.
    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
    ##
    # pullSecrets:
    #   - myRegistryKeySecretName
  resources: {}

## Enable authentication
## ref: https://docs.mongodb.com/manual/tutorial/enable-authentication/
#
usePassword: true
# existingSecret: name-of-existing-secret

## MongoDB admin password
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#setting-the-root-password-on-first-run
##
mongodbRootPassword: dan

## MongoDB custom user and database
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#creating-a-user-and-database-on-first-run
##
mongodbUsername: cristi
mongodbPassword: test
mongodbDatabase: test

## Whether enable/disable IPv6 on MongoDB
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#enabling/disabling-ipv6
##
mongodbEnableIPv6: false

## Whether enable/disable DirectoryPerDB on MongoDB
## ref: https://github.com/bitnami/bitnami-docker-mongodb/blob/master/README.md#enabling/disabling-directoryperdb
##
mongodbDirectoryPerDB: true

## MongoDB System Log configuration
## ref: https://github.com/bitnami/bitnami-docker-mongodb#configuring-system-log-verbosity-level
##
mongodbSystemLogVerbosity: 0
mongodbDisableSystemLog: false

## MongoDB additional command line flags
##
## Can be used to specify command line flags, for example:
##
## mongodbExtraFlags:
##  - "--wiredTigerCacheSizeGB=2"
mongodbExtraFlags: []

## Pod Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
##
securityContext:
  enabled: true
  fsGroup: 1001
  runAsUser: 1001

## Kubernetes Cluster Domain
clusterDomain: cluster.local

## Kubernetes service type
service:
  ## Specify an explicit service name.
  # name: svc-mongo
  ## Provide any additional annotations which may be required.
  ## The value is evaluated as a template, so, for example, the value can depend on .Release or .Chart
  annotations: {}
  type: ClusterIP
  # clusterIP: None
  port: 27017

  ## Specify the nodePort value for the LoadBalancer and NodePort service types.
  ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
  ##
  # nodePort:
  ## Specify the externalIP value ClusterIP service type.
  ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#external-ips
  # externalIPs: []
  ## Specify the loadBalancerIP value for LoadBalancer service types.
  ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer
  ##
  # loadBalancerIP:
  ## Specify the loadBalancerSourceRanges value for LoadBalancer service types.
  ## ref: https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
  ##
  # loadBalancerSourceRanges: []

## Setting up replication
## ref: https://github.com/bitnami/bitnami-docker-mongodb#setting-up-a-replication
#
replicaSet:
  ## Whether to create a MongoDB replica set for high availability or not
  enabled: true
  useHostnames: true

  ## Name of the replica set
  ##
  name: rs0

  ## Key used for replica set authentication
  ##
  # key: key

  ## Number of replicas per each node type
  ##
  replicas:
    secondary: 1
    arbiter: 1

  ## Pod Disruption Budget
  ## ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/
  pdb:
    enabled: true
    minAvailable:
      secondary: 1
      arbiter: 1
    # maxUnavailable:
    # secondary: 1
    # arbiter: 1

# Annotations to be added to the deployment or statefulsets
annotations: {}

# Additional labels to apply to the deployment or statefulsets
labels: {}

# Annotations to be added to MongoDB pods
podAnnotations: {}

# Additional pod labels to apply
podLabels: {}

## Use an alternate scheduler, e.g. "stork".
## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
##
# schedulerName:

## Configure resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources:
  limits:
    cpu: 500m
    memory: 2048Mi
# requests:
#   cpu: 100m
#   memory: 256Mi

# Define separate resources per arbiter, which are less then primary or secondary
# used only when replica set is enabled
resourcesArbiter:
  limits:
    cpu: 500m
    memory: 512Mi
# requests:
#   cpu: 100m
#   memory: 256Mi

## Pod priority
## https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
# priorityClassName: ""

## Node selector
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
nodeSelector: {}

## Affinity
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
# Define separate affinity for arbiter pod
affinityArbiter: {}

## Tolerations
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
tolerations: []

## updateStrategy for MongoDB Primary, Secondary and Arbitrer statefulsets
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
updateStrategy:
  type: RollingUpdate

## Enable persistence using Persistent Volume Claims
## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
##
persistence:
  enabled: true
  ## A manually managed Persistent Volume and Claim
  ## Requires persistence.enabled: true
  ## If defined, PVC must be created manually before volume will be bound
  ##
  # existingClaim:

  ## The path the volume will be mounted at, useful when using different
  ## MongoDB images.
  ##
  mountPath: /bitnami/mongodb

  ## The subdirectory of the volume to mount to, useful in dev environments
  ## and one PV for multiple services.
  ##
  subPath: ""

  ## mongodb data Persistent Volume Storage Class
  ## If defined, storageClassName: <storageClass>
  ## If set to "-", storageClassName: "", which disables dynamic provisioning
  ## If undefined (the default) or set to null, no storageClassName spec is
  ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
  ##   GKE, AWS & OpenStack)
  ##
  # storageClass: "-"
  accessModes:
    - ReadWriteOnce
  size: 8Gi
  annotations: {}

## Configure the ingress resource that allows you to access the
## MongoDB installation. Set up the URL
## ref: http://kubernetes.io/docs/user-guide/ingress/
##
ingress:
  ## Set to true to enable ingress record generation
  enabled: false

  ## Set this to true in order to add the corresponding annotations for cert-manager
  certManager: false

  ## Ingress annotations done as key:value pairs
  ## For a full list of possible ingress annotations, please see
  ## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md
  ##
  ## If tls is set to true, annotation ingress.kubernetes.io/secure-backends: "true" will automatically be set
  ## If certManager is set to true, annotation kubernetes.io/tls-acme: "true" will automatically be set
  annotations:
  #  kubernetes.io/ingress.class: nginx

  ## The list of hostnames to be covered with this ingress record.
  ## Most likely this will be just one host, but in the event more hosts are needed, this is an array
  hosts:
    - name: mongodb.local
      path: /

  ## The tls configuration for the ingress
  ## see: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
  tls:
    - hosts:
        - mongodb.local
      secretName: mongodb.local-tls

  secrets:
  ## If you're providing your own certificates, please use this to add the certificates as secrets
  ## key and certificate should start with -----BEGIN CERTIFICATE----- or
  ## -----BEGIN RSA PRIVATE KEY-----
  ##
  ## name should line up with a tlsSecret set further up
  ## If you're using cert-manager, this is unneeded, as it will create the secret for you if it is not set
  ##
  ## It is also possible to create and manage the certificates outside of this helm chart
  ## Please see README.md for more information
  # - name: airflow.local-tls
  #   key:
  #   certificate:

## Configure the options for init containers to be run before the main app containers
## are started. All init containers are run sequentially and must exit without errors
## for the next one to be started.
## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
# extraInitContainers: |
#   - name: do-something
#     image: busybox
#     command: ['do', 'something']

## Configure extra options for liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
livenessProbe:
  enabled: true
  initialDelaySeconds: 30
  periodSeconds: 10
  timeoutSeconds: 5
  failureThreshold: 6
  successThreshold: 1
readinessProbe:
  enabled: true
  initialDelaySeconds: 5
  periodSeconds: 10
  timeoutSeconds: 5
  failureThreshold: 6
  successThreshold: 1

# Define custom config map with init scripts
initConfigMap: {}
#  name: "init-config-map"

## Entries for the MongoDB config file. For documentation of all options, see:
##   http://docs.mongodb.org/manual/reference/configuration-options/
##
configmap:
#  # where and how to store data.
#  storage:
#    dbPath: /bitnami/mongodb/data/db
#    journal:
#      enabled: true
#    directoryPerDB: false
#  # where to write logging data.
#  systemLog:
#    destination: file
#    quiet: false
#    logAppend: true
#    logRotate: reopen
#    path: /opt/bitnami/mongodb/logs/mongodb.log
#    verbosity: 0
#  # network interfaces
#  net:
#    port: 27017
#    unixDomainSocket:
#      enabled: true
#      pathPrefix: /opt/bitnami/mongodb/tmp
#    ipv6: false
#    bindIpAll: true
#  # replica set options
#  #replication:
#    #replSetName: replicaset
#    #enableMajorityReadConcern: true
#  # process management options
#  processManagement:
#     fork: false
#     pidFilePath: /opt/bitnami/mongodb/tmp/mongodb.pid
#  # set parameter options
#  setParameter:
#     enableLocalhostAuthBypass: true
#  # security options
#  security:
#    authorization: disabled
#    #keyFile: /opt/bitnami/mongodb/conf/keyfile

## Prometheus Exporter / Metrics
##
metrics:
  enabled: true

  image:
    registry: docker.io
    repository: bitnami/mongodb-exporter
    tag: 0.10.0-debian-9-r49
    pullPolicy: IfNotPresent
    ## Optionally specify an array of imagePullSecrets.
    ## Secrets must be manually created in the namespace.
    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
    ##
    # pullSecrets:
    #   - myRegistryKeySecretName

  ## String with extra arguments to the metrics exporter
  ## ref: https://github.com/dcu/mongodb_exporter/blob/master/mongodb_exporter.go
  extraArgs: ""

  ## Metrics exporter resource requests and limits
  ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
  ##
  # resources: {}

  ## Metrics exporter liveness and readiness probes
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
  livenessProbe:
    enabled: true
    initialDelaySeconds: 15
    periodSeconds: 5
    timeoutSeconds: 5
    failureThreshold: 3
    successThreshold: 1
  readinessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 1
    failureThreshold: 3
    successThreshold: 1

  ## Metrics exporter pod Annotation
  podAnnotations:
    prometheus.io/scrape: "true"
    prometheus.io/port: "9216"

  ## Prometheus Service Monitor
  ## ref: https://github.com/coreos/prometheus-operator
  ##      https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md
  serviceMonitor:
    ## If the operator is installed in your cluster, set to true to create a Service Monitor Entry
    enabled: false

    ## Specify a namespace if needed
    # namespace: monitoring

    ## Used to pass Labels that are used by the Prometheus installed in your cluster to select Service Monitors to work with
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#prometheusspec
    additionalLabels: {}

    ## Specify Metric Relabellings to add to the scrape endpoint
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#endpoint
    # relabellings:

    alerting:
      ## Define individual alerting rules as required
      ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#rulegroup
      ##      https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
      rules: {}

      ## Used to pass Labels that are used by the Prometheus installed in your cluster to select Prometheus Rules to work with
      ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#prometheusspec
      additionalLabels: {}

@modassarrana  Yes i have the same issue but after deleting pv it's working fine.
kubectl delete pvc --all


Additional columns on "Projects" table

When reading the README, I felt like I wanted more information about the Projects before diving into each one by clicking them. Perhaps adding a couple of columns with a short sample of the instructions and an example of the project could help potential users browse and choose the idea in a friendlier manner.
For example:

Name
Instructions
Example

Christmas Lights
Draw seven colored circles in a row and based on a timer change the intensity of each each circle
PureCSSChristmasLights

Color Cycle
Draw a box filled with a user specified color and makes small changes over time also based on user input
CSS Color Changing Background

Edit: couldn't find the way to add the "new idea" label
Edit 2: if you like the idea, I can implement it for the current Projects table and submit a PR :)

Good idea, I'm just thinking how we'll add all the instructions in that table. 🤔 Some of the project have longer descriptions. What do you say?

This is a good idea. I suggest we do the following. Add a short description and a tier number to the app table in README.md. This will provide the viewer with information about the app as well as what level of expertise is required to complete it. We'll include a definition of the tiers in the README.md as well.

Hmm, yes...it would have to be a single sentence that would summarize the project, just like in my example.
If it is too complicated for some projects, perhaps that instructions could be something even more general. For example, if it is a super complex Pomodoro timer with lots of functionalities, the instructions could be something like: "Pomodoro timer with distinct dynamic functionalities". That way the person knows it is a timer but a complicated one. What do you think?
Update: as I was writing this, I saw @jdmedlock 's suggestion which sounds great. Let me know if I can help in any way.

Here's a more concrete example. Each detailed app specification start with the summary info:

We'll incorporate this info into the README.md so it looks like this:

That's perfect @jdmedlock !! Thank you!


cryptography: 1.5.3 -> 1.7.2

Also update cryptography-vectors.
cc @FRidh
Motivation for this change
Split out of #22683 since this bump is unneeded for radicale.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Tested, and no new failures it seems.


Clean-up BERT-BASE FSDP test

What does this PR do?
Clean-up flags from bert-base FSDP flags.

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

@regisss this needs to be merged after synapse 1.15 release.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Cannot read properties of null (reading 'getValue')

We would like to use Flagsmith with Plasmic and SSR.
When running "yarn build" I get the following error:"Generating static pages (0/1)PLASMIC: Encountered error when pre-rendering TweetsProvider: TypeError: Cannot read properties of null (reading 'getValue')"
This is my code for testing, which is mostly from the documentation of Plasmic.
import { DataProvider, usePlasmicQueryData } from "@plasmicapp/loader-nextjs";
import { useFlags } from "flagsmith/react";

export function TweetsProvider(props: { children: React.ReactNode }) {
  const flags = useFlags(["google-analytics-tracking"]);
  if (flags["google-analytics-tracking"].enabled) {
    console.log("Google Analytics enabled");
  }
  const { children } = props;
  const { data } = usePlasmicQueryData("/tweets", async () => {
    console.log("Fetching tweets...");
    const resp = await fetch(
      "https://studio.plasmic.app/api/v1/demodata/tweets"
    );
    return await resp.json();
  });
  if (!data) {
    return null;
  }
  return (
    <DataProvider name="tweets" data={data}>
      {children}
    </DataProvider>
  );
}

If I comment the four lines after "export function" everything is working fine. But with them the console.log("Fetching tweets..."); doesn't appear and instead the error comes up. It seems like the usePlasmicQueryData skips the whole arrow function.

Hi, is it possible that the useflags hook depends on some react context being available? That would be my initial suspicion, maybe it is trying to read some react context that is not being provided and thus is null.
You would need to provide the context wherever the extract plasmic query data function is being invoked. What's going on is it is trying to pre-render the react tree here, so you just need to specify a react tree that renders correctly, including any necessary context providers. The default nextjs quick start just renders the plasmic root provider and Plasmic component inside of the pre-rendering phase.
Please let me know if that helps / if that is the issue!

Hi!
I think I did everything right in this matter. Maybe you can have a look in my repo here?

Hi, that does seem to be the issue.
In the catchall page, the rendering function renders within the wrappers provided by _app.tsx, which has a FlagsmithProvider.

But this is not being provided within getStaticProps during pre-rendering to the extractPlasmicQueryData.

Please let me know if this makes sense!

Thank you so much! This did the trick!


Replace wait() with SmartWait()

I recommend replacing your wait() calls with something like SmartWait():
local Heartbeat = game:GetService("RunService").Heartbeat
local function SmartWait(timeToWait)
	timeToWait = timeToWait or 1/60
	local timeElapsed = 0

	while timeElapsed <= timeToWait do
		local timeWaited = Heartbeat:Wait()
		timeElapsed = timeElapsed + timeWaited
	end
	return timeElapsed
end

Clonetrooper demonstrates what can happen when using wait() on large scale projects here:
https://www.youtube.com/watch?v=cj_21dL_W38

Thank you for the suggestion!
From my current understanding, this sort of change would be of trivial effect to the stability and performance speed of ProfileService - wait() is only used in places where even a 50% offset in wait time would make no apparent difference.


1.13 Update?

When can i expect an update to 1.13? this is a core plugin for my server and can't update to 1.13 until this plugin is updated.

You can find stablish builds here: https://ci.codemc.org/job/EpicEricEE/job/ShopChest/


vagrant up on ubuntu cloud images fails when using vbguest plugin

To reproduce:
$ vagrant --version
Vagrant 2.0.1
$ vagrant plugin list
vagrant-share (1.1.9, system)
vagrant-vbguest (0.15.0)
$ vagrant init ubuntu/artful64
A `Vagrantfile` has been placed in this directory.  Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
$ vagrant up --provider virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/artful64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/artful64' is up to date...
==> default: Setting the name of the VM: vagrant-bug_default_1515002901534_82359
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.1.28
VBoxService inside the vm claims: 5.1.30
Going on, assuming VBoxService is correct...
[default] GuestAdditions seems to be installed (5.1.30) correctly, but not running.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.1.28
VBoxService inside the vm claims: 5.1.30
Going on, assuming VBoxService is correct...
Failed to start vboxadd.service: Unit vboxadd.service not found.
Failed to start vboxadd-service.service: Unit vboxadd-service.service not found.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.1.28
VBoxService inside the vm claims: 5.1.30
Going on, assuming VBoxService is correct...
bash: line 4: setup: command not found
==> default: Checking for guest additions in VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

 setup

Stdout from the command:

Stderr from the command:

bash: line 4: setup: command not found

Taking into account @jarl-dk 's https://github.com/dotless-de/vagrant-vbguest/issues/278#issuecomment-358023589 together with https://github.com/dotless-de/vagrant-vbguest#config-options , I've composed even better workaround:
Add this to Vagrantfile:
config.vbguest.installer_arguments = ['--nox11', '-- --do']

- and it will stop failing! Doubled double-slash is required.
Cheers)

Try updating to the latest image. I've just used it with the above Vagrantfile and its fine.
https://app.vagrantup.com/ubuntu/boxes/artful64
My setup has the following plugins:
vagrant plugin list
vagrant-host-shell (0.0.4)
vagrant-hostmanager (1.8.8)
vagrant-rancher (1.1.4)
vagrant-reload (0.0.1)
vagrant-share (1.1.9)
vagrant-triggers (0.5.3)
vagrant-vbguest (0.15.1)

Hello Richard
Thank you for your hints. I will try them. Nevertheless; I am using the dcos-vagrant cluster on Debian 8.10 host system (more for stability reasons), not as baremetal nor as onpremise nor as 'aws cloud'; so 'completely' virtualized, since I am in case studies on DC/OS. Do you think this could cause 'my' problems with VboxGuestAdditions' installation during 'vagrant up'? Since VBGuestAdditions will not install completely, automatically and with no errors, DC/OS may/will be my second choice.
Thank you for your response,
Roger

@jarl-dk, @RogerWeihrauch and @PatchRanger's workarounds didn't work for me unfortunately.
Environment:

Windows 10
VBox 5.2.12
Vagrant 2.1.1
CentOS 7

None of the workarounds worked for me.
My environment is:

Linux Mint 18.2 KDE
Vagrant 2.1.1
vagrant-vbguest 0.15.1
VirtualBox 5.2.12 r122591
config.vm.box = "centos/7"

I've just tried "vagraint init centos/7; vagrant up" with the following:

Ubuntu 18.04
Vagrant 2.1.2
vagrant-vbguest 0.15.2
VirtualBox 5.2.16 r123759

And it works nicely for me:
==> default: Machine booted and ready!
[default] GuestAdditions 5.2.16 running --- OK.

Still reproduces for me:

Ubuntu 18.10 (beta)
guest vm is generic/ubuntu1810
Vagrant 2.1.5
vagrant-vbguest 0.15.2
virtualbox 5.2.18-dfsg-2

==> default: Machine booted and ready!
[default] GuestAdditions seems to be installed (5.2.18) correctly, but not running.
bash: line 4: setup: command not found
==> default: Checking for guest additions in VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

 setup

Stdout from the command:

Stderr from the command:

bash: line 4: setup: command not found

I'm going out on a limb here, but I suppose it's a script run by the VirtualBox Guest Additions installer, not vbguets. (the only place when vbguest runs something like setup is, when it tries to run the re-install routine of an existing GA installation, and that's a singe command).
Can you try and run in debug mode (https://www.vagrantup.com/docs/other/debugging.html) to see which command gets send to the VM right before that error occurs.

I can confirm seeing similar problem.  I will report and confirm is symptom and proposed solution still work.
I wish Vagrant had a documented way to case-switch conditional block for detecting on which OS the current vagrant is running.

This is happening again, using VBox 6.0.6 that came out recently... the issue is with an error in the install script of the VBox Guest additions ISO that gets shipped with VBox...
Going back to VBox 5.2.28 works as a workaround.

Here is my result
`[docker-host] GuestAdditions seems to be installed (6.0.6) correctly, but not running.
bash: line 4: setup: command not found
==> docker-host: Checking for guest additions in VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
setup
Stdout from the command:
Stderr from the command:
bash: line 4: setup: command not found`

A workaround is to run
vagrant vbguest --do install
vagrant up

When it fails

Great tip! Thank you!
Before vagrant up I had to do a vagrant halt.

Can we reopen this? Or do we need a new issue?
I'm also encountering this with Virtualbox 6.0.6. Downgrading to 6.0.4 seemed to fix it for now.

Can we reopen this? Or do we need a new issue?
I'm also encountering this with Virtualbox 6.0.6. Downgrading to 6.0.4 seemed to fix it for now.

This appears to be an issue with Virtualbox. I was able to resolve the issue by downgrading to 6.0.4 per recommendation by Dane with the following commands:
$ brew cask uninstall virtualbox
$ brew cask install https://raw.githubusercontent.com/caskroom/homebrew-cask/d7f8219fa51f7c96a17c346acfab547a6af7f956/Casks/virtualbox.rb

It sounds like an issue should be opened with Virtualbox, is anyone familiar enough with this problem / the Virtualbox project to do that?

I've created a ticket with Virtualbox - https://www.virtualbox.org/ticket/18598

Related or maybe the same issue? https://github.com/dotless-de/vagrant-vbguest/issues/333

run
vagrant plugin install vagrant-vbguest
boxes works just fine.

VBGuest Addition plugin works with VB 6.0.6 when creating VM but fails on subsequent call to 'vagrant up' when trying to configure VB Guest Addition that seems not to be running.

VB 6.0.6 is kinda broken, try with 6.0.4

This seems to be caused by check for vboxsf (similar what you can see in the vboxadd*) scripts, see relevant part of the logs + some context:
DEBUG guest: Trying: redhat
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: cat /etc/redhat-release (sudo=false)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Exit status: 0
 INFO guest: Detected: redhat!
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: test -f /etc/centos-release (sudo=false)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Exit status: 0
 INFO subprocess: Starting process: ["/usr/local/bin/VBoxManage", "showvminfo", "d340c071-593a-4880-bd64-2e80211168d4", "--machinereadable"]
DEBUG subprocess: Command not in installer, not touching env vars.
 INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: name="mgt"
[stdout output removed for clarity]
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: VBoxService --version (sudo=true)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Exit status: 0

> DEBUG ssh: Re-using SSH connection.
>  INFO ssh: Execute: lsmod | grep vboxsf (sudo=true)
> DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
> DEBUG ssh: Exit status: 1

DEBUG vbguest-machine: Current states for VM 'mgt' are : guest_version=6.0.6 : host_version=6.0.6 : running=false
 INFO interface: warn: [mgt] GuestAdditions seems to be installed (6.0.6) correctly, but not running.
[mgt] GuestAdditions seems to be installed (6.0.6) correctly, but not running.

Forcing the module to be loaded at the boot seems to work fine as a workaround:
  config.vm.provision "shell", run: "always", inline: <<-WORKAROUND
    modprobe vboxsf || true
  WORKAROUND

This is still happening. Is there a permanent fix?

This is still an issue for me in Virtualbox 6.0.8. Keep in mind that the issue only seems to appear the second time you start the box (after the additions have already been installed), so you might be fooled into thinking it's solved if you just spin up a new box once on the new version of vbox.

This is still an issue for me in Virtualbox 6.0.8. Keep in mind that the issue only seems to appear the second time you start the box (after the additions have already been installed), so you might be fooled into thinking it's solved if you just spin up a new box once on the new version of vbox.

Seconded. I had to rollback to 6.0.4 because of this.

In case you are using vagrant, from ubuntu's apt repository, uninstall it and step away from the scenario immediately!
sudo apt-get purge vagrant
sudo apt-get clean
sudo apt-get autoremove
Now download vagrant's .deb by Hashicop from https://www.vagrantup.com/downloads.html install and the error would be gone IN CASE you installed vagrant from apt

Host: Windows 10 (1809)
Virtual Box: Version 6.0.8 r130520 (Qt5.6.2)
Vagrant 2.2.4
VBGuest: vagrant-vbguest (0.17.2, global)
Guest: bento/centos-7.6    (virtualbox, 201812.27.0)
I solved the above with:
echo vboxsf > /etc/modules-load.d/vboxsf.conf
I'm not sure if it needs added to the plugin, or if it's missing from the VBoxGuestAdditions-6.0.8 installer.

Running VirtualBox 6.0.8 here.   Updating vagrant-vbguest to version 0.18.0 fixed this issue for me.

I confirm, updating to vagrant-vbguest 0.18.0 fixes the issue on Vbox 6.0.8.
Just run once in the project:
vagrant plugin update vagrant-vbguest
You should see it updated to 0.18.0 and then you'll not see that error back! :) Thank you @openface !

I confirm, updating to vagrant-vbguest 0.18.0 fixes the issue on Vbox 6.0.8.
Just run once in the project:
vagrant plugin update vagrant-vbguest
You should see it updated to 0.18.0 and then you'll not see that error back! :) Thank you @openface !

This works for me, thanks!

I confirm, updating to vagrant-vbguest 0.18.0 fixes the issue on Vbox 6.0.8.
Just run once in the project:
vagrant plugin update vagrant-vbguest
You should see it updated to 0.18.0 and then you'll not see that error back! :) Thank you @openface !

Works for me too! Thanks!

Running VirtualBox 6.0.8 here. Updating vagrant-vbguest to version 0.18.0 fixed this issue for me.

This also works for me. Thank you.

I use virtualbox-guest-dkms 6.1.6-dfsg-1 in a Ubuntu focal64 image and on the Host: virtualbox                                                  6.0.14-dfsg-1
But I have the same problem here now


fix: use of all passed gas on reverts. add check to revert_reason test

https://github.com/Taraxa-project/taraxa-evm/pull/161

prnet cleaned-up successfully


Reduce PoolChunk's metadata size: change LongPriorityQueue to IntPriorityQueue

Motivation:
LongPriorityQueue[] is used by PoolChunk to store available run information of all page classes.
This information (i.e., handle) contains page offset,  page count, isUsed, isSubpage, and bitmapIdx of subpage.

Handle is inserted to LongPriorityQueue and LongLongHashMap when some memory is freed back to the chunk.
Handle is removed from LongPriorityQueue and LongLongHashMap when some memory is allocated.
One Handle can be split to two handles, and two continuous handles can be collapsed to one handle.

All the LongPriorityQueue operations are only related to page offset and page count. The low 32bit bitmapIdx is not used at all. So the high 32bit of handle is enough.
Modification:

Change LongPriorityQueue to IntPriorityQueue
Store high 32bit handle in IntPriorityQueue

Result:
PoolChunk's metadata is smaller.

@normanmaurer @chrisvest Thanks very much for your reviews.


Your yml file in sample is too old

Page : https://eksworkshop.com/advanced/310_servicemesh_with_istio/visualize/
Your file  : https://eksworkshop.com/advanced/310_servicemesh_with_istio/deploy.files/istio-telemetry.yaml
Correction :

Hello,
Thank you for the feedback, Istio has been updated #667


Added flake8 and black

Problem
Explain the problem you are fixing (add the link to the related issue(s), if any).
Solution
Explain the solution that has been implemented, and what has been changed.
Commandments

[ ] Write PEP8 compliant code.
[ ] Cover it with tests.
[ ] Update CHANGES.rst file to describe the changes, and quote according issue with GH-<issue_number>.
[ ] Pay attention to backward compatibility, or if it breaks it, explain why.
[ ] Update documentation (if relevant).

Is ruff not an beter option these days?


Label: Setting custom_colors/font_color breaks anti-aliasing

Godot version:
3.2.1 Stable
OS/device including version:
Mac OS Catalina 10.15.2
Issue description:
I have a label with a custom font. This is a Dynamic Font which has Filter enabled. The font is smooth in the editor. If I change the colour of the font in the editor (Custom Colors section), it remains smooth. When I perform the same action through code, the font loses its anti-aliasing causing harsh, pixelated edges.
Code: label.set("custom_colors/font_color", my_colour)
The same happens when I try the Modulate property of its CanvasItem class. And again, works fine in Editor, but not anymore during run-time.
Steps to reproduce:
Create a label with a custom font based on Dynamic Font.
Change the colour in code: label.set("custom_colors/font_color", my_colour)

This is probably because you set the font color to an overbright color. Color's values go from 0 to 1 to standard colors, not 0 to 255. (Use Color8 if you need to set colors with integers from 0 to 255.)

This is probably because you set the font color to an overbright color. Color's values go from 0 to 1 to standard colors, not 0 to 255. (Use Color8 if you need to set colors with integers from 0 to 255.)

Thank you for your quick reply. I was indeed setting colour values in the 0 to 255 range, never thinking about checking if that's allowed. I will close the issue. Thanks again!
<EMAIL_ADDRESS>


fix the import types example

Interesting, I guess we support a very lax syntax here because it does actually work

But let's fix this anyway, thanks


Which XML to add in the COMBINE archive?

Is there a systematic approach to selecting which XML file, where multiple are present, should be combined with the RDF metadata to produce the COMBINE archive? or is this manually determined for each BioModel?

Is this the code?
https://github.com/biosimulations/biomodels-qc/blob/639d644c0296427aea1dd56634144b735b471690/biomodels_qc/utils.py#L78-L108

Yes

I also have code already to apply this to this repo.

Is this code in the repository for me to use, or should I move to another task?

I intended to use that code; unless a couple days ago, that code was in this repository.

I can move to generating SED-ML files for models that do not have one (task #3), since all of the BioModels appear to have RDF files which suggests that metadata does not need to be scraped (task #4) .

Most of the remaining tasks, or at least their first steps, are easier for me to do. I already have code; I need to organize it into this repository.

There's code for generating SED-ML
The RDF in this repository encodes different metadata than what's on the BioModels website. I already have code for scraping the website and encoding that information into RDF.

Let me know if I can assist with anything else :)
Thank you,
Andrew

Hopefully I can put the code I have together this weekend. Then help would be great. I'd hate to have you repeat work I've already done, but haven't yet merged into this repo.

There's already a sedml file for the ones that were missing one.  Do we want a method for biosimulators-utils that does it? We could copy the code over.


ERROR:  missing FROM-clause entry for table "hi"

Hi,
when trying to execute this query SELECT * from prom_info.metric; using promscala with -install-timescaledb=false, i have the following error
ERROR:  missing FROM-clause entry for table "hi"
LIGNE 12 :                         hi.total_size as size,
                                   ^
REQUÊTE : SELECT
                        m.id,
                        m.metric_name,
                        m.table_name,
                        _prom_catalog.get_metric_retention_period(m.metric_name) as retention_period,
                        NULL::interval as chunk_interval,
                        ARRAY(
                            SELECT key
                            FROM _prom_catalog.label_key_position lkp
                            WHERE lkp.metric_name = m.metric_name
                            ORDER BY key) label_keys,
                        hi.total_size as size,
                        0.0 as compression_ratio,
                        NULL::bigint as total_chunks,
                        NULL::bigint as compressed_chunks
                    FROM _prom_catalog.metric m
CONTEXTE : PL/pgSQL function metric_view() line 4 at RETURN QUERY
SQL state: 42P01
Context: PL/pgSQL function metric_view() line 4 at RETURN QUERY

see https://github.com/timescale/promscale/blame/76518ed5ce1593223222638740bab141db814cc5/pkg/pgmodel/migrations/sql/idempotent/base.sql#L1226

This should get fixed by #297


Update readme with more explicit instructions

@mphillips12 Please take a look, review, and add comments for fixes since you've experienced the weak points.

@mphillips12 SUKOSHI

More updated version merged


Verbs Machine Layer: Add incorrectly removed rdma ack handling code

This code is exercised when sending large messages through the regular API (from LrtsSendFunc)

This one actually fixes the leak in NAMD.


Added Joe to developers

Open index.html
Verify Joe is there
Link goes to ....

Good stuff!

Be sure to sign up at https://hacktoberfest.digitalocean.com and do your four pull requests before the end of October to get your free t-shirt!


organized procedure into multiple sections

Fixes https://github.com/devfile/api/issues/253
Given that the GitHub issue was made months ago, not all the original points are still relevant. Therefore, I focused on reorganizing the procedure into subtasks.
See the Jira ticket: https://issues.redhat.com/browse/RHDEVDOCS-2566

@kim-tsao addressed your feedback in the commit, more reorg changes and addressed dev feedback please let me know what you think, thanks!


Submit issues through Hex

If anyone finds an issue, then they will be able to submit bug reports and feature requests through the bot itself. Here is an example:
<+Dead-i> hex a issue The PING command appears to have broken.
<@Hex> The issue was posted to GitHub.

under which account would the bot create issues?

Wrong button!
The GitHub account of the server admin.

so mine? XD
How would I tell it to submit an issue?

http://developer.github.com/v3/issues/


Playground share link contains angle brackets

Search Terms: playground share brackets
Code
type GenericType<T> = T;

Expected behavior:
< character is URL encoded in the share link.
Actual behavior:
< character is not URL encoded in the share link.
Playground Link: https://www.typescriptlang.org/play/#src=type GenericType%20%3D%20T%3B%0D%0A
The link above demonstrates the behavior. Github is not able to properly display the link due to the angle brackets. URL encoding the < character with %3C would resolve this issue.

The link actually eats the <T> entirely, it's not in your text (even as text), though it does cut off the hyperlinking.
For others, the link is https://www.typescriptlang.org/play/#src=type%20GenericType%3CT%3E%20%3D%20T%3B%0D%0A

it's not in your text (even as text)

Wow, I did not even notice that. It's GitHubs behavior on markdown. When I "edit" my post I can still see the <T> in the link.

This is fixed with the new playground 👍


vike-react-query: Linter error when using useSuspenseQuery() inside withCallback()

Description
When following the instructions in the vike-react-query README on how to use withCallback(), ESLint's react-hooks/recommended plugin (understandably) complains:
React Hook "useSuspenseQuery" cannot be called inside a callback.
React Hooks must be called in a React function component or a custom React Hook function

Of course, adding /* eslint react-hooks/rules-of-hooks: 0 */  on top of the file will mute the linter here, but this is not an ideal solution.
Thank you for your great work on Vike!

Up for a PR?

Okay, I just realized, the linter can also be satisfied by outsourcing the inline component to a separate function:
const MovieWithoutFallback = ({ id }: { id: string }) => {
    const result = useSuspenseQuery({
        queryKey: ['movie', id],
        queryFn: () =>
            fetch(`https://brillout.github.io/star-wars/api/films/${id}.json`)
                .then((res) => res.json())
    })

    const { title } = result.data

    return (

            Title: {title}

    )
};

export const Movie = withFallback(
    MovieWithoutFallback,
    ({ id }) =>
Loading movie {id}
,
    // The props `retry` and `error` are provided by vike-react-query
    // Other props, such as `code`, are provied by the parent component
    ({ id, retry, error }) => (

            Failed to load movie {id}
            <button onClick={() => retry()}>Retry</button>

    )
)

So this is indeed rather an ESLint-related issue, since it does not properly identify the inline component as a valid component but rather as a "callback".
I don't know, if it would make sense to add a little note about this in the Readme, but I guess this is actually out of vike-react-query's scope...

Hm, not sure, it does seem to be a user-land thing that is entirely independent from vike-react-query. Could happen with another library right?

@brillout yes, totally agree now. But thanks for your quick response!
Sorry for bringing that up in the first place.


Adding tags to GitHub repo page

I thought of maybe adding some tags to the repository for easier discoverability.
Something like #swift, #instagram, #api, #cocoapods or sth along these lines… idk.
What do you think? @TheM4hd1
And I would also consider moving the url to the README. It feels misplaced in the description, imho. But it's just an opinion though.

Done.
if you suggest more topics let me know.


Unable to create .dotnet-interactive files in arbitrary places in VS Code Insiders

Describe the bug
Please provide as much information as you can.
Please complete the following:
Which version of .NET Interactive are you using? There are a few ways to find this out:

In a notebook, run the #!about magic command.

At the command line, run dotnet interactive --version.
1.0.116805+e82617b33d4652ef09b36a1d595ac15de434a939

In VS Code Insider details
Version: 1.46.0-insider (user setup)
Commit:<PHONE_NUMBER>496504e0677ffcf2a46d47ad9130f5
Date: 2020-05-15T05:30:56.857Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

OS

[x] Windows 10
[ ] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[ ] Edge
[ ] Firefox
[ ] Safari

Frontend

[ ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[x] Visual Studio Code
[ ] Other (please specify)

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

When trying to create a .dotnet-interactive file in arbitrary place in VS Code Insiders I get this the error above after, launching VS Code Insiders from the terminal using this command code-insiders --enable-proposed-api ms-dotnettools.dotnet-interactive-vscode
Workaround

I created a new folder  notebooks and navigate to it
Launch VS Code Insiders like this code-insiders --enable-proposed-api ms-dotnettools.dotnet-interactive-vscode .  With a .

Inside notebooks created  foo.dotnet-interactive  then it worked

I believe this has been resolved. I've been opening files from anywhere and it works.

I will go a head and close the issue.


WorkerExecutor should limit the number of active work items

Currently DefaultWorkerExecutor creates an ExecutorService with an unbound thread pool to handle work requests.  This works fine for most scenarios, but if the number of work items is extremely large, this can consume a lot of resources (and potentially exhaust them).  We should move this to a queue-based approach similar to DefaultBuildOperationQueue where the number of active threads is limited.  We should take care to deal with contention between worker leases and avoid a scenario where the active thread pool is full of requests that can't get a worker lease.
Expected Behavior
WorkerExecutor limits the number of active threads when processing work items.
Current Behavior
WorkerExecutor creates as many threads as outstanding work items
Context
When submitting extremely large numbers of work items, lots of resources can be consumed (or exhausted)
Steps to Reproduce (for bugs)
Submit a lot of items to the WorkerExecutorService

Are we still going to make it in 4.7RC1? If not, please remove the milestone.

Yes, I'm trying to finish this today

@big-guy Is the intent to do this today? Please let the team know if we'll need to delay the RC for it.

Sorry, I commented on the PR, but didn't realize this issue also had a milestone set.  No, we cut the release branch before we could get the PR reviewed and put away.  This will have to go into 4.8.

This has been fixed.


storage: PutBucketACLRule currently broken by GCS Storage API

Leaving this issue open until we get a resolution from the GCS Storage team.

Just a heads up we received an update over here: https://github.com/GoogleCloudPlatform/gcloud-node/issues/716#issuecomment-125346513

https://code-review.googlesource.com/#/c/3370

The Google Cloud Storage team has fixed the issue on the backend.
Re-instituting test.


Make the strongbox port configurable from etc/conf/strongbox.xml

This is configurable via the etc/conf/strongbox.xml file. However, at the moment, this configuration property is not taken into consideration when starting Strongbox via the strongbox-assembly/strongbox-distribution. This should be controlled when Jetty is started viat the JettyLauncher class.
The best way to test the strongbox-assembly/strongbox-distribution, is to run the build-and-start script.

Additionally, it'd be really cool to be able to configure jetty-maven-plugin in the strongbox/strongbox-web-core to use value provided in etc/conf/strongbox.xml.

We should not proceed with this task before #755.

@fuss86 / @adavid9  @ptirador : Is this now obsolete with the migration to Spring Boot and YAML-based configuration? Is it configurable now? If not, perhaps we should update the description...?

@carlspring in my opinion we have proper property server.port in application.yaml but we should get rid of configuration.port from strongbox.yaml

I agree. This should be a simple task now. This should be configurable through the REST API and UI.
@adavid9 : When implementing the Spring Boot support did you do any work related to this?

@carlspring Hi, I am not sure about which issue you're talking about if you could remind me it, but I am totally agree with @fuss86 If we use the server.port in the application.yaml the configuration.port is useless.

The configuration controller will need to be changed to use the correct property now and we should drop the old property. This might affect the strongbox-web-integration-tests, although it's highly unlikely.
@adavid9 : Would you like to look into this?

@carlspring Yes I can do it.

Great! Thanks! :)

@carlspring, currently Spring Boot uses server.port from application.yaml which is embedded in the jar file, you can't make it

configurable through the REST API and UI.

unless we will decide to use external application.yaml file or read the port from other external file where we are allowed to write. You can't write to the configuration file embedded in jar package.

https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html

@fuss86 What do you propose, should we leave it for now until we will decide to use the external application.yaml file?

@strongbox/core-developers , @adavid9 , @ptirador ,
I think that we need to re-work things, so that:

[ ] When we package the strongbox-distribution, it's in such a way that the application.yaml file ends up in the etc/conf directory inside the distribution
[ ] The StrongboxConfigurationController (?) can modify this value.
[ ] This is configurable via the UI.
[ ] Clearly, changing this value through the UI will mean that the service will need to be restarted and when the user does this, they should be prompter whether, or not they'd like to restart now.

What do you guys think about this?

This task will open up other issues like the environment variables need to be taken into account so that they take precedence over the configuration files.
We should probably come back to this task later.


Update runtime to .NET 5

Latest is better, I guess.
Also fixed a typo in the workspacer.Watcher namespace that was left unnoticed for a long time.

LGTM.

Improved is improved!


Release 0.2.0-rc1

We have this milestone https://github.com/poldracklab/fmriprep/milestone/8 frozen in time. Let's update it with the issues we really want to get done for this release.
I'm also updating the deadline for that milestone.

Milestones are all rearranged and ready to rock.


Updated my data

Hacktoberfest! 🎊🎈
🎉 Have you read the Contributing Guidelines? 🤔
Yes
📝 Description
Updated my data in data.json file
Fixes #215  🔧

✅ Checklist

[x] I've read the contribution guidelines. 📚
[x] I've checked the issue list before deciding what to submit. 🔍
[x] I've edited the README.md and linked to my code. 📄

Hi there!
Although this repo is not part of Hacktoberfest 2024, we have some great alternatives for you. Welcome to SkillShow, a repository focused on skill enhancement!
Guidelines:

Please adhere to the existing guidelines.
No additional rules, thanks!
Check it out here: SkillShow.

Note: Start by creating an issue. Once it’s assigned to you, feel free to open a pull request (PR). Directly opening a PR will lead to an invalid label.
Looking forward to your contributions!


mouseenter/lease events should be tested

http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-mouseenter

+1

I'm not going to add a test for this, at this time. Closing this issue.


Packaged App Crashes on Start

The app I have built works and runs correctly in developer via npm start. But when I try to package the app, it packages correctly with no errors. But when the packaged app is run, the app's window open's and then immediately closes.

Platform: Windows 10 x64
Target Platform: Windows 10 x64
Repository: devRant.io
Packager Version: 7.0.4
Electron Version: 1.2.2
CLI SCRIPT: electron-packager . --overwrite --prune --out=../build --ignore='node_modules' --platform=win32 --arch=x64 --icon=../icon/favicon.ico --version-string.FileDescription=devRant.io
Error Messages: None(No console available to view).

I see you're also packaging for OSX. Does that work?

Yes, the OSX packages with no error and the app runs without problems. It is just win32 packages like this

Is there any output if you try running the .exe in a console?

No. I run the executable and the the window opens, closes and the console just moved down to the next line. No error messages or any output.

I can't debug this at the moment, but I would suggest putting console.log statements all over main.js to see what code did or did not get run.

Okay, I will run some tests and see what does and doesn't run.

[UPDATE] I tested packaging the app with another main.js file (Stock main.js file from Electron quick start repo) and the issue still remains.
Assumtion now is that there is some error when packaging.

Could you try moving your icon so that it's in the same folder as main.js? Also, I'm not sure the icon parameter of BrowserWindow accepts a .ico file.

Okay it appears me assigning it the .ico file in my main/js appeared to be the issue.
I've changed it to be .png instead and the app now runs perfectly.
Thanks.