text:
new test added

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Can you explain why you added this new test?  What does it accomplish that the other tests were missing?

I added since reader can get clear idea of possible inputs . I gave unique
input in both sets without common fields.
On Tue, Oct 23, 2018 at 12:32 PM Randell Dawson notifications@github.com
wrote:

Can you explain why you added this new test? What does it accomplish that
the other tests were missing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/pull/26704#issuecomment-432118675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ3biK-6MXCTZarx0dCOaXybxkhRblHjks5unr7zgaJpZM4X0z4g
.

--
-with regards
Karthik.B.S

@ezioda004 , @Manish-Giri  - What do think?

@virtplay @RandellDawson I'm not sure if this is required. The challenge description already has an example for unique elements:

For every additional symmetric difference you take (say on a set D = {2, 3}), you should get the set with elements which are in either of the two the sets but not both (C △ D = {1, 4} △ {2, 3} = {1, 2, 3, 4})

authors: RandellDawson ezioda004 virtplay


text:
Update grammar

Change code in line 26, it was written 'Hybrid app take least' I have updated to "Hybrid app take the least"

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

source: gharchive/pull-request

authors: Manuglen RandellDawson

repo: freeCodeCamp/freeCodeCamp

license_type: permissive

license_source: github-api


text:
Add the improved Russian translation to this challenge

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Thanks and congratulations on your first accepted submission!

authors: RandellDawson dodzon lynxlynxlynx


text:
Updated index.md with terms description

Added description for a Device Independent Pixel

[ x ] I have read freeCodeCamp's contribution guidelines.
[ x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x ] My pull request targets the master branch of freeCodeCamp.
[ x ] None of my changes are plagiarized from another source without proper attribution.
[ x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


text:
fix(client): replace react-responsive with media queries for menu

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

This is related to #35931, it specifically fixes the problem during page load on small screens. Namely that the menu briefly displays as expanded when the page is reloaded:

It touches the code for the menu button, removing the wrapping Media element, so it could affect that part of the issue.  However, that would need to be verified by someone with a Mac.
Finally, I was not sure if the nav menu should appear on the guide pages.  I opted not to display it at all, to be consistent with smaller screens and how it currently works in production.  That's part of why this is a draft PR.

Thank you for looking into this @ojeytonwilliams.
On my side, your solution does display the menu on guides as expected. (refer to the current state of .rocks reference for the full functionality)
However, the rest of the nav buttons are not displayed on larger screens on the guides

@ahmadabdolsaheb I should have checked for that, thanks for catching it!  It should look fine at all screen sizes now.  It should also behave properly when the page is reloaded, even when it has been built.
One thing that tripped me up was that the wrapPageElement appearing in gatsby-ssr and gatsby-browser wasn't quite the same, but it seems like it should be.  Is that deliberate, or would it be worth DRYing them out a little?

@ojeytonwilliams They only difference is having disableMenuButtonBehavior={true} on one.
I think both disableMenuButtonBehavior={true} and OnGuide={true} are there to accomplish the same goal. so feel free to tighten things up.
Additionally, I believe the props could be passed down from the wrapPageElement of either gatsby-ssr or gatsby-browser. So ideally we could get rid of one of them.
@ValeraS, since you have more context. what to you think of drying one of thewrapPageElements?

@ahmadabdolsaheb Good point about disableMenuButtonBehavior and onGuide.  I've simplified things a bit and removed what seems like unnecessary duplication.  Let me know if this is okay.
Finally, I added a comment about what disableMenuButtonBehaviour does, since that confused me a little the first time I looked at this.

@ojeytonwilliams thanks for the comment.
Also, the nav items don't show on large screens.

@ahmadabdolsaheb I wasn't sure if they were supposed to be there since they're inaccessible on small screens, so I erred on the side of consistency.  Anyway, thanks for clarifying - I'll fix that now.

Just to clarify, I was referring to the navigation items on the guide.

@ahmadabdolsaheb This should be a bit better, I tried to match the behaviour on rocks.  It still has a version of the bug I mentioned in #35952, but this should display correctly otherwise.
In future, I'll create some more gifs/pictures to clarify things before I get to work, as I'm terrible at describing UI changes without them!

Is there anyway I could help? @ojeytonwilliams

@ahmadabdolsaheb  I fixed the issue in #35952 with my last commit, but completely forgot to mention it - sorry about that!  And, definitely, if you have time to give this another look, that would be much appreciated.

@ojeytonwilliams for some reason non of the CI builds have triggered with any of your commits. Can you try and rebase this off of master and force push? Thanks.

@raisedadead A quick google turned up this: https://travis-ci.community/t/draft-pull-requests-not-being-built/2434/12 I guess this is related.

Thanks for sharing that topic. Although it was worth the rebase anyways 😅 ! Thanks for working on this. I will leave this for a QA and merge from the team.

Adding @ValeraS for additional review because this touched Gatsby's critical files.

@ValeraS Thanks for the review.  I tested and committed all your suggested changes, they all look good to me!
Isn't there always going to be a difference between what the server renders and what Media renders?  The problem is that the server doesn't know what size your page is, so it can't always match what Media does.
Finally, should I change the Gatsby configuration now or is it better to just fix the merge conflict later?

One possible solution would be not to render server-side parts that depend on Media.
For example:
<Media maxWidth={mediaBreakpoint} onChange={this.handleMediaChange}>
  <MenuButton />
  {displayMenu && !disableMenuButtonBehavior && <MenuLinks />}
</Media>
<Media minWidth={mediaBreakpoint + 1}>
  <MenuLinks />
</Media>

By default, media queries are resolved to false, and children are not rendered.

I tried this change, but ran into similar problems again.  Basically, whatever I do, the first client rendering makes menus appear or disappear.  It works well in development mode, but when you build it, the initial page load does not have the menus or the buttons.
For large windows it looks like this:

For smaller ones, it looks like this:

I created a branch for this, so you can see the code, without mixing it with the rest.
Also, the refactor you suggested made a lot of sense to me, so I put that in here.  I think that should be in whatever fix we end up with.

Of cause, this is how it works. On the first load, it shows static SSR page and, after load js bundle, hydrates with client-side render. After this, it works as a client app and does not use static pages from the server. So we get such behavior only on the load/reload whole page.

Yeah, I just thought it would look better if that never happened at all.

@raisedadead @ahmadabdolsaheb @ojeytonwilliams Let's do not change menu behavior on guide and use another control for side navigation. Something like this:

@ValeraS, it makes sense. we discussed this in #35249, it was differed to the next iteration due to the feature freeze. Also we have plans to move away from icons to words throughout our services.
To expand on the benefits of your suggestion:

a secondary nav for guide and  forum will become necessary as we ship our universal nav across services.
it would reduce redux wiring.
it would be less confusing to users because the same bottom does two different things on different pages at the moment.

That being said, it might be better to stick with the current functionality until we find a solution for a  secondary navigation across our services in the next iteration.
I defer the decision to @raisedadead on this.

Yes, that is correct. @ValeraS you have a valid point. But for now, we should get this in and overhaul the nav completely in the planned redesign.
If you are fine with the current change in this PR, let merge it. Thanks once again for the QA.

@ojeytonwilliams I don't like that the header contains logic specific for the guide. One more approach: we can pass a navigation block through props. And make two blocks, one for the guide and one for other layouts. But should we do it, if we plan to change the behavior of the guide?

@ValeraS I take your point that it will require a little bit more work, overall.  However, I think it's worth it to deal with these two bugs and the refactoring will make the redesign easier (or at least not harder!) to implement.
I'll take a look at it and let you know what I come up with.

@ValeraS it turned out to be far more involved and messy than I thought it would be.  I do agree that having the logic in the header is not good.  However, I've changed my mind and I now think trying to fix that creates more problems than it solves.
So, to answer your question

But should we do it, if we plan to change the behavior of the guide?

I no longer think so, but I still think it's worth fixing the two bugs for now.

@ValeraS I took at look at your changes and they seem good.  However, I thought we could go further and move the nav menu logic out of the Header and put it in gatsby-browser i.e. where the decision is actually made.  Also, could you explain why you changed from just passing menuButtonRef to using forwardRef?
Anyway, regardless, this LGTM.  Let me know if you're okay with my changes.

@ValeraS   I understand your reasoning now and I'm happy with the changes you suggested.  However, I'm about to leave and I'll be travelling for about a week. I'm not sure how much time I'll have to implement them before I get back.  If you have time to make them yourself, please do, otherwise I'll do them as soon as I can.

@ValeraS Thanks for sorting that out!

authors: ValeraS ahmadabdolsaheb ojeytonwilliams raisedadead


text:
Master

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[ ] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

sorry


text:
Clarify instructions about .test() method

The current instructions led me toward a solution that fails the test but that seems like it should pass. My solution failed because the test looks at the value of a variable called return, not directly at the return value of myRegex.test(myString). The instructions, however, just tell you to use the .test() method, and the directions say "your result should return true."
But if the last line of your code is simply myRegex.test(myString), that expression does return true. And that code is equivalent to what is shown in the instructions as returning true. So really, the test is not asking for a "result" to "return true"; "result" is not a function or a method, it is a variable. The test is really asking for "result" to equal true.
The simplest way to eliminate any confusion is to clarify that the return value of the method should be assigned to the variable result.
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Thanks @moT01. I'm afraid that I'm not really sure how to respond. I am proposing a minor change to correct something that I personally found confusing. My proposed change is accurate, so it's hard for me to see what harm it would do to accept it.
As for your instruction that I should open an issue before proposing a PR, if you're telling me that is the custom, I will keep it in mind. But if it's in the contributor guidelines, I didn't see it (it's not in the section on PRs). If the admins really want folks to open an issue before proposing a PR, they might want to revise the guidelines accordingly.

Heya @bhagerty~! First, thank you for your interest in contributing to freeCodeCamp, and congratulations on opening your first pull request! 🥳
Now on to the topics at hand. You are correct that the section on PRs in the contributing docs does not mention the issue->PR workflow, but there is this text in the Getting Started section:

I found a typo, should I report an issue before I can make a pull request?
For typos and other wording changes, you can directly open pull requests without creating an issue first. Issues are more for discussing larger problems associated with code or structural aspects of the curriculum.
However, please mention details, context etc. in the pull request's description area to help us understand and review your contribution even for minor changes.

This PR is technically a wording change, but it is a wording change that also affects a test.. So it could go either way. Ultimately, the purpose of creating an issue first is to allow the community and the freeCodeCamp dev team to triage the issue and discuss the best approach to improve the challenge in question. This was the reason for @moT01's recommendation, I believe.
In this case, I would suggest that we not change the test text at all, but instead change the test string. The challenge seed has line 3 marked as change this line, so campers should only be modifying that line. Rather than check if result === true, what if we change the test to assert myRegex.test(myString) === true?

