Can Wireguard display the peer configuration name in handshakes?

Can Wireguard display the peer configuration name in handshakes?
For troubleshooting purposes, it would be nice if the endpoint name is displayed in the handshakes.
Example:
current:
wg0 TkEFIXtRstIrT4r2oPqhr1SfyF0AWXSF9v3M7PgDJRI=<PHONE_NUMBER>
better:
wg0 (NAME OF THE PEER) TkEFIXtRstIrT4r2oPqhr1SfyF0AWXSF9v3M7PgDJRI=<PHONE_NUMBER>

I think this is already the Case when using the Dashboard widget?

which Dashboard widget?

Go to your Dashboard, Add widget, select WireGuard Widget and save.

thanks a lot, I found it.
Unfortunately it is exactly the same.
Only the private keys are shown without the peer names from the config

Looks like this is already in a PR, just waiting for approval / merging. https://github.com/opnsense/plugins/pull/1970

Looks like this is already in a PR, just waiting for approval / merging. https://github.com/opnsense/plugins/pull/1970


Update scalafmt-core to 2.7.2

Updates org.scalameta:scalafmt-core from 2.7.1 to 2.7.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Codecov Report

Merging #51 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #51   +/-   ##
=======================================
  Coverage   96.75%   96.75%
=======================================
  Files          15       15
  Lines         308      308
  Branches       18       15    -3
=======================================
  Hits          298      298
  Misses         10       10

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 ea44b90...5bbc8ad. Read the comment docs.


Big Brain Bots (Massive Bot optimizations)

Please describe the changes this PR makes and why it should be merged:
This PR is a WIP to optimize the library for huge bots.
Status

[ ] Code changes have been tested against the Discord API, or there are no code changes

Semantic versioning classification:

[x] This PR changes the library's interface (methods or parameters added)

[x] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

@ayntee Hey i think this is done or almost done and would love a review when u get a chance.

The last thing to do i probably to move rest and ws to a separate package

Since Deno supports publication of multiple modules from a single repository, we can separate both of them into their own directory―ws and rest.

@ayntee That's a good point, but tbh is it even necessary then. For example, our rest is literally just that 1 file. Deno could just pull that url directly and be done with it. Similarily for ws

@ayntee That's a good point, but tbh is it even necessary then. For example, our rest is literally just that 1 file. Deno could just pull that url directly and be done with it. Similarily for ws

I am suggesting this mainly because having separate repositories for each component is tedious.

I like the way you think!


In Height and Distance Page under Trigonometry, user input is not visible

Describe the bug

As for calculating Height and Distance under Trigonometry page, so here user input is not visible as the background is dark and the text is in black color so the user input is not clearly visible.

Possible solution

I would like to change the input text color from Black to White so that it is clearly visible.

Video
https://user-images.githubusercontent.com/61961107/137597150-601ed1bd-17e3-453c-a2b3-07f757d5b568.mp4
Can I work on this Issue under Hactoberfest2021
Kindly assign this issue to me under Hactoberfest2021

Hey @sairish2001 Kindly assign this issue to me under Hactoberfest2021 also please add Hactoberfest labels to it.


Add a page view UUID to the Javascript tracker

Add a UUID to each page view (the subsequent page pings should have the same UUID). This will make it much easier to aggregate page views and pings into single rows.

Basic idea:
page view ID (UUID) gets generated with each new page view. It get's fired with the initial page view event, and then any subsequent page view events.
The ID is pushed into Snowplow as part of a new com.snowplowanalytics.snowplow/web_page/jsonschema/1-0-0 context:
{
	"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
	"description": "Schema for a web page context",
	"self": {
		"vendor": "com.snowplowanalytics.snowplow",
		"name": "web_page",
		"format": "jsonschema",
		"version": "1-0-0"
	},

	"type": "object",
	"properties": {
		"id": {
			"type": "string",
			"maxLength": 60
		}
	},
	"required": ["id"],
	"additionalProperties": false
}

Note: over time we can explore migrating fields in atomic.events that really belong in a web page context to this object in the data model.

I would say the format/maxLength should match a UUID, otherwise looks good...

I have made this work like the ga cookies context, the performance timing context, and the geolocation context: you use a dictionary that looks like
          contexts: {
            webPage: true,
            gaCookies: true,
            performanceTiming: true
          }

when configuring the tracker, and if "webPage" is one of the entries and is set to true, the page view ID is attached to every event.
Is that right, or should the context be enabled by default?

@jbeemster - is the mobile_context on by default? That's probably the closest analogy...

