global: 6.6.5 -> 6.6.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/global/versions.
meta.description for global is: "Source code tag system"
meta.homepage for global is: "https://www.gnu.org/software/global/"
meta.changelog for global is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/global passed the binary check.

/nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/gozilla passed the binary check.

/nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/gtags passed the binary check.

/nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/htags passed the binary check.

Warning: no invocation of /nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/htags-server had a zero exit code or showed the expected version

/nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/globash passed the binary check.

/nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/gtags-cscope passed the binary check.

/nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/.gtags-wrapped passed the binary check.

/nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin/.global-wrapped passed the binary check.

7 of 9 passed binary check by having a zero exit code.

8 of 9 passed binary check by having the new version present in output.

found 6.6.6 with grep in /nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6

found 6.6.6 in filename of file in /nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6

directory tree listing: https://gist.github.com/1e67a6d5823bef3e9caf300390c30d1d

du listing: https://gist.github.com/12453483c832bc8b492c78ec1e5e2b44

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
global

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A global https://github.com/r-ryantm/nixpkgs/archive/17ad24788591f0a2f809a609630202a161475917.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6
ls -la /nix/store/sx7fvnbb5hil0g0625bgchk8f55i6k9c-global-6.6.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

global

Maintainer pings
cc @pSub @peterhoeg for testing.

Result of nixpkgs-review pr 121591 at 17ad2478 run on aarch64-linux 1

1 package failed to build:

global

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.


Add COMPUTE

I have added COMPUTE plain English Summary to the handbook. @gedankenstuecke or @BrainonSilicon  can you review it later when you have time, pls?
I am also keeping @SydneyAmbrose in the loop in case she needs them.

Thank you @gedankenstuecke - I made a few changes and will ask if they can add more information about how the project will involve patients and members of the public.

@gedankenstuecke I have updated the last section about "how the project will involve patients and members of the public". Feel free to review it when you have time!


Master channel closed on exit

When the master process is exiting, we attempt to notify workers of this fact but the master channel has already closed. In node 4+, these messages will never be sent and an uncaught error is thrown as a result. We should remove this exit listener as it serves no purpose. Instead, we should only send these messages prior to the master exiting. For example, when a worker suicides, the master process will exit, but it should wait until it has sent these messages to any workers that are still connected.
Also, while we're fixing this bug, note that worker.suicide has been deprecated and replaced with worker.exitedAfterDisconnect. See: https://nodejs.org/api/cluster.html#cluster_worker_suicide

Note: This bug can be seen by running bedrock-views' compile-less command when the number of workers is set to something higher than 1.

This is no longer applicable.


fix install script

Codecov Report

Merging #11 (9aea6bd) into main (bf5e638) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage   87.69%   87.69%
=======================================
  Files           5        5
  Lines          65       65
=======================================
  Hits           57       57
  Misses          7        7
  Partials        1        1

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 bf5e638...9aea6bd. Read the comment docs.


[zh] sync concepts/architecture/garbage-collection.md

PR Summary

I apologize for not contributing over the past three months. I've been preoccupied with a hurried relocation to another country. Hopefully, in 2024, I'll be able to commit more time and effort to our shared goals.

 You should avoid using external garbage collection tools, as these can
 break the kubelet behavior and remove containers that should exist.

@@ -137,6 +137,20 @@ collection, which deletes images in order based on the last time they were used,
 starting with the oldest first. The kubelet deletes images
 until disk usage reaches the `LowThresholdPercent` value.

+#### Garbage collection for unused container images {#image-maximum-age-gc}
+
+{{< feature-state for_k8s_version="v1.29" state="alpha" >}}
+
+As an alpha feature, you can specify the maximum time a local image can be unused for,
+regardless of disk usage. This is a kubelet setting that you configure for each node.
+
+To configure the setting, enable the `ImageMaximumGCAge`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kubelet,
+and also set a value for the `ImageMaximumGCAge` field in the kubelet configuration file.
+
+The value is specified as a Kubernetes _duration_; for example, you can set the configuration
+field to `3d12h`, which means 3 days and 12 hours.
+
 ### Container garbage collection {#container-image-garbage-collection}

 The kubelet garbage collects unused containers based on the following variables,
@@ -178,4 +192,4 @@ configure garbage collection:

 * Learn more about [ownership of Kubernetes objects](/docs/concepts/overview/working-with-objects/owners-dependents/).
 * Learn more about Kubernetes [finalizers](/docs/concepts/overview/working-with-objects/finalizers/).
-* Learn about the [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) that cleans up finished Jobs.
+* Learn about the [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) that cleans up finished Jobs.
\ No newline at end of file

Sync check byscripts/lsync.sh on sync/garbage-collection branch:
$ scripts/lsync.sh content/zh-cn/docs/concepts/architecture/garbage-collection.md
content/zh-cn/docs/concepts/architecture/garbage-collection.md is still in sync

Thanks to the reviewers in advance.
Best Regards,
Kivinsae Fang

@tengqm Thanks for the review.
New commits have been squashed and rebased.

@windsonsea
Thank you for the review.
All changes were updated and rebased, and co-author name list was updated.

/lgtm
/approve


fix: enable uniform_bucket_level_access

Fixes: b/302700168
Enable uniform bucket level access to avoid the error:
Error: googleapi: Error 412: Request violates constraint 'constraints/storage.uniformBucketLevelAccess', conditionNotMet

@davidcavazos can you please update the title to fit for conventionalcommits notation and update from main? I can rerun int tests after

@davenportjw Thanks, I just fixed it.

/gcbrun

/gcbrun

