Update CONTRIBUTING.md

The existing text seemed to imply that ipairs is slower than pairs, which is not true.

Might need to improve the overall documentation but thanks anyway


git-upgrade fails if email is not set global for git

Is this a bug report?
yes
Have you read the Contributing Guidelines?
no
Environment
Environment:
OS: Linux 4.13
Node: 9.5.0
Yarn: Not Found
npm: 5.6.0
Watchman: Not Found
Xcode: N/A
Android Studio: 3.0 AI-171.4443003
Packages: (wanted => installed)
react: ^16.2.0 => 16.2.0
react-native: ^0.53.2 => 0.53.2
Steps to Reproduce

Do not setup your email for git globally
But do setup your git email for the local project
run react-native-git-upgrade

Expected Behavior
no errors
Actual Behavior
$ git commit -m "Project snapshot"
On branch master
nothing to commit, working directory clean
$ react-native-git-upgrade
git-upgrade info Check for updates
...
git-upgrade info Add all files to commit
git-upgrade info Commit current project sources

*** Please tell me who you are.
Run
git config --global user.email<EMAIL_ADDRESS>git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'locus@cobalt.(none)')
git-upgrade ERR! An error occurred during upgrade:
git-upgrade ERR! Error: Command 'git commit -m "Project snapshot"' exited with code 128:
stderr: undefined
...

If I setup my email per git config --global user.email ... there are no errors.
It seems that git runs within react-native-git-upgrade differently compared to in the shell.

This is still an issue

ok. I found out what is the problem:
react-native-git-upgrade creates a temporary git repository. Therefore the default email is used. If it is not set the described malicious behavior occurs.

We're deprecating react-native-git-upgrade in favor of react-native upgrade using https://github.com/react-native-community/rn-diff-purge/ under the hood since RN 0.59.0. Please try that :)


[CI] Edit command for saving current star count

Signed-off-by: Aadhitya A<EMAIL_ADDRESS>Description
This fixes the depreciated ENV to get star count
This PR fixes #12
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Anyone @DelusionalOptimist or @leecalcote review this PR and check if it works!


WMS service item "Near Real-Time Observations NOAA nowCOAST WMS" references service from NOAA that does not exist

WMS service item 6cc00b9f0afd4ea9ac5b859dda0fd253 "Near Real-Time Observations NOAA nowCOAST WMS" references the following URL from NOAA that does not exist:
http://nowcoast.noaa.gov/wms/com.esri.wms.Esrimap/obs
Accessing this URL generates the following error:
Not Found
The requested URL /wms/com.esri.wms.Esrimap/obs was not found on this server.

@jfrygeo - is it located here by chance?
https://nowcoast.noaa.gov/arcgis/rest/services/nowcoast

Jim,
NOAA just fielded a new nowcoast app and the urls have changed. They now have rest endpoints too. I will look to update this tomorrow.
Regards,
John
Sent from my iPhone
On Sep 28, 2015, at 5:45 PM, Jim Weakland <notifications<EMAIL_ADDRESS>wrote:
@jfrygeohttps://github.com/jfrygeo - is it located here by chance?
https://nowcoast.noaa.gov/arcgis/rest/services/nowcoast
—
Reply to this email directly or view it on GitHubhttps://github.com/Esri/ops-server-config/issues/1017#issuecomment-143894701.

Service updated to:
https://nowcoast.noaa.gov/arcgis/rest/services/nowcoast/obs_meteocean_insitu_sfc_time/MapServer
https://nsec.esri.com/arcgis/home/item.html?id=4fba403aa63b41b982c48af3043843d5


Semantic highlighting proposal

Support for https://github.com/microsoft/vscode-languageserver-node/pull/367
Tested with clangd
The main reason for the WIP status is that it depends on this pr in lsp-types. For now i have changed the path in Cargo.toml to use a local lsp-types repo, which will obviously be changed back before merging. EDIT: This has now been merged
The second point is, currently the textmate scopes are being directly translated to kakoune faces.
Since textmate scopes are heirarchical, we should have a way of defining scope -> face mappings, which would let entity.type.cpp map to the face for entity.type.

Btw, if you need any help managing issues etc, hit me up!

Btw, if you need any help managing issues etc, hit me up! I see a lots been going on lately

Yes, a lot, and at the same time, I've got much less spare resources. Your help is much appreciated!

Damn, i see i messed up the git stuff. All that effort trying to keep these two branches separated...

http://ix.io/25x2
This is the list of scopes available from eclipse.jdt.ls, and its a lot less managable than the clangd list. So we do need a scoped mapping to faces. Regarding how, on the initialized notification, the server sends a list of available scopes, and then, when the actual highlighting is sent, its just indexes into that initial list. That means, we do not need dynamic scope->face mapping, we can just map that list of scopes to a list of faces upon initialization. It also means that the splitting/lookup/matching can be done in rust, and not kakrc, which is nice.
I think having the configuration in kakrc as a str-to-str map from scope to face, is what would make the most sense. We can even have a setter for that option, which sends it to kak-lsp, and lets that remap the scopes. This also lets colorschemes define a custom mapping.

the option in kakrc turned out to be infeasable - editing it in the toml file is fine, at least for now.
Tested with clangd and eclipse.jdt.ls

Damn, i see i messed up the git stuff. All that effort trying to keep these two branches separated...

I can help to clean it up if I'll get spare time before you. It should be a checkbox somewhere allowing me to push into your branch.

I think this all works as intended now

Excellent, thank you!


net + posix: avoid host includes when building for native_sim

A corner case involving C++, posix, networking, and native_sim was causing problems.
Even though C and C++ builds should include zephyr/posix/.. in the default search path with CONFIG_POSIX_API=y, for some reason, the native compiler pulls in /usr/include first anyway.
The stat.h header pulled in <sys/types.h> (which is normally fine) but due to the native build, it was pulling in /usr/include/sys/types.h, from the host toolchain.
Explicitly include <zephyr/posix/posix_types.h> instead of <sys/types.h> from stat.h, and continue using the workarounds for native builds (explicitly including zephyr/posix/arpa/net.h etc from net/sockets.h, etc).
The workaround must be left in the tree until the deprecated option CONFIG_NET_SOCKETS_POSIX_NAMES is removed, at which point Zephyr's POSIX API will be a consumer of the network subsystem, eliminating one of the few remaining dependency cycles in Zephyr.
Fixes #75319

Thank you, I can confirm that #75319 is fixed when this PR is checked out.


Should I use the package on production?

Hi,
Thank you for another awesome package. It looks like a very interesting package.
However, it works nicely in the test environment. Don't you prefer using this in a production environment? why? or Why not?
Thank you in advance.
Anwar

I'm thinking it should work fine in production.
Personally I stick to cron for production, because cron has a proven track record. It's being used by millions and is rock solid.

Thank you for your quick reply.


Input validation for cauchy

Sam found this bug, by reading wikipedia.

Codecov Report

Merging #388 (03df214) into develop (1f27ef8) will increase coverage by 16.31%.
The diff coverage is 79.31%.

:exclamation: Current head 03df214 differs from pull request most recent head b9c8a7e. Consider uploading reports for the commit b9c8a7e to get more accurate results

@@             Coverage Diff              @@
##           develop     #388       +/-   ##
============================================
+ Coverage    39.48%   55.80%   +16.31%
============================================
  Files           24       34       +10
  Lines         1750     2215      +465
============================================
+ Hits           691     1236      +545
+ Misses        1059      979       -80

Impacted Files
Coverage Δ

...script/Distributions/SymbolicDist/SymbolicDist.res
75.29% <0.00%> (+16.66%)
:arrow_up:

...rescript/Distributions/GenericDist/GenericDist.res
74.24% <85.71%> (+16.34%)
:arrow_up:

...g/src/rescript/Distributions/DistributionTypes.res
16.94% <100.00%> (+4.88%)
:arrow_up:

...rescript/Distributions/PointSetDist/Continuous.res
50.00% <100.00%> (+10.00%)
:arrow_up:

...educer_Dispatch/Reducer_Dispatch_BuiltInMacros.res
90.00% <100.00%> (ø)

...e-lang/src/rescript/Reducer/Reducer_ErrorValue.res
62.50% <100.00%> (+62.50%)
:arrow_up:

.../Reducer/Reducer_Expression/Reducer_Expression.res
91.52% <0.00%> (ø)

...ipt/Reducer/Reducer_MathJs/Reducer_MathJs_Eval.res
100.00% <0.00%> (ø)

...pt/Reducer/Reducer_MathJs/Reducer_MathJs_Parse.res
90.62% <0.00%> (ø)

...rc/rescript/Reducer/Reducer_Js/Reducer_Js_Gate.res
100.00% <0.00%> (ø)

... and 22 more

Continue to review full report at Codecov.

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


fix(nullfilter): filters out attributes with null values

This will ignore attributes with null values on creation of impression or conversion event.

Pull Request Test Coverage Report for Build 613

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 88.98%

Totals

Change from base Build 606:
0.008%

Covered Lines:
2382

Relevant Lines:
2677

💛  - Coveralls

FYI, I ran integration tests for these changes and they passed =)


Add cicd recipe to tfengine unit tests

so it's tested by a local terraform plan. There likely is some historical reason why it's not included at this moment.

Could also look into adding it to the integration test.

Currently the integration test uses team.hcl. The cicd template in the foundation.hcl used by team.hcl is currently using github as the source repo system. That needs to be changed to cloud source repository.

Added devops to tfengine integration test and updated build configurations

Added groups to the scope of this ticket since cicd is dependent on it.
Currently, groups and cicd have been added in the fork of the repo.

Added groups and cicd to integration test; merged changes.


x1092— v2.31 As ARA (Jasmine), I want Sample Processing renamed "Labware generation", Block Processing renamed "Block", and Pot Processing renamed "Pot"

note: Katy Needs to update billing reports etc. so can we release the beginning of a month please

On the title page it still reads "Original Sample Processing" can this be changed to "Labware generation" please?

then as you select the labware to be created the comments are titled "Processing comments" could these be changes to Labware generation comments
And I spotted that the sample processing comments under the labwork> original sample has changed to Labware generation comments can these be changed back to Sample processing comments please? as these can be applied to any step in the sample processing steps

Please make any changes on a branch from the current release candidate (2.31.1) so that it can be included in the next release.


request pahe.ph bypass

Domain
https://pahe.ph/mortal-kombat-legends-battle-of-the-realms-2021/
Link
https://intercelestial.com/?id=NEtLUW9ybmRNT0t0eDU5dUhzdXVreVQvaDlvc0F0ZENOMzJvVTNHMGF1UEpYWDljWFlLQWdUeVJ4YXN4MlZkdTJHbTRZK3cxT0pobTh0NWs4QXNtbUxhQlNURVVvNHVyNWZhby9ZaG93cEE1K1RpWURjVjZUSUNKZVhBQ2Nkc3MrSFhNQk5jWUxmeVVjV2FGeHVzOU1URHV4c1d5SlJaTmVEMDJ1aEtuSUlZUERLR0RGL3FoWG9SR0piWFZkRFRvY1pJQTZ3Ukp6T055ZHpBWHVNQW9EUT09
Version
0.0.0
What browsers are you seeing the problem on?
Firefox
What OS are you seeing the problem on?
Windows
(Optional) Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Will be fixed when server is up.