Thanks @nhcarrigan. You don't sound harsh. I think that what I proposed is in fact just a "wording change," because if you accepted my change, you wouldn't need to change the test. So in that sense, my proposal doesn't affect the test. That's exactly why I proposed it: as a minimal solution that would require changing only the explanatory text, not any of the code.
Having said that, I agree with the change that you propose. As an added benefit, your change would mean that the correct solution would more closely match the example in the explanation (the final line of which is just testRegex.test(testStr);, and doesn't involve setting any result variable). So I think that your change is the best solution.

Rather than check if result === true, what if we change the test to assert myRegex.test(myString) === true?

I don't think that would be the way to go. The seed code sets the regex and myString values I believe, so that would pass unless the user changes something - pretty sure anyway.

authors: bhagerty moT01 nhcarrigan


text:
fix(curriculum): typos in curriculum

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #47689

Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.

I have reopened your PR because it looks like you are working on one of the issues.
Please make sure to include the issue number you are working on so we know what this PR is for.
closes issue-number-goes-here

Thank you

Done! Fixed @jdwilkin4

Hey @jdwilkin4 , i also replaced new links with old links as mentioned in one issue
so i need to create another pull request?

Please do not combine issues in one PR.
Each issue should have its own PR.

Hey @codingis4noobs2
This PR seems to make similar changes as the existing PR <#47690>. As such, we are going to close this as duplicate.
If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened.
Thanks again! 😊

If you have any questions, feel free to ask questions on the 'Contributors' category on our forum or the contributors chat room.


text:
feat: integrate The Odin Project

Checklist:

[] I have read freeCodeCamp's contribution guidelines.
[] My pull request has a descriptive title (not a vague title like Update index.md)
[] My pull request targets the main branch of freeCodeCamp.
[] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

I am not sure of the context behind this change, but let us keep in mind to change the language used in these lessons (e.g. "you" instead of "we")
if draft PRs were not meant to be reviewed, then they should not show up in my notification feed 😅

Hey Shaun,
We are adding The Odin Project into the freeCodeCamp Curriculum, and make it more interactive.
Weird that it shows up on your notification feed.  Anyway this is far way from done.

Hey this part is ready for review,
If you have a ton of feedback please contact me through chat and we can schedule a meeting.
Of course this is not yet ready for the public but the first part is ready.

Thanks @naomi-lgbt,
The main reason why I did multiple challenges with the same text is that they have different questions with the same subject. I do not expect them to read it again.
It Is clear that the title has changed.  Also, you did not read my comment :)

We are officially on Node.js 18 now. We have changed the merge requirements accordingly.
You will need to rebase this PR against the main branch OR Click the "Update branch" button to get the new checks going.
Thanks for your contribution.

Like Naomi mentioned, there is a lot of repeated text across multiple challenges.
I can see why you did this, though ideally we'd be able to break up the descriptions more across multiple files like you did with the "Working with Text" challenges.
Or it'd be great if there was a way to have several multiple choice questions per challenge.
The repeated text could be difficult to handle if we have to make changes across multiple files. And it could be a burden on the translation team to translate / approve the same text for different challenges where the main difference is the multiple choice question at the very end.

Thanks for the review @moT01, I will try and resolve this issues in the next pr. Your review is appreciated.


text:
may be it can be good to add theme toggle at the toolbar

theme toggle which switches form light to dark themes

i checked the link at README  bottom - the theme change is not working (may be it good to reopen this issue)

source: gharchive/issue

repo: freeCodeCamp/ui


text:
Pandas have deprecated automatic dtype conversion

