Update set-up-git.md

title: Set up Git
redirect_from:

/git-installation-redirect/
/linux-git-installation/
/linux-set-up-git/
/mac-git-installation/
/mac-set-up-git/
/set-up-git-redirect/
/win-git-installation/
/win-set-up-git/
/articles/set-up-git
/github/getting-started-with-github/set-up-git
/github/getting-started-with-github/quickstart/set-up-git
intro: 'At the heart of {% data variables.product.product_name %} is an open source version control system (VCS) called Git. Git is responsible for everything {% data variables.product.product_name %}-related that happens locally on your computer.'
versions:
fpt: ''
ghes: ''
ghae: '*'
topics:
Pull requests
Issues
Notifications
Accounts

Using Git
To use Git on the command line, you'll need to download, install, and configure Git on your computer. {% ifversion fpt or ghes or ghae %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. For more information on {% data variables.product.prodname_cli %}, see the {% data variables.product.prodname_cli %} documentation.{% endif %}
If you want to work with Git locally, but don't want to use the command line, you can instead download and install the [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) client.  For more information, see "Installing and configuring {% data variables.product.prodname_desktop %}."
If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including:

Creating a repository
Forking a repository
Managing files
Being social

Setting up Git

Download and install the latest version of Git.
Set your username in Git.
Set your commit email address in Git.