UPSERT with RETURNING and WHERE condition returns non modified rows as well while scanning rows

Your Question
Hello!
Is there a way to get only modified rows back as result of Upsert query together with RETURNING clause and WHERE condition? Consider this example:
type Product struct {
	SKU     string `gorm:"primaryKey"`
	Country string `gorm:"primaryKey"`
	Price   float64
}

func (s Store) SaveProducts(ctx context.Context, products []Product) ([]Product, error) {
	if len(products) == 0 {
		return nil, nil
	}

	db := s.db.WithContext(ctx)

	op := db.Clauses(clause.OnConflict{
		Columns: []clause.Column{
			{Name: "sku"},
			{Name: "country"},
		},
		UpdateAll: true,
		Where: clause.Where{
			Exprs: []clause.Expression{
				gorm.Expr("products.price IS DISTINCT FROM EXCLUDED.price"),
			},
		},
	}, clause.Returning{}).Create(&products)
	if op.Error != nil {
		return nil, op.Error
	}

	fmt.Printf("affected rows = %d", op.RowsAffected)

	var savedProducts []Product
	rows, err := op.Rows()
	if err != nil {
		return nil, err
	}
	for rows.Next() {
		var p Product
		if err := db.ScanRows(rows, &p); err != nil {
			return nil, err
		}
		savedProducts = append(savedProducts, p)
	}

	return savedProducts, nil
}

If I'd insert one row and then try to insert exactly same row again I'd generally expect returned result to be empty on second insertion, however that is not the case because every time everything is returned regardless of whether row was updated or not.
On the other hand op.RowsAffected logs correct value always (1 and 0 in above mentioned example).

The document you expected this should be explained

Expected answer

@bedakb Yes, Even I got into this bug. Are you able to solve with any workaround for this?


Bulk actions not working in grid/tile/card view

When switching Google Drive or SharePoint to grid view (aka tiles or cards), the current selection can no longer properly be extracted from the DOM.

:tada: This issue has been resolved in version 6.12.3 :tada:
The release is available on:

GitHub release
v6.12.3

Your semantic-release bot :package::rocket:


DefaultSafe variable is incorrect in many cases

🐛 Summary
The DefaultSafe is a boolean variable in the Rego, intended to indicate whether the default value in the GWS admin center complies with the baseline. However, there are many cases where the DefaultSafe listed in the Rego is incorrect.
Cases where DefaultSafe should be set to true:

GWS.GROUPS.1.1, GWS.GROUPS.2.1, GWS.GROUPS.3.1, GWS.GROUPS.6.1
GWS.MEET.4.1, GWS.MEET.5.1
GWS.DRIVEDOCS.1.3, GWS.DRIVEDOCS.1.8, GWS.DRIVEDOCS.2.3, GWS.DRIVEDOCS.2.4, GWS.DRIVEDOCS.3.1
GWS.CLASSROOM.1.1, GWS.CLASSROOM.1.2
GWS.CHAT.1.1, GWS.CHAT.3.1
GWS.CALENDAR.1.1, GWS.CALENDAR.2.1, GWS.CALENDAR.3.1, GWS.CALENDAR.4.1
GWS.GMAIL.5.1, GWS.GMAIL.5.2, GWS.GMAIL.5.4, GWS.GMAIL.6.1, GWS.GMAIL.6.2, GWS.GMAIL.6.3, GWS.GMAIL.6.4, GWS.GMAIL.7.1, GWS.GMAIL.7.2, GWS.GMAIL.7.3, GWS.GMAIL.7.7, GWS.GMAIL.8.1, GWS.GMAIL.12.1, GWS.GMAIL.13.1, GWS.GMAIL.14.1, GWS.GMAIL.15.1
GWS.COMMONCONTROLS.5.1, GWS.COMMONCONTROLS.5.4, GWS.COMMONCONTROLS.5.5, GWS.COMMONCONTROLS.10.3, GWS.COMMONCONTROLS.11.2, GWS.COMMONCONTROLS.15.2

Cases where DefaultSafe should be set to false:

GWS.CLASSROOM.4.1
GWS.COMMONCONTROLS.12.1

To reproduce
While inside a brand new, default state GWS environment, check the default values.
Expected behavior
The DefaultState coded in the Rego to be correct in all cases.

@aormu can you create a PR for this issue


Global: collect frames to fix with settings

Changelog Description
Settings for Collect Frames to Fix will allow disable per project the plugin but also disable attribute for Rewriting version.
Testing notes:

Open settings in project_settings/global/publish/CollectFramesFixDef/enabled
Open Nuke or Maya and test all settings options in publisher and reload after each change.

the default setting should be False (Off)

This way it is backward compatible. Before it was always Enabled.

the default setting should be False (Off)

This way it is backward compatible. Before it was always Enabled.

so in Nuke you were always overwriting latest version? Sounds weird . . .

Nuke render instance is not following the settings

This is expected behavior. It will make the toggle disappear if you disable it in the settings. But I agree I should change the settings label to make it more clear.

Usual combinations work as expected, just this one with the whole creator disabled, should not propagate the children's state probably . . .

After several tests on several computers this was replicated only once and was caused due switching branches with ongoing nuke session.


Devfile test with DevConsole is failed

Which area/kind this issue is related to?
/area integration-tests
Issue Description
A recent periodic integration test for DevConsole is failed.
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-devfile-integration-tests-main-v4.8.console-e2e-gcp-console-periodic/1427963720868302848

Fixed by https://github.com/devfile/integration-tests/pull/33


Return history for entities in the order they were requested

Description:
Return history data in order
Also see home-assistant/home-assistant-polymer#3436
Related issue (if applicable): fixes home-assistant/ui-schema#213
Pull request with documentation for home-assistant.io (if applicable): N/A
Checklist:

[X] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the development checklist

No. It's not working for entity_ids=None.
 Will be fixed soon, though.

Do you think you could write a test case or 2 for the conditions if not already covered?

Fixed.
The condition I broke was already in a test, but I added one for the order of the results.
Please take an extra look on that one. I'm not comfortable with writing tests yet...

Failing test is for Python 3.5, which is to be expected.

@thomasloven you can use pytest.mark.skipif to skip if lower that 3.6.
@pytest.mark.skipif(sys.version_info < (3, 6), reason="requires python3.6 or higher")

Thanks. That gave me what I needed to find the unittest equivalent.

Ignore is no options because it's the current main version. End of the week we remove python3.5 and we don't block this PR after that.

Good point. Reverting

Py36 PR #25582


PWD env var and native pwd diverge after calling cd

> cd  # go the to home directory

> $nu.env.PWD
/home/kubouch

> pwd  # native command
/home/kubouch

> do { cd .. }

> $nu.env.PWD
/home/kubouch

> pwd
/home

@kubouch - is still broken for you with the latest e-q? I can't seem to repro

This should be fixed by the PWD scoping changes.

The only difference I see here, other than it works now, is that, on Mac:
pwd = /home/fdncred
$env.PWD = /home/fdncred/

I'm wondering if we should trim the trailing slash or not?


Refactor usage of namespaces to improve compiler performance

The compiler has been getting more and more sluggish due to some poorly scaling decisions I made back in the beginning of this project. Generally, this PR refactors the usage of namespaces as a metaphor for scopes. Previously, cloning namespaces happened to denote a new "scope". This is common when writing a compiler in a functional language with a garbage collector for a small language, and is what I learned in compilers class. Well, these namespaces are usually not modified and are cloned a lot, which means exponential memory growth and performance loss.
Overall I tried not to touch codegen since that will be improved with IR anyway -- these changes are almost entirely in the semantic analysis module.
Overview
This PR:

Modifies constant declarations to just be immutable variable declarations, although they remain more or less functionally the same
Introduces an arena which contains all modules and hands out references to those modules. Accessing a module can be done via read_module or write_module, which take a function that modifies or reads a module and the id of that module and handles it accordingly. The general idea is that while cloning namespaces is now much quicker, if you truly need to make a new scope, use create_new_scope instead of cloning the namespace.

Further Work/Drawbacks

Using an RwLock can leave us vulnerable to deadlocks. I would like to refactor this into a concurrent slab or similar, like how @canndrew did to the last RwLock-based refactoring I did. I need to learn a bit more about how to design that, though.
Trait namespaces are still pretty hard to deal with.

Closes #678

LGTM! Great work @sezna!

Will you make issues for the "further work" items?

Will you make issues for the "further work" items?

Yep I can do that now


Entries with MathJaX

Error when processing entries with MathJaX, e.g.: https://plato.stanford.edu/entries/logic-dependence/

Solved by e1ff871.


Fix "Indexer Status" table markdown formatting

Purpose of this pull request
Fix broken "Indexer Status" table markdown.


honor indentWithTabs when handling "Tab" key

The current behavior is intentionally the way it is. If you want a different behavior, simply bind Tab to something else.

Marijn,
Sorry, I'll revert the change and will try to find another way without having to modify CodeMirror core.
I just thought, that there is certain disparency:
when I use Tab key without selection - it adds one \t char which is 4 spaces.
but when I use Tab key with selection - it adds 2 space chars.
http://software-developments.com/u/150220-1752-12-125097723101278069255506862254471279130238-0_codemirror_disparency.mp4
AG
Marijn Haverbeke wrote:

The current behavior is intentionally the way it is. If you want a different behavior, simply bind Tab to something else.
—
Reply to this email directly or view it on GitHub https://github.com/codemirror/CodeMirror/pull/3094#issuecomment-75240127.

I agree there's a case to be made for the behavior you describe, but at this point I can't just change the behavior of a commonly used command out of the blue, since it would cause unexpected behavior for existing users.


Remove 'file:' functions from Lua builtins

(Original issue 482 created by None on 2010-03-12T12:50:31+00:00)
http://dev.pocoo.org/projects/pygments/browser/pygments/lexers/_luabuiltins.py lists 'file:close', 'file:flush', 'file:lines', 'file:read', 'file:seek', 'file:setvbuf', and 'file:write' as built-in functions of Lua's io library. This seems to have arisen from a misinterpretation of the [http://www.lua.org/manual/5.1/manual.html#5.7 Lua Reference Manual], which lists these functions in its section on the Input and Output Facilities for use with ''file objects'', which can have any name. For instance, if I were to say
{{{
pygments_example = io.open("example.txt")
}}}
I could then seek to a position in that file with
{{{
pygments_example:seek(20)
}}}
and, in fact, 'file' itself is not a built-in anywhere in Lua. A call to
{{{
file:close()
}}}
(without first creating a variable named "file") would result in an error for trying to index a nil value.
io.stdin, io.stdout, and io.stderr are the 3 built-in files that ''would'' work in this way: for instance, the call
{{{
io.stdout:setvbuf("no")
}}}
would be using all builtins.
Reported by guest