@davidcavazos can you take a look at this error from integration test and fix?
Error: Error updating default object acl for bucket lds-resource-169006968094-golang: googleapi: Error 400: Cannot use ACL API to update bucket policy when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access, invalid
with module.simple.module.storage.google_storage_default_object_acl.policy,
on ../../modules/storage/main.tf line 26, in resource "google_storage_default_object_acl" "policy":
26: resource "google_storage_default_object_acl" "policy" {


Get rid of TypeParser

Is your feature request related to a problem? Please describe.
I'm always frustrated with the type parser.
Describe the solution you'd like
I want to get rid of it
Describe alternatives you've considered
The language frontends should dissect the type as much as possible to scalar and object types. These types should then create primitive and object types.

This feature should build on https://github.com/Fraunhofer-AISEC/cpg/pull/1033


API Documentation not correct or not specified correctly on how to use the API!

Using the new API (apicalypse) there seems to be an issue on how to use the api. In the IGDB discord, I mentioned that after importing the new wrapper (node - apicalypse) I had to console log apicalypse to find { default: [Function function] }.
Now the reason why I looked for this was because I was receiving an error that said apicalypse is not a function.
It was also in the unofficial docs for a node module: [https://www.npmjs.com/package/igdb-api-node]
stating in installation and setup
const igdb = require('igdb-api-node').default;
This also applies to the new apicalypse wrapper.

I'm afraid I don't understand what isn't correct. The docs clearly have two sections, one for ES5 (which is the require version) and one for ES6 (the import version)
If you would like to fork the repo and suggest changes, we welcome Pull Requests.


Improve documentation for Reactor Networks and add two Python tutorials

I wrote an extended description for Cantera's Reactor Networks. It's surely not complete, but I think that it gives a better introduction to Reactors than the current documentation does.
Additionally, I added two Python examples: pfr.py models a PFR by tracing a Lagrangian particle and a chain of reactors (like surf_pfr.py), and compares the two methods.
ic_engine.py models a (gaseous) Diesel Internal Combustion engine by a homogeneous cylinder, moving piston, and flexible valves. It relies on the Madison n-heptane reaction mechanism, which is not included in Cantera. This is not ideal, but I did not come up with a better idea.

Sorry, I just noticed that this is the wrong branch. I'll file a new pull request in the Cantera/cantera branch in a minute.


drivers/rptun: add rptun trace feature for debug

Summary
add rptun trace feature for debug
Impact
rptun
Testing
CI

[Experimental Bot, please feedback here]
No, this PR description does not adequately meet the NuttX requirements.  While it touches on some areas, it lacks crucial details and depth.  Here's a breakdown:

Summary:  "add rptun trace feature for debug" is too vague.  Which part of rptun is being traced? What kind of trace information is added?  What debugging scenarios does this aim to address?  A NuttX issue reference should be provided if one exists.

Impact: Simply stating "rptun" doesn't explain the impact.  This section requires "YES/NO" answers for each category, followed by descriptions if "YES."  For example:

Is new feature added? YES (Adds tracing capabilities to the rptun driver)
Is existing feature changed?  Possibly YES (If the code was modified beyond just adding traces).  Explain how it changed.
Impact on user:  Possibly YES (If users need to enable the tracing or if the tracing affects performance). Explain how.
Impact on build:  Possibly YES (If new configuration options are added).  Explain the changes.
Impact on hardware: Likely NO (Unless the tracing interacts with hardware in some way).
Impact on documentation:  YES (Documentation should be updated to describe how to use the new tracing feature). Explain what documentation needs updating.
Impact on security:  Possibly YES/NO (Depending on the nature of the traced information. Could it leak sensitive data?). Justify the answer.
Impact on compatibility: Likely NO (Unless the changes break existing rptun functionality).

Testing: "CI" is insufficient.  List the specific build hosts and target platforms where the changes were tested.  Provide actual test logs (or snippets of relevant logs) showing the behavior before and after the change.

In short, the PR description needs significantly more detail and explicit answers to the questions posed in the template.  Without this information, reviewers cannot effectively assess the changes and determine if the PR is ready to be merged.

@luckyyaojin please update Documentation/ to include this feature

@luckyyaojin please update Documentation/ to include this feature

@acassis OK


Add file common.js

Hello,
I think it would be very helpful if Ratchet have a common.js file because they are few PRs which request that file like : https://github.com/twbs/ratchet/pull/675 or https://github.com/twbs/ratchet/pull/427

Closing in favor of #675.


Upgrade the minimum php version to 8.0 for nats.

link https://github.com/hyperf/hyperf/issues/4238


Batch Edit: Adding additional user and group permissions is not working

After adding additional user permissions to a batch of works, it appears to save correctly, but when refreshing the page, the new permissions are not present.

"Auto pointed" at 3.


Add Allied Telesis Vendor

Add Allied Telesis Vendor, support both SSH and Telnet

I have add Allied Telesis Vendor, so sorry if there is something wrong.
Because I'm new to Github process and I see #1, which should be something else.


SemanticTokensBuilder.buildEdits() returning incorrect deleteCount

I'm working on an issue where the users of a language server that I'm the maintainer of see their semantic coloring go haywire when doing deletes. I've confirmed that if I modify my language server to provide full tokens for a document every time (it currently registers as a full and delta provider), the tokens are correct after a delete. However, when registering as a delta provider and using the SemanticTokensBuilder.buildEdits() function, I observe this behavior:
My document upon open contains this text:
Class User.short
{

/// desc
ClassMethod t()
{
    q 1
}

}

And these tokens:
[ 0, 0, 5, 4, 0 ]
[ 0, 6, 4, 5, 0 ]
[ 0, 4, 1, 5, 0 ]
[ 0, 1, 5, 5, 0 ]
[ 1, 0, 1, 8, 0 ]
[ 2, 0, 3, 7, 0 ]
[ 0, 4, 4, 7, 0 ]
[ 1, 0, 11, 4, 0 ]
[ 0, 12, 1, 11, 0 ]
[ 0, 1, 2, 8, 0 ]
[ 1, 0, 1, 8, 0 ]
[ 1, 4, 1, 60, 0 ]
[ 0, 2, 1, 51, 0 ]
[ 1, 0, 1, 8, 0 ]
[ 2, 0, 1, 8, 0 ]

If I delete the line ///  desc (tokens 6 & 7), the result of textDocument/semanticTokens/full/delta is:
{
    "resultId": "1618608792098",
    "edits": [
        {
            "start": 27,
            "deleteCount": 9,
            "data": []
        }
    ]
}

and the expected result is:
{
    "resultId": "1618608792098",
    "edits": [
        {
            "start": 27,
            "deleteCount": 10,
            "data": []
        }
    ]
}

I'm using VSCode 1.55.2 and vscode-languageclient/server 7.0.0
Original issue: https://github.com/intersystems/language-server/issues/29

@isc-bsaviano thanks for the report. Could you add the source code behind the tokens so that I can easier relate the tokens. Then I can create that programmatically and see why it fails. Thanks!

Hi @dbaeumer, thanks for looking into this. textDocument/semanticTokens/full and textDocument/semanticTokens/full/delta both call function parseText():
export function parseText(text: string, moninfo: monikerinfo, builder: SemanticTokensBuilder) {

	//console.log('parseText: ' + moninfo.moniker + ':' + moninfo.monikeropt);

	const jsonform = parsedocument(moninfo.moniker,moninfo.monikeropt,text).compressedlinearray;
	if (parserlogcompressedresult) {
		logcompressedresult(jsonform);
	}

	let anyerrors = false;
	for (let lineno in jsonform) {
		const line = jsonform[lineno];
		for (let itemno in line) {
			const item = line[itemno];
			if (item.s === 0) {
				anyerrors = true;
			}
			const tokenmodifiers = (item.w === 0) ? [] : [WARNING];
			builder.push(+lineno, item.p, item.c, lookupattr(item.l,item.s), encodeTokenModifiers(tokenmodifiers));
		}
	}

	if (makeclsparsetree && !anyerrors && moninfo.moniker === 'CLS') {

		try {
			const ast = parseClassDocument(jsonform, text);
			console.log(ast);
		}
		catch (error) {
			console.log('error calling parseClassDocument: ' + error);
		}
	}
}

parseText() calls out to our proprietary C++ parsers to parse the document into an array of tokens of type compresseditem[][], where each token has these properties:
export type compresseditem = {
    'p': number, // offset within line
    'c': number, // count (length of source of this item)
    'l': number, // language index
    's': number, // coloring attribute index
    'w': number // 0=>no warning, 1=>warning
};

parseText() then pushes each one of the parser-generated tokens into the SemanticTokensBuilder. The only difference between our handlers for textDocument/semanticTokens/full and textDocument/semanticTokens/full/delta is that textDocument/semanticTokens/full just pushes the tokens into the builder, then calls builder.build() while textDocument/semanticTokens/full/delta first loads the previous result, then calls builder.buildEdits(). The source for textDocument/semanticTokens/full and textDocument/semanticTokens/full/delta can be found here and here. Let me know if you need any more details.

@dbaeumer Thanks for addressing this promptly! Do you know when a new "next" version of the modules will be released so I can pick them up in my LS?

My plan is to ship a new next version beginning of May when the next version of VS Code has shipped.

@dbaeumer are you able to ship this soon?

Sorry for that. I can make a next version beginning on next week.

Release<EMAIL_ADDRESS>and<EMAIL_ADDRESS>


Is it possible to add a custom button to the default toolbar button group?

I am not talking about adding buttons outside the viewer, but rather, add to the default shown here:

My case I want to add a custom "close" viewer button because the viewer will be a fullscreen modal window that I'll need to programmatically close when user is done viewing image.

I got it figured out.

@dosstx How ?

@SuhaibMaraqa I don't have a lot of experience in this area, but something like this should work:
viewer.buttonGroup.addButton(new OpenSeadragon.Button(buttonOptions));

For your buttonOptions see the constructor on https://openseadragon.github.io/docs/OpenSeadragon.Button.html.


Workflow and aim of project

I have created Workflow and Aim of our project in simple terms but it have quality content

@avinashkranjan  Hello sir if it is ok then can it be merged?

@avinashkranjan

thanks


[reloader] Add support for multiple config files

Currently the config file expects there to only be one config file
watched.  However, the nats config file can include other paths, and
we may also want to watch those.
This commit implements being able to specify an arbtirary number of
configuration files to be watched.

Sent PR to the branch with a couple of fixes: https://github.com/schancel/nats-operator/compare/multi-reloader...wallyqs:multi-reloader?expand=1

Can do tomorrow.

Pushed up a commit to figure out why e2e test blew up... :/

Picked commit https://github.com/nats-io/nats-operator/commit/38a67d92a82f61a2c3b3e3241e3649869be3482a from the branch and merged. Changes to the reloader should not have affected the results from the e2e tests, so taking a look at fixing the flapping test at https://github.com/nats-io/nats-operator/pull/178


MAINT: stats.gaussian_kde: error early if n_features > n_data

Reference issue
Resolves the scipy.stats part of gh-17436
What does this implement/fix?
When the dataset passed into gaussian_kde has fewer points than dimensions, the covariance matrix would be singular, and gaussian_kde would error out when attempting to perform Cholesky decomposition. However, sometimes this occurs when the user passes in the transpose of what gaussian_kde expects. This can result in a huge covariance matrix, causing problems like gh-17436. This PR prevents such problems by raising an error early, whenever the the dataset passed into gaussian_kde  has more dimensions than points.

Ok, I need to get a bit more decisive as branching is 10 days away. This claims to help prevent a segfault, modifies no old tests, the CI is passing, and just adds a small code change + 1 new test, so I'm going to merge it now.

@thomasrockhu any idea why the codecov patch diff is showing so many unrelated files on these PRs? Feel free to open an issue in this repo if you have a suggestion for a config change we might need (thanks!).

@tylerjereddy honestly I'm not too sure. My guess is some subset of tests aren't run or there is a flaky test around. Have you seen this in other PRs or just this one?


Invalid Input when creating new client

        opts := &socketio_client.Options{
		Transport: "websocket",
	}

	client, err := socketio_client.NewClient("https://cloud.tech", opts)
	if err != nil {
		log.Printf("NewClient error: %v\n", err)
		return
	}

	client.On("error", func() {
		log.Printf("on error\n")
	})

I am getting NewClient error: invalid input

I traced the error down to newClientConn()

don't use this lib,it's too old too buggy.I wast few days on it

@flufy3d Hi! What library do you recommend? Thx!

e

I switch to nodejs now ,golang is not well support for socketio especially client side

@flufy3d Hi! What library do you recommend? Thx!

I switch to nodejs now ,golang is not well support for socketio especially client side


Refactor themes

🚀 Pull Request
Description

See project item
To do

[ ] Tests
[ ] Did we want a docs page outside the API docs themselves?

This is still important.


Can't seem to cook for companions, only give them ingredients to eat

First, I'm sorry if this isn't how you'd prefer this problem be posted but I don't own the game on steam.
I'd like to feed my companion a cooked meal rather than individual ingredients but I can't figure out why I'm not able. The option goes straight to feeding them a single item. I have cooking and I'm standing next to a campfire. I checked the file and it seems like it should work, not sure what I'm doing wrong. Thanks for any help.

I wanted this feature! If I recall correctly, I couldn't figure out a fair way to handle effect expiration, since non-player creatures don't get hungry, and that's usually what makes effects wear off. Do you have an idea of a way to handle that that would feel fair?

Ahhh sorry, I didn't realize it wasn't implemented. I'm not a coder by any means, but I bet you could set it to the default metabolizing time, and maybe check if the companion has Fasting Way and/or Mind Over Body and just multiply it if they do rather than using hunger at all.
Or just give it a flat value if its hard to implement, honestly just having the option to feed them an actual meal at all would be so useful. Thanks for the amazing mod, its an absolute must have!

@Agalyon I've started work on this (c3d04438c2e477717a8af6d2d4c40b937f7085c3); it looks like the base game implemented expiration of cooking effects on non-player creatures at some point since I last checked, so this is just a matter of the cooking interface and applying the effects.
That commit has support for preset meals and cooking from ingredients if you want to try it out and maybe check for bugs! You can either use a campfire with companions adjacent to you to feed multiple at once, or feed your companion while near a campfire to just feed the one.

The ability to feed companions from campfires using preset meals, known recipes, or specific ingredients is implemented at ea4e5002cd947b013c0b5db54fb9b6bd98da4ede! Again, beta testing from the main branch would be super helpful to check for bugs, but otherwise this is probably going out to mainline soon and I'll expect the bugs to be reported there lol


TapRegion has no clear way to differentiate between different gestures

Use case
By default, the on screen keyboard is dismissed by non-mobile touch events, such as a click.
It is quite common to want similar behavior on mobile. That can be done by calling unfocus on the text fields FocusNode inside the onTapCallback. That does however mean that both taps and scrolls are handled the same, since TapRegion uses PointerDownEvent as a trigger for onTapOutside. (Contradictory to what the name might suggest. Compare with onTap and onTapDown in GestureDetector)
Having the ability to differentiate between scroll and tap would give developers the ability to close the text field on a tap, but keep it open when scrolling.
Attached below is a video of the Google Home app on Android, showing the behavior that I'm looking for.
https://github.com/flutter/flutter/assets/47989573/77d26c16-5359-44ae-8002-8e30ff88f8e8
Proposal
TapRegion, should have more parameters to differentiate between different gestures, similar to GestureDetector. This would be a breaking change, but onTapOutside should behave like onTap of GestureDetector, and a new parameter with the name onTapDownOutside should be added that has the current behaviour. Other gestures should be handled by other parameters.

Thanks for the report @Hannnes1

onTapOutside should behave like onTap of GestureDetector

Are you seeing the current behavior using onTapOutside that down event is not reported, but only up event is ?
If so, are you proposing that both events should be triggered as applicable ?

@darshankawar
The current behaviour of onTapOutside is that only the down event is reported (This is the same behavior as GestureDetector.onTapDown).
Compare that to GestureDetector.onTap, which is only triggered when a tap wins in the gesture arena.
My proposal is that TapRegion.onTapOutside should behave the same way as GestureDetector.onTap.

Don't you think we need a void Function(PointerUpEvent event); or a void function( ) to achieve what we want?
Because when I compared TapRegion with GestureDetector, GestureDetector uses :
typedef GestureTapDownCallback = void Function(TapDownDetails details);
typedef GestureTapUpCallback = void Function(TapUpDetails details);
typedef GestureTapCallback = void Function();

Yes, all three of those will probably be required @Utkarsh4517, Especially the last one, to correctly identify a tap.
Additional callbacks, such as onPanStart, onPanUpdate etc. might be needed as well. But that might be outside the intended scope of TapRegion. Someone with more knowledge about this than me should probably weigh in.

Just found out that we can achieve the desired output, If we wrap our entire Scaffold with the GestureDetector widget and pass FocusScope.of(context).unfocus(); inside onTap of GestureDetector.

Yes, that kind of works. There are some differences in the behavior of this solution and TapRegion though. For example TapRegion.groupId that can be used to group TapRegions together.

So what we can do is to rename the current TapRegion.onTapOutside to TapRegion.onTapDownOutside and Create a new TapRegion.onTapOutside which behaves the same as GestureDetector.onTap. also the onTap function takes no arguments, so PointerUpEvent is not required. my bad :(

Yes, that's what I'm thinking. Like I said, there are some differences between GestureDetector and TapRegion, but that shouldn't affect when a PointerDownEvent turns into a tap.

Hey @Hannnes1 @darshankawar I have a doubt. Do the new TapRegion.onTapOutside will be a void Function() or a void Function(PointerDownEvent event) ?

Hey @Hannnes1 @darshankawar I have a doubt. Do the new TapRegion.onTapOutside will be a void Function() or a void Function(PointerDownEvent event) ?

My interpretation is that it would have to be void Function(), since the PointerDownEvent might not have the correct information when the tap wins in the arena. (The pointer might have moved slightly, for example)

@Utkarsh4517 Did you make any more progress on this? I had a look at it myself, but it seems to be more complicated than I anticipated. Primarily because I would like to avoid a breaking change.

That issue is quite annoying and I experience the same when for example I push/pop route clicking on a close icon, and the new screen showing up contains a button in the same region, therefore it triggers the onTap of that button on that new screen...
Basically any buttons within the same region on different routes will get their onTapOutside function called.


Able to use chatroom with two users (two browsers)

Currently testing with (1) Chrome - Incognito and (2) Edge is unstable. Some functionality but very inconsistent.
Stabilize for demo purposes.

Originally found this issue on dev (and on all branches off of dev). After both users joined a room for the first time in one run, they couldn't see each other's messages, but they could see their own. Only the user that joined the room second could see that the first user was in the room, but even the user that joined second couldn't see the first user's messages as they were coming in. If they both left the room and returned to the same room or a different room then they could see each other's messages and they could see that each other were online, but the other user's status was always offline when they saw these messages.
Tested this issue again on the justine/LogoutCommand branch and didn't have any of these issues. The users in both browsers were able to see each other's messages the first time they joined a room and the status of each user was online. This issue was presumably fixed because I added missing calls to UpdateActivity() and OnUserIntialize() in the Join() method of Chat.cs on my branch.


Clean up teaching concept (credit to Birgit Willms)

Birgit Willms and I proofread the german teaching concept once more. This PR fixes language issues of the current version.

Perfect, thank you.


"Use metric units" toggle has no effect

Describe the bug
Even though I switch off the "Use metric units" toggle during the first configuration, sensor values are still expressed in metric units.
To Reproduce
Steps to reproduce the behavior:

Settings -> Devices & Services
Add Integration
Select "Toyota Connected Services"
Enter MyT email and password
Switch off the "Use metric units" toggle
Click "Submit":
Click "Finish"
On the Toyota Connected Service tile, click on "1 device"
Observe that all the numeric values for the Sensors are expressed in Km:

Expected behavior
The sensor values should be expressed in miles.
Screenshots

Additional context
Add any other context about the problem here.

That is strange. I'll have a look at it. Thank you for reporting it.

Hi @ccristal. This seems to be a issue of the category "It's not a bug, it's a Feature!" 😆
I have looked at our code and could not find any errors. The switch does exactly what it is supposed to do. Depending on the selection, the mytoyota python lib returns either metric or no metric values.
The "problem" lies with Home Assistant itself. Depending on the settings for Home Assistant, the units are converted automatically!
However, this can also be overwritten later in the settings of the respective sensors:

I think I have also found a setting option that allows you to specify the units with which a sensor should initially be displayed.
This should be included in the next release 😊
In the meantime, you can simply set your sensors to the desired display format yourself 😉

Thank you for looking into this... :-)


Extended the quickstart tutorial

Added more informative text and a slightly deeper dive based on early feedback.

This PR is outdated.


Explain Moderation in Settings/Store [Needs Design]

Above the section of the settings store tab where moderators are selected, there should be text explaining how moderation works:
"When a moderated purchase is made, the network fee is taken from the purchase price. That fee is currently estimated to be [Economic estimated fee] to [Priority estimated fee].
For example, if a moderated purchase is made for $50, and the fee is $5, you will receive $45.*
If that purchase is disputed, the moderator's fee will be subtracted from the total, then they will split the total between you and the buyer.
Because of this, moderated purchases are not allowed on purchases below [10 * estimated economic fee] to [10 times estimated priority fee], depending on the fee level the buyer uses. Keep this in mind when adding moderators and creating listings."

ideally this is shown in the display currency they have set in settings.

[ ] The text above should be shown somehow the first time the user accesses the tab.
[ ] The user should be able to view the text above again later.

An unfolding section of the page, or a modal that can be launched from a link or button are suggested.

@morebrownies this still needs some design work.

Ok added to my queue. Thanks for the reminder.


Manage Null equality

Be able to query : (e) => e.SurName == null

Is function string.IsNullOrEmpty(e.SurName) can help you ?

No, we have to filter only null value but not empty string


Improvement over the translator.js

It would be fine to do some modifications in the issued file,
So,
Group the parser functions over the "namespace" required, helping to keep the code more readable.
Use the functions .hasClass of jQuery ( api https://api.jquery.com/hasclass/ ) in replacement of $(this).attr('class')

Hi, thank you.
You're totally right, I'll encapsulate the parser functions.
For hasClass I will use the cheerio implementation :)


Use installed Abseil if available (otherwise download it)

This PR addresses the same issue as #1570. It enables a user to use an installed version of abseil. The main difference: If there is no installed package of Abseil, the repo will behave as before and download and build Abseil.
Thus, this PR should not mess with existing setups while allowing the user to use an installed version of Abseil.
I hope this prevents the concerns stopping  #1570 from getting merged.

@googlebot I signed it!

There is also #1387 which I believe is a superior method for downloading and configuring Abseil as
a Cartographer subproject, since this is done during configure-time. This voids the need to have a list of Abseil targets inside FindAbseil.cmake, since all are available natively because add_subdirectory() is used instead of the (IMHO) awful ExternalProject_Add.

The goal of this PR was to change as little as possible while allowing to provide your own version of abseil.
I hope this or any other PR achieving the same effect gets merged soon, since it is bothersome to work on a fork.

Closing in favor of #1570.


Azure Blob Storage Logs Sync Fix

Description
Azure Blob Storage logs are not getting synced.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[ ] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR require documentation updates?
[ ] I've updated documentation as required by this PR.
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have tested it for all user roles
[ ] I have added all the required unit/api test cases

Closing this PR as invalid


added hundrets of referer spammers

taken by own project darklist.de

I am not merging this pull request, since you made changes to the script to fit your specific needs/preference.
I am curious though, how did you build the huge domain list?

just do a git cherry-pick on commit 65698f2 to only get the list
how did i build it? i created a blacklist project (darklist.de) that focused very much on referer spamming. these are the domains that were spammed within the last 12 month.

i created a separate branch an pull request to merge, i you are interested in.. this one: closed


Update install instructions to support VIM/Neovim

Add new instructions to install via vscode marketplace, repository clone and conquer of completion (vim/neovim)
Closes #116

@pauloedurezende Thanks for instructions!


Market showing wrong rates for STEEM and SBD

On the market widget i can see this rates currently:

When i check on https://coinmarketcap.com/ i will get a very different rate:

Price we are showing not see reliable, there should be a similar rate on both sites.

Should be fixed now, closing this. Fixed in https://github.com/busyorg/busy/pull/968


Contribute to meta-rockchip.

Would you like to contribute recipes from this layer to meta-rockchip? The recipes are really useful.

At some point, maybe, but it looks to me like the meta-rockchip hosted at yoctoproject.org is more focused on using the upstream/mainline kernel, and Rockchip's meta-rockchip is more focused on development and testing of their chips/boards/drivers/etc., rather than creating a Yocto-friendly BSP layer. Not sure the stuff here would be appropriate in either place.

You have recipes for tools and some classes as well which will be useful in Yocto meta-rockchip, many people will be happy to use them. Please, consider contribution. Thanks for the replay anyway.


Feature Request: use tooltip of restore previous settings button to display diff of modules

This is yet another in the series of FRs titled 'please help my adhd brain', if this:

did something like
+Chat Portrait
-Levels

I think that'd be handy for 'I just enabled something and alt-tabbed while the reload worked and... I have no memory of what it was' situations, which, might just be me, come up a lot 😅
You might want to limit that to only, say, 10? modules or it could get pretty explody on going from full setup to almost-none for troubleshooting.

This is interesting, I wonder if it would be better to show a dialog that shows the changes like that. However, it would add an extra click.
Let me think about the best way to include something like this.


publish<EMAIL_ADDRESS>

Requested by: @romtsn
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] symbol-collector
[ ] maven
[ ] github
[ ] registry

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

6.1.0 because it contains a few features already


Tabs key navigation

Prevent jump to top of document on arrow key navigation

I can't replicate this, yo.

@thomasdigby Did a122eaf fix this?


[v6 rc4] Proper way to render custom component prop with a checkbox / radio?

Hi all!
A question came to my mind while upgrading my code to rc4:
Given this custom component with an input type checkbox:
class MyCustomInput extends Component {
  render() {
    const { input, meta: {error, touched} } = this.props
    return (

      <input {...input} type="checkbox"/>
      {touched && error &&
       {error}}

    )
  }
}

<Field name="myField" component={MyCustomInput}/>

The expected behaviour is that when the form is reseted / given an initial value, the checkbox updates accordingly, but the prop "value" doesn't affect checkboxes. I guess I should rewrite the input section like this:
...
const { input:{ value, ...additionalInput }, meta: {error, touched} } = this.props
...
<input {...additionalInput} type="checkbox" checked={value}/>

Is that the proper way? I'm confused because when using a string for the component prop it's working good without changes. Is the "checked" prop passed to the input? how can I get it?
<Field component="input" type="checkbox"/>

Actually, I'm reusing this component and is working outside redux-form:  "checked" is a property that I'm using to control the value and I can't do something like this:
...
<input {...additionalInput} type="checkbox" checked={value || checked}/>

In rc3 I was using some kind of hack to make it work:
<Field name="myField" component={renderField} type="checkbox"/>

Is there a similar o any other way?
Thanks in advance,

See https://github.com/erikras/redux-form/issues/1450#issuecomment-237288575.
This will have to be added to the docs.


World load order

I am trying to load in a world using worldboarder (/we fill) but run out of memory. This is fixable if I can reload it. However, the world I am trying to load in loads after worldboarder therefore worldborder thinks the world doesn't exist and cancels the command. Some worlds load before worldborder loads. Is there a way to change the order in which worlds load?

I'm having a problem with world loading order as well.  It causes problems with plugins not thinking that a world is there when it actually is.

I believe servers load files in alphabetical order

Spigot actually loads the plugins intitally based on when the plugin tells it to, based on the plugin.yml file within the jar, but after that level I don't know what it is based on.  In multiverse, it seems to be loading my worlds in this order:
world
world_the_end
Hub
But in my worlds.yml file it goes in this order:
world
world_nether
world_the_end
Hub
It doesn't seem to be putting anything into the logs about a nether world...
I also tried reorganizing the world.yml file and it is exactly the same.  No plugins seem to know about world_nether, and even though it shows it in the /mv list, multiverse seems to not know how to take me there...

Idk then.

I'm afraid I don't understand the original issue. Wouldn't you want all worlds to load before worldborder?
The order the worlds load in is not something you can configure. Bukkit does not gaurantee any kind of order when loading from a configuration file. That means that changing the order of the worlds in world.yml doesn't do anything because that's just not how Bukkit works.
In any case, the order Multiverse loads worlds shouldn't matter at all. Bukkit loads the default world (and it's nether and end) before most plugins (including Multiverse) are loaded. Then when Multiverse is loaded it loads in all the other worlds in worlds.yml. No other plugins will be loaded while Multiverse is loading worlds.