Next steps: Authenticating with {% data variables.product.prodname_dotcom %} from Git
When you connect to a {% data variables.product.product_name %} repository from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH.
Connecting over HTTPS (recommended)
If you clone with HTTPS, you can cache your {% data variables.product.prodname_dotcom %} credentials in Git using a credential helper.
Connecting over SSH
If you clone with SSH, you must generate SSH keys on each computer you use to push or pull from {% data variables.product.product_name %}.
Celebrate
Congratulations, you now have Git and {% data variables.product.product_name %} all set up! You may now choose to create a repository where you can put your projects. This is a great way to back up your code and makes it easy to share the code around the world. For more information see "Create a repository".
You can create a copy of a repository by forking it and propose the changes that you want to see without affecting the upstream repository. For more information see "Fork a repository."
Each repository in {% data variables.product.product_name %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "Be social."
{% data reusables.support.connect-in-the-forum-bootcamp %}

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[x] I have added the 'writer impact' label
[x] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

https://github.com/github/docs/pull/7813#issuecomment-871006835

https://github.com/github/docs/pull/7813#issuecomment-871006835

https://github.com/github/docs/pull/7813#issuecomment-871006835

title: Set up Gitredirect_from: - /git-installation-redirect/ - /linux-git-installation/ - /linux-set-up-git/ - /mac-git-installation/ - /mac-set-up-git/ - /set-up-git-redirect/ - /win-git-installation/ - /win-set-up-git/ - /articles/set-up-git - /github/getting-started

https://github.com/github/docs/pull/7813#issuecomment-871006835

Hey
welcome[bot] @.***> schrieb am Mi., 30. Juni 2021,
02:24:

Thanks for opening this pull request! A GitHub docs team member should be
by to give feedback soon. In the meantime, please check out the contributing
guidelines https://github.com/github/docs/blob/main/CONTRIBUTING.md.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/7813#issuecomment-871006835, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AURRVLXP7QGIO7O7KXSMO5TTVJP5JANCNFSM47RICZBQ
.


Issue #140 changed send value so Config properties are readed clearly

Send value is changed to true so as to have by default if Send is true to send information to Segment server. Also, changed set of IRequestHandler so if Send is true then is set to the RequestHandler that calls segment rest API

Pull request is closed, needs to be merged first to master of another repository


Implemented simple design of app and take out background

Fixes #304
Changes:
Changes the background colors to simple white color.
Screenshots for the change:

@mariobehling @chashmeetsingh @SIMRAN1 @Akshat-Jain @arundhati24 @batbrain7 @DNS-404 @hkedia321 @akshatnitd please review PR!

Please resolve conflicts. Thanks.

@mariobehling @chashmeetsingh Please merge!


Remove over logging in the pool manager

fixes #728 Remove over logging in the pool manager. Add log4s configuration for the blaze-client test.

Deleted

Cherry-picked and merged to master.  Thanks!


Add support for jsmin PHP extension or via Composer

Follows markstory/asset_compress#236

Coverage remained the same at 84.14% when pulling 9bcd2e0e51cca3fc1729250692c78ce6f8bea823 on deizel:jsmin into 966780d00c6b33b97e3acd5a4da5ce78f57710d0 on markstory:master.

Thanks :+1:


treewide: fix typos around "compatible" and "compatibility"

Description of changes
Perhaps the lowest-priority PR ever. Concocted by reading lib code, seeing a typo, and guessing that there were more out there.
Things done

[x] nixpkgs-review rev HEAD (no rebuilds)
[x] Fits CONTRIBUTING.md.

I have no idea why this rebuilds the darwin stdenv but not linux. I'm excited to learn more!

I have no idea why this rebuilds the darwin stdenv but not linux. I'm excited to learn more!

the modification to  pkgs/os-specific/darwin/apple-source-releases/libdispatch/default.nix most likely.

I have no idea why this rebuilds the darwin stdenv but not linux. I'm excited to learn more!

the modification to pkgs/os-specific/darwin/apple-source-releases/libdispatch/default.nix most likely.

You know, that checks out. Specifically the part about a typo in a shell script in installPhase rather just in the .nix file.


Feature/issue 1426 ibeta derivs large args

Summary:
Dramatically improves the robustness and performance of the regularized incomplete beta function derivatives, propagating the chances to neg_binomial_cdf and neg_binomial_2_cdf.  Changes still need to be propagated to beta_cdf, student_t_cdf, and others.
Intended Effect:
neg_binomial_cdf and neg_binomial_2_cdf gradients are now accurate for large arguments.
How to Verify:
./runTests.py src/test/prob/neg_binomial
./runTests.py src/test/prob/neg_binomial_2
Or build a crazy model using neg_binomial_cdf or neg_binomial_2_cdf with large arguments.
Side Effects:
None.  Performance should actually improve with the added checks that switch to different expansions for different arguments.
Documentation:
None.
Reviewer Suggestions:
None.

@syklic Are these fine?  I ran cpplint on the new/modified stuff before
the pull request and it passed (or rather I deleted a lot of
automatically-indented whitepspace until it passed).
On Apr 30, 2015, at 12:03 AM, Stan buildbot<EMAIL_ADDRESS>wrote:

Refer to this link for build results (access rights to CI server needed):
http://d1m1s1b1.stat.columbia.edu:8080/job/Stan Pull Request/352/
Build Log
last 20 lines
[...truncated 16 lines...]
Starting build job Stan Pull Request - Doc - Doxygen.
Starting build job Stan Pull Request - Doc - Reference Manual.
Finished Build : #346 of Job : Stan Pull Request - Doc - Reference Manual with status : SUCCESS
Finished Build : #352 of Job : Stan Pull Request - Doc - Doxygen with status : SUCCESS
Starting build job Stan Pull Request - Tests - Unit.
Starting build job Stan Pull Request - Tests - Integration.
Starting build job Stan Pull Request - Windows - Tests - Unit.
Starting build job Stan Pull Request - Tests - Header.
Finished Build : #318 of Job : Stan Pull Request - Tests - Header with status : SUCCESS
Finished Build : #320 of Job : Stan Pull Request - Tests - Integration with status : SUCCESS
Finished Build : #166 of Job : Stan Pull Request - Windows - Tests - Unit with status : SUCCESS
Finished Build : #320 of Job : Stan Pull Request - Tests - Unit with status : SUCCESS
Starting build job Stan Pull Request - CppLint.
Starting build job Stan Pull Request - Math Dependencies.
Finished Build : #72 of Job : Stan Pull Request - Math Dependencies with status : SUCCESS
Finished Build : #113 of Job : Stan Pull Request - CppLint with status : FAILURE
Build step 'MultiJob Phase' marked build as failure
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Setting status of 7e8db1c6f666c8fce2ad0d7b249c8981400bc759 to FAILURE with url http://d1m1s1b1.stat.columbia.edu:8080/job/Stan Pull Request/352/ and message: Merged build finished.
Test FAILed.
—
Reply to this email directly or view it on GitHub.

@betanalpha, could you add some basic tests for:

[ ] ddz_inc_beta
[ ] ddb_inc_beta
[ ] dda_inc_beta

that can go in src/test/unit/math/prim/scal/fun/inc_beta_derivatives.hpp for now. All we would need is a double-based test to go there, unless this is used for stan::agrad::var also.
Or, you can just give me reasonable values for each of the values just so we can instantiate these functions stand-alone and get reasonable values out.
I'll add some more comments in the code itself.

Double test added.
On May 4, 2015, at 4:09 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

@betanalpha, could you add some basic tests for:
ddz_inc_beta
ddb_inc_beta
dda_inc_beta
that can go in src/test/unit/math/prim/scal/fun/inc_beta_derivatives.hpp for now. All we would need is a double-based test to go there, unless this is used for stan::agrad::var also.
Or, you can just give me reasonable values for each of the values just so we can instantiate these functions stand-alone and get reasonable values out.
I'll add some more comments in the code itself.
—
Reply to this email directly or view it on GitHub.

Final needs (I'll take care of it):

[ ] split apart functions to own files
[ ] split apart tests appropriately

@betanalpha: the functions are missing documentation. I'll start filling stuff in, but might need your help. The incomplete beta derivatives have been renamed and moved to:

src/stan/math/prim/scal/fun/inc_beta_dda.hpp
src/stan/math/prim/scal/fun/inc_beta_ddb.hpp
src/stan/math/prim/scal/fun/inc_beta_ddz.hpp

Gimme an example of what you want.
On May 11, 2015, at 12:53 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

@betanalpha: the functions are missing documentation. I'll start filling stuff in, but might need your help. The incomplete beta derivatives have been renamed and moved to:
src/stan/math/prim/scal/fun/inc_beta_dda.hpp
src/stan/math/prim/scal/fun/inc_beta_ddb.hpp
src/stan/math/prim/scal/fun/inc_beta_ddz.hpp
—
Reply to this email directly or view it on GitHub.

@betanalpha, I added some doc, but I feel like it's wrong. Feel like taking a look? What I really wanted to add was something that indicated where it is expected not to work.

How's that?


LeetCode Binary Tree Questions

.98. Validate Binary Search Tree
.112. Path Sum

sure

Hey, @neolia-monu  I have quite a good hands-on knowledge of JAVA and I have done this Path Sum code. Please appoint me to the project.

Hey @Vanshika2063 I added a code on binary tree in #243

@satyamgupta461  Okay

Are we looking for Java solutions only or we can add Python ones also?

Assign me this issue, i will able to add some good question


Source map support

Inline and external source-map support is very much needed (f.e. when using preprocessors). Is there currently an official way to use source maps so that the line numbers of my errors (the very things that jest revolves around) are meaningful?

Any way to do this yet? Following suggestions from:
http://marmelab.com/blog/2015/06/24/jest-in-practice.html
<EMAIL_ADDRESS>I took out the "scriptPreprocessor" so that I could manually watch for changes using babel-cli. Is it possible to use inlined source maps from babel yet in jest?

I'm going to assume that this should probably work with babel. I'm going to close this as babel has a retainLines option that we are using in babel-jest and at FB we are currently unlikely to use another compile-to-JS language that needs this feature. Is there a reason why you'd want source maps if you know the exact line number of when something is failing?
I also appreciate contributions to babel-jest (see the packages/ folder) that improve support here.

I'm using typescript & jest reports the JS line numbers. Is there a workaround? Thx!

A feature to preserve line numbers in typescript was specifically rejected because they already produce source maps: https://github.com/Microsoft/TypeScript/issues/3142

@cpojer There is a reason for adding source map support: codecov.io doesn't support coverage reports for files not checked into source control. I tried using remap-istanbul, but it couldn't resolve the original source paths correctly.

I was finally able to solve this issue. See felipeochoa/jest-sourcemaps for the details. (It's not pretty, but it works!)

@cpojer I was poking around the refactoring you did in #3376 and #3388 and was excited to see that source maps are cleanly handled when coverage is enabled! Is the plan to allow saving source maps independently of whether coverage is enabled? It seems to me that simply removing the else clause in line 227 and  the instrument && mapCoverage on line 241 would be enough to let transformer authors specify sourcemaps.
A current limitation of the jest-sourcemaps approach is that I can't cache source maps, so having this built-in with jest would be amazing!

@felipeochoa I have no smart thoughts on this to be honest, so feel free to send a pull request with the changes and with tests and we'll see where can take it.

So, jest's support for source maps is currently limited to coverage only? If I write a custom preprocessor that extracts inline source maps for TypeScript I get accurate code coverage on my .ts files, but whenever I throw an exception the lines in the stack trace are completely wrong.

I've managed to use remap-istanbul with TypeScript, this should work with other transpilers. I could get Codecov and Code Climate to work with this.
Here the explanations: https://github.com/codecov/example-typescript/issues/7

Copy-paste for history:
What you need to change in your code for it to work: https://github.com/tkrotoff/ReactFormWithConstraints/commit/b5817829141ea6b28e77a8eeaa6bdb1571dc495c

Configure TypeScript to generate the source maps by adding "sourceMap": true to your tsconfig.json
Configure Jest so that it generates only coverage-final.json thanks to "coverageReporters": ["json"]. By default Jest generates everything including the HTML report (lcov-report) and lcov.info
Then use remap-istanbul to rewrite coverage-final.json using the source maps
And finally istanbul report to generate the right HTML report (lcov-report) and lcov.info from the correct coverage-final.json

This blog post: https://medium.com/@novemberborn/code-coverage-with-babel-istanbul-nyc-83b8c2f1093 allowed me to understand.

@tkrotoff  Thanks for your help,  you definitely have moved me in the right direction but my istanbul coverage report still shows the incorrect umber of lines.

while the actual lines in the file are:

Any help would be greatly appreciated.

@sean-killeen you should use ts-jest, no need for remap-istanbul: ts-jest now fully works, including vscode breakpoints

I actually started with ts-jest originally and have been getting an error with istanbul-lib-coverage when using it.

at CoverageMap.fileCoverageFor (node_modules/istanbul-lib-coverage/lib/coverage-map.js:96:15)
at Array.forEach ()

There is an open issue on this with ts jest here

Jest should fully support sourcemaps out of the box now, as long as they are either inline or the transformer returns it (meaning we don't look up external sourcemaps).
@sean-killeen could you provide a repro of your issue?

@SimenB I think this is an open issue with React 16 and Node 8.  I found this which I think is the same issue.  What I am getting is coverage but with incorrect line numbers.  looks the the numbers are generated from the transpiled source code that isn't source-mapped.

Is there a conversation somewhere about why jest does not support external source maps? With all that's baked in, I somewhat expected this and the workarounds to get support seem much heavier than other test runners (see https://github.com/facebook/jest/issues/2205#issuecomment-376222735).

PR welcome! We support inline sourcemaps, should be possible to support external as well.

Jest should fully support sourcemaps out of the box now, as long as they are either inline or the transformer returns it (meaning we don't look up external sourcemaps).

@SimenB How does Jest support sourcemaps? (I was expecting to see in babel-jest something like in felipeochoa/jest-sourcemaps, ie calling babel.transform with {sourceMap: true}, and passing these outputed sourcemaps to node-source-map-support).

Did you answer your own question? We might want to document how to utilise sourcemaps in Jest, but I'm not sure where to put it. It works out of the box, but custom transforms have to support it explicitly (by returning code and map properties

@chase-moskal  youp 🍺 inline source map in tsconfig.json compiler options solve the problem !
// ...
"sourceMap": true,
"inlineSourceMap": true,


Adding CC-100: Monolingual Datasets from Web Crawl Data

Adding a Dataset

Name: CC-100: Monolingual Datasets from Web Crawl Data
Description: https://twitter.com/alex_conneau/status/1321507120848625665
Paper: https://arxiv.org/abs/1911.02116
Data: http://data.statmt.org/cc-100/
Motivation: A large scale multi-lingual language modeling dataset. Text is de-duplicated and filtered by how "Wikipedia-like" it is, hopefully helping avoid some of the worst parts of the common crawl.

Instructions to add a new dataset can be found here.

cc @aconneau ;)

These dataset files are no longer available.  https://data.statmt.org/cc-100/ files provided in this link are no longer available. Can anybody fix that issue?
@abhishekkrthakur @yjernite

Hi ! Can you open an issue to report this problem ? This will help keep track of the fix :)

Ok


Perceived Inconsistencies

what

Identify and address inconsistencies

why

we cannot begin to standardize something which is inconsistent.

When do variables go in the Dockerfile vs somewhere else? e.g. .tfvar file or .envrc?

Why are some variables prefixed with TF_VAR_ but not others?

Needing to have some env vars set in the dockerfiles during cold start and others set empty or not set is very unintuitive

There's kind of a discrepancy between the expectation of running make docker/build locally, vs pulling down an image. When would we pull down an image and run from that vs building locally and running?

Also the needing to comment out assume role in the root dockerfile while also then using sed to comment out the backend in the same file makes me sad.
https://unix.stackexchange.com/questions/26284/how-can-i-use-sed-to-replace-a-multi-line-string
Is what I would look at, though have not as yet done so

Also the needing to comment out assume role in the root dockerfile while also then using sed to comment out the backend in the same file makes me sad.

Hah, me too. Just to be precise, are you referring to this? https://github.com/cloudposse/terraform-root-modules/blob/master/aws/tfstate-backend/scripts/init.sh

The issues raised here have been addressed in the following PRs:

https://github.com/cloudposse/reference-architectures/pull/1
https://github.com/cloudposse/reference-architectures/pull/2
https://github.com/cloudposse/geodesic/pull/330
https://github.com/cloudposse/geodesic/pull/332
https://github.com/cloudposse/geodesic/pull/335
https://github.com/cloudposse/terraform-root-modules/pull/70
https://github.com/cloudposse/terraform-root-modules/pull/69
https://github.com/cloudposse/terraform-root-modules/pull/68
https://github.com/cloudposse/terraform-root-modules/pull/67
https://github.com/cloudposse/terraform-root-modules/pull/66
https://github.com/cloudposse/terraform-root-modules/pull/64
https://github.com/cloudposse/terraform-root-modules/pull/63
https://github.com/cloudposse/terraform-root-modules/pull/61
https://github.com/cloudposse/terraform-root-modules/pull/60
https://github.com/cloudposse/terraform-root-modules/pull/56

Basically, we've made the following wide sweeping changes

Radically reduce the number of environment variables that need to be set
Allow environment variables to be consistently named (e.g. with TF_VAR_ prefix) by using tfenv
Do not default to sticking environment variables in the Dockerfile as it is overwhelming and not clear what projects consume them
Rely on .tfvar files for terraform settings (non-secrets); b/c defining maps and lists in envs for terraform as environment variables is ugly/error prone and seldom need to be used outside of terraform
Rely on .envrc (aka direnv) for all other project settings
Use terraform remote state to reduce env passing / hardcoding

@jdn-za closing this issue. We can open up new issues if you find other inconsistencies. The "cold start" automation exercise in the reference-architectures projects forced us to adopt some extreme consistency.


Create a models.ts to mimic Rucio types

Description
The data fetched from the server should be parsed into TypeScript classes.
Motivation
No response
Change
Create a new models.ts file. Add models for Account, Rule types.
Additional Information

[ ] The Rucio API needs to be changed.

https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#differences-between-type-aliases-and-interfaces

Closed as a part of #90


How to check /tf_static tree with Cyber RT?

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04):
Apollo installed from (source or binary):
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0):

Hello all,
I am using Apollo 3.5 and Apollo 5.0.
I have problems regarding that the pose cannot be get when I launch the perception module.
How I can check the tree of /tf_static or /tf with Cyber RT framework?

See if this is what you need https://github.com/ApolloAuto/apollo/blob/bf2b3730835fd5a98f91a5fb00f9d82ef750be9d/docs/cyber/CyberRT_Developer_Tools.md#cyber_monitor


SQL Assistant is not working on versio 23.1.0

Description
For some unknow reason my saved scripts are not working with SQL Assistant. When I try a new one it works:

But when trying in the old one:

I've tried to change the charset but no lucky.
DBeaver Version
23.1.0
Operating System
Windows 11
Database and driver
Database driver: mysql8 (com.mysql.cj.jdbc.Driver)
Steps to reproduce

Open saved script (which was working on version 23.0.5).
Try to use auto-complete (SQL Assistant) on an aliased table.

Additional context
No response

Could you try turning off Enable experimental feature setting?

Thank you Elizabeth. I had not look into this option and it is, indeed, marked:

Unchecking it and it is now working! Thank you!!

#20199

@nataklug could you provide SQL sample to reproduce the issue?

@nataklug could you provide SQL sample to reproduce the issue?

Hello @uslss. I am not using that version anymore and after @E1izabeth tip it is working fine with no more problems. To reproduce the problem I had some saved scripts on my computador, most of them made in an old version of DBeaver, with encoding as ISO-8859-1 (I have no idea if this is important). When I opened it on the version 23.1.0 with Experimental marked I was not able to use SQL Assistant. The first thing I made was migrating them to UTF-8. No luck. After that I tried re-writen the code and as it grows more difficult was to SQL Assistant work. I attached one of this scripts but I don't think you will be able to reproduce but you can see the joins I made.
EXP0003_cancelamento.zip

Thanks for bug report!

We made some improvements recently. Please try our latest version to see if this issue is still actual with Enable experimental features on.

@E1izabeth sure, I will try and if I find some error I will let you know. Thank you for the efforts.

Looks like it is working:


.gdignore does not exclude C# scripts from build

Godot version
3.4.2.stable.mono
System information
MacOS (M1)
Issue description
After adding an empty .gdignore file to a folder, C# scripts are still being included when I build the project.
More specifically, I am trying to create a project-defined C# template according to the docs. The project encounters errors while being built because I added the %CLASS% placeholder to the template script. My current workaround is to add a . in front of the folder name because apparently, that excludes the folder from being included in the build.
Steps to reproduce

Create a new project
Create a new folder named script_templates
Create a new C# script in script_templates
Change the class name to %CLASS%
Create a new file in script_templates named .gdignore
Build the project in Godot (click button on top right corner)

Minimal reproduction project
No response

.gdignore only prevents resource importing. I don't think it was ever special-cased to ignore C# scripts located within a folder.

You can exclude them by adding the following to your .csproj project file:
<ItemGroup>
    <Compile Exclude="script_templates/*.cs" />
</ItemGroup>

Otherwise, some IDEs have the option to exclude a folder when you right-click it.
This should probably be added to that doc page.
I don't think we can support this automatically out of the box because the doc page says the location can be overridden via the project setting editor/script_templates_search_path.

@neikeq thanks for the tip!
I tried the solution you mentioned but it gave the error, Items that are outside Target elements must have one of the following operations: Include, Update, or Remove. However, after changing Exclude to Remove, it seems to be working now and ignoring the template files.

@neikeq thanks for the tip!
I tried the solution you mentioned but it gave the error, Items that are outside Target elements must have one of the following operations: Include, Update, or Remove. However, after changing Exclude to Remove, it seems to be working now and ignoring the template files.

Oops, sorry. Yes, it's <Compile Remove=.

Oops, sorry. Yes, it's <Compile Remove=.


reduce repo size

generally we might just reduce the repo size (i.e., remove catalogs, since the module can build catalogs)...
Chris even mentioned it in his review, which i have turned into an issue: https://github.com/UNCG-DAISY/psi-collect/issues/86
I know our the JOSS bot had troubles building the paper because the repo was big (see the review issue).. originally I wanted the catalog to be in the repo for search features, but that enhancement is a bit downstream.
@Matmorcat , are you ok if the catalogs are removed?

Yes, I was thinking eventually, for neatness sake, the archives would be available to the program to download via the downloading tool.
It is a bit unorthodox to have the generated catalogs distributed with the code, but having the catalogs available (which they are on the fig-share site) is crucial for people who don't want to have to download all the archives to see data that has already been discovered before!

@Matmorcat — ok, so i can move the archives to a seperate place (likely another github repository). It's a good point that it's helpful for people who may want to know what is available w/o downloading all the files (saying this as my work computer has spent 2 fulls days of downloading just the florence archives to a local computer 😆 )..
also btw — The catalogs are not in the figshare repository (only the tags)..
I can remove them tommorrow and then close this issue.

Also, you should look at BFG Repo-Cleaner to help remove the large files from the git history. If you don't, even if you delete them, they will still be in the history and the repo will still be large.

i removed the catalogs. I am a bit scared of dealing with the git history..  if someone else wants to be brave, feel free... otherwise i will leave it for now out of fear.

I had a go at cleaning the history, but couldn't push it back to the repo due to permissions. Someone else can run these commands and clean the history. You'll need a bit of a workaround since you can't specify the full path with BFG though. More details on the bfg page. Good luck if you decide to try this!
In the repo, use git rev-list and grep to get the id's of the blobs for files in the data/ folder.
ADUNSW+z5189959@leaman /c/Users/z5189959/Desktop/psi-collect (master)
λ git rev-list --all --objects -- data/ | git cat-file --batch-check='%(objectname) %(objecttype) %(rest)' | grep -Pe '^\w+ blob'
cec3538275cca7bea6c998590302f45904c9f5f0 blob data/catalogs/v1/Barry.csv
1eac7b4385131655a690e55361044cab575dfa75 blob data/catalogs/v1/Dorian.csv
74642417717fd491749e59c6cd8de492b3501b68 blob data/catalogs/v1/Florence.csv
21ada943f02b382f4fb1e6c7532baa3021793ac9 blob data/catalogs/v1/Gordon.csv
e6c6c2ef86129f7900ed4b780758ab83541fe6dc blob data/catalogs/v1/Michael.csv
2be642a6fe5cd81905e99dfc638c112c44783b28 blob data/catalogs/v1/catalog.csv
36b352d9fe1462bf8eec21e7947b90949a119134 blob data/catalogs/v2/Barry.csv
7bf96b962096aad61eafd4f0e023d22eb5574784 blob data/catalogs/v2/Dorian.csv
8c9d90f0fb43e4d4358291150fd8462218801a93 blob data/catalogs/v2/Florence.csv
42ea780c631145d7f3af24e13324db07be242185 blob data/catalogs/v2/Gordon.csv
bfbfebbc5a530a36a90f8bc9a09b02d64d6e6eae blob data/catalogs/v2/Michael.csv
2d5e14790ef2568033a9923e34de942f0a041c5a blob data/catalogs/v2/global.csv
660c8411912549a9207ee07aba1d8c3bab8bd4b8 blob data/archive_cache/.gitignore
2c8aba9f47c3ac3ea1c5896913ba2daaa50b13f3 blob data/input/.gitignore

Save these blobs to ./to-delete.txt:
ADUNSW+z5189959@leaman /c/Users/z5189959/Desktop/psi-collect (master)
λ git rev-list --all --objects -- data/ | git cat-file --batch-check='%(objectname) %(objecttype) %(rest)' | grep -Pe '^\w+ blob' | cut -d' ' -f1 > ./to-delete.txt

Run BFG to remove the blobs specified in ./to-delete.txt:
ADUNSW+z5189959@leaman /c/Users/z5189959/Desktop/psi-collect (master)
λ java -jar bfg.jar --no-blob-protection --strip-blobs-with-ids ./to-delete.txt

Using repo : C:\Users\z5189959\Desktop\psi-collect\.git

Found 0 objects to protect
Found 2 tag-pointing refs : refs/tags/v1.0.1, refs/tags/v1.0.2
Found 13 commit-pointing refs : HEAD, refs/heads/master, refs/remotes/origin/HEAD, ...

Protected commits
-----------------

You're not protecting any commits, which means the BFG will modify the contents of even *current* commits.

This isn't recommended - ideally, if your current commits are dirty, you should fix up your working copy and commit that, check that your build still works, and only then run the BFG to clean up your history.

Cleaning
--------

Found 1843 commits
Cleaning commits:       100% (1843/1843)
Cleaning commits completed in 6,814 ms.

Updating 13 Refs
----------------

        Ref                                                             Before     After
        -----------------------------------------------------------------------------------
        refs/heads/master                                             | e4e74ef0 | 5ec3d826
        refs/remotes/origin/dependabot/pip/markdown-3.2.1             | 2a9d6289 | f9b5c8e2
        refs/remotes/origin/dependabot/pip/mkdocs-minify-plugin-0.2.3 | 8305e907 | a2758b00
        refs/remotes/origin/master                                    | e4e74ef0 | 5ec3d826
        refs/tags/v0.3.0                                              | 10a41fb4 | 7faddc8b
        refs/tags/v0.4.0                                              | a8fd0a51 | c9d9fc4b
        refs/tags/v0.4.1                                              | aab4bc14 | 82626417
        refs/tags/v0.5.0                                              | ca8b468e | ea390ab3
        refs/tags/v0.5.4                                              | 86c6d2ca | 5e1a568d
        refs/tags/v0.6                                                | e238bcff | 68284948
        refs/tags/v1.0.0                                              | 9f977c6b | 6398ef7a
        refs/tags/v1.0.1                                              | b3d261b0 | 4f1b2073
        refs/tags/v1.0.2                                              | 0fe90084 | 0415bbc6

Updating references:    100% (13/13)
...Ref update completed in 59 ms.

Commit Tree-Dirt History
------------------------

        Earliest                                              Latest
        |                                                          |
        DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

        D = dirty commits (file tree fixed)
        m = modified commits (commit message or parents changed)
        . = clean commits (no changes to file tree)

                                Before     After
        -------------------------------------------
        First modified commit | 4f2ec0c4 | 24dfd2cc
        Last dirty commit     | 2a9d6289 | f9b5c8e2

Deleted files
-------------

        Filename                               Git id
        -------------------------------------------------------------------------------
        .gitignore                           | 2c8aba9f (48 B), 660c8411 (49 B)
        Barry.csv                            | 36b352d9 (2.2 MB), cec35382 (1.7 MB)
        Dorian.csv                           | 7bf96b96 (3.2 MB), 1eac7b43 (2.2 MB)
        Florence.csv                         | 8c9d90f0 (7.7 MB), 74642417 (5.5 MB)
        Gordon.csv                           | 21ada943 (387.7 KB), 42ea780c (523.7 KB)
        Michael.csv                          | bfbfebbc (2.4 MB), e6c6c2ef (1.8 MB)
        catalog for image pixel and size.csv | 2be642a6 (12.2 MB)
        catalog.csv                          | 2be642a6 (12.2 MB)
        global.csv                           | 2d5e1479 (16.4 MB)

In total, 3694 object ids were changed. Full details are logged here:

        C:\Users\z5189959\Desktop\psi-collect.bfg-report\2020-02-14\07-52-35

BFG run is complete! When ready, run: git reflog expire --expire=now --all && git gc --prune=now --aggressive

--
You can rewrite history in Git - don't let Trump do it for real!
Trump's administration has lied consistently, to make people give up on ever
being told the truth. Don't give up: https://www.aclu.org/
--

Prune the history:
ADUNSW+z5189959@leaman /c/Users/z5189959/Desktop/psi-collect (master)
λ git reflog expire --expire=now --all && git gc --prune=now --aggressive
Enumerating objects: 24526, done.
Counting objects: 100% (24526/24526), done.
Delta compression using up to 8 threads
Compressing objects: 100% (23323/23323), done.
Writing objects: 100% (24526/24526), done.
Total 24526 (delta 10727), reused 11729 (delta 0)
Removing duplicate objects: 100% (256/256), done.

Push back the repo:
git push


Add methods to NodeAPI for signmessage and checkmessage

It would be great if the NodeAPI could expose methods to perform signmessage and checkmessage on the Greenlight node.
https://lightning.readthedocs.io/lightning-checkmessage.7.html
https://lightning.readthedocs.io/lightning-signmessage.7.html

Even though I originally asked about this because of LNURL-auth, I think there are still several other use cases where it would be nice to at least sign a message, so that a 3rd party service can verify you are in control of the node. I rough example would be embedding a 3rd party web service (like an exchange) into an application using WebLN.

FYI the endpoints are disabled. I've tried signing the mesage in a variety of ways, but all result in the wrong pubkey. I've posted about this in the greenlight chat. Let's see what comes next week.

Fixed in https://github.com/breez/breez-sdk/pull/319


minimalmodbus.NoResponseError: No communication with the instrument (no answer)

Hello  I have kinco ac servo fd124s driver and I can not use it with this code as well
here is my error
I used RS485 to USB converter
minimalmodbus.NoResponseError: No communication with the instrument (no answer)

Can you set the baud rate to 115200 in servo driver rs485 communication settings and try again? Because in my code I have fixed the communication rate. however you also need to find which COM port the RS485 to USB is connected. This you can check in the windows device manager.

@rikhsitlladeveloper  has the problem been resolved? If you experience any other problems regarding this library you may open another issue. As of this I am assuming it resolved due to inactivity. Thank you.


TokenNetwork - 2 nodes can have maximum 1 channel

fixes https://github.com/raiden-network/raiden-contracts/issues/40
Structural changes for limiting the number of channels between two nodes to 1.

Reviewing this PR.

I am satisfied by the changes. PR approved.


Introducing global tests that are not specific to a certain service

This crazy idea came to me while doing an internal pentest with many Windows hosts => many open crazy ports, and the fact that celerystalk ignores not supported predefined services (as also noted in the source comments ;-))
To put it short:
I might want to run testssl.sh against all services that speak SSL/TLS, but this is not directly obvious with different service names/banners, so what I did was writing a one-liner bash command that go over a list of hostnames/domains in scope, do an nmap scan and export in greppable format using -oG then with grep and awk I took only the identified ports and did a timed openssl s_client ... against the host:port then I grepped for ----BEGIN CERTIFICATE---- and when that was found I ran testssl.sh against the host:port and saved the output somewhere.
The one-liner works, but I might as well integrate it in celerystalk, the only problem is.. there is no way to do that.
Perhaps there are other use-cases (see for instance #14) that could use such a feature, so my suggestion would be to extend the flexibility offered by the ini-parser to add a section of tools that are executed against each host
[w00t]
tool1: one_liner_to_execute
tool2: one_liner_or_script_to_execute
...

or another way to do it would be to add a command line option to celerystalk, like --w00t tool1,tool2,... where users can ask celerystalk to execute those instead of the the traditional tests, or perhaps in addition to them.
Cheers

You know what's funny? I already do have a "catch all" command that runs a basic nmap scan with default scripts against any service not in the supported service list, but this is hardcoded.  Moving it to the ini is a great idea and should not be very difficult. Thanks for this suggestion!
https://github.com/sethsec/celerystalk/blob/master/lib/scan.py#L190 if interested :)


Inline equations linebreak at appropriate places

This is a PR that continues working of #1826, because I feel pity if the effort made by @damaxwell is abandoned. This is also encouraged by @Enter-tainer. I made these changes since last review:

Rebase @damaxwell's commit to main branch (the first commit).
Make two changes according to previous comments from @laurmaedje (the latter two commits).
Pass all tests, @laurmaedje but there are two editions on existing tests that I cannot confirm.

Add #set page(width:122pt) in tests/typ/math/delimited.typ. @damaxwell was adding #set page(width:121pt) in #1826, so I followed that. But it looks a bit weird to me, since the default width of page is known to be 120pt.
tests/ref/text/linebreak-obj.png is changed, but that change looks good to me.

Note: the following content is copied from #1826.
Currently, Typst treats an inline equation as a monolithic item. No line breaks are possible in the middle.
This PR implements something close to TeX's strategy for allowing line breaks. A break is allowed:

After a binary operator or a relation,
unless the operator or relation is enclosed in a left-right group (or in a more complicated thing like an exponent or a radicand),
except that a relation followed by a relation doesn't line break.
Notwithstanding the above, inline equations with more than one line never line break.

This ended up being somewhat trickier than I anticipated. The paragraph rendering algorithm delayed rendering of equations and boxes until late, but needed to know how many items in the paragraph these objects will become early on. That's easy if the answer is always "1", but for equations the answer now depends on layout. So layout was migrated sooner in the algorithm.
Additionally, when determining whether a line break is allowed after all of the initial math layout is done, you need to know if binary ops and relations are sitting inside of LR groups. But not enough information was left behind to determine this. So an additional layer of tags was introduced so that beginnings/ends of LR groups could be identified after the fact.
Some notes/questions:

Meta information for the whole inline equation is applied to all of the resulting (non-space) fragments. I need confirmation that that was the right choice.
The Layout trait takes a &mut Vt as an argument. I think that means, in principle, that there can be ordering effects if children are laid out in different orders. So when I moved the equation rendering early, I also moved the box rendering early. But I noticed that layout of fractional-spaced boxes was, in fact, already delayed until the very end of paragraph layout, just before completion. Are ordering effects a non-issue? I'm not exactly sure what in the Vt might be altered during layout. At any rate, this PR lays out paragraph children in the same order as was done previously (preserving any bugs, if they were present).
In TeX, something like $10^3$cm does not allow a line break between the formula and the text. By contrast, Typst allows line breaks here. One could implement this, I think, by changing the way formula fragments are represented in the paragraph (as a non-breaking space U+00A0 instead of an object replacement U+FFFC, perhaps). But this is best tackled, if desired, in a separate PR.
A couple of test source files were edited so that newly legal line breaks did not interfere with the spirit of the test.

Example
See referenced images for example.

I did a small bit of refactoring myself. I'm mostly fine with the state of things now. Just the into_par_items function is a bit complicated for my liking. In particular, I don't understand what space_is_visible is doing.

I don't know either, should we ping damaxwell? But I may also try reading it when I have time.

We can try (@damaxwell), but I think he's very busy.

I may take a look, but this requires me to be familiar with code about math equations. I mean I should understand code base before understanding space_is_visible.

I read it quickly, looks like into_par_item is easy to understand to me, if my judgement that it is quite independent to other codes.
First, the entry point is:
let mut items = if rows.row_count() == 1 {
    rows.into_par_items()
} else {
    vec![MathParItem::Frame(rows.into_fragment(&ctx).into_frame())]
};

If there is only single row in MathRow, it uses into_par_items. Otherwise, it uses the default approach to layouting them. [^codebase1]
Second, we look into into_par_items, let us ignore code that are not related to space_is_visible.
We call an items that either binary operators or last relation symbols are vital items, as the MathRow is breakable after the items. [^codebase2]
into_par_items iterates a row and peeks items during iteration:

Initially, all spaces in the row are converted by fragment.into_frame() and pushed into the output vector, until it peeks a vital item.
When peeks a vital item, it turns space_is_visible on and inserts a zws as needed.[^zws] Jump to 2.
All visible spaces are specially converted into MathParItem::Space(s) and pushed into the output vector, until it peeks a not vial item. Jump to 1.

There are two main semantic things generated:

inserts a zws if there is no space between a vital item and the following item.
visible spaces after a vital item are specially converted into MathParItem::Space(s).

[^codebase1]: I'm unfamiliar with the "Otherwise" part, which needs double check.
[^codebase2]: Not sure whether the definition of a vital item by damaxwell is correct.
[^zws]: The inserted zws item is MathParItem::Space(Abs::zero())

Ok, I think I understand. I'd be happy to merge this once the conflict is resolved.

Thank you for reviving this!


Feature to avail provision of a HTTP/HTTPS API (get/post) to act as a data source for Superset

For a multi-tenancy deployment, we want to isolate our DB from Superset deployment. A minimal and trusted approach will be to use an API as a data source for Superset. With API we will have better control of what data is exposed to each user, to terminate access as per the requirement and implement a unified architecture for a front-end application which uses reactjs. I have gone through these two repos:
https://github.com/betodealmeida/shillelagh
https://github.com/cancan101/graphql-db-api
But an officially released and validated module as part of Superset's DB engine will be very helpful in implementing this out-of-the-box.

Closing this as stale since it's been silent for so long, and is a feature request rather than a bug. If this is relevant in current versions (currently 3.x) please open a new Ideas discussion or a PR to address the problem.


Build for Windows and Mac

See https://github.com/Senzing/explain/issues/9

Pull requests

https://github.com/Senzing/senzing-tools/pull/94


fix issue "I am reay" announcement is too early

@muratams
As we discussed, I added MFLocalizeStatus to enable nodes can check the multi-floor localization is ready to navigate.
Now, it announces "I am ready" when the localization is in the MFLocalizeStatus.TRACKING state.
Currently, MFLocalizeStatus.UNRELIABLE is not used because there isn't such a clear state in the multi_floor_manager.py.
Failure detection has one threshold, self.rmse_threshold = 5.0 to determine if restart localization is required (only auto relocalization is enabled).
How can we implement the state?
https://github.com/CMU-cabot/cabot/blob/87cfaa6805c7920c209b2fd6da6012a68d9c5e02/mf_localization/src/multi_floor_manager.py#L358-L363

It is not necessary to implement the unstable state for now.

I'm not sure if this change L519-520 is correct.
https://github.com/CMU-cabot/cabot/blob/87cfaa6805c7920c209b2fd6da6012a68d9c5e02/cabot_ui/src/cabot_ui/navigation.py#L515-L525

fixed by commit https://github.com/CMU-cabot/cabot/commit/66390ca30ab14f47b8fe11b95ea3f94454b80704

I'm not sure if this change in cabot_ui (L519-520) is correct.
https://github.com/CMU-cabot/cabot/blob/87cfaa6805c7920c209b2fd6da6012a68d9c5e02/cabot_ui/src/cabot_ui/navigation.py#L515-L525


PDF link and Image src in tinymce

Hi,
when using a wysiwyg field type, adding an asset link (image or pdf for sample) always set the src with relative path /storage/andco...
So when retrieve datas from frontend app, the link is of course 404 !
Is there a solution to append cockpit base_url in this case and only in this case ? Nota: i'm ok with append base_api_url from frontend app when using an image field type, so the question here is only in the wysiwyg case.
I've checked relative_path in tinymce config and it's false.
thanks

Has this ever been resolved?  Did you get it working?  I'm having this same issue and I can't figure out how to fix it.  If I can't get this fixed it kinda defeats the entire purpose of using Cockpit as a CMS...


List beahviour odd

Talking about my folder of 800+ files, when I move down that list at some point the selected row is "below" the screen bottom, effectively making it invisible. Scrolling up two or three times brings it back into the visible area.
Another odd behavior was when I scrolled backwards (from the first position of the list on the top pressing key up). I could only scroll to roughly half of the visible list before the selection would reset to the last element again. It would basically loop from there on.
Maybe all these oddities have something to do with the UI breaking in between from trying to preview different file types.

Yeah most likely due to the broken UI when previewing files. Ill add some logic to not open files that are not supported yet which would prevent the breakage

@mrusme let me know if you still seeing this after 0.13.5 which should prevent the UI from breaking on those files

Seems like this was fixed!


Add log location for macOS

Fixes #249

@Senryoku incorporated this in #248 by now.
(Please do not close the PR/stop the deployment until I received the feedback from the mac user)


GraphiQL no longer persists Variables/Headers after closing tab

Describe the bug
The state in the graphiql playground for Variables and Headers tab no longer persists thru browser sessions.  This is a slight annoyance as I like to store csrf tokens, etc there while developing & debugging
Your Example Website or App
n/a
Steps to Reproduce the Bug or Issue
To repro:

Open graphiql that ships with latest version of yoga
Put something in headers sub-tab
Close browser tab/window for this session
Go back to api playground and see that Headers tab is now blank

Expected behavior
I expected the headers info to persist across sessions, as it used to with old versions of yoga
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome 111.0.5563.146
Yoga: latest

Additional context
No response

There is a prop shouldPersistHeaders which is false by default. It should probably changed in the yoga graphiql package?
See:

https://graphiql-test.netlify.app/typedoc/modules/graphiql_react#editorcontextproviderprops-4
https://github.com/graphql/graphiql/issues/1984


Spyder (or python) hangs when calling pdb.set_trace() in class definition. See example

From<EMAIL_ADDRESS>on 2014-02-02T12:45:15Z
Spyder Version:  2.2.1
Python Version:  2.7.5+
Qt Version:      4.8.4, PyQt4 (API v1) 4.10.3 on Linux
What steps will reproduce the problem?

Import module so.py (MRE, attached)
Python hangs What is the expected output? What do you see instead? If there is a recursion error, I'd like to see Spyder display its actions and the python interpreter to trip after a certain maximum recursion limit is reached. Instead, Spyder becomes completely unresponsive.

I'd like to be able to call pdb.set_trace() within a class definition. Is this not possible?
Attachment: so.py
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1717

From ccordoba12 on 2014-02-07T05:23:40Z
Thanks for reporting. I'll take a look at it.
Labels: MS-v2.3.1 Cat-Debugger

From ccordoba12 on 2014-08-17T18:44:48Z
Labels: -MS-v2.3.1 MS-v2.4


Login

With email and password.
Suggestion: use a session cookie at least 128bit long, stored in Redis, valid for 7 days.

This is being implemented as part of #13


Implement target validation

Work to date only covers refreshing the repository metadata / polling for presence of new targets to download. The other high level operation an application requests TUF libraries to do is to download (or at least verify) a "target", or essentially a file that's downloadable.
We should totally do that.

Here's the stub method:
commit 3d5991f33483c76c6050c9eebd84f7554c3c6f15
Author: xjm<EMAIL_ADDRESS>Date:   Tue Aug 11 06:05:55 2020 -0500

    Remove empty validateTarget() method for now, which is empty and dead code ATM. #35 will reimplement it.

diff --git b/src/Client/Updater.php a/src/Client/Updater.php
index d561913..6aa960a 100644
--- b/src/Client/Updater.php
+++ a/src/Client/Updater.php
@@ -212,6 +212,22 @@ class Updater
         }
     }