(Original issue was assigned to gbrandl)
(Original issue 482 last updated on 2010-03-12T19:14:20+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by gbrandl on 2010-03-12T19:14:20+00:00)
Thanks, fixed in [461a6fc5b50b].


full text pdf links fail on results page

returns page with: " The website encountered an unexpected error. Please try again later."

i've fixed the issue, by using the native php header to redirect to pdf in case user is authenticated


Add ACLs to contexts to control read-access to objects.

Another attempt at solving the problem of object access control (an alternative to #930).
This adds 3 separate but related mechanisms to object access control:

Every context (i.e. call-stack frame) gains an ACL which is a bitset indicating which objects in the host object pool the frame can access. When an object is passed from frame A to frame B (during a call) or from B to A (during a return) its corresponding access bit is set in the receiving frame -- the idea being that if you pass someone an object, you intend for them to be able to read it!
The set of objects in the host is split in two separate vectors: one behaving as before, and a new one called "system objects". Object references now come in two flavors depending on their low bit: 1 means system objects and 0 means user objects. The VM marshalling path is modified to check that system object handles are never returned to users (by accident) and if a user tries to forge one it won't work anyway (unless they can figure out a way to feed it into code running in system mode, which should not exist).
The host gains a new boolean flag indicating whether it's running in "system mode", which grants two privileges: access to system objects, and ignoring the context's ACL when looking at non-system objects. Only the auth and event subsystems run in system mode -- there are explicit short-lived transitions into it in a few places, easy to grep for.

The first mechanism (ACLs) broadly isolates objects belonging to each contract from one another. The second mechanism (system objects) lets two subsystems of the host -- auth and events -- freely allocate "their own" objects without perturbing object numbers seen by users and without worrying if they can be seen from the current context. The final mechanism (system mode) allows those subsystems to access system objects from any context, as well as access user objects (eg. for recording objects into the event buffer or authentication trees).
When the auth system calls contracts back for custom auth logic, it transitions back from system to user, and copies the objects of interest from the system table to the object table. Not ideal, but it works.
This is not 100% perfect isolation: there is still a covert channel observable in the allocation of objects. Namely if contract A calls contract B, after B returns A can tell how many objects B allocated by looking at the next available object number. This might be enough to leak information about behaviour B wanted to keep secret. I have an idea of how to close this channel also (changing the system/user split to a global/local split and replacing the ACL with a per-contract indirection table) but that'll take a bit more time. This at least "works" and closes the most egregious channel.
(There are no tests yet, I'm still trying to figure out if this is even the right / final approach to settle on)

closing in favor of https://github.com/stellar/rs-soroban-env/pull/947


I added all the operators that malfunction supports.

I added all the operators that malfunction supports.
Unfortunately, trying to use xor operator results in segmentation fault.
module Main

import Data.Bits

main : IO ()
main = do printLn (xor (MkBits {n=64} 7) (MkBits {n=64} 45))
          pure ()

Gdb reports this:
Program received signal SIGSEGV, Segmentation fault.
0x0000000000404c5e in camlIdris_malfunction_output__Data$2eBits$2ebitAt_4084 () at pervasives.ml:32
32      pervasives.ml: No such file or directory.

The problem is the two FIXMEs in CodegenMalfunction.hs, which implement the sign-extension and truncation primitives as no-ops. Since bigints that happen to be small are represented the same way as plain ints, this sorta-kinda-works for int to bigint conversions, but is totally wrong for int to int64 conversions (in the OCaml runtime system, int64s are always boxed).
Your commit looks good, but I'll hold off merging it until I expose integer conversions in Malfunction, which are needed to do this correctly.

As soon as I have the time, I will try to update this to the new syntax.

There are remaining problems in this pull request.

Fixed length integers are treated as unsigned in Idris.
The shift operators in Idris does not take 'int' in the second argument like shift_left of Ocaml.

There  might be other problems as well.


[AIRFLOW-3276] Cloud SQL: database create / patch / delete operators

Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Adding 3 new operators to communicate with Google Cloud Platform's Cloud SQL database resources:

CloudSqlInstanceDatabaseCreateOperator
Creates a new database inside a Cloud SQL instance.

CloudSqlInstanceDatabasePatchOperator
Updates a resource containing information about a database inside a Cloud SQL instance using patch semantics.

CloudSqlInstanceDatabaseDeleteOperator
Deletes a database from a Cloud SQL instance.

Tests

[x] My PR adds the following unit tests:
test_gcp_sql_operator.py

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes flake8

Thanks @sprzedwojski


Performance Degradation in stable_diffusion_cpp_python Compared to stable-diffusion.cpp

I've observed performance degradation in stable_diffusion_cpp_python compared to the base stable-diffusion.cpp implementation. The slowdown is particularly noticeable when using AMD Radeon GPUs, with execution times being up to 15x slower in some cases.
Environment

OS: Windows 11 (10.0.22631)
RAM: 32GB
CPU: AMD Ryzen 5 5600X 6-Core Processor
GPU: AMD Radeon RX 7600 XT (16GB)
HIP SDK 5.5.1 (for GPU tests)

Benchmark Results
Timing information was extracted from logs showing messages like:
[INFO ] stable-diffusion.cpp:1449 - txt2img completed in 23.69s

Configuration
stable-diffusion.cpp
stable_diffusion_cpp_python
Slowdown Factor

no option (CPU)
324.25s
426.17s
~1.31x

HIP (GPU)
23.69s
353.27s
~14.91x

HIP configuration: https://github.com/william-murray1204/stable-diffusion-cpp-python/issues/5
CMAKE_ARGS=-G Ninja -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DSD_HIPBLAS=ON -DCMAKE_BUILD_TYPE=Release -DAMDGPU_TARGETS=gfx1102

stable-diffusion.cpp Command
sd --diffusion-model ../models/flux1-schnell-q3_k.gguf --clip_l ../models/clip_l.safetensors --t5xxl ../models/t5xxl_fp16.safetensors --vae ../models/ae.safetensors -p "a lovely cat holding a sign says 'flux.cpp'" --steps 4 --cfg-scale 1.0 --sampling-method euler

stable_diffusion_cpp_python Code
Using the FLUX.1 sample from README.md:
from stable_diffusion_cpp import StableDiffusion

stable_diffusion = StableDiffusion(
    diffusion_model_path="../models/flux1-schnell-q3_k.gguf", # In place of model_path
    clip_l_path="../models/clip_l.safetensors",
    t5xxl_path="../models/t5xxl_fp16.safetensors",
    vae_path="../models/ae.safetensors",
)
output = stable_diffusion.txt_to_img(
      prompt="a lovely cat holding a sign says 'flux.cpp'",
      sample_steps=4,
      cfg_scale=1.0, # a cfg_scale of 1 is recommended for FLUX
      sample_method="euler", # euler is recommended for FLUX
)

Hi @william-murray1204, thank you for the quick fix! The performance is now on par with stable-diffusion.cpp, which is fantastic.
I wanted to express my deep gratitude for this project. While stable-diffusion.cpp requires launching a new process for each generation, meaning model reloading every time, which was a significant overhead. With stable_diffusion_cpp_python, I can now load the models just once and experiment with various prompts efficiently. Your project has made stable-diffusion.cpp truly practical for real-world use cases.
For example, I can now easily try multiple prompts in a loop like this:
prompts = [
    ("flux1-cat.png", "a lovely cat holding a sign says 'flux.cpp'"),
    ("flux1-dog.png", "a lovely dog holding a sign says 'flux.cpp'"),
]

for fn, prompt in prompts:
    output = stable_diffusion.txt_to_img(
        prompt=prompt,
        sample_steps=4,
        cfg_scale=1.0,
        sample_method="euler",
    )
    output[0].save(fn)

Thank you for your outstanding work on this project. It has genuinely enhanced the usability of stable-diffusion.cpp!


Add theme to place anchor inside of the tab

The problem
As a user I want to place the anchor inside of the tab and make it to occupy the full height and width. This is now impossible because of the padding
Solution
Add theme="link" similar to what paper-tab does with the attribute.

BTW, another possible feature here would be also to also forward click events which paper-tab does here, so the links would be accessible from the keyboard.

I think the best option is to wrap the tab with the anchor. Like #71.
More references:

https://github.com/PolymerElements/paper-tabs/issues/155
https://github.com/PolymerElements/iron-elements/issues/37

@abdonrd I remember that use case as well, IMO it would make sense to maintain both.

I agree with @abdonrd, what is the advantage of having the anchor inside the tab? What if I place two anchors inside a tab, one to activate the tab and one for another action?
Another solution could be using vaadin-link-tab element, which itself wraps an anchor in its shadow root.

I'm not a Polymer expert, but could this work: <a href="tab1" is="vaadin-tab">?

Any news here? Thanks in advance!

I'm currently using link in tabs without issues with this custom theme:
<dom-module id="vaadin-tab-link-theme" theme-for="vaadin-tab">
  <template>
    <style>
      :host ::slotted(a) {
        display: flex;
        align-items: center;
        width: calc(100% + 2em);
        height: 100%;
        margin: -.25em -1em;
        padding: .25em 1em;
        text-decoration: none;
        color: inherit !important;
        outline: none;
      }

      :host ::slotted(a:hover) {
        text-decoration: none !important;
      }

      :host ::slotted(a) > iron-icon {
        margin: 0 4px;
      }

      :host ::slotted(a) > iron-icon:first-child {
        margin-left: 0;
      }

      :host ::slotted(a) > iron-icon:last-child {
        margin-right: 0;
      }

      :host([theme~="icon-on-top"]) ::slotted(a) {
        display: flex;
        flex-direction: column;
        align-items: center;
        text-align: center;
      }

      :host([theme~="icon-on-top"]) ::slotted(a) > iron-icon {
        margin: 0;
      }
    </style>
  </template>
</dom-module>

I can submit a PR with this added to the core tab theme.

This is also something that Flow users need when they are using vaadin-tabs as a navigation menu, as there should be anchors inside the tabs that trigger the navigation.


Add new server: Schooldays.club (LVS on top)

Hi, this guy is trying to steal my domain, im the owner of schooldays.club.
If you don't do anything I will have to file a legal claim.

Hi, this guy is trying to steal my domain, im the owner of schooldays.club. If you don't do anything I will have to file a legal claim.

Registering a server that is not yours and you don't know how to register it LOL

chispero you are registering a server that is not yours, man, how bored must you be?


Picture is required error

My problem is that I want to be able to upload a picture, but when required: true in the post settings, I get the required error. What do I need to do to be able to upload a picture?

Confirm: picture upload does not work.

Same here when using a fresh meteor-starter install (imagemagic & graphicsmagick installed).

Doesn't work yet.


(feature request) proper save support

pretty much as title says; proper save support would be pretty cool i think,,,.. had a run crash on me and was sad to see my mountain shrines gone ,.,.,.,.,..,

implemented in latest update 🙂


[ENHANCEMENT] Changing storage network setting needs to consider user workload

Is your enhancement related to a problem? Please describe.

We prohibit setting storage network settings when there is a running VM (code).
We should also consider user workloads in v1.2.0.
Describe the solution you'd like

Check if there are any non-system attached volumes.
Describe alternatives you've considered

Additional context

Tested on Harvester v1.2.0-rc3
This looks good :smile: :+1: , opened up #4217 - for an item discovered.
Thanks @WebberHuang1118

Was able to see the ds/harvester-network-controller on harvester-system logs generate:
I0710 21:31:42.777306       1 controller.go:46] nad configuration harvester-system/storagenetwork-2f52q has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:42.789690       1 controller.go:46] nad configuration harvester-system/storagenetwork-spg8p has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:42.796663       1 controller.go:46] nad configuration harvester-system/storagenetwork-2f52q has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:42.809388       1 controller.go:46] nad configuration harvester-system/storagenetwork-d6jcb has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:42.814213       1 controller.go:46] nad configuration harvester-system/storagenetwork-spg8p has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:42.819556       1 controller.go:46] nad configuration harvester-system/storagenetwork-spg8p has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:42.826371       1 controller.go:46] nad configuration harvester-system/storagenetwork-d6jcb has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:42.879286       1 controller.go:46] nad configuration harvester-system/storagenetwork-2f52q has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:42.886538       1 controller.go:46] nad configuration harvester-system/storagenetwork-spg8p has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:43.061858       1 controller.go:46] nad configuration harvester-system/storagenetwork-d6jcb has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:43.204235       1 controller.go:46] nad configuration harvester-system/storagenetwork-2f52q has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:43.600074       1 controller.go:46] nad configuration harvester-system/storagenetwork-spg8p has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:31:43.797301       1 controller.go:46] nad configuration harvester-system/storagenetwork-d6jcb has been changed: {"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"additional-br","promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24","exclude":["<IP_ADDRESS>/24","<IP_ADDRESS>/24"]}}
I0710 21:32:19.871358       1 controller.go:104] lm additional matches node harvester-node-0