I think what is happening for Greenfoot5 is that some of the worlds load, and then in between world b and world c loading, the worldborder plugin loads.

@MrRiptide The only way that is happening is that the default worlds loaded, WorldBorder loaded, then all the worlds created/managed with Multiverse load. Worldborder cannot load during the Multiverse worlds.
If you want WorldBorder to load after Multiverse, you can edit the plugin.yml within the jar file and put the edited version back into the jar file. You would need to add depend: [Multiverse-Core].

I thought that changing the world load order would allow for me to have a world load perform a certain plugin. I thought this was possible because my default world had loaded and then worldborder and then my multiverse world. I didn't know there was a difference.


Bug with frame size that is not multiple of 128

I was wondering if you could help me to debug the following issue: if I set the frame size that is not multiple of 128 I get a segmentation fault on the following line:
https://github.com/kooBH/STFT/blob/1b8eb2a6954660f7921e1564d56f85c937c3d062/cpp/Ooura_FFT.h#L883
For example, if I set the frame size to 320, and the shift size to 160 I get a segmentation fault. Please, could you help me to fix this issue? Any help will be greatly appreciated.

I think it might be due to frame size not being a power of 2, because FFT requires it. So this issue might possibly be solved with padding.

Most of FFT algorithms requires frame size as power of 2.  Yes, padding is good solution.