See here:
Version: 0+untagged.1.gd4073b2
checkCPU: Linux-6.2.0-10[19](https://github.com/freejstone/Percolator-RESET/actions/runs/7822518380/job/21341719050#step:11:20)-azure-x86_64-with-glibc2.35
[20](https://github.com/freejstone/Percolator-RESET/actions/runs/7822518380/job/21341719050#step:11:21)24-02-07 23:28:27.348728
Command used: /home/runner/work/Percolator-RESET/Percolator-RESET/percolator_RESET/__main__.py --overwrite T --get_psms T --get_all_psms T --initial_dir TailorScore --seed 1 ./data/test1/narrow_50.make-pin.pin ./data/test1/tide-index.peptides.txt
Successfully read in arguments.
Using seed: 1.
Reading in search file(s).
/home/runner/work/Percolator-RESET/Percolator-RESET/percolator_RESET/utility_functions.py:159: FutureWarning: errors='ignore' is deprecated and will raise in a future version. Use to_numeric without passing `errors` and catch exceptions explicitly instead
  yield psms.apply(pd.to_numeric, errors="ignore")
Reading in peptide list(s).
Taking top 1 PSMs.
Doing peptide-stem level competition.
/home/runner/work/Percolator-RESET/Percolator-RESET/percolator_RESET/percolator_functions.py:341: FutureWarning: Setting an item of incompatible dtype is deprecated and will raise in a future error of pandas. Value '[ 1.41982295  1.73377309  2.36167338 ... -1.0917782   0.94889773
 -1.0917782 ]' has dtype incompatible with int64, please explicitly cast to a compatible dtype first.
  df_all.loc[:, ~(df_all.columns.isin(['SpecId', 'Label', 'filename', 'fileindx', 'ScanNr', 'Peptide', 'Proteins', 'trained']))] = scale.fit_transform(
/home/runner/work/Percolator-RESET/Percolator-RESET/percolator_RESET/percolator_functions.py:341: FutureWarning: Setting an item of incompatible dtype is deprecated and will raise in a future error of pandas. Value '[-1.05119595 -1.05119595 -1.05119595 ...  0.95129742 -1.05119595
  0.95129742]' has dtype incompatible with int64, please explicitly cast to a compatible dtype first.
  df_all.loc[:, ~(df_all.columns.isin(['SpecId', 'Label', 'filename', 'fileindx', 'ScanNr', 'Peptide', 'Proteins', 'trained']))] = scale.fit_transform(
/home/runner/work/Percolator-RESET/Percolator-RESET/percolator_RESET/percolator_functions.py:341: FutureWarning: Setting an item of incompatible dtype is deprecated and will raise in a future error of pandas. Value '[ 1.05119595  1.05119595  1.05119595 ... -0.95129742  1.05119595
 -0.95129742]' has dtype incompatible with int64, please explicitly cast to a compatible dtype first.
  df_all.loc[:, ~(df_all.columns.isin(['SpecId', 'Label', 'filename', 'fileindx', 'ScanNr', 'Peptide', 'Proteins', 'trained']))] = scale.fit_transform(
/home/runner/work/Percolator-RESET/Percolator-RESET/percolator_RESET/percolator_functions.py:341: FutureWarning: Setting an item of incompatible dtype is deprecated and will raise in a future error of pandas. Value '[-0.19239537 -0.19239537 -0.19239537 ... -0.19239537 -0.19239537
 -0.19239537]' has dtype incompatible with int64, please explicitly cast to a compatible dtype first.
  df_all.loc[:, ~(df_all.columns.isin(['SpecId', 'Label', 'filename', 'fileindx', 'ScanNr', 'Peptide', 'Proteins', 'trained']))] = scale.fit_transform(
Dropping the features from training: enzInt, ExpMass, CalcMass.
Conducting iterative SVM.
iteration: 0.
Observed power: 6427.
Mean cross-validation power: 1993.0.
Std cross-validation power: 12.256517540566824.
iteration: 1.
Observed power: 6482.
Mean cross-validation power: 2042.0.
Std cross-validation power: 33.02860712910686.
iteration: 2.
Observed power: 6549.
Mean cross-validation power: 2073.6666666666665.
Std cross-validation power: 62.686167178697055.
iteration: 3.
Observed power: 6685.
Mean cross-validation power: [21](https://github.com/freejstone/Percolator-RESET/actions/runs/7822518380/job/21341719050#step:11:22)06.3333333333335.
Std cross-validation power: 46.676189504571454.
iteration: 4.
Observed power: 6690.
Mean cross-validation power: 2147.0.
Std cross-validation power: 53.54333654983493.
Final SVM feature coefficients:
deltLCn        0.678358
deltCn         0.719712
XCorr          1.500704
TailorScore    0.5[24](https://github.com/freejstone/Percolator-RESET/actions/runs/7822518380/job/21341719050#step:11:25)495
PepLen        -0.[28](https://github.com/freejstone/Percolator-RESET/actions/runs/7822518380/job/21341719050#step:11:29)9809
Charge2        0.076562
Charge3       -0.076562
lnNumDSP       0.2086[34](https://github.com/freejstone/Percolator-RESET/actions/runs/7822518380/job/21341719050#step:11:35)
dM             0.1475[37](https://github.com/freejstone/Percolator-RESET/actions/runs/7822518380/job/21341719050#step:11:38)
absdM         -0.621006
intercept     -1.6086[39](https://github.com/freejstone/Percolator-RESET/actions/runs/7822518380/job/21341719050#step:11:40)
Features that are constant are dropped.
Reporting all PSMs within each mass-cluster associated to a discovered peptide.

Lots of changes to Pandas it seems. This has been fixed in the following commits:
https://github.com/freejstone/Percolator-RESET/commit/9d71242fac88160174d26eeaf9af6c57628cfd5c
https://github.com/freejstone/Percolator-RESET/commit/d82c31b0bc3f7d9aeefb33aa6f0050d2882cace2

repo: freejstone/Percolator-RESET


text:
Request doesn't works

Hi,
i followed the instructions for this package. But when i execute a simple request i get this message:
"Error refreshing the OAuth2 token, message: '{
"error" : "invalid_grant"
}'"
What mean ?

I think you forgot to include ga: before your key!

Ok, i'll try again. Thanks

authors: MatthiasDeWinter Mdpproduction

repo: freekmurze/laravel-analytics

license: MIT


text:
Fixed parenthesis, added full_span function and test

I created a new full_span() function that takes into account the whole citation (including plaintiff, defendant, and post_citation).
We still have an issue when plaintiff name is made of several words, or when the extra attribute contains too much text, but this can be solved independently.
Have a good weekend !

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

Also, don't forget to sign our license, please.
Thanks for this neat feature.

@mlissner That being said I think this is actually a great addition that I have wanted before in use.

About the license, should I personally sign it, or should the company I am working at do it ?

Fyi this is a list of examples and their spans (full span in red, regular span in blue)
span_examples.zip

About the license, should I personally sign it, or should the company I am working at do it ?

I think you should sign it, but when you do you're saying that if your work owns the IP, you have the ability to assign that to us, and are doing so.

Sorry, I won't get to this today, but it's on my list for tomorrow. I got bogged down in a major architecture issue, but tomorrow should be better.

I signed the contributor license and sent it at legal@free.law, I also pushed a new commit because I realized that stopwords such as 'citing' were included in the span

Cool. I cleaned up a couple things, but this looks good to me on the whole. I'm going to merge and hopefully that'll run our benchmark suite, which runs eyecite across a big collection of data (I forget how much). If that runs smoothly, I think we'll be in business. I do wish I knew how span was getting set though!

@overmode - I want to like your idea of using regexes, but I want to run a few things by you.  In the Pa Super example, our citation string in Courts-db is Pa. Super. Ct.  How would we handle the Ct. citation.  I understand how we do the whitespace but we cant just allow a wild card to handle the ct.

@overmode, just a quick update to let you know that 2.5.1 is now released and should have this functionality baked in. Sorry for the delay. Our automated deploy failed and I didn't catch it.

authors: CLAassistant flooie mlissner overmode

repo: freelawproject/eyecite


text:
[RFE] Have a setting to show all token codes right away without an extra tap

Reported by dpal on 21 May 2014 18:40 UTC
Comes from FreeOTP feedback.

Comment by npmccallum on 28 Jul 2014 18:05 UTC
This is a very bad idea from both the security perspective and from the battery drain perspective. I don't think the benefit is worth the added complexity.

Comment by vinaur on 28 Aug 2014 00:11 UTC
I just want to understand the security considerations here for not providing this option. The concern is that someone who already knows my password for some service is going to look over my shoulder, see a TOTP code for the service that I'm not currently interested in (since the one I'm interested in I will reveal anyway), and will be able to authenticate within 1 minute (typical 30 second timestep, plus an additional timestep typically allowed by the authentication server)? I can conceive a scenario where this could be a concern, but I can also confidently say that this would not be a concern for me (and I'm sure that's the case for a lot of other users).
I also don't understand the battery drain concern, since the TOTP generation should only happen while the app is active.

Modified by vinaur on 28 Aug 2014 00:17 UTC

repo: freeotp/freeotp-ios


text:
Easier way to identify what just deployed

In release dialog:

make it way more obvious that you're looking at the same release (e.g. by background color).
Also disable deploy buttons if this version is already deployed.
Display what was previously deployed. Ideally show the whole history of deployments on a dedicated page. E.g. on the release history page, show when each release was deployed. (check if this is redundant with the commit history, which wasn't rolled out yet at this point)

Suggested by @matthiasBender

The first two points are pretty much done.

repo: freiheit-com/kuberpult


text:
Generated NIF check

Hi Nilesh, it would be great if you could take a look at the NIF generated by the e-Internationalization converter. Please, let me know if you notice something wrong.
NIF File
@prefix xsd:   <http://www.w3.org/2001/XMLSchema#> .
@prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> .
@prefix nif:   <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#> .
@prefix dc:    <http://purl.org/dc/elements/1.1/> .

<http://freme-project.eu/#char=0,33>
        a               nif:RFC5147String , nif:Context , nif:String ;
        nif:beginIndex  "0"^^xsd:nonNegativeInteger ;
        nif:endIndex    "33"^^xsd:nonNegativeInteger ;
        nif:isString    "Hello World! What a beatiful day!"@en .

<http://freme-project.eu/#char=13,33>
        a                     nif:Phrase , nif:RFC5147String , nif:String ;
        nif:ReferenceContext  "http://freme-project.eu/#char=0,33" ;
        nif:anchorOf          "What a beatiful day!"@en ;
        nif:beginIndex        "13"^^xsd:nonNegativeInteger ;
        nif:endIndex          "33"^^xsd:nonNegativeInteger ;
        dc:identifier         "2" ;
        itsrdf:target         "Che bella giornata!"@it .

<http://freme-project.eu/#char=0,12>
        a                     nif:Phrase , nif:RFC5147String , nif:String ;
        nif:ReferenceContext  "http://freme-project.eu/#char=0,33" ;
        nif:anchorOf          "Hello World!"@en ;
        nif:beginIndex        "0"^^xsd:nonNegativeInteger ;
        nif:endIndex          "12"^^xsd:nonNegativeInteger ;
        dc:identifier         "1" ;
        itsrdf:target         "Ciao Mondo!"@it .

Just in case you need it... Original XLIFF file
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2">
<file source-language="en" target-language="it" datatype="x-test" original="file.ext">
<body>
<trans-unit id="1">
<source>Hello World!</source>
<target>Ciao Mondo!</target>
</trans-unit>
<trans-unit id="2">
<source>What a beatiful day!</source>
<target>Che bella giornata!</target>
</trans-unit>
</body>
</file>
</xliff>

@borriellom  Can we close this issue? Or we ask someone else for help?

do you need help? I assumed this is already solved...

Yes, it's solved. Thank you.  I'm closing it right now.

authors: borriellom jnehring m1ci

repo: freme-project/e-Internationalization

license_source: bigquery


text:
FREME NER produces nif:isString twice

curl -X POST -H "Cache-Control: no-cache" -H "Postman-Token: 6da7f638-ac30-79e5-d80f-e78d44c530f5" -d 'Welcome to Europe!' "http://api-dev.freme-project.eu/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&informat=text"
produces
@prefix xsd:   <http://www.w3.org/2001/XMLSchema#> .
@prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> .
@prefix nif:   <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#> .

<http://freme-project.eu/#char=11,17>
        a                     nif:RFC5147String , nif:Phrase , nif:Word , nif:String ;
        nif:anchorOf          "Europe"^^xsd:string ;
        nif:beginIndex        "11"^^xsd:nonNegativeInteger ;
        nif:endIndex          "17"^^xsd:nonNegativeInteger ;
        nif:referenceContext  <http://freme-project.eu/#char=0,18> ;
        itsrdf:taClassRef     <http://dbpedia.org/ontology/Location> , <http://dbpedia.org/ontology/PopulatedPlace> , <http://dbpedia.org/ontology/Place> , <http://www.w3.org/2002/07/owl#Thing> , <http://dbpedia.org/ontology/Continent> ;
        itsrdf:taConfidence   "0.5313763171783054"^^xsd:double ;
        itsrdf:taIdentRef     <http://dbpedia.org/resource/Europe> .

<http://freme-project.eu/#char=0,18>
        a               nif:String , nif:Context , nif:RFC5147String ;
        nif:beginIndex  "0"^^xsd:nonNegativeInteger ;
        nif:endIndex    "18"^^xsd:nonNegativeInteger ;
        nif:isString    "Welcome to Europe!" , "Welcome to Europe!"^^xsd:string .

<http://freme-project.eu/#char=0,7>
        a                     nif:Phrase , nif:Word , nif:String , nif:RFC5147String ;
        nif:anchorOf          "Welcome"^^xsd:string ;
        nif:beginIndex        "0"^^xsd:nonNegativeInteger ;
        nif:endIndex          "7"^^xsd:nonNegativeInteger ;
        nif:referenceContext  <http://freme-project.eu/#char=0,18> ;
        itsrdf:taClassRef     <http://dbpedia.org/ontology/Film> , <http://dbpedia.org/ontology/Work> , <http://dbpedia.org/ontology/Wikidata:Q11424> , <http://www.w3.org/2002/07/owl#Thing> ;
        itsrdf:taConfidence   "0.49767660362327676"^^xsd:double ;
        itsrdf:taIdentRef     <http://dbpedia.org/resource/Welcome_(2007_film)> .

It does not happen when I specify nif-version=2.1

Hi @jnehring,
I have fixed it in our NIF library.
We need to deploy it to test, but our Jenkins task to it is disabled.
Best,

should be enabled now, please try to re-build freme ner and check if this is fixed. At the moment it is not fixed, see
https://api-dev.freme-project.eu/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&mode=all&outformat=turtle&informat=text&input=Diego Maradona is from Argentina.&nif-version=2.0

Any news on this? Just trying to work with FREME-NER and still get the
repetition.
2016-11-16 11:33 GMT+01:00 Milan Dojčinovski notifications@github.com:

should be enabled now, please try to re-build freme ner and check if this
is fixed. At the moment it is not fixed, see
https://api-dev.freme-project.eu/current/e-entity/freme-ner/
documents?language=en&dataset=dbpedia&mode=all&outformat=
turtle&informat=text&input=Diego%20Maradona%20is%20from%
20Argentina.&nif-version=2.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freme-project/freme-ner/issues/161#issuecomment-260911333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABH5AtZwekq0UO784CwR7mCB2VGbjYmVks5q-tvrgaJpZM4Kuyxu
.

@sandroacoelho have fixed it but I dont see the fix in the API dev. @sandroacoelho ?
btw, @fsasaki the issue only occurs in NIF 2.0. If you use NIF 2.1 there is no such issue. See https://api.freme-project.eu/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&mode=all&outformat=turtle&informat=text&input=Diego Maradona is from Argentina.&nif-version=2.1
Note the nif-version=2.1 parameter.

Hi @m1ci , @fsasaki
Problem solved: https://api-dev.freme-project.eu/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&mode=all&outformat=turtle&informat=text&input=Diego%20Maradona%20is%20from%20Argentina.&nif-version=2.0

Thanks! What needs to happen to have this in the live version?
2016-11-21 3:11 GMT+01:00 Sandro notifications@github.com:

Hi @m1ci https://github.com/m1ci , @fsasaki https://github.com/fsasaki
Problem solved: https://api-dev.freme-project.
eu/current/e-entity/freme-ner/documents?language=en&dataset=
dbpedia&mode=all&outformat=turtle&informat=text&input=
Diego%20Maradona%20is%20from%20Argentina.&nif-version=2.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freme-project/freme-ner/issues/161#issuecomment-261826340,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABH5ArZ6mUc1ucEyKwTWsyDTcuAmaJWdks5rAP3bgaJpZM4Kuyxu
.

@sandroacoelho you have missed to add the datatype for isString. Its xsd:string - see https://github.com/NLP2RDF/ontologies/blob/master/nif-core/nif-core.ttl#L154 Please fix this. Thanks!

Thanks! What needs to happen to have this in the live version?

This requires a release of FREME NER. We will do a release later this week to fix this bug for the SWIB presentation.

it seems the issue with datatype is fixed. @sandroacoelho please confirm?

This API call  uses nif-version=2.0 and does not produce a datatype for nif:isString. When I set nif-version=2.1 then it produces the datatype.
@m1ci Is this behaviour correct? I think it should produce the datatype also for nif-version 2.0

you are right, there is no datatype for nif:isString. Sorry. I was specifying wrong nif version.

@sandroacoelho can you fix this until tomorrow? It would be nice to have the bug fixed before the release.

Sure. I will do it.

Hi @m1ci , @jnehring
Issue fixed. The problem was at FREMECommon.
Best,

thanks @sandroacoelho

fixed on live through the release

The bug happens also when the prefix parameter is specified:
curl -X POST -H "Cache-Control: no-cache" -H "Postman-Token: 6da7f638-ac30-79e5-d80f-e7d44c530f5" -d 'Welcome to Europe!' "http://rv1443.1blu.de/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&informat=text&prefix=http://hello.de"
@prefix xsd:   <http://www.w3.org/2001/XMLSchema#> .
@prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> .
@prefix nif:   <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#> .

<http://hello.de/#char=0,70>
        a               nif:String , nif:Context , nif:RFC5147String ;
        nif:beginIndex  "0"^^xsd:nonNegativeInteger ;
        nif:endIndex    "70"^^xsd:nonNegativeInteger ;
        nif:isString    "language=en&dataset=dbpedia&informat=text&prefix=http%3A%2F%2Fhello.de"^^xsd:string .

<http://hello.de#char=0,70>
        a               nif:String , nif:Context , nif:RFC5147String ;
        nif:beginIndex  "0"^^xsd:nonNegativeInteger ;
        nif:endIndex    "70"^^xsd:nonNegativeInteger ;
        nif:isString    "language=en&dataset=dbpedia&informat=text&prefix=http%3A%2F%2Fhello.de"^^xsd:string .

authors: fsasaki jnehring m1ci sandroacoelho

repo: freme-project/freme-ner


text:
Datepicker fixes

📥 Proposed changes

Nudge the datepicker 2px down to conform with the design.
Close datepicker when choosing date
Add ability to type text into datepicker
Add bottomtext to datepicker
Add label to text-field (use by datepicker)
Change opening behaviour to opening datepicker on focus
Capitalize months in datepicker

☑ Submission checklist

[x] I have read the CONTRIBUTING doc
[x] yarn build works locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

This change does have a bug in chrome: https://github.com/nrkno/core-components/issues/322

I've found one bug/unexpected behavior (that might have been there before as well): The dropdown stays open when you tab to another input, possibly blocking that input or others. This is especially relevant when entering a date as text and then tabbing to the next input in the form.

authors: Saegrov piofinn

repo: fremtind/jokul


text:
Fixed bug in multiple occurrences of & in query pairs resulted in a failed parse. Now multiple & are correctly ignored.

Also included a test.

When/why would you have multiple &&?

No idea, I assume real world urls are just plain bad.
Again the spec doesn't specify a key/value format but since Query pairs is a nice function to do this common format for us it at least makes it more resilient.

According to section 2.2 the & is just reserved as a delimiter so the use of multiple delimiters (even by accident) doesn't seem to fall foul of this.

Hmmm. That's interesting. As you say, the spec doesn't mention anything about this, it's effectively an informal standard. Where there is a spec, I've erred on the side of strict. I'm in two minds. I can't see any particular harm that it would do (and Postel's principle might well imply that we should be liberal here). On the other hand, it feels like a fairly special case to cope with a measurably broken system. Tempted to say, given that there's 3 of us, that we should vote :)

+1 for me :)

What happens if you have an html encoded value in there? Is that allowed? I'll have to check the spec. Example: ?foo=bar&&ref=mem

Hmm, I'll have to try again on a desktop, as I don't have backticks on my phone.

I think the above is a bogus example; I just want to make sure it is not dropped in situations where the user would not expect it to be dropped. Does that make sense? I should add a test.

Ah so "foo" value would be "bar&"
Since "&" is a reserved character then I'm not 100% sure what the best course would be.

Ah but would "& amp;" be valid? It does say in the spec that & is reserved :)

You are correct. I was thinking post-url-decoding. With your clarification, I would be -1, as I would prefer strictness over flexibility. I am open to being convinced otherwise. Do you know of other libs that ignore double &?

I used an online query parser to see what it would do based on this url "http://example.com?foo=bar&&ref=mem"

key
Value

'foo'
bar

'amp;ref'
mem

It seems to strip out multiple & occurrence.
I've also used System.Web.HttpUtility.ParseQueryString with the following code
let y = System.Web.HttpUtility.ParseQueryString("foo=bar&&ref=mem")
for k in 0 .. y.Keys.Count-1 do
    printf "key:%A value:%A" y.Keys.[k] (y.GetValues(k))

and this is the response
key:"foo" value:[|"bar"|]key:<null> value:[|""|]key:"amp;ref" value:[|"mem"|]val it : unit = ()

Notice the empty pair?
If we look at other string parses that handle delimiters they produce a similar result.
Take the CSV parser in FSharp.Data
If we run the following code and make the csv parse use & for a separator
    let x = FSharp.Data.CsvFile.Parse("foo=bar&&ref=mem",separators="&", hasHeaders=false);;

then we get the following:
    > x.Rows;;
    val it : seq<FSharp.Data.CsvRow> = seq [[|"foo=bar"; ""; "amp;ref=mem"|]]

Notice the empty pair again?
So it seems to me that we have the following choices:

Ignore multiple delimiters (effectively this PR)
Include them as an empty pair

If we choose 1 then we are all good, if we choose 2 then we should still accept this PR as it still lets us parse query string without breaking while working on included it as an empty pair.

I can somewhat see the sanity in making it an empty pair. I have to admit that I do worry about ever adding extra code to be maintained to deal with an edge case. How often do people run in to this problem? I'm also wary of making this change, then another, which would mean a behavioural change for a short period of time. Hmmmm. I have to admit I'm not sure! Is it causing you a big problem?

Not necessarily extra - more correcting existing code :).
Yeah it has caused a bit of a problem for me, that's what prompted this PR - Real world urls are horrid, this library has helped hugely in navigating them.

Okay, I'm convinced.

I think I'm actually reasonably convinced for that case - provided a parser for && as empty KV pair can be written reasonably concisely and effectively, I don't mind that change. It's a loose standard, and I can see that being OK. I'll try and write one at the beginning of next week, provided nobody beats me to it!
I would like to be helpful, and I think this is - if it makes the lib more useful for your real world case @TWith2Sugars - let's do it.

Right, Sorry for the delay in getting back. I have time to this with the empty pair and will have a go at it today.

I've also added a check for null/whitespace to so the parser isn't even called in those circumstances.

Only noticed the build failed. Any ideas why?

authors: TWith2Sugars kolektiv panesofglass

repo: freya-fs/arachne

license: mit


text:
NGI0-FSFE Updating Selected Documents with REUSE Specification

Hello,
By way of introduction, I am Gabriel with the Free Software Foundation Europe (FSFE) a consortium member of the NGI0 Initiative. Part of what is offered FrictionlessData's involvement with NGI0 is help from us with your project on your copyright and license management.
After a quick check on your repository, I would like to propose some template updates regarding copyright and licensing information in your repo. Our REUSE specification (https://reuse.software) intends to make licensing easier with best practices to display legal information through comment headers on source files that can be easily human and machine readable. The REUSE tool we have developed to support this specification also makes the process of applying licenses to files and compliance checking much easier.
Instructions on how to install the REUSE tool can be found here: https://reuse.readthedocs.io/en/stable/readme.html#install
You can also check out this screencast for more instructions on how to use the REUSE tool: https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif
The changes in this pull request have also been made for you to understand the basic ideas behind REUSE, and how adopting the REUSE practices would look like within your repository.
REUSE Features:
• SPDX copyright and license comment headers for relevant files.
• LICENSES directory with licenses used in the repository
• Associating copyright/licensing information through a DEP5 file in large directories.

Files Missing Copyright and Licensing Information
The idea behind REUSE is that every single file in your repository should have a header that includes information about the copyright and license of your project files.
To serve as an example, I added the SPDX headers with copyright and license information to the copyrightable files in the "content/docs/ folder. This should give you an idea of how comment headers should look like in a REUSE compliant repository, and how they should be added to the other source code files in your repository.
Please also check if the personal information in these headers are correct and consistent to your knowledge, as I have merely used a placeholder for the copyright segment of the comment header. In the event that there are more copyright holders, please include them in these comment headers.
LICENSES Directory in the Root of the Project Repository
The LICENSES Folder should contain the license text of every license applicable in your repository. I included in this directory the file that contained the Unlicense license text.
I hope that you find this useful and please feel free to contact me directly at gabriel.ku@fsfe.org if you have any questions.
Best,
Gabriel
(Free Software Foundation Europe)

Hi @gabriel-ku, thanks for proposing this. In my opinion applying a copyright and license to all files in the repository:

Is harder to maintain, unless by running the REUSE script as part of CLI.
Creates headers (for text-based files) or additional files (for binary files like images, see example), which can clutter a repository
Specifies a license multiple times (and can thus create conflicting information):

As a LICENSE or LICENSE.md file in the root (a general best practice for open source software, also picked up by GitHub)
As a LICENSES/Unlicense.txt
As a SPDX-License-Identifier in the header of or additional file for every file

But more importantly, I have not seen this approach as a general best practice. I can understand the appeal if different licenses are use for a single repository, but that is not the case for this one. @roll or others, any thoughts?

Let's close it for now in favor of https://github.com/frictionlessdata/dplib-py/pull/20

authors: gabriel-ku peterdesmet roll

repo: frictionlessdata/datapackage

license: Unlicense


text:
[s] add github icon in signin button refs - #268

We use gihub for our authentication. It is good to have a github icon in sign in button.

Perfect 👍

authors: rufuspollock subhankarb

repo: frictionlessdata/dpr-api


text:
Reason for dates being moment objects?

I'm giving jsontableschema-js a try in a project, I'm surprised that the 'data' type returns moment objects.  Any reason not to return JS date objects?  If you are using moment just for parsing how about returning the .toDate() output.

Hi @Hypercubed
After thinking about this a bit, I'm quite partial to leaving it as moment objects. The user can easily get a date string by calling toDate, but they also get the flexibility to use other methods on moment.
Apart from this being undocumented, which is easily fixed, can you describe a use case where it is restricting to be provided with a moment object?

@akariv
WDYT?
It feels a little bit wrong for me when a core lib like jsontableschema have such a dependency on API level.

@pwalsh My idea is to use this module to transform table data to data types usable within JS applications; for example in angular or d3 applications.  These, typically, expect the date type to be a JS native Date.  If I need to perform a second transform after the schema transform to convert moment objects to native Date objects this kind of defeats the purpose.  Anyway, that is just my opinion.

@zhenyab
Use native Date seems the safest way for me based on this and many other we don't know for now. WDYT?

If we call native date, we actually also should ensure it is cast to the right format.

Native Date object has poor API, and moment object provide much more possibilities to work with the date. What the reason then to have it as JS native Date object? Need to see real use case and real usage examples to understand what will be better to return.

Yes, moment has a better API and it makes sense to produce moment objects, however, not many API consume moment objects.  I think the purpose of using the schema transform is to generate data that is coconsable by other applications. If you are casting to moment objects then using the data in an angular application (maybe ui-grid for example) or a d3 chart (using d3 time scale) you will need to convert the moment object to a Date object.  I think this is a real world use case.

Here is an example of where I would need to convert the moment object to a date object for use by both angular and d3:  http://hypercubed.github.io/Project-Chi/#/examples/universe
(note this is using https://github.com/Hypercubed/chi-datapackage , not jsontableschema-js, in part for this reason).

authors: Hypercubed pwalsh roll zhenyab

repo: frictionlessdata/jsontableschema-js


text:
Guide: Table and Table Schema, Validation, and Tabulator

Create the first main section of the guide on tables.
Subissue of: #430
Acceptance

We have a working guide for Table and Table Schema
We have a working guide for Validation and Tabulator

Tasks

[x] What is a table
[x] Table schema
[ ] Validation
[x] Tabulator

In Progress: Content Draft written here. https://hackmd.io/605lAS1xTHC0anrKhTXp5A

@lauragift21  let me know when you need this reviewed?

Alright, sure I will.

Update: Currently facing an Issue with the goodtables-js library I've created an issue on the repo to address it. https://github.com/frictionlessdata/goodtables-js/issues/23

Ready for review. The only blocker right now is adding a demo for goodtables-js library. @rufuspollock

The content is ready for review @rufuspollock

@lauragift21 on my queue - could you get an initial review e.g. from @monikappv or @mpolidori?

@lauragift21 I can take a look later today

@lauragift21 Here's my review HackMD and a diff (if you want to see the exact changes).

Thanks, @mpolidori. Really helpful review.

authors: lauragift21 mpolidori rufuspollock

repo: frictionlessdata/project


text:
Dockerize app, add workflow for pushing to GHCR

Adds a Dockerfile based on node:lts-alpine to minimize image size
Adds a gh-workflow to build & push the image to the GHCR

Regards #18.

Thank you <3

authors: IQNeoXen philipbrembeck


text:
Update package.json to avoid warnings

Update to hoek 4.2.1 and moment 2.19.3

Moment is already in version 2.22.2 in package-lock.json:
"moment": {
      "version": "2.22.2",
      "resolved": "https://registry.npmjs.org/moment/-/moment-2.22.2.tgz",
      "integrity": "sha1-PCV/mDn8DpP/UxSWMiOeuQeD/2Y="
    }

I opened the vulnerability issue a while ago. So not sure why github is complaining about v2.19.3 in package-lock.json.
I can't find hoek or hapijs in our package.json either.
Closing as everything seems fine. Maybe a github problem?

repo: frontity/wordcamp-theme


text:
[android] Overhaul of Promo capabilities.

Promos on Android should support:

Video previews when available.
Link to the related FrostClick post.
Share button. It would basically allow the user to send a share intent to social media apps to share the frostclick related post to the promo.

repo: frostwire/frostwire


text:
Symbol "BIGNUM-TYPE" not found in the SB-BIGNUM package. (SBCL-1.3.11/W32)

Hi guys,
I got this error after I upgraded sbcl to 1.3.11.
I filled this to SBCL bug list, but rejected. ;-p
https://bugs.launchpad.net/sbcl/+bug/1643771
BR,
fragrans

This error only appears using SBCL/1.3.11.
OS: windows 7, 32bit
No such issue with SBCL/1.3.9.
This is SBCL 1.3.11, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.

WARNING: the Windows port is fragile, particularly for multithreaded
code. Unfortunately, the development team currently lacks the time
and resources this platform demands.
* (ql:quickload :ironclad)
To load "ironclad":
  Load 1 ASDF system:
    ironclad
; Loading "ironclad"
.;
; caught ERROR:
; READ error during COMPILE-FILE:
;
; Symbol "BIGNUM-TYPE" not found in the SB-BIGNUM package.
;
; Line: 53, Column: 52, File-Position: 2151
;
; Stream: #<SB-INT:FORM-TRACKING-STREAM for "file C:\\Users\\xeltek\\quick
lisp\\dists\\quicklisp\\software\\ironclad_0.33.0\\src\\digests\\digest.lisp" {2
47847D1}>

debugger invoked on a UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread
#<THREAD "main thread" RUNNING {23E0DC69}>:
  COMPILE-FILE-ERROR while
  compiling #<IRONCLAD-SOURCE-FILE "ironclad" "src" "digests" "digest">

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [RETRY ] Retry
                                     compiling #<IRONCLAD-SOURCE-FILE "ironclad"
 "src" "digests" "digest">.
  1: [ACCEPT ] Continue, treating
                                     compiling #<IRONCLAD-SOURCE-FILE "ironclad"
 "src" "digests" "digest">
                                     as having been successful.
  2: Retry ASDF operation.
  3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
                                     configuration.
  4: [ABORT ] Give up on "ironclad"
  5: Exit debugger, returning to top level.

(UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T "~/asdf-action::format-actio
n/" ((#<ASDF/LISP-ACTION:COMPILE-OP > . #<IRONCLAD-SYSTEM::IRONCLAD-SOURCE-FILE
"ironclad" "src" "digests" "digest">)))
0]

Their reply:
The type has been removed in commit 101ab291060383d7a9a97131d78d9ce852d36885 which states:
  It's just a deftype to BIGNUM.
Using CL:BIGNUM instead of SB-BIGNUM:BIGNUM-TYPE should resolve the issue.
Note that the SB-BIGNUM package is internal and its exported symbols present an interface for other parts of SBCL, not for public consumption.

This is also occurring on 32-bit SBCL 1.3.12-70-9a62b77 (git master) on linux.
I applied #72 locally and now it works.

authors: daveloyall fragrans

repo: froydnj/ironclad


text:
Run cleanup from button in app

People with no background in programming should be able to admin this app. Thus a button somewhere in the app to perform cleanup:keep_users would be nice.

@navro do you have time to implement this?

repo: fsek/voting


text:
fsi.PrintLength has no effect with sequences

Setting the print length in an interactive session works as expected when printing a list but seems to have no effect when printing a sequence.
e.g. executing these elicits very different results:
   fsi.PrintLength <- 50;;

   [1..50];;

   seq {1..50};;

It's not obvious to me why this would be so I'm considering it to be a bug.

This is by design - sequences are drastically reduced in size since they are on-demand and sometimes slow to compute.   You should install a custom pretty printer (fsi.AddPrinter of fsi.AddPrintTransformer) if you want to change their printing.

authors: Korporal dsyme


text:
Create pull requests for all paket users on github

@vbfox created the following statement
"1524 projects have files that are either paket or it's bootstrapper in standard positions https://docs.google.com/spreadsheets/d/19Th3rRWBIoFxlBpbuDQ9QSd7tlJ05Fibq7VFH9h52mE/edit#gid=1315769600
Of theses 590 had commits after 2017-01-01: https://docs.google.com/spreadsheets/d/1m6Qu_lEy1LQYKoBpKA9HVMvMvIRQj70mdf1pfaA3S0A/edit#gid=63915918
Thanks google bigquery :slightly_smiling_face: Family time now but if someone wants to auto-create PRs it's a start."
SELECT
  MAX(committer.date) AS last_commit,
  individual_repo_name
FROM
  `bigquery-public-data.github_repos.commits`,
  UNNEST(repo_name) AS individual_repo_name
WHERE
  individual_repo_name IN (
  SELECT
    DISTINCT repo_name
  FROM
    `bigquery-public-data.github_repos.files` AS f
  WHERE
    ((path = '.paket/paket.bootstrapper.exe')
      OR (path = '.paket/paket.exe')
      OR (path = 'paket.exe')) )
  AND committer.date > '2017-01-01'
GROUP BY
  individual_repo_name
ORDER BY
  MAX(committer.date) DESC

So all these projects need the patch in https://github.com/fsprojects/Paket/pull/3066
What we need to do:
For each of the repos we need to replace the bootstrapper with 5.142
If the repo uses it as paket.bootstrapper.exe then we just need to replace it. If they have a paket.exe then we copy paket.bootstrapper.exe over their existing paket.exe and call it paket.exe (magic mode)

Example PR for magic mode: https://github.com/SAFE-Stack/SAFE-BookStore/pull/300
Example PR for old school mode: https://github.com/fsprojects/Argu/pull/104/files
Note: in both cases we add the 63KB paket.bootstrapper.exe to the project - just target file names differ.
@shiftkey offered help. I would appreciate that very much

I've noticed that quite a few of these are forks - do we want to open PRs on the mainline repos only or also on all the forks?

When sending PR, don't forget to add "I'm some random person on the internet. To check that I'm not adding any malicious code into your codebase, refer to official Paket repository with pubished SHA256 checksum and, please, validate that it is matching."

@cdrnet Yes that was my next message on the slack, Github API (via Octokit?) should be queried for each to get if it's a fork, get the size to ensure that it's not the main paket and download it to check the version

@eugene-g yes good point. The text message should be good and also include security notice. And we should send it from a trusted account.

Ok I computed the repos that would need an upgrade : https://docs.google.com/spreadsheets/d/1cjmf7YD-3ZnPzJxNIPl_6m0YS2dFYf45kdUF3ZJ-yYU/edit?usp=sharing
That is the previous list where I queried if they were forks and the version of the bootstrapper to check that it wasn't the latest
open FSharp.Control.Tasks
open Octokit
open Octokit.Helpers
open Octokit.Internal

let repos =
    [|
        "fsprojects/FSharp.Configuration";"15below/Ensconce";"gigya/microdot";"BlythMeister/Gallifrey";"fsprojects/FSharpLint";"jgrund/fable-jest";"vik-borisov/TelegramClient";"delegateas/XrmMockup";"SAFE-Stack/SAFE-BookStore";"fsprojects/Paket";"CSBiology/BioFSharp";"ionide/ionide-vscode-fsharp";"fable-compiler/Fable";"fsprojects/matprovider";"fwaris/CALib";"Thorium/Owin.Compression";"JohanLarsson/Gu.Reactive";"red-gate/RedGate.Build";"WebApiContrib/WebAPIContrib.Core";"elastic/elasticsearch-net";"mennowo/TLCGen";"yurii-litvinov/REAL.NET";"CSBiology/FSharp.Stats";"janno-p/XRoadLib";"krauthaufen/FShade";"hafuu/FSharpApiSearch";"SayToMe/Solve";"gusty/FSharpPlus";"fsdn-projects/FSDN";"vbfox/stidgen";"NinetailLabs/VaraniumSharp.Initiator";"NinetailLabs/VaraniumSharp";"punker76/code-samples";"fslaborg/XPlot";"ReedCopsey/Gjallarhorn";"nhsevidence/ld-bnf";"TheAngryByrd/MiniScaffold";"KevM/tikaondotnet";"fsprojects/FSharp.CloudAgent";"fluentribbon/Fluent.Ribbon";"aardvark-platform/aardvark.rendering";"fsprojects/FSharp.TypeProviders.SDK";"lefthandedgoat/canopyStarterKit";"JohanLarsson/Gu.Wpf.DataGrid2D";"mennowo/Gu.Wpf.DataGrid2D";"stefanmaierhofer/Uncodium.Units";"madhon/lighthouse";"aabenoja/Cake.Parallel";"MangelMaxime/Fulma";"JohanLarsson/Gu.State";"ionide/ionide-vscode-helpers";"colinbull/colinbull.github.io";"jet/kafunk";"fsprojects/FSharp.AWS.DynamoDB";"PaulStovell/ServiceBouncer";"eiriktsarpalis/TypeShape";"CSBiology/FSharp.Care";"fsprojects/FSharp.Data.TypeProviders";"enovales/LudumLinguarum";"JasperFx/alba";"fable-compiler/fable-react";"nozzlegear/davenport.net";"inosik/Fable";"ncave/Fable";"intellifactory/websharper";"y2k/JoyReactorRN";"steego/Steego.Demo";"lefthandedgoat/canopy";"nessos/Argu";"fsprojects/Argu";"NinetailLabs/NeuroLinker";"JohanLarsson/Gu.Analyzers";"pingthepeople/ptp-functions";"jhoerr/iga-tracker-functions";"intellifactory/websharper.ui.next";"wastaz/Hyperboliq";"muehlhaus/FSharp.Plotly";"pbbwfc/Lizard";"intellifactory/websharper.owin";"intellifactory/websharper.forms";"intellifactory/websharper.ui.next.piglets";"intellifactory/websharper.html";"sergey-tihon/OpenNLP.NET";"nessos/FsPickler";"mbraceproject/FsPickler";"ionide/ionide-vscode-paket";"fsharp/FsCheck";"fscheck/FsCheck";"OpenTl/OpenTl.Schema";"johnberzy-bazinga/FSharp.Data.GraphQL";"bazingatechnologies/FSharp.Data.GraphQL";"fslaborg/FSharp.Charting";"Antaris/RazorEngine";"phatcher/CsvReader";"haf/expecto";"punker76/Fluent.Ribbon";"fluentribbon/XamlCombine";"eacasanovaspedre/functional-data-structures";"fsprojects/IfSharp";"fable-compiler/fable-suave-scaffold";"draganjovanovic1/terminal-snake";"intellifactory/websharper.o3d";"intellifactory/websharper.leaflet";"intellifactory/websharper.glmatrix";"intellifactory/websharper.bing.maps";"intellifactory/websharper.d3";"intellifactory/websharper.charting";"mvno/Okanshi";"bjornna/dips-ckm";"intellifactory/websharper.forms.bootstrap";"F-2-F/F2F.ReactiveNavigation";"phatcher/NCheck";"kerams/Templatus";"fsprojects/SwaggerProvider";"Horusiath/Akkling";"phatcher/SpecFlow.Unity";"TIHan/Foom";"fsharp/FsAutoComplete";"baronfel/Paket";"CSBiology/BioFSharp.Mz";"getgauge/gauge-csharp";"YaccConstructor/YaccConstructor";"niklaslundberg/Arbor.X";"gmpl/FSharpPlus";"delegateas/XrmDefinitelyTyped";"Zaid-Ajaj/LiteDB.FSharp";"sergey-tihon/Stanford.NLP.NET";"sqc1999/LxRunOffline";"nozzlegear/alexa-skills";"the-gamma/gallery-csv-service";"the-gamma/thegamma-script";"xiaoyvr/SimpleHttpMock";"vrvis/aardvark.base";"fsharp-editing/Forge";"ai-traders/liget";"fsprojects/FSharp.TypeProviders.StarterPack";"RFQ-hub/SocketIoSuave";"DigitalFlow/Xrm-Update-Context";"fsprojects/FsXaml";"readysetmark/WealthPulse";"Hosch250/Checkers";"isaksky/FsSqlDom";"delegateas/Delegate.XrmDefinitelyTyped";"JohanLarsson/Gu.Wpf.UiAutomation";"JohanLarsson/Gu.Roslyn.Asserts";"BillHally/FSharp.Chart";"nessos/UnionArgParser";"JohanLarsson/Gu.Wpf.ValidationScope";"JohanLarsson/Gu.Wpf.ToolTips";"JohanLarsson/Gu.Wpf.PropertyGrid";"JohanLarsson/Gu.Wpf.NumericInput";"JohanLarsson/Gu.Wpf.Media";"JohanLarsson/Gu.Wpf.Geometry";"JohanLarsson/Gu.Wpf.FlipView";"JohanLarsson/Gu.Localization";"JohanLarsson/Gu.Wpf.Adorners";"fsprojects/FSharp.Control.AsyncSeq";"chinwobble/DaisyParser";"julienadam/AttachR";"Thorium/Linq.Expression.Optimizer";"dungpa/fantomas";"mathnet/mathnet-symbolics";"OrleansContrib/Orleankka";"JohanLarsson/Gu.ChangeTracking";"JohanLarsson/Gu.Persist";"JohanLarsson/Gu.Settings";"DotNetAnalyzers/WpfAnalyzers";"vrvis/aardvark";"Creuna-Oslo/Episerver.Basis.Slim";"janno-p/XRoadProvider";"tpetricek/FSharp.Formatting";"jackfoxy/FSharp.Formatting";"wikibus/Argolis";"daniel-chambers/FSharp.Azure.Storage";"fsprojects/FSharp.Azure";"fsprojects/FSharp.Azure.Storage";"fsprojects/ProjectScaffold";"AmyrisInc/GslCore";"cloudRoutine/Paket";"tytusse/GitVersionTypeProvider";"mennowo/MiniTD";"cloudRoutine/FSharp.Formatting";"AlaricDelany/Schwefel.Ruthenium";"BayardRock/IfSharp";"persimmon-projects/Persimmon";"pdfforge/translatable";"fsprojects/Paket.VisualStudio";"vbfox/Paket";"questnet/FSCS-Lensgenerator";"embix/FSCS-Lensgenerator";"RMCKirby/ColorConsole";"dsyme/FSharp.TypeProviders.StarterPack";"JohanLarsson/Gu.Inject";"aardvarkplatform/aardvark.docs";"kichristensen/InfluxDB.WriteOnly";"mastoj/kalender2015";"teo-tsirpanis/FsRandom-pcg";"EveResearchFoundation/EveGameEngine";"callmekohei/deopletefs";"tpluscode/UriTemplateString";"pocketberserker/Data.HList";"TheAngryByrd/Marten.FSharp";"vrvis/aardvark.rendering";"erbg/HRON";"persimmon-projects/Persimmon.MuscleAssert";"sergey-tihon/FSharp.TypeProviders.StarterPack";"fjoppe/Legivel";"fjoppe/FsYamlParser";"JohanLarsson/Gu.Units";"muehlhaus/BioFSharp";"hoonzis/Pricer";"persimmon-projects/Persimmon.Script";"jorgef/fsharpworkshop";"madhon/statsd.net";"madhon/ostrich";"rflechner/Suave.Swagger";"sideeffffect/FSharpx.Collections";"95ulisse/FsCPS";"vreniose95/Ccr";"reflash/chat-backend";"VasiliskDevelopment/CardboardFactorySolution";"smolyakoff/conreign";"sergey-tihon/SwaggerProvider";"mattstermiller/koffee";"giacomociti/FSharp.Data.Xsd";"unic/bob-keith";"jkone27/AliceMQ";"demystifyfp/FsTweet";"sillyotter/BackupDBToAzure";"theimowski/SuaveMusicStore";"YaccConstructor/Brahma.FSharp";"fsprojects/AzureStorageTypeProvider";"arthis/glomulish";"rflechner/LinqToSalesforce";"0x53A/Paket";"thinkbeforecoding/Paket";"dady8889/Fluent.Ribbon";"RFQ-hub/ZabbixAgentLib";"janno-p/fable-vue";"whitetigle/samples-pixi";"mbraceproject/MBrace.Azure";"AmyrisInc/Gslc";"WalternativE/fableshotdetection";"ionide/ionide-fsgrammar";"hanswolff/dedilib";"cloudRoutine/FAKE";"jjpatel/pushtray";"mbraceproject/MBrace.Core";"teo-tsirpanis/Farkle";"ivaylo5ev/mason";"YaccConstructor/Examples";"e-rik/XRoadLib";"phatcher/Meerkat.Security.Hmac";"rflechner/FSharp.Data";"codehutch/pg3d";"nu-soft/FSharp.Plc.Ads";"CaringDev/FsUnit.xUnit.Typed";"boumenot/Wapiti.NET";"Jallah/Connect4Challenge";"HLWeil/BioFSharp";"fsprojects/Canopy.Mobile";"ed-ilyin/FSharp.EdIlyin.Core";"mbraceproject/MBrace.AWS";"also-cloud/AlsoCloud.Marketplace";"VaseninaAnna/Brahma.FSharp";"danieljsummers/FromObjectsToFunctions";"pkese/Orleankka";"ShalamovRoman/YC.Web";"bvenn/BioFSharp";"editorconfig/editorconfig-visualstudio";"FSharp-CN/FSharpBB";"baronfel/FAKE";"migfig/Labs";"ExM/NMoney";"ar3cka/Journalist";"mbraceproject/Vagabond";"nessos/Vagabond";"ExM/NConfiguration";"cgravill/TypesTSFS";"delegateas/Delegate.XrmContext";"nessos/Thespian";"ncave/fable-repl";"steego/toychest";"datNET/fs-fake-targets";"DigitalFlow/Xrm-Oss-Interfacing";"corux/seafile-cli-windows";"popular-parallel-programming/quad-ropes";"pocketberserker/FSDN";"fable-compiler/samples";"vbfox/FAKE";"MiloszKrajewski/FAKE";"yodiz/HttpApp";"ploeh/FsCheck";"MatrixSolutions/FSharp.Data.JsonValidation";"jeremyabbott/Presentations";"lefthandedgoat/openfsharpdemo";"pblasucci/quickpbt";"mleech/scotch";"GraanJonlo/MiniScaffold";"Dzoukr/Fue";"mhertis/Orleankka";"UgurAldanmaz/ServiceBouncer";"Lleutch/Sast";"leleutch/GenerativeTypeProviderExample";"amazingant/Amazingant.FSharp.TypeExpansion.Templates";"NinetailLabs/VaraniumSharp.Monolith";"LambdaFactory/fable-vscode-demo";"nhsevidence/ld-viewer";"nhsevidence/ld-qs-viewer";"sideeffffect/FSharpx.Extras";"elic-io/Hello.World";"fsprojects/FSharp.Data.Toolbox";"vrvis/fablish";"OlegZee/Xake";"cagyirey/Capstone.FSharp";"TheAngryByrd/Fable.Template.Library";"ElijahReva/ticket-problem";"awright18/SimpleExcelExporter";"sergey-tihon/Paket";"Cubey2019/Fluent.Ribbon";"teo-tsirpanis/expecto";"kMutagene/BioFSharp";"artur-s/Paket";"matthid/Yaaf.FSharp.Scripting";"haraldsteinlechner/FsPickler";"barsgroup/linq2db";"barsgroup/bars2db";"Spreads/Spreads.R";"lukasimir/SimJobShop1";"jeroldhaas/Gjallarhorn";"theprash/AzureStorageTypeProvider";"varon/FSLogger";"TOTBWF/FSharp.Data.GraphQL";"hodzanassredin/NFastText";"fsprojects/ExcelProvider";"CSBiology/FSharp.FGL";"irustandi/ReinforcementLearningFSharp";"BayardRock/Fungible";"blair55/canopy";"TeaDrivenDev/Amagatsha";"TeaDrivenDev/BranchDocuments";"cloudRoutine/FsAutoComplete";"nicolocodev/suavegnalr";"DingpingZhang/MaterialDesignInXamlToolkit";"TahaHachana/XPlot";"relayfoods/FsToolkit";"MattiasJakobsson/SuperGlue";"SuperGlueFx/SuperGlue";"fsprojects/projekt";"johnazariah/roslyn-wrapper";"andburn/hs-art-extractor";"mattj23/mathnet-spatial";"ArtofQuality/F2F.ReactiveNavigation";"sideeffffect/ProjectScaffold";"aolney/braintrust-server";"robertmuehsig/Fluent.Ribbon";"lexarchik/Paket";"Amyris/AmyrisBio";"Rickasaurus/Barb";"toburger/FSharp.Json";"divad4686/places-google-details";"15below/Sproc.Lock";"andredublin/Forge";"cryosharp/fluentwindsor";"JohnStov/Frobnicator2";"hoonzis/fluentnest";"CSGOpenSource/elasticsearch-net";"NUIM-BCL/DiffSharp";"DiffSharp/DiffSharp";"gilles-leblanc/genesis";"tjaskula/akka.net-fsharp.extensions";"ploeh/PollingConsumer";"Steinpilz/confifu-commands";"pittsw/TheWanderer";"eriove/mathnet-numerics";"ChipmunkHand/GiraffeRescue";"wooga/Paket.Unity3D";"ed-ilyin/EdIlyin.FSharp.Elm.Core";"daz10000/fss";"pkanavos/FakeCake_DNZ";"fsprojects/ExcelFinancialFunctions";"vilinski/MongoDB.Bson.FSharp";"pirrmann/FSketch";"johnazariah/csharp-algebraictypes";"johnazariah/csharp-uniontypes";"fsprojects/FSharp.Management";"RinsibleElk/TextOn.Atom";"contactsamie/FinCa";"miklund/inquiry";"Stift/Paket";"CSBiology/FSharpGephiStreamer";"fslaborg/RProvider";"fsprojects/FSharp.Compiler.CodeDom";"fsprojects/FSharpx.Collections";"ksmirenko/Brahma.FSharp";"TeaDrivenDev/StatusPotentiae";"fsharp-editing/fstoml";"fsprojects/FsLexYacc";"Hopac/Hopac";"cotyar/Akkling";"johanclasson/Unity.Interception.Serilog";"npmurphy/IfSharp";"scottgrey/weather";"the-gamma/govuk-data-import";"spr13/ACWES";"rneatherway/FsAutoComplete";"bullmastiffo/Contour";"josselinauguste/exim-maillog";"mandest/FSFabric";"mseknibilel/Alfred";"dsyme/MBrace.Azure";"dsyme/MBrace.Core";"adelnizamutdinov/music-page";"dsyme/FSharp.Charting";"madhon/Formo";"tipunch74/MaterialDesignInXamlToolkit";"eerohele/oath";"TheInnerLight/Nomad";"sfukui/MNNPlus";"sideeffffect/FinFun.Contracts";"boloutaredoubeni/kaleidoscope";"mhtraylor/market-sim";"Slesa/Dotter";"dkholod/GoogleCloudChaosMonkey";"cagyirey/Shodan.FSharp";"mastoj/BigQueryProvider";"caindy/ODataTypeProvider";"csjune/mathnet-spatial";"mathnet/mathnet-filtering";"skalinets/eat-now";"mandest/Nap";"colinbull/SqlProvider";"VerbalExpressions/FSharpVerbalExpressions";"enovales/feltlion";"kellerd/TicTacToeProvider";"stewart-r/AzureDocumentDbTypeProvider";"pkanavos/CSharpRevolution_DNZ";"mvno/Franz";"TheInnerLight/CSharp.Formatting";"Thilas/commandline";"pittsw/Indy.NET";"persimmon-projects/Persimmon.Unquote";"giacomociti/AntaniXml";"teo-tsirpanis/brainsharp";"sergey-tihon/FSharp.Management";"Steinpilz/confifu";"sergey-tihon/FSharp.Compiler.Service";"fsharp/xamarin-monodevelop-fsharp-addin";"danm-de/Fractions";"beeker/FAKE";"mavnn/Taggen";"FsStorm/FsStorm";"bennylynch/SQLProvider";"tgrospic/advent-of-code";"mzabolotko/Contour";"SDVentures/Contour";"Badmoonz/FSharp.ReportDSL";"fsharp-editing/FSharp.Editing";"FSharpBristol/FSharpBristolPresentations";"jmquigs/ModelMod";"cloudRoutine/toml-fs";"matthid/Yaaf.AdvancedBuilding";"carbon-twelve/Akabeko";"CumpsD/knx.net";"sidburn/sidburn.github.io";"vossccp/BotBuilderChannelConnector";"0x53A/FSharp.Compiler.Service";"snowcrazed/Paket";"figrollapps/PersonalTrainer";"pocketberserker/FSharp.Object.Diff";"robertpi/caffe.clr.demo";"rackspace/rackspace-net-sdk";"alfonsogarciacaro/FSharp.Compiler.Service";"forki/FSharp.Compiler.Service";"xavierzwirtz/FSharp.QueryProvider";"voiceofwisdom/FSharp.QueryProvider";"zeromq/fszmq";"pblasucci/fszmq";"jbeeko/TypeUp";"object/MidiFsharp";"cosmo0920/grnline.fs";"rfrerebe/fable-suave-scaffold";"adam-mccoy/elasticsearch-net";"Thorium/Paket";"rflechner/SlackTypeProvider";"pocketberserker/ZeroFormatter.FSharpExtensions";"simonhdickson/Paket";"soerennielsen/canopy";"imazen/libwebp-net";"tpetricek/Deedle";"czifro-tech/30-days-of-fsharp";"AITGmbH/ApplyCompanyPolicy.Template";"AITGmbH/AIT-Apply-Company-Policy-SDK";"dolly22/FAKE.Dotnet";"alexeyzimarev/MassTransit.RavenDbIntegration";"et1975/fable-suave-scaffold";"mjul/aws-lambda-fsharp-lab";"wallymathieu/SemVer.FromAssembly";"mvkra/WebsocketFrameworkTester";"vain0/EnumerableTest";"ScottShingler/FsStorm";"dangets/ionide-atom-fsharp";"ionide/ionide-atom-fsharp";"ionide/ionide-fsharp";"fbehrens/vscode-polyglott";"fsharping/Website";"msdyncrm-contrib/PluginAssemblyLoader";"ionide/ionide-vscode-fake";"jeremyabbott/doctoralsurvey";"ijsgaus/fun";"rexcfnghk/marksix-parser";"rojepp/FSharp.Compiler.Service";"fradav/IfSharp";"deapsquatter/FSharp.SSEClient";"alexpantyukhin/FSharp.Data.GraphQL";"fsprojects/FSharp.ViewModule";"pocketberserker/ComVu";"mjul/dropbox-activity-reports";"TIHan/Ferop";"opcon/turnt-ninja";"inosik/Paket";"arthis/psychic-tribble";"davidpodhola/fable-suave-scaffold";"amazingant/Amazingant.FSharp.TypeExpansion";"TomGillen/GoldenHammer";"TheInnerLight/FSPipes";"bchavez/Dwolla";"ksmirenko/type-providers";"jindraivanek/fueBlog";"HackYourJob/hexagonchallenge";"Graph-Parsing-Demo-Group/YC.GraphParsingDemo";"Bio-graph-group/YC.BioGraph";"mjul/fslab-playground";"KochetovKirill/YC.GraphParsingDemo";"ZachBray/FunScript";"vbfox/U2FExperiments";"kate-paulk/tae_exam_candidate_kp";"statmuse/TokensRegexProvider";"kuroyakov/fsharp-study";"wikibus/Rdf.Vocabularies";"eugene-g/ambiata-weather";"rexcfnghk/FSharp.Backup";"cloudRoutine/VisualFSharpPowerTools";"fsprojects/VisualFSharpPowerTools";"kjnilsson/FSharp.AutoComplete";"ionide/ionide-fsi";"ionide/ionide-helpers";"jmjrawlings/SpannerFS";"BlythMeister/BingImageDowload";"frankshearar/etwas";"Giusy151/mathnet-spatial";"xdaDaveShaw/FSharp-Suave-Expecto";"lefthandedgoat/genit";"Bomret/Unit";"cloudRoutine/Forge";"isaacabraham/Paket";"MnZrK/fundcpp";"MnZrK/fdcpp";"fsprojects/FSharpx.Extras";"Bomret/NeverNull";"theor/GitShow";"smkell/fsfbl";"the-gamma/thegamma-olympics-web";"DIPSASA/dips-ckm";"fsprojects/FSharpx.Async";"NinetailLabs/Cake.PaketRestore";"mathias-brandewinder/wonderland-fsharp-katas";"endeavour/PerfectShuffle.WebsharperExtensions";"hsharpsoftware/use-case-maker";"pmbanka/kkm-reminder";"hmemcpy/Paket.VisualStudio";"enovales/FsGettextUtils";"bartelink/FunDomain";"john-patterson/FSharp.Desktop.UI";"wikibus/JsonLD.Entities";"persimmon-projects/Persimmon.Dried";"sylvanc/CamdenTown";"TheAngryByrd/OWASPPipelineSlides";"SDVentures/HostBox";"mfwilson/myriad";"larzw/Cake.Paket.Example";"OlegZee/Suave.OAuth";"endeavour/PerfectShuffle.Security";"nhsevidence/ld-compiler";"blainne/RightHandOfFate";"gjuljo/HelloSuave";"willryan/MemoryWaybackAPI";"FoothillSolutions/FunctionalEconnect";"enerqi/AlgorithmPad";"JeremyBellows/NeuralFish"
    |]

let getBootstrapperInTree (tree: TreeItem seq) =
    tree |> Seq.filter(fun item ->
        (item.Type.Value = TreeType.Blob)
        && (item.Size < 100 * 1024)
        && (item.Path = "paket.exe"
        || item.Path = "paket.bootstrapper.exe"))
        |> List.ofSeq

let getDotPaketInTree (tree: TreeItem seq) =
    tree |> Seq.tryFind(fun item ->
        (item.Type.Value = TreeType.Tree)
        && (item.Path = ".paket"))

let getBootstrapper owner name reference (client: GitHubClient) = task {
    let! (treeResponse: TreeResponse) = client.Git.Tree.Get(owner, name, "heads/" + reference)
    let direct = getBootstrapperInTree treeResponse.Tree |> List.map(fun x -> x.Path, x)
    match getDotPaketInTree treeResponse.Tree with
    | Some dotPaket ->
        let! (dotPaketTreeResponse: TreeResponse) = client.Git.Tree.Get(owner, name, dotPaket.Sha)
        let inDotPaket = getBootstrapperInTree dotPaketTreeResponse.Tree
        return direct @ (inDotPaket |> List.map(fun x -> ".paket/" + x.Path, x))
    | None -> return direct
    }

let limit = Version("5.142.0")
let cred = new Credentials((*shhh*))
use github = new GitHubClient(new ProductHeaderValue("old-paket-finder"), InMemoryCredentialStore(cred));
(task {
    for repo in repos do
        let parts = repo.Split('/')
        let user = parts.[0]
        let repoName = parts.[1]
        let! (repo: Repository) = github.Repository.Get(user, repoName)
        if repo.Fork = false then
            let defaultBranch = repo.DefaultBranch
            let! bootstrappersFound = getBootstrapper user repoName defaultBranch github

            if bootstrappersFound.Length > 0 then
                let (path, treeItem) = bootstrappersFound.Head
                let! (blob: Blob) = github.Git.Blob.Get(user, repoName, treeItem.Sha)
                let fileBytes = Convert.FromBase64String(blob.Content)
                File.WriteAllBytes(@"C:\temp\paket_temp.exe", fileBytes)
                let verInfo = FileVersionInfo.GetVersionInfo(@"C:\temp\paket_temp.exe")
                let v = Version(verInfo.FileVersion)
                if v < limit then
                    printfn "%s,%s,%s,%s" user repoName path (verInfo.FileVersion)
}).Wait();

I just checked the list to see which of my repositories came up, and I think the query may be a bit off.
For example https://github.com/TeaDrivenDev/BranchDocuments doesn't exist anymore and has been renamed to https://github.com/TeaDrivenDev/Amagatsha (which is also listed).
And https://github.com/TeaDrivenDev/GjallarhornTest2 is missing, although it has a 5.132 bootstrapper (weirdly as both paket.exe and paket.bootstrapper.exe).

@forki I've put together a rough script to do all this over in https://github.com/shiftkey/paket-upgrader, and you can see it in action here: https://github.com/TeaDrivenDev/StatusPotentiae/pull/1

@forki @TeaDrivenDev and others - I'm looking for feedback on how to simplify this so others can use it and share the load, mostly around a proper CLI so that you could pass in a list of repositories or just point it at someone's account.
Also, I want to make sure that these PRs do resolve the problem before broadcasting this more broadly...

@shiftkey Works for me. I deleted the 5.142 .exe from AppData\Local\NuGet\Cache\Paket, ran the "magic mode" bootstrapper on master and got the TLS error. Bootstrapper on the PR branch correctly downloads Paket 5.142.

Yes that was my next message on the slack, Github API (via Octokit?) should be queried for each to get if it's a fork, get the size to ensure that it's not the main paket and download it to check the version

@vbfox I'd recommend using the Content API to check the SHA of the paket.exe or paket.bootstrapper.exe  rather than rely on the file size:
https://github.com/shiftkey/paket-upgrader/blob/master/PaketUpgrader/PaketUpgrader.cs#L47-L60
And the work to create a new commit through the GitHub API (avoiding the need to clone it locally) is here:
https://github.com/shiftkey/paket-upgrader/blob/master/PaketUpgrader/PaketUpgrader.cs#L178-L249
Apologies for the C#, but it was quicker for me to bash something together 😈

cool stuff. After small test I tried to run it on repositories.txt but two things:
a) everything in parallel seems to be an issue
b) I assume it hit rate limit ---> no pull request created

