Better validation errors in ingests endpoint

For #3076

So, the error messages here are slightly different from the error messages suggested in #3076 :

If a required property is missing the error looks like
Invalid value at .sourceLocation: required property not supplied.
if a nested property is missing, the full path to the missing property is provided i.e.
Invalid value at .sourceLocation.bucket: required property not supplied.

If we only accept a controlled set of values as we do for ingestType.id and provider.id and the supplied value is not one of the allowed ones, the error message looks like:
Invalid value at .sourceLocation.provider.id: invalid value supplied, valid values are: aws-s3-standard, aws-s3-ia.

If a property is supplied with a different format than the one supported, the error message looks like:
Invalid value at .sourceLocation.bucket: should be a String.

Also, if there are multiple errors in the JSON, they are all accumulated in the response message and line separated i.e.
Invalid value at .sourceLocation: required property not supplied.
Invalid value at .ingestType: required property not supplied.

The returned error is a JSON repsonse in the format:
{
 "httpStatus": 400,
 "description": "...",
 "label": "Bad Request"
 "type": "Error"
}

which is consistent with what we do in the API


support to Swift Package Manager

Is it possibile to add the support to Swift Package Manager?

Vote for it, please add Package.swift

+1

+1

There are some update about this topic?

I need this too


Redux documentation is down - SSL certificate issue

Do you want to request a feature or report a bug?
Report a bug.
What is the current behavior?
Navigating to https://redux.js.org/ returns a privacy error.
Specifically, in Chrome at least, the error is NET::ERR_CERT_COMMON_NAME_INVALID, and in Firefox the error is SSL_ERROR_BAD_CERT_DOMAIN.  The certificate served by https://redux.js.org/ is valid for *.netlify.com and netlify.com, and not for anything under the js.org domain.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar.

Navigate to https://redux.js.org/
There is an error.

What is the expected behavior?
I should be able to browse to the Redux documentation and read it.
Which versions of Redux, and which browser and OS are affected by this issue? Did this work in previous versions of Redux?
I was using the documentation yesterday, about 16 hours previously to this post.  I noticed it this morning about fifteen, twenty minutes ago, when I first navigated to the Redux documentation today.
I experience this issue using Chrome (Version 70.0.3538.110 (Official Build) (64-bit)) and Firefox (63.0.3 (64-bit)), although I imagine the same issue will show up in every browser version released in the last five or ten years... ;)

Yep, we just switched over to the new docs site hosted on Netlify, and it took a bit for Netlify to deploy a new SSL certificate for us.  Should be fixed now.  If it persists, let us know!


[RN] (BUG) #2374 Dashboard - Claim button animation isn't working well

Description
Its a copy of #2381 PR for the react-native branch.
About #2374

pls apply those fixes #2381 (review)

I see you already applied them

@yaroslav-fedyshyn-nordwhale with these changes the animation no longer works in react-native. it doesn't crash but it doesn't animate the button at all. from the quick investigation I did, it's all happening because of the await on line 282 Dashboard.js, it's causing setQueueStatus to never execute hence never resolving the promise

I found what was wrong - react-native uses another claimButton component (which is AnimatedClaimButton) rather than master so the onStatusChange callback was not assigned to the ClaimButton component. See my last commit with the fix.

@mauriguz @yaroslav-fedyshyn-nordwhale i've added onLayout fix for IOS 13.4
please re-check it. thanks!

@mauriguz @MathiasMoralesDixtra

If height is also returns, this fixes the issue
could you please merge with latest react-native

@mauriguz @MathiasMoralesDixtra

If height is also returns, this fixes the issue ?
could you please merge with latest react-native

@serdiukov-o-nordwhale returning height isn't enough to fix the problem, yesterday I did a quick test and to make it work I had to add a delay to the measure func to make sure the layout calcs are correct.
I'll pull react-native here no problem


python312Packages.python-kasa: 0.7.2 -> 0.7.3

Changelog: https://github.com/python-kasa/python-kasa/blob/0.7.3/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 341316 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.tplink
python311Packages.python-kasa
python311Packages.python-kasa.dist
python312Packages.python-kasa
python312Packages.python-kasa.dist


YJDH-699 | test(kesaseteli): add longer timeouts to tests that seem to need them

Description :sparkles:
TL;DR:

Increasing timeouts in favor of retries (Retries were added in PR #2940 by @sirtawast and now removed in this PR)

test(kesaseteli): add longer timeouts to tests that seem to need them
remove jest.retryTimes(5) as they should not be needed anymore
with the increased timeouts, if they still fail then it's good to get
the information about them failing rather than thinking that they're
not failing
refs YJDH-690, YJDH-699
Issues :bug:
YJDH-690 "Some kesäseteli tests fail randomly on employer and youth"
YJDH-699 "Increase timeouts for the kesäseteli tests that fail randomly on employer and youth"
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

API branch is deployed to platta: https://tet-pr2981.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

ADMIN branch is deployed to platta: https://tet-admin-ui-pr2981.dev.hel.ninja :rocket::rocket::rocket:

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr2981.dev.hel.ninja :rocket::rocket::rocket:

API branch is deployed to platta: https://helsinkilisa-pr2981.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr2981.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://tet-admin-ui-pr2981.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://helsinkilisa-ui-handler-pr2981.dev.hel.ninja :laughing::tada::tada::tada:

YOUTH branch is deployed to platta: https://tet-youth-ui-pr2981.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://tet-youth-ui-pr2981.dev.hel.ninja :laughing::tada::tada::tada:

API branch is deployed to platta: https://kesaseteli-pr2981.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr2981.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-employer-pr2981.dev.hel.ninja :laughing::tada::tada::tada:

HANDLER branch is deployed to platta: https://kesaseteli-handler-pr2981.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-handler-pr2981.dev.hel.ninja :laughing::tada::tada::tada:

YOUTH branch is deployed to platta: https://kesaseteli-youth-pr2981.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-youth-pr2981.dev.hel.ninja :laughing::tada::tada::tada:

For code reviewing I suggest using "Hide whitespace":

As it'll make the diff much smaller.


Use Clap

This pull request replaces docopt with Clap to provide a more convenient and user friendly way to specify command line arguments.
Note: This also slightly changes how the user needs to pass arguments where before it worked like this -w yes now the user can simply pass --write.

@badboy I restored the old flag behavior because while I was working on the failing tests I realized that my changes would break the existing and expected behavior.

Opened a ticket for structopt: https://github.com/semantic-rs/semantic-rs/issues/127

:shipit:


Use format=None to return raw Python data structure

Fixes https://github.com/hugovk/norwegianblue/issues/228.
For programmatic use, return the decoded JSON before turning it into a formatted string.
So there's no need to do something like parse a JSON string back into a Python data structure.

Released! Thanks for the suggestion and review! https://pypi.org/project/norwegianblue/0.20.0/


Intercept the ActionLink render pipeline

I have a requirement to validate the rendering of the html control based on user permissions.
I have an extension method:

public static BootstrapActionLinkBase<'T'> SecurityAware<'T'>(this BootstrapActionLinkBase<'T'> linkBase) where TModel : BootstrapActionLinkBase<'T'>

used @Html.Bootstrap().ActionLink("Settings", "Index", "Setting").SecurityAware().PrependIcon("fa fa-cogs")
To intercept the pipeline and trying to evaluate the action method on the controller against the current user.
I would like to have the ability to access the model to:

get the action method name and controller
set the ShouldNotRender property already exists on the BootstrapActionLinkModel

any help would be appreciated.

the model that contains all the stuff that you need is a protected property. It's not made public because if it was that, it'd be showing in the intellisense when you type @Html.Bootstrap().ActionLink("Settings", "Index", "Setting")., which is not desirable.
What you can do instead of writing an extension is writing a separate helper:
public static class BmvcExtensions
{
	public static ActionLinkAuthorized ActionLinkAuthorized(this HtmlHelper htmlHelper, string linkText, string actionName)
	{
		string controllerName =  htmlHelper.ViewContext.RouteData.GetRequiredString("controller");
		return new ActionLinkAuthorized(htmlHelper, linkText, actionName, controllerName);
	}
	public static ActionLinkAuthorized ActionLinkAuthorized(this HtmlHelper htmlHelper, string linkText, string actionName, string controllerName)
	{
		return new ActionLinkAuthorized(htmlHelper, linkText, actionName, controllerName);
	}
}

public class ActionLinkAuthorized : BootstrapActionLink
{
	public ActionLinkAuthorized(HtmlHelper htmlHelper, string linkText, string actionName, string controllerName)
		: base(htmlHelper, linkText, actionName, controllerName)
	{
		//TODO: condition to check if action is authorized:
		if (true/*your logic for authorizing*/)
		{
			base._model.ShouldNotRender = true;
		}
	}
}

You'd use it like so:
@Html.ActionLinkAuthorized("text", "action", "controller")

That worked perfectly..
Thank you


Xpense: Adding DFD

Graphical representation of the flow
of data through our system, modeling its process aspects

@shlior7  @Yoavsc129 @orIsrael  can you approve as well?

description = story ?

Waiting on the disduccsion in Slack, then I'll fix it in the file

It need to be repush to rerun the tests

I don't entirely understand what each shape represents, what are the circles stand for? a button? a web page? an endpoint?
What do you mean by post tips? a user can add tips on his own?
which statistics are you looking for? what do filter parameters mean?
The DFD is supposed to be very clear and does not require any explanations

I don't entirely understand what each shape represents, what are the circles stand for? a button? a web page? an endpoint? What do you mean by post tips? a user can add tips on his own? which statistics are you looking for? what do filter parameters mean? The DFD is supposed to be very clear and does not require any explanations

The circles represent processes, The squares are multiple entities that are not inside the program (like here the users) and the third shape is a Data Base we read it here: https://www.lucidchart.com/pages/data-flow-diagram .
Plus on the gliffy site when you edit the diagram, the shapes have names (Data Base)
for instance, creation of a new house requires for the user to give his expenses, story, city and country (etc.)
that processes accesses the DB, implements a new house, and returns the user
The filter parameters are the parameters the user has to give the system in order for the filtering to show something
you filter by a spesific parameter (category, city, country, number of children etc..)

rebased and repushed

rebased and repushed after #56 merge

About the tips page - we need to add the option to view tips
About the private page - 1. we need to add the option to add the house information
2. we need to add the option to edit the house information
I don't have an option to login to gliffy (my trial time has expired) :(

Was there any change done in the diagram? I still see the same one I commented on

Was there any change done in the diagram? I still see the same one I commented on

Yes, We have updated the new DFD now

I think we should also add as @svatares suggested the functionality of changing data of the house like private <-> public, name change, add expenses  etc
also the filtered_houses should also be pointed out that these are the public_filtered_houses
other than that it looks amazing and very detailed Good Job @LiorKGOW and everyone who worked on this 👏

Rebased after #63 was merged,
and added suggested changes 👍

This diagram looks much better! Great work! I do have a few questions, once those will be answered we will be able to continue:

From the flow of the I see that anyone (even without a user) can create a tips, is that the intended behavior? Since you don't go through an authentication/login stage before reaching the "add a tip" view.
Anyone can view the global houses page and filter as they want. Is that right? (again no need for login to do it according to the diagram)
Is it possible to edit an expense? It is not mentioned in the diagram, and the flow of editing is different than the flow of adding.
Is it possible to edit tips? If so, same as the previous question, but also, since adding a tip (according to the current diagram) is done without authentication, how to you plan to get the information for getting the tip that you want to edit? (you want only the user that created the tip to be able to edit it)
I would recommend also adding the link to the Gliffyv diagram, since it is really hard to see something in here.

I'll add a link to the gliffy 👍
For The rest of the questions I'll move the conversation to Slack because I think everyone should express their opinions on the subject

rebased and repushed after #58 was merged to main

This diagram looks much better! Great work! I do have a few questions, once those will be answered we will be able to continue:

From the flow of the I see that anyone (even without a user) can create a tips, is that the intended behavior? Since you don't go through an authentication/login stage before reaching the "add a tip" view.
Anyone can view the global houses page and filter as they want. Is that right? (again no need for login to do it according to the diagram)
Is it possible to edit an expense? It is not mentioned in the diagram, and the flow of editing is different than the flow of adding.
Is it possible to edit tips? If so, same as the previous question, but also, since adding a tip (according to the current diagram) is done without authentication, how to you plan to get the information for getting the tip that you want to edit? (you want only the user that created the tip to be able to edit it)
I would recommend also adding the link to the Gliffyv diagram, since it is really hard to see something in here.

resolved 👍

rebased and repushed after #67 was merged

Updated the DFD with the final version after todays meeting.
Ready to merge 👍

Good job, looks much better


Unhandled Promise errors aren't inspectable.

I'm building a code hosting framework on Zone.js and ran into trouble with unhandled rejections. I force middleware like an error handler and try to catch any unhandled rejections or promises. I wanted to do intelligent things with that error like report the message and provide your beautifully stitched together stack trace to a debugging tool. Unfortunately the great work the longStackTraceZoneSpec has done is lost for me.
The Zone.js code for handling a rejected promise rethrows that promise twice. This causes the entire cleanly formatted object of the original Error to get smashed into the message of the final error. The unit tests that worked flawlessly with an unhandled Error required a lot of string parsing for unhandled Promises and I'm really worried about the stability of any hand-crafted parsing.

@inlined , do you mean you want to get the original uncaught error?
I think you can get the original error information from error.rejection which was re-throwed by zone

@inlined , I have made a PR #627 to add unhandledRejection event trigger, is that meet your requirement?

Sorry I didn't catch the comment last month. This looks great. Thanks! I'll start testing with this asap.


CLI: RUN and BUILD commands are working from module's root or upper but not lower

Module's root (work)
cd <module_root>
neva run <path/to/main/pkg>

Upper than module's root (also work)
cd <module_root>
neva run <path/to/main/pkg>

Lower than module's root (doesn't work)
Let's say you have this structure
somedir/
..neva_module/
....foo/
......bar/main.neva

