Why is expand-to-line disabled?

I was trying to figure out why the selection doesn't expand to the full line, and tracked it down to this commit: https://github.com/aronwoost/sublime-expand-region/commit/eab9e3dc84fb6573a7d0c86b1245573d644f6bb3. Why was that commented out, and would you be open to re-enabling it?

I would assume the reason for this is, that expand to line can break semantical expansions. For example consider the following code (where | is the cursor):
def foo(bar1, bar2, bar3, |bar4,
        bar5, bar6, bar7):
    ...

If we use expand to line this would expand outside the parens, which is not the desired behavior for this case.
However you could checkout and try out https://github.com/aronwoost/sublime-expand-region/pull/59, which solves this issue using sorted closest expansions. I.e. do both expansions and take the expansion, which is inside the other. If they are different take the first one (expand to parens).
I would appreciate feedback and problems for that PR.

Yes, it was causing trouble with other expansion strategies. Also I considered it not-so-important for the typical use case (= my usage). However, I understand that expand-to-line might be super important for some languages.
What language are you using @russelldavis?

I'm mainly using Ruby at the moment, but it's problematic for other languages as well. For example, with this line in javascript:
var fs = require('fs');

Starting on either side of the =, the region stops expanding once it hits the =.
@r-stein, that sounds like a great solution.

You can use cmd-L to select line.

Of course. You can also use cmd-D to select a word. That doesn't mean this plugin should stop selecting words. :)

Sure, I just wanted to provide an alternative.
It all started with cmd-D, right? :smiley:


TSServer outputs NPM warnings at startup

Since TypeScript 2.6.1, TSServer outputs NPM warnings at startup (see actual behavior below). That's problematic since clients expect HTTP-like responses from TSServer stdout.
TypeScript Version:  2.7.0-dev.20171101
Steps to reproduce
npm -g install typescript@next
tsserver

Expected behavior:
No output.
Actual behavior:
The following lines are printed:
npm WARN 2.7 No description
npm WARN 2.7 No repository field.
npm WARN 2.7 No license field.

@micbou Check out typescript@next tomorrow and tell us if this is fixed for you.

I tried with TypeScript 2.7.0-dev.20171102 (I first deleted the ~/.cache/typescript folder) and I am still getting the NPM warnings although the contents of package.json in ~/.cache/typescript/2.7 is
{ "description": "", "repository": "", "license": "" }


[Feature] Flink-Kubernetes-V2 QA

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
This issue will record the problems and testing situations I encountered when testing Flink-Kubernetes-V2
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

cc @wolfboys

I'm not sure I can complete it all. If anyone else is interested, you can follow this issue and participate. I will improve the issue tomorrow.

cc @wolfboys

Thanks for driving it. Sounds good to me~

Check and improve Flink-Kubernetes-V2 backend testing
Jointly debug the front and back ends for testing (run through the basic demo)
and more


Bump cacert.pem version to 2018.01.17

See https://gitlab.com/gitlab-org/gitlab-ce/issues/3251#note_58447984
cc: @stanhu

@ageis Thanks for your contribution! Can you make sure you rebase from current master? There are a number of changes in this MR that are already in master.

@maxlazio Rebased.

Thanks for your contribution @ageis!


Remove shard damage from non-humanoids

About the PR

All mobs that are instances of SimpleSpaceMobBase (mice, rats, roaches, etc.) will no longer be stunned/damaged by sharp objects with this behavior excluding mouse traps.
Humanoid mobs like humans (excluding mobs that already have protection cough vox cough) will still take damage from sharp objects when not wearing footwear.
Why / Balance

Most mobs that aren't humanoids can't wear footwear and most of them are weak enough to die or be sent into critical health from stepping on a sharp object, and since maint dweller mobs like mice and roaches can't even see in the dark they are extremely susceptible to dying from glass shards / sharp trash left in maints without even knowing it was there.
This change would prevent death to a mechanic that doesn't bring much to the table in terms of an interesting challenge. It also makes maintenance shafts a bit safer from random death to mobs that should be able to survive in those areas
Technical details

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Mice, rats and all other non-humanoid creatures will not longer take damage from sharp objects such as glass shards and broken lights, this excludes mouse traps.

Wouldn't this also make them immune to everything else using StepTrigger? Like lava, slipping, glue puddles and so on?

Wouldn't this also make them immune to everything else using StepTrigger? Like lava, slipping, glue puddles and so on? Instead of hardcoding mousetraps as an exception this should have some kind of yaml compatible blacklist dafafield for what types of immunity StepTriggerImmuneComponent gives to its entity.

Good point, I didn't think about those. I'll start working on a whitelist/blacklist

I already have a PR up to fix the system #27684


even smaller browser module

I think just module.exports = btoa (or window.btoa if you want to be a bit more explicit) will get it done for browser support. Here's a very similar reference file from form-data.

module.exports = btoa results in an invocation error in the browser given that it's not called directly from window :') Thanks for reporting though!


Add this to allow gulp to run with NodeJS >= 12

I do not know if this project is still active, but I wanted to give some insight on some things.
I came across some errors trying to build the project with gulp. My version of Node, and probably many others, are greater than the version compatible with gulp 3.9. Here is a solution that doesn't require user's to use a version of Node under 10 or rewrite your existing gulp code for gulp 4.3.
Add a file named: npm-shrinkwrap.json in the root directory with package.json with the following contents:
{     "dependencies": {       "graceful-fs": {           "version": "4.2.2"        }     }   }
Then run npm i to install the depends and it'll automatically update the shrinkwrap file. Now the build command will run smoothly on modern versions of Node.

Did it work?
On Sat, Feb 29, 2020, 8:59 AM Jeremy Boggs<EMAIL_ADDRESS>wrote:

I do not know if this project is still active, but I wanted to give some
insight on some things.
I came across some errors trying to build the project with gulp. My
version of Node, and probably many others, are greater than the version
compatible with gulp 3.9. Here is a solution that doesn't require user's
to use a version of Node under 10 or rewrite your existing gulp code for gulp
4.3.
Add a file named: npm-shrinkwrap.json in the root directory with
package.json with the following contents:
{ "dependencies": { "graceful-fs": { "version": "4.2.2" } } }
Then run npm i to install the depends and it'll automatically update the
shrinkwrap file. Now the build command will run smoothly on modern versions
of Node.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pokemon-essentials/pokemon-essentials/issues/4?email_source=notifications&email_token=AF6YISLR2XEM5IEQ4A3GFEDRFGXOFA5CNFSM4K6FH2X2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IRIUIZQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF6YISIZCNYC2ED4PT5X2SLRFGXOFANCNFSM4K6FH2XQ
.

It did. This just takes the graceful-fs dependency and upgrades it to a version that is compatible with Node 12. My initial error was:
$npm run build

><EMAIL_ADDRESS>build /home/nicocchi/Documents/Development/Projects/pokemon-essentials
> gulp dev-build

fs.js:27
const { Math, Object } = primordials;
                         ^