And also the addition of the network-attachment-definitions when the Storage Network setting was activated:
╭─mike at suse-workstation-team-harvester in ~/Projects/test_3867
╰─○ kubectl get network-attachment-definitions -n harvester-system -o wide
NAME                   AGE
storagenetwork-2f52q   76m
storagenetwork-d6jcb   76m
storagenetwork-spg8p   76m

And additionally spun up some VMs to test.
So I feel like this looks good and we can go ahead and close this out :+1: :smile:

@WebberHuang1118
validation questions:
Wanted to re-open this briefly for a few questions:

When Nodes get removed from the cluster do the storagenetwork-* network-attachment definitions get cleaned up?

As it looks like if you have a Harvester cluster of "N" nodes, there are then N storagenetwork- network-attachment-definitions under harvester-system that get built.
And it looks as if Longhorn, can only ever support "one" NAD at a time - does that end up getting updated by the controller when:
a. the network-attachment-definition was removed / cleaned up?

I'm guessing that it doesn't?
╭─mike at suse-workstation-team-harvester in ~/Projects/test_3867
╰─○ kubectl logs ds/harvester-whereabouts -n kube-system --follow
Done configuring CNI.  Sleep=false
2023-07-11T00:10:00Z [verbose] pod controller created
2023-07-11T00:10:00Z [verbose] Starting informer factories ...
2023-07-11T00:10:00Z [verbose] Informer factories started
2023-07-11T00:10:00Z [verbose] starting network controller
W0711 00:10:31.042727      24 reflector.go:324] github.com/k8snetworkplumbingwg/network-attachment-definition-client/pkg/client/informers/externalversions/factory.go:117: failed to list *v1.NetworkAttachmentDefinition: Get "https://<IP_ADDRESS>:443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout
I0711 00:10:31.042824      24 trace.go:205] Trace[1298498081]: "Reflector ListAndWatch" name:github.com/k8snetworkplumbingwg/network-attachment-definition-client/pkg/client/informers/externalversions/factory.go:117 (11-Jul-2023 00:10:00.944) (total time: 30098ms):
Trace[1298498081]: ---"Objects listed" error:Get "https://<IP_ADDRESS>:443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout 30098ms (00:10:31.042)
Trace[1298498081]: [30.098550283s] [30.098550283s] END
E0711 00:10:31.042835      24 reflector.go:138] github.com/k8snetworkplumbingwg/network-attachment-definition-client/pkg/client/informers/externalversions/factory.go:117: Failed to watch *v1.NetworkAttachmentDefinition: failed to list *v1.NetworkAttachmentDefinition: Get "https://<IP_ADDRESS>:443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout
W0711 00:10:31.042916      24 reflector.go:324] github.com/k8snetworkplumbingwg/whereabouts/pkg/client/informers/externalversions/factory.go:116: failed to list *v1alpha1.IPPool: Get "https://<IP_ADDRESS>:443/apis/whereabouts.cni.cncf.io/v1alpha1/ippools?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout
I0711 00:10:31.042943      24 trace.go:205] Trace[1427131847]: "Reflector ListAndWatch" name:github.com/k8snetworkplumbingwg/whereabouts/pkg/client/informers/externalversions/factory.go:116 (11-Jul-2023 00:10:01.041) (total time: 30001ms):
Trace[1427131847]: ---"Objects listed" error:Get "https://<IP_ADDRESS>:443/apis/whereabouts.cni.cncf.io/v1alpha1/ippools?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout 30001ms (00:10:31.042)
Trace[1427131847]: [30.001205826s] [30.001205826s] END
E0711 00:10:31.042947      24 reflector.go:138] github.com/k8snetworkplumbingwg/whereabouts/pkg/client/informers/externalversions/factory.go:116: Failed to watch *v1alpha1.IPPool: failed to list *v1alpha1.IPPool: Get "https://<IP_ADDRESS>:443/apis/whereabouts.cni.cncf.io/v1alpha1/ippools?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout
W0711 00:10:31.042946      24 reflector.go:324] k8s.io/client-go/informers/factory.go:134: failed to list *v1.Pod: Get "https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dharvester-node-1&limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout
I0711 00:10:31.042984      24 trace.go:205] Trace[939984059]: "Reflector ListAndWatch" name:k8s.io/client-go/informers/factory.go:134 (11-Jul-2023 00:10:00.944) (total time: 30098ms):
Trace[939984059]: ---"Objects listed" error:Get "https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dharvester-node-1&limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout 30098ms (00:10:31.042)
Trace[939984059]: [30.098648255s] [30.098648255s] END
E0711 00:10:31.042989      24 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Pod: failed to list *v1.Pod: Get "https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%3Dharvester-node-1&limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: i/o timeout
2023-07-11T00:24:40Z [verbose] deleted pod [longhorn-system/instance-manager-r-0d0d6e92babb7a1b77ea903a844de23d]
2023-07-11T00:24:40Z [verbose] skipped net-attach-def for default network
2023-07-11T00:24:40Z [verbose] result of garbage collecting pods: <nil>
2023-07-11T00:24:40Z [verbose] deleted pod [longhorn-system/instance-manager-e-0d0d6e92babb7a1b77ea903a844de23d]
2023-07-11T00:24:40Z [verbose] skipped net-attach-def for default network
2023-07-11T00:24:40Z [verbose] result of garbage collecting pods: <nil>
2023-07-11T00:25:21Z [verbose] deleted pod [cattle-system/apply-sync-additional-ca-on-harvester-node-1-with-2c27af4-swc7j]
2023-07-11T00:25:21Z [verbose] result of garbage collecting pods: <nil>
2023-07-11T00:25:23Z [verbose] deleted pod [cattle-system/apply-sync-containerd-registry-on-harvester-node-1-with-4-w6d9x]
2023-07-11T00:25:23Z [verbose] result of garbage collecting pods: <nil>
2023-07-11T00:25:31Z [verbose] deleted pod [cattle-system/apply-system-agent-upgrader-on-harvester-node-1-with-995f-pzjzf]
2023-07-11T00:25:31Z [verbose] result of garbage collecting pods: <nil>
error: stream error: stream ID 5; INTERNAL_ERROR; received from peer
╭─mike at suse-workstation-team-harvester in ~/Projects/test_3867
╰─○ kubectl get nodes
NAME               STATUS   ROLES                       AGE   VERSION
harvester-node-1   Ready    control-plane,etcd,master   35m   v1.25.9+rke2r1
╭─mike at suse-workstation-team-harvester in ~/Projects/test_3867
╰─○ kubectl get network-attachment-definitions -n harvester-system -o wide
NAME                   AGE
storagenetwork-5lcw2   20m
storagenetwork-cpnkj   20m