It's intuitive to assume that neva run bar from /somedir/neva_module/foo will work but it actually won't.
The problem is that wd will be /somedir/neva_module/foo and mainPkgPath will be bar. And when builder CD into WD it can't see bar there.

Note that we have e2e test for that inside e2e folder (run cli not from module root)


UNABLE to npm install bleno!!!

i've been trying to Install Bleno via Node.js Package Manager (npm), it fails to do so, and gives me the erros :
npm WARN optional Skipping failed optional dependency /bleno/xpc-connection:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

@MussabNuri this is fine, all warnings. xpc-connection is an optional dependency needed for OS X only.


operator: remove s3 operator flags

LGTM
Note that we also need to update upgrade docs and CHANGELOG
@fanminshi Do you want to do it here or in a different PR?

@hongchaodeng I'll add it to this pr.

@hongchaodeng updated change log. PTAL

lgtm


Update azure iotedge and rust to latest versions

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/tools/cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

Update azure-iotedge to latest version (1.1.0). Also update rust to latest version (1.50.0) since this is required to compile the latest azure-iotedge.
Change Log

Update azure-iotedge
Update rust

Does this affect the toolchain?

YES
NO
Associated issues

#xxxx

Links to CVEs

https://nvd.nist.gov/...

Test Methodology

Local package build

Also update rust to latest version (1.50.0) since this is required to compile the latest azure-iotedge.

The BuildRequires line still reads rust >= 1.39.0- that should probably be updated to match the new version.

Also update rust to latest version (1.50.0) since this is required to compile the latest azure-iotedge.

The BuildRequires line still reads rust >= 1.39.0- that should probably be updated to match the new version.

Good point, will update. The error I was seeing with 1.39.0 was: "error[E0658]: cfg(doctest) is experimental and subject to change"


Sync eng/common directory with azure-sdk-tools for PR 6230

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/6230  See eng/common workflow

/check-enforcer override


fixed #21 - reset bg and fg with 39 and 49 code

Fixing #21 - I hope @jimbauwens don't mind me making this pull request. Added as a contributor as well. Ping @drudru
It's the first time I write mocha tests but they pass with the patch so it should be fine. :)

I don't mind at all :-) Thanks!

Solid :+1:  thanks!


pgdtools v0.1.0

This is the first implementation of an actually feasible version. It is far from perfect, but ready for users to hack against it and try to test it out.
The current version contains (some major features):

Database download and management section
Filtering, data retrieval
Information on the database, techniques, and references

The maintainer tools stayed mostly the same.
 This will come.
Note: The "very early dev version..." warning upon import is gone. Basically all user functionality with that version is broken and does not exist anymore. You have been warned ;)

Hello @trappitsch! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/pgdtools/classify.py:

Line 94:80: E501 line too long (82 > 79 characters)
Line 135:80: E501 line too long (85 > 79 characters)
Line 190:80: E501 line too long (83 > 79 characters)
Line 198:80: E501 line too long (83 > 79 characters)
Line 335:80: E501 line too long (88 > 79 characters)
Line 361:80: E501 line too long (81 > 79 characters)
Line 369:80: E501 line too long (81 > 79 characters)
Line 382:80: E501 line too long (81 > 79 characters)

In the file src/pgdtools/pgdtools.py:

Line 3:80: E501 line too long (84 > 79 characters)
Line 11:80: E501 line too long (82 > 79 characters)
Line 36:80: E501 line too long (81 > 79 characters)
Line 111:80: E501 line too long (83 > 79 characters)
Line 113:80: E501 line too long (82 > 79 characters)
Line 114:80: E501 line too long (85 > 79 characters)
Line 166:80: E501 line too long (84 > 79 characters)

In the file src/pgdtools/sub_tools/data.py:

Line 13:80: E501 line too long (86 > 79 characters)
Line 14:80: E501 line too long (87 > 79 characters)
Line 48:80: E501 line too long (82 > 79 characters)
Line 62:80: E501 line too long (84 > 79 characters)
Line 63:80: E501 line too long (82 > 79 characters)
Line 77:80: E501 line too long (83 > 79 characters)
Line 79:80: E501 line too long (84 > 79 characters)
Line 80:80: E501 line too long (82 > 79 characters)
Line 110:80: E501 line too long (80 > 79 characters)
Line 119:80: E501 line too long (81 > 79 characters)
Line 151:80: E501 line too long (80 > 79 characters)
Line 161:80: E501 line too long (82 > 79 characters)
Line 162:80: E501 line too long (84 > 79 characters)
Line 165:80: E501 line too long (84 > 79 characters)
Line 167:80: E501 line too long (84 > 79 characters)
Line 169:80: E501 line too long (81 > 79 characters)
Line 171:80: E501 line too long (87 > 79 characters)
Line 174:80: E501 line too long (81 > 79 characters)
Line 176:80: E501 line too long (83 > 79 characters)
Line 179:80: E501 line too long (83 > 79 characters)
Line 181:80: E501 line too long (86 > 79 characters)
Line 182:80: E501 line too long (85 > 79 characters)
Line 183:80: E501 line too long (85 > 79 characters)
Line 190:80: E501 line too long (83 > 79 characters)

In the file src/pgdtools/sub_tools/filters.py:

Line 30:80: E501 line too long (88 > 79 characters)
Line 44:80: E501 line too long (83 > 79 characters)
Line 45:80: E501 line too long (80 > 79 characters)
Line 60:80: E501 line too long (80 > 79 characters)
Line 73:80: E501 line too long (81 > 79 characters)
Line 81:80: E501 line too long (84 > 79 characters)
Line 92:80: E501 line too long (81 > 79 characters)
Line 96:80: E501 line too long (82 > 79 characters)
Line 97:80: E501 line too long (81 > 79 characters)
Line 100:80: E501 line too long (84 > 79 characters)
Line 103:80: E501 line too long (82 > 79 characters)
Line 108:80: E501 line too long (86 > 79 characters)
Line 119:80: E501 line too long (85 > 79 characters)
Line 123:80: E501 line too long (84 > 79 characters)
Line 129:80: E501 line too long (81 > 79 characters)
Line 141:80: E501 line too long (84 > 79 characters)
Line 147:80: E501 line too long (81 > 79 characters)
Line 149:80: E501 line too long (80 > 79 characters)
Line 151:80: E501 line too long (80 > 79 characters)
Line 152:80: E501 line too long (81 > 79 characters)
Line 155:80: E501 line too long (84 > 79 characters)
Line 158:80: E501 line too long (82 > 79 characters)
Line 163:80: E501 line too long (86 > 79 characters)
Line 209:80: E501 line too long (80 > 79 characters)
Line 236:80: E501 line too long (87 > 79 characters)