Hi @kooBH. Thank you for your answer. Do you know by any chance how to properly pad the buffer with zeros? Can I just append zeros at the end of the buffer like that:
#include "cpp/STFT.h"
#include "WAV/WAV.h"

int main(){

  int ch = 1;
  int rate = 16000;
  int frame = 512;
  int shift = 256;
  int length;

  WAV input;
  WAV output(ch,rate);
  STFT process(ch,frame,shift);

  input.OpenFile("input.wav");
  output.NewFile("output.wav");

  short buf_in[ch*shift];
  double **data;
  short buf_out[ch*shift];

  data = new double*[ch];
  for(int i=0;i<ch;i++){
    data[i] = new double[frame+2];
    memset(data[i],0,sizeof(double)*(frame+2));
  }

  while(!input.IsEOF()){
    length = input.ReadUnit(buf_in,160*ch);
    for (size_t i = 160; i < 256; ++i) {
        buf_in[i] = (short int)0;
    }
    process.stft(buf_in,length,data);
    process.istft(data,buf_out);
    output.Append(buf_out,160*ch);
  }

  for(int i=0;i<ch;i++)
    delete[] data[i];
  delete[] data;

  return 0;
}

Thank you so much for your help again.

I guess  as you did
for (size_t i = 160; i < 256; ++i) {
        buf_in[i] = (short int)0;
    }