If you then go modify the storage-network setting to let's say "add" an IPv4 exclusion the logs fire off as:
2023-07-11T00:48:19Z [verbose] skipped net-attach-def for default network
2023-07-11T00:48:19Z [debug] pod's network status: {Name:harvester-system/storagenetwork-cpnkj Interface:lhnet1 IPs:[<IP_ADDRESS>] Mac:c6:c2:c8:c1:6e:73 Default:false DNS:{Nameservers:[] Domain: Search:[] Options:[]} DeviceInfo:<nil>}
2023-07-11T00:48:19Z [verbose] result of garbage collecting pods: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:19Z [verbose] re-queuing IP address reconciliation request for pod longhorn-system/instance-manager-e-0d0d6e92babb7a1b77ea903a844de23d; retry #: 0
2023-07-11T00:48:19Z [verbose] skipped net-attach-def for default network
2023-07-11T00:48:19Z [debug] pod's network status: {Name:harvester-system/storagenetwork-cpnkj Interface:lhnet1 IPs:[<IP_ADDRESS>] Mac:c6:c2:c8:c1:6e:73 Default:false DNS:{Nameservers:[] Domain: Search:[] Options:[]} DeviceInfo:<nil>}
2023-07-11T00:48:19Z [verbose] result of garbage collecting pods: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:19Z [verbose] re-queuing IP address reconciliation request for pod longhorn-system/instance-manager-e-0d0d6e92babb7a1b77ea903a844de23d; retry #: 1
2023-07-11T00:48:19Z [verbose] skipped net-attach-def for default network
2023-07-11T00:48:19Z [debug] pod's network status: {Name:harvester-system/storagenetwork-cpnkj Interface:lhnet1 IPs:[<IP_ADDRESS>] Mac:c6:c2:c8:c1:6e:73 Default:false DNS:{Nameservers:[] Domain: Search:[] Options:[]} DeviceInfo:<nil>}
2023-07-11T00:48:19Z [verbose] result of garbage collecting pods: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:19Z [verbose] re-queuing IP address reconciliation request for pod longhorn-system/instance-manager-e-0d0d6e92babb7a1b77ea903a844de23d; retry #: 2
2023-07-11T00:48:19Z [verbose] skipped net-attach-def for default network
2023-07-11T00:48:19Z [debug] pod's network status: {Name:harvester-system/storagenetwork-cpnkj Interface:lhnet1 IPs:[<IP_ADDRESS>] Mac:c6:c2:c8:c1:6e:73 Default:false DNS:{Nameservers:[] Domain: Search:[] Options:[]} DeviceInfo:<nil>}
2023-07-11T00:48:19Z [verbose] result of garbage collecting pods: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:19Z [error] dropping pod [longhorn-system/instance-manager-e-0d0d6e92babb7a1b77ea903a844de23d] deletion out of the queue - could not reconcile IP: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:19Z [verbose] Event(v1.ObjectReference{Kind:"Pod", Namespace:"longhorn-system", Name:"instance-manager-e-0d0d6e92babb7a1b77ea903a844de23d", UID:"f16fc73b-cdce-462a-9b0b-0c462d8c3f50", APIVersion:"v1", ResourceVersion:"49695", FieldPath:""}): type: 'Warning' reason: 'IPAddressGarbageCollectionFailed' failed to garbage collect addresses for pod longhorn-system/instance-manager-e-0d0d6e92babb7a1b77ea903a844de23d
2023-07-11T00:48:20Z [verbose] deleted pod [longhorn-system/instance-manager-r-0d0d6e92babb7a1b77ea903a844de23d]
2023-07-11T00:48:20Z [verbose] skipped net-attach-def for default network
2023-07-11T00:48:20Z [debug] pod's network status: {Name:harvester-system/storagenetwork-cpnkj Interface:lhnet1 IPs:[<IP_ADDRESS>] Mac:5e:de:b2:de:49:2f Default:false DNS:{Nameservers:[] Domain: Search:[] Options:[]} DeviceInfo:<nil>}
2023-07-11T00:48:20Z [verbose] result of garbage collecting pods: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:20Z [verbose] re-queuing IP address reconciliation request for pod longhorn-system/instance-manager-r-0d0d6e92babb7a1b77ea903a844de23d; retry #: 0
2023-07-11T00:48:20Z [verbose] skipped net-attach-def for default network
2023-07-11T00:48:20Z [debug] pod's network status: {Name:harvester-system/storagenetwork-cpnkj Interface:lhnet1 IPs:[<IP_ADDRESS>] Mac:5e:de:b2:de:49:2f Default:false DNS:{Nameservers:[] Domain: Search:[] Options:[]} DeviceInfo:<nil>}
2023-07-11T00:48:20Z [verbose] result of garbage collecting pods: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:20Z [verbose] re-queuing IP address reconciliation request for pod longhorn-system/instance-manager-r-0d0d6e92babb7a1b77ea903a844de23d; retry #: 1
2023-07-11T00:48:20Z [verbose] skipped net-attach-def for default network
2023-07-11T00:48:20Z [debug] pod's network status: {Name:harvester-system/storagenetwork-cpnkj Interface:lhnet1 IPs:[<IP_ADDRESS>] Mac:5e:de:b2:de:49:2f Default:false DNS:{Nameservers:[] Domain: Search:[] Options:[]} DeviceInfo:<nil>}
2023-07-11T00:48:20Z [verbose] result of garbage collecting pods: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:20Z [verbose] re-queuing IP address reconciliation request for pod longhorn-system/instance-manager-r-0d0d6e92babb7a1b77ea903a844de23d; retry #: 2
2023-07-11T00:48:20Z [verbose] skipped net-attach-def for default network
2023-07-11T00:48:20Z [debug] pod's network status: {Name:harvester-system/storagenetwork-cpnkj Interface:lhnet1 IPs:[<IP_ADDRESS>] Mac:5e:de:b2:de:49:2f Default:false DNS:{Nameservers:[] Domain: Search:[] Options:[]} DeviceInfo:<nil>}
2023-07-11T00:48:20Z [verbose] result of garbage collecting pods: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:20Z [error] dropping pod [longhorn-system/instance-manager-r-0d0d6e92babb7a1b77ea903a844de23d] deletion out of the queue - could not reconcile IP: failed to get network-attachment-definition for iface harvester-system/storagenetwork-cpnkj: networkattachmentdefinition.k8s.cni.cncf.io "storagenetwork-cpnkj" not found
2023-07-11T00:48:20Z [verbose] Event(v1.ObjectReference{Kind:"Pod", Namespace:"longhorn-system", Name:"instance-manager-r-0d0d6e92babb7a1b77ea903a844de23d", UID:"3345a89f-5d36-41c8-a46d-bd8f7a61fdf8", APIVersion:"v1", ResourceVersion:"49742", FieldPath:""}): type: 'Warning' reason: 'IPAddressGarbageCollectionFailed' failed to garbage collect addresses for pod longhorn-system/instance-manager-r-0d0d6e92babb7a1b77ea903a844de23d

But it seems to have done some cleanup?
It went from:
╭─mike at suse-workstation-team-harvester in ~/Projects/test_3867
╰─○ kubectl get network-attachment-definitions -n harvester-system -o wide
NAME                   AGE
storagenetwork-5lcw2   22m
storagenetwork-cpnkj   22m

To:
╭─mike at suse-workstation-team-harvester in ~/Projects/test_3867
╰─○ kubectl get network-attachment-definitions -n harvester-system -o wide
NAME                   AGE
storagenetwork-5lcw2   24m
storagenetwork-5wrs2   80s
storagenetwork-b5pcw   80s

In the Embedded Longhorn - Storage Network, it seems to have updated the NAD to:
storagenetwork-5wrs2

Previously in Embedded Longhorn - Storage Network, it was:
storagenetwork-cpnkj

@WebberHuang1118 is this behavior normal? :thinking:
I'm willing to close this out if:

it's typical that a cluster of 9 nodes for instance, will have 9 NADs created, and that when the nodes get removed from the cluster it is typical to not have any of the NADs deleted
it's typical, that the only time NADs will get cleaned up is when someone is modifying / updating the storage-network setting in harvester

@irishgordo
Longhron only requires one NAD for Storge-Network, the creation of multiple NADs seems an issue. I have created ticket #4226 for tracking.
Since the multiple NADs issue is not related to this ticket, I suggest closing this one. Thanks.

@WebberHuang1118 thanks for opening that up :smile:  - in that case I'll go ahead and close this out :+1:


Added the Weatherbit API.

Added under Weather header. Thought it would be appropriate to list here!
Thanks.

Thanks!


StreamWriter should support insert picture 不支持图片写入

StreamWriter 不支持图片写入

This issue was duplicated with #1194. I will close this issue and move on to discuss #1194.


Docs: Updating 'Developing in Go'

These updates are based on my experience using the Go documentation.
Changes are based on issues with the following topics:

Minimum golang version requirement
Change in Run function signature
Change in test data structure
Missing Dockerfile

Thanks for the fixes @abangser. It looks great!
Just FYI, I'm working on rewriting the "Develping in Go", which uses the latest examples, added many sample code snippets for different method usage and introduces a SDK mini CLI (no Dockerfile is needed).


Update README.md

Fixes up some typos and grammar mistakes.
At Ritza.co we love helping technical companies like Snowflake produce documentation, guides, ebooks and other technical resources. Please let me know if you need any help in creating SF Quickstarts or any other materials!

Thank you for your contribution!


Refactor non-localizable data out of localized pages.

The GPG key in the security page should be identical across languages, so it now includes a copy of the existing key file.
Liquid seems to require the included file to be in _includes, so the copy was necessary---the symlink also works but was avoided to avoid possible platform issues (not to say that the current website builds everywhere though).

Almost all data in the team page has been moved to _data. Previously translated pages have been retrofitted to use a saner localization mechanism (modelled after what ko-KR was using).
This should fix the absence of withoutboats except for en-US ;)

r? @nikomatsakis
(rust_highfive has picked a reviewer for you, use r? to override)

Awesome, thanks!


feature request(hardlinking): Automagically hardlink to differing partition/disk/mount

Hardlinking seems like the most preferred linking solution, and indeed, https://github.com/cross-seed/cross-seed/pull/619 seeks to set hardlinking as the default.
Currently only one linkDir: is allowed to be set, resulting in what would appear to be non-optimal outcomes for those who have media files spread across different partition/disk/mount.
The most ideal solution, for us dumb users, would seem to allow multiple entries within linkDir:, where the user can set the directories for each partition/disk/mount, and xseed automagically uses the appropriate directory when linking.

@Audionut just to confirm you want something like:
["/datadir1" => "/linkdir1"]
["/datadir2" => "/linkdir2"]

this is kind of solve by mergefs, but might make sense for some cases

mergefs would appear to be unix only.
"/datadir1" => "/linkdir1" would undoubtedly work, however in cases with many data directories residing on the one partition, it would seem to be excessive config.
A cleaner solution, IMO:
linkDir: ["a:\\linked", "b:\\linked", "c:\\linked",] with xseed automagically linking the data match from the relevant datadir to the correct linkDir.

mergefs would appear to be unix only.
"/datadir1" => "/linkdir1" would undoubtedly work, however in cases with many data directories residing on the one partition, it would seem to be excessive config.
A cleaner solution, IMO: linkDir: ["a:\\linked", "b:\\linked", "c:\\linked",] with xseed automagically linking the data match from the relevant datadir to the correct linkDir.

there are 2 things:

linkdir from torrents (I assume you have only single mount there), otherwise it will be hard to do linking
linkdir for data. So data should contains its map:

["/linkdir1" => "/datadir1/tv", "/linkdir1/movies"]
["/linkdir2" => "/datadir2/tv", "/linkdir2/movies"]

there are 2 things:
1. linkdir from torrents (I assume you have only single mount there), otherwise it will be hard to do linking

2. linkdir for data. So data should contains its map:

Don't understand 1, as linking only works with data matching.
2 is good, although it would ideally parse the data directories only from the linkdir: config, if enabled, and ignore datadir:
So instead of adding directories to datadir: and linkdir:, with linking enabled, the directories would only need to be added to linkdir:.
Fuse system makes sense, and if that does indeed work, it would seem the logical solution. I'll have to edumacate myself though, as I don't understand how a single directory in the xseed config and storage pool, automagically creates the link on the correct disk.

Well, it would be the same way that cross seed would do it.
This seems like a pretty niche feature, so unless we see a swarm of demand for it, we probably won't implement it anytime soon . I would look at solutions for running a single file system on multiple disks, or running multiple instances of cross seed.