In the file src/pgdtools/sub_tools/format.py:

Line 13:80: E501 line too long (85 > 79 characters)
Line 34:80: E501 line too long (82 > 79 characters)
Line 52:80: E501 line too long (82 > 79 characters)
Line 65:80: E501 line too long (85 > 79 characters)

In the file src/pgdtools/sub_tools/headers.py:

Line 12:80: E501 line too long (88 > 79 characters)
Line 45:80: E501 line too long (88 > 79 characters)
Line 89:80: E501 line too long (80 > 79 characters)

In the file src/pgdtools/sub_tools/info.py:

Line 46:80: E501 line too long (85 > 79 characters)
Line 56:80: E501 line too long (83 > 79 characters)
Line 77:80: E501 line too long (81 > 79 characters)
Line 94:80: E501 line too long (83 > 79 characters)
Line 95:80: E501 line too long (83 > 79 characters)

In the file src/pgdtools/sub_tools/references.py:

Line 53:80: E501 line too long (85 > 79 characters)
Line 54:80: E501 line too long (80 > 79 characters)
Line 89:80: E501 line too long (84 > 79 characters)
Line 99:80: E501 line too long (84 > 79 characters)
Line 105:80: E501 line too long (84 > 79 characters)
Line 108:80: E501 line too long (84 > 79 characters)
Line 112:80: E501 line too long (84 > 79 characters)
Line 114:80: E501 line too long (83 > 79 characters)
Line 133:80: E501 line too long (83 > 79 characters)
Line 155:80: E501 line too long (83 > 79 characters)
Line 156:80: E501 line too long (88 > 79 characters)
Line 163:80: E501 line too long (87 > 79 characters)

In the file src/pgdtools/sub_tools/techniques.py:

Line 47:80: E501 line too long (85 > 79 characters)
Line 48:80: E501 line too long (80 > 79 characters)
Line 83:80: E501 line too long (81 > 79 characters)
Line 92:80: E501 line too long (85 > 79 characters)
Line 96:80: E501 line too long (85 > 79 characters)
Line 98:80: E501 line too long (83 > 79 characters)
Line 124:80: E501 line too long (83 > 79 characters)

In the file src/pgdtools/sub_tools/utilities.py:

Line 7:80: E501 line too long (82 > 79 characters)
Line 13:80: E501 line too long (85 > 79 characters)
Line 14:80: E501 line too long (81 > 79 characters)
Line 29:80: E501 line too long (87 > 79 characters)
Line 35:80: E501 line too long (86 > 79 characters)
Line 86:80: E501 line too long (82 > 79 characters)

In the file tests/conftest.py:

Line 45:80: E501 line too long (80 > 79 characters)
Line 54:80: E501 line too long (83 > 79 characters)

In the file tests/test_pgdtools.py:

Line 14:80: E501 line too long (87 > 79 characters)

In the file tests/test_sub_tools/test_data.py:

Line 59:80: E501 line too long (82 > 79 characters)
Line 63:80: E501 line too long (81 > 79 characters)
Line 66:80: E501 line too long (87 > 79 characters)
Line 70:80: E501 line too long (82 > 79 characters)
Line 86:80: E501 line too long (82 > 79 characters)
Line 96:80: E501 line too long (84 > 79 characters)
Line 101:80: E501 line too long (80 > 79 characters)

In the file tests/test_sub_tools/test_filters.py:

Line 41:80: E501 line too long (82 > 79 characters)
Line 43:80: E501 line too long (81 > 79 characters)
Line 47:80: E501 line too long (84 > 79 characters)
Line 127:80: E501 line too long (83 > 79 characters)
Line 168:80: E501 line too long (87 > 79 characters)

In the file tests/test_sub_tools/test_format.py:

Line 19:80: E501 line too long (83 > 79 characters)

In the file tests/test_sub_tools/test_headers.py:

Line 16:80: E501 line too long (87 > 79 characters)

In the file tests/test_sub_tools/test_utilities.py:

Line 12:80: E501 line too long (87 > 79 characters)
Line 33:80: E501 line too long (80 > 79 characters)


Dracula doesn't read jQuery triggered mouse-events for some reason

Hi,
I have something like this inside my Qunit test:
    jQuery(el).mouseover();
    jQuery(el).mousedown();
    jQuery(target).mousemove();
    jQuery(target).mouseup();

also tried
    jQuery(el).trigger('mouseover');
    jQuery(el).trigger('mousedown');
    jQuery(target).trigger('mousemove');
    jQuery(target).trigger('mouseup');

... to test a drag event. This does not work, while I can manually drag the elements. I populate the drake.containers in another module, by passing the DOM elements. Don't have a lot of issues with real application.
Do you have a better way to test / trigger drag?
Thanks.

Please refer to our Slack channel for support requests. You can join our Slack channel through this link.
Thanks! :tada:


kv(ticdc): fix data loss when upstream txn conflicts during scan (#5477)

This is an automated cherry-pick of #5477
What problem does this PR solve?
Issue Number: close #5468
What is changed and how it works?
Do not match prewrite and commit util it receives init event.
See more in #5468
Check List
Tests

Unit test

Will it cause performance regression or break compatibility?
It caches more events in memory during incremental scan, it cause OOM when upstream workload is write-heavy.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note
Fix data loss when upstream transaction conflicts during cdc reconnection

/run-unit-test

/merge

/run-all-tests tidb=release-5.4 tikv=release-5.4 pd=release-5.4

/run-all-tests tidb=release-5.4 tikv=release-5.4 pd=release-5.4 tiflash=release-5.4

/run-integration-test tidb=release-5.4 tikv=release-5.4 pd=release-5.4 tiflash=release-5.4


[Angular2] router-link needs router-params

@btford I assume you prefer the issue in this repo even the code is in the Angular2 repo for now?
I have this template
Login

And the navigation won't work if I don't add route-params, even if I don't need it:
Login

It looks like because the method updateHref is waiting for both attributes to be set:
in router-link.js:
if (isPresent(this._route) && isPresent(this._params)) {
  var newHref = this._router.generate(this._route, this._params);
  DOM.setAttribute(this._domEl, 'href', newHref);
}

I would gladly submit a PR, but I'm not sure what would be the proper way to fix it...

Looks like it will be fixed by https://github.com/angular/angular/commit/77d1fc149a0eb34bc872b8444c763bd05466f53c


Move logical size calculation to "online"

I see two problems with the suggested approach:

self.gert_wal - this function is not so easy to implement because PS is not storing original WAL stream, it stores scattered by key WAL in its key-value storage.
// do the blocks +- calculation => i64
It actually requires duplication of all logic from walingest.rs. I am even not speaking that apply WAL twice is not so good idea.

So my vision of the logical size problems there following:

Logical size cane calculated (as it is done in vanilla) as sum of logical size of all relations. Usually there are not so much relation in the database, so it should not take a lot of time. Also logical size will be needed mostly for reporting database size for user - so it will be called quite rarely.
No need to limit maximal database size at all! IMHO we do not need to calculate logical or synthetic size. We can limit number of storage used by tenant on PS (other layers will be evicted to S3) and change users for the produced WAL (it is also storage spect of billing, we can also charge for CPU time, network traffic,...)

self.get_wal - this function is not so easy to implement because PS is not storing original WAL stream, it stores scattered by key WAL in its key-value storage.

Ah yes, was thinking this was the reason; we essentially store (key, lsn) so this becomes multiple full btree key reads. Which is not to say it would be completly out of question, I think we do have an api with layer files we could use to filter and sort these out.  But, perhaps inelegant.
I was going to write "I wish we would store wal in layer files sequentially by LSN and have btree on top of that". I can't remember nor have time right now to investigate, do we store it like this?

// do the blocks +- calculation => i64
It actually requires duplication of all logic from walingest.rs

Well, it would be great to factor walingest a bit, but I see what you are meaning, the process can be long winded.. Oki, perhaps the idea doesn't really work out so well.

Logical size can[ b]e calculated (as it is done in vanilla) as sum of logical size of all relations. Usually there are not so much relation in the database, so it should not take a lot of time.

I think this is exactly how we calculate it right now, is it not?
The reason why we do a lot of these is because of eviction_task's imitations. Imitations are needed because evictions happens on the basis of last access, and accessing the cached vaues does not touch the last accessed values of layers.

No need to limit maximal database size at all! IMHO we do not need to calculate logical or synthetic size.

Going back to what I remember the idea was to model the COW near-ideal bytes. That way we don't have to worry about implementation details moving the cost needle for user as evolution happens. There would also be incentive for us to optimize so that we move closer to the model.

We can limit number of storage used by tenant on PS (other layers will be evicted to S3) and change users for the produced WAL (it is also storage spect of billing, we can also charge for CPU time, network traffic,...)

Limiting number of storage used by tenant: We could quite semi-easily run some tests with this, if not now maybe soon, Chi has some PRs moving towards "register interest at layer file" so we would have security of not causing file not found errors while evicting. You are thinking that on flush and download we evict eagerly the LRU layer files, or do anything to keep it down, aside from evicting currently accessed layers?
However, I think the problem with this approach is that user does not really have any control on the physical layout that pageserver creates for their wal records/images. This would probably be ok, if the effects on the database operations were random, but they are not. Updates to some relation can require first getting L1 for that relation, then adding a row in some other relation will require eviction of the last L1 and downloading a new one.

I think this is exactly how we calculate it right now, is it not?

No, we are now maintaining logical timeline sizer in memory - it is called incremental logical size.
So the expensive thing is initial logical size calculation after PS restart. Incremental update of logical size is quite simple.

The reason why we do a lot of these is because of eviction_task's imitations. Imitations are needed because evictions happens on the basis of last access, and accessing the cached vaues does not touch the last accessed values of layers.

Why not to maintain access counters in layer map?

Going back to what I remember the idea was to model the COW near-ideal bytes.
Logical size doesn't take in account COW at all. Synthetic size tries to model it, but it is quite complex and expensive to calculate.

My suggestion is based on the assumption that S3 storage is cheap. So there is not so much reasons for us to try to"model" COW and calculate synthetic size. May be we will spend more money for calculating it rather than just have unlimited storage  size (real serverless!) and just swap layers to S3.

You are thinking that on flush and download we evict eagerly the LRU layer files, or do anything to keep it down, aside from evicting currently accessed layers?

Sorry, I do not understand the question. My suggestion is quite simple: limit total size of tenant's layers files stored locally at PS. Using LRU discipline we throw away excessive layers. Any "file not found" errors during eviction just mean some race condition which should be fixed.  I am not familiar with recent layer map refactoring, but there should be no problems with replacing local layer file with RemoteLayer in layermap.

However, I think the problem with this approach is that user does not really have any control on the physical layout that pageserver creates for their wal records/images. This would probably be ok, if the effects on the database operations were random, but they are not. Updates to some relation can require first getting L1 for that relation, then adding a row in some other relation will require eviction of the last L1 and downloading a new one.

User should not have any control on own internal layers. What you have described in trashing - when working set is larger than PS open-tenant limit for local storage. Still it should not happen that we evict just loaded layer. May be I just do not completely understand your explanation. Update of any relation most likely require just latests L0 layer. But it may certainly also need L1 layer. If it is not present in PS we have to download it. Access to another relation may need some other layer, doesn't matter L0 or L1. If it is absent, we also have to download it (but it should not cause eviction of first layer. It can can happen only ion the worst case when user have many huge relation and simultaneously updating all of them. It is transhing.
It can be avoided by just extending limit for local PS storage.
I do not think that we should ever inform user about this limit and current total size of layers stored in PS.  Just until some moment work with database is fast because working set is located in PS. And starting from some moment swapping to S3 takes place. User can improve performance by choosing more expensive plan. It may be not so good that we can not  precisely till him home much storage at PS awe actually needs. But IMHGO it is still better then returning error that you project quota is exceeded. And it certainly more looks like real server-less.

@knizhnik @koivunej your discussion started my thinking of the following:
Could we run a separate process in a lambda function / low-cost instance, that will iterate over S3 bucket tenants and do the calculation?
This way eliminates all hacks we do to imitate access to layers and the fact we download layers for it on some occasions.

@knizhnik @koivunej your discussion started my thinking of the following:
Could we run a separate process in a lambda function / low-cost instance, that will iterate over S3 bucket tenants and do the calculation?
This way eliminates all hacks we do to imitate access to layers and the fact we download layers for it on some occasions.

We do not need to iterate through all layers to calculate logical size. We just need relation metadata. Unfortunately this metadata is scattered through the whole database space:
// RelSize:
// 00 SPCNODE  DBNODE   RELNODE  FORK FFFFFFFF

I have created PR which moves this metadata to the end of keyspace, but it requires some ugly code to preserve backward compatibility and ... I didn't notice some significant reducing of write amplification.
But in any case - yes, it is possible to try to extract relation metadata at page server and sum relations size. But it will be deteriorated information because most recent values are stored  in PS layers.
I do not see what advantages we can get here: such calculation in any case will happen at PS node. The only difference is that it will have to retrieve data from S3 rather than from local disk.
I still think that calculation of logical size is expensive and useless if we do not taker in account CoW.

I do not see what advantages we can get here: such calculation in any case will happen at PS node. The only difference is that it will have to retrieve data from S3 rather than from local disk

I thought of this code running in a cheap instance with only size logic calculation
But I totally agree that if we can reach a formula it's much easier, something like:
(physical_size * price_unit_to_ssd)  + (((remote storage/normal_amplification_constant) - physical_size) * price_unit_to_s3)
this will account for both nvme storage for the tenant as well as for its S3 usage, WDYT ?

I like this approach, @stepashka @acervantes23 would love to hear your thoughts about this one, maybe indeed we can simplify this.

Or if I am completly off please let me know, I am having hard time tracking the different ideas and why we wanted this online calculation which sohuld be updated to the issue desc.

We have access counters. But when you read the logical size, it does not access layers. We did bounce around some ideas, but none were implemented. We have imitation (redoing the calculation) instead.

Ok, logical size calculation dopes't update access counters. I still do not completely understand why (non-incremental logical size calculation is just extracting relation metadata, particular key-value pair and from layman point of view it has not difference from access to any other data). And especially I do not understand why it cause some problems and requires some imitations. Non-incremental logical size is calculated just once at PS startup. And eviction is expected to be done permanently...

And by extending, you mean make it a paid feature? If so, it makes sense to me.
Yes, free-tier client have some limit (unknown for them mostly because it makes sense only in content of our internal data representation).  Paid customers should have some large limit (still precise value is not published). I do not think that it is possible to avoid limit at all, because otherwise some client can exhaust disk space as PS. User should be able to control PiTR interval, inspect current logical database size (sum of logical size of all relations) and may be get some statistic about PS hits/misses.


Move several log messages to the debug level

Fix #392
Fix lima-vm/lima#1160

@cfergeau Could you take a look?
CI failures seem irrelevant

/lgtm
/approve


Refactor seq

summary
This PR is pure refactoring. The goal was to make only non-breaking changes, which was mostly honored. The exception was with respect to method names and model hooks (see below).
highlight changes

Rearranged some components of compute_free_surface and finalize_free_surface to actually separate at the point of computation vs finalization. All docs and tests were updated accordingly.
run_one_timestep has been renamed to solve_water_and_sediment_timestep. This makes the method name fall in line with the underlying modular design of route_water and route_sediment, which can be swapped out for non-routing-based solvers. These two methods are still orchestrated by solve_water_and_sediment_timestep. This change required many small changes to names in docs and tests, but the change was simple. Note, this is a breaking change with respect to the hook_run_one_timestep, which is now replaced with hook_solve_water_and_sediment_timestep.
water routing is now wrapped into a single method route_water called from solve_water_and_sediment_timestep (formerly run_one_timestep), so that it matches the API for sediment routing (route_sediment, formerly sed_route).
sediment routing method has been renamed route_sediment to be more descriptive, and now matches the water API (route_water).
sediment routing now has a separate method for initialization init_sediment_routing, matching the water routing API.
across all of these changes, hooks, tests, pyplots, and documentation have been updated

hook deprecation
This PR introduces a necessary evil, I think, regarding hooks. When a hook is deprecated due to it's parent method being deprecated (e.g., hook_run_one_timestep), there is no way to let a user of a subclass know that this hook is no longer being called. So, the best I could come up with is to add deprecated hooks to a "forbidden list", and then raise an error that the implemented hook is no longer available, and supply the new name to use.

@elbeejay wondering if you agree with the name changes here, and the deprecation approach. This will be a somewhat breaking change, so want to run it past you. Also, you are welcome to give a full review, but don't want to make you look at all of it, may be easy enough if you go commit-by-commit tho.

@elbeejay wondering if you agree with the name changes here, and the deprecation approach. This will be a somewhat breaking change, so want to run it past you.

Yeah commit-by-commit was a good idea, made it pretty easy to look through. I'll confess I haven't built the docs locally to make sure the updates covered everything there.
Overall I think the PR goes a long way to making the method naming more consistent throughout the model :+1:. Re: the deprecation stuff, I don't have strong feelings about it - I don't know if anyone out there is really subclassing besides us at this time. Is the plan to drop all of those deprecation messages and warnings whenever we move to v2?


Statistics and visualizations per challenge

Difficulty, success, challenge popularity, completion speed, etc.

@nickfrostatx assign yourself or @atti1a

Some of this stuff was specific to OverTheWire (like completion speed).  I think solve counts (and aggregate statistics about solve counts) should be the main metric we look at for challenges.
Time of first solve is interesting, but with a small CTF it tells us more about teams' strategies (eg. do the lowest point challenges first) than about the challenge itself.


Fix typo.

@MitjaBezensek : Thanks for your contribution! The author, @markingmyname, has been notified to review your proposed change.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerbi-docs/developer/office-store.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@MitjaBezensek : Thanks for your contribution! The author, @markingmyname, has been notified to review your proposed change.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

powerbi-docs/developer/office-store.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Error when creating new virtual machine

I use the command docker-machine create --driver=parallels prl-dev. But it failed with:
Error creating machine: Error in driver during machine creation: prlctl create prl-dev --distribution boot2docker --dst /Users/daniel/.docker/machine/machines/prl-dev --no-hdd failed: exit status 255

parallels version is 11.0.2 pro edition

here is the output if running with debug flag:
Docker Machine Version: 0.5.0 (04cfa58)
Found binary path at /usr/local/bin/docker-machine-driver-parallels
Launching plugin server for driver parallels
Plugin server listening at address <IP_ADDRESS>:64936
() Calling RpcServerDriver.GetVersion
Using API Version 1
() Calling RpcServerDriver.SetConfigRaw
() Calling RpcServerDriver.GetMachineName
(flag-lookup) Calling RpcServerDriver.GetCreateFlags
Making call to close connection to plugin binary
Making call to close driver server
(flag-lookup) Calling RpcServerDriver.Close
Successfully made call to close driver server
Found binary path at /usr/local/bin/docker-machine-driver-parallels
Launching plugin server for driver parallels
Plugin server listening at address <IP_ADDRESS>:64940
() Calling RpcServerDriver.GetVersion
Using API Version 1
() Calling RpcServerDriver.SetConfigRaw
() Calling RpcServerDriver.GetMachineName
(prl-dev) Calling RpcServerDriver.GetMachineName
(prl-dev) Calling RpcServerDriver.DriverName
(prl-dev) Calling RpcServerDriver.GetCreateFlags
(prl-dev) Calling RpcServerDriver.SetConfigFromFlags
Running pre-create checks...
(prl-dev) Calling RpcServerDriver.PreCreateCheck
(prl-dev) DBG | executing: prlctl --version
(prl-dev) DBG | executing: prlsrvctl info --license
(prl-dev) DBG | Found Parallels Desktop version: 11, edition: pro
(prl-dev) Calling RpcServerDriver.GetConfigRaw
(prl-dev) Calling RpcServerDriver.GetConfigRaw
Creating machine...
(prl-dev) Calling RpcServerDriver.Create
(prl-dev) OUT | Creating SSH key...
(prl-dev) DBG | SSH key: /Users/daniel/.docker/machine/machines/prl-dev/id_rsa
(prl-dev) OUT | Creating Parallels Desktop VM...
(prl-dev) DBG | executing: prlctl create prl-dev --distribution boot2docker --dst /Users/daniel/.docker/machine/machines/prl-dev --no-hdd
Error creating machine: Error in driver during machine creation: prlctl create prl-dev --distribution boot2docker --dst /Users/daniel/.docker/machine/machines/prl-dev --no-hdd failed: exit status 255

Same as Parallels/docker-machine/issues/4?

I have tried to use the workaround mentioned --parallels-boot2docker-url https://github.com/boot2docker/boot2docker/releases/download/v1.8.2/boot2docker.iso also tried boot2docker 1.9.0.
To be sure to have the newest iso in the local cache, i have run a docker-machine upgrade on an existing virtualbox vm.
But in all cases the error is the same.

@dzwicker No, in your case there is some error while creating a new virtual machine in Parallels Desktop.
Unfortunately, debug log doesn't provide a verbose output from our plugin (due to https://github.com/docker/machine/issues/2145).
Please execute the specified command in the terminal:
prlctl create prl-dev --distribution boot2docker --dst /Users/daniel/.docker/machine/machines/prl-dev --no-hdd

Is there any error message?

Creating the virtual machine...
Generate the VM configuration for boot2docker.
Remove the hdd0 device.
Failed to register the VM: The operation failed. To perform this operation, you must enter the host OS administrator's credentials.
Failed to create the virtual machine.

I have all the 'Require Password to:' under the security preferences enabled. Turning off password for creating a vm fixed this error .

See comment before

Yes, that's a little bit confusing message, but actually prlctl couldn't manage VMs unless security preferences are disabled
https://github.com/Parallels/docker-machine/issues/8
https://github.com/Parallels/vagrant-parallels/issues/67#issuecomment-32774326


Homepage promo updates

Updating the homepage promos. I've updated them and added the new
images. The images have been resized and cropped to the correct
size, optimised using photoshop and optimised further using
imageoptim.
3 new promos -
• election 2015
• vehicle tax has changed
• find a job
Also another minor update, adding a deadline date to the register to
vote promo on the homepage.
Redundant images removed.
https://www.pivotaltracker.com/story/show/91380894
Before -

After -

:sunny:


Impact on performances ?

Hello, this is more a question than an issue but there is nothing related to the performance overhead added by vernier on a ruby program, did someone made a benchmark or something like that already ?

It's hard to give a specific number, since there are a variety of factors. But I think we should state something in the README. Vernier is a sampling profiler so we expect the overhead to be very low (and based on the sample rate set).
I did commit examples/measure_overhead.rb the first test of which shows that as expected there is almost no overhead:
$ ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-linux]
Warming up --------------------------------------
         no profiler   737.000 i/100ms
             vernier   725.000 i/100ms