ReferenceError: primordials is not defined
    at fs.js:27:26
    at req_ (/home/nicocchi/Documents/Development/Projects/pokemon-essentials/node_modules/natives/index.js:143:24)
    at Object.req [as require] (/home/nicocchi/Documents/Development/Projects/pokemon-essentials/node_modules/natives/index.js:55:10)
    at Object.<anonymous> (/home/nicocchi/Documents/Development/Projects/pokemon-essentials/node_modules/graceful-fs/fs.js:1:37)
    at Module._compile (internal/modules/cjs/loader.js:955:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
    at Module.load (internal/modules/cjs/loader.js:811:32)
    at Function.Module._load (internal/modules/cjs/loader.js:723:14)
    at Module.require (internal/modules/cjs/loader.js:848:19)
    at require (internal/modules/cjs/helpers.js:74:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `gulp dev-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/nicocchi/.npm/_logs/2020-02-29T00_25_24_296Z-debug.log

Which is due to versions of Gulp under 4 not compatible with Node 12.


Fixed enum to wrong string cause by misuse GetNameStringByValue and GetNameStringByIndex

This change is

Hi Julee, Thanks for the revision, but can you explain what you are solving and what was the problem? I think the way you are modifying this index by value is not right. Can you explain more? The enums are assigned a value from 0 to N, and that is the index they represent in the enum. Why using an arbitrary value? Also, in that case, we need to cast the value to 64 bits, because they are not 32bits value like the index is.
Regards

No, you can't assume the enum index is the enum value, because enum value can assign to any value!
Check the QualityLevelUE.h:

UENUM(BlueprintType)
enum class EQualityLevel : uint8
{
  Null = 0, // Workarround for UE4.24 issue with enums
  Low    = CARLA_ENUM_FROM_RPC(Low)    UMETA(DisplayName = "Low"),
  // Medium = CARLA_ENUM_FROM_RPC(Medium) UMETA(DisplayName = "Medium"),
  // High   = CARLA_ENUM_FROM_RPC(High)   UMETA(DisplayName = "High"),
  Epic   = CARLA_ENUM_FROM_RPC(Epic)   UMETA(DisplayName = "Epic"),

  SIZE      UMETA(Hidden),
  INVALID   UMETA(Hidden)
};

We can see enum index is not the with enum value ( EQualityLevel::Low index is 1, but the enum value is 0).
And we can't assume assigning enum value is a special case, it's very common.
Unreal Engine documentation also pointed out the issue:

Index is the internal index into the Enum array, and is not useful outside of the Enum system Value is the value set in the Enum Class in C++ or Blueprint Enums can be sparse, which means that not every valid Index is a proper Value, and they are not necessarily equal It is not safe to cast an Index to a Enum Class, always do that with a Value instead Gets the internal index for an enum value.

You say:

Also, in that case, we need to cast the value to 64 bits

This is just according whether the enum is defined to 64 bits int or not, if not, cast to int32_t doesn't matter. Unreal give the parameter with int64_t is because the enum can be defined to 64 bits int, it must support all enum definitions.

This bug should be fixed


(fix) Only getting first page of items

fixes #31

This works!
@doitlikejustin could you merge it into master?

Yes, seems to work. However, not sure what "lek" means? Would merge if that was more clear in the code.

This works!
@doitlikejustin could you merge it into master?

Parse error: syntax error, unexpected '$next_page' (T_VARIABLE), expecting while (T_WHILE) in /var/XXX/wishlist.php on line 166
How i can fix it?

Okay, it will work now for me.
i change the lines from

					$i++;
				}
			}
		}
	}
}

    $next_page = pq('script[data-a-state=\'{"key":"scrollState"}\']')->html();
    preg_match("/\"lastEvaluatedKey\":\"(.*)\"/", $next_page, $next_page_url);
    $lek = $next_page_url[1];

} while (!$lek == '');

to ->

					$i++;
				}
			}

			$next_page = pq('script[data-a-state=\'{"key":"scrollState"}\']')->html();
			preg_match("/\"lastEvaluatedKey\":\"(.*)\"/", $next_page, $next_page_url);
			$lek = $next_page_url[1];
		}
	}
}

while (!$lek == '');

Hey @doitlikejustin , can this please be merged if the fix still works?


onreorderfiles Event is not triggering

Summary
Hello, thank you for the amazing library! I have an issue with reorderfiles event it's not trigger whenever I re-order the items. Other events are working well without any issue. Tried this with Firefox and faced with same issue.
How to reproduce
<input id="images" class="filepond-custom-container" />

<script>
$('#images').filepond({
        name: 'chapter_images[]',
        allowMultiple: true,
        storeAsFile: true,
        required: true,
        allowReorder: true,
        itemInsertLocation: 'after',
});

// Working well
$('#images').on('FilePond:removefile', function (e) {
        console.log('remove is triggered', e);
});

// Not working
$('#images').on('FilePond:onreorderfiles', function (e) {
        console.log('the collection is just being reordered', e);
});
</script>

Expected behaviour
Event should be triggered.
Additional information

Environment
Version

OS
MacOS Monterey

Device
Mac Mini M1

Browser
Chrome Version 95.0.4638.69 (Official Build) (arm64)

It's reorderfiles instead of onreorderfiles
https://codesandbox.io/s/filepond-reorder-9v9bt?file=/src/index.js

But it written as onreorderfiles the current documentation.

Correct me if I'm wrong. Because I tried to do it with plain javascript as written (which is onreorderfiles) and also not working.

I think that is a typo, looking into it.

Fix the typo, should indeed be activefile and reorderfiles updated the codesandbox demo as well.


TestPeriodic fails: len(actions) = 0, expected >= 1

via semaphore,
2016-07-26 19:56:41.103215 N | etcdserver: Starting auto-compaction at revision 1
2016-07-26 19:56:41.103422 N | etcdserver: Finished auto-compaction at revision 1
2016-07-26 19:56:41.242566 N | etcdserver: Starting auto-compaction at revision 13
2016-07-26 19:56:41.242635 N | etcdserver: Finished auto-compaction at revision 13
2016-07-26 19:56:41.374956 N | etcdserver: Starting auto-compaction at revision 25
2016-07-26 19:56:41.375034 N | etcdserver: Finished auto-compaction at revision 25
2016-07-26 19:56:41.791289 N | etcdserver: Starting auto-compaction at revision 25
2016-07-26 19:56:41.791354 N | etcdserver: Finished auto-compaction at revision 25
2016-07-26 19:56:41.947325 N | etcdserver: Starting auto-compaction at revision 1
2016-07-26 19:56:41.947393 N | etcdserver: Finished auto-compaction at revision 1
2016-07-26 19:56:42.134529 N | etcdserver: Starting auto-compaction at revision 13
2016-07-26 19:56:42.134619 N | etcdserver: Finished auto-compaction at revision 13
2016-07-26 19:56:42.278163 N | etcdserver: Starting auto-compaction at revision 25
2016-07-26 19:56:42.278234 N | etcdserver: Finished auto-compaction at revision 25
2016-07-26 19:56:42.709166 N | etcdserver: Starting auto-compaction at revision 25
2016-07-26 19:56:42.709414 N | etcdserver: Finished auto-compaction at revision 25
--- FAIL: TestPeriodic (10.13s)
    compactor_test.go:51: len(actions) = 0, expected >= 1
2016-07-26 19:56:53.284981 N | etcdserver: Starting auto-compaction at revision 25
2016-07-26 19:56:53.285066 N | etcdserver: Finished auto-compaction at revision 25
FAIL

@heyitsanthony Happened again?
Running unit tests...
ok  	github.com/coreos/etcd/auth	2.785s	coverage: 44.2% of statements
ok  	github.com/coreos/etcd/client	1.710s	coverage: 41.3% of statements
ok  	github.com/coreos/etcd/clientv3	7.113s	coverage: 16.8% of statements
ok  	github.com/coreos/etcd/clientv3/naming	1.399s	coverage: 75.0% of statements
2016-08-11 15:16:05.787061 N | etcdserver: Starting auto-compaction at revision 1
2016-08-11 15:16:05.787227 N | etcdserver: Finished auto-compaction at revision 1
2016-08-11 15:16:05.919183 N | etcdserver: Starting auto-compaction at revision 13
2016-08-11 15:16:05.919251 N | etcdserver: Finished auto-compaction at revision 13
2016-08-11 15:16:06.062111 N | etcdserver: Starting auto-compaction at revision 25
2016-08-11 15:16:06.062183 N | etcdserver: Finished auto-compaction at revision 25
2016-08-11 15:16:06.457836 N | etcdserver: Starting auto-compaction at revision 25
2016-08-11 15:16:06.457909 N | etcdserver: Finished auto-compaction at revision 25
--- FAIL: TestPeriodic (10.12s)
	compactor_test.go:54: len(actions) = 0, expected >= 1
2016-08-11 15:16:16.960200 N | etcdserver: Starting auto-compaction at revision 25
2016-08-11 15:16:16.960258 N | etcdserver: Finished auto-compaction at revision 25
2016-08-11 15:16:17.092411 N | etcdserver: Starting auto-compaction at revision 1
2016-08-11 15:16:17.092488 N | etcdserver: Finished auto-compaction at revision 1
2016-08-11 15:16:17.224574 N | etcdserver: Starting auto-compaction at revision 13
2016-08-11 15:16:17.224639 N | etcdserver: Finished auto-compaction at revision 13
2016-08-11 15:16:17.366894 N | etcdserver: Starting auto-compaction at revision 25
2016-08-11 15:16:17.366959 N | etcdserver: Finished auto-compaction at revision 25
2016-08-11 15:16:17.768511 N | etcdserver: Starting auto-compaction at revision 25
2016-08-11 15:16:17.768580 N | etcdserver: Finished auto-compaction at revision 25
FAIL
coverage: 89.7% of statements

https://semaphoreci.com/coreos/etcd/branches/master/builds/760

--- FAIL: TestPeriodic (10.25s)
	compactor_test.go:57: len(actions) = 0, expected >= 1
2016-08-27 18:56:34.426012 N | etcdserver: Starting auto-compaction at revision 25
2016-08-27 18:56:34.426086 N | etcdserver: Finished auto-compaction at revision 25
FAIL

Happened again? https://semaphoreci.com/coreos/etcd/branches/pull-request-6244/builds/11

https://semaphoreci.com/coreos/etcd/branches/master/builds/1472

Really nothing we can do there. The vm just stopped for 10 seconds:
2017-01-23 18:20:03.994234 N | compactor: Starting auto-compaction at revision 1
2017-01-23 18:20:03.994288 N | compactor: Finished auto-compaction at revision 1
2017-01-23 18:20:04.141931 N | compactor: Starting auto-compaction at revision 13
2017-01-23 18:20:04.141993 N | compactor: Finished auto-compaction at revision 13
--- FAIL: TestPeriodic (10.42s)
	compactor_test.go:57: len(actions) = 0, expected >= 1
2017-01-23 18:20:14.704074 N | compactor: Starting auto-compaction at revision 25
2017-01-23 18:20:14.704149 N | compactor: Finished auto-compaction at revision 25

There is the missing 10 seconds between last compaction and the previous one. Cannot reproduce on my local evn either.
I suggest to just close this issue. Or increase timeout up to 20 seconds if we really care.

The 10s could be from rg.Wait(1) timing out (5s), followed by the timeout in compactable.Wait(1) that's throwing the error (another 5s). I don't think it's the VM.

@heyitsanthony So you think rg.Wait and compactable.Wait actually blocks things? I looked at the code, wait only tries to receive from chan, not sending or waiting.

They're using stream recorders, so there's a 5s timeout: https://github.com/coreos/etcd/blob/master/pkg/testutil/recorder.go#L115. The only claim here is the rg.Wait(1) never receives the event it expects, and missing that event can cascade down to the compactable.Wait(1) missing whatever event it expects and timing out, and that's 10s. rg.Wait(1) probably needs an error check at least.
If the VM hangs for 5s, then it'll also cause this error, but the RecorderStream code is all over the place, so I'd expect more failures like this in other tests.

@heyitsanthony It is strange enough since the event actually sent after 10 second
it prints out this after 10 seconds. So I feel the VM got stuck.
2017-01-23 18:20:14.704074 N | compactor: Starting auto-compaction at revision 25
2017-01-23 18:20:14.704149 N | compactor: Finished auto-compaction at revision 25

Fixed by #7632 again.


Inconsistent updates

Since Nov. 7th the updates from the sensor are very sparse. I would guess it comes from fitx itself, because they're changing their software right now

You're right, I noticed it yesterday as well. There's nothing I can do about it because the sensor relies on the data which is published by fitx on their website.

Yes this is a rather strange behavior. I noticed that too. Sometimes the graphs show up, sometimes they don't. This is how the graph in my gym looks like:

But at least for my gym starting yesterday around 6 pm CET the updates are happening more frequently again.

As the updates seem to work again I'm closing this issue. I also added a note to the README in release 0.0.3 with the info that for some locations this won't work.
Thanks @xrzldzlx for opening the issue tho 🙂


Allow setting textdomain manually

First off thank you very much for the github action. I already implemented it in our plugin boilerplate CI: https://github.com/JUVOJustin/wordpress-plugin-boilerplate
However when the workflow clones the repo with a simple
- uses: actions/checkout@v4
And the repository has a different name than the textdomain configured in the plugin header, the pipeline seems to use the folders name inside the github action which is the repo name by default.
Example:
Repo: my-awesome-plugin
Textdomain: awesome-plugin
Result:
Mismatched text domain. Expected 'my-awesome-plugin' but got 'awesome-plugin'.
By passing the expected textdomain to the action this could be solved.

You could also just do
- name: Checkout repository with correct slug
  uses: actions/checkout@v4
  with:
    path: 'awesome-plugin'

No need to reimplement this in this action :)

@swissspidy  I have a similar issue and your trick doesn't work. My plugin is availabe on "/dist", and it's name is "my-plugin".
with the following config:
name: 'WP plugin check'
on:
  push:
    branches: "*"
  pull_request:
jobs:
  standard:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout
      uses: actions/checkout@v4
      with:
        path: 'my-plugin'

    - name: Run plugin check
      uses: wordpress/plugin-check-action@v1
      with:
        build-dir: './dist'
        exclude-directories: 'vendor,.wordpress-org'

I get the following github error:
ℹ Starting 'wp plugin list-check-categories' on the cli container.  name	slug General	general Plugin Repo	plugin_repo Security	security Performance	performance Accessibility	accessibility ✔ Ran wp plugin list-check-categories in 'cli'. (in 0s 484ms) ℹ Starting 'wp plugin get dist --field=requires_plugins' on the cli container.  Error: The 'dist' plugin could not be found. ✖ Command failed with exit code 1 Command failed with exit code 1 Error: Process completed with exit code 1.
What should I do?

I found a similar issue with the WP plugin, which could be resolved with --slug=my-plugin apparently.

Setting path: 'my-plugin' of course does not work if your actual built plugin file is in a differently named subfolder and you pass that one to Plugin Check.
I will consider adding for --slug, but I worry that it will lead to issues with accidentally hiding legit issues. So it will need to be documented well.
In the meantime Irecommend just renaming your folder.
  - name: Build plugin
    run: |
      mv ./dist ${{ runner.temp }}/my-plugin

  - name: Run plugin check
    uses<EMAIL_ADDRESS>    with:
      build-dir: ${{ runner.temp }}/my-plugin

@swissspidy Thanks, it worked out perfectly ;)


⚠ Auth API Endpoint has degraded performance

In e482b6e, Auth API Endpoint (https://auth.roblox.com) experienced degraded performance:

HTTP code: 503
Response time: 4542 ms

Resolved: Auth API Endpoint performance has improved in 6dfadb0.


Design Updates

Just some minor updates to the design. @EricJFisher Let me know if something is wonky on the solution branch. You can just cherry-pick this commit, if you want to test it out there.

Everything looks good.


Applying directive dynamically

I'm submitting a ...  (check one with "x")
[x] feature request

Expected behavior
No way of attaching directives dynamically, suppose I want to use this third party library of masking https://www.npmjs.com/package/angular2-text-mask, I can't use it, except with the change in the input template.
I should be able to add it using field configuration. like ngModelAttrs in angular-formly.

Thanks for your work on this.
Do you have any progress on this feature ? Dynamic templates looks very hard in ng2. Maybe the ComponentFactoryResolver can be used to create dummy component dynamically for a given template while the formly module would expose a static method for registering all dynamic component to its entryComponent section.

not sure if there is a clean way for this right now, we should wait until https://github.com/angular/angular/issues/11716 is implemented

I'm going to close this issue since it's not actionable right now, we'll reopen this once fixed in angular side.

Is this possible now?  It would be great to be able to apply directives using formly

@AshMcConnell not possible, Angular doesn't support that yet.


Custom JDWP transports

This is going to be a brain dump of thoughts. Currently, there are two stock implementations of the Java Debug Wire Protocol (JDWP) transport layer: dt_socket used to communicate over a TCP/IP socket  and dt_shmem (Windows-only) used to communicate via a shared memory region.
I have never personally used the dt_shmem option, but I have made extensive use of the dt_socket transport implementation as I'm sure many others have as well. While the TCP option is nice on its own to either listen for or attach to a remote debugger, there are a variety of other higher-level protocols that could be used to communicate. My thoughts jump to websockets and ZeroMQ. Heck, for experimentation, you could throw HTTP into the mix, although you would still need to encode and decode command packets, but the thought of having HTTP or websockets over TLS sounds interesting.
In fact, an old use case I had for this was when I was working with Apache Spark. Being able to have a debug port exposed on each of the executors so I could have a distributed debugger would be quite handy. Sure, you can do this now by having a debugger listen with a forwarded port and have all of the executors attach to it, but there is no re-attach (that I'm aware of) in case one of the executors has a hiccup.
Another possibility this opens up is the ability to bind to a random, open port using 0 as the port number and have the transport layer phone in assigned port. Essentially, add a callback to a RESTful endpoint, a websocket, database, or anything else. Rather than risking the race condition of looking up an open port and then feeding it to a new process - hoping that the port isn't filled in-between - a new process could be started up that finds and binds to an open port with no race condition.
I think the transport layer (and JDWP agent) is an interesting area that has not received much attention. Ideally, I'd love for this to be entirely in Java, but I think at minimum the transport layer must be a library that can be loaded by the built-in JDWP agent. If we could create a custom agent with transport bundled in a jar and load it, that would provide a cleaner loading and distribution mechanism instead of a library.
Some links I've looked through while researching:

http://docs.oracle.com/javase/7/docs/jdk/api/jpda/jdi/com/sun/jdi/connect/spi/TransportService.html (interface for transport layer on the debugger side; this can be written in Java, I believe)
https://github.com/dmlloyd/openjdk/blob/jdk7u/jdk7u/jdk/src/share/classes/com/sun/tools/jdi/SocketTransportService.java (Java implementation of debugger socket transport service)
https://github.com/dmlloyd/openjdk/blob/jdk7u/jdk7u/jdk/src/share/transport/socket/socketTransport.c (Java 7's TCP socket transport layer)
https://github.com/dmlloyd/openjdk/blob/jdk7u/jdk7u/jdk/src/share/back/debugInit.c (starting point for JDWP agent, I think)
http://docs.oracle.com/javase/7/docs/technotes/guides/jpda/jdwpTransport.html (JDWP transport layer interface documentation for C/C++)
http://docs.oracle.com/javase/7/docs/technotes/guides/jpda/jdwp-spec.html (JDWP protocol packet details)
http://javabeat.net/introduction-to-java-agents/ (writing a Java agent using Java, could be useful if we could write the transport layer in Java somehow or bundle native libraries in a jar that this agent would load as a resource)

If we have to go the JNI route, here are some helpful docs:

http://www.ibm.com/developerworks/java/tutorials/j-jni/j-jni.html (tutorial for writing a basic JNI library)
http://docs.oracle.com/javase/7/docs/technotes/guides/jni/spec/jniTOC.html (main specification of writing JNI code)
http://www.ibm.com/developerworks/library/j-jni/index.html (JNI best practices)
https://www.adamheinrich.com/blog/2012/12/how-to-load-native-jni-library-from-jar/ (guide on loading a JNI library bundled in a jar)
http://stackoverflow.com/questions/2937406/how-to-bundle-a-native-library-and-a-jni-library-inside-a-jar (stack overflow that pointed me to the guide above)
https://github.com/adamheinrich/native-utils (MIT-license library to do the work for you, from author of the guide above)

Found a good doc explaining the process: http://docs.oracle.com/javase/7/docs/technotes/guides/jpda/jpda_spis.html
Specifically, the section Developing a TransportService where it describes

Another example arises in enterprise environments where an Integrated Development Environment (IDE) implementer wishes to support debugging over a non-Sun provided transport. For example an IDE may wish to provide the option of debugging over a secure connection using TLS/SSL.

In this example the IDE implementer develops a transport library using the jdwpTransport interface. This allows the debuggee to use the new transport. On the debugger-side the IDE implementer has a choice. One option is to develop and deploy a TransportService implementation. This option would allow the new transport to be used for remote debugging.

Links for the C-level jdwpTransport needed for the backend (the debuggee) include http://docs.oracle.com/javase/7/docs/technotes/guides/jpda/jdwpTransport.html
And links for the Java TransportService and Connector needed for the frontend (the debugger) include http://docs.oracle.com/javase/7/docs/jdk/api/jpda/jdi/com/sun/jdi/connect/spi/package-summary.html.

Am I the only one excited about this stuff? The option for providing a websocket or HTTP interface on top of the debugger wire protocol seems pretty nifty. Browser-based debuggers, anyone?

I'm excited!


html being rendered inside a 'pre' tag when 'X-Content-Type-Options "nosniff" always' is enabled

This is happening in Chrome 64 and Epiphany 3.26. However it is not happening in Firefox 58. I'm using nginx:latest and php:fpm inside of Docker.
'X-Content-Type-Options "nosniff" always' is enabled:

'X-Content-Type-Options "nosniff" always' is disabled:

This is my /etc/nginx/conf.d/default.conf (really the only modification I made was to "fastcgi_pass"):
server {
    listen 80;
    listen [::]:80;

    server_name localhost;
    set $base /var/www/html;
    root $base/public;

    # index
    index index.php;

    # $uri, index.php
    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    # security headers
    add_header X-Frame-Options "SAMEORIGIN" always;
    add_header X-XSS-Protection "1; mode=block" always;
    add_header X-Content-Type-Options "nosniff" always;
    add_header Referrer-Policy "no-referrer-when-downgrade" always;
    add_header Content-Security-Policy "default-src * 'unsafe-eval' 'unsafe-inline'" always;

    # . files
    location ~ /\. {
        deny all;
    }

    # assets, media
    location ~* \.(?:css(\.map)?|js(\.map)?|jpe?g|png|gif|ico|cur|heic|webp|tiff?|mp3|m4a|aac|ogg|midi?|wav|mp4|mov|webm|mpe?g|avi|ogv|flv|wmv)$ {
        expires 7d;
        access_log off;
    }

    # svg, fonts
    location ~* \.(?:svgz?|ttf|ttc|otf|eot|woff|woff2)$ {
        add_header Access-Control-Allow-Origin "*";
        expires 7d;
        access_log off;
    }

    # gzip
    gzip on;
    gzip_vary on;
    gzip_proxied any;
    gzip_comp_level 6;
    gzip_types text/plain text/css text/xml application/json application/javascript application/xml+rss application/atom+xml image/svg+xml;

    # handle .php
    location ~ \.php$ {
        try_files $uri =404;

        # fastcgi
        #fastcgi_pass                unix:/var/run/php/php7.2-fpm.sock;
        fastcgi_pass                php:9000;
        fastcgi_index               index.php;
        fastcgi_split_path_info     ^(.+\.php)(/.+)$;
        fastcgi_param               SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param               PHP_ADMIN_VALUE open_basedir=$base/:/usr/lib/php/:/tmp/;
        fastcgi_intercept_errors    off;

        fastcgi_buffer_size             128k;
        fastcgi_buffers                 256 16k;
        fastcgi_busy_buffers_size       256k;
        fastcgi_temp_file_write_size    256k;

        # default fastcgi_params
        include fastcgi_params;
    }
}

# subdomains redirect
server {
    listen 80;
    listen [::]:80;

    server_name *.localhost;

    return 301 https://localhost$request_uri;
}

Hi @dupkey!
It looks like an issue with MIME settings.
Is this line present in your nginx.conf file: include mime.types;?
Also could you please attach the output of curl -vvv http://localhost command?

Thanks @valentinxxx for your help!
Yes, I have include /etc/nginx/mime.types; in my nginx.conf
Here is the output of curl -vvv http://localhost:8081:
* Rebuilt URL to: http://localhost:8081/
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8081 (#0)
> GET / HTTP/1.1
> Host: localhost:8081
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.13.8
< Date: Mon, 12 Mar 2018 19:34:26 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< X-Powered-By: PHP/7.2.2
< Set-Cookie: PHPSESSID=a211902b28a1ca03c9486198c40cb3ba; path=/
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< Referrer-Policy: no-referrer-when-downgrade
< Content-Security-Policy: default-src * 'unsafe-eval' 'unsafe-inline'
<
<!doctype html>

    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
    <title>Create An Account</title>
    <meta name="description" content="A single email and password gets you into everything."/>
    <link rel="stylesheet" href="/assets/css/style.min.css">
    <link rel="apple-touch-icon" href="/assets/img/apple-touch-icon.png">
    <link rel="shortcut icon" href="/assets/img/favicon.ico">

Create An Account

                        <form method="post"  id="register" novalidate>

          Full Name
          <input type="text" name="name" id="name" class="form-control">

          E-mail
          <input type="email" name="username" id="username" class="form-control">

          Password
          <input type="password" name="password" id="password" class="form-control">

          By creating an account, you agree to the Terms of Service and Privacy Policy.

        <input type="hidden" name="csrf_name" value="csrf5aa6d64280b88">
        <input type="hidden" name="csrf_value" value="a34bbefa89e2a5ef7c2fe6d77460a3e6">
        <button type="submit" class="btn btn-primary btn-block">Create</button>

Already have an account? Sign In

      </form>

* Connection #0 to host localhost left intact

The Content-Type and Content-Length headers are missing from the response.
This output is generated with PHP (X-Powered-By: PHP/7.2.2), are you using a framework for that?
Either the PHP script strips the headers or something is misconfigured on PHP(-FPM). (Maybe you've set an empty Content-Type header?)
It should be fine with a basic html file.

I'm using Slim 3 with the Twig-view package.
https://github.com/slimphp/Slim
https://github.com/slimphp/Twig-View
At some point I was told to set 'addContentLengthHeader'=> false in the Slim settings which would allow the web server to send the content-length header. I can just set that to true and solve one problem.
I'm looking at Twig-view now to see if I have a misconfiguration.

I can safely say this issue is on my end and is regarding the Http\Response that I'm creating. Sorry to take up your time with this!


Run bun in CI

I wish we had allow-failure to make this more reasonable, but bun is getting stabler so this may be okay.

As of 1.0.17, this hangs: bun run --bun test --no-lint

Actually, it's not hanging, it's just really, really slow. It definitely worked before:

I tried doing npx<EMAIL_ADDRESS>to go back a few versions but apparently bun mistakenly reexecs my global install and runs 1.0.17 again. Even happens when I use downloaded binaries. If I remove my global install, it just runs node which is not helpful, even when I symlink it into $HOME/.local/bin to get it back into PATH.
Resorting to explicitly globally installing bun ... I can bisect to this having changed between v1.0.7 and v1.0.8. v1.0.7 makes progress, but v1.0.8's CPU usage falls down to nothing.
@Jarred-Sumner do you like to get nerd sniped? 😄

Still broken in 1.0.18. I'll try to file a bug.


Ghc921 basement

See also https://github.com/haskell-foundation/foundation/issues/563.

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Sorry, wanted to create a PR against haskell-updates.


Add explicit functions for settle, withdraw, and complete. Add explicit types and states for the pending swaps.

    enum PendingSwapType {Null, TokenToSynth, SynthToToken, TokenToToken}
    enum PendingSwapState {
        Waiting,
        ReadyToSettle,
        Settled,
        PartiallyCompleted,
        Completed
    }

Above enums are used for storing the types and states of all pending swaps.
In case of TokenToSynth swap, any user can call completeToSynth(uint256 itemId) to settle the synth and withdraw to the respective owner.
In case of SynthToToken or TokenToToken swap, only the owner of the itemId can call below function to settle the synth and swap it to the requested token.
function completeToToken(
        uint256 itemId,
        uint256 swapAmount,
        uint256 minAmount,
        uint256 deadline
    )

calcTokenToSynth -> tokenToSynth -> after 6 minutes, call completeToSynth.
calcSynthToToken -> synthToToken -> after 6 minutes, call completeToToken  or/and withdraw with desired amounts.
calcTokenToToken -> tokenToToken -> after 6 minutes,  call completeToToken  or/and withdraw with desired amounts.


Compatibility with shopkeeper

When you hit a villager generated with the plugin shopkeeper, it will attack you.

Fixed in the 4.4 updatr

Fixed in the 4.4 update!


Update Documentation in Header Component

Issue Title: Update Documentation in Header Component
Issue Description:
Ensure that the Header component's usage is well-documented, and add comments to improve code readability.
Tasks:
Review the component's documentation and comments.
Update and improve documentation where necessary.
Add comments to clarify the purpose of different parts of the code.
Acceptance Criteria:
The component's documentation is updated and accurate.
Code comments enhance code readability and understanding.

Hey @Curtis-Thomas can you please assign me this issue Just wanna confirm that this issue deals with the Header.js file and I am suppose to add comments and improve code readability right?

@eshan-one I will assign, yes that is correct, comment and clean up the code only. No added functionality.

Thanks!✌


Full-Length video summary generation idea

The idea is to have ChatGPT create a summary of each part of a video that is sent in segments. At the end, the extension will prompt the IA to combine all of these summaries to create a full-length video summary.

Hey @kazuki-sf, great work 👍🏻 . do you still plan to support this extension?
suggestion: when the user clicks the AI summary button, just open a new openai tab for each 15k chunk instead of just 1 tab. only click the send button for the first tab though, otherwise:

this way the user would only have to switch to next tab and hit send (for each additional tab)
a "smarter" way would be to work with only 1 chatgpt tab and wait for it to finish before auto sending the next chunk. but error handling (maybe chatgpt is too busy and bails) would be tricky, so I would go for the first option since it's easy to implement and the UX would be good

It seems like current solution was applied to skip chunks in between, I think indeed your proposed solution would be better, I can try to implement it with similar function waiting for response then sending next chunk:
https://github.com/7flash/AutoChatGPT/blob/b8679a9ab16c97e64c952d9ddfebfbed0d575754/content.js#L56


poor search experiences

Here’s a quick summary from back when I was looking at the crosswalk docs…
Searching from within the registry
“AWS” results:

:white_check_mark: AWS Package from registry
:white_check_mark: AWS-native package from registry
:question: AWS-IAM package from registry (not actively supported)

“Awsx” results:

Only show awsx in registry, not crosswalk
No crosswalk guide link

:x: “Crosswalk” results only show “Crosswalk for Kubernetes” package (unmaintained) - no AWSx or EKS or guide

Search from within the docs

“AWS” returns same results as above

“Awsx”
Awsx package

Pulumi crosswalk for aws guide
Blog post
Typescript-only SDK docs (this should probably not exist any more)

“Crosswalk”

“Crosswalk for AWS” guide
“Crosswalk for Kubernetes” guide
“Crosswalk for Kubernetes” package
Blog posts
:x: No link to AWSx or EKS in the registry

I've read this issue a few times now, and I'm afraid I don't quite understand all that it's saying.
@danielrbradley if you have a few, would you mind fleshing out what you were expecting vs. what you saw here so I can be sure what we're building addresses everything properly?

@cnunciato here's the original doc where this was taken from which might give better context:
https://docs.google.com/document/d/1dRR7zJoP_EM-nSsnVK9LfdJStCW_q_GNWV2veLvGKhI

"AWS” results:
✅ AWS Package from registry
✅ AWS-native package from registry
❓ AWS-IAM package from registry (not actively supported)

All right I think we're good here -- queries for aws surface the AWS tutorials and guides (in Docs) and AWS Classic and Native (in Registry), in that order.

“Awsx” results:
Only show awsx in registry, not crosswalk
No crosswalk guide link

I'm assuming this means it's a bug that "awsx" doesn't yield the AWS Guides. This is still happening because there's a lot of content containing "awsx" in the title/H1 tags, which rank highly in search, so the content we want to promote (which is lacking these terms in the titles) is getting outranked.
As a temporary measure, we can manually promote these pages in results (PR in the works now), but we'll probably want to consider putting "Crosswalk" and/or "AWSx" in the titles or H1 tags to better align our content with queries.


Mistakes in Row-Only Attention ?

https://github.com/lucidrains/global-self-attention-network/blob/aa0b7d14f384df8fa85f5e904ed03dfc58e78e7d/gsa_pytorch/gsa_pytorch.py#L79
It seems there are dimension errors in row-only attention. I think the right version may be as below:
Py = einsum('xir,rd->xid', Iy, self.rel_columns)
# Sy = einsum('ndxy,xid->nixy', q, Py)
Sy = einsum('ndxy,yid->nixy', q, Py)
# rel_pos_out = einsum('nixy,neiy->nexy', Sy, Yh)
rel_pos_out = einsum('nixy,nexi ->nexy', Sy, Yh)

Could you please check it?

@spyflying yes, you are right! fixed in the latest!


docs: security office hour meeting minutes 2024-06-20

Description
Adding the security office hour meeting minutes for 2024-06-20.

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

LGTM, page could be build and info´s are related to consortia env...
Maybe marking theese info´s as former GitHub Organisation Catenax-ng without mentioning the to be "read-only" org...
... just a little reminder to you @RoKrish14 with committer permission you could create a little branch directly within the upstream repo on https://github.com/eclipse-tractusx/eclipse-tractusx.github.io makes it a bit easier to validate the changes to our meeting minutes section.

The changes are placed and thanks @FaGru3n for the hint.
I will do so for the next meeting minutes.


IRCTC 2.0 Project

IRCTC 2.0 has been accomplishes.

Close #2038

Checklist:

[✅] I have mentioned the issue number in my Pull Request.
[✅] I have commented my code, particularly in hard-to-understand areas
[✅] I have created a helpful and easy to understand README.md

https://codepen.io/schandru/pen/WxYMaP
This is a copied code, please follow the instructions carefully


ComboBox and Flyouts render under customed titlebar

Describe the bug
Flyouts and other control that render in a PopupRoot doesn't respect the
AppTitlebar.ExtendsContentIntoTitleBar
AppTitlebar.SetDragRectangles
API settings.
For example:

The redline shown above indicate the boundary of the DragRect and clickable area.
However, combobox and other control can render under the titlebar so that make the popup partially unreachable.

Steps to reproduce the bug
Just do as I described above.
Expected behavior
There should be some API to change the so-called Clickable area programmatically.
And Popup should aware to that.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.1.4
Windows app type

[ ] UWP
[X] Win32

Device form factor
Desktop
Windows version
Windows 11 (21H2): Build 22000
Additional context
No response

appwindow titlebar and winui 3 controls are not aware of each other like how winui 3 custom titlebar and controls are somewhat aware of each other. We are working for unification of both titlebar effort. Once done, then this bug will be fixed.
Keeping it open for tracking

Thanks for your explanation, by the way is there any workaround currently? @pratikone

@ojhad / @ranjeshj  is there a way to override flyout dimensions so that it doesn't slip under the custom titlebar ? the user is using appwindow titlebar (and not winui 3 custom titlebar)

2. Add Loaded and Unloaded event handlers to a FrameworkElement contained with in the flyouts, to detect when the flyout is opened and closed.

Why not hook Opened and Closed event? Or are they equivalent?

Oh, I see, Flyouts aren't FrameworkElements

@DHancock Anyway to detect ComboBox's droplist?

According to https://github.com/microsoft/microsoft-ui-xaml/discussions/8638, I'm comment this to make this issue tracked.


Support remote SQL queries

Goal is to support having connections to remote SQL databases at least for T-SQL and PostgreSQL.

Should include an external YAML config that can be passed as an argument to include permissions. This file should stay outside of the versioned system.


panic from built-in function leaves Thread in a bad state

This is the test code:
https://go.dev/play/p/_xtHd5Mb3nB
package main

import (
	"fmt"
	"log"

	"go.starlark.net/starlark"
)

func check(err error) {
	if err != nil {
		log.Fatal(err)
	}
}

func main() {
	t := &starlark.Thread{}
	sd := starlark.StringDict{
		"test": starlark.NewBuiltin("test", func(*starlark.Thread, *starlark.Builtin, starlark.Tuple, []starlark.Tuple) (starlark.Value, error) {
			panic("panic")
			// println("123")
			return starlark.None, nil
		}),
	}
	g, err := starlark.ExecFile(t, "", `
def mytest():
	test()
`, sd)
	check(err)
	g.Freeze()
	v := g["mytest"]

	calltest := func() {
		defer func() {
			if e := recover(); e != nil {
				fmt.Println("get panic", e)
			}
		}()
		_, err = starlark.Call(t, v, make(starlark.Tuple, 0), nil)
		println("get err:", err.Error())
	}

	calltest()
	calltest()

}

The output I am expecting is:
get panic panic
get panic panic

But the output I get is：
get panic panic
get err: function mytest called recursively

When starlark is aborted by Builtin panic, calling starlark.Call again will get an error. I would like a way to have starlark revert to a usable state without renew a Thread

You need to enable the AllowRecursion flag to cause the interpreter not to fail when a recursive call is encountered. (This flag also enables the use of while loops.)

AllowRecursion is not the root problem, it's just one possible cause of panic. The fundamental issue here is that the interpreter is not designed to deal gracefully with panics in built-in functions. Perhaps it should? I've reopened the issue to track the decision.

Change from
if !resolve.AllowRecursion {
to
if !resolve.AllowRecursion && thread.frameAt(0).locals != nil {
what do you think?

change from
if !resolve.AllowRecursion {
to
if !resolve.AllowRecursion && len(thread.stack) <= 1 {
what do you think?

change from
if frfn, ok := fr.Callable().(*Function); ok && frfn.funcode == fn.funcode {
	return nil, fmt.Errorf("function %s called recursively", fn.Name())
}

to
if frfn, ok := fr.Callable().(*Function); ok && frfn.funcode == fn.funcode {
	if fr.locals != nil {
		thread.stack = thread.stack[idx+1:]
		break
	}
	return nil, fmt.Errorf("function %s called recursively", fn.Name())
}

what do you think?

After some tests, the only way is to wrap panic as an error to return the stack to correct state
in func CallInternal
change form
...
	code := f.Code

loop:
	for {
...

...
	code := f.Code

	defer func() {
		if e := recover(); e != nil {
			err = &EvalError{Msg: fmt.Sprint(e), cause: fmt.Errorf(fmt.Sprint(e))}
			// ITERPOP the rest of the iterator stack.
			for _, iter := range iterstack {
				iter.Done()
			}
			fr.locals = nil
		}
	}()

loop:
	for {
...

you can see change in here:
https://github.com/vanishs/starlark-go/commit/f5b91f58332354ea71cc8316255fe3ad6864642a

Add an Explicit call:
func (thread *Thread) CallStackPop() {
	for i := len(thread.stack) - 1; i >= 0; i-- {
		fr := thread.stack[len(thread.stack)-1]
		thread.stack = thread.stack[:len(thread.stack)-1]
		if _, ok := fr.Callable().(*Function); ok {
			break
		}
	}
}

what do you think?

The internal invariants shouldn't be exposed. I've posted #422 containing the correct fix. The benchmark doesn't seem to show significant extra cost.

thanks! i close my pr


Publish 7.6-20220811004345+0000

Publish 7.6-20220811004345+0000

@bot-gradle test and merge

No milestone for this PR. Please set a milestone and retry.

@bot-gradle test and merge

OK, I've already triggered a build for you.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

Pre-tested commit build cancelled.

OK, I've already triggered a build for you.


Update writing custom actions documentation

Signed-off-by: Aaron Nickovich<EMAIL_ADDRESS>Hey, I just made a Pull Request!
The "integrations" variable was missing from the auto-generated backstage app.
This is not needed from the backstage CLI tool because it's not used in the scaffolder.ts file until users want to add their own custom actions.
I'm adding this snippet of code to the custom actions documentation in order to help others who want to create custom actions without having to figure out why the integrations object is undefined.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Looks good, thank you! This is sort of a weird semi-representation of the file contents, but it was already that way and makes sense to show the imports you'll need to add 🙂

No problem! I struggled with this one myself. My first modification was to add a new action and I couldnt figure out why copying the documentation resulted in a failed build. Newcomers will appreciate the documentation more when copying it "just works".
I suppose the other way to help others starting out would be to make the app creator CLI create the builtin actions object by default. Then, the documentation could be shortened to only showing how to append a new action.


Rolling windows sequence function?

Orion version: 0.1.6
Python version: 3.7.10
Operating System: Windows 10

Description
When I apply time function rolling window sequence take a too long time? My time series index is np.datatime64 and the interval of function is not seconds when the function is applied.
What I Did
Redifine inteval parameter to :

interval = np.timedelta64(interval, 's')

Hi @FranVV-Ecu, can you provide more detail? What does the input look like? It would be helpful for me to see what code you ran and causes this problem.
The rolling_window_sequence primitive would talk a long time if the signal is long and the interval set is small. However, it still should be relatively fast.


#25 added basic metadata support for plugins

added support for name and description;
fixed resolve_task_type method from possible circular reference;
started using __future__.unicode_literals;


Support vitest 0.16+

Fixes #2
This upgrades to vitest 0.17.0, fixes the SpyFunction type and removes the usage of done() callbacks in favor of promises in api.test.js (vitest was complaining)

Hmmmm, it looks like Mock is the replacement for SpyInstanceFn: https://github.com/vitest-dev/vitest/pull/1525#issuecomment-1163602304.  Mind updating that here?
Also, I think we should add a peerDependencies on vitest >= 0.16.0.

Oops this needs to have a peer dependency of > 0.16 not 0.16 - 0.17

Fixed in 0.2.1.


Installation of easy_wbs plugin

Hi,
I'm using the sameersbn/docker-redmine (4.1.1-3) with postgres and I had an issue when installing the plugin with command :
docker exec -it redmine redmine-install-plugins
Migrating plugins. Please be patient, this could take a while... rake aborted! NoMethodError: undefined method assets' for #
/home/redmine/data/tmp/bundle/ruby/2.4.0/gems/railties-<IP_ADDRESS>/lib/rails/railtie/configuration.rb:97:in method_missing' /home/redmine/data/tmp/bundle/ruby/2.4.0/gems/redmine_extensions-0.2.16/lib/redmine_extensions/engine.rb:20:in '
/home/redmine/data/tmp/bundle/ruby/2.4.0/gems/redmine_extensions-0.2.16/lib/redmine_extensions/engine.rb:9:in ' /home/redmine/data/tmp/bundle/ruby/2.4.0/gems/redmine_extensions-0.2.16/lib/redmine_extensions/engine.rb:8:in '
/home/redmine/data/tmp/bundle/ruby/2.4.0/gems/redmine_extensions-0.2.16/lib/redmine_extensions.rb:1:in require_relative' /home/redmine/data/tmp/bundle/ruby/2.4.0/gems/redmine_extensions-0.2.16/lib/redmine_extensions.rb:1:in '
/var/lib/gems/2.4.0/gems/bundler-2.1.4/lib/bundler/runtime.rb:74:in require' /var/lib/gems/2.4.0/gems/bundler-2.1.4/lib/bundler/runtime.rb:74:in block (2 levels) in require'
/var/lib/gems/2.4.0/gems/bundler-2.1.4/lib/bundler/runtime.rb:69:in each' /var/lib/gems/2.4.0/gems/bundler-2.1.4/lib/bundler/runtime.rb:69:in block in require'
/var/lib/gems/2.4.0/gems/bundler-2.1.4/lib/bundler/runtime.rb:58:in each' /var/lib/gems/2.4.0/gems/bundler-2.1.4/lib/bundler/runtime.rb:58:in require'
/var/lib/gems/2.4.0/gems/bundler-2.1.4/lib/bundler.rb:174:in require' /home/redmine/redmine/config/application.rb:18:in '
/home/redmine/redmine/Rakefile:5:in require' /home/redmine/redmine/Rakefile:5:in '
/home/redmine/redmine/vendor/bundle/ruby/2.4.0/gems/rake-13.0.1/exe/rake:27:in `'
(See full trace by running task with --trace)
Desired behavior:
no error ! ;)`
The support of easyredmine helped me, please check their response :

I've investigated the issue. I've installed this specific dockerized redmine (with postgres) and tried to install plugins there (before that I've rechecked that on regular redmine there is no such problem).
I was able to reproduce the problem, found out it's source and fix it (but you will need to reapply the fix every time you rerun the container).
So, I've found out that

there were some needed gems removed from Gemfile. I've added them to plugin's gemfile (it was easier).

I've edited file easy_midmup/Gemfile and added the next lines there:
Use SCSS for stylesheets
gem 'sass-rails', '~> 5.0'
Use Uglifier as compressor for JavaScript assets
gem 'uglifier', '>= 2.7.2'
Use jquery as the JavaScript library
gem 'jquery-rails'

After that I've found out that there was very important line commented in one redmine file. I've found and uncommented it:

sudo docker exec -it redmine bash
vi config/application.rb
uncomment the line
require 'sprockets/railtie'

After that I've found our that one important package was not installed in the system. To be able to install it I had to run the next command

apt update & apt upgrade
apt-get install nodejs

After that I've reinstalled plugins without restarting the container with the command

sudo docker exec -it redmine redmine-install-plugins
And plugins were installed successfully.
So there is nothing in our plugins that prevents the installation (gems that I've added to plugin's gemfile should be initially presented in redmine's gemfile). The problem is in dockerized redmine itself. For some reasons the author of the docker decided to remove this parts from the container. You may contact him and suggest him to add these changes to his docker file.

Thanks I'm a bit busy this week but I'll see if I can find time to look into this.

The problem appears to be caused by updates in redmine 4.1.1 and not this docker image. The plugin author needs to update their plugin to support redmine 4.1.1
 $ cd /tmp
 $ wget "http://www.redmine.org/releases/redmine-4.1.1.tar.gz" -O /tmp/redmine-4.1.1.tar.gz
 $ tar xzf redmine-4.1.1.tar.gz
 $ grep -R sprock redmine-4.1.1
redmine-4.1.1/doc/CHANGELOG:* Defect #32839: Redmine 4.1 installation fails due to an attempt to install sprockets 4.0.0 if bundler prior to 1.15.2 is used on Ruby prior to 2.5
redmine-4.1.1/doc/CHANGELOG:* Defect #32223: Disable sprockets to avoid Sprockets::Railtie::ManifestNeededError raised by sprockets 4.0.0
redmine-4.1.1/doc/CHANGELOG:* Defect #32300: Don't use sprockets 4.0.0 in order to avoid Sprockets::Railtie::ManifestNeededError
redmine-4.1.1/Gemfile:gem 'sprockets', '~> 3.7.2' if RUBY_VERSION < '2.5'
redmine-4.1.1/config/application.rb:# require 'sprockets/railtie'
 $ grep -R sass-rails redmine-4.1.1
 $ grep -R uglifier redmine-4.1.1
 $ grep -R jquery-rails redmine-4.1.1
redmine-4.1.1/doc/CHANGELOG:* Patch #31205: Replace jquery-rails with vanilla javascript ujs

Thanks for your response, I will transfer the message !


[22.05] knot-resolver: 5.5.0 -> 5.5.3

5.5.3 fixes CPU-expensive DoS by malicious domains.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] N/A Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

For NixPkgs master there should instead be 5.5.3 update later today.  For 22.05 I guess we take just the patch, though both ways seem OK to me.

So after discussion in the master PR I looked at the changes in more depth and decided to take them all instead, as they do seem to have significantly more benefits than risks.


add the rust client for simple  pub sub.

The rust api for the client needs to be create and it needs to be packaged with the crate.

done.


Add support for npm dependencies for Meteor build packages (package.js files)

Most Meteor applications today install npm packages just like any other Node app, using package.json with npm or yarn.
But if a Meteor build package depends on Npm, it has it specified inside the package.js file using the Npm.depends function.
The format of the input of that package is identical to package.json.
Adding support for tracking npm dependencies for Meteor's Npm.depends would be very cool :)
Here is an example
It can have all types of URLs that npm supports such as git URLs
Reference
The only difference is that it supports only exact version numbers, not including ^.

Can you point me to one or more public examples? Enough to cover all use cases

@rarkins oops how did I forget that :)  added to the main comment

@rarkins made more changes to the comment

Are package.js files only found at root of a repo or can they be nested? (Eg inside monorepo)

I think there will be a lot of false positive package.js files found in repos, although I suppose that NPM.depends is distinctive enough that we shouldn't fine any false positives of that in non-meteor repositories.
Does the package.js file have any formatting conventions by any chance? E.g. 2 spaces? How about single vs double quotes?
Assuming not, it will be a little challenging to modify the dependencies in a way that doesn't reformat the rest of the file. Actually, detecting them to begin with could be challenging too, if there is no convention for the JS formatting. Probably needs an AST parser to substitute for the JSON.parse we use for JSON.

@rarkins they can also be nested.
there is no formatting conventions and now I see your point and yes, it can be more challenging than parsing a JSON.....

I can't access the Example link. Is it a typo or private repo?

I've updated the links

This looks useful in terms of parsing-editing-writing the file while retaining as much formatting as possible: https://github.com/benjamn/recast/blob/master/README.md

@Urigo this feature is now ready for testing in #786. I've tested it locally only against a copy of https://github.com/RocketChat/Rocket.Chat so far and it works as I'd expect. Can you suggest some additional repositories to test against before I merge?

ok!  after a lot of unrelated cleanups, I've merged renovate to the Angular Meteor repo!
@rarkins first of all thank you !
second, I hope I've done it right, at the beginning it gave me this config which I haven't found on the docs, so I've changed it to this and pushed.

@Urigo I submitted a PR to fix the renovate.json :)
https://github.com/Urigo/angular-meteor/pull/1666
I'm actually about to flip the switch and make Meteor support enabled by default anyway, however you would still need to fix up the renovate.json config.

@Urigo please also see #1008


Event streaming bash script not working for me

I'm getting the following error when trying to run the stream-events shell script in Gitpod. Is here the correct place to raise it? :-)

@tamlyn10 bash stream-events/stream-events.sh now works.


{u'error_code': 71, u'result': u'FAIL', u'error': u'RPC_CALL_FAIL 400: INPUT_FETCH_ERROR'} on set_profile_photo

The problem
set_profile_photo returns
{u'error_code': 71, u'result': u'FAIL', u'error': u'RPC_CALL_FAIL 400: INPUT_FETCH_ERROR'}
after uploads image
Your environment
python 2.7.6, last pytg and Elementary OS (Ubuntu).
Steps to reproduce
sender = Sender(host, port)
sender.set_profile_photo(path)
The path is correct, if the path is incorrect returns other error.
Expected behaviour
return True and update the profile picture
Actual behaviour
return {u'error_code': 71, u'result': u'FAIL', u'error': u'RPC_CALL_FAIL 400: INPUT_FETCH_ERROR'}

Looks like the problem actually lies in Telegram CLI. I get exactly the same error there.

Please check the command in the cli (--json flag).
If you need help, post the log output please. how to enable Debug

In the cli returns the same error.
The complete log is:
DEBUG:pytg.sender:Parsing set_profile_photo: Argument /home/sento/a.jpg -  (needed)
DEBUG:pytg.sender:Sending command >[disable_preview] set_profile_photo '/home/sento/a.jpg'
<
DEBUG:pytg.sender:Socket Connected.
DEBUG:pytg.sender:All Sent.
{u'error_code': 71, u'result': u'FAIL', u'error': u'RPC_CALL_FAIL 400: INPUT_FETCH_ERROR'}

So the command [disable_preview] set_profile_photo '/home/sento/a.jpg' fails?
Does set_profile_photo '/home/sento/a.jpg'fail too?

Yes

The problem can be fixed in Telegram CLI, concretly in:
https://github.com/vysheng/tgl
In order to fix the problem, remove the duplicated line:
out_int (CODE_photos_upload_profile_photo);
At tgl/queries.c, method static void send_avatar_end, case TGL_PEER_USER, line 1865.
Or just check pullrequest: vysheng/tgl#105
Then just re-make Telegram-CLI.

Thank you very much @s-londono this solves the problem

Maybe I should maintain a fork with all the needed pull requests, as @vysheng seem to have not enough time anymore to work on it or even merge existing pull requests...

I have same issue,
When I want forward a media I see this error,
My code is :
`
coding=utf-8
from future import unicode_literals
from pytg import Telegram
tg = Telegram(
telegram="/home/saeb/Downloads/git/tg/telegram-cli/bin/telegram-cli",
pubkey_file="/home/saeb/Downloads/git/tg/telegram-cli/tg-server.pub",
port=8032
)
inline_image = False
receiver = tg.receiver
sender = tg.sender
from pytg.receiver import Receiver  # get messages
from pytg.sender import Sender  # send messages, and other querys.
from pytg.utils import coroutine
import logging
logging.basicConfig(level=logging.DEBUG)
#315156394
author = 'saeb'
ADMIN_IDS =['$0100000084cba20ed401c9a0893540b9']  # you should probably change this.
def main():
receiver.start()
receiver.message(schedulerDeleter(sender))
receiver.stop()
print("I am done")
@coroutine
def schedulerDeleter(sender):
quit = False
try:
while not quit:
msg = (yield)
print(msg)
sender.status_online()
if msg.event == "message" and not msg.own:
msgTime = msg.sender.when.split()
msgID = msg.id
msgSenderId = msg.sender.id
print("\n msg time= {}\n msgID = {}
msgSenderId = {}".format(msgTime, msgID,
msgSenderId))
#print("\n msg txt = {} \n".format(msg.text))
if 'text' not in msg:
msgFromId = msg.fwd_from.id
sender.fwd_media(msgFromId,msgID)
else:
sender.fwd(msgSenderId,msgID)
        #print(msg)
        if msg.event != "message":
            continue
        if msg.own:
            continue
        else:
            sender.send_msg(msg.peer.cmd, "سلام!")