I was totally missing that point that everything is in the same mount, so of course the hard link would work within the mount, regardless of the underlying drive structure.

there are 2 things:
1. linkdir from torrents (I assume you have only single mount there), otherwise it will be hard to do linking

2. linkdir for data. So data should contains its map:

Don't understand 1, as linking only works with data matching.

This will change with v6, as torrent-based linking has been implemented if appropriately configured

2 is good, although it would ideally parse the data directories only from the linkdir: config, if enabled, and ignore datadir:
So instead of adding directories to datadir: and linkdir:, with linking enabled, the directories would only need to be added to linkdir:.
Fuse system makes sense, and if that does indeed work, it would seem the logical solution. I'll have to edumacate myself though, as I don't understand how a single directory in the xseed config and storage pool, automagically creates the link on the correct disk.

This is how unraid operates, and I believe even mergerfs works in this manner. This is the general consensus on how to accomplish this currently. It requires some reading and understanding of the implementation, but isn't overly complex.
I don't think someone's unwillingness and laziness to get their system configured in a way that accomplishes their desires is necessarily something we should just "solve" for them. It's not a small task, but it's not like a huge hurdle for the user. Spend a few hours and you can have it up rather easily without us "doing it for them" - just my thoughts though.
I don't mean to sound like I'm attacking, but there are solutions to this issue, and the implementation isn't something we necessarily have to prioritize to accommodate people who don't want to bother with getting their system setup in a way to facilitate the optimal setup.


[plot] Log colormap with bound <= 1: changing bounds

On unittests, we have a spam of warning concerning the ColorBar.
I am quite sure, all this logs do not come from tests of the ColorBar.
Then it looks to be a common case (and it would be nice to not spam warnings), or there is a wrong assertion somewhere.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
.WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
.WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
.WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
.WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.
WARNING:silx.gui.plot.ColorBar:Log colormap with bound <= 1: changing bounds.

Looks to be fixed


Count start from 0 due to heroku free plan will sleep the app

Since current app is deployed on heroku free plan , if no request in 1 hour, the app will be sleeped.
All the cached count will be lost and start over from 0 again.
Need to persist the count instead of cache in memory.

Fixed by integrate with postgresql to persit the visitor count info into database


Environment configuration issue

Dear Dr. Zeng,
I have some code problems. Very disturbing! Thank you very much!
I run this project in ubuntu18.04 and install required packages in python3.7. Is the following error caused by matplotlib's version?
The PostScript backend does not support transparency; partially transparent artists will be rendered opaque.
Traceback (most recent call last):
File "/home/highlight/cbf/models/kinematic_car_test.py", line 344, in
kinematic_car_all_shapes_simulation_test(maze_type, robot_shape)
File "/home/highlight/cbf/models/kinematic_car_test.py", line 257, in kinematic_car_all_shapes_simulation_test
plot_world(sim, robot_indexes, figure_name=name, local_traj_indexes=traj_indexes, maze_type=maze_type)
File "/home/highlight/cbf/models/kinematic_car_test.py", line 83, in plot_world
plt.savefig("figures/" + figure_name + ".eps", format="eps", dpi=500, pad_inches=0)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/pyplot.py", line 977, in savefig
res = fig.savefig(*args, **kwargs)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/figure.py", line 3058, in savefig
self.canvas.print_figure(fname, **kwargs)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/backend_bases.py", line 2325, in print_figure
**kwargs)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/_api/deprecation.py", line 415, in wrapper
return func(*inner_args, **inner_kwargs)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/backends/backend_ps.py", line 847, in print_eps
return self._print_ps(outfile, 'eps', **kwargs)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/_api/deprecation.py", line 389, in wrapper
return func(*inner_args, **inner_kwargs)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/backends/backend_ps.py", line 889, in _print_ps
orientation=orientation, papertype=papertype, **kwargs)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/backend_bases.py", line 1648, in wrapper
return func(*args, **kwargs)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/backends/backend_ps.py", line 1024, in _print_figure
with cbook.open_file_cm(outfile, "w", encoding="latin-1") as file:
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/cbook/init.py", line 465, in open_file_cm
fh, opened = to_filehandle(path_or_file, mode, True, encoding)
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/cbook/init.py", line 451, in to_filehandle
fh = open(fname, flag, encoding=encoding)
FileNotFoundError: [Errno 2] No such file or directory: 'figures/triangle_maze.eps'

Hi @AkshayThiru, would you mind having some quick check on it when you are available?

Hi @Highlight123, can you let us know if you are running the code from the root directory or the repo directory? I think that if you run it from the repo directory you will not have any errors.

Thank you for help! Working directory has been set to the repo directory(/home/highlight/cbf). I can achieve triangle_maze.eps and triangle_maze.png. But still come across error:
Traceback (most recent call last):
File "/home/highlight/cbf/models/kinematic_car_test.py", line 344, in
kinematic_car_all_shapes_simulation_test(maze_type, robot_shape)
File "/home/highlight/cbf/models/kinematic_car_test.py", line 258, in kinematic_car_all_shapes_simulation_test
animate_world(sim, animation_name=name, maze_type=maze_type)
File "/home/highlight/cbf/models/kinematic_car_test.py", line 137, in animate_world
anim.save("animations/" + animation_name + ".mp4", dpi=300, writer=animation.writers"ffmpeg")
File "/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/animation.py", line 151, in getitem
raise RuntimeError(f"Requested MovieWriter ({name}) not available")
RuntimeError: Requested MovieWriter (ffmpeg) not available
/home/highlight/anaconda3/envs/cbf/lib/python3.7/site-packages/matplotlib/animation.py:888: UserWarning: Animation was deleted without rendering anything. This is most likely not intended. To prevent deletion, assign the Animation to a variable, e.g. anim, that exists until you have outputted the Animation using plt.show() or anim.save().
'Animation was deleted without rendering anything. This is '

Thank you for help! I run again in the repo directory(/home/highlight/cbf) on another computer and the errors is resolved. I have no problem and this issue can be closed!


Add Doctrine Annotation ruleset

Adds a ruleset with all Doctrine Annotation related rules.
Current default options of these rules are based on examples found in Doctrine Annotation documentation and Symfony documentation. I changed some options in the ruleset based on discussion in https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/2693.

integration test is needed

Test added.

Thank you @julienfalque.


Problem with less variables imported from other packages

Problem
If you're importing less variables from other package, the changes to the variable are not seen by the builder, unless you remove .dart_tool & run rebuild.
How to reproduce
Link to the repo to reproduce the issue - https://github.com/missvalentinep/less_variables_example

Serve angular-app. Open the served app - the text is in green color

Change value of @chosen-color (in imported-styles/lib/src/basic_palette.less) to blue, for example. Save.

Rebuild finished with 1 outputs (2 actions)

Open the served app - the text is still in green color

Remove .dart_tool, serve the app once again

The text now has blue color.

Additional
For some reason, when I tried to create a new project that had less variables and import it, the problem did not reproduce.
I'm not sure that the problem occurs precisely because of the variables file being in another package. I've encountered a similar issue, when the value of the less variable was changed inside the same project (perhaps, it has something to do with imports, since in that case they were used too, but from the same package) and no changes were visible. Unfortunately, I was unable to reproduce this issue on a small repo.

Are you in the less_dart last version?
Your problem reminds me the issue with 2.3.5: [https://github.com/AdalbertoLacruz/less_dart/issues/26] yet resolved.
From your example the less_dart version is 2.3.5.

I've checked - I'm using 2.3.8 because of the pub upgrade. But I've updated the code in the example project to use ^2.3.8. Sorry for the confusion.
Were you able to reproduce the issue locally?

OK. You must use package notation inside the package.
So, in the file: lib\palette.less in the  imported_styles package, replace:
@import (reference) "src/basic_palette.less";
to
@import (reference) "packages/imported_styles/src/basic_palette.less";
The less builder needs to know what files are changed and the package notation helps.

@AdalbertoLacruz that seems to solve the issue, thank you! Don't you think it's a bug that this works only with package notation?

I do apologize for the late reply. Thank you for describing the alternative option, I will put in into consideration.


single-letter query

current search appears to be for individual letters, but a simple contains search does not target the single-letter field and there is no general single-letter search.

done


[Download] Small fixes/updates

update text for place selector, no variables selected message, and update button
add additional option for selecting all available dates
fix bug where preview table shows loading and then disabled when options change
add info text

Thanks for the review! I've been noticing the timeouts too and I've been meaning to find time to look into them, will try to do it this week


MINOR: Using rocksdb's prefixScan in fk joins for better performances

Use prefixScan for scanning subscribed keys to a foreign key instead of range. The native store's prefixScan already exclude the last key corresponding to the bytes increment (needed for scanning) while range included it. It allows removing the Arrays.equals, improving performances. I also removed the full combined key to be deserialized as we only need the PK (the suffix).
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@AyoubOm is there something else missing to merge?

@mimaison @halorgium @astubbs @mjsax as said in the docs, pinging you (GH proposed your name)

@AyoubOm any update here?


[2.1.0] Throwing error after ionig generate

Short description of the problem:
The command ionic g throws an error, nevertheless its doing its job before.
What behavior are you expecting?
No error
Steps to reproduce:

ionic g
component
enter name

? What would you like to generate: component
? What should the name be? ClubCard
[OK] Generated a component named ClubCard!
TypeError: Cannot read property 'initializer' of undefined
    at Object.appendNgModuleExports (/home/heisenberg/code/cap/node_modules/@ionic/app-scripts/dist/util/typescript-utils.js:238:33)
    at /home/heisenberg/code/cap/node_modules/@ionic/app-scripts/dist/generators/util.js:246:58

global packages:

    @ionic/cli-plugin-proxy : 1.3.2
    @ionic/cli-utils        : 1.5.0
    Cordova CLI             : 7.0.1
    Ionic CLI               : 3.5.0

local packages:

    @ionic/app-scripts              : 2.1.0
    @ionic/cli-plugin-cordova       : 1.4.1
    @ionic/cli-plugin-ionic-angular : 1.3.2
    Cordova Platforms               : android 6.2.3 ios 4.4.0
    Ionic Framework                 : ionic-angular 3.5.3

System:

    Node       : v6.10.0
    OS         : Linux 4.4
    Xcode      : not installed
    ios-deploy : not installed
    ios-sim    : not installed
    npm        : 5.3.0

Had the same issue after upgrading @ionic/app-scripts to 2.1.0, moved back to 2.0.2 & was here to check if anyone else had a similar problem.

Solved in current version. Thanks guys <3

close Thx guys :)


Added basic support for examples

PR related to #64

Can you rebase and squash all your commits into the Added a simple implementation for examples one? Seems the mut fix is already committed and the short comment is just a fixup.
If you need help with that, just ping me.

Can you rebase and squash all your commits into the Added a simple implementation for examples one? Seems the mut fix is already committed and the short comment is just a fixup.
If you need help with that, just ping me.