+  /**
+   * Validates a target.
+   *
+   * @param $targetRepoPath
+   * @param $targetStream
+   *
+   * @return bool
+   *   Returns true if the target validates.
+   *
+   * @todo implement target validation.
+   *     https://github.com/php-tuf/php-tuf/issues/35
+   */
+    public function validateTarget($targetRepoPath, $targetStream) : bool
+    {
+    }
+
     protected function checkSignatures($verifiableStructure, $type)
     {
         $signatures = $verifiableStructure['signatures'];

I think we have this now, with the implementation of the Updater::verify() method. I'll leave this issue open for now but I suspect it's outdated and can be closed.

This has long since been completed :) The way to do it is call Updater::download(), which will download the target, verify it transparently, and return it as a stream.
It's time to close this.


[Bug]: Commands Not Working On Laravel with Octane

PHP version
8.2
Telegram Bot SDK version
3.14
Laravel version (if any)
10
What happened?
When using Laravel Octane,  Telegram::commandsHandler(true); not working.
Code To Reproduce the bug
Route file:
Route::post('/telegram/webhook', function(Request $request){     Telegram::commandsHandler(true); });
the standar /help function won't reply anyting on telegram bot.
Error stacktrace (if any)
No error available

Additional Context
No response
Possible Solution
No response

