how to uses MVP-RxJava architecture in viewpager ?

firstly, thanks to solved the problem of communicate between two presenter.
But there is a serious need to solve how to uses viewpager in mvp architecture. In fact, fragment is more suitable to role in 'View'  than Activity which usually used to control fragment. The viewpager, you know, is often used in our apps.

+1

Are you referring to the tablet presenter branch?

I've tried different implementations about this problem. I think the most suitable one is passing fragments to ViewPager adapter and before pass check if there's a fragment which reained by ViewPager. If there's use it as View and pass it to ViewPager's adapter.
You can find the fragments you used in ViewPager by Tag with this pattern:
"android:switcher:"+R.id.your_view_pager+":"+position
Here i'll send an example code.
`BankRollDetailFragment detailFragment = (BankRollDetailFragment) getSupportFragmentManager()
.findFragmentByTag(UiUtil.generateViewPagerFragmentTag(R.id.viewpager_bankroll, BankRollTabsAdapter.TAB_DETAIL));
if (detailFragment == null) {
detailFragment = BankRollDetailFragment.newInstance();
}
    BankRollBetsFragment betsFragment = (BankRollBetsFragment) getSupportFragmentManager()
            .findFragmentByTag(UiUtil.generateViewPagerFragmentTag(R.id.viewpager_bankroll, BankRollTabsAdapter.TAB_BETS));
    if (betsFragment == null) {
        betsFragment = BankRollBetsFragment.newInstance();
    }

    final SparseArray<Fragment> fragments = new SparseArray<>();
    fragments.put(0, detailFragment);
    fragments.put(1, betsFragment);

    final ViewPager viewPagerBankRollTabs = (ViewPager) findViewById(R.id.viewpager_bankroll);
    final TabLayout tabLayout = (TabLayout) findViewById(R.id.tabs);
    final BankRollTabsAdapter bankRollTabsAdapter = new BankRollTabsAdapter(getSupportFragmentManager(),
            getResources().getStringArray(R.array.tabs_bankroll),
            fragments);
    viewPagerBankRollTabs.setAdapter(bankRollTabsAdapter);
    tabLayout.setupWithViewPager(viewPagerBankRollTabs);

    DaggerBankRollComponent.builder()
            .bankRollDetailPresenterModule(new BankRollDetailPresenterModule(detailFragment, bankrollId))
            .bankRollBetsPresenterModule(new BankRollBetsPresenterModule(betsFragment))
            .bankRollRepositoryComponent(((BetSafeApp) getApplication()).getBankRollRepositoryComponent())
            .build()
            .inject(this);`


Error on zoom

Hi, I'm using leaflet 1.0 and the corresponding version of this plugin, however, I get errors, and they seem to be generated by the following code:
L.Renderer.include({
    _updateTransform: function () {
        var zoom = this._map.getZoom();
        var center = this._map.getCenter(true);
        var scale = this._map.getZoomScale(zoom, this._zoom);
        var offset = this._map._latLngToNewLayerPoint(this._topLeft, zoom, center);

        L.DomUtil.setTransform(this._container, offset, scale);
    }
});

this._topLeft is undefined, which propably creates the error.

Hi !
This issue should be solved by this pull request
(Thx to helbling)
Could you try again with this commit ?
Thx

When I change the code, the zoom works as intended, however something strange now happens to my map. I have a baselayer switch on my map to switch between a coloured open street map and a (css) greyscale map. Standard this greyscale map is put on first. By changing the code, the css class isn't applied on the layer. The original version with your old code can be seen here : www.backtothemap.be

nevermind, I've found the little culprit :p I added 1 line of code to make sure I got an id on the images so I could put some css on that id :p working good now :)


spring cloud zuul support Placeholder?

Sorry for my bad Englist first.
spring cloud zuul support Placeholder???
Like this:
zuul:
  routers:
    users:
      path:  /cities/{areaCode}/
      url: http://{areaCode}.google.com

Where does {areaCode} come from?

A path Variable,{areaCode} can be any city code .
I find a same issues :     https://github.com/spring-cloud/spring-cloud-netflix/issues/2173

Duplicate of #2173

You can achieve what you want to achieve with a slightly modified route definition and just a small redirector microservice of your own.

your route configuration:

zuul:
  routes:                        # <-- AFAIK it is 'routes' not 'routers'
    users:
      path: /cities/*/           # <-- note the '*' in the route definition
      url: http://<host>:<port>/redirector-service
      strip-prefix: false

In the redirector microservice the uri fragment represented by the '*' in the zuul route can be retrieved as a @PathVariable:

@RestController
public class RedirectorService {
    @GetMapping(value = "/cities/{areaCode}/")
    public String redirectTo(@PathVariable("areaCode") String areaCode) {
        // use a restTamplate to make the call to google.com with the areaCode
    }
}

Kishore Babu Diyyana: Recursive Path with ** - Add on points to pathParam (@PathVariable) and queryParam (@RequestParam)
applicaiton.yml
zuul:
routes:
gatewayPathParamTest:
path: /pathParamTest/**
url: http://localhost:8081/pathParamTest/

RestService
@RequestMapping(value = {"/pathParamTest/{id}/test/getdata"},
produces = "application/json", method = {RequestMethod.GET})
public String pathParamTest(@RequestParam(value="name", required = false)
String name, @PathVariable (value="id", required = false) String id) throws Exception
{ ....
.... }
Valid endpoints access:
http://localhost:8085/pathParamTest/123/test/getdata
http://localhost:8085/pathParamTest/123/test/getdata?name=diyyana


Update query.py

In CaptionQuery class, added a method and a supporting data member to get captions by language name.
This solves issue #759

Coverage increased (+0.005%) to 94.793% when pulling 889e9cec1ed239821058a6f05adfbf8c3035dac3 on skoare:master into 8464dc15c388e4e425d35cfcd6d736f54adfadc4 on nficano:master.

@skoare I implemented the fix suggested by urna in #779 in this PR, which I believe is a more effective solution. Can we close this PR?


Fix features unittest using pytorch 2.0

There is one failing unittest when using pytorch 2.0. This fixes it and should work for all versions.

thank you @pplantinga!


README/CompanyGitHub

| AI4Finance Foundation |  AI4Finance Foundation — An open-source community sharing AI tools for finance.|
TuringPi Machines |

#1449 closes #1448


Fix issue with webviews.

We were instantiating a WKWebView on a background thread and even though
we weren't doing anything with it, it borked everything.
Weirdly this was impacting both WKWebView and UIWebView.

@mikekatz please review

I am going to land this because it is blocking a bunch of testing, but it still needs review

this explains so much! :+1:


Crafting Fixes

Resolved issue 229 relating to crafting issues and improved the overall health of the crafting with recipie book system.
Issues resolved:

Resolved an issue where crafting with the crafting book would sometimes result in getting stuck endlessly switching between items.
Resolved an issue where crafting with the crafting book would break at a crafting table (would get super spammy with opening and closing the table). This was caused by items getting stuck in the 2x2 player crafting grid.

Update Notes:
The fixes in this update only apply to crafting with the recipe book. Any issues with crafting that do not deal with that are still unresolved.
The ender eye issue is not necessarily a crafting issue since the task works fine by itself. Rather, it is an issue with the tasks interrupting each other when running BeatMinecraft2. I will investigate this in the future, but I wanted to get these crafting fixes out now.

DO NOT MERGE YET


Changing a Cloudflare Worker Secret results in a delete; then create

Confirmation

[X] This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
[X] I have searched the issue tracker and my issue isn't already found.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.9.5
on darwin_arm64

provider registry.terraform.io/cloudflare/cloudflare v4.43.0

Affected resource(s)
cloudflare_worker_secret
Terraform configuration files
Can't provide full configuration - but assume that there is a worker - with an already managed secret - changing that secret results in a destruction; and then creation of a new secret. Instead of updating within the next execution.
This is the plan output.

-/+ resource "cloudflare_worker_secret" "worker-secrets" {
      ~ id          = "59775269137828e79d859bb835a3b1f2" -> (known after apply)
        name        = "SECRET_NAME"
      ~ secret_text = (sensitive value) # forces replacement
        # (2 unchanged attributes hidden)
    }

Example:
variable "worker_script_name" {
  type = string
  description = "CF Worker Script Name - as defined in wrangler.toml"
}

variable "secrets" {
  type = map(string)
  description = "Map of AWS Secret Values to Cloudflare Env Vars"
}

variable "cloudflare_account_id" {
  type = string
  description = "Cloudflare Account Id"
}
variable "environment" {
  type = string
  description = "Environment"
}

locals {
  worker_script_env = "${var.worker_script_name}-${var.environment}"
}

data "aws_secretsmanager_secret" "secrets" {
  for_each = toset(keys(var.secrets))
  name = each.value
}

data "aws_secretsmanager_secret_version" "secrets" {
  for_each  = data.aws_secretsmanager_secret.secrets
  secret_id = each.value.id
}

resource "cloudflare_worker_secret" "worker-secrets" {
  for_each    = var.secrets
  account_id  = var.cloudflare_account_id
  name        = each.value
  script_name = local.worker_script_env
  secret_text = data.aws_secretsmanager_secret_version.secrets[each.key].secret_string
}

Link to debug output
Unable to link due to security.
Panic output
No crash/panic.
Expected output
I would expect that the provider not destroy; and rather recognize that the value just needed to be updated/set again.
The cloudflare API supports the PUT endpoint; and the provider should not destroy the resource.
https://developers.cloudflare.com/api/operations/namespace-worker-put-script-secrets
Actual output
Resource was destroyed in one operation; which resulted in multiple deployments for a worker; one of which had the wrong (ie - none) value for the secret as it was deleted.

Steps to reproduce

Create a worker with a secret (either through terraform or wrangler.)
Manage that secret through terraform; either creating a new one, or updating the existing one.
Change the value in the terraform resource for the secret; and the plan will result in destroying; then creating a new version of the worker deployments with the secret removed; and then another with the secret re-added.

Additional factoids
No response
References
No response

changing the text value of the resource is expected to force creation of a new terraform resource. there is no way to retrieve the secret value once it has after creation to determine if the value has changed or if it should be inline replaced. instead, you may want to look into the create_before_destroy or a two phase swap of secrets.
side note: including a graph with three lines and no context is of no use to helping describe the problem here 🙂

I would expect that the provider never "destroys" the cloudflare secret unless the resource itself is deleted; only updates it via put - even in a case where managing multiple secrets - that it would only ever create a single deployment.

as i mentioned above, this isn't possible to differentiate in all scenarios hence why the replacement causes a new resource to be created. if you don't want this behaviour, you'll need to use the meta-arguments or a two phase apply.

Maybe it's better to suggest something like https://developers.cloudflare.com/workers/wrangler/commands/#secretbulk get added to Cloudflare-Go? and then downstream to TF? That way you can change n secrets without multiple calls?

terraform operates on a per resource operation; using bulk endpoints requires additional parsing and overhead that we don't want to capture in the provider. this is why we have individual endpoints that support all the CRUD lifecycle operations.

How would moving to a create-before-destroy method change this? It would still result in the secret being removed from the worker would it not?

Tested this - using create-before-destroy actually is not at all what should happen - it creates/updates the secret correctly - then removes it entirely from the worker. This is absolutely not proper - and caused an outage.


Please clarify licensing terms

Pypi says BSD-2-Clause, along with README.rst and sphinxcontrib/documentedlist.py.
Github says BSD-3-Clause and so does LICENSE.
I'm packaging this module for a linux distribution and I need to specify one of the two.
Thanks

My apologies.
Fixed by changing the LICENSE text to the 2-clause license.
Thanks for your effort packaging this for a distribution!


XStreamAutoConfiguration fails with property based @ComponentScan

Basic information

Axon Framework version: 4.5.4
JDK version:  15
Complete executable reproducer if available (e.g. GitHub Repo): N/A

Steps to reproduce
Have a class annotated with @ComponentScan on the class path that uses Spring property syntax in its
basePackages attribute, e.g. org.springframework.cloud.function.context.config.ContextFunctionCatalogAutoConfiguration.PlainFunctionScanConfiguration
Expected behaviour
Should not interfere with existing properties in scanned beans annotated with @ComponentScan
Actual behaviour
Fails loading Spring application context with Axon 4.5.4 and e.g. Spring Cloud Function in class path, throwing java.util.regex.PatternSyntaxException.

Thanks for the bug mark @maverick1601; we didn't test this specific.
I wonder if you're able to provide a more fleshed-out sample of an @ComponentScan annotated bean.
Right now, I sense a little ambiguity. I just want to make sure we fix the right thing.
As a quick workaround, you can exclude the XStreamAutoConfiguration from your project, by the way.
All you'd need to make sure if you do so is that you provide an actual XStream instance since Axon's XStreamSerializer no longer provides that.

The class that is causing us to fail is the following:
@Configuration(proxyBeanMethods = false)
	@ComponentScan(basePackages = "${spring.cloud.function.scan.packages:functions}", //
			includeFilters = @Filter(type = FilterType.ASSIGNABLE_TYPE,
					classes = { Supplier.class, Function.class, Consumer.class }))
	@ConditionalOnProperty(prefix = "spring.cloud.function.scan", name = "enabled", havingValue = "true",
			matchIfMissing = true)
	protected static class PlainFunctionScanConfiguration {

	}

Unfortunately, I am not able to provide more context, as of now.

Much appreciated @maverick1601!
We're stretched thin at the moment due to a number of conferences our engineers are presenting at.
I will be able to work on a solution on Thursday I think, however.
I will be sure to update this ticket accordingly as soon as work starts.


CommonJS support in browser

Frameworks like Component, Duo, etc... all let you use require() in the browser.  Unfortunately these lines of code causes js-base64 not to be usable by them:
if (typeof module !== 'undefined' && module.exports) {
    buffer = require('buffer').Buffer;
}

Is there a better way to determine if you are running in node?  If so we can use this library in the browser using CommonJS.  Thanks!

+1
comment these line save the problem but not beautiful

709d17d6819acf50e2b1799bdb7bace4781e1ea7 closed the issue as:
if (typeof module !== 'undefined' && module.exports) {
        try {
            buffer = require('buffer').Buffer;
        } catch (err) {}
    }

Same problem with SystemJS + Zone


added Hero-section #2

Related Issue

Info about the related issue

[x] KSOC Participant

[x] Contributor

Closes: #issue number that will be closed through this PR
Describe the changes you've made
Give a clear description what modifications you have made
Type of change
What sort of change have you made:

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

How Has This Been Tested?
Describe how have you verified the changes made
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Screenshots

Original
Updated

Original Screenshot
Updated Screenshot

I have pushed the changes as it was shown in the first screen shot.

I have pushed the changes as it was shown in the first screen shot.

Follow the PR template , make the necessary changes

I have made this hero-section


consolidate with rewrite

Merging in the refactoring-branch of the typescript rewrite to start work on consolidating and merging with latest improvements and bug-fixes of the master branch. All further work is based on this branch.
@timruffles @xStrom
As mentioned in #44 I did a few changes to get started:

[x] use tsconfig.json for TS config instead of grunt task config
[x] introduce TSLint
[x] implement setDragImage() in rewrite
[x] make sure latest bugfixes either are not needed in first place or are applied to rewrite

[x] #57 - Fixed.
[x] #54 - Fixed. Double check but since I'm using that lib too and have no issues I guess its fixed.
[x] #49 - Deliberately requiring a call to Initialize() because of reasons like that.
[x] #59 - Fixed.
[x] #58 - Fixed.
[x] #56 - This needs to be implemented.
[x] #55 - Fixed.
[x] #52, #53 - Fixed by enabling override hooks: 1dfd213
[x] #51 - Fixed.
[x] #37 - Fixed.
[x] #60 - Fixed.
[x] #62 - Fixed.
[x] #50 - Should be fixed. Double check.
[x] #23 - Fixed.
[x] #40 - The only browser I could not test is IEMobile. Could be it has native support? IEMobile has native support. Edge-Browser is untested yet.
[x] #42 - Fixed.

[x] Fixed. Current Mobile Safari seems to behave better now when shrink-to-fit=no is specified. find solution for Safari 9 zooming the whole webpage when a drag item reaches right edge of the viewport (they changed something from v8 to v9 that I couldn't come up with a solution yet), more specifically it seems to occur when drag starts and that the drag item initially is overlapping the right edge of the viewport. Maybe this can be hacked by initializing it in a way that makes sure its not overlapping the right edge.
[x] refactor code to allow hook for customizing drag start conditions
[x] refactor code to allow hook for default action when drag was not started
[x] refactor code to allow hook for scrolling a container or viewport when dragging close to an edge
[x] read transition duration for snapback transitions from drag image style instead of hardcoding it
[x] fix snapback transition target coordinates
[x] scrolling when dragging close to edges implemented as plugin
[x] defer UMD support until TypeScript 2.0
[x] #63 implement option to force the polyfill to be applied

As far as I can tell all improvements and bugfixes that went into master are now also implemented in the rewrite.
The latest commits also add override hooks:

drag start condition
default action when no drag was started
drag image translate

The latter enabled me to move all scrolling related code to a plugin, which now is able to handle nested scrollable containers and has a velocityFn so based on how much you get close to a scrollable container's edge will increase the scrolling speed. It still has its rough edges and corner cases but its ok for most usage scenarios.
The other two hooks are primarily focused on letting polyfill users do their custom thing when they need to. Whilst implementing them I discovered a few things that I wanted to point out here:

Not canceling touchstart/touchmove immediately will lead to problems once a hook decides to start the drag operation.

When doing a deferred drag start, a scrolling of the browser might be initiated and you won't be able to stop it. Also the translate of the drag image will not work right. It feels like a broken parallax-effect.
This happens especially often when the site is zoomed-in because then the browser most likely will start scrolling if not canceling the initial touchstart/touchmove.
The rule is: Once the browser starts scrolling to can't stop it. If a drag operation is then started it is broken.

Why NOT cancel the initial touchstart then?

No custom code for triggering the default action if the drag was not started (which kind of obsoletes the default action override hook)
Native scrolling will just work. You can make list items draggable by using a dedicated drag handle.

In my opinion this outweighs the possibly buggy behavior that results from a deferred drag operation start. Because most of these drag start conditions that need to defer the decision are doing so because they need to be able to scroll and would be better off by implementing a dedicated drag handle because its also the most obvious thing from a users perspective. If you have a drag start condition that can be determined immediately by looking at the initial touchstart/touchmove it won't produce any buggy behavior.

Really nice work by the looks of it!
Regarding myself, the plan is to do some review/testing tomorrow.

Fantastic stuff!

Thx :) As for the rename - what do you think about drag-drop-polyfill?

Sounds good to me!
On Wed, Mar 2, 2016 at 6:59 AM, Stefan Steinhart<EMAIL_ADDRESS>wrote:

Thx :) As for the rename - what do you think about drag-drop-polyfill?
—
Reply to this email directly or view it on GitHub
https://github.com/timruffles/ios-html5-drag-drop-shim/pull/61#issuecomment-191098177
.

I have no opinion about the name. All of them work for me.

Ok so lets name it drag-drop-polyfill.
How do we handle the rename?
To achieve a hassle-free publishing procedure I would like to include the release workflow as script. A quick research showed that npm already has some handy command: https://docs.npmjs.com/cli/version
But to do npm and bower simultaneously https://github.com/vojtajina/grunt-bump seems to be a good alternative, too.

Having a script do the release workflow seems like a good idea to me. Unfortunately I don't have any experience with publishing on npm/bower, so I don't have any opinion on how to exactly do it.
I'm not really a fan of compiled code under source control though. The diffs aren't understandable, malicous or buggy code can get through code review due to this, and it's just noise in general. Is that the common way of doing it for npm/bower?
If we do keep compiled code under source control, then I suggest we update it only with the release script and accept commits that modify these compiled files only from collaborators.

I'm not really a fan of compiled code under source control though. The diffs aren't understandable, malicous or buggy code can get through code review due to this, and it's just noise in general. Is that the common way of doing it for npm/bower?

For the release code this is true, yes. Otherwise you put the burden of compiling the package to the user, who might not uses any of the build setup infrastructure required for the package so they can't really use it easily.
Thats why there is a release folder in the project setup where the build results go. This is the folder that the users will get when installing the package. Everything else will be omitted so the footprint of files is as low as possible. Installing the package should not fetch demo files and source files. Those are only needed when developing.

If we do keep compiled code under source control, then I suggest we update it only with the release script and accept commits that modify these compiled files only from collaborators.

Yes, if people contribute, they contribute to the src files. Even when they commit release files they will be cleaned and overwritten once a maintainer does the release after merging pull requests.
The workflow would be:

merge changes and make sure everything is fine (git status is clean after that)
start the release script which will build, lint, run tests and after success trigger the version bump
version bump does raise version numbers, commit the release-code, make a tag and push it -> released.

Since committing/pushing is only possible for maintainers it is safe.
Right now this is manual work, so its prone to forget something.

We could just push each release as a history-less commit and tag them to
avoid them being garbage collected.
On Sunday, 6 March 2016, Stefan Steinhart<EMAIL_ADDRESS>wrote:

I'm not really a fan of compiled code under source control though. The
diffs aren't understandable, malicous or buggy code can get through code
review due to this, and it's just noise in general. Is that the common way
of doing it for npm/bower?
For the release code this is true, yes. Otherwise you put the burden of
compiling the package to the user, who might not uses any of the build
setup infrastructure required for the package so they can't really use it
easily.
Thats why there is a release folder in the project setup where the build
results go. This is the folder that the users will get when installing the
package. Everything else will be omitted so the footprint of files is as
low as possible. Installing the package should not fetch demo files and
source files. Those are only needed when developing.
If we do keep compiled code under source control, then I suggest we update
it only with the release script and accept commits that modify these
compiled files only from collaborators.
Yes, if people contribute, they contribute to the src files. Even when
they commit release files they will be cleaned and overwritten once a
maintainer does the release after merging pull requests.
The workflow would be:

merge changes and make sure everything is fine (git status is clean
after that)
start the release script which will build, lint, run tests and after
success trigger the version bump
version bump does raise version numbers, commit the release-code,
make a tag and push it -> released.

Since committing/pushing is only possible for maintainers it is safe.
Right now this is manual work, so its prone to forget something.
—
Reply to this email directly or view it on GitHub
https://github.com/timruffles/ios-html5-drag-drop-shim/pull/61#issuecomment-192866391
.

:shipit: Want a bit of a hand getting this shipped?

Yes, indeed. I'm very busy at the moment and will be for the coming weeks.

Hi, Any news on when this refactoring will be finished?

I want to get this done in the next two weeks but I can't promise anything because I'm very short of time.
Having said that you can expect very few breaking changes if any so you can directly reference this branch in your project until it is out officially.

Woah! So much is happening here I can't even keep up.
I see tons of bugfixes and things, but I just realized that for some reason ticket #5 is randomly closed. Technically cross-frame dragging is part of the html5 spec. It works rather well on the desktop.
@timruffles can you please re-open issue #5? This project is literally the only one where there is a hope of getting that support in a polyfill.

Any news about when this might be merged?

@felixruponen I'm still drowning in my day-job workload so I can't tell any timeframe. The remaining work is mostly around docs and demos though.

Merged to continue work in the dedicated rewrite branch as its now about demos, documentation and bug-fixes. Remaining work is documented here https://github.com/timruffles/ios-html5-drag-drop-shim/issues/69. Continuing with preparing the first beta release now.

First beta release based on the rewrite branch is available https://github.com/timruffles/ios-html5-drag-drop-shim/releases/tag/v2.0.0-beta.0

This looks amazing!
What are next steps - really want to see your great work get released. Anyone able to help @xStrom @reppners @nathanbedford ?

TODOs are tracked in #69.
I had started work on demos but lost all the progress due to a corrupted disk  :-/
What I really would like to be completed prior to release is the upgrade to TypeScript 2.x to support UMD and proper automatic generation of declaration files.
#87 has already started the upgrade.
So basically it's about making it easy to consume the polyfill.

Documentation/example work probably shouldn't be blocking the release. However I agree that there's value in waiting for the TS 2.x / module work.
I'll try to find some time to help see the 2.0 branch into a releasable state.


Implement Lazy Loading with Loader

To address this issue and enhance the user experience, I propose implementing lazy loading for images and other resources. Lazy loading will delay the loading of non-essential content until it's needed, reducing initial load times. Additionally, we'll incorporate a loader to provide visual feedback to users while content is being loaded.

@M-A-N-I-K Okay you can implement the feature in a new branch and it will be reviewed then.
All the Best !

The issue is complete
Thank you for your contribution


[8.x] Use lowercase OpenSSL cipher names

See https://github.com/laravel/framework/issues/38558 for the issue discussion leading up to this PR.
Problem
OpenSSL < 1.1.0 doesn't recognize AES-128-GCM as a cipher name, but aes-128-gcm (i.e. lowercase) is valid. This is caused by the fact that OpenSSL previously maintained upper- and lowercase names for ciphers as aliases, and for GCM a different alias was used instead (id-aes128-GCM). More recent versions of OpenSSL perform case-insensitive matching.
Prior to this PR, all cipher names are referenced in uppercase in Laravel, causing AES-128/256-GCM to not work on php versions using OpenSSL < 1.1.0. Assuming the following information is updated, this problem remains in PHP 8 (the requirement is OpenSSL ≥ 1.0.1): https://www.php.net/manual/en/openssl.requirements.php
The effect is that AES-128/256-GCM can't be used as the new default cipher in Laravel, which is unfortunate since it does provide some performance and theoretical security advantages over the CBC+MAC mode.
Solution
This PR instead passes lowercase strings to OpenSSL.
Backwards compatibility
The internal cipher name in Encrypter.php is untouched and strtolower() is only applied when being passed to OpenSSL. Also, uppercase strings are still supported in the config file and can be left unchanged. This keeps BC with any packages or extending code peeking at config('app.cipher') or $encrypter->cipher.
The other supported ciphers (only AES-128/256-CBC) has always used the lower- and uppercase names as aliases in OpenSSL, so there is no risk of lowercase CBC not working on older systems.

Thanks for the PR @Krisell. Appreciate your help with this 👍


vswhere.exe doesn't find anything

Setup
OS: Windows 11 (64-bit)
Dart version: 3.6.0
Problem
Simply invoking vswhere.exe without any other options just prints the logo and exits, causing the build process to crash when it can't find the compiler.
Invoking it like this:
"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath

Prints:
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools

Which seems to be what the code is trying to retrieve anyway. I only have Visual Studio Build tools installed (not Visual Studio), maybe that's why it's failing?

Hi @Keithcat1!
Thanks for the report.

I only have Visual Studio Build tools installed (not Visual Studio), maybe that's why it's failing?

That might be true. If the build tools do contain the compiler (cl.exe), we should be able to support that use case. 👍
Would you be willing to supply a PR s that it works for the case when only the build tools are installed? Then I can double check if it also works with full MSVC installed.


[cherry-pick][branch-2.5][Enhancement] Add lag metrics for PAUSED Kafka Jobs (#18558)

After Kafka Jobs is PAUSED unexpectedly, the lag offset is not updated. Then the operator can not get the lag offset metrics and alter the the job.
What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_fe_unittest


TIM - Add mouse tracker

Implement mouse position display widget
Separate mouse tracking from coordinates display.
Mouse coordinates reference is an element. Mouse coordinates are valid only within this element.
Mouse coordinates tracking

Listen to mouse events
Listening can be enabled or disabled.
Coordinates are specific to an element to provide
Is also provided with a coordinate transformation function (for scaling purpose)

Mouse coordinates display

Display must be positionned on the upper left corner of the target view
Display of mouse coordinates must be (almost) transparent
Display of mouse coordinates can be hidden or shown

Base example
Check mouse tracker example in Vue 3 guides

Avoid disabling tracker as it remove listeners and prevent to display shape creation.


Revert "Estimate gas for RRP fulfillments"

Reverts api3dao/airnode#1693
See: https://api3workspace.slack.com/archives/C02AYRX8D89/p1680604964571329

Github is able to create a revert PR. Since there were only tiny updates added after this PR this should be a clean revert.


Feature: add ability to call custom transaction functions

We'd like to be able to abstract away complex operations on transactions and still be able to chain them as part of a sequence of operations along with other simpler operations. Here's a simple example use case.
function insertTextOrSetSelection(tr, text, anchor, head, doInsert) {
    return doInsert
        ? tr.insertText(text)
        : tr.setSelection(TextSelection.create(tr.doc, anchor, head))
}

// what we want to be able to do
state.tr
    .chain(insertTextOrSetSelection, 'first', 1, 2, getDoInsert())
    .insertText('second')

// current workaround
const tr = state.tr
insertTextOrSetSelection(tr, 'first', 1, 2, getDoInsert())
tr.insertText('second')

You could imagine the branching logic within the custom function being a lot more complex, and maybe you'd even want to be able to chain multiple of them together.
Since this is my first time contributing to prosemirror, I wasn't sure if we want features to have an associated ticket in the github issue tracker, or only bugs. If so, I'll create one and link it to this.

I don't think introducing a regular function call in a piece of code is a big enough problem to justify a feature like this. For things like conditionals and loops you'll already have to leave the method chaining format, you can make calls on a local variable for custom functions as well, I'd say.

I'm probably misunderstanding what you're saying, but conditionals and loops are just what this would allow us to abstract away. For example, you could do tr.chain(fn) where fn contains any number of loops or conditionals that tack on modifications to the transaction.

Nevermind, I think I understand what you're saying. You're referring to the conditional within fn, which would not be chained, I guess. This new chain method is really just a way to abstract away this kind of complexity from the perspective of the caller, and so just to make sure I understand then, your opinion is that it's not worth adding this extra functionality to be able to create abstractions in these kinds of use cases?

Right, you could pass conditional or looping functions to chain, that's true. But I really don't think being able to chain everything is a very important thing for this interface to support, so no, I don't think this is worth adding.


Create Market Liquidity Issues

There's an issue happening in create market liquidity on the sportsbook branch. chwy said he was trying to make a market with liquidity on dev.augur.net and ran into bugs in unsigned orders and then when he went to the account management page and popped up the modal to sign his unsigned orders it also thew an error/blew up.

fixed - closing


Multiple Trees (along walk)

Add support for parsing multiple trees along each step of the path.
Needed to support templates as well as other option files.

Walk for one tree at a time, but provide for a get templates ==> multiple trees


Unable to Access Console and MyAccount After Configuring deployment.toml for "X509 Certificate Authenticator" Flow

Describe the issue:
After configuring the deployment.toml file to enable the "X509 Certificate Authenticator" flow, encountering issues with accessing both the console and MyAccount. The problem manifests as follows:
Console Login:
Users are able to log in to the console successfully.
However, upon login, the navigation does not proceed to the Getting Started page.
The console page remains empty, failing to load the expected content.
Browser Console Error:
In the browser console, a 400 status error is identified specifically with the /token endpoint.
Management Console Access:
It's noted that there are no issues accessing the management console.
How to reproduce:

Configure the deployment.toml file to enable the "X509 Certificate Authenticator" flow.[1]
Attempt to access the console and log in.
Observe the behavior described above.

Expected behavior:
Successful login should lead to the expected Getting Started page in the console. and able to proceed the flow
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: wso2is-7.0.0-beta6-SNAPSHOT
OS: Mac
Database: H2
Userstore: JDBC

Console view

Management Console

[1] https://is.docs.wso2.com/en/latest/guides/mfa/x509/ referred 6.1 docs since we don't have docs for 7.0 based

i hit the same error

This issue is no longer reproducible in the latest IS version. However the generated certificate or the CA certificate required to be added to the IS truststore.
A documentation issue is created for the missing/ confusing steps.

screen-capture.webm


Staging for version increment automation

Description
Gradle project: Staging to add gradle tasks (setVersion and versionIncrement) that support version increment automation for supported versions and add/update gradle.properties file to the project.
Related META issue
Part of: https://github.com/opensearch-project/opensearch-build/issues/1375
From solution: https://github.com/opensearch-project/opensearch-build/issues/1375#issuecomment-1159476686
Current Behavior
Version Increment is a process that needs to be done for all plugin repos during and after a specific release.
This is time consuming and includes lot of manual human effort (that can lead to multiple errors) to go through each repo, check for previous merged PR and then create a version increment PR, allow plugin team to review, follow-up, update the PR with suggestions and then finally get merged for CI to run.
Expected Behavior
After every release expect to raise an [AUTO] PR that increments the version.
Sample automation version increment PR's: job-scheduler, common-utils, anomaly-detection, k-NN
Proposed solution
Automate this version increment process across all plugin components, that increment’s the version, modifies the required files and raise a PR that awaits for plugin team approval, this way an engineer need not spend hours of time to increment the version for all plugin components.
Implementation Changes:
Add gradle versionIncrement and setVersion tasks to the project.
setVersion : This task will update the gradle property opensearch.version and updates the value in gradle.properties file.
gradle.properties : Contains gradle project properties that can be used by project during runtime, for version increment uses opensearch.version.
versionIncrement : This task is configurable and depends on the plugin requirement to modify any files where version is present and that needs to incremented, this task uses ant.replaceregexp to parse the required files that are added in include() section of the task.
Sample Implementation PR's: job-scheduler, common-utils, anomaly-detection, k-NN
More examples: https://github.com/opensearch-project/opensearch-build/issues/1375#issuecomment-1165692455

Hey the version increment PR for 1.3.5 https://github.com/opensearch-project/dashboards-reports/pull/420, has to have the plugin zip checked in every-time,  its hard moving forward with this manual process, can someone please take a look at this issue.
Thank you
@bbarani @dblock @joshuali925 @anirudha

Closing this issue as I see the task added to main, 2.x, 2.2 and 1.3 release branches.


Migrate to fsproj

Updated some packages too. Leaving framework at 1.0, as I don't know if AWS supports it yet. This is inline with the RC4 tooling, fsproj is not supported by Visual Studio 2017 and won't be in the first RTM, will likely come in the first update.

Cheers for this @slang25, I've tested locally using the dotnet command line tooling version 1.0.0-preview2-1-003177, unfortunately it throws the below error:
Couldn't find 'project.json' in current directory

I'm not seeing an updated dotnet core SDK that supports .fsproj, is this exclusive to the VS 2017 RC, or does it require this RC package here? https://github.com/dotnet/core/blob/master/release-notes/rc4-download.md

Hey, yeah you'll need the RC4 SDK, the commands are the same. Note that if you then want to with with project.json then you need a global.json file to force the SDK version

Another thing to remember is that vs2017 won't have support for dotnet core fsproj projects when it RTMs, this will hopefully come in a vs update.

@lukemerrett Updated to new tooling "proper". VS Code + Ionide required.


[CT-3175] Convert print call sites to logging events

Housekeeping

[X] I am a maintainer of dbt-core

Short description
There are two places where we currently call print, and should instead fire events. The reason these call print is that we don't want them to include timestamps or other formatting additions when sent to stdout. This enables easy copy-paste or piping to file/jq/etc.

Custom user print Jinja context method (source, docs).  Convert to a new UserPrint event.
dbt list with non-JSON logging (source). Convert to existing ListCmdOut event.

We also need a new behavior for the text + stdout logger (and only the combination of text + stdout). We should skip adding formatting (including timestamp/spacing) for the UserPrint + ListOutput events.
Acceptance criteria

[ ] Tests for these events with different loggers:

stdout + text-formatted → change: no formatting
stdout + JSON-formatted → no change
log file + text-formatted → no change
log file + JSON-formatted → no change

[ ] Catalog any remaining instances of Python print method within dbt-core codebase

Impact to Other Teams

IDE & CCLI to support custom user-provided print
CCLI will also need to implement the same no-formatting logic for UserPrint + ListOutput events

Will backports be required?
Let's just fix this going forward
Context

https://github.com/dbt-labs/dbt-core/issues/6543

@jtcohen6 if I understand correctly, this also affects the python CLI? I've been trying to suppress the output of the below command but it seems to ignore the -q and --no-print flags.
    command = ["ls", "--models"] + models + ["--output", "json", "--output-keys", "config", "name", "--project-dir", "../../../dbt/", "-q", "--no-print"]
    parse_result = dbtRunner().invoke(command)
    ```

Relates to #10030

We should consider deprecating the jinja print in favor of using log when working on this ticket.

Note: This may also close https://github.com/dbt-labs/dbt-core/issues/9174

There is one potential complication with the dbt list behavior, and it is related to @mrhallak's observation. We don't want to show the dbt version notification or line timestamps, etc., but we do want to show the list output itself. I think that's why we've left this as a print() for so long. So we'll need a plan to deal with that.

@peterallenwebb You're right about the need to hide timestamps. We suggest that users who wish to hide unrelated lines use dbt list --quiet, which suppresses all events that aren't "printed" to stdout — the output of dbt list should continue to appear.
Could you imagine adding logic within the EventManager such that:

certain events are "print-like" and not suppressed by --quiet
those same events should also not be prefixed with timestamps

@dbeatty10 has another good related proposal, which is that --quiet should actually be the default for dbt list (or at least dbt list --output json): https://github.com/dbt-labs/dbt-core/issues/7994


[BL702] bring up Bouffalo Lab BL702

Change overview

Add Bouffalo Lab BL702 chip (Thread) and lighting app example support.

Testing

Tested commission and lighting control with chip-tool running on Raspberry PI OTBR.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.wyhong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Implement trusted advisor addons recommendations

https://uktrade.atlassian.net/browse/DBTP-308
Fixing various trusted advisor recommendations and a few bugs encountered when redeploying return-to-office.
Recommendations and action taken:

Enable bucket logging for most buckets - adding a logging bucket and policy to s3 template
Enable bucket versioning on most buckets to prevent accidental deletion or overwriting - updated s3 template
S3 Block Public Access setting should be enabled at the bucket-level - set IgnorePublicAcls and RestrictPublicBuckets to true in s3 template
Amazon ECS Containers should only have read-only access to its root filesystems - set storage.readonly_fs: true in public and backend templates

Bugs with rds template:

MaxAllocatedStorage needs to be an int
EngineVersion 13.4 not supported

Looks like you have conflicts to resolve @gabelton.
Also, how has this been tested?

To resolve the conflicts... you will have to rebase main and make sure the templates folder is inside the commands folder.

I've resolved merge conflicts and, in terms of testing, I had to fix one of the make_config tests and tested manually by redeploying return to office and adding s3 buckets. I think there's probably a gap in our unit testing, though, because more tests should fail when I make several changes to rds and s3 templates. I don't know whether that belongs in this ticket or not though

I've created a ticket for adding more unit tests here https://uktrade.atlassian.net/browse/DBTP-338


Oauth

Oauth for google
May have to change/add client id<PHONE_NUMBER>70-6uourl66lqhb72a61263hnor0jckccgs.apps.googleusercontent.com) and client secret (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).
TODO After publishing

add the final published link to the google oauth page for it to work well.
add the final published link to django social part with admin

Make an .ENV for the secret and client id. Load that in via python-dotenv
Add these instructions to the README
so this works properly for deployment as well.

and when there are a lot of commits, we use squash and merge, it's cleaner

once env is setup you can add it with your next PR. Refresh the secret as well since by now it has been accessed by 85% of the world's hacking bots

    path('', quiz_views.home, name='home'),
    path('markdownx/', include('markdownx.urls')),
    path('admin/', admin.site.urls),
    # path('register/', quiz_views.register, name='register'),
    path('login/', auth_views.LoginView.as_view(template_name='quiz/login.html'), name='login'),
    path('logout/', auth_views.LogoutView.as_view(template_name='quiz/logout.html'), name='logout'),
    path('player/', include('player.urls')),
    path('task/', include('quiz.urls')),

    path('leaderboard/', quiz_views.leaderboard, name='leaderboard'),
    path("accounts/",include('allauth.urls')),
] + static(settings.STATIC_URL, document_root=settings.STATIC_ROOT)

    path('leaderboard/', quiz_views.leaderboard, name='leaderboard')
] + static(settings.STATIC_URL, document_root=settings.STATIC_ROOT)```

- There are some errors.
- Requirements.txt is missing some new deps.


Display group rooms by day

Do you want to request a feature or report a bug?
We want to display the day and then each room inside, in the work week view.
What's the current behavior?
Currently each room has its own set of days in the work week view.

Current progress is on the branch feature/dates-above-resources


asResolutionRoot does not affect validation

            container.Register(
                Made.Of(_ => ServiceInfo.Of</*ILoggerFactory*/_SerilogLoggerFactory>(),
                    f => f.CreateLogger(Arg.Index<Type>(0)),
                    r => r.Parent.ImplementationType),
                setup: Setup.With(condition: r => r.Parent.ImplementationType != null,
                    asResolutionRoot: false));