padding on the end of the buffer is proper way.
https://www.bitweenie.com/listings/fft-zero-padding/
and if you pad on end of time domain buffer. like
fs = 16000;
t = linspace(0,1,256);

x1 = sin(2*pi*fs*t);
figure;specgram(x1);title('x1');caxis([-80 20])

x2 = zeros(1,256);
x2(1:160) = x1(1:160);

figure;specgram(x2);title('x2');caxis([-80 20])

you can see, though the scale might be different, the struct is maintained.


Line 0:  Parsing error: Cannot find module 'babel-plugin-transform-class-properties'

Describe the bug
(Write your answer here.)
I'm getting this error

Did you try recovering your dependencies?
Yes

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

(paste the output of the command here.)
Steps to reproduce

(Write your steps here:)

Expected behavior

(Write what you thought would happen.)
Actual behavior

(Write what happened. Please add screenshots!)
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

in bash type  npm install --save-dev babel-plugin-transform-class-properties

I found the solution of it just restart again and see no if it not get resolved from it just use therm -rf node_module and use the npm i again or you can also use npm ci for clean install


Using "dom: 'shadow'" option in polymer invalidates the css styles

The polymer documentation states:

shadow. Local DOM is rendered using shadow DOM where supported (this will be the default in the future).

Setting the dom global variable to shadow breaks all the css styles and rules.
window.Polymer = {dom: 'shadow'};

Add ::shadow to nvd3-shared-styles.html selectors fix many issues but some issues such as background of tooltip box aren't fixed.

Fixed at v0.19.0.


Integration tests for Resource sync

thanks @deepankarb :)
same in this PR: what tests should we have had that should have failed for this code change?

@jingtang10 Individually both resource sync and local change management work fine.  Integration tests for resource sync are missing :)
Originally posted by @deepankarb in https://github.com/google/android-fhir/issues/302#issuecomment-795363609
We need to implement integration test for Resource sync.

So by integration test here, we mean instrumentation test which mean using real device? I can push a fix for it in which we'll be verifying if the sync actually takes place via observing the UI

thanks @deepankarb :)
same in this PR: what tests should we have had that should have failed for this code change?

@jingtang10 Individually both resource sync and local change management work fine. Integration tests for resource sync are missing :)
Originally posted by @deepankarb in #302 (comment)
We need to implement integration test for Resource sync.