Ok, I think I need some assistance for that.
I have never done that before.

No problem.
First, check that the main branch is up-to-date locally first with a pull. If you cloned the repo before I renamed master to main, git pull --all should grab main.
Then, to do an interactive rebase, after checking out to your feature branch, run git rebase -i main. This will rebase your feature branch against main. It should pop up an editor showing your three commits.
Change it so that only the top commit says pick, and change the others to say squash or s. Save.
Once you've done that you'll get another editor, this time with all the previous commit messages it's going to merge. Delete everything you don't want to keep (which is all of it except for "Added a simple implementation for examples". Save.
You should now have just one commit on that branch compared with main. 😄

Ah, no, you have your own fork that is a few commits behind. To fix this is a bit more than I can explain in comments, I'll rebase it myself this evening and merge it for you. :smile:

Thank you 😄

Thanks for the contribution. I will make some modifications to this, and report on them in #64.


Error: 400-IdcsConversionError, Post request failed{"schemas"

While deploying i am getting following error, probably related to #13
oci_identity_user.nc-bucket-user: Creating...
oci_objectstorage_bucket.nc-bucket-data: Creating...
oci_objectstorage_bucket.nc-bucket: Creating...
oci_objectstorage_bucket.nc-bucket-data: Creation complete after 0s [id=n/frhe6y3cxplt/b/nextcloud-bucket-data]
oci_objectstorage_bucket.nc-bucket: Creation complete after 0s [id=n/frhe6y3cxplt/b/nextcloud-bucket]
Error: 400-IdcsConversionError, Post request<EMAIL_ADDRESS>is an invalid format for an email address . The format must be compliant with RFC 5322.","status":"400","urn:ietf:params:scim:api:oracle:idcs:extension:messages:Error":{"messageId":"error.common.validation.invalidEmailFormat"}}

i was able to apply cleanly, darn. Trying something else now.

3a02823 pushed, same deal
mv oci.tfvars custom.tfvars
git pull
mv custom.tfvars oci.tfvars

hi, i was able to deploy completely but in order to do so i substituted my email adress in the oci-iam.tf file as I was still getting the same error as before.
resource "oci_identity_user" "nc-bucket-user" {   compartment_id = data.oci_identity_compartment.nc-root-compartment.id   description    = "OCI bucket user"   name           = "${var.nc_prefix}-bucket-user"   email          =<EMAIL_ADDRESS>i purged the deployment as i had trouble with the duckdns setup and can not redeploy now as i hit the vault limit and it takes 7 days to delete the entries, will get back to it once oci lets me deploy again
br


Update Microsoft Teams Rooms - Managed Service endpoints

With the availability of NOAM, EMEA and APAC regions, the list of urls for the Microsoft Teams Rooms - Managed Service is updated.

@dstrome Managed Service team needs URLs updated for new availability.

@joolive @kdspiess - The system that syncs contributions from this repo to the private repo where builds are run is experiencing an outage. To work around this, I've made the change requested in the private repo directly. I'm going to close this PR without merging but the changes will go live sometime today or tomorrow.
In the future, I recommend using the https://review.docs.microsoft.com/en-us/microsoftteams site to submit changes to content. This will direct your changes directly to the private repo.


Replace comment macro with triple backticks

The comment macro was replaced by Splunk with 'triple backticks' formatting in version 8.1 - which was deemed end-of-life in April 2023.
The changes included here update comment macro references in savedsearches.conf, macros.conf, and a handful of dashboards.

Thanks for submitting the merge. The new splunkbase website no longer tells me which splunk versions are in use.
I suspect it's likely safe to drop support for the older versions by using the new comment style
I'll review this later this week


Access the topology of a graph

Given a graph that the user constructed, I need to be able to access the topology of the graph.
Currently, it almost seems possible with FlowScene::nodes() and FlowScene::connections(), but although Connection is defined through its header, Node is not. Node is merely forward declared. If Node.hpp was visible or #include'd somewhere, it would work.

Agreed. On my fork I actually export Node and include <../src/Node.hpp>. It's definitely a needed feature.

@russelltg  Could you please make a pull-request?


Can't find resilient 17810...60 for rollback data

Is this a bug, feature request, or feedback?
Bug
What is the current behavior?
1567547458.335202,Can't find resilient<PHONE_NUMBER>30419317035484219558610158560 for rollback data
This should never happen: failure in /home/vagrant/wallaroo/lib/wallaroo/core/recovery/event_log.pony at line 361

What is the expected behavior?
Crashed process restarts successfully
What OS and version of Wallaroo are you using?
Ubuntu Xenial/18.04 LTS + aloc-tee-source branch at commit cd256a281
Steps to reproduce?
Compile with: make PONYCFLAGS="--verbose=1 -d -Dresilience -Dtrace -Didentify_routing_ids" build-examples-pony-aloc_passthrough
Then execute the script at https://gist.github.com/slfritchie/6bfd700b3f826aa5fb0a17034b358d7a
Output looks like this:
aloc_passthrough: no process found
python: no process found
python3: no process found
start 2 node wallaroo
run source
version 0.0.1 cookie Dragons Love Tacos! program_name celsius at least once instance_name instance host <IP_ADDRESS> port 7100 delay 0.05
2019-09-03 21:50:45,821 DEBUG    [__init__.py:361] ALOConnectorSource.connect
2019-09-03 21:50:45,822 DEBUG    [__init__.py:364] ALOConnectorSource.connect
2019-09-03 21:50:45,823 DEBUG    [__init__.py:367] ALOConnectorSource.connect
2019-09-03 21:50:45,823 DEBUG    [__init__.py:374] ALOConnectorSource.connect
2019-09-03 21:50:45,823 DEBUG    [__init__.py:383] ALOConnectorSource.connect
2019-09-03 21:50:45,981 DEBUG    [__init__.py:387] ALOConnectorSource.connect
2019-09-03 21:50:45,981 DEBUG    [__init__.py:389] ALOConnectorSource.connect
2019-09-03 21:50:45,982 DEBUG    [__init__.py:391] ALOConnectorSource.connect
2019-09-03 21:50:45,982 DEBUG    [__init__.py:394] ALOConnectorSource.connect
2019-09-03 21:50:45,982 DEBUG    [__init__.py:401] ALOConnectorSource.connect
2019-09-03 21:50:46,033 DEBUG    [connectors.py:409] MultiSourceConnector added Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=0, is_open=False)
2019-09-03 21:50:46,084 DEBUG    [connectors.py:409] MultiSourceConnector added Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=0, is_open=True)
2019-09-03 21:50:46,084 DEBUG    [connectors.py:425] MultiSourceConnector stream_opened Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=0, is_open=True)
2019-09-03 21:50:47,027 DEBUG    [connectors.py:460] MultiSourceConnector acked Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=816, is_open=True)
2019-09-03 21:50:48,094 DEBUG    [connectors.py:460] MultiSourceConnector acked Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=816, is_open=True)
    [SLF: The 1st message sent by the source is much bigger than the source's byte rate throttle, so nothing is sent & ack'ed for several seconds....]
2019-09-03 21:50:49,160 DEBUG    [connectors.py:460] MultiSourceConnector acked Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=816, is_open=True)
2019-09-03 21:50:50,215 DEBUG    [connectors.py:460] MultiSourceConnector acked Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=816, is_open=True)
2019-09-03 21:50:51,320 DEBUG    [connectors.py:460] MultiSourceConnector acked Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=816, is_open=True)
2019-09-03 21:50:52,392 DEBUG    [connectors.py:460] MultiSourceConnector acked Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=924, is_open=True)
2019-09-03 21:50:53,449 DEBUG    [connectors.py:460] MultiSourceConnector acked Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=1093, is_open=True)
2019-09-03 21:50:54,494 DEBUG    [connectors.py:460] MultiSourceConnector acked Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=1253, is_open=True)
Now to kill 30904
Now restart
Restarted, sleeping a while
2019-09-03 21:50:58,351 WARNING  [__init__.py:626] Received RESTART message. Closing streams and reinitiating handshake.
2019-09-03 21:50:58,352 DEBUG    [__init__.py:632] Removing socket from asyncore map
2019-09-03 21:50:58,353 DEBUG    [__init__.py:638] Closing socket 3
2019-09-03 21:50:58,354 DEBUG    [connectors.py:439] MultiSourceConnector closed Stream(id=8085650408159805463, name='/home/vagrant/foo', point_of_ref=1253, is_open=False)
2019-09-03 21:50:58,354 INFO     [__init__.py:650] Updating target address from <IP_ADDRESS>:7100 to <IP_ADDRESS>:7100
2019-09-03 21:50:58,354 DEBUG    [__init__.py:361] ALOConnectorSource.connect
2019-09-03 21:50:58,355 DEBUG    [__init__.py:364] ALOConnectorSource.connect
2019-09-03 21:50:58,357 DEBUG    [__init__.py:367] ALOConnectorSource.connect
2019-09-03 21:50:58,357 DEBUG    [__init__.py:374] ALOConnectorSource.connect
2019-09-03 21:50:58,358 DEBUG    [__init__.py:383] ALOConnectorSource.connect
Sleep done

The complete logs are at http://wallaroolabs-dev.s3.amazonaws.com/logs/logs.20190903a.tar.gz

The same error happens if I try to restart the initializer: see /tmp/pass1b.log in the tarball at http://wallaroolabs-dev.s3.amazonaws.com/logs/logs.20190903b.tar.gz


very important updates

What's this PR do?
adds emoji
How should this be reviewed?
enjoy the emoji
Any background context you want to provide?
we should use the tools we have
Checklist

[X] Documentation added for new features/changed endpoints.

🔥 🔥 🔥 🔥


[dartsim] Add new port

Describe the pull request