except GeneratorExit:

    pass
except KeyboardInterrupt:

    pass
else:

    pass

if name == 'main':
main()
`
and when I forward a media to it I see this error:
https://pastebin.com/f89xhznd


Does Argo assume Docker the container runtime used by Kubernetes

We are the SQLFlow.org team. We are trying to refactorize SQLFlow.org to convert a SQL program into a workflow. For that purpose, a team member https://github.com/Yancey1989 tried to deploy Argo on a customized implementation of Kubernetes, which doesn't use Docker as the default container runtime.
The trial failed with error messages indicating that Argo expected to mount /var/run/docker.sock to some step containers. However, this customized Kubernetes doesn't use Docker, so there is no /var/run/docker.sock.
After git-grep the source code, it seems that the following snippet is suspicious to me.  Could Argo authors please confirm? If so, may we have suggestions from Argo authors please? Thanks!
https://github.com/argoproj/argo/blob/54f44909a0e68bc24209e9e83999421b814e80c9/workflow/controller/workflowpod.go#L54-L82

(Not a maintainer, just a drive by suggestion):
The default executor for Argo is the docker executor which is why it's trying to mount docker.sock.  There are multiple others executors available which should avoid the need to do that:
https://github.com/argoproj/argo/blob/master/docs/workflow-executors.md
https://github.com/argoproj/argo/blob/59a190697286bf19ee4a5c398c1af590a2419003/docs/workflow-controller-configmap.yaml#L78-L80

@dcherman is correct, you can change the container runtime. What runtime do you need to use? containerd?

Thanks, @dcherman for pointing me to the container runtimes available to Argo and how to choose one.
Hi @alexec, I was trying to deploy SQLFlow on an Alibaba internal customized Kubernetes cluster running Pouch https://github.com/alibaba/pouch when I noticed the problem. In other deployments to vanilla Kubernetes, including the one at DiDi https://en.wikipedia.org/wiki/DiDi, everything thing works fine.
Still a little bit of confusion in my mind - It looks to me that Kubernetes is customizable to work with multiple container runtimes, as explained in https://kubernetes.io/docs/setup/production-environment/container-runtimes/. Does that mean Argo should work with any container runtime that the Kubernetes cluster uses? Why would Argo users need to configure and choose the container runtime?

@jessesuen ?

Does that mean Argo should work with any container runtime that the Kubernetes cluster uses?

Argo started out with only the Docker runtime, and subsequently added kubelet, K8s, and finally PNS to address the security concerns with the mounting of docker.sock on the host. The kubelet, k8s, and PNS executor should work with any container runtime including containerd.

Why would Argo users need to configure and choose the container runtime?

There are tradeoffs to using each runtime as explained in the docs. Often, the choice is made for you such as if you are not running docker runtime, or if you have an admission controller that blocks docker.sock from mounting. In your case, PNS is probably your best option.


Rendering Problem

Hello,
I've copy pasted the example code from the the README.md.
It is working actually but the problem is the size of the generated image.
It looks like this:

but actually it should look like this:

I don't know what is wrong. The code is a simple copy paste from the examples and looks like this:
        Graph g = graph("example1").directed()
                .graphAttr().with(RankDir.LEFT_TO_RIGHT)
                .with(
                        node("a").with(Color.RED).link(node("b")),
                        node("b").link(to(node("c")).with(Style.DASHED))
                );
        try {
            Graphviz.fromGraph(g).height(100).render(Format.PNG).toFile(new File("example/ex1.png"));
        } catch (IOException e) {
            e.printStackTrace();
        }

This bug appears with the latest versions. After rolled back to v0.8.0, it's working properly.

I changed something in 0.8.4 regarding the image size.
But I cannot reproduce this issue neither with 0.8.0 nor with 0.8.10. The resulting image has always 100px height.
Maybe it's the graphviz version you have on your machine, can you try adding Graphviz.useEngine(new GraphvizV8Engine()) at the beginning?

I found an issue that could cause your problem. It is fixed in version 0.11.0. Please check it out.

hi,
how can i do to start and configure the Graphviz.useEngine () method?

Just call Graphviz.useEngine(new GraphvizV8Engine()) at the beginning of your program.

Additionally in version 0.11.1, the image sizing is improved and maybe thus the issue is solved?

Closing this. Feel free to reopen if the problem is still here.


New version: Microsoft.PowerBI version 2.124.2028.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

@wingetbot run

/AzurePipelines run

/AzurePipelines run

/AzurePipelines run

[Policy] Blocking-Issue

Blocked by #131328

@stephengillie this needs License-Blocks-Install label

[Policy] Blocking-Issue

Blocked by P.S.A. Packages with explicit agreements in manifests removed #131328

@stephengillie this needs License-Blocks-Install label

Let me know if you want this removed from my automation.

Let me know if you want this removed from my automation.

@PckgrBot -
Yes, i think we should do that until support for agreements is added in the community repository (#131328), or until the package offers a silent install without the ACCEPT_EULA=1 switch

Close with reason: package added in different PR;


Automatically update the README with the latest -h message

This is a new issue to track the work started in https://github.com/anaconda-distribution/anaconda-linter/pull/238
We got very close to having our README updated automatically with pre-commit. However, we ran into some bootstrapping issues and our current use of Python modules doesn't feel correct to me.
I've captured the Python module changes in this issue and that is a pre-req to this issue.
@cbouss also mentioned that this man page tool may be useful for generating docs: https://github.com/click-contrib/click-man

Tracking: https://anaconda.atlassian.net/browse/PAT-177


Creating three node cluster with all three roles( for each node) fails

Rancher versions:
rancher/server: Master from March1
Steps to Reproduce:

Create a 3 node cluster with all 3 roles on each node using digital ocean template
Two of the nodes are stuck in registering state and the cluster fails to start successfully
Server logs :

E0301 18:28:19.622573       1 generic_controller.go:200] SecretController kube-system/node-controller-token-cphdd [secretsController] failed with : Operation cannot be fulfilled on secrets "node-controller-token-cphdd": the object has been modified; please apply your changes to the latest version and try again
E0301 18:28:19.633115       1 generic_controller.go:200] NamespaceController kube-public [namespace-auth] failed with : Operation cannot be fulfilled on namespaces "kube-public": the object has been modified; please apply your changes to the latest version and try again
E0301 18:28:19.633120       1 generic_controller.go:200] NamespaceController kube-system [namespace-auth] failed with : Operation cannot be fulfilled on namespaces "kube-system": the object has been modified; please apply your changes to the latest version and try again
time="2018-03-01T18:28:19Z" level=info msg="Successfully created default network policy for project: project-t44fg"
E0301 18:28:19.698773       1 generic_controller.go:200] ProjectController cluster-rxg89/project-t44fg [project-precan-alert-controller] failed with : Operation cannot be fulfilled on projects.management.cattle.io "project-t44fg": the object has been modified; please apply your changes to the latest version and try again
time="2018-03-01T18:28:19Z" level=info msg="adding label field.cattle.io/projectId=project-t44fg to namespace=default"
time="2018-03-01T18:28:27Z" level=warning msg="Service [default-http-backend/ingress-nginx] already exists but with diff owner"
time="2018-03-01T18:28:38Z" level=warning msg="Service [kube-dns/kube-system] already exists but with diff owner"
2018-03-01 18:30:04.594670 I | mvcc: store.index: compact 2663
2018-03-01 18:30:04.602447 I | mvcc: finished scheduled compaction at 2663 (took 4.660997ms)
2018-03-01 18:35:04.610065 I | mvcc: store.index: compact 3390
2018-03-01 18:35:04.617436 I | mvcc: finished scheduled compaction at 3390 (took 3.992835ms)
2018-03-01 18:40:04.617989 I | mvcc: store.index: compact 3850
2018-03-01 18:40:04.623224 I | mvcc: finished scheduled compaction at 3850 (took 2.950915ms)
2018-03-01 18:45:04.627492 I | mvcc: store.index: compact 4313
2018-03-01 18:45:04.632864 I | mvcc: finished scheduled compaction at 4313 (took 2.653045ms)
E0301 18:45:48.149292       1 watch.go:228] unable to encode watch object: http2: stream closed (&streaming.encoder{writer:(*http.http2responseWriter)(0xc444f296c0), encoder:(*versioning.codec)(0xc42991f710), buf:(*bytes.Buffer)(0xc42417f570)})
time="2018-03-01T18:45:48Z" level=error msg="Error during subscribe websocket: close sent"
time="2018-03-01T18:45:48Z" level=error msg="Unknown error: websocket: close sent"

On another setup there were similar logs as above and also the following errors were seen:

E0301 19:40:26.669030       1 generic_controller.go:200] ClusterController cluster-dlwjh [cluster-provisioner-controller] failed with : Failed to reconcile etcd plane: Failed to create etcd client for host [<IP_ADDRESS>]: client: etcd cluster is unavailable or misconfigured; error #0: Failed to dial to <IP_ADDRESS>:2379: ssh: rejected: connect failed (Connection refused)
time="2018-03-01T19:40:26Z" level=info msg="ClusterController cluster-dlwjh completed with dropped err: [cluster-provisioner-controller] failed with : backing off failure, delay: 8m0s"
time="2018-03-01T19:40:27Z" level=info msg="ClusterController cluster-dlwjh completed with dropped err: [cluster-provisioner-controller] failed with : backing off failure, delay: 8m0s"
time="2018-03-01T19:40:37Z" level=info msg="ClusterController cluster-dlwjh completed with dropped err: [cluster-provisioner-controller] failed with : backing off failure, delay: 8m0s"
time="2018-03-01T19:40:37Z" level=info msg="ClusterController cluster-dlwjh completed with dropped err: [cluster-provisioner-controller] failed with : backing off failure, delay: 8m0s"
time="2018-03-01T19:40:37Z" level=info msg="ClusterController cluster-dlwjh completed with dropped err: [cluster-provisioner-controller] failed with : backing off failure, delay: 8m0s"
2018-03-01 19:40:43.728577 I | mvcc: store.index: compact 3998
2018-03-01 19:40:43.739406 I | mvcc: finished scheduled compaction at 3998 (took 6.786777ms)

@soumyalj I'm unable to reproduce this issue with mar 5 build.
Can you try to reproduce? With issues like this, we need devs to look at the setup immediately as they aren't consistently failing.

Tested with v2.0.0-alpha17. Still see the same issue.

Tested with v2.0.0-alpha18.
Created a 3 node cluster with all 3 roles on each node using digital ocean template
The cluster was created successfully. Namespace and workload creation also worked ok.


remove multithreading from ExtractIlluminaBarcodes

i removed multithreading, we're not doing it.

fixes #401
@droazen please review

Coverage increased (+0.03%) to 70.73% when pulling 91b0f5f5541572884175b8e88515bbbece17454b on ak_remove_multiThreading_from_ExtractIlluminaBarcodes into a75b706c98c542ded89a771b93b1c3df78ba7f6a on master.

@akiezun Back to you.  Looks good.  There's a weird exception hiding mechanism that I'm sure is from its Runnable heritage.  I think it could stripped out, but I'm not absolutely certain that there aren't side effects build around it.  It might be in the bucket of stuff not worth dealing with.

back to @lbergelson
i exposed the hidden exceptions a bit more. Annoyingly I had to catch IOExceptions and SAMExceptions (an alternative would have been to let SAMExceptions go all the way up to the caller but that seemed suboptimal). Ideally, htsjdk should not have wrapped IOException in a SAMException but rather expose IOExceptions for what they are and leave their handling to the app layer (ie us)

Looks good.  Need to rebase on master to resolve conflicts.  Back to you @akiezun

closing this pull req. these classes are going away

Coverage remained the same at 70.88% when pulling 5421cd2d0298944cc59fd45e82e386c8a5b1b44e on ak_remove_multiThreading_from_ExtractIlluminaBarcodes into 2192ba48479cf358a565f5b3bc872552b451587e on master.

Coverage remained the same at 72.6% when pulling 5421cd2d0298944cc59fd45e82e386c8a5b1b44e on ak_remove_multiThreading_from_ExtractIlluminaBarcodes into 2192ba48479cf358a565f5b3bc872552b451587e on master.

Coverage remained the same at 72.6% when pulling 5421cd2d0298944cc59fd45e82e386c8a5b1b44e on ak_remove_multiThreading_from_ExtractIlluminaBarcodes into 2192ba48479cf358a565f5b3bc872552b451587e on master.


filebeat support in logging role

With LSF being deprecated this role adds support to install and configure filebeat.

👍

retest

retest

retest

retest

retest

retest

retest

retest

retest

retest

retest


Ack call timeout

Description
Describe your issue here.
It is mentioned in the api doc that a method should be returned immediately with ack() call to avoid timeout. My usecase is to fetch a file from slack and upload the file in a cloud server and return some information like the hosted url. This takes more than the 3 second limit and I can't move to the next view. Any suggestions on how I could achieve something like this?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

Hi @mrafiqi21, thanks for asking the question!
If your goal is to asynchronously post a message, you can use respond() utility to do so after ack(). Refer to https://slack.dev/bolt-js/concepts#action-respond for more details:

If your use case is to handle data submission from a modal, check my suggestion at https://github.com/slackapi/bolt-python/issues/481#issuecomment-930038349 (displaying "Now loading" page first, and then calling views.update API method when the result is ready)
I hope this helps.

@mrafiqi21 Yes, I am. As for the view_id, you can use view.id for it.

Thanks @seratch, works fine.
Just one question, can we disable the close button in the loading page modal because it risks the user closing the loading view?

Unfortunately, there is no way to do so. The only thing that I can suggest is to receive view_closed events to know the situation. https://api.slack.com/reference/interaction-payloads/views#view_closed
Is everything clear now?

Yes, thank you so much. Closing the issue.


docs(introduction): add video to the introduction 🚗

wonder if we should rather turn this into small video section (with thumbnails of each video) with a couple useful introductory videos. Two more i'd include:

https://www.youtube.com/watch?v=UvIWmzscWp8
https://www.youtube.com/watch?v=pla6wfWN7tE

Some of these videos are out of date (eg: config format is different). Is that a big deal?

Some of these videos are out of date (eg: config format is different). Is that a big deal?

I don't think so because we state the date they were taken, and it's clear in a fast-moving industry that they might be inaccurate.

I feel pretty strongly we shouldn't clutter the Quickstart guide with these - they're not actually quick start videos.
And I agree that them being out of date doesn't help either. They would be more misleading and confusing than helpful in this context.
Can we make a separate videos section? Maybe as part of "Guides"?


c2hs version constraints

Building with c2hs 0.17.2 (debian jessie default) fails:
src/Graphics/UI/FLTK/LowLevel/Button.chs:116: (column 66) [ERROR]  >>> Missing "out" marshaller!
There is no default marshaller for this combination of Haskell and C type:
Haskell type: CInt
C type      : CInt

0.26.2 is fine. Not sure, however, how to include such a constraint in the cabal file, so this is just an issue report instead of a PR.

The new version does have those constraints. Thanks for the report!


Add default remote metadata timeout settings for remote creation

We have some new design for this feature, so close and will commit new pr later.


Issue while installing cocoa pods for macbookpro M1

Description
Stack
   CocoaPods : 1.11.3
        Ruby : ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin21]
    RubyGems : 3.3.11
        Host : macOS 12.0.1 (21A559)
       Xcode : 13.3.1 (13E500a)
         Git : git version 2.32.0 (Apple Git-132)
Ruby lib dir : /opt/homebrew/Cellar/ruby/3.1.2/lib
Repositories : trunk - CDN - https://cdn.cocoapods.org/

Plugins
cocoapods-deintegrate : 1.0.5
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.1
cocoapods-trunk       : 1.6.0
cocoapods-try         : 1.2.0

Podfile
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

platform :ios, '11.0'
install! 'cocoapods', :deterministic_uuids => false

target 'RNP1' do
  config = use_native_modules!

  # Flags change depending on the env values.
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
    # to enable hermes on iOS, change `false` to `true` and then install pods
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  target 'RNP1Tests' do
    inherit! :complete
    # Pods for testing
  end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable the next line.
  use_flipper!()

  post_install do |installer|
    react_native_post_install(installer)
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end
end

Error
Errno::EACCES - Permission denied @ rb_sysopen - /Users/abhishekambekar/Library/Caches/CocoaPods/Pods/VERSION
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/downloader/cache.rb:171:in `initialize'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/downloader/cache.rb:171:in `open'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/downloader/cache.rb:171:in `open'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/downloader/cache.rb:171:in `ensure_matching_version'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/downloader/cache.rb:22:in `initialize'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/downloader.rb:41:in `new'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/downloader.rb:41:in `download'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer/pod_source_installer.rb:118:in `download_source'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer/pod_source_installer.rb:69:in `install!'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:563:in `install_source_of_pod'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:514:in `block (2 levels) in install_pod_sources'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/user_interface.rb:86:in `titled_section'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:513:in `block in install_pod_sources'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:496:in `each'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:496:in `install_pod_sources'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:255:in `block in download_dependencies'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/user_interface.rb:64:in `section'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:254:in `download_dependencies'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:162:in `install!'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/command/install.rb:52:in `run'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/lib/cocoapods/command.rb:52:in `run'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/gems/cocoapods-1.11.3/bin/pod:55:in `<top (required)>'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/bin/pod:25:in `load'
/opt/homebrew/Cellar/cocoapods/1.11.3/libexec/bin/pod:25:in `<main>'

Version
0.68.1
Output of npx react-native info
System:
OS: macOS 12.0.1
CPU: (8) arm64 Apple M1
Memory: 181.67 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 18.0.0 - /opt/homebrew/bin/node
Yarn: Not Found
npm: 8.6.0 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.68.1 => 0.68.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
after creating new react native project npx react-native init project-name, it shows this message
✔ Downloading template
✔ Copying template
✔ Processing template
✖ Installing CocoaPods dependencies (this may take a few minutes)
✖ Installing CocoaPods dependencies (this may take a few minutes)
error Error: Failed to install CocoaPods dependencies for iOS project, which is required by this template.
Please try again manually: "cd ./RNP1/ios && pod install".
But tried with pod install under ios folder, shows info mentioned in above description.
Kindly need help with this.
Thank you 😊
Snack, code example, screenshot, or link to a repository
No response

I have had also the same issue today "somehow" I fixed it,  run inside the ios folder brew install CocoaPods then I got(probably you will get the same) another error built error(I don't remember exactly) then back to the root folder and run this code cd ios && pod install && cd ../ && react-native run-ios
I have used this resource https://stackoverflow.com/questions/58546659/podfile-lock-missing-when-initial-react-native-run-ios

I have had also the same issue today "somehow" I fixed it, run inside the ios folder brew install CocoaPods then I got(probably you will get the same) another error built error(I don't remember exactly) then back to the root folder and run this code cd ios && pod install && cd ../ && react-native run-ios
I have used this resource https://stackoverflow.com/questions/58546659/podfile-lock-missing-when-initial-react-native-run-ios

Thank you @azeezipro, I have tried your solution, but issue remains same.

Hey @abhishekambkr 👋
Have you also try running pod cache clean? (which should delete the /Users/abhishekambekar/Library/Caches/CocoaPods directory, otherwise, I would also delete it manually)

@abhishekambkr have you solved the issue?

@abhishekambkr @cipolleschi can you try this in M1
sudo arch -x86_64 gem install ffi
arch -x86_64 pod install

These commands install the ffi package, to load dynamically-linked libraries and let you run the pod install properly, and runs pod install with the proper architecture.

Since I am using a M1 based mac book when I ran pod install normally it did not work but when I ran arch-x86_64 pod install it worked. I would like to point out here that I was not getting any error when I ran pod install

I used brew instead and it works fine
brew install cocopoads

I think we can close this now as I believe the version supplied by brew of cocoapods is M1 compatible

hey try this I faced this issue on an M1 based mac book macOS big sure 11.6.8,

brew install cocopoads
ruby 2.6.8p205 (2021-07-07 revision 67951) [x86_64-darwin20]
then in project cd ios run 2 commands as,
sudo arch -x86_64 gem install ffi
arch -x86_64 pod install
then you need to remove libswiftWebKit.tbd  from build phases -> Link Library With Libraries


Misaka 8.1.0 ipad 9th gen (12,1) 16.5 still kernel panics and reboots when kopen

As the title says, still an issue

Fact is v3.2.5 is working ,v8.0.9 is not working; but 2.3.5  is forced to update. Please let us choose