Just remembered that we already have a org.schema/WebPage schema (https://github.com/snowplow/iglu-central/blob/master/schemas/org.schema/WebPage/jsonschema/1-0-0)
Should we rename this context to avoid confusion?

No I think it's okay - it's two different vendors' "take" on a web-page...

That makes sense.

Given the other contexts are opt-in, it would be cleaner to have the web_page context off by default. Perhaps we could have it turned on in all our examples to make it clear that it's recommended?

Sounds good to me.


Math rendering problems

PDF.js often has trouble rendering mathematical expressions in PDF documents that are compiled from LaTeX. Particularly affected are summation signs (\sum), square roots (\sqrt), tensor products (\otimes), and brackets (\langle, \rangle, (, ) etc.). They are often stretched vertically way too much. This effect is diminished if one zooms in sufficiently. This problem is quite pervasive and it seems to affect a large fraction of PDF files on the arXiv repository. Below are several examples from a document where the problem is particularly noticeable.
Link to PDF file (or attach file here): https://arxiv.org/pdf/1703.08346.pdf
Configuration:

Web browser and its version: Firefox 52.0.1 (64-bit)
Operating system and its version: Linux Mint 18.1 Cinnamon 64-bit
PDF.js version: 1.6.315
Is an extension: no

Steps to reproduce the problem:

Open the document
Set zoom to 100% or similar and scroll to pages 12, 13, 16, 22.

What is the expected behavior? (add screenshot)
Page 12:

Page 13:

Page 16:

Page 22:

What went wrong? (add screenshot)
Several mathematical symbols are stretched vertically.
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
I'm using the default viewer in Firefox.

From the information provided, I believe that this is a duplicate of (the fixed) issue #2594.

PDF.js version: 1.6.315

This issue should already be fixed by PR #7705, but please note that the patch is only included in PDF.js versions of 1.6.380 and above.
@marozols Please try downloading the file and opening it (using the "Open file" button on the right-hand side of the toolbar) with https://mozilla.github.io/pdf.js/web/viewer.html. Does the file render correctly there?

It renders just fine with the latest version of PDF.js. Too bad that Firefox doesn't ship the latest version.

It renders just fine with the latest version of PDF.js.

In that case, I'm closing this as duplicate of issue #2594.

Too bad that Firefox doesn't ship the latest version.

It's included in Firefox 53, since it was part of bug 1323915.


Bugfix/fix uploading of episode

Fix uploading of episode by waiting for navigation after logging in.
The first thing done after logging in is uploading the episode. After the logging in is done, we should wait for the navigation ot be completed using await page.waitForNavigation. Note, the call is encapsulated in try-catch in case navigation was not needed.
Additionally, refactor cleanUp and exiting

Merging. Thanks for the quick check.


release from master?

Hi! I filed #82 and although I still would love to see an example, it turns out that #69 at least partly addresses my confusion. Is there a timetable for a release from master? Would it be better to make a temporary lol-html-master on crates.io?
Thanks!

Hi - A new version has been released

Thank you!


CSETMODE is probably dispensible

Unlike CANDPERM or CRAM which are critical for memory allocation, CSETMODE only seems to be used when setting up pointers to functions, which typically only happens during program loading or JITing.  For an operation that's unlikely to be done more than 1e5 times in a program execution, we can probably lower it to:
CGETHIGH temp0, in
BINVI temp0, temp0, 25|47
CSETHIGH temp0, in, temp0
CBUILDCAP out, in, temp0

Yes - but there is a big performance difference between the two sequences.
A minimal ISA set without csetmode would be acceptable.

The question is whether the dynamic counts of CSETMODE in real-world applications are high enough for anyone to notice replacing them with a four-instruction sequence.  I'm not proposing to define a new extension, either CSETMODE is a frequently used instruction or it isn't.

there are many such examples - analysis of the frequency of usage of all instructions is planned

In dynamic traces of test workloads of specint benchmarks, pure-cap, statically linked, CSetFlags (the old equivalent of SetMode) did not appear even once.  I imagine this implies that we're only successfully tracing userspace (I'm relying on the objdump of the binary to lookup the actual instructions, so kernel instructions won't be found); CSetFlags was surely used by the loader at some point, for example.
A static count of a pure-capability kernel found 10 instances of CSetFlags.

Also, for something like the loader, one could keep an executable root capability for each mode, and just choose the right one for deriving executable capabilities, avoiding even the very rare uses of this instruction.

CSetMode is definitely used by rtld, you must not be tracing correctly

@jrtc27 These were statically linked benchmarks; I presume tracing began after the benchmark began running and after loading.  (These were traced by Mingle) Is it conceivable that rtld did not run after the benchmark began executing?

Static linking by definition means no rtld

The latest version of CHERI RISC-V allows using most of the ISA extension with a different encoding. However, this requires that we provide instructions to perform all capability manipulation operations without having to manually fiddle with the metadata and then using CBLD, so the CSETMODE (now SCMODE) must remain and we added related instructions like GCMODE, GCTYPE, etc even though they are probably used infrequently.


Add new language

Projects:
https://crowdin.com/project/grav-admin
https://crowdin.com/project/grav-core
Required language:
Sinhala (si)

Added.. thanks.


Make reprogramming more user-friendly

If the user presses the reprogram button without first pressing the white button on the Teensy, a dialog will appear. This dialog tells the user to press the white button, and when they do, will continue the reprogramming process.

Looks good, merging.


improvements for mobile device support of the webUI

made layout responsive to mobile devices
formatted uptime (this would be better done in the socket code)
added mobile web app icon
added prompt to pin webUI to device homescreen
added shape formatting to red/green indicators for accessibility
updated styles to reflect current design recomendations
suggestion for socket data - add RPi board temperature
/sys/class/thermal/thermal_zone0/temp

Excellent! Good suggestion on the RPi board temperature.

https://github.com/cyoung/stratux/commit/ecd29a8425c5bb8b1088a65d9df6ccd6f50444c2

Getting:
 TypeError: time_parts is null

And "Uptime: --". Just after starting.

Ok. Let me check that. I was getting the error on the local uptime temporary variable but there must be a condition when uptime is defined but the value is unrecognized.

What about formatting the uptime on the server side. It looks like Go provides a way to represent time in about any conceivable format.

Sure, how do we want it formatted?

Actually I was about to suggest the opposite. Separate data from formatting. Keep the format in the JS code

Well, let's do that then. Ball is in your court :)
Here is a string that breaks the current display: "Uptime":"7.004683139s"

That sting would indeed break my code. Sorry about that. Working on the code now.

This will take a little while. I'm going to need to build a Dev environment


Export applications to a PDF

Program Administrators would like to have the option to export and save a PDF version of a program application.
Describe the solution you'd like
It would be helpful if there was an "Export to PDF" button when Program Admins view an individual application.
Additional context
This is needed for auditing purposes. Program staff also find it easier to view individual applications from the "View Applications" screen than reviewing in the excel export.
Mock-up attached ("Export PDF of Application")

For whoever implements this:
The code base already has some of the needed functionality to support this, which should reduce the level of effort to meet the basic requirements. See https://github.com/seattle-uat/civiform/blob/main/universal-application-tool-0.0.1/test/services/export/PdfExporterTest.java

@swatkat1 -- Are you able to give an ETA on this one? Program staff are excited that it will help resolve some process pains.


c/c++

Issue Type: Feature Request
can not compile my c files although the path and extension installed.
VS Code version: Code 1.66.1 (8dfae7a5cd50421d10cd99cb873990460525a898, 2022-04-06T14:50:12.141Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Is this an issue with the vscode c++ extension, or with your own project's setup? If it's an issue with the C++ extension, please file an issue on that repo


Blurry thanks message

This does not work:
-webkit-font-smoothing: subpixel-antialiased;

For unknown reasons this works: transform: scale(10) translate(0, -30px);, instead of transform: scale(10) translate(0, -100%);.

:open_mouth: ok. Of course I prefer relative units, but hey...

Also: We want smooth as butter animations at 60 fps
Conditions:

:ballot_box_with_check: Never ever animate with javascript
:ballot_box_with_check: Use CSS animations
:ballot_box_with_check: Use CSS animations but restrict yourself to translate, scale, rotate and opacity

What we didn't have:

Use will-change to promote an element to its own layer. Most browsers will do this on their own but you can help them with this attribute.

FIxed with 52034e39bdf75bee62d7e85767e480f83ca2a161

Wow, good job!

Closed in #5


Remove coverage badge from README.md

This is looking really bad currently. We can consider adding this back later once the coverage is boosted.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 8.15%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
311

Relevant Lines:
3816

💛  - Coveralls

Personally, I prefer keeping it since it encourages us to complement the tests. WDYT
/cc @kubeflow/wg-training-leads

Personally, I prefer keeping it since it encourages us to complement the tests. WDYT

Interesting. I actually agree with you but the coverage report is available in PRs anyways. IMO README is more for users to gain understanding and trust of the project. Happy to hear any feedback from others though.

I agree with  @gaocegege  IMO Since it is that bad, we have to prioritise it before any major task for the next release.

Something like https://github.com/kubeflow/training-operator/pull/1473#issuecomment-974408580 is already very useful (although that shows 24% coverage).

Closing this. Now we are at 24% which can be improved soon.


Update editor.less for .pageLine

Change the .pageLine (page break) border from bottom to top, since any text on the same line is part of the following page rather than the preceding page.  Also, background-color had a value of fade( ... ) which I wasn't familiar with, and didn't seem to be doing anything.  Replaced with a slight linear gradient.  I'm not very attached to the gradient.

Some changes to the file to line up the colons.
I took this up with the thought of maybe someday allowing a toggle to add page number and footer snippets to every new page.

In the latest commit I basically undid what I originally set out to do, because along the way it was determined that \page would only work when alone on a line.  And I wasn't married to the idea.
NOW....this PR is about adding a page number to the .pageLine in the editor.  It does this with only CSS using an :after pseudo element and css counters, in the same way auto page numbering snippet works.   This may help users navigate long brews in the editor.
This should not be interpreted as a match to a .pageNumber snippet, as users can start those however often they like.  However, it should match the page counter in the bottom right of the preview window.

I do like the page numbering.
I'm not sold on the CSS styling of the line though. Removing all the background color makes it much harder to locate the start and end of a page simply because it looks like standard paragraph text with an easy-to-miss underline.
How about something like
background: linear-gradient(to bottom, white, #33333328 40%);
border-bottom: #339 solid 1px;

This way we keep the underline which I think it important, we keep a distinctive background, but it has just the slightest of gradients at the top to blend into the page above.
This does bring up another question though... I feel like the \page separator should actually belong to the page below. Like, the divider that created page 2 seems like it should be a part of page 2, not page 1? And scrolling to the bottom of the page content to find what page it is doesn't quite click for me. What do you think?

So to your last question:  That is what I was originally concerned about when I first opened this PR, before I changed direction.  When \page was still possible even with other text on the same line (\page more text here), it was evident that the following text was being placed on the "second" or new page.   This meant it was more clear to have the solid black border at the top of the .newLine.
However, the change was made that nothing else could appear after \page on the same line, if you wanted to actually create a new page, so this became less relevant.
In my mind's eye I could see re-allowing text on the same line as \page (only after).   This could play well with the future possibility of #1489, allowing the .page element to be targeted by a curly injector right on the same line as \page.  For instance, adding a pre-made page layout using a class name:
\page {coverPage}

Or replacing the default background image:
\page {background-image:url(imgur.com)}

In both examples the style is being applied to the new page, below \page.  And more to the point for this PR, a page number could be included as done in the latest commit and that page number would be at the "top" of the page in the editor as you prefer.
Of course, the first page has to be considered, since it currently doesn't have a \page line.   So if we do the above, the first page wouldn't have the page number etc.  But what if all pages required \page at the start, including the first page?  A new document would already come preloaded with \page at the top, along with it's page number.  If the user deletes that first line, it would just show the brewRenderer background with a tip on how to get started (or a random rotating choice of 'tips'):

Overall, this makes the first page consistent with the rest of the pages, allows page numbering from "1" to be displayed at the top of the page, and a convenient place for parent-element injection.  Finally, it is also a good spot for commented "page names" for easy reference if we ever introduce code folding by page:
\page /* Table of Contents */
\page /* Class Descriptions */
\page /* Equipment */

There's still possibility that we can allow content after \page on the same line at a later date. Don't let that be the deciding factor, but also keep in mind that is probably far down the road because it involves writing a whole separate Markdown extension just for that special case.
We can discuss requiring \page at the start (as it is now, the last page will be missing a page number) in a separate PR I think, since this one is aimed at just adding page numbers.
I say we move ahead with associating \page with the start of a new page. So lets move the border to the top to make it clear \page belongs to the page contents below, and let's just leave Page 1 unlabeled for now. It's obvious enough that the top of the document coincides with page 1 for now, and we can address it later after some discussion on the Gitter perhaps.

Updated this PR to match the change requests.....Page Number starts at '2' now.   Removed the gradient entirely though as I now think that a single line height gradient looks a little silly, and doesn't fit the design of the overall site (gradients are used nowhere else).
If ever we allow \page at the start of the document as discussed, the start of the page incrementing will need to be worked out....right now, the first incrementation from 0 is done by counting .codeEditor, and then subsequent .page elements.
Does this address #846?  Wasn't sure if we should leave that open and plan for a more explicit page indicator to match the preview side.

Does this address #846? Wasn't sure if we should leave that open and plan for a more explicit page indicator to match the preview side.

I think it addresses it. I'll try to get this PR merged tonight. Good work!


fix: GuiUtils.showMessageDialog: don't block the application thread (#551)

for #551. Though note this PR changes the method used by all showMessageDialog callers, not just that one about starting the game.
How to test

In Settings / Advanced Options, add some nonsense like -XX:+PleaseCrash💥 to Java Arguments.
Run the game. (download first, if necessary.)
After five seconds, you should see a dialog pop up saying "Could not start the game!"
After dismissing that dialog the application should respond as normal. (can select menus, switch between tabs, etc.)

Oh, that's a good question, I'll check.
On Linux:

No, the user still has to dismiss the dialog before using the main UI. It seems like .showAndWait is still doing its job in that regard.

I don't have a Windows to test on.


Will not be merged: Spark timestamptz discrepancy

I ran into this issue when I was trying to improve our tests for verifying write integrity for the timestamp types following our recent implementations for supporting inputs of other precisions and timezones.
This Draft PR demonstrates a discrepancy with Spark Iceberg where TimestamptzType is being read as TimestampType versus in PyIceberg where it is correctly being read as TimestampType.

Here's the dataframe schema that represents the Iceberg tables that are loaded through:

Spark Iceberg
PyIceberg

Spark Iceberg loads both timestamptz and timestamp types as timestamp, whereas PyIceberg is able to distinguish these two types correctly
tests/integration/test_writes/test_writes.py:1063: AssertionError
----------------------------- Captured stdout call -----------------------------
timestamp_s               datetime64[ns]
timestamptz_s             datetime64[us]
timestamp_ms              datetime64[ns]
timestamptz_ms            datetime64[us]
timestamp_us              datetime64[ns]
timestamptz_us            datetime64[us]
timestamp_ns              datetime64[ns]
timestamptz_ns            datetime64[us]
timestamptz_us_etc_utc    datetime64[us]
timestamptz_us_z          datetime64[us]
dtype: object
timestamp_s                    datetime64[us]
timestamptz_s             datetime64[us, UTC]
timestamp_ms                   datetime64[us]
timestamptz_ms            datetime64[us, UTC]
timestamp_us                   datetime64[us]
timestamptz_us            datetime64[us, UTC]
timestamp_ns                   datetime64[us]
timestamptz_ns            datetime64[us, UTC]
timestamptz_us_etc_utc    datetime64[us, UTC]
timestamptz_us_z          datetime64[us, UTC]
dtype: object


Unable to add limit to schema type array

 Schema configuration updates

This happened in 2.17.x.


Implement glossary

This can be used for definitions which can then be referenced in the manuscript.

(Hi, only comments to check if I am in the right direction)
At this moment <glossary> element is not at the "Simple JATS" of docs/TextureArticle. Yes, is an useful element in my opinion... But let's check in deep:

There are no simpler alternative as <p> staring with terms in bold, because lack of glossary-semantic. The <list list-type="simple"> is simpler but the adaptations may be complex...

There are similar-semantic element, <def-list> that can generate some confusion... Perhaps this discussion is about both, glossary and def-list.

Is useful and a "in use" documental structure:

Generic glossaries are in use in nowadays, the analog tag in HTML was porpused in ~1995 as <dl> element... And was preserved  as it, in HTML3, HTML4 and HTML5.

Scientific literature use it in nowdays. (need sources to assertion?)

...?  ... Substance JATS corpus statiscs (exist?) show some significative  frequence of use of  glossary or def-list tags?

...?  ... Substance Manuscript corpus statiscs (exist?) show some significative "intention of use"? Perhaps the HTML Manuscripts have some occurences of dl.


Move test syscall handler to new runtime implementation

Closes #916
Introduced changes

It moves TestExecutionSyscallHandler to the new runtime implementation
Isolates the abstractions of implementing a cheatcode and overriding a syscall

Checklist

[x] Linked relevant issue
[x] Updated relevant documentation
[x] Added relevant tests
[x] Performed self-review of the code
[x] Added changes to CHANGELOG.md

Future work: #1207 #1209


amplify init issues after updating to latest amplify version

Describe the bug
I cloned a fresh version of my current project, however upon amplify init (after updating to the latest amplify version), I am getting issues with file not found errors. I assume the issue is that a file is not being generated upon build step.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.29.2
To Reproduce
Steps to reproduce the behavior or terminal output if applicable
Running amplify init
Expected behavior
A clear and concise description of what you expected to happen.
Amplify should be initialized such that basic functionalities should work.
LOGS
$ amplify init
Note: It is recommended to run this command from the root of your app directory
? Do you want to use an existing environment? Yes
? Choose the environment you would like to use: prod
? Choose your default editor: Vim (via Terminal, Mac OS only)
Using default provider  awscloudformation
For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html
? Do you want to use an AWS profile? Yes
? Please choose the profile you want to use default
✖ There was an error initializing your environment.
init failed
Error: ENOENT: no such file or directory, stat '/XXX/XXXX/PROJECT/amplify/.temp/#current-cloud-backend/function/createPostAndTimeline/src/node_modules/.bin/loose-envify'
    at Object.statSync (fs.js:1016:3)
    at Object.statSync (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graceful-fs/polyfills.js:307:34)
    at getStatsSync (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/fs-extra/lib/util/stat.js:58:18)
    at Object.checkPathsSync (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/fs-extra/lib/util/stat.js:90:33)
    at copyDirItem (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:119:29)
    at /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:113:39
    at Array.forEach (<anonymous>)
    at copyDir (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:113:23)
    at mkDirAndCopy (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:108:3)
    at onDir (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:99:25) {
  errno: -2,
  syscall: 'stat',
  code: 'ENOENT',
  path: '/XXX/XXXX/socialmarket/amplify/.temp/#current-cloud-backend/function/createPostAndTimeline/src/node_modules/.bin/loose-envify'
}

Desktop (please complete the following information):

OS: MAC
Node Version. You can use node -v to check the node version on your system
v12.18.3

Additional context
Add any other context about the problem here.
I was following the Boyaki guide here: https://amplify-sns.workshop.aws/en/00_prerequisites.html
After completing #5, I tried to clone my repo from another machine. However, amplify init is giving me errors with configuring my workspace.

@alexlao Thanks for the issue I am can you share the package.json from your lambda?

Hi @ammarkarachi, thanks for helping us take a look! Here's the package.json for the lambda
{
"name": "createPostAndTimeline",
"version": "2.0.0",
"description": "Lambda function generated by Amplify",
"main": "index.js",
"license": "Apache-2.0",
"dependencies": {
"aws-appsync": "^4.0.1",
"graphql-tag": "^2.11.0",
"node-fetch": "^2.6.1"
}
}

Thanks for the update I tried using the same libraries and reiniting, I am suspecting there is a missing package in the node modules of you amplify installation. Would you be able to reinstall amplify-cli?

I've cleared my workspace, reinstall amplify-cli and am getting the same issue. I was fine before I updated my amplify version the other day, which is why I suspect it could be a versioning issue.

I am sorry I should have asked you to email it earlier to<EMAIL_ADDRESS>be sure to put the issue number in the subject

Thanks. Just sent. Gmail blocks tars from sending, so I've attached a link that points to my google drive to access the tar

@alexlao Thanks!

Had the same issue. The issue we had was because of broken symbolic links inside one of then node_modules/.bin folder. The symbolic links were having a backslash instead of forward slash.

We resorted to downloading the #current-cloud-backend.zip from the S3 bucket which has the last pushed changes. Fixed up the broken sym links and re-uploaded to the S3 bucket again. amplify pull worked then !!
Not sure if this was the right way to go but just sharing what worked for us or rather how me made it work. Would love to know if we have better solutions for this..


[Docs] Allow providing a custom theme and preview it live

We're going to make a lot of modifications to our theme soon, and I was thinking that it'd be really cool if I could enter a custom theme (JS and all) in the material-ui docs, through an inline editor, and navigate through all the docs with that theme.
Benefits:

Previewing and testing custom theming options is a breeze
Remove all "customization" demos from the components, and add a button that loads a pre-defined global theme, which then modifies all demos in real time: "Try Button with different themes"
Potentially improve the interactivity of the customization docs, making theming more aproachable for every one

This is obviously a huge effort, but as you can already change the theme colors across the website, maybe there is some infrastructure in place already to do this.

@mbrookes Has started an effort in this direction a couple of days ago, an early preview:  https://github.com/mbrookes/material-ui/tree/docs-themetool. Feedback appreciated!

Ha, yeah that's exactly what I was thinking about!
Here's some feedback:

It'd be great if the theme was accessible via the top navigation bar, like the colors currently are. Modifying it in a Dialog would be great on Desktop, or maybe in a Drawer that persists across navigation
Not sure what the limitations are of this editor, but it crashed when I tried to declare a const or var

Probably needs an error boundary or something around it if people write bad/unsupported code
Are there other code editors that could allow for richer JavaScript? So people can paste their current configs in more easily

As I mentioned above, theme shortcuts on individual component demos would be awesome

Each component demo could have a dedicated section called "Customization", with a couple themes that you can apply in a single click, and a quick way to copy each theme into your own code

Great stuff! This could be a killer feature for this docs website, pushing and helping everyone make material-ui their own, very fast :)

Probably needs an error boundary or something around it if people write bad/unsupported code

Yep, this was just a rough POC.

Are there other code editors that could allow for richer JavaScript?

This is the editor that underpins VSCode, so I doubt it! 😄 The issue isn't the editor, it's how to eval the resulting text.


Fix typo in comment.

core/color.js and core/tags.js are described in API Reference, so I PR.

Thanks!!


Auto Save is not working as expected.

Auto save feature as it worked in 1.4.0 is not functioning in 1.4.2.

Edits are not Auto saved when the internet connection is lost(offline)
Open en_tn TSV file, make an edit.
Turn off the wifi (Console>Network>Offline)
Click on Save button. The save button functions as if it saved the changes(Alert message pops up"Error saving the file").
Turn on the wifi/internet.
Open the edited file again. Note that the changes are not saved. (This works in 1.4.1)

Case II:When edits are made on DCS and the app has an autosave file, The app shows a popup message for the user to chose to either Keep or Discard the auto Save file. In this case, user is unable to keep the autosave file. The message keeps on popping back till the user chooses to discard the autosave changes.

Make edits to a file in a user branch.(Use the same file that we used in Case I)
Open TCC and open the file. The app shows a modal to either Keep or discard the autosave file.
Select the option "Keep the auto savefile ". Note that the file shows the changes from the DCS instead  of the autosaved file.
The modal keeps on popping up till you choose "Discard my autosave file"

Auto save feature as it worked in 1.4.0 is not functioning in 1.4.2.

Edits are not Auto saved when the internet connection is lost(offline)
Open en_tn TSV file, make an edit.
Turn off the wifi (Console>Network>Offline)
Click on Save button. The save button functions as if it saved the changes(Alert message pops up"Error saving the file").
Turn on the wifi/internet.
Open the edited file again. Note that the changes are not saved. (This works in 1.4.1)

Case II:When edits are made on DCS and the app has an autosave file, The app shows a popup message for the user to chose to either Keep or Discard the auto Save file. In this case, user is unable to keep the autosave file. The message keeps on popping back till the user chooses to discard the autosave changes.

Make edits to a file in a user branch.(Use the same file that we used in Case I)
Open TCC and open the file. The app shows a modal to either Keep or discard the autosave file.
Select the option "Keep the auto savefile ". Note that the file shows the changes from the DCS instead  of the autosaved file.
The modal keeps on popping up till you choose "Discard my autosave file"

Found a problem in translationCore Create - v1.4.2 build 139-e045820. When we switch files from the drawer, the autosave data is persisted and copied to the other file.

Open Gen.tsv and make some edits. do not save.
From the drawer menu, select Exodus.tsv. Note that the autosave from Gen is persisted and when Exodus is opened, the target side stays as Gensis.

I see a newer build and I tested the issue and found that its resolved in translationCore Create - v1.4.2 build 142-498b6eb

Looks good in translationCore Create - v1.4.2 build 142-498b6eb.


Heroku config updates

needed to work on Heroku

Thanks for creating a pull request. Although the live demo is hosted on Heroku, I'd like to leave these types of changes up to the developer. I plan on adding a wiki article that addresses deploying to Heroku.


Correction for raw affiliation Centre Atlantique de Philosophie,  França

Correction needed for raw affiliation Centre Atlantique de Philosophie,  França
raw_affiliation_name: Centre Atlantique de Philosophie,  França
new_rors: 059ynac98
previous_rors:
works_examples: W3163720416
contact: b420c5cecd3041b08ad67d547755d56c:c4b5ffac1ef34839bd0317db1a211f @ univ-nantes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Fix/cb error

update for https://github.com/luvit/luv/issues/663
Maybe found another bugs.
ok 5 shrinking interval using methods
ok 6 timer init
ok 7 timer huge timeout
  e:    Error in timeout callback
Uncaught Error: (null)
ok 8 timer callback with errors
# All tests passed

not call metamethod __tostring in object

https://github.com/neovim/neovim/issues/12045#issuecomment-603445165

See my comments in https://github.com/luvit/luv/issues/663. I think cfc2621c12480cc5311d4fc1497b3bee9dd7c6d1 is okay, but e3c93a6a79676bf4145ac4aa6c82f25556ba1dd7 should not be part of this.


chef server 12.0.2 fresh setup failed on CentOS 6.6

Hello guys,
I am a fresh bird in chef world. Today is my second time to setup chef server 12.0.2 on linux. Last time on RedHat 5.5 is also crased with similar issues.
Here are my steps. I followed the official document.

Setup a CentOS 6.6 x86_64 on Virtual box 3.20 with 1 core , 3 GB RAM and 40G storage.
Upload the newest file chef-server-core-12.0.2-1.x86_64.rpm.
rpm -Uvh chef-server-core-12.0.2-1.x86_64.rpm //successfully
4.chef-server-ctl reconfigure
// First warning : the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should not be loaded in the same Ruby VM
The result is good .
Running handlers:
Running handlers complete

Chef Client finished, 46/394 resources updated in 23.49545599 seconds
opscode Reconfigured!

Adding administrator user and organization. //successfully
Adding Chef manager.
chef-server-ctl install opscode-manage  //failed

[root@chefser chef]# chef-server-ctl install opscode-manage
the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should not be loaded in the same Ruby VM
falling back to ffi which might work (or might not, no promises)
the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should not be loaded in the same Ruby VM
falling back to ffi which might work (or might not, no promises)
Starting Chef Client, version 11.12.2
Compiling Cookbooks...
Converging 3 resources
Recipe: private-chef::add_ons_wrapper
  * ruby_block[addon_install_notification_opscode-manage] action nothing (skipped due to action :nothing)
Recipe: private-chef::add_ons_remote
  * yum_repository[chef-stable] action createRecipe: <Dynamically Defined Resource>
  * template[/etc/yum.repos.d/chef-stable.repo] action create
    - create new file /etc/yum.repos.d/chef-stable.repo
    - update content in file /etc/yum.repos.d/chef-stable.repo from none to c6e6e2
        --- /etc/yum.repos.d/chef-stable.repo   2015-02-05 19:16:55.378546813 +0800
        +++ /tmp/chef-rendered-template20150205-27804-1askjpb   2015-02-05 19:16:55.386546813 +0800
        @@ -1 +1,12 @@
        +# This file was generated by Chef
        +# Do NOT modify this file by hand.
        +
        +[chef-stable]
        +name=Chef Stable Repo
        +baseurl=https://packagecloud.io/chef/stable/el/6/$basearch
        +enabled=1
        +gpgcheck=1
        +gpgkey=file:///opt/opscode/embedded/keys/packages-chef-io-public.key
        +sslcacert=/etc/pki/tls/certs/ca-bundle.crt
        +sslverify=1
    - change mode from '' to '0644'
    - restore selinux security context

  * execute[yum-makecache-chef-stable] action run
    - execute yum -q makecache --disablerepo=* --enablerepo=chef-stable

  * ruby_block[yum-cache-reload-chef-stable] action create
    - execute the ruby block yum-cache-reload-chef-stable

  * execute[yum-makecache-chef-stable] action nothing (skipped due to action :nothing)
  * ruby_block[yum-cache-reload-chef-stable] action nothing (skipped due to action :nothing)

Recipe: private-chef::add_ons_remote
  * package[opscode-manage] action install
================================================================================
Error executing action `install` on resource 'package[opscode-manage]'
================================================================================

Chef::Exceptions::Exec
----------------------
 returned 1, expected 0

Resource Declaration:
---------------------
# In /opt/opscode/embedded/cookbooks/private-chef/recipes/add_ons_remote.rb

 48:   package pkg do
 49:     notifies :create, "ruby_block[addon_install_notification_#{pkg}]", :immediate
 50:   end
 51: end

Compiled Resource:
------------------
# Declared in /opt/opscode/embedded/cookbooks/private-chef/recipes/add_ons_remote.rb:48:in `block in from_file'

package("opscode-manage") do
  action :install
  retries 0
  retry_delay 2
  guard_interpreter :default
  package_name "opscode-manage"
  version "1.9.0-1"
  cookbook_name :"private-chef"
  recipe_name "add_ons_remote"
end

Running handlers:
  - #<Class:0x000000026c8930>::AddonInstallHandler
Running handlers complete

[2015-02-05T19:18:15+08:00] FATAL: Stacktrace dumped to /opt/opscode/embedded/cookbooks/cache/chef-stacktrace.out
Chef Client failed. 4 resources updated in 81.956794839 seconds
[2015-02-05T19:18:15+08:00] FATAL: Chef::Exceptions::Exec: package[opscode-manage] (private-chef::add_ons_remote line 48) had an error: Chef::Exceptions::Exec:  returned 1, expected 0

The out file is below.
Generated at 2015-02-05 19:18:15 +0800
Chef::Exceptions::Exec: package[opscode-manage] (private-chef::add_ons_remote line 48) had an error: Chef::Exceptions::Exec:  returned 1, expected 0
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/mixin/command.rb:158:in `handle_command_failures'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/provider/package/yum.rb:1019:in `yum_command'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/provider/package/yum.rb:1134:in `install_package'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/provider/package.rb:82:in `block in action_install'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/mixin/why_run.rb:52:in `call'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/mixin/why_run.rb:52:in `add_action'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/provider.rb:155:in `converge_by'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/provider/package.rb:80:in `action_install'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/provider.rb:120:in `run_action'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/resource.rb:637:in `run_action'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/runner.rb:49:in `run_action'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/runner.rb:81:in `block (2 levels) in converge'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/runner.rb:81:in `each'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/runner.rb:81:in `block in converge'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/resource_collection.rb:98:in `block in execute_each_resource'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/resource_collection/stepable_iterator.rb:116:in `call'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/resource_collection/stepable_iterator.rb:116:in `call_iterator_block'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/resource_collection/stepable_iterator.rb:85:in `step'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/resource_collection/stepable_iterator.rb:104:in `iterate'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/resource_collection/stepable_iterator.rb:55:in `each_with_index'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/resource_collection.rb:96:in `execute_each_resource'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/runner.rb:80:in `converge'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/client.rb:345:in `converge'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/client.rb:431:in `do_run'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/client.rb:227:in `run'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/application.rb:217:in `run_chef_client'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/application/solo.rb:221:in `block in run_application'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/application/solo.rb:213:in `loop'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/application/solo.rb:213:in `run_application'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/lib/chef/application.rb:67:in `run'
/opt/opscode/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.2/bin/chef-solo:25:in `<top (required)>'
/opt/opscode/embedded/bin/chef-solo:23:in `load'
/opt/opscode/embedded/bin/chef-solo:23:in `<main>'
~

Is it means my network has someproblem to login packagecloud ?
How can I resolved these 2 issues.

the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should not be loaded in the same Ruby VM
running failed in chef manage

Thanks.

By the way I have ruby already.
[root@chefser sft]# yum list ruby
Loaded plugins: fastestmirror, refresh-packagekit, security
Loading mirror speeds from cached hostfile
Installed Packages
ruby.x86_64                              <IP_ADDRESS>4-3.el6_6
[root@chefser sft]# which ruby
/usr/bin/ruby
But gem is not support.
[root@chefser sft]# gem install package_cloud
-bash: gem: command not found

You can safely ignore the Ruby warning. Chef server uses it's own embedded
Ruby and whether or not you have Ruby installed has no bearing on this
problem. That warning message is fixed in a more recent version.
As for the inability to install Manage, what happens if you do sudo yum install opscode-manage after this happens? That may work. Will have to
look into why it's failing with this command though. Please let me know how
it turns out.
Thanks
On Thu, Feb 5, 2015 at 5:42 AM, illidanpc<EMAIL_ADDRESS>wrote:

By the way I have ruby already.
[root@chefser sft]# yum list ruby
Loaded plugins: fastestmirror, refresh-packagekit, security
Loading mirror speeds from cached hostfile
Installed Packages
ruby.x86_64 <IP_ADDRESS>4-3.el6_6
[root@chefser sft]# which ruby
/usr/bin/ruby
But gem is not support.
[root@chefser sft]# gem install package_cloud
-bash: gem: command not found
—
Reply to this email directly or view it on GitHub
https://github.com/chef/chef-server/issues/83#issuecomment-73033490.

--
Nathan L Smith
<EMAIL_ADDRESS>

I had a very similar issue although on CentOS 6.6 x86_64:
    ================================================================================
    Error executing action `run` on resource 'execute[chef-server-ctl install opscode-reporting]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '1'
    ---- Begin output of chef-server-ctl install opscode-reporting ----
    STDOUT:
    ================================================================================
    Error executing action `install` on resource 'yum_package[opscode-reporting]'
    ================================================================================

    Chef::Exceptions::Exec
    ----------------------
     returned 1, expected 0

    Resource Declaration:
    ---------------------
    # In /opt/opscode/embedded/cookbooks/cache/cookbooks/private-chef/recipes/add_ons_remote.rb

     48:   package pkg do
     49:     notifies :create, "ruby_block[addon_install_notification_#{pkg}]", :immediate
     50:   end
     51: end

    Compiled Resource:
    ------------------
    # Declared in /opt/opscode/embedded/cookbooks/cache/cookbooks/private-chef/recipes/add_ons_remote.rb:48:in `block in from_file'

    yum_package("opscode-reporting") do
      action :install
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      package_name "opscode-reporting"
      version "1.2.3-1"
      timeout 900
      flush_cache {:before=>false, :after=>false}
      declared_type :package
      cookbook_name "private-chef"
      recipe_name "add_ons_remote"
    end

    [2015-03-05T00:48:22+00:00] FATAL: Stacktrace dumped to /opt/opscode/embedded/cookbooks/cache/chef-stacktrace.out
    [2015-03-05T00:48:22+00:00] FATAL: Chef::Exceptions::Exec: yum_package[opscode-reporting] (private-chef::add_ons_remote line 48) had an error: Chef::Exceptions::Exec:  returned 1, expected 0
    STDERR:
    ---- End output of chef-server-ctl install opscode-reporting ----
    Ran chef-server-ctl install opscode-reporting returned 1

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/aws_ha_chef/recipes/reporting.rb

     11: execute 'chef-server-ctl install opscode-reporting' do
     12:   not_if "rpm -q opscode-reporting"
     13: end

    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/aws_ha_chef/recipes/reporting.rb:11:in `from_file'

    execute("chef-server-ctl install opscode-reporting") do
      action "run"
      retries 0
      retry_delay 2
      default_guard_interpreter :execute
      command "chef-server-ctl install opscode-reporting"
      backup 5
      returns 0
      declared_type :execute
      cookbook_name "aws_ha_chef"
      recipe_name "reporting"
      not_if "rpm -q opscode-reporting"
    end

[2015-03-05T00:48:23+00:00] INFO: Running queued delayed notifications before re-raising exception
[2015-03-05T00:48:23+00:00] ERROR: Converge failed with error message execute[chef-server-ctl install opscode-reporting] (aws_ha_chef::reporting line 11) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'

However I was able to manually install opscode-reporting:
Downloading Packages:
Setting up and reading Presto delta metadata
Processing delta metadata
Package(s) data still to download: 127 M
opscode-reporting-1.2.3-1.x86_64.rpm                                                                                | 127 MB     02:53
warning: rpmts_HdrFromFdno: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY
Retrieving key from file:///opt/opscode/embedded/keys/packages-chef-io-public.key
Importing GPG key 0x83EF826A:
 Userid : CHEF Packages<EMAIL_ADDRESS> Package: chef-server-core-12.0.5-1.el6.x86_64 (installed)
 From   : /opt/opscode/embedded/keys/packages-chef-io-public.key
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
  Installing : opscode-reporting-1.2.3-1.x86_64                                                                                1/1
Thank you for installing the Opscode reporting addon!
  Verifying  : opscode-reporting-1.2.3-1.x86_64                                                                                1/1

Installed:
  opscode-reporting.x86_64 0:1.2.3-1

Complete!

This of course then resolved things. I'm still not sure why it fails when called from the recipe.

Having the same problem too.
Done the same steps as illidan except the ruby install. Running sudo yum install opscode-manage  doesn't work also.
See error logs below:
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.mirror.secureax.com
 * extras: centos.mirror.secureax.com
 * updates: centos.mirror.secureax.com
No package opscode-manage available.
Error: Nothing to do

[root@localhost ~]# sudo chef-server-ctl install opscode-manage
Starting Chef Client, version 12.0.3
resolving cookbooks for run list: ["private-chef::add_ons_wrapper"]
Synchronizing Cookbooks:
  - yum
  - apt
  - runit
  - enterprise
  - build-essential
  - yum-epel
  - private-chef
Compiling Cookbooks...
Converging 3 resources
Recipe: private-chef::add_ons_wrapper
  * ruby_block[addon_install_notification_opscode-manage] action nothing (skipped due to action :nothing)
Recipe: private-chef::add_ons_remote
  * yum_repository[chef-stable] action create
    * template[/etc/yum.repos.d/chef-stable.repo] action create (up to date)
    * execute[yum-makecache-chef-stable] action nothing (skipped due to action :nothing)
    * ruby_block[yum-cache-reload-chef-stable] action nothing (skipped due to action :nothing)
     (up to date)
  * yum_package[opscode-manage] action install
    * No version specified, and no candidate version available for opscode-manage
    ================================================================================
    Error executing action `install` on resource 'yum_package[opscode-manage]'
    ================================================================================

    Chef::Exceptions::Package
    -------------------------
    No version specified, and no candidate version available for opscode-manage

    Resource Declaration:
    ---------------------
    # In /opt/opscode/embedded/cookbooks/cache/cookbooks/private-chef/recipes/add_ons_remote.rb

     48:   package pkg do
     49:     notifies :create, "ruby_block[addon_install_notification_#{pkg}]", :immediate
     50:   end
     51: end

    Compiled Resource:
    ------------------
    # Declared in /opt/opscode/embedded/cookbooks/cache/cookbooks/private-chef/recipes/add_ons_remote.rb:48:in `block in from_file'

    yum_package("opscode-manage") do
      action :install
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      package_name "opscode-manage"
      timeout 900
      flush_cache {:before=>false, :after=>false}
      declared_type :package
      cookbook_name "private-chef"
      recipe_name "add_ons_remote"
    end

Running handlers:
  - #<Class:0x00000001d4fb60>::AddonInstallHandler
Running handlers complete
[2015-05-03T01:29:46+08:00] FATAL: Stacktrace dumped to /opt/opscode/embedded/cookbooks/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 9.149255886 seconds
[2015-05-03T01:29:48+08:00] FATAL: Chef::Exceptions::Package: yum_package[opscode-manage] (private-chef::add_ons_remote line 48) had an error: Chef::Exceptions::Package: No version specified, and no candidate version available for opscode-manage

My error message says that:
Chef::Exceptions::Package
    -------------------------
    No version specified, and no candidate version available for opscode-manage

How can that be?

Seeing exact same error
Error executing action `install` on resource 'yum_package[opscode-manage]'

when running
chef-server-ctl install opscode-manage

Red Hat Enterprise Linux Server release 7.1 (Maipo)
chef-server-core-12.0.8-1.el6.x86_64

Ditto. I am working around it by removing the "if" altogether since I don't have any debian to manage..
getting:

RuntimeError -  I don't know how to install addons for platform family:

(note that the platform family is blank)
Version is:
CentOS Linux release 7.1.1503 (Core)

@tstrangio i think that you can use this work around to install manage:
curl -s https://packagecloud.io/install/repositories/chef/stable/script.rpm.sh | sudo bash
sudo yum install opscode-manage
chef-server-ctl reconfigure
opscode-manage-ctl reconfigure
but i couldn't find other opscode additional packages on the repo.
My conclusion is that only chef-server and opscode-manage(with work-around) support CentOS7 so it is still work in progress so, IMHO, is better to wait and continue with CentOS 6.6 for 1 or 2 months at least.

thanks @roviluca

@Roviluca your workaround worked for me as well. Thanks!

@Roviluca Works perfect.  Thanks!

Thanks @Roviluca that worked a treat! :metal:

+1 @Roviluca

Thanks! @Roviluca
Had the same issue on Amazon Linux.

Worked for me too, thanks

where is the script?  it is a ERROR 404 now

got the same error as @dvh-jenkins-github

Closing since this should no longer be an issue. Please reopen is needed.


Remove all relative requires by using webpack resolve.modules

I haven't removed ALL, because there are a lot of require('./blabla'), or require('../') that reference modules on the same part of the application, and these are trickier to automatically replace.
I'm OK-ish with require('./something'), because it usually refers to something that is very tied to the requiring module (a template, for example) but if you're already going up a few levels (../../../), it's probably better off as a module require.
Also, it makes refactoring the folder structure a nightmare, but if we had (for instance) cartodb3/components/..., everything would be easier to locate & rename.
I don't think we need to do all of it on this PR, though, this might as well be a Scout principle thing, and if you find a file that can be replaced.
It's probably worth to investigate an automated way to do these, either by writing a small program or something magical like https://github.com/facebook/jscodeshift
Also, this PR is against the PoC migration because there were already some webpack changes in there.
@CartoDB/frontend if you have any opinion on this matter, now's the time :grimacing:

Using jscodeshift (https://gist.github.com/rjimenezda/71ac3db88c76f2b0fcad6c2ba4278119) I've replaced all the '../' with the aliased path 🎉
I'll drop this on staging just to verify that nothing's weird, but it should've broken at build time.


Peering Request

Full Name
Marco Bungalski
ASN
59790
PeeringDB Integration

[X] My PeeringDB Entries are current
[X] Peer at ALL EXCHANGES (and skip the Peer Address(es) field below)

Peer Address(es)
No response
Multihop

[ ] Multihop Peering Request

Hi Marco
It does not look like we have any mutual IXP locations to set up peering.
Kind regards
Nina
RouteViews Peering team


Postcss plugin

This one is a follow-up to https://github.com/giakki/uncss/pull/212, that implements the plugin. I've verified that sourcemaps work correctly in my local testing/usage.

Curious, should I be using peerDependencies for the postcss dependency?

Wasn't peerDependencies dropped in npm 3?

Oh, hah, looks like I'm somehow still running npm 2 (I must have installed it ages ago, but really only started actively using npm a couple weeks ago, and must have gotten confused by the warnings I saw regarding peerDependencies).
Also potentially more worrisome, https://github.com/postcss/postcss says postcss doesn't work on 0.10.0 and provides a polyfill workaround. I've tried to set that up, but it still doesn't pass the travis build on 0.10.0. I suspect I'm going to need to install 0.10.0 locally to dig in before it's committable (assuming we want to retain bwcompat to 0.10.0)...but hopefully the rest of the change can be reviewed and stable in the meantime.

I'd say it's OK to drop 0.10 support if @giakki agrees too.

Well I got 0.10 to work, once I fixed my version comparison string.
Though another point of mention, phantom (either our use of it, or the library itself) seems to perform very poorly with concurrency. If you combine CSS before passing to Uncss, things work fine, but if you process multiple files in parallel (as is done in webpack without a choice), execution errors and you get malformed CSS. I've solved this by serializing all Uncss use (and thus Phantom use) across Postcas plugin invocations, but technically the problem still exists with regular Uncss (I ran into this problem when using gulp based setup that ran two tasks that called Uncss in parallel)
So this is fixed for Postcss parallelizatiom in this pull request, but let me know if you want me to serialize it for any/all invocations altogether.

@giakki: it might be worth giving @mikelambert push rights.

Wowzers! Thanks @mikelambert! I've given you push rights, you can merge this in! :smiley:

@XhmikosR I agree, we can safely drop support for 0.10, maybe we can test against 0.12?

@giakki: @mikelambert mentions above that he fixed 0.10 support so we should be OK for now.


 Should update so that images are orientated correctly.

I have a "Fix” for the inversion “problem”, however…

This may not be a problem - data geolocation is ok.

Data is Lower-Left oriented.
Typical TIFF viewers assume Upper-Left orientation.
GIS viewers will show the data correctly.

My current fix is not conditional and probably should be.

Only if Lat units is degrees, and increment is positive?

In fact, the code already had the implementation to invert the data, but it was commented out.  So the quick fix is to remove the comment markers.

Ok, I was suspecting this might be the case. If the metadata is correct and it's just a matter of the viewing software not using the metadata correctly I agree this is a non-issue.


[FLINK-11483][tests] Improve StreamOperatorSnapshotRestoreTest with JUnit's Parameterized

What is the purpose of the change
Improve StreamOperatorSnapshotRestoreTest with JUnit's Parameterized
Brief change log
In current we will test StreamOperatorSnapshotRestore with three backends: file, rocksdb full and rocksdb incremental, each in a separate class.
In the current patch, we improve this by using JUnit's Parameterized.
Verifying this change
This change is already covered by existing tests, such as StreamOperatorSnapshotRestoreTest.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@tzulitai changing the ping seemingly did not work, but now I saw it anyways :-) I have no objections against the refactoring, looks good to me. 👍


⚠ Cioos Pacific CKAN Sitemap has degraded performance

In 53ea3d0, Cioos Pacific CKAN Sitemap (https://catalogue.cioospacific.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 8472 ms

Resolved: Cioos Pacific CKAN Sitemap performance has improved in 8914085 after 5 minutes.


Optimizing inference container

Crop-mask inference runs inside docker containers in Google Cloud Run. These containers scale automatically with the amount of tif files available for inference but occasionally we still get the error:
The request was aborted because there was no available instance.

This issue has been partially addressed by adding retries into the Cloud Function that triggers the docker containers, however further container optimization as per below link would further alleviate this issue:
https://cloud.google.com/run/docs/tips/general#run_tips_global_scope-python

Closing in favor of #201


Initial checkin of DSO Week 3 Lab 1

Passwords must have:

11 characters
Mixed case letters
At least 1 number
At least 1 special character

This section needs a minor improvement:
aws sts assume-role \
--role-arn arn:aws:iam::100352119871:role/dso/ctrl/my-app/CTL-my-app-DeploymentAdmin \
--role-session-name student1-$$ --profile dso \
--serial-number arn:aws:iam::100352119871:mfa/student1 \
--token-code 123456

For example:

Store your username in .bash_profile and source the file to load it in your environment:

echo "export USERNAME=INSERT_YOUR_USERNAME_HERE" >> ~/.bash_profile
source ~/.bash_profile

Use STS to assume the control account role.

aws sts assume-role \
  --role-arn arn:aws:iam::100352119871:role/dso/ctrl/my-app/CTL-my-app-DeploymentAdmin \
  --role-session-name $USERNAME-$$ \
  --profile dso \
  --serial-number arn:aws:iam::100352119871:mfa/$USERNAME \
  --token-code YOUR_MFA_TOKEN

+1


Fentry failing to load on arm64

I am successfully building bootstrap, minimal, uprobe examples and they all work on M1 Macbook running an arm64 ubuntu VM but Fentry fails for some odd reason I can't figure out. Any tips on how to debug such issues:
$ uname -a
Linux devvm 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 09:01:50 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

$ sudo ./fentry
[sudo] password for sasan:
libbpf: loading object 'fentry_bpf' from buffer
libbpf: elf: section(2) fentry/do_unlinkat, size 200, link 0, flags 6, type=1
libbpf: sec 'fentry/do_unlinkat': found program 'do_unlinkat' at insn offset 0 (0 bytes), code size 25 insns (200 bytes)
libbpf: elf: section(3) fexit/do_unlinkat, size 256, link 0, flags 6, type=1
libbpf: sec 'fexit/do_unlinkat': found program 'do_unlinkat_exit' at insn offset 0 (0 bytes), code size 32 insns (256 bytes)
libbpf: elf: section(4) license, size 13, link 0, flags 3, type=1
libbpf: license of fentry_bpf is Dual BSD/GPL
libbpf: elf: section(5) .rodata.str1.1, size 76, link 0, flags 32, type=1
libbpf: elf: skipping unrecognized data section(5) .rodata.str1.1
libbpf: elf: section(6) .BTF, size 945, link 0, flags 0, type=1
libbpf: elf: section(7) .BTF.ext, size 364, link 0, flags 0, type=1
libbpf: elf: section(8) .symtab, size 144, link 12, flags 0, type=2
libbpf: looking for externs among 6 symbols...
libbpf: collected 0 externs total
libbpf: loading kernel BTF '/sys/kernel/btf/vmlinux': 0
libbpf: sec 'fentry/do_unlinkat': found 1 CO-RE relocations
libbpf: prog 'do_unlinkat': relo #0: kind <byte_off> (0), spec is [6] struct filename.name (0:0 @ offset 0)
libbpf: CO-RE relocating [0] struct filename: found target candidate [1115] struct filename in [vmlinux]
libbpf: prog 'do_unlinkat': relo #0: matching candidate #0 [1115] struct filename.name (0:0 @ offset 0)
libbpf: prog 'do_unlinkat': relo #0: patched insn #16 (LDX/ST/STX) off 0 -> 0
libbpf: sec 'fexit/do_unlinkat': found 1 CO-RE relocations
libbpf: prog 'do_unlinkat_exit': relo #0: kind <byte_off> (0), spec is [6] struct filename.name (0:0 @ offset 0)
libbpf: prog 'do_unlinkat_exit': relo #0: matching candidate #0 [1115] struct filename.name (0:0 @ offset 0)
libbpf: prog 'do_unlinkat_exit': relo #0: patched insn #22 (LDX/ST/STX) off 0 -> 0
libbpf: prog 'do_unlinkat': failed to attach: ERROR: strerror_r(-524)=22
libbpf: failed to auto-attach program 'do_unlinkat': -524
Failed to attach BPF skeleton

fentry is only supported on x86 architecture, unfortunately. arch_prepare_bpf_trampoline() has to be implemented for arm64 to allow this (at the very least).

Is there an easy way to check which calls are supported on arm64 vs x86? I looked around for quite a bit and wasn't able to tell if this was a config issue vs a support problem.

I don't think there is any easy way to check that except trying to load a simplistic fentry program, sorry.

If I see it correctly, then with https://github.com/torvalds/linux/commit/efc9909fdce00a827a37609628223cd45bf95d0b fentry should be available for arm64 since kernel version 6.0.
Unfortunately I have not been able to get it to work on the Raspberry Pi 4 B with kernel version 6.0 and 6.1RC8 fentry and get the same error message as @samp66.
bootstrap, kprobe, minimal_legacy, minimal, sockfilter, uprobe and tc work.
Is there any factor I have not considered?

@Jeftah  I can only recommend trying https://github.com/anakryiko/retsnoop or some similar tool to understand where the failure in kernel originates from, and go from there.


Branch 1.99.6

When completing the TO part of a job, people cannot state custom SQL statement by any means:

When both TableName and SQL statement are provided, it reports the'GENERIC_JDBC_CONNECTOR_0007("The table name and the table sql cannot be specified together")' exception.
When only the SQL statement is provided, it reports the 'Both table name and SQL cannot be specified' exception.

The modification we have made is simply to allow the TableName and the SQL statement can be input together and in this case, the SQL have the higher priority to be executed.

Hi @FuqiaoWang. We typically use jira and review board for handling issues and patches (the github exists purely as a mirror). Please submit your patch to: https://issues.apache.org/jira/secure/Dashboard.jspa and I would be happy to review it.

Thank you for your reply @afine, I have submitted my patch to:https://issues.apache.org/jira/browse/SQOOP-2916 .I would be very happy if you can review it.


Release version 2.1

There some some api-minor patches and the example code on the website changed to the new syntax for getViewport, which caused some confusion for people that use the NPM package. We should make a release of version 2.1 to solve this and other issues we found and fixed after version 2.0.

Hi Tim, is there any schedule? I'm really looking forward to this release!

BTW this getViewport change is a breaking change in documented area of the app, so that's actually api-major unless you support both old and new way of passing the arguments.

I don't think we have anything in the queue holding back a release. I don't mind taking core of this, so perhaps we can already do it next week if everyone agrees (/cc @brendandahl @yurydelendik).
The getViewport change is backwards compatible; refer to https://github.com/mozilla/pdf.js/pull/10369/files#diff-0ecad279ed2252e3eb47a4d96ec1463cR921. The old way of calling will still work and show a deprecation notice that the user should change it. It will only be removed in a major version (3.x).

make sure I'm not forgetting about something that really needs to be in version 2.1

Ideally, issue #10391 really ought to be fixed before the next release.

I'm able to make the release soon, but I'm a bit short on time to also address the issue mentioned above. @brendandahl Last time we released version 2.0, did you look at why the master branch for pdfjs-dist was not updated (see #10391). It would be nice if we can get that fixed before making a new release.

The issue above is now done, so I'll try to make the new release this weekend unless there are major objections (please comment here in that case). Doing that will also resolve the getViewport confusion.

The release of version 2.1.245 is done. However, because of misunderstood instructions on https://github.com/mozilla/pdf.js/wiki/Release-Process the version is called 2.2.2 on pdfjs-dist and NPM because I updated the pdfjs.config file before making the release. To prevent this from happening again, I updated to page to remove the section from https://github.com/mozilla/pdf.js/wiki/Release-Process/055c021ab425b3e88877a40d8cb18d3956d4832e about updating the version prefix since I read that as that it should happen first because api-minor changes were merged.
@brendandahl Is there a way we can change the version number to 2.1.245 on pdfjs-dist or NPM? I'm not sure if it's really a problem because a future release will have a higher version number anyway.

@timvandermeij Within 24 hours you can unpublish a version from npm. You could then publish a correct version again.

@wojtekmaj Thank you, I didn't know that.
@brendandahl Since the process is automated, I think only the bots or someone with the Node.js publisher account can do this. If we can remove it from NPM this way first, we can then remove it from pdfjs-dist manually and try to create a new release.

The following steps should be taken:

[x] Unpublish the release on NPM
[x] Unpublish the release on pdfjs-dist

[x] Remove the tag
[x] Remove the release
[x] Remove the commit

[x] Unpublish the release on pdf.js

[x] Remove the tag
[x] Remove the release
[ ] Revert the pdfjs.config version bumps

Any new on the re-release ofd version 2.1? I can see the pdfjs-dist package was unlisted.

I'll make the new release this weekend.

Closing since v2.1.266 is now published as a pre-release (next tag on NPM).


What version ...

What version of NLOG do I need to get to run on .NET 4.6 ?

I think my question is pretty straight forward:
What version of NLOG do I need to get to run it on .NET 4.6 ?

Think you can use any version from NLog ver. 1.0 and forward. Ofcourse the latest version is the best version :)
But I guess you are holding back information, that makes you think NLog will not work with NET4.6


[build_script.py] Deprecate obsolete parameters

"--swift-build-dir" and "--arch" are no longer used by the build script. We could remove them outright, but that would break CI. Instead, mark them as deprecated first. We will remove them once apple/swift's build script has been updated to no longer pass "--swift-build-dir" and "--arch".
The build script also contains some instructions on how to build, but these are duplicated in the README. Remove them to save us the trouble of updating two sets of instructions.

Let's give the CI a spin! Could someone please ask @swift-ci to please test? :grin:

@swift-ci please test

Wow, it worked!! Awesome. Thanks for setting this up, @shahmishal! One additional request, though: would it be possible to enable OS X builds for swift-corelibs-xctest as well? It would help with #43, for example--that pull request would like pass Linux CI but not OS X.

@modocache Yes, I will setup OS X bot for swift-corelibs-xctest. Thanks!

@modocache Yes, I will setup OS X bot for swift-corelibs-xctest. Thanks!


3.6.1 Missing

From the dockerhub README we should be able to pull python:3.6.1-alpine.
But we are running into the following error
$ docker pull python:3.6.1-alpine
Error response from daemon: manifest for python:3.6.1-alpine not found
$ docker pull python:3.6.1
Error response from daemon: manifest for python:3.6.1 not found

3.6.0 is the last know version that appears under tags

A docker build of Python 3.6.1 (docker build https://github.com/docker-library/python.git#:3.6/alpine) generates the text:
+ gpg --batch --verify python.tar.xz.asc python.tar.xz
gpg: Signature made Tue Mar 21 07:48:11 2017 UTC using RSA key ID AA65421D
gpg: Good signature from "Ned Deily (Python release signing key<EMAIL_ADDRESS>[unknown]
gpg:                 aka "Ned Deily<EMAIL_ADDRESS>[unknown]
gpg:                 aka "keybase.io/nad<EMAIL_ADDRESS>[unknown]
gpg:                 aka "Ned Deily (Python release signing key<EMAIL_ADDRESS>[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.

FYI: @ned-deily

See a change merged here that doesn't show up on the Docker Hub yet? Check the "library/python" manifest file in the docker-library/official-images repo, especially PRs with the "library/python" label on that repo.

No, the Docker Store is not the source of truth, it just happens to be correct because the tag has not been pushed yet. The tags in the description on the Docker Hub is controlled by the content of the library/ files in official-images.  We merged it with https://github.com/docker-library/official-images/pull/2774, but our build server locked up and we had to restart docker which then took a while (https://github.com/docker/docker/issues/31462) and we were not able to get back to it last night. The image is building and pushing right now, so it should be up in the next few minutes.
@cclauss that output is normal; since the python keys are the only keys imported, there is no way to verify it with a web of trust.

Thanks much for the great explanation.  It is clear to me now.  I will retry soon.

All is good now!


Need support require from local

thank for lib, but it still run uri image link, dont run with require source.
i hope lib support require: source={require('../Images/no-avatar.png')}

@hungdev Images like require('../Images/no-avatar.png') are bundled within the javascript. What would be your use case to use such images via react-native-img-cache?

@wcandillon  i want to use react-native-img-cache like this:
<CachedImage
resizeMode='cover'
indicatorProps={{ color: '#fff' }}
source={require('../Images/no-avatar.png')}
style={styles.imageSelected}
/>

@hungdev I'm not sure why you would want to cache a local image. Should you only need to cache remote images?

@wcandillon I have a similar use case.
I have an Image component, that it's source could be from remote server, or a default image from assets, but I want the view to be the same.

@hungdev @dotansimha This is fixed in 1.4.0. Please let me know if you have more issues.

@wcandillon , thank you so much.

Thanks @wcandillon !


action.List client is unable to return a list of all releases

The action.List client is unable to return a list of all releases.
Because it applies this filter, it is only able to return the following:
(a) A list of the recent releases
(b) A list of all  releases marked Superseded
I believe this is due to the change introduced in https://github.com/helm/helm/pull/8282.
If you use the helm SDK, then I think this behavior is a bug. However, if you use the helm CLI list command, then this behavior may conform to the requirements of the CLI.
I have written a unit test (#9029) that asserts that action.List returns a list of all releases. If there's consensus on a fix, it can be added to that PR.

Responding to @bacongobbler  from #9029:

Thank you for demonstrating the issue. However, it is difficult to determine whether the proposed change to the StateMask would introduce a breaking change to the SDK's intended output or to the output of helm list. Right now this seems more of a theoretical issue, and I'd like to see a more practical example on what this intends to fix.

I can confirm that this is not a theoretical issue. I consume the Helm SDK. I expect the following code, which sets StateMask = action.ListAll before it calls listClient.Run(), to return all releases matching the name. It does not, because of this bug.
func listAllReleasesForName(cfg *action.Configuration, name string) ([]*helm3release.Release, error) {
	listClient := action.NewList(cfg)
	listClient.Limit = 0
	listClient.Filter = name
	listClient.StateMask = action.ListAll

	return listClient.Run()
}

I would also suggest writing a unit test under cmd/helm/list_test.go to verify this does not unintentionally break backwards compatibility for the CLI.

I can do that. I'll open a separate PR. Once that merges, I can rebase, fix the bug in the  action package, and if the CLI unit test fails, I'll make an additional fix to the CLI package.

I thought that action.List could be (and should be) used to return a list of all release versions. This is incorrect; the right API to use is action.History. I filed this issue by mistake, so I'm closing it. I've added some comments (#9139) to clarify the difference in the two APIs.


Suggestion - Submit to awesome list

TL:DR copier is awesome!
I see it offering the most functionality that cookiecutter possess without the bloat.  Hence we should consider submitting it to an awesome list to make it known to more users.
It could be one of those:
https://github.com/sindresorhus/awesome
Most likely the python list:
https://github.com/vinta/awesome-python

Good idea!
Tell your friends, family, neighbors, and strangers! 😉
https://github.com/vinta/awesome-python/pull/1350

Awesome. Great to see you back!
I like to merge two more PRs before we can release version 3:

#61
And one I am preparing for #58

@jpscaletti
We have reached 20 votes. Still, copier the underlying PR did not get merged.
Could you take care of that (before someone decides to unlike again and we fall below 20 again), as you are the author of the thread on the vinta repo?
https://github.com/vinta/awesome-python/pull/1350


Bump the MLIR commit

Update the MLIR commit in MIGraphX to e5af8f0558d0fed8c93aaf50489f19291ac307db. This commit includes a fix to blocksize check that caused the performance issue. Need to backport to release 6.1.

This is stale now. CLosing


chore: use new common pipelines for CI and release

Description
Changed CI and Release pipelines to use the new common configurations from common-pipeline-assets.
Tick the relevant boxes:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Examples / tests (addition or updates of examples or tests)
[ ] Documentation update
[x] CI related update (pipeline, etc)

Checklist:

[ ] If relevant, a test for the change has been added / updated as part of this PR.
[ ] If relevant, documentation for the change has been added / updated as part of this PR.

Merge:
Merge using "Squash and merge" and ensure to use a relevant conventional commit message based on the PR contents (this ultimately determines if a new version of the modules needs to be released, and if so, which semver number should be used).

:tada: This PR is included in version 1.0.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Central User API (for backup / recovery)

basic user model
jwt for expire-able user sessions
signup and sign-in routes

Ready for a review / merge. I've got this deployed via Docker Swarm to https://api.textile.io, the setup for that uses a docker-compose.yml file, which is currently ignored since it declares production-level environment variables... still working out how to handle all that (will revisit).

(btw, our Docker Swarm is in our EC2 VPC)


chore: fix setup and start scripts

Reading the README, I'm a bit confused: should I be using ./scripts/docker_start.sh rather than docker-compose up? Both are mentioned, and it's not immediately clear to me why...

I guess this is nothing to do with this PR, but when I run it I get
couchdb-sync-rq_1  | psycopg2.OperationalError: FATAL:  database "couchdb-sync" does not exist

Also

Ah, true, good point

Hopefully this time works :crossed_fingers:

And now nginx never starts up 💢

:tada:


Terminal message looks wrong

Solutions:

Make it look more friendly
Config option to customize message contents
Config option to remove that message

This is obviously not a bug but it just doesn't look like a finished message.

My way of thinking about this, is that since I decided to make purchasing slots NOT enabled by default, many people wouldn't know it's an option they can enable. This is kinda like advertising that it is indeed an option for them in the config.
I agree, I don't exactly love the text there, but the screenshot you sent is from opening the terminal for the first time. Every time players open the terminal after that, they will not see that message anymore. (unless a mod does something to change it, idk)
But with all that said, if you have a solution that can satisfy the points I made, or if you think rewording the text would be better, share your thoughts here! Just because I made the mod does not mean that every decision/choices in this mod are perfect lol. I'm open to all suggestions! Maybe I could at least get rid of the strikethrough, and make the last part of the text more informative? I'm not sure.

I agree with xlifi, it looks terrible. I understand that you want to ensure people are aware of the new option so I think it's fine if the message appears in default, but it would be nice if you added a option to remove the text in the config file. I and many people don't want things that can make the game feel "modded" and want a more polished-looking game. The Too Many Emotes mod had a similar issue and ended up removing it.
Of course that's on you, im not the mod creator, just pointing out my view on this. Thx for the great mod <3!

Yeah this sadly feels too spammy, and is not aesthetically pleasing.
I think by now people are used to looking at configs, and should be aware of the available options when installing a mod. Advertising that an option exists is unnecessary.
If the option is disabled, there should be no text added to the terminal.
This should be the case with all options within all mods.
Alternatively, if you absolutely insist on keeping it there, please add a "Disable Terminal Messages" option, which you can also disable by default, so the default config still shows your message.

Sorry, I missed this thread for like 9 days!
My solution would be to change the text (see "Images") and add a config option to disable the message.

Images
(appears if you are the host)
Buying Reserved Slots is currently disabled. You can enable it or hide the message in config.

(appears if you are not the host)
Buying Reserved Slots is disabled by host. You can hide the message in config.

(appears if buying slots is enabled)
Buying Reserved Slots is enabled. Type "Reserved" to purchase slots.


FT: replace analogServer (deprecated) with multipleanalogsensorsserver

This has been done both for uniforming with the simulated robots: https://github.com/robotology/icub-models-generator/pull/231 and for the deprecation of analogServer
It fixes #470
To be tested on a robot

fyi @GiulioRomualdi @S-Dafarra @gabrielenava this may affect any code that is readying directly from FT sensor ports as a vector.

After a T2T alignment with @traversaro and @pattacini we decided to proceed merging this PR(it ha been tested on iCubGenova11) and then address

One thing that we may took the occasion to do know that we do a breaking change is that we could group in a single wrapper all the FT sensors of the leg, for consistency with what we do for other wrappers, such as controlboard.

in a second stint; https://github.com/robotology/robots-configuration/issues/485


[9.x] Fixing some tokens that came with url characters

Some software as Insomnia, Postman, etc... used to send the cookie csrf token like this:
eyJpdiI6Ikp6UDJoTnpJTTlkNGh5bnZnc0tvOUE9PSIsInZhbHVlIjoiUjkvbzUzeTNUQk5nWUJrQjNrSEZGQ1dmM3lOVUdPdkhaV1UxK3I1UC96Y2ZLbHB4VFZRS1RZQjd1SXoxMld0Ymo4KzlSVFRWOVlLU3BjL01BTmppWkxDc3JIeWhlRVViUERsZFZVcW5xY0laWnY3dnRBU05MZ1A0Rm5YOURCMEUiLCJtYWMiOiJkMDQ1NjdlM2E4NWU3MjBhZTk0YjNhYWQxNjc2OGVkNmJlMTc4ZjllNjZmYmE3ZWIxYjk5M2E3Y2ExYzE1NzNiIiwidGFnIjoiIn0%3D
The problem is that the function can't decrypt the token because of URL characters as %3D, so I just added the urldecode function to prevent this kind of issue.

Not sure I want to change CSRF behavior on a patch release.


Cannot deselect specific stored procedure from list of changes. Error: "Specified method is not supported"

Issue Type: Bug

Make a schema comparison
Try to remove a specific stored procedure from the list of actions (Change) by removing the checkmark from the "Include" column.

Expected result: the checkmark is removed
Actual result: The checkmark is removed at first. But after a few seconds, I get an error box with the message "Specified method is not supported" (Source: SQL Server Schema Compare (Extension)). The list of changes updates, and the stored procedure gets ticked again, so there is no way for me to deselect it.

This seems to happen only for one out of two databases I try to sync the same stored procedure and same changes with. Both are hosted at at an external web service and should run on the same version of SQL Server, even though they are on different servers.
Is there a log file for the Schema Compare extension operations where I can get more information about the error to help me/you to troubleshoot?
The stored procedure is relatively long, 660 rows, not sure if this can cause problems?
This problem does not occur when syncing against the same database using SSDT in Visual Studio.
Extension version: 1.9.1
Azure Data Studio version: azuredatastudio 1.27.0 (765c7064d46253d88393e0e1ff78874b6fe8fa64, 2021-03-16T21:18:54.187Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 4, 4

Memory (System)
16.00GB (0.25GB free)

Process Argv

Screen Reader
no

VM
25%

@maccer83 can you share source and target dacpacs that repro this issue(doesn't have to be the exact dacpacs you were seeing this problem with, just sample dacpacs that have the same issue) so that we can repro and debug this?

I'm also having this issue but mine is when trying to deselect a table.  The console log window is empty and there are no relevant logs in the log directory.

I'm also having this issue but mine is when trying to deselect a table. The console log window is empty and there are no relevant logs in the log directory.

I'm comparing MSSQL database to MSSQL database directly.  No dacpac.

I tried comparing AdventureWorks to another database and was able to exclude AdventureWorks tables with the latest insiders build and schema compare 1.10.0.
Can you use the dacpac extension to extract dacpacs for a source and target that repro this and email them to me at<EMAIL_ADDRESS>

I tried comparing AdventureWorks to another database and was able to exclude AdventureWorks tables with the latest insiders build and schema compare 1.10.0.
Can you use the dacpac extension to extract dacpacs for a source and target that repro this and email them to me at<EMAIL_ADDRESS>
I'm not sure I can/should do that.  I can't open the exported dacpac file to verify that sensitive information isn't in it.  This is a client's database.

@jkylehumphrey the dacpac created by the dacpac wizard contains schema only, no data. You can verify the contents by changing the file extension of the dacpac to .zip and unzipping it. Another option is to share only the model.xml from the unzipped dacpacs since that's the schema, which is all that's needed for reproing.
If you're still uncomfortable with that, please try to create a sample source and target database that repros this issue and share dacpacs from those.

@jkylehumphrey if you deploy the dacpacs, does the issue repro for those databases?

@jkylehumphrey just following up here with Kim's question- did you try deploying the dacpacs? And did that repro the issue for those databases?

Closing this issue for now, since we didn't hear back on it further. Please feel free to re-open it with more information.


Scheduled Triggers become unreliable

Describe the bug
After a few days, the scheduled triggers cease to work. Also, timed triggers have been observed to stop working once the scheduled triggers fail.
To Reproduce
Run with a scheduled trigger (or a few of them) and wait for a few days.
Expected behavior
Triggers operate as expected indefinitely.
Desktop (please complete the following information):
v1.3.3
Workaround
Restart the child-bridge hosting the plugin or all of home bridge.

Issue was the result of the check performed to compensate for changes in time (resetting the system clock, DST, etc) swamping the Homebridge system with event notifications.


Live edit layout icon images oversized

In the development version the live edit layout my icon images in the right column appear over sized. I've refreshed the cache in admin > settings and reloaded the database.
Also the left column width seems over wide, class main-bar-column has increased from 100 to 230, I assume that's work-in-progress.

I solved the over sized icon image, I had left some template files in \userfiles\modules\layouts\templates which nolonger exist in the latest dev version. Once removed all looked ok.
But not sure what's happening with the left column width, seems overly wide.


Handle Overfunding / Underfunding

I propose the following to handle overfunding / underfunding of both Bitcoin and Monero:
In case the Bitcoin funding transaction's amount does not match the requested amount, the swap should abort. Alice's swap will run indefinitely for now until the user manually cancels it.
In case the Monero lock transaction's amount does not match the requested amount, the protocol should progress like a usual refund swap, with Alice  waiting for Bob to cancel and refund, and then sweeping the Monero. If Alice overfunds, she should not publish the buy transaction.

I'm not convinced about failing upon counterpartiy's overfunding. One should be thankful for the gift :D Msg::ThankYou

I'm not convinced about failing upon counterpartiy's overfunding. One should be thankful for the gift :D Msg::ThankYou

Yeah, when Bob replies with the BuySignature for Alice, she should ignore it if she overfunded. Eventually the refund path must be triggered.

Closing with #530 and #531.


Add and use sampling loggers

Add a sampling logger to enable high-volume error points that provide sufficient fidelity of the underlying condition but doesn't drown the system in IO or useless repeated data.  Zerolog supports this but a global singleton sampling logger needs to be present someplace.
https://github.com/rs/zerolog#log-sampling

Please make sure we can disable any sampling behaviour in the configuration file.


Improve doc of element-wise sigmoid logistic function

This PR improves the documentation of the element-wise sigmoid logistic function by adding a usage example.
Adding plots using sphinx extensions will be left for future PRs :).
EDIT: previously [WIP] Add example usage to docstrings of functions and links:
PRs welcome!
Part of improving documentaion effort. See also https://github.com/pfnet/chainer/issues/1867
TODO (finish this list):
Functions:

[ ] linear
[x] sigmoid
[ ] ...

Links:

[ ] Bilinear
[ ] Maxout
[ ] ...

Very good stating point. Some points I got as feedbacks:

You can check the output by just putting the estimated output after it instead of using assert as follows:

>>> y.shape
(3, 4)

Writing this line (3, 4) enables the doctest to check the output of y.shape is the same as that line.

Let's think about adding plots to show the difference of functions effectively like:

numpy.exp
Transfer Function Layers (from torch.nn)

We can add emmbedded plots using sphinx extensions: http://matplotlib.org/sampledoc/extensions.html#inserting-matplotlib-plots

This PR is ready for review.

LGTM

Let's split PRs for each function to improve docstrings for them.


Fixed strict type in PHP file

I made these changes to my local vendor manually and this does not fix the issue.
The change needs to happen in here too as mentioned in the issue #30.
https://github.com/mmoreram/php-formatter/blob/v1.3.1/src/PHPFormatter/Console/Application.php#L34-L37
if (function_exists('ini_set') && extension_loaded('xdebug')) {
    ini_set('xdebug.show_exception_trace', false);
    ini_set('xdebug.scream', false);
}

Hum, I don't have xdebug installed. True :(

@matt-usurp updated :)


Fix .babelrc

See developer guidelines

Yes, this should be fixed, but just to give a context why this is at the moment.
The library is used in react-native project. In react-native, there are many issues reported in case you have .babelrc file present in your project dependencies. The main discussion is here:
https://github.com/facebook/react-native/issues/4062
This has led that most of the project in the eco-system are not publishing .babelrc (either by npm ignoring it, or by opting in what will be included on npm publish). I can verify this. On the react-native project I'm currently on, that are a number of dependencies. But, there is not a single .babelrc, except:

one on project root level (that has been included in recent version of react-native templates, because of issues).
one in this module (at the moment I'm using this project as a git-submodule, so npm ignoring it does not help).

There are proposals where this is headed here:
https://github.com/facebook/react-native/issues/10966

switched to react-native preset
with #33 .babelrc is now in the top-level package and will not be included with the other packages


New Tool: Automate Redirect Updates

We want a make recipe like:
# make update_redirects from_path to_path
$ make update_redirects /dbt-cli/installation-guides/windows /dbt-cli/installation

Which would:
    search the _redirects file for any entries that have the from_path as the target, and replaces it with the to_path
    add a new entry to the _redirects file for the new mapping

The front end eng team is working on optimizing our redirects file. @JKarlavige @wendyvasq Curious if a tool like this would be useful or should I close this issue out?

We are planning on removing the Makefile altogether for this repo, as it looks like we no longer need the functionality within it. I'm not 100% sure if that affects this, but i'm assuming a make recipe references that.
However, I feel like using a find/replace would be efficient enough for updating old redirects when requested, so I don't feel like this would be needed.

Thanks Jason! Closing this issue!