What does your PR fix? This PR adds a new port for the DART (Dynamic Animation and Robotics Toolkit) library, a articulated body simulated library used in Robotics and Graphics (http://dartsim.github.io/). Fix https://github.com/microsoft/vcpkg/issues/10015 .

Which triplets are supported/not supported? Have you updated the CI baseline?
As far as I know all the triplet should be supported.

Does your PR follow the maintainer guide?
Yes

Apparently this need a bit more work, marking it as WIP.

The second patch failed to apply, could you update it?
Checking patch cmake/DARTMacros.cmake...
error: while searching for:
endif()
else()
set(HAVE_${variable} FALSE CACHE BOOL "Check if ${variable} found." FORCE)
if(ARGV3) # version
message(WARNING "Looking for ${dependency} - NOT found, to use"
" ${component}, please install ${dependency} (>= ${ARGV3})")
else()
message(WARNING "Looking for ${dependency} - NOT found, to use"
" ${component}, please install ${dependency}")
endif()
return()
endif()
error: patch failed: cmake/DARTMacros.cmake:135
error: cmake/DARTMacros.cmake: patch does not apply

Yes, I already fixed it locally, I need to push it upstream, but the port is still blocked by https://github.com/microsoft/vcpkg/pull/12795 .

Yes, I already fixed it locally, I need to push it upstream, but the port is still blocked by #12795 .

https://github.com/microsoft/vcpkg/pull/12795 has been merged, I just rebased the PR on the top of the latest master.

The PR is now failing due to the error:
FAILED: dart/utils/CMakeFiles/dart-utils.dir/XmlHelpers.cpp.o
/usr/bin/c++  -DBOOST_TEST_DYN_LINK -I/mnt/vcpkg-ci/buildtrees/dartsim/src/v6.9.4-8a922c6dbc.clean -I. -isystem /mnt/vcpkg-ci/installed/x64-linux/share/eigen3/../../include/eigen3 -isystem /mnt/vcpkg-ci/installed/x64-linux/include -fPIC -Wall -Wextra -fPIC -g -fno-omit-frame-pointer -fno-inline-functions -fno-inline-functions-called-once -fno-optimize-sibling-calls -MD -MT dart/utils/CMakeFiles/dart-utils.dir/XmlHelpers.cpp.o -MF dart/utils/CMakeFiles/dart-utils.dir/XmlHelpers.cpp.o.d -o dart/utils/CMakeFiles/dart-utils.dir/XmlHelpers.cpp.o -c /mnt/vcpkg-ci/buildtrees/dartsim/src/v6.9.4-8a922c6dbc.clean/dart/utils/XmlHelpers.cpp
In file included from /mnt/vcpkg-ci/installed/x64-linux/include/boost/lexical_cast/detail/converter_lexical_streams.hpp:63:0,
                 from /mnt/vcpkg-ci/installed/x64-linux/include/boost/lexical_cast/detail/converter_lexical.hpp:54,
                 from /mnt/vcpkg-ci/installed/x64-linux/include/boost/lexical_cast/try_lexical_convert.hpp:44,
                 from /mnt/vcpkg-ci/installed/x64-linux/include/boost/lexical_cast.hpp:32,
                 from /mnt/vcpkg-ci/buildtrees/dartsim/src/v6.9.4-8a922c6dbc.clean/dart/utils/XmlHelpers.cpp:38:
/mnt/vcpkg-ci/installed/x64-linux/include/boost/lexical_cast/detail/inf_nan.hpp:34:10: fatal error: boost/math/special_functions/sign.hpp: No such file or directory
 #include <boost/math/special_functions/sign.hpp>
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

That is probably due to https://github.com/microsoft/vcpkg/issues/8753 . However, an obvious workaround is to add an explicit dependency on boost-math.

The CI tests are now running correctly.

Thanks!


CLI parameters with Click

Hello,
Instead of changing the pathFolder and destinationFolder variable in the file bloodvessels.py to point to the directory where your images are located (which can lead to inappropriate Git commits when submitting PR), you should use command line parser with default value for pathFolder and destinationFolder.
http://click.pocoo.org/5/ can help.
@click.command()
@click.option('--path_folder', default='', help='Path folder.')
@click.option('--destination_folder', default='', help='Destination folder.')
def main(path_folder, destination_folder):
    print("Do it")

if __name__ == '__main__':
    main()

Thanks. Will fix this by either adding inbuilt python command line parser via argparse or through the method you so kindly suggested.


nativeEvent is returned for most of the events listeners

Hi guys,
First of all I need to say I love the library, thanks very much for such a nice API for interactions. I am porting the API to JS in order to make it work also when using react-native-web. And to check if it's properly working I am porting the playground to a web version too.
I have realized that most of the listener props returns an object that contains an attribute nativeEvent in it, e.g.:
https://github.com/wix/react-native-interactable/blob/master/playground/src/real-life-examples/RealChatHeads.js#L95
The documentation doesn't say anything about the nativeEvent attribute:
https://github.com/wix/react-native-interactable/blob/master/PROPS.md#onstop-function
It says that the listener receives an event directly with x and y attributes. The version I am working on skips the nativeEvent part, but then is not the same than yours. What's really wrong the docs or the implementation?

nativeEvent is a standard pattern for passing data from native code to JS. For example onLayout prop for react-native is called with an evt object with the form evt.nativeEvent.layout.height. The nativeEvent object is assembled when you pull it out of evt so you can't call evt.nativeEvent twice without an error. I believe this is a performance optimization.

Then documentation should be updated, because the event listener receives an object that contains a nativeEvent object, and the docs say that receives the event object directly see:

x - The horizontal position of the view (relative to the center).
y - The vertical position of the view (relative to the center).```

It's wrong, `{x,y}` is not passed as an argument, `{nativeEvent: {x,y}}` is passed as an argument.

@arqex is right, could somebody please update the documentation, so every new developer would not spend extra time figuring out why events have no properties described in documentation?


Add support for Java8 CompletableFuture to Call

It would be nice to support a niladic form of Call#enqueue that returns CompletableFuture<Response>. Is it currently reasonable to upgrade support for Android to at least v7.0 (API Level 24, where CompletableFuture arrives)?

That accounts for 0.7% of active Android devices so it will be at least 3
or 4 years before Java 8 is viable for a project like OkHttp.
On Wed, Jan 11, 2017 at 2:09 PM John Napier<EMAIL_ADDRESS>wrote:

It would be nice to support a niladic form of Call#enqueue that returns
CompletableFuture. Is it currently reasonable to upgrade support for
Android to at least v7.0 (API Level 24, where CompletableFuture arrives)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/3102, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEWtmgS1Ve4qctF7fOMdaifj87k0Uks5rRVL9gaJpZM4LhIWm
.

We could ship a sibling module adding static methods to wrap a Call, but it
seems fairly low-value since it's fairly easy to write your own. Also
Kotlin extension methods work great here since you can add an enqueue-like
method that returns a CompletableFuture.
On Wed, Jan 11, 2017 at 2:23 PM John Napier<EMAIL_ADDRESS>wrote:

Closed #3102 https://github.com/square/okhttp/issues/3102.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/3102#event-919888538, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEEazMUvz6TOnE_xS87E1MSE1qJwG5ks5rRVZ3gaJpZM4LhIWm
.

I see that Java 8 is required now - will be great to reopen this issue.

Worth a quick discussion. Seems high value for java callers.

CF is a pretty poor API to push people towards though. I wouldn't want to evangelize its use implicitly.

I agree with you @JakeWharton but do we really need something more in simple applications (lambda functions in my case)?
For me CF is better than custom Callback class - I can integrate it with my software in an easier way then.

I think you can write about 6 lines of code to do this. Maybe paste a sample here for those interested? I don't want this in the library directly.

@swankjesse could you elaborate a bit? Custom Callback class vs standard JVM solution (CF)?
Btw.
Please keep in mind that I'm not ❤ in CF - I just don't like to reinvent the wheel.

Voila: https://gist.github.com/swankjesse/3c11c407f2fc80c1fa9242a94dd0f7e2

This would be much more convenient to have in the library itself. Taste aside, java.util.concurrent.CompletableFuture is the standard JVM class for representing a future.


[ci/cd] Use of matrix platform to parallelize docker images build

Related to #248
Actually, docker images builds are too long (~ one hour).
This PR try to reduce the time of build.
By removing the docker workflow, and mixing the docker builds in the api workflow, it allows us the reuse of build artifacts.
We build all packages in general-build and reuse it in the docker-{api/app}-build jobs.
I add also cache directives with gha. Don't know if it's really useful. Will check this in the future workflows to see if any decrease in build time is observable.

@Alketta you can check results more precisely here : https://github.com/locokit/locokit/issues/248#issuecomment-1693092598


Potential crash when rotating a log file due to initialisation order

I suddenly had a site today go down with a PHP warning about setting the default timezone. It was quite odd because the site was working fine until a random refresh.
I discovered that as the bundle.php uses static Symphony methods to set the configuration, start the error handler, database and extension manager, we actually aren't invoking Symphony's constructor until later on. This means the date, language and sessions all are not started until the symphony() method is called.
This caused an issue because when the error handler initialised, it wanted to write a log file and give it a date but the configuration hadn't been yet set, and as my local PHP doesn't set the timezone either, the warning was raised.
There is also a potential for edge cases where an error occurs before the error handler is invoked or before the session is actually initialised.
This error was introduced in Symphony 2.5 with the index reorganisation and launcher abilities. Fortunately it's fairly easy to resolve as everything goes through bundle.php these days, regardless of the renderer.
Proposal:

[ ] add a Symphony::boot method which replaces the existing Symphony::initialise* calls in the bundle
[ ] move the date configuration settings out of the constructor into their own method
[ ] remove the duplicate calls to start the error handler
[ ] remove the Frontend::_construct() method (unused variable)

@nitriques Let me know what version you'd like me to target for this and I can make the necessary changes.

@brendo This would need to wait until #2509 is merged. I was hitting similar problems with things being 'not initialised' for some time.
The Symphony::boot proposal is great, but would also mean the we need to target this to 2.7.0

There is a quick fix that can be implemented for a 2.6.5, simply move the date constant settings from the constructor to the initialiseConfiguration method call. I can submit a PR for this if you like?

Yes please !

Let me know what version you'd like me to target for this and I can make the necessary changes.

@brendo If you'd like to tackle this problem in the 2.7.x branch, it would be nice!

@brendo Ping? Thanks mate.

Mmm, gonna leave this alone. It'll no doubt happen as I pull things apart to get a CI build going.

Great!


Switch from class-based to function-based

Refs #8

On the one hand, this is a HUGE breaking change.
But I've not used this library for anything yet, and a GitHub code search finds no-one else using it either: https://cs.github.com/?q=%2F\basyncinject\b%2F language%3APython&scopeName=All repos&scope= (/\basyncinject\b/ language:Python)
https://pypistats.org/packages/asyncinject suggests 9 downloads a week, which are likely vulnerability scanning bots.

Since it's not 1.0 yet I'm going to go ahead and break the whole thing!


LocalFileSystem doesn't work with local URLs

It would be useful to have LocalFileSystem work with local URLs, such as file:///some/path, not just with local paths.

Not sure of your use case, but if believed to be a valid and useful addition to Luigi feel free to submit a PR! All are welcome!

I mean a very simple modification to the class. It is frequent, when working with pyspark, to deal with local file URLs, such as the one I showed in the head post, especially within unit test suites, so it would be convenient to have methods such as LocalFileSystem.listdir yield results for urls as well, for instance:
>>> fs = luigi.LocalFileSystem()
>>> list(fs.listdir('file:///home/jytug/some_directory'))
['file:///home/jytug/some_directory/some_file.txt', ...]

I will open a PR, so that anyone with write permissions can decide if it's useful and should be included


Introduce a flag to block merges for certain milestones

This blocks merge for v1.4 and next-candidate. When we open for v1.4 we
should remove v1.4 from the flags and remove next-candidate from all
PRs.

Manual rebase of #1083