@metasanjaya Hello, are you found a solution?

@metasanjaya Hello, are you found a solution?

No, I am using another library now.

I made like this and this is working
`
use Illuminate\Http\Request;
use Nyholm\Psr7\Factory\Psr17Factory;
use Symfony\Bridge\PsrHttpMessage\Factory\PsrHttpFactory;
use Telegram\Bot\Laravel\Facades\Telegram;
$psr17Factory = new Psr17Factory();
$psrHttpFactory = new PsrHttpFactory($psr17Factory, $psr17Factory, $psr17Factory, $psr17Factory);
$psrRequest = $psrHttpFactory->createRequest($request);
Telegram::commandsHandler(true, $psrRequest);
`


OSP is OpenStack Platform, OpenShift is OCP

Checklist

[ ] Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
[ ] Make sure mvn install runs for the whole project and, if you touched any code in the respective service, submission and distribution service can be run with spring-boot:run

Description
Since OpenShift is OCP/OKD, correct the acronym in the architecture document.

Thanks, looks about right. I will check if this abbreviation used in other places as well.


Docs: advanced examples

Codecov Report

Merging #816 (e5e15ba) into main (2f0eb65) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #816   +/-   ##
=======================================
  Coverage   52.01%   52.01%
=======================================
  Files          69       69
  Lines        2082     2082
  Branches       65       65