Currently this does not affect validation whatsoever because there's no exclusion of AsResolutionRoot == true services in the Validate, which is counterintuitive.
Originally posted by @Metadorius in https://github.com/dadhi/DryIoc/issues/577#issuecomment-1564329201
One option would be amending the default validation condition which would probably make more sense in general conditions (usually there's not many resolution roots) but would break the default behavior: https://github.com/dadhi/DryIoc/issues/577#issuecomment-1564362538
Another option is:

I would rather filter all registrations based on the IsResolutionRoot, then if nothing found fallback to the current behavior.

Originally posted by @dadhi in https://github.com/dadhi/DryIoc/issues/577#issuecomment-1564377235

Hello! Been checking for a while, is there any ETA on the new version release?

@Metadorius No promises, but will try to release this weekend.

@Metadorius Released right now, it might be some time until NuGet will index the 5.4.1 version.


Modified this to make sure we can display the documentation in the De…

…veloper Hub.

Changes within this PR were implemented as part of the API platform config story and have been merged to master. Closing PR.


Import campus farms and gardens content/project type

Import that data campus farms and gardens data from Lindsey MacDonald into a Campus Farm content type. This should come after importing resources from our current site (e.g., solar pv database, green funds).

Moving to Sprint 1 temporarily for discussion. This resource may now be outdated and not worth adding. I believe Lindsey was anxious to do this a while ago but has not been in contact for a while?


Showing a Specific Commit

I didn't find a method for getting a specific commit so I added this to phpGitHubApiCommit.php
public function getCommit($username, $repo, $branch, $path)
{
$response = $this->api->get('commits/show/'.urlencode($username).'/'.urlencode($repo).'/'.urlencode($branch).'/'.urlencode($path));
return $response['commit'];

}

My new comment


fix(waku/client): CJS import hack

close #129

Oooookay, this is tricky. (I really hope there issues are resolved by official Vite bindings...)


Add special handler to allow logger messages during shutdown

This gets rid of those pesky FATAL Unable to register shutdown hook because JVM is shutting down. messages.
Previously the shutdown hooks fire essentially at random. This was causing logging messages to regularly be lost during the shutdown cycle if the log4j shutdown hook was fired before some of the ones that use logging in their shutdown messages.
This patch (with the appropriate server setting) causes the logger shutdown to fire as the last lifecycle.stop() item.
Omitting the server property simply reverts to the prior behavior of regularly discarding logger messages during shutdown.

Example without this patch:
2015-05-22T23:13:46,153 INFO [main] com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler - Invoking start method[public void io.druid.server.coordination.AbstractDataSegmentAnnouncer.start()] on object[io.druid.server.coordination.BatchDataSegmentAnnouncer@7df01c0f].
2015-05-22T23:13:46,153 INFO [main] io.druid.server.coordination.AbstractDataSegmentAnnouncer - Announcing self[DruidServerMetadata{name='localhost:8081', host='localhost:8081', maxSize=10000000000, tier='_default_tier', type='historical', priority='0'}] at [/druid/announcements/localhost:8081]
2015-05-22T23:13:46,670 INFO [Thread-52] com.metamx.common.lifecycle.Lifecycle - Running shutdown hook
2015-05-22 23:13:46,703 FATAL Unable to register shutdown hook because JVM is shutting down.

Example WITH this patch:
2015-05-22T23:14:46,373 INFO [main] io.druid.server.coordination.AbstractDataSegmentAnnouncer - Announcing self[DruidServerMetadata{name='localhost:8081', host='localhost:8081', maxSize=10000000000, tier='_default_tier', type='historical', priority='0'}] at [/druid/announcements/localhost:8081]
2015-05-22T23:14:48,511 INFO [Thread-52] com.metamx.common.lifecycle.Lifecycle - Running shutdown hook
2015-05-22T23:14:48,514 INFO [Thread-52] com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler - Invoking stop method[public void io.druid.server.coordination.AbstractDataSegmentAnnouncer.stop()] on object[io.druid.server.coordination.BatchDataSegmentAnnouncer@18a7811e].
2015-05-22T23:14:48,514 INFO [Thread-52] io.druid.server.coordination.AbstractDataSegmentAnnouncer - Stopping class io.druid.server.coordination.BatchDataSegmentAnnouncer with config[io.druid.server.initialization.ZkPathsConfig@58d3f4be]
2015-05-22T23:14:48,514 INFO [Thread-52] io.druid.curator.announcement.Announcer - unannouncing [/druid/announcements/localhost:8081]
2015-05-22T23:14:48,535 INFO [Thread-52] com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler - Invoking stop method[public void io.druid.server.coordination.BaseZkCoordinator.stop()] on object[io.druid.server.coordination.ZkCoordinator@86e795a].
2015-05-22T23:14:48,535 INFO [Thread-52] io.druid.server.coordination.ZkCoordinator - Stopping ZkCoordinator for [DruidServerMetadata{name='localhost:8081', host='localhost:8081', maxSize=10000000000, tier='_default_tier', type='historical', priority='0'}]
2015-05-22T23:14:48,538 INFO [Thread-52] com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler - Invoking stop method[public void io.druid.curator.announcement.Announcer.stop()] on object[io.druid.curator.announcement.Announcer@1eac5edf].
2015-05-22T23:14:48,539 INFO [Thread-52] io.druid.curator.announcement.Announcer - unannouncing [/druid/segments/localhost:8081/localhost:8081_historical__default_tier_2015-05-22T23:14:46.300Z_3f633ec82ac044cf87bfbd06f452026d0]
2015-05-22T23:14:48,540 INFO [Thread-52] io.druid.curator.CuratorModule - Stopping Curator
2015-05-22T23:14:48,545 INFO [Thread-52] org.apache.zookeeper.ZooKeeper - Session: 0x14d2f23309e0112 closed
2015-05-22T23:14:48,545 INFO [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down
2015-05-22T23:14:48,558 INFO [Thread-52] org.eclipse.jetty.server.ServerConnector - Stopped ServerConnector@6a3cb917{HTTP/1.1}{<IP_ADDRESS>:8081}
2015-05-22T23:14:48,560 INFO [Thread-52] org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@3441ba3a{/,null,UNAVAILABLE}
2015-05-22T23:14:48,566 INFO [Thread-52] com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler - Invoking stop method[public void com.metamx.metrics.MonitorScheduler.stop()] on object[com.metamx.metrics.MonitorScheduler@44b641c4].
2015-05-22T23:14:48,567 INFO [Thread-52] com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler - Invoking stop method[public void com.metamx.emitter.service.ServiceEmitter.close() throws java.io.IOException] on object[com.metamx.emitter.service.ServiceEmitter@2fc64742].
2015-05-22T23:14:48,567 INFO [Thread-52] com.metamx.emitter.core.LoggingEmitter - Close: started [false]
2015-05-22T23:14:48,567 INFO [Thread-52] com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler - Invoking stop method[public void com.metamx.emitter.core.LoggingEmitter.close() throws java.io.IOException] on object[com.metamx.emitter.core.LoggingEmitter@3b53bb3b].

Bummer about the shutdown hooks.
Some questions:

Does the code actually get called? It doesn't look like anything is injecting the QuietLoggerShutdown and I dunno if it will actually get instantiated.
Is it possible to do something useful without needing a property? If not, how about emitting a warning on startup if the property isn't there, so people know they have a less than perfect setup?
Is the dependency worth it or is it doing something really simple that we could just do ourselves?

@gianm : The dependency is exactly one java class https://github.com/DjDCH/Log4j-StaticShutdown/blob/master/src/main/java/com/djdch/log4j/StaticShutdownCallbackRegistry.java that we would pretty much have to copy to get the functionality. It is MIT license so direct copy is probably a no-go.
The CLI classes pickup ManageLifecycle automagically.
This will not function at all without the property.

Looking at what that class does, it basically just extends Log4j's ShutdownCallbackRegistry.  It's pretty difficult to do programmatic stuff to adjust the configuration of the log4j subsystem when you use properties files to initialize it.  We essentially need to set the system property before the log4j system is initialized.
I believe it is initialized by the first call to LoggerFactory.getLogger() in com.metamx.common.logging.Logger.
So, if we were to actually add a static initializer there to set the system property for us, we would likely be able to register our own shutdown handler instead of having it use the internal one.
I would then recommend that we create our own ShutdownCallbackRegistry that

Registers with the normal JVM shutdown hook
On start() removes the JVM shutdown hook
On close(), if start() was called, shuts things down, if start() was not called, is a noop.

@cheddar : Doing such a thing in the Logger would also be a multi-system intrusion of log4j instead of slf4j abstraction.
We cannot rely on the JVM shutdown hook because they are fired essentially randomly. We have to be in able to specify that the logger shutdown hook runs after the Lifecycle shutdown, which is not the case if both are registered as shutdown hooks (unless you know some magic you would like to share :) )

@cheddar : Modified

Is it at all possible to add a check somewhere that can notice if the static property setting stuff was too late and warn/error about it?

@cheddar There is now a check in the configure step via class cast and a warning if the class cast fails.

:+1:

@gianm  / @cheddar   updated to 2.4.1 to eliminate the need for reflection

still :+1:


Shared FilePool

In iOS/iPadOS, an AU plugin's process is shared.
In order to reduce its memory, I made this changes.
It's Ok if this PR is not approved.

Thanks, this is a longstanding request! I'll need some time to review it though, global structures can be a bit tricky in this context.

As errors occur, I temporally close this PR.

you can use draft PRs in GitHub if needed, it's not a problem if there are failures with CI anyway.

Yeah you can keep using this PR to test if needed, no worries.


start updating documentation; add x1dints reader for JWST/ERO transit data

This pull request:

starts updating a bunch of the documentation
adds a reader for x1dints files with no int_times and one that's able to handle the multiple orders needed for NIRISS
changes a bunch of function names to make the documentation cleaner. These should mostly be intuitive to figure out, but some of your code might break temporarily because of this.

@catrionamurray , here's a reader that should hopefully work with something like:
from chromatic import *
w96 = read_rainbow('niriss/jw02734/jw02734002001/jw02734002001_04101_00001-seg00*_nis_x1dints.fits', order=1)
w96.trim().normalize().pcolormesh(vmin=0.95, vmax=1.05);

or
from chromatic import *
h18 = read_rainbow('niriss/jw02734/jw02734001001/jw02734001001_04101_00001-seg00*.fits', order=1)
h18.trim().normalize().pcolormesh(vmin=0.95, vmax=1.05);

@catrionamurray , watch out that I got carried away and did this in my update-docs branch, where I change the name of a few chromatic methods. I think the replacements should be pretty intuitive to identify, but please be aware your code might break if it's calling on something that had a name change.


@npmccallum In the case of official "Google Authenticator" app I'm using (3.1.1, iOS), it seems to ignore the label prefix, and only display Issuer when it is specified as a parameter.

@npmccallum In the case of official "Google Authenticator" app I'm using (3.1.1, iOS), it seems to ignore the label prefix, and only display Issuer when it is specified as a parameter.
Originally posted by @rophy in https://github.com/freeotp/freeotp.github.io/pull/51#issuecomment-809862683

@npmccallum In the case of official "Google Authenticator" app I'm using (3.1.1, iOS), it seems to ignore the label prefix, and only display Issuer when it is specified as a parameter.
Originally posted by @rophy in https://github.com/freeotp/freeotp.github.io/pull/51#issuecomment-809862683

@gorwhh - Please stop. I don't know what you are doing, but its just making issues in Apktool for seemingly no reason.


pls add sftp support

get /usr/libexec/sftp-server from openssh and get /usr/lib/libcrypto.0.9.8.dylib from openssl, and then put them to bootstrap.tar, thx

Don't you think it's better to modify the OS just the way you want it to be?


sbcl: 1.4.0 -> 1.4.1

Motivation for this change
Update sbcl to the last version
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg maxima

(if I don't have permissions, at least I will know how the failure looks like)

My nox reports build failures: (no idea if this is new)
; compiling (DECLAIM (INLINE MAKE-STATIC-VECTOR))
; compiling (DEFUN MAKE-STATIC-VECTOR ...)
; compiling (DEFINE-COMPILER-MACRO MAKE-STATIC-VECTOR ...)builder for ‘/nix/store/q42750p8qdb3mcrik8yxwm8dw8jvlxaf-lisp-iolib-v0.8.3.drv’ failed with exit code 1
error: build of ‘/nix/store/q42750p8qdb3mcrik8yxwm8dw8jvlxaf-lisp-iolib-v0.8.3.drv’ failed

iolib in some versions of lispPackages (there are options for different ASDF) could fail, that's true.

@GrahamcOfBorg maxima

I bumped SBCL to an unstable revision after looking the upstream bug tracker… The iolib failure was fixed by the upstream fixes.


Ask for location permission != Display location permission

Making the title and body finally agree with each other.

Also what does turning this off mean? Does it mean go ahead and don't ask for permission and do things anyway? Or does it mean don't even attempt to do the thing in the first place? As you can see is just not clear.


Fixed compilations issues

github.com/creack/go-splice
../../creack/go-splice/splice.go:97: invalid operation: written + w (mismatched types int64 and int)
../../creack/go-splice/splice.go:99: invalid operation: written += w (mismatched types int64 and int)

Coverage remained the same at 96.15% when pulling a06f37a1f7f53d5fdca217f6cc2739e3605072b7 on icorderi:patch-1 into 435d01907613e5f203fd5cde4c81b77860c43607 on creack:master.

thanks


404's on the web-based admin interface

I understand that this may be related to changes in 0.9.0, but how do we get the web-based admin interface to work again. Had influxdb-0.8.8 installed, and removed it with rpm -e influxdb-0.8.8-1.x86_64

In 0.9.0 the admin UI is available at http://localhost:8083.

yes, that's where I proxy requests using Nginx. I can see the UI but all queries returns 404.

@skynet sounds like it might be a problem with how you're using nginx.  does it work without nginx?

I wish it was a problem with Nginx since that's something I can easily fix. But no, it isn't. All requests are transparently proxied through Nginx. And running it like this still fails:
> curl 'http://<IP_ADDRESS>:8083/query?u=root&p=root&q=SHOW%20DATABASES' 404 page not found

@skynet it looks you're trying to send queries to the admin port (8083). they should be getting sent to API port (8086).

@toddboom - you were right. I just realized that in order to run this in a Web browser remotely I also need to proxy localhost:8086 through Nginx. Thanks, everyone!


Rough Fire Diamond Recipe Should Use Diamond

The current recipe claims to need a rough ruby which is an invalid combination, It should be a rough diamond in actuality.

#51 closes this


Refactor and simplify logic in tags macro

See https://github.com/cfpb/cfgov-refresh/pull/288#discussion_r25460334

Fixed in https://github.com/cfpb/cfgov-refresh/pull/316


Touchable onPress not triggering after switch to RN62.0 from RN61.5

#27243  Description
Touchable components onPress functions are not triggering when after upgrade to RN62.0 from RN61.5 in debug mode in pretty much 100% of the cases. Also sometimes it happens not just in debug mode. It all happens after 3-5 seconds from application boot.
React-native-gesture-handler touchables are still working.
The problem is probably because the JS thread gets busy and can't process the onPress events. Older version of react-native had no such problem. We still use the react-native-debugger and not Flipper solution.
React Native version:
System:
OS: Linux 5.3 Ubuntu 18.04.3 LTS (Bionic Beaver)
CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
Memory: 2.44 GB / 62.74 GB
Shell: 5.4.2 - /usr/bin/zsh
Binaries:
Node: 8.13.0 - ~/.nvm/versions/node/v8.13.0/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v8.13.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
react-native-reanimated: 1.4.0
Steps To Reproduce
The least steps we do to reproduce the error.

Starting from an RN 0.62.0 code, things are frozen.
If we downgrade react-native to 0.61.5 and react versions from 16.11.0 to 16.9.0 then the problem disappear.
Run yarn to downgrade packages.

Expected Results
Touchable components should work the same after upgrading react-native version to 0.62.0 from 0.61.5. Also the JS thread should not be frozen.
Snack, code example, screenshot, or link to a repository:
We expect the same things happen on example react-native code.

Is this in debug mode?

Is this in debug mode?

Yes.

Is this in debug mode?

Yes, in debug mode it is reproducible with high chances.

Yeah same thing for me. I tried on old upgraded project and created a new clean one. In both cases it looks like debugger silently lost connection, thats why its not working ( I think). Without debug it works ok.
** Env:
System:     OS: macOS Mojave 10.14.6     CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz     Memory: 257.77 MB / 16.00 GB     Shell: 3.2.57 - /bin/bash   Binaries:     Node: 10.13.0 - /usr/local/bin/node     Yarn: 1.21.1 - /usr/local/bin/yarn     npm: 6.4.1 - /usr/local/bin/npm     Watchman: 4.9.0 - /usr/local/bin/watchman   SDKs:     iOS SDK:       Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1     Android SDK:       API Levels: 17, 23, 25, 26, 27, 28       Build Tools: 26.0.3, 27.0.0, 27.0.1, 27.0.2, 27.0.3, 28.0.0, 28.0.0, 28.0.0, 28.0.1, 28.0.2, 28.0.3       System Images: android-17 | ARM EABI v7a, android-17 | MIPS, android-17 | Intel x86 Atom, android-17 | Google APIs ARM EABI v7a, android-17 | Google APIs Intel x86 Atom, android-19 | Google APIs Intel x86 Atom, android-25 | China version of Android Wear ARM EABI v7a, android-25 | China version of Android Wear Intel x86 Atom, android-25 | Android Wear ARM EABI v7a, android-25 | Android Wear Intel x86 Atom, android-25 | Intel x86 Atom, android-25 | Intel x86 Atom_64, android-25 | Google APIs ARM 64 v8a, android-25 | Google APIs ARM EABI v7a, android-25 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom_64, android-25 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64       Android NDK: Not Found   IDEs:     Android Studio: 3.3 AI-182.5<IP_ADDRESS>14842     Xcode: 11.3/11C29 - /usr/bin/xcodebuild   Languages:     Python: 2.7.15 - /usr/local/bin/python   npmPackages:     @react-native-community/cli: Not Found     react: 16.11.0 => 16.11.0      react-native: 0.62.0 => 0.62.0    npmGlobalPackages:     *react-native*: Not Found
I am seeing same error logged multiple time in LogCat during app start:
`
2020-04-02 00:12:15.801 17598-17854/com.myapp E/unknown:ReactContextBaseJavaModule: Unhandled SoftException
java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by WebSocketModule
at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:67)
at com.facebook.react.modules.websocket.WebSocketModule.sendEvent(WebSocketModule.java:62)
at com.facebook.react.modules.websocket.WebSocketModule.access$100(WebSocketModule.java:40)
at com.facebook.react.modules.websocket.WebSocketModule$1.onMessage(WebSocketModule.java:187)
at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:322)
at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219)
at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105)
at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:273)
at okhttp3.internal.ws.RealWebSocket$1.onResponse(RealWebSocket.java:209)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
`

Same here for me.

In noticed that it's not triggered (in my case) when you do a longPress.

i have same error with debug enable in iOS

This is an interesting issue, maybe it has connections to the react-native-gesture-handler library? I also use that. Also I only tested this issue on Android, I don't know if this is the same on iOS.

Same issue but I don't have the same message in logcat as @inpendio
No real error messages for us, just no action from the touchables.

This fixed the issue for me:
https://github.com/facebook/react-native/issues/27008#issuecomment-592048282

Same issue
error message:
E/unknown:ReactContextBaseJavaModule: Unhandled SoftException
    java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by WebSocketModule
        at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:67)

info:
System:
    OS: Windows 10 10.0.18362
    CPU: (8) x64 Intel(R) Core(TM)
    Memory: 2.94 GB / 15.85 GB
  Binaries:
    Node: 12.16.1
    Yarn: 1.22.4
    npm: 6.13.4
    Watchman: 20200604.181126.0
  SDKs:
    Android SDK:
      API Levels: 20, 23, 26, 27, 28, 29
      Build Tools: 26.0.2, 27.0.3, 28.0.3, 29.0.3
      System Images: android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-192.7<IP_ADDRESS>41897
  Languages:
    Java: 1.8.0_181
    Python: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2

Hi @Sixzero than you for the issue!

This fixed the issue for me:
#27008 (comment)
Did this help solve your issue?

I'll close this issue as a dup of the issue filed above ^


package registry

Have you considered registering your package in the Julia package registry? It would make it easier for other people (such as me) to use your package in their projects. Do you need support with that?

Hi, thanks for reaching out, and sorry for the late response.
Please, feel free to do it as I am currently overcommitted. Otherwise, let me know if you need any help, I will try to answer faster.
Cheers!

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/58475
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.1 -m "<description of version>" ac0375c5b05a44bdb0f2f98fd1584d742ea0b153
git push origin v0.4.1

Also, note the warning: This looks like a new registration that registers version 0.4.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/58476
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.5.0 -m "<description of version>" cecf5b35fcf467c75a67042a10050fd859aae831
git push origin v0.5.0

Also, note the warning: This looks like a new registration that registers version 0.5.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Error while trying to register: "Tag with name v0.5.0 already exists and points to a different commit"

@JuliaRegistrator register()

Error while trying to register: "Tag with name v0.5.0 already exists and points to a different commit"

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/58632
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.6.0 -m "<description of version>"<PHONE_NUMBER>f68c8a6c9471d0884c1c52f5d06c6e
git push origin v0.6.0

Also, note the warning: This looks like a new registration that registers version 0.6.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@alexriss done!
https://github.com/JuliaRegistries/General/pull/58632

That is great, thank you for your efforts!


Specifying Go Version

It would be helpful to have the ability to specify the version of Go compiler itself too - and maybe also the version of dep (should panic or prompt for a dep update, pretty much like pip).
(I searched the issues and failed to find it; if it got proposed.)

hi, welcome, thanks for the issue!
Go versions is #223 - expressed a little differently, so easy to miss 😄
As for dep versions, it's possible we may do it in the future via explicitly versioning the Gopkg files. But for now, we're going to try to avoid it, managing it ad hoc by having there only be additions to the file structure, and warn when unrecognized fields are there (which would generally be an indication that your tool may be out of date).
(closing as dup)


The query about raw CSI data manifestation (AEGHB-484)

Hi There,
When I tried the sub-tasks "csi_recv_router" on different routers.
They just responded CSI raw data in the different format layouts as follows (I skipped other information):

CSI_DATA, e8:48:b8:e9:2b:b1:[0,0,0,0,0,0,0,0,0,0,0,0,1,-3,2,-2,3,-2,4,-1,4,-1,5,0,5,0,6,1,6,1,6,1,5,2,5,2,4,3,3,3,3,4,2,5,1,6,0,6,-1,7,-1,7,-2,8,-2,8,-2,8,-2,7,-3,6,-3,5,0,0,-4,3,-4,1,-5,0,-6,-2,-7,-2,-8,-3,-9,-3,-10,-3,-11,-3,-12,-3,-12,-2,-11,-1,-10,-1,-9,0,-7,0,-5,0,-3,-1,-1,-2,1,-3,3,-5,4,-8,4,-10,5,-12,4,-14,3,-16,2,-17,0,0,0,0,0,0,0,0,0,0]

2.CSI_DATA,54:b8:0a:7e:62:64:
[0,0,13,-6,11,-6,8,-5,6,-5,2,-5,-1,-6,-4,-7,-6,-8,-8,-9,-10,-10,-12,-12,-12,-13,-13,-14,-13,-14,-12,-15,-11,-15,-10,-14,-8,-13,-7,-11,-5,-8,-5,-5,-5,-2,-5,1,-6,4,-8,6,-9,8,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,2,6,5,8,6,11,7,13,7,15,7,17,6,18,5,18,4,18,2,17,1,15,1,13,1,11,2,8,2,4,4,2,5,-1,7,-3,9,-5,11,-7,12,-8,14,-9,15,-9,17,-9,17,-9,16,-8]"
I was wondering why I got these two different data patterns since the only difference was the router.
Parts of the null subcarriers are at the start, middle, and end based on my understanding. However, I was not able to figure out the second one. Seems the data is still fine but different sequences, and the null subcarriers line in the middle of the data packet. What is the possible reason for that? Cuz I won't know where I should start to compute for the second one.
Hope someone can give me a guide for it.

The format of CSI data from wireless packets with different channels and bandwidths may vary. To obtain well-organized CSI data, the 'valid_data' field in the 'wifi_csi_filtered_info_t' structure can be utilized.

Do you mean the function in "/esp-csi/tree/master/examples/esp-radar/console_test/main)
/app_main.c"?

yes, exactly.

For the order of the CSI raw values I acquired, were they collected in sequence like subcarrier 1,  subcarrier 2, ... or not?
I am not quite sure about the order of the data array.
Or I have to put another rule to sort them?

Hi @4444monkey ,
The issue you mentioned here can be referenced in https://github.com/espressif/esp-csi/issues/139.

So in light of the question I lised above, there were only 52 valid subcarriers over the acquired 64 subcarriers regardless of the order and the data packet varies from the PHY standard.
If I have to process the CSI data analysis further, I may decide the order among them, correct?
Just hope I catch the right point about that and thanks for your reply.

So in light of the question I listed above, there were only 52 valid subcarriers (104 bytes) over the acquired 64 subcarriers (128 byte) regardless of the order and the data packet varies from the PHY standard. If I have to process the CSI data analysis further, I may decide the order among them like subcarrier 1, 2, 3, ..., correct? Just hope I catch the right point about that since not much info about CSI order in that discussion. Thanks for your reply.

Got it, we will reach the internal R&D to confirm the order of subcarrier among CSI data with different formats and keep you informed of any progress.

Splendid! Thanks for your support.

May I answer your latest progress on this issue?I also want to know the order of subcarrier among CSI data with different formats.Thanks for your reply.

May you answer the latest progress on this issue?I also want to konw the order of subcarrier among CSI data with different formats.Thanks for your reply.

May you answer the latest progress on this issue?I also want to konw the order of subcarrier among CSI data with different formats.Thanks for your reply.


Refactor passed message to Dialogue Utterance

This is the first of several mini-PRs that will cover the changes proposed in https://github.com/PTG-Kitware/angel_system/pull/378
We should remove the previously used messages upon confirmation of working implementation.

@Purg @hdefazio @joshanderson-kw
I'm trying to run ./angel-workspace-shell.sh -r to test and apply the code style. However, I have been facing the following error ever since the latest changes:
(base) da2985@multilingual:/local/data/derekahmed/angel_system_vocal$ ./angel-workspace-shell.sh -r
[INFO] Creating local xauth file: /local/data/derekahmed/angel_system_vocal/.container_xauth/local-ZI4nnF.xauth
xauth:  file /home/da2985/.Xauthority does not exist
xauth: (argv):1:  bad display name "" in "nlist" command
xauth: (argv):1:  unable to read any entries from file "(stdin)"
[INFO] Using container tag: latest
[INFO] Using v2 docker compose plugin
./workspace_entrypoint.sh: line 15: /angel_workspace/install/setup.bash: No such file or directory
[INFO] Container run exited with code: 1
[INFO] Removing local xauth file.


Know More button not working on mobile view

I would like to work on this issue sir. please assign it to me.

Okay!

And can I send the PR on 1st October for the count in Hacktoberfest?

Okay, you can do it on 1st of October.

resolved the #235 issue.
Please review it and accept so that my contribution for hacktoberfest can also be counted.
Best regards,
Shashwat.

Got your pr and it's working now.
Thanks!


Feat(eos_cli_config_gen): Add support for IPv4 BGP Labeled-Unicast (BGP-LU)

Change Summary
This PR is based on the other IPv4 Address-Families and adds support for BGP-LU
Related Issue(s)
Fixes #4380
Component(s) name
arista.avd.python-avd
Proposed changes

Many - the datamodel is based on pre-existing ones. All changes live under router_bgp.address_family_ipv4_labeled_unicast
How to test
molecule tests added
Checklist
User Checklist

N/A

Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

converting to draft since we need to confirm some data model choices. Thanks!


AWS Amplify deployments failing for Next.js app (PNPM)

Description
None of our deployments are succeeding as each build reaching Extracting cache... and just hangs until it times out on 30 minutes.
Nothing has changed on our side for this to break and it seems a few issues have been raised around this already.
This is high priority as it is blocking our deployments!

https://github.com/aws-amplify/amplify-backend/issues/1772
https://github.com/aws-amplify/amplify-backend/issues/1765

As per @Jay2113's comment here, I have tried this and no success?
            cache:
                paths:
                - node_modules/**/*
                - $(pnpm store path)

I have confirmed that npm does not have the same issue and the app deployment was fine.. so this must related specifically to pnpm

Hi @TomBell95, we are investigating into it and in the interim can you remove the cache path from the build specification or amplify.yml file, and then redeploy your application?

Thanks @Jay2113 - I have responded on the other thread - https://github.com/aws-amplify/amplify-backend/issues/1765#issuecomment-2245473944
That didn't work unfortunately...

@TomBell95 We have identified the root cause of the issue. Please find the details below:
Amplify experienced a problem extracting cache artifacts for pnpm builds in the regions ca-central-1, eu-south-1, us-east-2, us-east-1, eu-west-1, and ap-southeast-1. The issue has been resolved and the service is operating normally. You can retry any failed deploys from the Amplify Console.
Can you please retry and confirm if you are now unblocked?

Deployed my app d1qqp0zr1l3zrm and it looks to be working.
Thanks for the swift help @Jay2113


Only returning "😶" as replies.

As far as I know I've done everything right and I have the cog fully configured and using my api token. Is there something obvious that I'm missing?

Currently it's working fine for me, I usually get 😶 when you talk moderated stuff to the bot.
Have you tried talking normal stuff to it?
Also, when there's a error or a 😶 response there should be something in your bot logs, if ur on linux try journalctl -feu redbot
Source: https://github.com/zhaobenny/bz-cogs/blob/c511c968de67bedf12fc67fc036248eb5951cf52/ai_user/response/response.py#L25

Currently it's working fine for me, I usually get 😶 when you talk moderated stuff to the bot.
Have you tried talking normal stuff to it?
Also, when there's a error or a 😶 response there should be something in your bot logs, if ur on linux try journalctl -feu redbot
Source: https://github.com/zhaobenny/bz-cogs/blob/c511c968de67bedf12fc67fc036248eb5951cf52/ai_user/response/response.py#L25

Yes, I've tried with normal chats and same result. I tried journalctl -feu redbot but no output was ever produced.

Well, you should replace redbot with your bot instance/service name. It was an example.

Well, you should replace redbot with your bot instance/service name. It was an example.

My instance name IS redbot actually. I'll double check though.

journalctl should output the bot console, you could also try sudo service botname status

journalctl should output the bot console, you could also try sudo service botname status

Name was red@redbot surprisingly. I'm getting an error stating that I've exceeded my quota, but I can use chatgpt just fine.

journalctl should output the bot console, you could also try sudo service botname status

Name was red@redbot surprisingly. I'm getting an error stating that I've exceeded my quota, but I can use chatgpt just fine. I generated a brand new api key to use for this, so it was in my clipboard making mistyping it impossible. Is this a plus account only thing?

It's not a plus thing, but from my previous experience, api keys might still work up to 48 hours after expired/overquota'd.
If you're using a trial account, and you're out of credits, well it's gg unless you create another trial account

journalctl should output the bot console, you could also try sudo service botname status

Name was red@redbot surprisingly. I'm getting an error stating that I've exceeded my quota, but I can use chatgpt just fine. I generated a brand new api key to use for this, so it was in my clipboard making mistyping it impossible. Is this a plus account only thing?

It's not a plus thing, but from my previous experience, api keys might still work up to 48 hours after expired/overquota'd.
If you're using a trial account, and you're out of credits, well it's gg unless you create another trial account

Ahhhh. My trial credits expired a week ago. Thanks for the quick help!

Thanks for the help, @DJTOMATO! 🔥


Why is gxx required as run dependency?

Comment:
Curious about the purpose of having a c++ compiler as a run dependency for pytensor?
I ran build-locally.py without the gxx dependency and it seemed to build OK, not sure if any pytensor features would be affected at runtime though.

It's used by the C backend, see pytensor/link/c/cmodule.py


doc: Clarify when to rebase a non-conflicting PR and how

Issue being fixed or feature implemented
Issues with rebasing non-conflicting pull requests on top of the updated target branch:

It's ~impossible~ annoying to run gfd on each rebase to verify that it was indeed a clean rebase ~if you did not pull the original/previous version~ (it is possible actually, must use full commit hash)
Github GUI is pretty much useless if a target branch update was huge

Because of (1) and (2) if a rebase was done in the middle of your review you have to basically start your review from scratch which is super annoying and should be avoided. Rebasing a conflicting PR or rebasing on top of the same HEAD as before is ok.
cc @kittywhiskers @vijaydasmp @knst
What was done?
How Has This Been Tested?
Breaking Changes
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

I believed that the process for reviewing rebases would be alleviated as the process to diff between two sets of changes (approved and new) was trivial but since that doesn't seem to be the case, this policy makes sense.
One clarification, usually when suggestions are made, I tend to rebase the branch on top of develop (usually to stay ahead of changes that might cause a conflict, I've found that GitHub would report a conflict which didn't require any actual conflict resolution, just a rebase) and then implement/incorporate changes.
Would this policy prevent me from doing a rebase at all unless GitHub reports a conflict (restraining the above usage) or restrains only rebases not accompanied by any changes.

@kittywhiskers Rebasing to solve merge conflicts is ok. Rebasing only to keep up with the target branch is not. So if implementing suggestions/fixes would introduce a conflict when pushed to github, rebasing such PR is ok too.

So I take it that unless the suggestions implemented/incorporated cause a conflict, there shouldn't be a rebase on top of develop?

there shouldn't be a rebase on top of develop?

Since review is requested - yes

Alright, then. Thanks for the clarification. Concept ACK.


Support function & element parameters in native module APIs

A function parameter should be converted to a callbackId before send to native module APIs.
A Element parameter should be converted to a element ref before send to native module APIs.

If Element could be automatically converted to ref, then in this example: https://github.com/Jinjiang/weex/blob/jsfm-feature-vue-examples/examples/vue/components/web.vue
webview.goForward(el.ref) could be webview.goForward(el)
The user should just know Element but no ref

If function could be automatically converted into callbackId, then in this example: https://github.com/Jinjiang/weex/blob/jsfm-feature-vue-examples/examples/vue/modules/modal.vue#L34:L67
The callbacks of the last three modal API calls will work.

v0.1.6 fixed it


fix: ability to cancel profile update

Summary
Fix #389
The vscode.window.showInputBox API will return undefined when user press ESC to cancel. We should really cancel the process when user choose to cancel.
Testing
Test case in #389

It can cancel the profile update as expected.


[RTL] - Add PMP module

Instantiate generic PMP module
Wire up I-side and D-side PMP faults

just curious, since this was something i asked in a separate context.  It
seems like there should be no issues instantiating an ibex_pmp outside ibex
for other purposes.  Is that roughly correct?
On Wed, Aug 21, 2019 at 5:03 AM Alex Bradbury<EMAIL_ADDRESS>wrote:

@asb commented on this pull request.
In rtl/ibex_pmp.sv
https://github.com/lowRISC/ibex/pull/252#discussion_r316145803:

@@ -0,0 +1,125 @@
+// Copyright lowRISC contributors.
+// Copyright 2018 ETH Zurich and University of Bologna.
+// Licensed under the Apache License, Version 2.0, see LICENSE for details.
+// SPDX-License-Identifier: Apache-2.0

+////////////////////////////////////////////////////////////////////////////////
+// Engineer:       Tom Roberts -<EMAIL_ADDRESS>                     //
We're not doing these big doc comments on any new code (and are now able
to remove them for existing code - see #236
https://github.com/lowRISC/ibex/pull/236).
In rtl/ibex_pmp.sv
https://github.com/lowRISC/ibex/pull/252#discussion_r316145926:

@@ -0,0 +1,125 @@
+// Copyright lowRISC contributors.
+// Copyright 2018 ETH Zurich and University of Bologna.

This file doesn't need // Copyright 2018 ETH Zurich and University of
Bologna. as it is newly written.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/ibex/pull/252?email_source=notifications&email_token=AAH2RSRSPPPUF46GZI2PE5TQFUVHJA5CNFSM4IOE6PR2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCCHAUUY#pullrequestreview-277744211,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH2RSQNMVAK625W65UVVU3QFUVHJANCNFSM4IOE6PRQ
.

I have also changed the default number of PMP regions to 2 for now to ease timing


Exclude files

Hi Jake,
Is there a way to exclude files and folders, like .git or .DS_STORE ?
Thanks

Hi Borisco,
No, not currently. This is something I may consider later though.
Best regards,
Jake


Wire up malioc to run on .spv shaders

Right now we only run malioc on shaders that compile to GLES. For the SSBO gradients, and potentially future shaders, we can get analysis by running over the generated spv.

We should potentially run malioc over all .spv shaders, since the gles and spv second stage will be different.

@zanderso I believe this is done now?

Yeah, the analysis will happen if the target GPU supports the GLES or Vulkan version that the impeller_shaders target declares, like here: https://github.com/flutter/engine/blob/main/impeller/entity/BUILD.gn#L91.


Hand-prying unpowered fire/airlocks is faster.

About the PR

This PR buffs prying open unpowered doors and airlocks to reduce the threat level of spaced rooms, as mentioned by jez in previous conversation (in the design discussion channel). Specifically, it takes half as long now.
Why / Balance

Changelog
:cl: Ubaser

tweak: Hand-prying unpowered doors and firelocks is a lot faster now.

Wait why remove the flare? I think there's one more empty tile to add the airlock wrench

Wait why remove the flare? I think there's one more empty tile to add the airlock wrench

there's no more space, and the flare is going to fit inside the airlock wrench

Ah yes, no more rounds start rushing to yoink a crowbar? Yes please
Will this be equal in effectiveness to a crowbar by the way? In door prying that is.

yes

This solves the problem of "are crowbars powergaming?"

no. question solved. This is just a 1x1 crowbar but we put it inside the player inventory. why not just give people a crowbar?

also can you not pry most unpowered doors with your bare hands??

i feel like to that point it'd be better to improve the actual baseline survivability by reducing those pry doafters and having better firelock mechanics rather than just introducing special-case tools that we just give everyone round start.

Yeah, if the item is roundstart available to everyone and 1x1, why not just integrate it into hand-prying by making hand-prying better?
We could have crowbar prying as instant but have an internal cooldown of the current doafter length so you can't pry tiles everywhere like you could 2-3 years ago, pretty sure that's also what SS13 does. While making handprying still use a doafter now with the same duration as crowbar prying doafters.

This was also raised in the Discord design discussion channel.

I also agree that it would be better to make hand prying better than to add a very specialized door prying tool

ready for le review

I feel like this changes balance in the wrong direction.
I don't feel that making prying easier, especially without tools, "reduce the threat level of spaced rooms" because it makes it easier for spacing and other atmos problems to spread. Suddenly instead of one player dying, you have the whole station dying. This actually makes it more dangerous.

Hand prying is pitifully bad right now to the degree of it being almost unusable, besides, atmos woes spreading means more volume to dissolve into and more vents/scrubbers to work with so it's not that bad.

Hand prying is pitifully bad right now to the degree of it being almost unusable

This sounds a bit like hand-prying power-creep to me. Hand-prying exists for a very specific purpose. Before that, you couldn't hand-pry. You're really supposed to go get a crowbar.

atmos woes spreading means more volume to dissolve into and more vents/scrubbers to work with so it's not that bad

While there is "more volume to dissolve into" that doesn't make things better; spreading fires and spacing really does mean that one person trying to save themselves messes it up for a lot of other people.

To follow up with the submitter: the "Why/Balance" section of the PR description exists for a reason. Please fill that in with links to relevant discussions or a summary of discussions that exist, otherwise the only information I have to go off of is what people are writing in the comments.

will explain in a moment

Doesn't really make sense if people can pry open airlock doors with their bare hands really fast. What's the point of a crowbar then? People in spaced rooms should die if it's spaced without a crowbar. People should be open airlock doors if it's just unpowered.

going to close it for the feature freeze


fix(tablecard): increase the available rows in a tablecard

Closes #
Summary

https://github.ibm.com/wiotp/monitoring-dashboard/issues/661 Internal issue, more rows should be available in the tablecard

Change List (commits, features, bugs, etc)

fix(tableReducer): update the pageSize in our reduced state if it changes as a prop
fix(TableCard): show the page selector if the card is expanded
fix(TableCard): allow tables to internally scroll on the card if the card isExpanded. Fix some pagination styles to allow this scrolling without scrolilng the pagination widget
fix(TableCard): increase the default page size choices from 10,20, 30 to 10, 25, 100.

Acceptance Test (how to verify the PR)

tests here

:tada: This PR is included in version 2.24.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ Bofrost.at has degraded performance

In 4104fb4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1318 ms

Resolved: Bofrost.at performance has improved in 93bd5ee.