Calculating -------------------------------------
         no profiler      7.374k (± 0.4%) i/s -     37.587k in   5.096970s
             vernier      7.275k (± 0.2%) i/s -     36.975k in   5.082242s

Comparison:
         no profiler:     7374.5 i/s
             vernier:     7275.4 i/s - 1.01x  slower

Nice, thx for the benchmark, I will give it a try in production and see how it goes then :)


Install rtx with home-manager since 23.11 stable release

Looks nothing at this moment
https://github.com/jdxcode/rtx/issues?q=is%3Aissue+is%3Aopen+nix
https://github.com/NixOS/nixpkgs/search?q=jdxcode%2Frtx&type=issues

https://github.com/NixOS/nixpkgs/pull/218450 merged.
As I understand it, unstable or 23.11 channel can use it.
Avoiding the unstable channel as https://github.com/kachick/dotfiles/commit/5efa3ecf7c9b57e8f9588988e56ac7cc86b27f2c, so I will integrate it in next release

dprint issue is fixed, so using unstable is a way.

https://github.com/nix-community/home-manager/pull/4051
https://github.com/nix-community/home-manager/blob/f58889c07efa8e1328fdf93dc1796ec2a5c47f38/modules/programs/rtx.nix#L12
Provided the manager 😮

Currently raising error in zsh
https://github.com/kachick/dotfiles/actions/runs/5712841784/job/15477106695?pr=223#step:10:23
/home/runner/.config/zsh/.zshrc:60: no such file or directory: /home/runner/.local/share/rtx/bin/rtx


ARROW-3862: [C++] Improve third-party dependencies download script

The following changes were made:

Refactored definitions such that adding a new dependency should not
involve modifying the script but only the version.txt. file (excluding cmake).
Safer bash mode with -u
Added version in the tarball at the cost of disk size, but safer
operation if content-length match for some unlucky reason.

I opened https://issues.apache.org/jira/browse/ARROW-3863 about the flaky Ruby build. Just restarted that build here

All comments were addressed (minus the URL discussion).


Run rush audit before bumping version

It is possible that between the latest commit on a branch, and when the version bump commit is created, a CVE could have been introduced causing the version bump CI build to fail. This PR updates the pipeline to run rush audit before creating a version bump commit as a validation step to avoid this.

Could you also update audit.js to remove the last advisory we added, since it was bogus and withdrawn?


Add Version Number to Duck Generator to Allow for Forward Compatability

Idea
Pretty much one of the big problems with the duck generator is that there needs to be forward and backward support. Right now, there is not, so I am thinking we should just get rid of the whole system and create something new instead. So, the new format will need to support versioning as a default and all future formats will need to follow that versioning system.
The issue with the information about formatting and where the versioning will actually be implemented is this issue.

The version number is now a built-in part of the parser.


PF-727: Update readme with resources changes

Updated the README with the reorganized terra resources group of commands.
Also did a pass through both README and CONTRIBUTING updating wording and fixing paragraph structure.

Thanks! Not always easy to know when the documentation is helpful, but I know I've appreciated having it.

I hear you on not knowing when to look at which documentation page. I've been thinking perhaps a reorganization of the documentation might be helpful. (README for a description of the GitHub repo and what the code does, USER-GUIDE with examples/instructions for CLI users, CONTRIBUTING for developers). Thoughts?

That sounds good to me, though maybe keep the user guide in the front readme to make it even easier for users to find info.
(to be clear, I'm happy with what you've been adding so far :) )


Loosen Pylance version

Is it possible to loosen the pylance version restriction? The pinning to 0.14.1 is causing a few issues on our package resolution to due subsequent dependency on legacy pyarrow versions.

I think we will eventually be able to do this, once we docouple the Python package from pylance. However, right now, they are very tightly coupled. New features in LanceDB are often just features in pylance that we expose in a new API. So we can't loosen it very much right now.
That being said, in the next release of pylance we will loosen the pyarrow pin (https://github.com/lancedb/lance/pull/2597), so that should alleviate your issue.


snmp_diagnostics: 0.1.1-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository snmp_diagnostics to 0.1.1-1:

upstream repository: https://github.com/ctu-vras/snmp_diagnostics.git
release repository: https://gitlab.fel.cvut.cz/cras/ros-release/snmp_diagnostics.git
distro file: noetic/distribution.yaml
bloom version: 0.12.0
previous version for package: null

snmp_diagnostics
* Initial release with the IF-MIB module. Do not consider any API stable yet.
* Contributors: Martin Pecka

New package review checklist

[x] At least one of the following must be present

[x] Top level license file: https://github.com/ctu-vras/snmp_diagnostics/blob/master/LICENSE
[ ] Per package license files:

[x] License is OSI-approved: https://opensource.org/license/bsd-3-clause
[x] License correctly listed in package.xmls
[x] Public source repo: https://github.com/ctu-vras/snmp_diagnostics
[x] Source repository contains ROS packages
[x] Each package meets REP-144 naming conventions - while the name is somewhat generic, it also precisely describes what the package does.  Thus I believe it meets REP-144.

@alsora Can you take another look at it, and if you agree with my reasoning, merge this in?


more than one component with the same name in a project module, but UI always opens the first created one

It's possible to have more than one component with the same name in a project module, but UI opens always the first created one. It's not possible to open the second one.

Perhaps a simple first step would be to forbid path/name duplicates in all modules.

I think the best way to get unique path.
Name and description are common attributes for all resources and their usage should stay the same and coherent between resources, this is why I don't like the idea to make name unique.
To verify that path is unique on server, we derive uuid from the path. This will require to reindex 17 existing modules in production to get the new uuids.

@mebster pointed the issue of moving module to another path.
This give advantage to make a search in modules to check if the path is unique without using the dervied uuids.
For info: In the UI, actually the name field is used to specify the name and the path of the module at the same time. The path is created from the name but is lowercase string with spaces replaced by dash


[Central_v2] - Bug Report - # Line 42 Desktop

Describe the bug
Highlight on click - Highlight only appears once previous two cards are completely filled
To Reproduce
Steps to reproduce the behavior:

Go to Create Question page
Click on incorrect answer card
See error

Expected behavior
Incorrect answer card to highlight on click
Screenshots

Desktop (please complete the following information):

MacOS
Chrome; Safari

Additional context
Add any other context about the problem here.

Same question as:

https://github.com/rightoneducation/righton-app/issues/1373
https://github.com/rightoneducation/righton-app/issues/1380

cc @rod-hinn


SDD Template is now legacy

This sets can_create to no for the SDD template, effectively making it unavailable for new Spaces.

Ike Plugins (test-keeper)
Thank you @michaelkleinhenz for this contribution!

It appears that no tests have been added or updated in this PR.
Automated tests give us confidence in shipping reliable software. Please add some as part of this change.
If you are an admin or the reviewer of this PR and you are sure that no test is needed then you can use the command /ok-without-tests as a comment to make the status green.
For more information please head over to official documentation. You can find there how to configure the plugin.

/ok-without-tests

Hey @michaelkleinhenz! It seems you tried to trigger /ok-without-tests command, but this will not have any effect due to insufficient permission. You have to be admin or requested reviewer or pull request approver, but not pull request creator for this command to take an effect.

/ok-without-tests

Hey @baijum! It seems you tried to trigger /ok-without-tests command, but this will not have any effect due to insufficient permission. You have to be admin or requested reviewer or pull request approver, but not pull request creator for this command to take an effect.

/ok-without-tests


Starting location

We should show the starting location on the map, and add the context menu item to quickly set it.

Closed in 0adf4bb7a4025444c467ecaa5fcd2c73319cf37e .


adds declarations for pseudobooleans

Hi, I've got a couple of additions coming to the higher level api as well. thanks for you work on this library.

Hello. I had taken over maintenance of this crate and it now lives at https://github.com/prove-rs/z3.rs
In the course of my updates there, I have already added these bindings. Feel free to contribute any other changes though!


Lighting is broken on some blocks (namely stairs) depending on how they're placed.

Minecraft 1.20.1, Forge 47.3.0, any mod version ≥2.0.0.
Placing blocks with the arrow indicator on the ground places blocks that have normally shaded faces, placing blocks with the arrow facing upwards causes broken shading. Rolled back to 1.8.0, works perfectly fine.

This is most likely a conflict between a mod that modifies block rendering, and the rotated models feature introduced in 2.0.0. either find and remove the offending mod, or disable rotated models in the client config.


Add path validation to signers & verifiers

Since path should always start with / we can validate that this is the case and return a helpful error before an incorrect signature or incorrect verify usage ends in an opaque error.
E.g. trying to use the whole url .path("https://example.com/foo"). We could produce something like an error invalid path "https://example.com/foo" must start with '/'.
We can use the full url scenario as a new test for signing & verifying in all langs.

Perhaps invalid path, it must be a relative path starting with '/'?
It might even be possible to suggest the correct one by playing around with HTTP URL parsing (e.g. you probably wanted to pass '/foo'?).

Perhaps invalid path, you passed an absolute URL. The path must be relative, starting with '/'? It might even be possible to suggest the correct one by playing around with HTTP URL parsing (e.g. you probably wanted to pass '/foo'?).

That would be very nice, but the biggest win is just having any error saying "path" instead of just generating an invalid, or failing verify a, signature which indicates very little. So the simplest impl is just ensuring the path starts with /.

Also related to the proposed reason deduction, but this issue is much easier to achieve https://truelayer.slack.com/archives/C01UYLYQ2HE/p1655124955742179
^^ that would actually suggest the correct path in the signing case. I should move that proposal to an issue here...


Allow setting server bind address

Hello,
This change allows the server to be bound to alternate interface, either via commandline argument or the BIND_ADDRESS environment variable.
The newer version of camp is required as the 'hostname' settings parameter was introduced into camp in https://github.com/espadrine/sc/commit/b071d163b42c889017d4063031606fd546b4fe83, which appears to be newer than the version of camp previously used.
Thanks!
Mike

Thanks for contributing!
I'd love you to detail the use-case you are solving.

Essentially the use-case is to allow greater deployment flexibility - I'm on the DevOps team for ondemand.coverity.com and we needed to make this change to be able to run local shields.io servers in development/testing environments, without the need of deploying behind a reverse proxy.
Being able to specify the bind interface is a feature I use quite often on a lot of things, as I often work on remote systems via ssh and connecting to localhost or via IPv6 is not always easy; I though others might find themselves in similar situations and find this ability useful :)