=======================================
  Hits         1083     1083
  Misses        999      999

Continue to review full report at Codecov.

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


Support npm ci with a package-lock.json

We don't currently npm install prior to deployment so there is no package-lock.json generated in the dist folder.
It's not ideal to run npm install prior to every build/deploy, but the package-lock.json would be useful for the following reason (comment from another repo)

From my understanding, when deploying to Cloud Functions, Cloud Build installs your dependencies with npm ci, but your apps/api directory doesn't have a package-lock.json file, so your dependencies are installed in a non-deterministic way, which isn't desirable. If any dependency (e.g. firebase-functions) were introduced a bug in a minor release, this bug would suddenly appear on production.

Possibly  npm install --package-lock-only might do it...

I've successfully deployed using plugin v0.3.4 against a 13.10.6 Nx workspace, with node version 14, and 16, firebase-tools 10.8.0 with no issues.
Closing this.


add 'clock' example

clock.py and index_clock.html show an example where:

the client opens the ws channel
the server send every seconds a time stamp
the client display it

The client clicking on the close button is closing the ws channel

Thanks! I've merged this with some minor changes for consistency.

 Thanks for your work @miguelgrinberg


Webots cannot start on Windows with current MSYS2

The workaround is simple: copy libicu*62.dll from an installed Webots R2019a revision 1 to the development environment:
cp /C/Program\ Files/Webots/msys64/mingw64/bin/libicu*62.dll ~/webots/msys64/mingw64/bin
The problem was reported here: https://github.com/msys2/MINGW-packages/issues/5273 and should be fixed soon hopefully.