authors: TeaDrivenDev cdrnet eugene-g forki shiftkey vbfox

repo: fsprojects/Paket


text:
Issue with packet pack and multiple paket.template files

I discovered the issue with Paket version 1.16.0, and it is still present in the current version 1.17.0.
Details
When calling packet pack inside a multi-project solution where multiple projects have paket.template, pack selects the wrong .csproj file - see below for an example.
Reproduction steps
Given the following directory layout:
.paket/
  paket.bootstrapper.exe
  paket.exe
bin/
src/
  paket.dependencies
  ProjectA/
    ProjectA.csproj
    paket.template
  ProjectB/
    ProjectB.csproj
    paket.template

When calling:
src\ProjectB> ..\..\.paket.exe pack output . templatefile paket.template

I get the following error (note: this should use ProjectB.dll, and not ProjectA.dll!):
found: C:\<path>\src\paket.dependencies
Parsing C:\<path>\src\paket.dependencies
Loading assembly metadata for C:\<path>\src\ProjectA\..\..\bin\ProjectA.dll
Paket failed with:
        Die Datei "C:\<path>\bin\lib.SD.DefaultImplementations.dll" konnte nicht gefunden werden.
StackTrace:
     bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, S
tring msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolea
n checkHost)
   bei System.IO.File.InternalReadAllBytes(String path, Boolean checkHost)
   bei Paket.PackageMetaData.loadAssemblyId(String buildConfig, ProjectFile projectFile)
   bei Paket.PackageProcess.merged$cont@56(String buildConfig, TemplateFile templateFile, ProjectFile projectFile, OptionalPackagingInfo opt, ProjectCoreInfo md, Unit unitVar)
   bei Paket.PackageProcess.f@1-10(String buildConfig, FSharpOption`1 version, HashSet`1 allTemplateFiles, ProjectFile projectFile, TemplateFile templateFile)
   bei Paket.PackageProcess.Pack(DependenciesFile dependencies, String packageOutputPath, FSharpOption`1 buildConfig, FSharpOption`1 version, FSharpOption`1 releaseNotes, FSharpOption`1 templateFile)
   bei Paket.Program.handler@288-19.Invoke(ArgParseResults`1 results)
   bei Paket.Program.processWithValidation[T](FSharpFunc`2 validateF, FSharpFunc`2 commandF, Command command, String[] args)
   bei Paket.Program.processCommand@71-1.Invoke(Command command, String[] args)
   bei Paket.Program.main()

since you already described the repro setting. could you please create a minimal repro? It's much easier if I can just download a repro and fix right away. that would be really helpful.

I forgot my GitHub password, so I currently cannot upload things. Sorry.

The contents of the paket.template files:
type project
id ProjectA

and:
type project
id ProjectB

You can email me on sforkmann @ google

At gmail

I've uploaded a zip archive at https://github.com/cr7pt0gr4ph7/Paket/releases/download/issues%2Frepro%2F893/Paket_Issue_893.zip.

Fix confirmed. It might might sense to put up some integration tests for the command line interface, using a known input state (i.e. local package repository, known paket.template setup) and comparing it to a known output state.

Yep did integration tests a couple of months ago,  but removed them because
of bad test infrastructure. We look for volunteers who want to create a
useful integration testing lib.
On Jun 22, 2015 10:50 AM, "Lukas Waslowski" notifications@github.com
wrote:

Fix confirmed. It might might sense to put up some integration tests for
the command line interface, using a known input state (i.e. local package
repository, known paket.template setup) and comparing it to a known
output state.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/893#issuecomment-114042950.


text:
Notifications

Host treba da dobije notifikacije kada:
● Neko kreira zahtev za rezervaciju
● Neko otkaže rezervaciju
● Neko ga oceni
● Neko oceni njegov smeštaj
Guest treba da dobije notifikacije kada:
● Host odgovori na zahtev za rezervaciju

With the merge of #6 (and frontend service pr), we can consider this issue as Done.

repo: ftrip-io/notification-service


text:
Native HA streaming is not working

While webrtc is working fine, native streaming inside HA is not working. This is happening versions after 2021.10.3 as I have no issues in production setup using this version.
My dev setup is using latest one 2021.11.0.dev0 and stream popup is not showing anything other than title.

I'm getting slow boot issues, looked find for a while, starting updating via new updates and beta channel crashed since.

This entity is currently unavailable and is an orphan to a removed, changed or dysfunctional integration or device.
If the entity is no longer in use, you can clean it up by removing it.

Sorry i am not able to follow your two messages, this issue is about broken native stream functionality, are your messages related? If not, please create issue for them separately after checking if similar was created

Hi, all good, I'm going to start from scratch and see how it goes, maybe the process of upgrading the Home Assistant to new 2021 product has messed up a few processes..... Will get back to you, but out of all products so far your Eufy works...

Same behavior here, anything we can do to help debug?

Same here...

this issue is not related to add-on, but directly related to integration and how I handle internally camera entity. I am definitely missing something but I do not have any way other than tracking the functions one by one.
BUT, even though I could resolve this soon or later, I would not use native streaming functionality as it was causing memory leaks in my installation and webrtc is much more faster.

this is the log of a fresh installation. Camera has RTSP enabled and is working perfectly fine in the eufy app.
2021-11-18 17:25:47 DEBUG (MainThread) [custom_components.eufy_security] eufy_security Bedroom Terase - stream_source - start 2021-11-18 17:25:47 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "start_rtsp_livestream", "command": "device.start_rtsp_livestream", "serialNumber": "T8114P6121030CAC"} 2021-11-18 17:25:47 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait start - is_streaming 2021-11-18 17:25:47 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 0 - is_streaming False 2021-11-18 17:25:47 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:48 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 1 - is_streaming False 2021-11-18 17:25:48 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 2 - is_streaming False 2021-11-18 17:25:48 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:49 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 3 - is_streaming False 2021-11-18 17:25:49 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 4 - is_streaming False 2021-11-18 17:25:49 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:50 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 5 - is_streaming False 2021-11-18 17:25:50 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 6 - is_streaming False 2021-11-18 17:25:50 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:51 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 7 - is_streaming False 2021-11-18 17:25:51 DEBUG (MainThread) [custom_components.eufy_security] eufy_security Bedroom Terase - camera_image -https://zhixin-security-eu.s3.eu-central-1.amazonaws.com/thumb/2021/10/10/station/T8010P2320503511/fdZqNEOZHLMGhWUW./camera00_20211010153021.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJYLV2KOLW6PU4FSA%2F20211118%2Feu-central-1%2Fs3%2Faws4_request&X-Amz-Date=20211118T152236Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=05cde5f3967c5d4a6eaf7bd55883043c2449c7b7ac8aac5bd901b97ced7ce2cd - 17173 2021-11-18 17:25:51 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 8 - is_streaming False 2021-11-18 17:25:51 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:52 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 9 - is_streaming False 2021-11-18 17:25:52 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 10 - is_streaming False 2021-11-18 17:25:52 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:53 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 11 - is_streaming False 2021-11-18 17:25:53 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 12 - is_streaming False 2021-11-18 17:25:53 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:54 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 13 - is_streaming False 2021-11-18 17:25:54 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 14 - is_streaming False 2021-11-18 17:25:54 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:55 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 15 - is_streaming False 2021-11-18 17:25:55 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 16 - is_streaming False 2021-11-18 17:25:55 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:56 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 17 - is_streaming False 2021-11-18 17:25:56 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 18 - is_streaming False 2021-11-18 17:25:56 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:57 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 19 - is_streaming False 2021-11-18 17:25:57 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 20 - is_streaming False 2021-11-18 17:25:57 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:58 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 21 - is_streaming False 2021-11-18 17:25:58 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 22 - is_streaming False 2021-11-18 17:25:58 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:25:59 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 23 - is_streaming False 2021-11-18 17:25:59 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 24 - is_streaming False 2021-11-18 17:25:59 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data 2021-11-18 17:26:00 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - wait - 25 - is_streaming False

Any logs from add on?

eufy.txt

Can you tell your add on version? it should be 0.5.3
On Thu, Nov 18, 2021, 17:33 leonardpitzu @.***> wrote:

eufy.txt
https://github.com/fuatakgun/eufy_security/files/7564384/eufy.txt
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/eufy_security/issues/102#issuecomment-973034893,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUSN7UGU2FLFHUBD4HV5VLUMUTETANCNFSM5HPSP3CA
.

i think its 0.3.3

edit: updated to latest and switched to webrtc and it works!!!

Let's keep this issue related to native ha streaming, for separate issues, we can track with individual issues.

OK, so after some hours (over night) the streaming_source_address and streaming_source_type sensors become empty and streaming_sensor remains false no matter what i do. If i restart the docker container (running :latest) and wait a bit in HA it all comes back. I am now checking to see how long does it have to be in idle for the sensors to disappear.
current log:
eufy.txt

fixed now.

authors: MackPit fabianluque fuatakgun jontemalm leonardpitzu