That's a good use-case, and great explanations. Thanks a lot!


[BUG] create:map fails with untyped fields

Given a profile which contains a use case like:
usecase Request safe {
  input {
    headers string
    body
  }

  result {
    ok boolean
  }
}

I run sf create:map with this profile.
Expected Behavior
Map is created.
Current Behavior
I get an error: Error: Type is undefined with no futher information.
Rerunning the cli with DEBUG='*' gives me the following stack trace:
Error: Type is undefined
    at .../node_modules/@superfaceai/cli/dist/templates/prepared-map/usecase/example/structure-tree/parse.js:96:23
    at Array.map (<anonymous>)
    at visitObjecDefinition (.../node_modules/@superfaceai/cli/dist/templates/prepared-map/usecase/example/structure-tree/parse.js:91:35)
    at visit (.../node_modules/@superfaceai/cli/dist/templates/prepared-map/usecase/example/structure-tree/parse.js:12:20)
    at Object.parse (.../node_modules/@superfaceai/cli/dist/templates/prepared-map/usecase/example/structure-tree/parse.js:5:12)
    at extractExample (.../node_modules/@superfaceai/cli/dist/templates/prepared-map/usecase/example/build.js:11:33)
    at .../node_modules/@superfaceai/cli/dist/templates/prepared-map/usecase/example/build.js:30:24
    at Array.map (<anonymous>)
    at Object.buildUseCaseExamples (.../node_modules/@superfaceai/cli/dist/templates/prepared-map/usecase/example/build.js:27:45)
    at .../node_modules/@superfaceai/cli/dist/templates/prepared-map/usecase/prepare-usecase-detail.js:24:34

Steps to Reproduce

Create a profile foo with a use case containing an untyped field and any provider bar
Run superface create:map foo bar
Observe the error