For conveniency, I created an archive with the files to copy:
libicu.zip

Fixed. See https://github.com/msys2/MINGW-packages/issues/5273


Microsoft.AspNetCore.Server.Testing inconsistency between shipping status and version number

This package is used by our functional tests and we need to decide whether it should be shipped or not. If we decide to ship it, we will probably need to clean up the code and update packages.csv to ship. If not, we should change the version number to 0.1.0 from 1.0.0  to be consistent with other noship packages and remove 1.0.0 versions from our feeds.
cc @davidfowl @Eilon @muratg

We can't avoid doing this in RC2 and then do it in RTM. This is either done in RC2 or never.
@muratg thoughts?

Let me clarify one point:

ship/noship/ext -- this distinction is for the packages that we own and ship on nuget, packages we own but not push to nuget and partner packages
Prerelease/RTM -- this distinction is ONLY valid for "ship" packages (i.e. the ones we push to nuget.org).  Prerelease versions would have 0.1.0 version, and RTM ones would have 1.0.0.

This package is currently noship category (among other Testing packages)
So if we decide to ship this one (or more of the Testing packages), we'll need to do the version changes now. If not, we can skip the work.

We can change the version for no-ship packages at any time, it's the same amount of work to purge them from our myget feeds. That said, the sooner the better.
Is there any reason not to change all of our no-ship package versions to v0.1?

@muratg ah ok so not urgent.
@Tratcher I suppose we could.

https://github.com/aspnet/MusicStore/commit/87e3544fda2f5cf89897ea6aefdcab683f4aebfd
https://github.com/aspnet/ServerTests/commit/ed687d08b6f5bdd6e7c5a082c31856fcd26dccec
https://github.com/aspnet/Localization/commit/0283099928382da520f958269bb714b3480680cb
https://github.com/aspnet/Entropy/commit/0a0130560e52e1ce0df3601bb0ffe676ca675a2d
https://github.com/aspnet/ServerTests/commit/ed687d08b6f5bdd6e7c5a082c31856fcd26dccec


Refactorings to the VDomModifier hierarchy.

I did some refactorings to the VDomModifier hierarchy so that StringNode is no longer a VNode_, instead is a VDomModifier_, so that it was possible to remove the apply(args: VDomModifier*) method from VNode_ which was failing with a runtime exception if somebody tried to apply modifiers to a StringNode.
As a consequence, VNode_ is replaced by VTree and I introduced a StaticVNode that can be either a StringVNode or a VTree, but the StringVNode is only used in those cases a where a StringModifier would not work, for example when using something like:
val stringStream: Observable[String]
div(child <-- stringStream)

This PR also fixes the way strings are converted to Snabbdom in most cases, for example currently  something like span("foo") ends up translated to {'sel': 'span', children: [{'text': 'foo'}]} instead of {'sel': 'span', 'text': 'foo'}. This is fixed, except for those cases when a StringVNode is required, like in the example above.
I re-ordered the traits/classes in VDomModifier.scala in breath-first order so that similar classes (Attributes, Properties, ...) are next to each other.
This PR is on top of #115.
Fixes #113.

I think we should establish a practice of submitting separate rename and code-move PRs. This makes it a lot easier to review and resolve conflicts.

I reverted the VDomModifier_ rename and added a def tag() for custom tag creation.

I have added a trait TitledAttribute to distinguish between EmptyAttribute (without title) and normal attributes (with title).


Regression in fbx with new indexer

Godot version:

4.0 master
I am working in #44653

OS/device including version:

Linux, RX580, VK backend

Issue description:

Opened working scene in 4.0
Scene is not rendered

video of issue
https://www.youtube.com/watch?v=zw3hdC2iOV0&feature=youtu.be
Steps to reproduce:

load current master
open Bistro Exterior fbx
bistro fbx is blank visually but nodes and meshes are in the scene
revert commit 3fdf4bfe71311000bf706c16d79b475308a200ac
problem is gone

Minimal reproduction project:
https://developer.nvidia.com/orca/amazon-lumberyard-bistro
I spent 5 hours yesterday debugging this and it's caused by this commit, before it didn't happen.
I would like to fix this, there are no errors reported on opening the scene.
Fixes tried

null materials
increase scaling values
clearing material mapping manually
rescaling scene meshes
copying meshes outside of the scene seems to make them visible in some cases but they still disappear.
flipping cull direction, disabling culling and also disabling depth test
This completely blocks me from working.

reproduction meshes.zip
Added reproduction meshes to the project

OK so the bug can be 'worked around' by setting mesh to be 1.0 scale (hardcoded scale)
Then if i rescale the mesh the mesh appears.
So we are generating bad AABB's most likely happening in SurfaceTool

#44660 contains fixes to reproduce the scaling workaround
I disabled materials entirely to keep things as simple as possible right now.

Notes:

in some cases adding a world environment and enabling SDFGI fixes the mesh preview.
for bistro external the problem is not fixed but, we at least know there are some bugs
simple geometry doesn't seem to be effected (cubes etc)
re-scaling scene fixes visual problem but then the CPU usage spikes for the culling insanely.

for now I think it's best we leave this as-is and just wait until the new indexer is ready for use

OK so a workaround is this patch below:
diff --git a/servers/rendering/renderer_scene_cull.cpp b/servers/rendering/renderer_scene_cull.cpp
index 94f5788683..a7016a6dd2 100644
--- a/servers/rendering/renderer_scene_cull.cpp
+++ b/servers/rendering/renderer_scene_cull.cpp
@@ -1160,7 +1160,7 @@ void RendererSceneCull::_update_instance(Instance *p_instance) {

        p_instance->transformed_aabb = new_aabb;

-   if (p_instance->scenario == nullptr || !p_instance->visible || Math::is_zero_approx(p_instance->transform.basis.determinant())) {
+ if (p_instance->scenario == nullptr || !p_instance->visible) {
                p_instance->prev_transformed_aabb = p_instance->transformed_aabb;
                return;
        }

Some xforms in the file are actually this value, so this is very bad. I made some patch already to find them but no luck yet.


Angular 7 many warnings

Hi
In angular 7, there are those warnings:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
kind regards

Similar warnings myself.
warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>
Tested, and everything seems to work still. I believe dependency versions for these just need to be updated to support 17.0

Thank you very much for your help.
Kind regards,
Vesel Haxha

From: Daniel Moncada<EMAIL_ADDRESS>Sent: 22 October 2018 22:08
To: swimlane/ngx-datatable
Cc: vhaxha; Author
Subject: Re: [swimlane/ngx-datatable] Angular 7 many warnings (#1582)
Similar warnings myself.
warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>Tested, and everything seems to work still. I believe dependency versions for these just need to be updated to support 17.0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/swimlane/ngx-datatable/issues/1582#issuecomment-431986961, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMN6kTx-0BpIIIeByppQQbDKy25fBsKTks5unjPJgaJpZM4XzoOL.

Released 14.0.0 with support for angular 7.


Very minor spellos in README.md

add a link referenced in the doco, couple of very minor spellos

@xlfe Thank you!


[Data]: Add RUM instrumentation to grant details view UI elements

Why is this issue important?
We want to be able to accurately and intuitively track user interactions with various page elements in Datadog RUM, but automatic element names can be unreliable.
Current State
Datadog RUM views and actions are fully reliant on auto-generated UI element names.
Expected State
When the myProfileEnabled feature flag evaluates to true, UI elements with which users may interact (buttons, toggles, etc.) are annotated with the data-dd-action-name attribute, and significant user actions are instrumented. This issue focuses specifically on the new "grant details" view.
Implementation Plan

Update the grant details modal component so that UI elements are annotated. The following screenshots display examples of the minimum set of elements (additional elements may be annotated if it seems valuable to do so):

NOTE: The above screenshots reflect Staging as of the creation of this ticket, and do not reflect the planned designs for the new Grant Details view that are represented in Figma. A comment will be posted to this issue with similar annotations based on the new designs.
Update element callback handlers to include calls to datadogRum.addAction() as follows (fill in <placeholder> values accordingly):

User submits team a status:

Name: submit team status for grant
Context:{ team: { id: <team id> }, status: <selected status text>, grant: { id: <grant id> } }

User removes a team status (by clicking trash can icon):

Name: remove team status for grant
Context:{ team: { id: <team id> }, status: <previously selected status text>, grant: { id: <grant id> } }

User assigns a team:

Name: assign team to grant
Context:{ team: { id: <assigned team id> }, grant: { id: <grant id> } }

User removes a team assignment (by clicking trash can icon):

Name: remove team assignment from grant
Context:{ team: { id: <unassigned team id> }, grant: { id: <grant id> } }

Relevant Code Snippets
No response

Additional screenshot with annotations, based on current Figma design specifications:


Implement crt shader.

Move CRT shader into internal shader.

Note that the background colour does not work on the metal.


Add build workflows for dev, nightly, and release wheels

Summary

Add a workflow which based on the conditions, will create a nightly, dev or release wheel
The workflows make use of the actions in nm-actions and relies on this PR: https://github.com/neuralmagic/nm-actions/pull/3
The following cases are covered:

1. Dev

For dev, a wheel is created if a PR to main is opened or updated. This wheel will be called sparsezoo_dev-[version].dev[PR] where [PR] will be replaced to use the PR number and [version] will be replaced to the current version listed in version.py. All dev PRs are pushed to the internal bucket in s3 (from which jenkins should push to the internal PyPi server)

2. Release

When a PR is opened/updated to a release branch: in that case, the built wheel will be pushed to the internal bucket in s3 and the wheel will be called sparsezoo-[version] where the [version] will be replaced to the current version listed in version.py
When a new release tag is cut, the naming will be the same however, the release will be pushed to the external/production s3 bucket for the production PyPi server

3. Nightly

When a PR is merged into main, the wheel will be built and named sparsezoo_nightly-[version].[date]
A scheduled nightly cron job will trigger a nightly build and create a wheel with the same name. The wheel will be pushed to an external/production s3 bucket for the production PyPi server

The equivalent workflow can be added in to sparseml once approved
Testing

Nightly and dev workflows have been tested however, this is with a dummy s3 bucket so we do not overload the buckets being used by the current workflow
Release builds have not been tested

NOTE:

Before this PR can be merged, the actions PR mentioned above must be merged

Next Steps:

Update jenkins to use the new/updated buckets
Find a non-destructive way to test release workflows

keeping open until relevant nm-actions are merged


MAINT: add custom metrics in otel-trace-source README

Signed-off-by: Qi Chen<EMAIL_ADDRESS>Description
This PR adds the custom metrics introduced in #1241 into README of otel_trace_source
Issues Resolved
#1158
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1246 (0ddaa10) into main (1ed9305) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #1246   +/-   ##
=========================================
  Coverage     93.79%   93.79%
  Complexity     1104     1104
=========================================
  Files           153      153
  Lines          3064     3064
  Branches        257      257
=========================================
  Hits           2874     2874
  Misses          138      138
  Partials         52       52

Continue to review full report at Codecov.

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


Add VueFlux

Project URL

https://github.com/ra1028/VueFlux
Description

Unidirectional Data Flow State Management Architecture for Swift - Inspired by Vuex and Flux
Why it should be included to awesome-ios (optional)
This will be the best choice to handle the complicated data flow of large-scale Swift project.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

2852
Error
https://ioscompanies.info/about/welcome  Connection refused - connect(2) for "ioscompanies.info" port 443

  Generated by :no_entry_sign: Danger


Subsequent component add's changes earlier manually added THREE.Points

I have a "stars" component:
const stars = Stars({ size: 128, scale: starsScale })
app.$scene.add(stars)

(need to see full image to notice stars better)

Then, if I add some spheres:
}].reduce(function (links, { title, position, color }) {
  const sphere = new Sphere({
    // buffer: true,
    geometry: {
      radius: 0.2,
      widthSegments: 16,
      heightSegments: 16
    },
    position,
    material: new THREE.MeshBasicMaterial({ color })
  })

  app.add(sphere)
  mouse.track(sphere)

  sphere.on('click', () => console.log(`${title} clicked`))

  return { ...links, [title]: sphere }
}, {})

At this point, the stars seems to have scaled itself to match the size of the spheres. I verified this by changing sphere sizes.

Also, if I do buffer: true, they seem to become is big as the skybox, and geometry becomes broken/jagged. You could see the stars same size near the edge of the green circle:

Maybe wrap() is acting on more than it should be?

It might actually be modifying the actual geometry:
(stars should be more numerous and randomly placed)

I tracked it down to here.
If  you comment that line, the component will not get added, but the previous one will not change.

Ok.....found out it was a problem with my own code
but it is still really confusing, and I've only fixed the problem by playing around...if anyone has any suggestions..
The original code is this:

This only works if there is no skybox (when there is skybox, there are no stars):

Then this, if the Sphere I add has { buffer: false }, then the stars will take the geometry of the sphere:

And then this works. whaaaaaaaatt!!!

I'll close this since it's no longer a WHS issue. Maybe I am doing something wrong, or it is a Three issue.


requirements

Hi, is it possbile to have a requirements.txt file (pip install - r requirements.txt ) to have the right version of libs to install (pandas, erdpy ....)
Thanks !

Hey :)
I've added the requirements file, thank you for raising this issue :)
However, you might still need to install additional libraries for erdpy (ncurses) and you'll probably want to install it with erdpy-up, as opposed to pip.
You'll find more info here :)