@jingtang10 @deepankarb
I kind of am working on this (issue number: #380 and #381)
If you don't mind I can take this up and make a PR ASAP.

Not in UI - since the SDK doesn't have any. I think something like the medium tests mentioned here: https://developer.android.com/training/testing/fundamentals#medium-tests
From the above link:

Tests in your app's repository layer, which verify that your different data sources and data access objects (DAOs) interact as expected.


Nuke: freschdesk tickets

fixing prerender publishing workflow
fixing viewer to be set to correct colorspace on start new script
not opening control nuke panes when creating write node group

Families still don't work correctly with "Use existing frames". Frames constantly go to /write folder instead of /render.

Please sort the conflic and we can merge


Memory leak when producing analysis trees

This relates to issue to the slow sorting mentioned in #559
When sorting spice data there appears to be a memory leak at the analysis tree construction stage. GRSISort eats up all the memory in even a 32GB machine, goes into swap and hence slows to a crawl.
We have had this in all the versions of grsisort and TSiLi we have tried. For several different users and several different computers. By turning off tigress it did seem it might be an issue of event/file rather than the sili class. We aren't sure.
/tig/midtig02_data/tiguser/SPICETestAnalysis/SPICETestAugust2015/run35661_000.mid
/tig/midtig02_data/tiguser/SPICETestAnalysis/CalibrationFile.cal

There is no memory leak that I know of, just lots of memory usage based on how root does it's thing. Cal grind says no leak. Vinzenzs is working on our own sorting method rather than roots and reduces memory consumption. Preliminary test show this is a significant improvement.

On Oct 29, 2015, at 11:23 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
This relates to issue to the slow sorting mentioned in #559
When sorting spice data there appears to be a memory leak at the analysis tree construction stage. GRSISort eats up all the memory in even a 32GB machine, goes into swap and hence slows to a crawl.
We have had this in all the versions of grsisort and TSiLi we have tried. For several different users and several different computers. By turning off tigress it did seem it might be an issue of event/file rather than the sili class. We aren't sure.
/tig/midtig02_data/tiguser/SPICETestAnalysis/SPICETestAugust2015/run35661_000.mid
/tig/midtig02_data/tiguser/SPICETestAnalysis/CalibrationFile.cal
—
Reply to this email directly or view it on GitHub.

Well there may not be a "memory leak" in the computing definition, but using >32Gb to sort a 430Mb file suggests to me something is very wrong.

Yeah , we've had this problem in griffin for a while. It happens when we try to time order the data using roots native ordering function. Should be fixed soon by using our own stl container to order.

On Oct 29, 2015, at 10:15 PM, jsmallcombe<EMAIL_ADDRESS>wrote:
Well there may not be a "memory leak" in the computing definition, but using >32Gb to sort a 430Mb file suggests to me something is very wrong.
—
Reply to this email directly or view it on GitHub.

Hmm, ok. Is this a fundamental part of the fragment->analysis event construction?
As for tigress we don't care about time ordering of the events beyond collecting the fragments together from their event ID.

For the 32gb sort on a ~450md file, can you point me towards an account and
file.  If this is true, it sounds like something is seriously setup wrong.
On Oct 30, 2015 12:33 AM, "jsmallcombe"<EMAIL_ADDRESS>wrote:

Hmm, ok. Is this a fundamental part of the fragment->analysis event
construction?
As for tigress we don't care about time ordering of the events beyond
collecting the fragments together from their event ID.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152412717
.

I'll let peter deal with finding a bug. However it is currently fundamental. We order our timestamps and you order your event id. You also can't compare the Midas size to our file size. The data is masked in the Midas file so you can have multiple pieces of information in one 32 bit word. We break that apart which would of course expand the total size it takes. It shouldn't be that bad so something else is going on. We do already know that the tree ordering can be a hog though.

On Oct 29, 2015, at 10:33 PM, jsmallcombe<EMAIL_ADDRESS>wrote:
Hmm, ok. Is this a fundamental part of the fragment->analysis event construction?
As for tigress we don't care about time ordering of the events beyond collecting the fragments together from their event ID.
—
Reply to this email directly or view it on GitHub.

Data files and calibration files for the SPICE data can be found on midtig02 in /data/tiguser/SPICETestAnalysis/
run35661_000.mid is what we've been testing on. It is relatively small and yet still fills up the memory when sorting.
Data are being sorted on belodon and midtig02 (my account and James's), the memory issue is seen on both machines.

Just to clarify 430Mb was the size of the fragment root file

You can print the file to see the uncompressed fragment file size. It is likely over a few GB.

On Oct 30, 2015, at 11:37 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
Just to clarify 430Mb was the size of the fragment root file
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152596861.

Also, if you sort from Midas->fragment->Analysis in one step, root doesn’t do a good job of clearing the memory used for the first step. You can get around it by sorting midas to fragment in one session and then fragment to analysis in another.
This is a problem we have encountered when using 2GB midas files.

On Oct 30, 2015, at 11:37 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
Just to clarify 430Mb was the size of the fragment root file
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152596861.

This particular file is under 2GB uncompressed.  The ttreeindex is ~800MB
in its full read.  The memory usage goes up during the tdetector branch
filling, and is clearly a memory leak.  I just haven't found out who or
what is leaking yet.
On Oct 30, 2015 2:17 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Also, if you sort from Midas->fragment->Analysis in one step, root doesn’t
do a good job of clearing the memory used for the first step. You can get
around it by sorting midas to fragment in one session and then fragment to
analysis in another.
This is a problem we have encountered when using 2GB midas files.

On Oct 30, 2015, at 11:37 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
Just to clarify 430Mb was the size of the fragment root file
—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152596861
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152607377
.

Ok. We ran valgrind not too long ago and didn’t see a leak. But if you actually suspect a leak then I suppose we should try to find it.

On Oct 30, 2015, at 12:20 PM, pcbend<EMAIL_ADDRESS>wrote:
This particular file is under 2GB uncompressed. The ttreeindex is ~800MB
in its full read. The memory usage goes up during the tdetector branch
filling, and is clearly a memory leak. I just haven't found out who or
what is leaking yet.
On Oct 30, 2015 2:17 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Also, if you sort from Midas->fragment->Analysis in one step, root doesn’t
do a good job of clearing the memory used for the first step. You can get
around it by sorting midas to fragment in one session and then fragment to
analysis in another.
This is a problem we have encountered when using 2GB midas files.

On Oct 30, 2015, at 11:37 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
Just to clarify 430Mb was the size of the fragment root file
—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152596861
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152607377
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152608095.

If ROOT deletes a TDetector I think that only deletes the “TTigress” or whatever it may be. I’m not sure we are deleting the hits anywhere, so that might be a good place to look.

On Oct 30, 2015, at 12:20 PM, pcbend<EMAIL_ADDRESS>wrote:
This particular file is under 2GB uncompressed. The ttreeindex is ~800MB
in its full read. The memory usage goes up during the tdetector branch
filling, and is clearly a memory leak. I just haven't found out who or
what is leaking yet.
On Oct 30, 2015 2:17 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Also, if you sort from Midas->fragment->Analysis in one step, root doesn’t
do a good job of clearing the memory used for the first step. You can get
around it by sorting midas to fragment in one session and then fragment to
analysis in another.
This is a problem we have encountered when using 2GB midas files.

On Oct 30, 2015, at 11:37 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
Just to clarify 430Mb was the size of the fragment root file
—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152596861
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152607377
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152608095.

Yeah, I have a valgrind output from this morning.  My suspicion is the
tclonesarray in tigress.  It turns out tclonesarray::clear should really be
tclonesarray::delete, but even with this it is not working "right" yet.
My hope is to get a chance to look again a bit later this afternoon, or
possible just pull the tclonesarray from tigress altogether.
On Oct 30, 2015 2:22 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Ok. We ran valgrind not too long ago and didn’t see a leak. But if you
actually suspect a leak then I suppose we should try to find it.

On Oct 30, 2015, at 12:20 PM, pcbend<EMAIL_ADDRESS>wrote:
This particular file is under 2GB uncompressed. The ttreeindex is ~800MB
in its full read. The memory usage goes up during the tdetector branch
filling, and is clearly a memory leak. I just haven't found out who or
what is leaking yet.
On Oct 30, 2015 2:17 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Also, if you sort from Midas->fragment->Analysis in one step, root
doesn’t
do a good job of clearing the memory used for the first step. You can
get
around it by sorting midas to fragment in one session and then
fragment to
analysis in another.
This is a problem we have encountered when using 2GB midas files.

On Oct 30, 2015, at 11:37 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
Just to clarify 430Mb was the size of the fragment root file
—
Reply to this email directly or view it on GitHub <

https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152596861

.

—
Reply to this email directly or view it on GitHub
<
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152607377

.

—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152608095
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152608455
.

 That would remove potential variables from the problem, as well as make it more consistent with other detectors. I also don’t think we are getting the advantage from the clones anyway.

On Oct 30, 2015, at 12:27 PM, pcbend<EMAIL_ADDRESS>wrote:
Yeah, I have a valgrind output from this morning. My suspicion is the
tclonesarray in tigress. It turns out tclonesarray::clear should really be
tclonesarray::delete, but even with this it is not working "right" yet.
My hope is to get a chance to look again a bit later this afternoon, or
possible just pull the tclonesarray from tigress altogether.
On Oct 30, 2015 2:22 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Ok. We ran valgrind not too long ago and didn’t see a leak. But if you
actually suspect a leak then I suppose we should try to find it.

On Oct 30, 2015, at 12:20 PM, pcbend<EMAIL_ADDRESS>wrote:
This particular file is under 2GB uncompressed. The ttreeindex is ~800MB
in its full read. The memory usage goes up during the tdetector branch
filling, and is clearly a memory leak. I just haven't found out who or
what is leaking yet.
On Oct 30, 2015 2:17 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Also, if you sort from Midas->fragment->Analysis in one step, root
doesn’t
do a good job of clearing the memory used for the first step. You can
get
around it by sorting midas to fragment in one session and then
fragment to
analysis in another.
This is a problem we have encountered when using 2GB midas files.

On Oct 30, 2015, at 11:37 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
Just to clarify 430Mb was the size of the fragment root file
—
Reply to this email directly or view it on GitHub <

https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152596861

.

—
Reply to this email directly or view it on GitHub
<
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152607377

.

—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152608095
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152608455
.

—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152609498.

I agree. The new tigress I gave you guys already has it removed.  The
tclonesarray is really a failed experiment.  It does make the draw command
faster but seems to muck everything else up.
 That would remove potential variables from
the problem, as well as make it more consistent with other detectors. I
also don’t think we are getting the advantage from the clones anyway.

On Oct 30, 2015, at 12:27 PM, pcbend<EMAIL_ADDRESS>wrote:
Yeah, I have a valgrind output from this morning. My suspicion is the
tclonesarray in tigress. It turns out tclonesarray::clear should really
be
tclonesarray::delete, but even with this it is not working "right" yet.
My hope is to get a chance to look again a bit later this afternoon, or
possible just pull the tclonesarray from tigress altogether.
On Oct 30, 2015 2:22 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Ok. We ran valgrind not too long ago and didn’t see a leak. But if you
actually suspect a leak then I suppose we should try to find it.

On Oct 30, 2015, at 12:20 PM, pcbend<EMAIL_ADDRESS>wrote:
This particular file is under 2GB uncompressed. The ttreeindex is
~800MB
in its full read. The memory usage goes up during the tdetector
branch
filling, and is clearly a memory leak. I just haven't found out who
or
what is leaking yet.
On Oct 30, 2015 2:17 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Also, if you sort from Midas->fragment->Analysis in one step, root
doesn’t
do a good job of clearing the memory used for the first step. You
can
get
around it by sorting midas to fragment in one session and then
fragment to
analysis in another.
This is a problem we have encountered when using 2GB midas files.

On Oct 30, 2015, at 11:37 AM, jsmallcombe <
<EMAIL_ADDRESS>wrote:
Just to clarify 430Mb was the size of the fragment root file
—
Reply to this email directly or view it on GitHub <

https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152596861

.

—
Reply to this email directly or view it on GitHub
<

https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152607377

.

—
Reply to this email directly or view it on GitHub <

https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152608095

.

—
Reply to this email directly or view it on GitHub
<
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152608455

.

—
Reply to this email directly or view it on GitHub <
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152609498
.

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152613070
.

Just FYI, while testing the new branch I re-sorted some files with the master branch, and the memory usage for analyzing a 430MB fragment file (created from a 500MB midas file) was 10GB.
Now this is GRIFFIN data, which all (I think?) inherits from TGRSIDetector rather than TDetector directly, which might change some of the behaviour?

"The new tigress I gave you guys" is this referring to the upcoming version we pedestrians don't have yet?

Yes, it is going to come along with the multi-set branch. Can you guys test that branch out? It works very well with GRIFFIN, we just don’t want to merge it until it works with TIGRESS.

On Nov 2, 2015, at 2:09 PM, jsmallcombe<EMAIL_ADDRESS>wrote:
"The new tigress I gave you guys" is this referring to the upcoming version we pedestrians don't have yet?
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-153127203.

Oh good.
Yes, saw that thread, one of us will try and test today or tomorrow.

Awesome. Thanks guys.

On Nov 2, 2015, at 2:34 PM, jsmallcombe<EMAIL_ADDRESS>wrote:
Oh good.
Yes, saw that thread, one of us will try and test today or tomorrow.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-153134158.

I can confirm that this seems to be fixed on the multiset branch, with my TSiLi additions.

I would guess that this is gone now. Please re-open if I am wrong.


Use ZipEntry.CompressionMethodForHeader when writing the header entries

When writing the local/central directory entries in ZipFile, use the CompressionMethodForHeader property of ZipEntry instead of the CompressionMethod property, in order to handle the case where the entry method is WinZipAes.
Add a couple of extra unit tests, which both try to verify using SharpZipLib locally (#317 aside) and with 7-Zip.
refs #439
I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License.

The CompressionMethodForHeader property shouid only differ from the CompressionMethod property for AES encrypted entries, and as you can't presently add those via ZipFile the change should only effect updates to existing files that contain AES encrypted entries.
I don't think there are any situations where this would break anything, given that the current code already breaks such entries when the file is updated?

No, it shouldn't afaik.


fix non-credit filter

What are the relevant tickets?
None.
Selecting 'Non-Credit' at  https://ocw.mit.edu/search/ does not work. This fixes the issue
Description (What does it do?)
We have parameter validation for the ocw search. Unfortunately, the parameter validation needs to be updated when we update the results from the api.
How can this be tested?
Set
SEARCH_API_URL=https://open.mit.edu/api/v0/search/
Run yarn start www
Turn CORS off in your browser
Go to http://localhost:3000/search/
Verify that you can select non-credit
Additional Context
Needing to manually update the possible parameters every time they change isn't great.
Once ocw is migrated to the new search api and https://github.com/mitodl/mit-open/issues/269 is implemented we can get the possible parameters from the client that will be created by https://github.com/mitodl/mit-open/issues/269

Thanks for fixing this! @abeglova
I had changed Non Credit to Non-Credit in ocw-hugo-projects, but I wasn't aware that there was a coupling of this in ocw-hugo-themes.


Decide on the new API namespace

From @georgiana-b on October 16, 2017 6:50
From @nightsh on April 16, 2017 18:59
This is a crazy small issue, I know. But a lot of things on the operations side depend on whether we replace the v1 namespace or create a new, shiny v2.
I'd advocate for the latter, as we might want to keep two APIs up for a while, for a bunch of various reasons. We can discuss this below, if needed, but it's a discussion I'd rather like happening sooner than later.
Copied from original issue: tenders-exposed/elvis-backend#39
Copied from original issue: tenders-exposed/elvis-backend-py#19

Agreed. Let's drop api as requested in #16 and replace v1  with v2.

Ideally we'd have a variable namespace, useful for example in deployments alongside other things (e.g. the frontend, or other app, on the same domain). But since this is a very specific API project, I wouldn't expect people installing it as it were a wordpress instance. I am still more than happy to see all "introductory" namespaces such as /api/ gone.


Eliah Kagan: Watch sattakingfirst.in

Eliah Kagan requests the watch of the watch_keyword sattakingfirst\.in. See the MS search here and the Stack Exchange search here.

sattakingfirst\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Shree in Charcoal HQ


Texture URL

We could add support for serving specific textures from Mojang's textures servers. This would be super simple, and who knows, maybe useful?

I'm not sure what you mean exactly. As I understand it this would be a proxy for http://textures.minecraft.net/texture/<hash>? Why would someone need that?

I have an use case for this - getting rendered head models from texture hashes. I think this issue should be reopened - I could even work on it!

You probably want to start looking here:
https://github.com/crafatar/crafatar/blob/1816b18b1292fca7ae123212b2b516a7532a332a/lib/helpers.js#L325-L326
It gets the texture hash for a user ID, then loads the image from disk or network and uses it to render a 3D model. Shouldn't be easy to modify this for your needs. Feel free to fork, but I don't think enough people would benefit from it to justify merging this in.

I don't think enough people would benefit from it to justify merging this in.

I think I should give a bit of background on why more people might want to use this. Recently Hypixel released their SkyBlock API, containing inventory and auction data. Now - the data is in nbt format and many custom items use minecraft heads for their textures. Being able to get pre-rendered head from the hash would be very useful for people making SkyBlock related stat sites.

Alright. We could probably accept texture hashes in place of UUIDs in the URL.
Texture hashes are a SHA256 hash (in hex) of the image. These are usually 64 characters long, but Mojang cuts of any leading 0s, so they can be shorter. UUIDs are also in hex, but 32 characters.
I guess it's safe to assume that we won't find a hash with 32 leading 0s, so if it matches the RegEx /[0-f]{33,64}/ we can treat it as a hash instead of UUID.
I'll accept PRs.

I'll take a stab at this tomorrow

What ist the status of this?

What ist the state of this?

Haven't had the time to get any real progress

In lib/renders.js, I assume the var exp = {} already has the skin cached? I'm trying to make renders support URL's. Any ideas?

This seems to work. I tried it with a bedrock edition skin and it worked very nicely.

This seems to work. I tried it with a bedrock edition skin and it worked very nicely.

How thought? Bedrock editions don't have UUID, only XUID. Could you link me with what you tried or did?

This seems to work. I tried it with a bedrock edition skin and it worked very nicely.

How thought? Bedrock editions don't have UUID, only XUID. Could you link me with what you tried or did?

Basically, using Geyser/Floodgate Skin API I was able to take the texture ID given by the bedrock player and put it in crafatar

This seems to work. I tried it with a bedrock edition skin and it worked very nicely.

How thought? Bedrock editions don't have UUID, only XUID. Could you link me with what you tried or did?

Basically, using Geyser/Floodgate Skin API I was able to take the texture ID given by the bedrock player and put it in crafatar.
I have another API that was created by a few friends and I that actually does it automatically for the user. It uses mc-heads skin API since I was unaware at the time that crafatar used texture IDs.

Oh? May I know what the geyser skin api link is? Or the documentation to it

This seems to work. I tried it with a bedrock edition skin and it worked very nicely.

How thought? Bedrock editions don't have UUID, only XUID. Could you link me with what you tried or did?

Basically, using Geyser/Floodgate Skin API I was able to take the texture ID given by the bedrock player and put it in crafatar.
I have another API that was created by a few friends and I that actually does it automatically for the user. It uses mc-heads skin API since I was unaware at the time that crafatar used texture IDs.

Oh I see, alright I'll look into it. Thank you

This seems to work. I tried it with a bedrock edition skin and it worked very nicely.

How thought? Bedrock editions don't have UUID, only XUID. Could you link me with what you tried or did?

Basically, using Geyser/Floodgate Skin API I was able to take the texture ID given by the bedrock player and put it in crafatar.
I have another API that was created by a few friends and I that actually does it automatically for the user. It uses mc-heads skin API since I was unaware at the time that crafatar used texture IDs.

Do you have discord or anything, would like to talk to you about a few things?

This seems to work. I tried it with a bedrock edition skin and it worked very nicely.

How thought? Bedrock editions don't have UUID, only XUID. Could you link me with what you tried or did?

Basically, using Geyser/Floodgate Skin API I was able to take the texture ID given by the bedrock player and put it in crafatar.
I have another API that was created by a few friends and I that actually does it automatically for the user. It uses mc-heads skin API since I was unaware at the time that crafatar used texture IDs.

Oh I see, alright I'll look into it. Thank you

Edit: After doing quite some research, I see that I can use the texture ID on mc heads. The issue is that xbox doesn't give a texture ID for every single player unless it's something with the Geyser API for skins. It just said success: true although data was {} .

This seems to work. I tried it with a bedrock edition skin and it worked very nicely.

How thought? Bedrock editions don't have UUID, only XUID. Could you link me with what you tried or did?

Basically, using Geyser/Floodgate Skin API I was able to take the texture ID given by the bedrock player and put it in crafatar.
I have another API that was created by a few friends and I that actually does it automatically for the user. It uses mc-heads skin API since I was unaware at the time that crafatar used texture IDs.

Oh I see, alright I'll look into it. Thank you
Edit: After doing quite some research, I see that I can use the texture ID on mc heads. The issue is that xbox doesn't give a texture ID for every single player unless it's something with the Geyser API for skins. It just said success: true although data was {} .

A few buddies and I managed to get an API working from that here. Xbox itself does not give out anything. Geyser does all the dirty work. It just uses the XUID to find the player. My API does everything automatically and is powered by mc-heads. (Documentation on that here: https://tydiumcraft.tk/docs/skinapi ) Theoretically it should work somewhat the same now with crafatar.

The changes I made do work, but still has some issues. For example the server still sends a request to the Mojang API for a texture. I'm also not sure whether or not it's possible for the server to find out if a texture belongs to a slim skin or not, but for now I added a query parameter to force a slim skin or not.
Please let me know what you think of these changes.

It's been a whilke

You probably want to start looking here:
https://github.com/crafatar/crafatar/blob/1816b18b1292fca7ae123212b2b516a7532a332a/lib/helpers.js#L325-L326
It gets the texture hash for a user ID, then loads the image from disk or network and uses it to render a 3D model. Should be easy to modify this for your needs. Feel free to fork, but I don't think enough people would benefit from it to justify merging this in.

I tried that but failed, do you make multiple canvas's and then combine them into one? is the skin input in a buffer?
Also what's rid in the thing you mentioned?

Anything moving on this?

Doesn't look like that, I am using an endpoint from mc-heads.net to do this now

like

Would you be able to help me to accomplish this?

Anything moving on this?

Doesn't look like that, I am using an endpoint from mc-heads.net to do this now

Would you be able to help me accomplish the same? Discord is OhNo2#8242

Anything moving on this?

Doesn't look like that, I am using an endpoint from mc-heads.net to do this now

Would you be able to help me accomplish the same? Discord is OhNo2#8242

Just go to https://mc-heads.net you can use texture IDs for everything marked as identifier.
Eg. https://mc-heads.net/avatar/{textureid}
Or
https://mc-heads.net/head/525088ac98a7df223ecb2971f6488d14a820d837943ca1ad4d1f15b99bde6c


files structure refactor, add special commands!

Also codebase refactor
A lot of changes in typescript/index.ts
ensure to fix #38
ensure to fix emmet (next pr): enable full support by default, manage sorting

ensure . snippet works
ensure refactor typescript/index.ts, one test

Don't care of integration on ci, anyway it's bettter than what is on main


fix typo in Readme

-Upostgres (without the space) works fine here - what platform and version of PostgreSQL are you using?

Oh, was at work machine. Seems to work on now. May be I misread error message.


add dockerfile and scripts to build image for rust-verification-tools(klee only)

These scripts and dockerfiles is to build rust-verification-tools(klee only) docker image.
The building process almost follows the using-klee doc(three steps, install rust, install klee and install rust-verification-tools) but has some additional steps.(I think it may be essential)
First, the script compiles cargo from source to work as the default cargo for the compiled rustc, so it leads to a stage2 compiling.
Second, the script installs rustup from official scripts and choose stage2 as the default toolchain.
The try-klee example has been added to the image for test use and it can work properly.  However, when I try to follow the example replay input values in doc , there is still one link error. I have mentioned this in #36 .

@googlebot I signed it!

As I know, the common practice is to add current user to docker group to avoid sudo privilege when using docker. run  sudo groupadd docker, sudo usermod -aG docker $USER, then exit current shell and reload. Docker then will no longer need sudo.

Hi Steven,
Sorry it is taking me a while to review this. I haven't used Docker before (beyond trying 'hello world' like examples) so it is taking me a while to understand how Docker is meant to be used. Your PR is really, really helpful for building my understanding.
Thinking about what $USER to use, etc. my colleagues have pointed me at what our sister project developing the "Oak" runtime in Rust has done for Docker:

When they build the Docker image, they pass in the USER, UID, GID that they want to use. script
Within the Dockerfile, they use USER, UID, GID to create a user identical to the user who created the image. Dockerfile

The net effect of which is that if the image reads or writes a file, it does so using exactly the same user as the person that created the image.
I think this is the right way to go so I will push some additional changes that add this (for the rust_verification image). (Probably tomorrow and trying to copy their scripts as closely as possible.)

I have amended the change as follows:

remove the use of the external docker image stevenjiang1110/ubuntu-expect:lates
remove the jjf user associated with that image

This is now fine to merge


Bumped Gradle, Loom, dependencies versions

This PR seems to do a little bit more than just bump versions, like pre-maturely bumping the main mod version and including static analysis. Care to describe why?

I updated the minor version of mod to reflect that this build has slight changes comparing to previous version.
Regarding including static analysis I'm afraid didn't get you properly.
If you meant adding a findbug dependency, I made it because in modern Java versions some annotations were removed (particularly NotNull). I've added findbug dependency to support removed annotations.

See attached review comments

Thanks for your review, I appreciate it. I suppose that I've fixed all by your comments and I made a new commit.


Issues with Members Using Tuppers

I'm new to Tupperbox and have been making a few tuppers for members on my server to use. Upon asking them to try using tuppers, none of them are able to use them but me (I am the server owner). I've messed with different roles to see what works, but nothing is working.

Created tuppers are saved to your user account, not to the server. Other members in the server will have to make an identical tupper, or import tuppers exported using tul!export.

I see, thank you much!


Doesn't work with headless chrome on Windows Subsystem for Linux 2.

When running pyleniumio with python 3.9 on wsl2 ubuntu focal, installing and running chrome from the command line doesn't work.
Specifically, when I create a tests/ directory and try the test_google_search.py hello world example - it gives me this error.
E         (unknown error: DevToolsActivePort file doesn't exist)
E         (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
StackOverflow tells me this error is because we aren't setting chrome options.
https://stackoverflow.com/questions/50642308/webdriverexception-unknown-error-devtoolsactiveport-file-doesnt-exist-while-t

okay, I think this might actually be a feature rather than a bug.
I get an error when running the chained .type('puppies') method,
just asking for py.get("[name='q']") works fine.
*** selenium.common.exceptions.ElementNotInteractableException: Message: element not interactable
So I think this error is saying, 'if you are running a headless browser, then you can not type, which is the system working as intended, PEBKAC.'

@jcoombes you should still be able to type and click on things when in headless mode. Headless does behave slightly differently obviously, but most things should work.
Unfortunately, I don't have a Windows 10 + WSL2 setup so I can't help test or debug this.


Make architecture configurable

What this PR does / why we need it:
This makes the architecture variable configurable. Since we would like to skip the ARM64 builds.

right, put it to draft and will check how to fix this, thanks!

applied the matrix build to the release as well

As discussed offline, the release can't be run in a build matrix, hence added if to the arm64/amd64 steps that check the architecture passed.


Slimefolk can violently shove people if they revert while on the same tile

Description
When a slimeperson reverts from blob form back into humaniod form, while ontop of a person or other solid object, the object gets violently shoved away.
Reproduction
Be sliem
Go into ball form
Go back into human form while on the same tile as another person
The other person will get flung away
Additional context
people are taking blunt damage from walls and getting fused into objects because they are getting flung so hard.

After some personal testing, i was unable to recreate the bug. Perhaps the slime i saw doing the bug had something in their inventory or some other factor. The round was Levi 51802, ill see if i can watch the replay to figure out more information and will post back here.


Cert validation issues

Hi again.
I updated to 2.3.0 to try and test the issues I was having with it setting the read flag, and now I am having a new issue. When I have the validate_cert option set to true I cannot authenticate at all and get the following error. The cert is valid on the mail server. Tested with the same Dovecot based mail server and a Gmail account.
ErrorException: stream_socket_client(): SSL operation failed with code 1. OpenSSL Error messages:
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

Next Webklex\PHPIMAP\Exceptions\ConnectionFailedException: connection failed in vendor/webklex/php-imap/src/Connection/Protocols/ImapProtocol.php:77

Hi @TCURT15 ,
thanks for your report.
Please replace "ssl" here:
https://github.com/Webklex/php-imap/blob/d74fbddfafb8e2d8d296a1b0c7352c7d2b88367a/src/Connection/Protocols/Protocol.php#L155
..with $transport and try again. I assume you don't use the encryption method ssl?
Best regards and thanks for testing,

I am using the ssl encryption option. I tried that and had the same result. I also dumped $transport to ensure it is returning ssl

Alright, and if you comment out this section:
https://github.com/Webklex/php-imap/blob/d74fbddfafb8e2d8d296a1b0c7352c7d2b88367a/src/Connection/Protocols/Protocol.php#L155-L158
..it works?

With validate_cert set to true and that section commented out, I still am unable to connect. It is not a self signed cert. Tried the verify_host option as well.

Then I'm not sure it is actually related to v2.3.0. I currently can't think of anything else regarding the connection setup, which could be responsible.
Please let me know if you get any additional information.
Best regards and many thanks for testing,

Okay, thanks. Would you be able to try with a Gmail account, if you have not already?

Yes, I've tested the latest release on both a Google (gmail) account and on my own debian / postfix server setup.
I can't test for Yahoo, Outlook, GMX and Web - they keep deleting my test accounts -.-
Best regards,

It seems to be working fine on my production server with the validate_cert option set to true, but not on my Mac locally. Not sure what is causing that, but we can close this issue.

Hi @TCURT15 ,
thanks for the followup. You've demonstrated the potential need for additional connection options. I have to think about the integration though.
While googling my way through that ssl error message, I also came across some reports which mentioned a missing certificates in the php-openssl extension.
Best regards,


Either today's article is weird or there's a bug

https://larsgw.github.io/censordle/?day=177 seems to go wrong. I haven't solved it yet though.

It's just the article.


Fix RubyGem link in README

CLA done

@quartzmo Sure thing! got that one as well.

Great catch. Thanks!