Your Environment
@superfaceai/cli/3.0.1 linux-x64 node-v18.12.1 (with<EMAIL_ADDRESS><EMAIL_ADDRESS>

Fixed in v3.0.2 by #274


Limit metaspace used by the daemon

@oehme I've merged release into your branch and triggered another build.

@oehme Have you seen the tests failing on the latest build? https://builds.gradle.org/viewQueued.html?itemId=16956208&tab=queuedBuildOverviewTab

I guess we're still leaking more than I hoped :/

The other failures were due to a Groovy leak. We have a workaround for that leak, but it wasn't activated because it was checking for version == 2.4 and we are on 2.5 now.

Ping @paulk-asert @jwagenleitner :point_up:

Starting with Groovy 2.5.x java.lang.ClassValue is used by default for caching class information. It may not make a difference and isn't a final fix (as noted there are still other places that hold hard refs), but I'd be interested to know if things are different if you run your tests with -Dgroovy.use.classvalue=false.

@jwagenleitner I found another leak in the Preferences class. It registers a global change listener which is never removed, leaking the classloader that loaded Groovy. This leak seems to be new in 2.5, although the class in question is old. Maybe it is now on one of the code paths we use and wasn't before.

That change listener really only makes sense for groovysh I think. It would be worth seeing if moving it's initialization to a static method which can be called from groovysh fixes the problem.

Alright, I've finally reached a workable state. There are plenty of leaks left, especially around script loading and Kotlin compilation. I'll open separate issues for those and try to lower our memory limits further once they are fixed.


Preflight upgrade validations for pod disruption budgets

Issue #, if available:
https://github.com/aws/eks-anywhere/issues/5189
Description of changes:
This PR introduces preflight upgrade validations for clusters having pod disruption budgets. If a cluster has any pod disruption budgets active on it, EKSA will error out for upgrade cluster command. We provide a flag for the users to skip the preflight validations if they wish to.
The design doc for this issue is here https://github.com/aws/eks-anywhere/pull/5685
The help command looks like this:
This command is used to upgrade workload clusters

Usage:
  anywhere upgrade cluster [flags]

Flags:
      --bundles-override string             Override default Bundles manifest (not recommended)
.....
      --per-machine-wait-timeout string     Override the default machine wait timeout per machine (default "10m0s")
      --skip-validations stringArray        Bypass upgrade validations by name. Valid arguments you can pass are --skip-validations=pod-disruption
.....

Testing (if applicable):

Unit tests
Manually testing the CLI

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/woof

/approve


Reorganising

Features by packages:
godot.c - low level C stuff which by my understanding is purely for C ABI to make interop part happy.
godot.d - wrappers of godot.c for not doing bytes massaging in high level language
godot.core - mimics godot engine built-in types API somewhat like godot-cpp does
util.generator - a real mess!
Inside godot.d there is also register.d that does class registration with some help from script.d that wrap.d them in order to interact with godot engine and call its methods by using bind.d.
godot.d.bind is the main work horse, and basically all methods calls is done by ptrcall(), with some help from godot.core.variant

Fixed in 9db0554

godot.api -> godot.util
godot.api.util -> godot.util.tools
godot.c -> godot.abi
godot.d -> godot.api
godot.util.path -> godot.api.path
godot.core -> godot
godot.c.core -> godot.abi.core + godot.abi.types
godot.core.defs -> godot.api.types
godot.d.type -> godot.api.types


Elastic Weight Consolidation + regularization refactor

Implemented EWC from: https://arxiv.org/pdf/1612.00796.pdf
Moved the regularization to a separate module/classes.
Added GradientRunner for easier gradient output.
Added script for gradient averaging.

Note, that currently this branch removes the default l1, l2 logging into summaries

Oh, I didn't even notice. I'd like to keep the L2 plot in TensorBoard.

The L2 plot is back.

Právě kvůli ty sémantice bych to nedělal.. regularizers jsou regularizers a
new regularizers and then some..
Dne pá 3. 8. 2018 21:48 uživatel Dušan Variš<EMAIL_ADDRESS>napsal:

@varisd commented on this pull request.
In neuralmonkey/trainers/generic_trainer.py
https://github.com/ufal/neuralmonkey/pull/742#discussion_r207649319:

         # unweighted losses for fetching

       self.losses = [o.loss for o in objectives] + [l1_value, l2_value]

       tf.summary.scalar("train_l1", l1_value,

                         collections=["summary_train"])

       tf.summary.scalar("train_l2", l2_value,

                         collections=["summary_train"])

       self.losses = [o.loss for o in objectives] + reg_values

       # we always want to include l2 values in the summary

       if L2Regularizer not in [type(r) for r in self.regularizers]:

           reg_values.append(L2Regularizer().value(regularizable))

Ten L2Regularizer by se mel pridat i do self.regularizers.
reg_values se potom, co se pridaji do summaries, dale uz nikde
nepouzivaji, takze neni problem tam pridat tenhle "default" regularizer
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ufal/neuralmonkey/pull/742#discussion_r207649319, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABwcs4sS68v6cTEfJRcyTu-TgJa6xpDFks5uNKkLgaJpZM4VkjNe
.

S/new/ne/
Dne pá 3. 8. 2018 21:54 uživatel Jindra Helcl<EMAIL_ADDRESS>napsal:

Právě kvůli ty sémantice bych to nedělal.. regularizers jsou regularizers
a new regularizers and then some..
Dne pá 3. 8. 2018 21:48 uživatel Dušan Variš<EMAIL_ADDRESS>napsal:

@varisd commented on this pull request.
In neuralmonkey/trainers/generic_trainer.py
https://github.com/ufal/neuralmonkey/pull/742#discussion_r207649319:

         # unweighted losses for fetching

       self.losses = [o.loss for o in objectives] + [l1_value, l2_value]

       tf.summary.scalar("train_l1", l1_value,

                         collections=["summary_train"])

       tf.summary.scalar("train_l2", l2_value,

                         collections=["summary_train"])

       self.losses = [o.loss for o in objectives] + reg_values

       # we always want to include l2 values in the summary

       if L2Regularizer not in [type(r) for r in self.regularizers]:

           reg_values.append(L2Regularizer().value(regularizable))

Ten L2Regularizer by se mel pridat i do self.regularizers.
reg_values se potom, co se pridaji do summaries, dale uz nikde
nepouzivaji, takze neni problem tam pridat tenhle "default" regularizer
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ufal/neuralmonkey/pull/742#discussion_r207649319,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwcs4sS68v6cTEfJRcyTu-TgJa6xpDFks5uNKkLgaJpZM4VkjNe
.

Jo, testy jsem jeste neresil.
Ten gradient runner pouzivam, abych si vyprintil gradienty z celeho datasetu (vetsinou validacniho, protoze neni tak velky). Z toho si pak bokem udelam prumer gradientu pro kazdou vahu modelu; ty pak muzu pouzit v EWC.


Create and manipulate posts

User Story

As a user, I can create a post

As a user, I can retrieve all of my posts

As a user, I can retrieve a post by id

As a user, I can update the title of a post

As a user, I can delete a post

Post routes successfully created and verified


Highlight Issues

I am having an issue with spaceport.nvim and reactive.nvim.
It appears reactive is somehow changing all the highlights from my start screen.
So this

Turns into this

Is there a buf_ignore for reactive?(Because the config options don't stop reactive from changing the highlights)
I have seen another issue here that seems to be a version of this but can't confirm(as another plugin indent-blankline also causes the issue which is fixed by using the ignore option.
So can we get something similar?
[P.S. I already checked my plugin manager and it can't disable plugins based on buffer_type and file_type so this is the next best thing]

Hi there! There's a skip function available inside a preset spec. You can use it turn off highlights when it returns true. There's also an example in the README, look at this image:

If you want to configure presets added by someone else and not yourself, then you can do it during setup.
require('reactive').setup {
  configs = {
    ['yourpresetname'] = {
      skip = function() end
    }
  }
}

Please try those methods and tell me whether the issue is solved.
By the way, I'm not really sure how reactive affects those colors you mentioned. The only reason I can see is that they are linked to the colors used by reactive.

You see that's the problem.
Let me tell you what actually is happening.

When the nvim command is used an empty buffer(the default start screen) is created. Your plugin and every other plugin reads the buffer type of it(which is "").
Now spaceport changes it to its own buffer and sets the file type to "spaceport".
Which makes the skip property useless.

However one thing I did notice is if I call a refresh on the spaceport buffer all the colors return to their initial values(and reactive isn't working anymore(?))
Anyway, either,
A) Reactive is taking all the highlights but isn't reapplying them(or it's a Neovim bug which isn't letting it apply).
or B) Spaceport highlights are added after reactive has applied its own highlights(essentially somehow overwriting them somehow).
Whatever it is, I have already lost enough brain cells trying to fix it.

I knew it.
The buftype is reported as "" to reactive and then is changed to spaceport.
The issue is fixed. I just had to change the condition from == "spaceport" to == "".
Anyway, thanks for the code snippet.


[BUG] System.UnauthorizedAccessException: Access to the path 'C:\Users\awby2\AppData\Local\Bloxstrap\Bloxstrap.exe' is denied.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
System.UnauthorizedAccessException: Access to the path 'C:\Users\awby2\AppData\Local\Bloxstrap\Bloxstrap.exe' is denied.

Liar
https://github.com/pizzaboxer/bloxstrap/wiki/"Access-to-the-path-is-denied"-error-when-trying-to-reinstall-Bloxstrap


fix(PeriphDrivers): Fix Unusable MAX32690 I2C Pins

Pull Request Template
Description
Fixes #949
The ME18 assigns the same alternate function to both sets of I2C pins.  This is logged as an errata (Rev A2 Errata 16), but in order to make the second set of pins usable our drivers will now configure both sets simultaneously.
Doxygen has been updated on the init function to highlight this change:

Checklist Before Requesting Review

[ ] PR Title follows correct guidelines.
[ ] Description of changes and all other relevant information.
[ ] (Optional) Link any related GitHub issues using a keyword
[ ] (Optional) Provide info on any relevant functional testing/validation.  For API changes or significant features, this is not optional.

Not sure about the MSDK version stuff reverting to the last release.

@sihyung-maxim need to merge #954


Page slowing down firefox becoming a common ocurrency

What happened?
anybody else has seen a similar message on other browsers?

is that happening on nuxt.kodadot.xyz too?

First time on Nuxt today:

I think could be some huge query?

will reopen if stumble upon another occurrence


Option to turn "Command exited with 0" back on

I think this was present in older version of cargo-watch, and I noticed it's still present in watchexec that it shows some text after the child terminated.
The latest version of cargo-watch doesn't do this by default and I couldn't figure out how to turn it back on. Without this text it's difficult to tell from the output if the command completed or hangs. :)
Thanks!

Specifically this was disabled on powershell in windows due to bugs, but still exists elsewhere. Watchexec has a different mechanism for it so it still works there for all platforms.


playground integration

Hey, @EmmaDawsonDev and team great work 👏
I highly appreciate the work!!!  I am looking forward to being part of this amazing journey.
Feature request
Present
The initiative taken to explain each pattern with code examples and demos is amazing. Currently, the code, demo, and styling are isolated. What I meant by isolation is, let's look at the below page breadcrumbs.

Here we start with an introduction, show a demo then give code and the styling.
Feature
a playground where users can interact with code and look at live demos. For example in react.dev  they give code editor to live demo.

can I get the chance to work on this feature ?

This is a nice idea. So far I have considered adding codepen embeds for this, but I haven't got around to it yet. What's your opinion on codepen vs a custom component for this?

Hi @EmmaDawsonDev 👋
I figured out this https://sandpack.codesandbox.io/docs/advanced-usage looks good for our usecase.

I  was going through React dev blogs and got inspired by the challenge section they have. We can also have something like that and user can test their reading.
What are your thoughts ?


Cache browser after deployment

Hi all,
I have an issue related to cache.
I used this command to build production: ng build --aot --configuration=production --output-hashing=all --base-href=https://mbvb1223.github.io/

I changed something (add a new text...) at index.html (or some html component files: contest-list.component.html)
When I access https://mbvb1223.github.io, there is no change.
I have to refresh many times and sometimes need to press shift + f5 then the new added text will be shown

Not sure this issue is related to this boilerplate or not? If anyone knows about this issue, please advise me

I deployed into google firebase, it seems google firebase has some cache config. I will investigate more about it

Hi @mbvb1223, sorry for the late response.
May I ask you which Angular version are you using and a screenshot of the content of your dist folder?
I've used this boilerplate for some projects and never have had any cache-related issues deploying to Vercel, Azure, or Netlify since ng build hashes the lazy chunk files as follows:

So the browser has to download the file again because it has a new name.
Please, let me know if you still need help with this & if you do, please, feel share a project where I can reproduce this issue.
Note: if you're generating your projects from a fork & the fork is outdated, you could try to update it to the latest Angular 12 version with the new GitHub option: "Fetch and merge"

Regards.


Update BufferObjectFlags in README example

Without including BufferObjectFlags::CURSOR, I was getting the following error:
Os { code: 22, kind: InvalidInput, message: "Invalid argument" }

Uh, CURSOR actually means a buffer for a cursor bitmap it seems :see_no_evil: I was confused by the documentation for BufferObjectFlags::WRITE mentioning that it is only guaranteed to work with CURSOR flag... Curiously, removing the cursor flag in my test code is now working. No idea what was happening before.
Carry on!


How to use WebSockets between Ember and Sails ?

Would you have any pointer guiding to an example of using a socket between an Ember Controller and a Sails Controller ?

Yep that is something quite untouched by sane so far - has not been in my critical path yet. But I know off these three projects:

https://github.com/Wildhoney/EmberSockets
https://github.com/huafu/ember-data-sails
https://github.com/bmac/ember-data-sails-adapter

Hope that helps a bit and maybe someone else from the community can pitch in.

Thank you,
I've managed to have EmberSockets installed but during the initialization it complains about [Report Only] Refused to connect to 'ws://localhost:4200/socket.io/?EIO=3&transport=websocket&sid=nEtyYpIlTX9mFJg5AAAC' because it violates the following Content Security Policy directive: "connect-src 'self' ws://localhost:35729 ws://<IP_ADDRESS>:35729".
35729 seems to be the port on wich livereload is working : client   | Livereload server on port 35729
In sails there is a wrapper for socket.io but I'm not sure what it does, or it works or even how to use it in ember. the wrapper can be found at server/assets/js/dependencies/sails.io.js
This is everything I've managed to find so far but I'm lost on how to connect the dots. If someone has more info on the topic I'd be glad to hear from them

I managed to get rid of the security report by dropping the ember-cli-content-security-policy package. It's probably not a good idea but at least I'm progressing.
I also managed to get the sails.io.js in my browser by copying the file in my client/vendor directory and adding the following line in my Brocfile app.import('vendor/sails.io.js');

I wouldn't drop content-security-policy, because you can use it's values to populate the headers when you go live.  Also, ws://localhost:4200 doesn't look right for sails, shouldn't it be a different port?  Anyways, you can just add it to the list of accepted connect-src in your config/environment.js

I'll bring back content-security-policy security then and try to customize it. localhost:4200 is the host and the port on which I go on my browser so I was expecting it is the address I should use but if I understand it correctly when I go live , my ember app will be served by sails so I should use the sails address and port in dev (1337) , then ?

You can host the ember app with the sails app, and I think that's what @Globegitter and @mgenev do with theirs.  I host separately using ember-deploy, with assets going to an S3 bucket and the HTML riding in a Redis database and served up from node.js, where I can version select the SHA1 for the ember app, and set a SHA1 as the default.  This helps me to stage the app, prior to going live with it.

@Systho also, sails.js uses the same port as HTTP, which is 1337 in development.

@Systho I am also trying to use sockets between ember and sails. I am using at the moment https://github.com/huafu/ember-data-sails with sails 0.11 which is not working at the moment but update should be out soon. Look here https://github.com/huafu/ember-data-sails/issues/2

Thank you for your help Kulja. I think I have found the cause of your issue and proposed a workaround (but no real clean fix because my JS skills are too low  ;) ) .
I'm looking forward to use ember-data-sails

I am glad I could help out. I saw your proposed solution, good job!

@Systho @Kulja we now have official websocket support: http://sanestack.com/#sane-stack-sails-ember-websockets
I haven't had the chance to test it myself, so report any bugs if that doesn't work. Closing this in the meantime.

Awesome, I'm trying it immediately !
Many thanks to all of you

yeah fix http://sanestack.com/#sane-stack-sails-ember-websockets and remove In the meantime just add app.import('vendor/js/sails.io.js'); to your Brocfile.js, I forgot to update readme, this is not needed anymore.

@huafu thanks and done.

oh my comment was kinda said in a rude way, result of answering at 4am with a huge hangover haha, anyway, thanks for the update ;-)