GLES2 GL_RGB buffer breaks OpenVR

Godot version:
Commit # 35444576ff684aebb0133d46495be85d3d434900 but seems to have changed in Godot 3.2 some time ago
OS/device including version:
Tested on Windows, but any OpenVR capable OS will exhibit this
Issue description:
In Godot 3.2 the code here was changed:
https://github.com/godotengine/godot/blob/master/drivers/gles2/rasterizer_storage_gles2.cpp#L4587
We now create a GL_RGB buffer if we're not using a transparent background. In Godot 3.1 we always created an GL_RGBA buffer regardless.
When sending the render output to OpenVR, GL_RGB is not a supported format, likely because the 24bit color buffer is more inefficient then a 32bit color buffer (data alignment wise)
I'm wondering if there is a good reason to use GL_RGB here other than slightly less memory usage (if the hardware doesn't decide to use a 32bit based buffer anyway)?
I'd hate to introduce a new switch to force GL_RGBA...
While I think its unrelated it is also interesting to note that the texture object returned for the viewport always assumes GL_RGBA:
https://github.com/godotengine/godot/blob/master/drivers/gles2/rasterizer_storage_gles2.cpp#L4679
Steps to reproduce:
Run the OpenVR demo project in GLES2 mode (https://github.com/godotvr/godot_openvr)
Minimal reproduction project:
https://github.com/godotvr/godot_openvr

Commit # 3544457 but seems to have changed in Godot 3.2 some time ago

Wrong commit hash?

@akien-mga nah, thats the commit i'm on, last pulled a few days ago :)
Got feedback from Valve that GL_RGB8 is supported, I remember that the internal format should include the bit indicator, ran into problems with that before. I guess GL_RGB doesn't always resolve properly.
Just made the change and it seems to work like a charm. Need others to verify :)

That sounds great! I just recently did that with the depth texture to make it run on more Android devices. Glad to hear the solution was so simple!


Distance Matrix Rounding

I'm having trouble understanding the rules for rounding in the edge_weight matrix. Below is a code where I calculate the cost by using edge_weight matrix of instance from vrplib and compare it with the cost value from instance file. I calculate these costs based on the edge_weight matrix of the instance obtained from CVRPLIB using vrplib. The output of the code is a bit long, so I've uploaded it as a text file. Thank you.
num = 0 # number of instances
false_num = 0 # number of instances with wrong solution
true_num = 0 # number of instances with correct solution

path = Input_Handler_CVRP.get_input_path()

# FINAL_INSTANCE_NAMES is the list of the instances that are going to be tested
# it contains the names of the instances that has less than 1500 nodes and has node_coord
for index in range(len(FINAL_INSTANCE_NAMES)):

    instance_name = FINAL_INSTANCE_NAMES[index] # name of the instance
    instance_set = FINAL_INSTANCE_SETS[index] # set of the instance

    instance_dict: dict = vrplib.read_instance(path + '/' + instance_set + '/' + instance_name + '.vrp')
    solution_dict: dict = vrplib.read_solution(path + '/' + instance_set + '/' + instance_name + '.sol')

    opt_route: list = solution_dict['routes'] # list of lists (in the instance file, got from vrplib)
    opt_dist = solution_dict['cost'] # optimal distance (in the instance file, got from vrplib)

    dist_matrix: np.ndarray = instance_dict['edge_weight'] # distance matrix (in the instance file, got from vrplib)
    weigth_type: str = instance_dict['edge_weight_type'] # type of the distance matrix (in the instance file, got from vrplib)

    sol_dist = calculate_solution_distance(dist_matrix, opt_route)

    if sol_dist == opt_dist:
        print(instance_name + ' is OKEY with distance ' + str(opt_dist) + ' *** ' + weigth_type)
        true_num += 1
    else:
        print('Solution distance: ' + str(sol_dist) + ' Optimal distance: ' + str(opt_dist) +
                ' in instance ' + instance_name + ' *** ' + weigth_type)
        false_num += 1

    num += 1

print('True: ' + str(true_num) + ' False: ' + str(false_num) + ' Total: ' + str(num))

The functions that I use to calculate distances are below:
def calculate_route_distance(matrix: np.ndarray, route: list):
    route_distance = 0

    for i in range(len(route)):

        if i == 0:
            node_from = 0 # depot
            node_to = route[i] # first node to visit
        else:
            node_from = route[i - 1]
            node_to = route[i]

        dist = matrix[node_from][node_to]
        dist = round(dist, 0)
        route_distance += dist

    last_node = route[-1] # last node before returning to the depot

    dist = matrix[last_node][0] # distance from the last node to the depot
    dist = round(dist, 0)
    route_distance += dist

    return route_distance

def calculate_solution_distance(matrix: np.ndarray, routes: list):
    solution_distance = 0

    for route in routes: # it iterates over the routes and calculates the distance of each route
        route_distance = calculate_route_distance(matrix, route) # it returns the distance of the route
        solution_distance += route_distance

    return solution_distance

I am rounding distances that I get from edge_weight matrix to 0 decimal numbers by using round(dist, 0) method.
Here is the output of the code: output.txt
To use that code you have to just specify the path, FINAL_INSTANCE_NAMES list, and  FINAL_INSTANCE_SETS list.
Thank you so much :)

Hi @boraaktas!
Thanks for opening this issue. There is nothing wrong with your code and the vrplib package (fortunately!). The differences in the solution cost calculation and the cost provided by the files are due to different rounding conventions that are used in the literature.
As can be seen in output.txt file, the X instances work fine. That's because, in this instance set, the convention is to round the distances to the nearest integer. This can be found back in the associated paper.
However, the CMT, tai, Golden, and Li instance sets don't use this rounding convention. Even though their VRPLIB instance format specifies EUC_2D, whether to round or not is something that is not specified accurately by these instances. To know how to round the distances in these instances, you will have to look into the literature and find the corresponding papers on how they handle this.
This is something I can't do much about because the instances are provided by CVRPLIB, which I'm not the maintainer of. I suggest simply using the X instances, which are currently the benchmark instances for CVRP. Hope this helps.

Thank you so much for your response, @leonlan. Just as you mentioned, I also noticed that a different approach was used in those sets. However, what puzzled me the most was encountering errors in the instances below:
Solution distance: 1319.0 Optimal distance: 1312 in instance B-n50-k8 *** EUC_2D
Solution distance: 1155.0 Optimal distance: 1153 in instance B-n57-k7 *** EUC_2D
Solution distance: 537.0 Optimal distance: 534 in instance E-n30-k3 *** EUC_2D
Solution distance: 721.0 Optimal distance: 724 in instance F-n45-k4 *** EUC_2D
Solution distance: 1159.0 Optimal distance: 1162 in instance F-n135-k7 *** EUC_2D
It is quite strange that while other instances in these sets provide correct results with rounding to 0 decimals, these cases having errors. Do you think that the values mentioned in the solution files might be incorrect? I don't want to dismiss all other sets based on just a few instances, though! :)
Once again, thank you so much.