pull request for e2e test at 11/12/2016 20:15:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update how-to-configure-connectors.md

Updating for GCP

#sign-off

@kenwith
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Support mailing on Windows

Looks like mailing doesn't run on Windows (see #168).  Add support for Windows in this issue.

I started using mailing around 0.6.2, and it worked fine on windows. Installing later versions (specifically >=0.7.2) broke support on windows. Not sure what changed, but you had it working once before!
Rolling back to 0.7.1 lets it work again, so something between 0.7.1 and 0.7.2 broke it.

In 0.7.2 we began bundling the emailsDir using esbuild.  This is so that you can import source files from outside your emails directory.  I haven't used esbuild on Windows before, do you know if esbuild supports Windows?  Perhaps esbuild needs to be configured differently on Windows?

AFAIK, esbuild works just fine on Windows. I can't speak directly to what the problem is here, but I don't believe it is an esbuild compatibility issue. Based on the other thread, it looks like something to do with cross-platform filepaths, but I didn't dig in to it too much.

Thanks for the info.  There is some dynamic code generation that happens here: https://github.com/sofn-xyz/mailing/blob/e83411abefb3eb494a750088499707ff331c4d04/packages/cli/src/commands/preview/server/setup.ts#L79 and here: https://github.com/sofn-xyz/mailing/blob/e83411abefb3eb494a750088499707ff331c4d04/packages/cli/src/commands/preview/server/setup.ts#L94
I could see that not working since it bypasses the usual process that node has for using the correct filepath separator.  You're right, something like upath might help there.

See also: https://github.com/sofn-xyz/mailing-templates/issues/6 The error message it raises at the moment references lib/beautify, but it is probably not something specific to that library, just happens to be the first import statement it hits

Any Windows users care to take a stab at this or pair on it with one of us?  Message us on Discord: https://discord.com/channels/1027828685098717195/1028005638418202635

@alexfarrill I've got my eyes on this issue as well, looking how much can I do.

Is this issue solved ? Getting error while running npx mailing in windows.
Failed to compile
./src/moduleManifest.js
Module not found: Can't resolve './lib/beautify'

@yatharth1706 this issue is not resolved.  I haven't had a chance to look at it since December.  Do you have any ideas on how we could fix it?

Newer bug report of the same issue: #450

Any progress @alexfarrill ? Or is anyone working on it ?

I'm not actively working on it @samyogdhital.  Do you have any ideas for something we could try to get it working?

Any new updates to mailing.run on windows?


Installing plugin fails with: fork/exec ./nozzle-plugin-linux: permission denied

When i try to install this plugin on Ubuntu 14.04 - 4.2.0-35 kernel version. I get the following errors:
cf --version
cf version 6.16.1+924508c-2016-02-26
cf install-plugin nozzle-plugin-linux -f
Installing plugin ./nozzle-plugin-linux
FAILED
fork/exec ./nozzle-plugin-linux: permission denied

@jyidiego Sorry for the late response. I just came across this issue. Apparently, we don't have the Pivotal Tracker integration set up for this repo.
If you download the plugin from the github release page, you will have to make it executable first, e.g. chmod +x ./nozzle-plugin-linux.
Otherwise, you could just follow the instruction in the README and download the plugin from the community repo.
Let me know if that fixes your problem, so that we can close this issue.

@jyidiego Let us know if you still are unable to install the plugin.


fix: move coercion of union from builder to TypeCoercion

Which issue does this PR close?

Closes #11742.
Rationale for this change
Currently, in the LogicalPlan builder, we coerce the inputs of a union plan to a common schema.
But this common schema is inaccurate because it lacks type coercion for expressions.
For example, in #11742, the return type of the expression nvl(v1, 0.5) is INT before type coercion and will become Float64 afterward.
/// The return type of `nvl` depends on the type of the first argument.
fn return_type(&self, arg_types: &[DataType]) -> Result<DataType> {
    Ok(arg_types[0].clone())
}

The fix is to place coercion of the union after the type coercion of expressions.
What changes are included in this PR?

Move coercion of union from builder to TypeCoercion.
Move some union-related SQL planner tests to slt, as these tests need to perform type coercion to achieve the same results as before.

Are these changes tested?
Yes

Are there any user-facing changes?
Yes
project_with_column_index has become private. It was introduced for UNION in #2108, and I think it should only be used internally.

Looks great @jonahgao  -- thank you

Thanks for the review @alamb


"stable" version unavailable

First off, great project, thanks!
Now, to business. git nim stable exists with an error:
$ git nim stable
git-nim against https://github.com/nim-works/gitnim
+git submodule update --no-fetch frosty
fatal: reference is not a tree: 6b4a82c67d3284848f5cca6e3088d213a3c2abb4
fatal: Unable to checkout '6b4a82c67d3284848f5cca6e3088d213a3c2abb4' in submodule path 'frosty'

So that latest 2.0.x version I can get is 2.0.3, which apparently is a dev version.

Now, after running git nim, I got the command to work but it pulls an ancient 1.4.9 version:
git nim stable
git-nim against https://github.com/nim-works/gitnim

Nim Compiler Version 1.4.9 [Linux: amd64]
Compiled at 2021-10-28
Copyright (c) 2006-2021 by Andreas Rumpf

git hash: a8aaf5a27d3c7697b22c6912bf0510f87343cb5f
active boot switches: -d:release

I lost track of which mainline Nim was stable.  I just decided to call the version-2-0 branch stable, and updated the tag here to point to 2.0.10.  Let me know if that doesn't make sense.
You can simply
$ git nim

to pull in all the new tags, etc.


Publishing Docker images to Amazon ECR Public registry

Describe the feature
Problem
Using Docker Hub public registry can be problematic, as there are now rate limits for the free plan. The fee isn't an issue in itself, and IMO is fine. It's just when using the image inside CI/CD pipeline can cause issues, as the registry needs to be authenticated, which means storing secrets.
This is especially problematic when using AWS CodePipeline as it shares build servers and/or IPs, and often builds fail due to rate limiting.
Solution
Publish Docker images to Amazon ECR Public registry.
Describe alternatives you've considered
N/A
Additional context

Quick start: Publishing to Amazon ECR Public using the AWS CLI
Getting Verified account badge
Amazon ECR Public registry
ECR

Who will this benefit?
Users of AWS who wish to use Docker images for dbt.
Are you interested in contributing this feature?
Maybe.

@moltar Thanks for opening, and for providing that context about the less-than-ideal interaction between DockerHub rate limiting and AWS CodePipeline.
In a couple of weeks, as part of the lead-up to v1.0, we're going to take another look at our overall distribution strategy (https://github.com/dbt-labs/dbt/issues/3361). In all likelihood, we'll start pushing a separate Docker image for each warehouse adapter that we maintain.
@kwigley and I (among other folks) are going to spend some time thinking about which image registry (or registries) makes the most sense. I don't think we're going to opt for any cloud-specific registries (Amazon ECR, GCP Container Registry, Azure Container Registry), but I can't say that for sure until we've had a chance to discuss in more detail. At the very minimum, we'd be creating a new DockerHub org named dbt-labs, and we'd stop pushing to the one named fishtownanalytics :)
I'm going to close this issue for the time being, not to say that it's a definite no, but just to say that we'll be revisiting this in a handful of weeks, and we'll be considering DockerHub's rate limiting as one consideration among many.

@jtcohen6 Thank you for your reply. Understood.
I believe it's essential to have official images at all major registries due to security concerns.
If you don't publish your own image, someone else will and that image will gain traction. It may have bugs from the image author or eventually be compromised in some way.
I understand it can be tedious to maintain support for multiple registries, but I'm sure dbt community would help.
I can certainly help with ECR.

@moltar Good points all around. Thanks again for opening, and for starting the conversation. All the more reason for us to develop a more comprehensive plan around image registries.

Might be helpful: https://github.com/xelalexv/dregsy


We can't able to integrate the uptime-kuma with mail for notification

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
We can't able to integrate the uptime-Kuma with mail notification
For username, password and hostname we have created a SES(AWS) service.
📝 Error Message(s) or Log
While testing the notification we are receiving the mails but not while the monitor is down.
🐻 Uptime-Kuma Version
1.22.1
💻 Operating System and Arch
Ubuntu
🌐 Browser
Edge
🐋 Docker Version
No response
🟩 NodeJS Version
No response

I have a few thoughts, where this might come from:

have you loooked in the spam folder
is there a ratelimit / other filter configured in SES which might block this notification
have you made shure that the notification is actually enabled on the monitor

I have a few thoughts, where this might come from:

have you loooked in the spam folder
is there a ratelimit / other filter configured in SES which might block this notification
have you made shure that the notification is actually enabled on the monitor

Thanks @CommanderStorm
We have found that the issue is with the domain.

Closing the issue