I can't say whether the values are incorrect, but it may well be. The best bet is to contact the maintainers of CVRPLIB or to check the references about these data.

Yes, you're right. I appreciate your assistance. Wish you the best with your work.


non-babel environment - dynamic components

I am attempting to render a component isomorphically with react-universal-component in my typescript environment
const makeUniversal = ({ chunkName, filePath }) => {
  console.log({ filePath })
  const loadFn = props => Promise.all([
    import(
      /* webpackChunkName: '[request]' */
      filePath
    )
  ]).then(proms => proms[0])

  const UniversalComponent = universal(loadFn, {
    chunkName: () => `universal-${chunkName}`,
    resolve: () => {
      return require.resolveWeak(
        // if i pass hardcoded string here, it works just fine
        filePath
      )
    }
  })

  return UniversalComponent
}

const Thing = makeUniversal({
  chunkName: 'large-full-width',
  filePath: 'apps/large/ListingCards/FullWidthEntryPoint/container',
})

// etc
render() { return <Thing /> }

When require.resolveWeak is run through webpack, it returns the wrong module (in this case it looks as though it returns  a test file that is completely unrelated) do I need to change the way I am dynamically loading my components?
^[[server] ./src/apps/large/MapSearch/components/List/__tests__/container-test.jest.js
Module not found: Error: Can't resolve 'mocks' in '/Users/lfender/source/ag.js/src/apps/large/MapSearch/components/List/__tests__'
resolve 'mocks' in '/Users/lfender/source/ag.js/src/apps/large/MapSearch/components/List/__tests__'
  Parsed request is a module

its interesting that it thinks im attempting to load a tests file instead of the specified filepath

will try and come up with more complete example


Added callback function and missing translations to the minified version

This pull request has the following changes

I've added a callback function which will be called every time the user submits a date. In that way I will be able to retrieve the date in the angular version of Datedropper.
Also I've added the Greek locale to the minified version that for some reason was missing.

I will release the angular version as soon as the changes are merged to the main lib :)

Hey Felice,
you seem really really busy with your stuff. I can give you a hand with the repository maintenance. :smile: I'm waiting this merge to publish the angular version of datedropper :smile:
Cheers,
Nasos


Fix for uneven column heights

@caseywebdev  Is there any Nodejs/Front End position available in OrgSync? I am looking for new opportunity and interested in the Stack you are using.
I am this is not a good place for the question. May i have your email or could you send me a<EMAIL_ADDRESS>?   Thank you.


Update WorkflowRun.Get Doc String

Doc string improvement - 😓

What was changed

Describe behavior of WorkflowRun.Get in the doc string.
Why?

This is a contract some folks might rely on, so it's good to encode it via a comment.
Checklist

Closes
No formal tickets

How was this tested:

Comment

Any docs updates needed?

 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.

 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.

Please sign the CLA to land.


Refactor | Move to an existing file

I'd be surprised if this hasn't already been requested, but I can't find any issue for it.  "Refactor | Move to a new file" already exists, but more often than not, what I really want is to move a symbol to an existing file. Without editor support, I have to manually update all of the imports that reference the symbol.
So what I propose is "Refactor | Move to an existing file".
Thanks!

This is for JavaScript or TypeScript, correct?

Typescript, yes.


Fixed some typos in Informed Lesson Three.

Thank you for the lessons, I'm really enjoying them.

Awesome, thanks!

Happy to help.
I wasn't sure, should I have fixed the same typos in the Playground file as well or are those generated from the readme.md files?

They're not generated, so they're fine to fix too :dancers: - we seem to get so many typo fixes on this repo ;)

At least not as many as the main Apple Swift repo ;) I added the playground fixes and a few others I found while doing the rest of the tutorials to pull request #24. Thanks!


How do I make a custom component act as an inertia link?

Using React Bootstrap and it allows you to specify hrefs in the components e.g.:
<Navbar.Brand href="/">
    {app.name}
</Navbar.Brand>

How would I make this Navbar.Brand component act like an inertia Link?

Uses the as attribute in the Navbar.Brand. It would look something like this:
<Navbar.Brand href="/" as={Link}>
    {app.name}
</Navbar.Brand>

This only works for some bootstrap components.


Investiage alternatives to Github for SSO

If Github has a long downtime, we might need to look into alternatives for SSO.
Perhaps we could use GSuite?

We can use Google directly as an OpenID provider, or, if we are also moving the repository store to Gitlab, we could use that as a direct replacement for Github.


Do you know of this effort to kickstart a database-wg for Rust?

Hello,
I couldn't find another way to contact you, but I thought you should know about a new effort that is being kickstarted by @spacecookie announced at Rust Internals to build a database working group for Rust.

Yeah, I'm aware of it. We'll see where it goes.


Fix release description for 1.0

The description for the release of 1.0 (https://github.com/cakemanager/cakephp-notifier/releases/tag/1.0.0) mentions

The CakePHP core team is happy to announce...

Please remove this, since the CakePHP core team has nothing to do with this plugin! :) Also, maybe tag a new point release?

Thanks for noticing @dakota, I used the default one of Cake to have some good guidelines ;)


Pre-trained models

Can you release pre-trained models on Image-Net?

Sorry, I haven't trained this model on ImageNet. (Only CIFAR-10, with limited success...)


[TypeScript] Does not work with project references

I try to deploy one of my TypeScript projects to ZEIT Now and get a lot of Module build failed (from (webpack)/ncc/loaders/ts-loader.js): errors.
Could it be that I'm getting these errors because I'm using project references? Or is this somehow related to #291?
My tsconfig.json file looks like this:
{
  "files": [],
  "references": [
    { "path": "./src/one" },
    { "path": "./src/two" },
    { "path": "./test/unit/one" },
    { "path": "./test/unit/two" }
  ]
}

(every of these directories contain a separate tsconfig.json with composite set to true).
I'm not sure if this is related to zeit/now-builders or to ncc 🤔

@screendriver Can you try to reproduce this bug with the latest ncc?
npm install -g @zeit/ncc
ncc build src/one/index.js # assuming this is the entry point
node dist/index.js

I'm not using ncc directly. I'm using it indirectly via the ZEIT Now builder @now/node

Since I don't have your source code, I can't reproduce the bug.
So that's why I'm asking you to run ncc in your project and see if you get an error.

Or does @now/node just use this under the hood and this call is almost the same that the builder would do?

Basically yes and many sources of errors in @now/node is caused by ncc or an improper now.json configuration.

ncc: Using<EMAIL_ADDRESS>(local user-provided)
Error: Hash: 12a2a6b144c58b5cdcbb
Version: webpack 5.0.0-alpha.9
Time: 1608ms
Built at: 03/21/2019 9:38:02 PM
           Asset       Size  Chunks  Chunk Names
        index.js   1.71 KiB   {404}  main
    mongodb.d.ts  190 bytes
mongodb.d.ts.map  308 bytes
Entrypoint main = index.js
[823] ./src/one/index.ts 380 bytes {404} [built] [failed] [2 errors]

ERROR in ./src/one/index.ts
Module build failed (from ./node_modules/@zeit/ncc/dist/ncc/loaders/ts-loader.js):
Error: TypeScript emitted no output for /Users/me/project/src/one/index.ts.
    at makeSourceMapAndFinish (evalmachine.<anonymous>:1:2894210)
    at successLoader (evalmachine.<anonymous>:1:2893770)
    at Object.loader (evalmachine.<anonymous>:1:2892441)

ERROR in /Users/me/project/src/one/index.ts
./src/one/index.ts
[tsl] ERROR in /Users/me/project/src/one/index.ts(7,28)
      TS6305: Output file '../two/foo' has not been built from source file '/Users/me/project/src/two/foo.ts'.

    at compiler.close.n (evalmachine.<anonymous>:3:1349875)
    at _promise0.then._result0 (eval at create (evalmachine.<anonymous>:1:349386), <anonymous>:13:1)
    at processTicksAndRejections (internal/process/next_tick.js:81:5)
error Command failed with exit code 1.

Should I create a test repository for you?
By the way: I saw in the output that you are using ts-loader internally. As far as I know ts-loader doesn't support project references completely. At the moment my workaround is to build my project "manually" with tsc --build and let the Zeit builder run against my output dist directory.

@screendriver Yes, an example repository (preferably the smallest possible) would be of great help!

At the moment my workaround is to build my project "manually" with tsc --build and let the Zeit builder run against my output dist directory.

That sounds painful.
One solution you might try is change your now.json to something like the following:
{
  "builds": [
    { "src": "src/one/index.ts", "use": "@now/node-server", "config": { "bundle": false } }
  ]
}

You would also have to add the listen(3000) in your index.ts file to use this builder but it would circumvent ncc bundling.

@styfle I created a very very small repository where you can reproduce it easily 😉

@screendriver Thank you!
So this issue is currently blocked on the upstream  ts-loader (as you mentioned earlier).
And ts-loader is blocked on typescript because the builder API is not exposed yet 😮
Related Issues

https://github.com/TypeStrong/ts-loader/issues/851
https://github.com/Microsoft/TypeScript/issues/28640

:scream:
Oh, that's sad... Project references are really great and I don't understand why they are not so much used out there. But ok, so we have to wait. Should we keep this issue open until it's fixed?

It looks like ts just added support for tsc --build and --incremental

Issue: https://github.com/microsoft/TypeScript/issues/28640
PR: https://github.com/microsoft/TypeScript/pull/31432

@styfle Any update on this? Looks like ts-loader v6.1.0 landed and supports project references: https://github.com/TypeStrong/ts-loader/pull/935
Happy to help out with this if no one is looking at it.

@anthonyshort Feel free to submit a PR with implementation and tests 👍
I should also point out that ZEIT Now is no longer using ncc for tree-shaking user code and instead uses node-file-trace.