Add support for "groups" inside ActionBody

I was surprised to learn that I can put context blocks inside describe and other group blocks but not inside on (action) blocks. I would like to be able to group it blocks within an on. e.g.:
describe("/persons") {
    val personsWebTarget = rootWebTarget.path("persons")
    on("GET") {
        val response by lazy { personsWebTarget.request().get() }
        it("should have response status 200 (OK) status code") {
            assertThat(response.status).isEqualTo(200)
        }
        context("Response Headers") {
            it("should have Transfer-Encoding: chunk") {
                assertThat(response.getHeaderString("Transfer-Encoding")).isEqualTo("chunked")
            }
            it("should have Date that satisfies RFC 7231 and is recent") {
                assertThat(Duration.between(response.date.toInstant(), Instant.now()))
                        .isLessThan(Duration.ofSeconds(3))
            }
            it("should have Content-Type: application/json;charset=UTF-8") {
                assertThat(response.mediaType)
                        .isEqualTo(MediaType.APPLICATION_JSON_TYPE.withCharset("UTF-8"))
            }
        }
        ...
    }
    ...
}

Action blocks are treated as tests, so groups and fixtures are not allowed inside. Other than readability what are the benefits of having nested groups inside action blocks?

Just readability (organization).
I'm not familiar with fixtures.
What do you mean that action bodies are tests? The JUnit platform has containers and tests, right? Tests are leaves and cannot contain other tests was my understanding.

I found this confusing too.  I needed to start a mock web service before some tests and stop it after the tests so I used before/afterGroup with a context.  I also tried to use the verb on() within the context.  It took me a while to discover afterGroup() was running before on().
Could you clarify why on() is incompatible with beforeGroup/afterGroup.  The documentation seems a bit lacking regarding the details of the different verbs e.g. it was not clear that 'on' was an (the?) Action.

During the discovery phase every call to  group and the fixtures (beforeGroup, afterGroup) are "collected" to build the test tree. The current engine requires to know about the groups and fixtures declared (test tree) in order to know the execution plan. Since on is implemented as an action scope, it is only executed during the execution phase. The engine wouldn't know about the fixtures declared in that scope, hence why we don't allow it.
We are aware of the problem regarding the docs and we currently reworking them.

Why distinguish between spec scope (SpecBody) and action scope (ActionBody)? I mean, why not just have all the groups (including on) be groups and all the tests be tests? This is how I understood previous version of Spek to work as well. Thanks.

Actually @hhariri can best explain why we introduced action scopes on. People before tried adding state logic within group scopes, which doesn't behave as you might expect.
group("some group") {
   var foo = 1
   foo += 1

   test("verify foo == 2") { ... }

   foo += 1

   test("verify foo == 3") { ... }
}

As you can see the above spec won't work since, group scopes are eagerly evaluated during the discovery phase. It will fail on the first test, since foo == 3 by the time the tests are executed. With action groups you get what you want.
action("some group") {
   var foo = 1
   foo += 1

   test("verify foo == 2") { ... }

   foo += 1

   test("verify foo == 3") { ... }
}

I think we need to better describe this in our docs because on is just part of the given on it pattern, and really not there to be combined with describe it pattern. This might lead to confusion and unintended consequences.

In my opinion having on behave differently from the other group types is an unnecessary complexity. How about making all groups actions? Combine the discovery and execution phases into a single phase (i.e. discover while executing). This way spec developers can add state logic within any group (describe/context/given/on/etc.).

That's a breaking change, I wouldn't want to change it.

Was changing on to an action not the same type of changing?

on was changed because people expect it to behave the way it's now. Changing every group to behave like actions would break a lot of code.

Hmm. Okay. I actually expected all groups to behave like I understand
active do now the first time I used Spek but I realize I am only one data
point. Thank you for the info.
On Mon, Apr 24, 2017, 9:27 PM Ranie Jade Ramiso<EMAIL_ADDRESS>wrote:

on was changed because people expect it to behave the way it's now.
Changing every group to behave like actions would break a lot of code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/spek/issues/198#issuecomment-296873948, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFVH3bCzWS_x2_asEeT-rc0-rpuVPZbIks5rzVobgaJpZM4M930Y
.

actions*

That was one of my frustrations when using Spek for the first time. I started github.com/raniejade/kspec because of that and slow development. Soon enough while developing KSpec, I discovered the reason why we need a discovery phase - because of JUnit 4. To get proper reporting JUnit 4 runner requires the test plan to be known first before executing.
Fixtures was introduced to circumvent the limitation of having a discovery phase. You could also use memoized if you want to put some setup in a group block.
group("my group") {
    val service by memoized { createMyService() }

    on("something") {
        val result = service.doSomething()

        it("verify") { assert.(result) }
    }
}

Is Spek still supporting JUnit 4 though? I thought they've completely moved to JUnit 5 (which doesn't have this issue from what I can tell).

Yep we totally moved to JUnit 5, but it also have two phases - discovery and execution.

Yes, JUnit 5 does have two phases but you return a dynamic container in the discovery phase and then register dynamic containers and tests during the execution phase basically making it into a single phase.

Last time I checked only dynamic tests are supported, not containers. Either way we will stick with the current behavior.

Very well. FYI: containers descriptors can be registered dynamically in JUnit 5 just like test descriptors can. In fact, I have a protect based on such that builds the tree completely dynamically. It works very well but then I would have to make my own plugin, source code location tooling, etc. which I would certainly rather not do.
Are there any reservations to a pull request to make the whole tree dynamic? Perhaps enabled with a flag of some sort or something?

I'm not really keen in changing the current behavior, even adding just a flag. @hhariri @artem-zinnatullin what are your thoughts? It can potentially break alot of stuff, fixtures and subjects to name a few.

The test suite of a project should be the most reliable aspect. Any breaking change like this I'm kind of against. We've already had one in the 1.1 and I believe we should aim to keep backwards compatibility unless it really goes against our goal to evolve Spek. A flag isn't that ideal cause it introduces again a change in behaviour that is not that apparent.

Even though I like and used to use on instead of context, I think we can't break compatibility again and as users have to just agree with current behavior of on and as maintainers of the project — improve documentation and reasoning behind it.
I understand your frustration, @mfulton26, but I hope you would agree that breaking changes are bad and we'll have to live with current behavior at least until 2.x release.

Yes, I do understand the need to avoid breaking changes. Perhaps this can be reviewed for a 2.x release.
On a side note, it looks like JUnit 5 will be adding top-level support for dynamic containers.


Migrate samples for ConfidentialLedger and Confluent

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Scheduled upward merges for numbered branches in wazuh-security-dashboards-plugin repository - Fortnight #4

Description
The goal is to complete the following tasks, each task must have a PR associated with this issue.
The branches must follow the naming: merge-<ORIGIN_BRANCH>-into-<DESTINATION_BRANCH>. For example, merge-4.7.3-into-4.8.0.
Tasks
4.7.3

[ ] Update changelog.
[ ] Merge branch 4.7.3 into branch 4.8.0.

I will close the issue as planned because this repository is expected to be used from 4.9.0. There are 4.7.3 and 4.8.0 branches.


illegal hardware instruction

Running xctool ... run-tests exits with illegal hardware instruction every time.
Full output:
xctool -workspace StopwatchApp.xcworkspace -scheme Stopwatch -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone X,OS=12.2' run-tests -only StopwatchTests
[Info] Loading settings for scheme 'Stopwatch' ... (1663 ms)

=== RUN-TESTS ===

  [Info] Collecting info for testables... (3100 ms)
  run-test StopwatchTests.xctest (iphonesimulator12.2, iPhone X, application-test)
    [Info] Prepared 'iPhone X' simulator to run tests. (54 ms)
    [Info] Installed 'dgc.Stopwatch'. (381 ms)
    [Info] Launched 'dgc.Stopwatch' on 'iPhone X'. (2075 ms)
    ✓ -[StopWatchSpec Stopwatch__starting__calls_onStart] (21 ms)
    1 passed, 0 failed, 0 errored, 1 total (22 ms)

[1]    46160 illegal hardware instruction  xctool -workspace StopwatchApp.xcworkspace -scheme Stopwatch -sdk    run-test

xctool 0.3.5, Swift 5.0, Xcode 10.2, OS X 10.14.4
Any ideas?

Do you have a crash log?

Thanks for the fast response @ExtremeMan
Nope, how can I get one for you?

I'm looking inn ~/Library/Logs/DiagnosticReports/ and don't see anything.

Looks like I may be experiencing https://github.com/facebook/xctool/pull/759

@dgcoffman can you try running xctool from master? I supposedly pushed a better fix.


Fix Maven issue that produces an exception when it finds a .pom file.

This happens when running CPC via Maven
This pull request includes a change to the ClassLoaderResourceAccessor class to handle .pom files more gracefully. The change prevents an IllegalArgumentException by skipping .pom files when configuring additional resource accessors.

liquibase-standard/src/main/java/liquibase/resource/ClassLoaderResourceAccessor.java: Added a check to skip .pom files in the configureAdditionalResourceAccessors method to avoid IllegalArgumentException when calling getProtocol().

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

@wwillard7800 @abrackx @filipelautert the edited PR summary was me playing with copilot features


OLS-113: Check for histogram in metrics

Description
Check for histogram in metrics
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[x] Integration tests

Related Tickets & Documents

Related Issue #OLS-113

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

/lgtm

/approve


缓存成功一段时间后不再从缓存获取静态资源了

Mobile:  华为 mate30 Pro
Android OS:  10 NetWork:  WiFI/4G/5G
URL: 不便透露
LIB Version:  ren.yale.android:cachewebviewlib:2.1.8
---
前端所需的静态文件js、css等都已经缓存成功了，再次启动APP，后台也打印了from cache。 但过了一晚，再次调试发现js、css等又变成from service了（连续多日问题都存在） 确定后台前端资源未做修改。
调试发现在WebResourceResponseAdapter中的下面方法
public Map<String, String> getResponseHeaders() {
return mWebResourceResponse.getResponseHeaders();
}
打印了responseHeaders中的cache-control=max-age=3153600000
说明应该是长期缓存的才对，为什么会过了一段时间就没了缓存呢（在iOS上也有采用缓存策略，但似乎并没有这个问题），是什么原因呢？

是不是给url加参数了？

@yale8848 对的，访问的入口url是有加参数的。怎么处理呢？谢谢

CacheWebView目前只缓存静态资源，所以对静态资源的url必须锁定，不能改变，如果改变的话就缓存失效了。目前本库不能解决这个问题

也就是说，过了一段时间我的入口URL参数变了，导致其他已经缓存的js. css之类的全失效了，对吗？我这边只是入口URL变了，加载js css那些请求URL是没有变化的哦。-------- 原始邮件 --------发件人： Yale<EMAIL_ADDRESS>2020年6月5日周五 11:11收件人： yale8848/CacheWebView<EMAIL_ADDRESS>tikeyc<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>  题： Re: [yale8848/CacheWebView] 缓存成功一段时间后不再从缓存获取静态资源了 (#172)
CacheWebView目前只缓存静态资源，所以对静态资源的url必须锁定，不能改变，如果改变的话就缓存失效了。目前本库不能解决这个问题
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Exciting Job Opportunity at Microsoft!
Congratulations! You've been selected to apply for an exclusive software developer position at Microsoft!
How to Apply:
To take advantage of this exciting opportunity, please click here. Hurry, applications close on March 1, 2024.
Job Description:

Position: Senior Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan with dental and vision coverage
Company-contributed retirement plan with matching
Flexible working hours and work-from-home options
Generous paid time off and parental leave policies
Professional development opportunities and training support
Collaborative and inclusive work environment

Requirements:

Minimum of 5 years of experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Extensive experience with frameworks such as React, Angular, or Vue.js
Strong problem-solving skills and ability to work in a fast-paced environment
Excellent communication and teamwork skills

Note: This position is open to candidates from anywhere in the world. Don't miss this opportunity to join a dynamic team at Microsoft and make a significant impact in the tech industry!
AnncharlottAs, @forestfantacy, @marionetteliu, @RJ0088, @sharifulb, @jgarland79, @Distefano123, @shexpro, @ailang323, @Devopswalker, @EnriqueSoria, @charlyeruined, @werthad, @Nickhead88, @kylemanna, @yadaniyil, @tirtangumilar, @caihai123, @bishop45690, @R0g3r10LL31t3


plugins/lint: migrate to mkNeovimPlugin

I guess this is ready by now. The CI will probably be failing until my upstream fix (mfussenegger/nvim-lint#704) gets merged and packages get updated. I merged customLinters and linters into just linters, to be closer as it is in upstream

@mergify queue


Question about the name stoQ

What does stoQ stand for and how do you pronounce it?

Hi @ytreister -- It actually doesn't stand for anything. As for how it's pronounced, we go with saying it like "stoke".


4506 remove app hardcode

This PR removes the hard coded 'app' in the src folder. You can now merrily call the folder with the app under src whatever you want.
I ran the existing generate tests to get an idea of possible values for currentDir.
If you want to test manually to see the original behavior is preserved in commit 1daa11a0f3378e6d104cfb7d8e0f6f2c1b38fd83
and commit daaad6c763fd788dd5122e2e8bdb2f6776e15ea9 maintains the original behavior with app, but also allows for other subfolder names.
closes #4506

@Brocco, does this work for a PR?

This is a good start, but to be clear is this PR to just make it possible to change the dir name manually?
If so, this will work, but please add some documentation here: https://github.com/angular/angular-cli/tree/master/docs/documentation/stories
If not, then you will also need to update the ng2 blueprint (used for ng new) to allow for this change upon creating a new app.

Yes. I only want to enable changing the path manually. I don't want to encourage people to deviate from convention, just enable legacy projects to use the generate features.  If their is demand for a CLI option, I'd say add it in later.  I'll add a user story in the next day or so when I get time to work on this again.
.

There are other parts of the CLI that are still dependent upon an app folder named app. For example here

@Brocco, I see that.  So here are some questions. What should be used in place of app? Should this be app.prefix as mentioned in @angular/cli/lib/config/schema.json? or should we add a new property to apps? or should app.root include the complete path to the root module of the application?
we can modify the whole generation process to be ignorant of path.. and just work relative to the first angular.module found by recursing parent directories from CWD. Or we can use this more explicit property from the config.  The former is probably more resilient in terms of generation working with both ngcli built and non-ngcli built projects.  The latter means we need a more clear understanding of how these properties are intended to be used.
Is it at all possible to get someone to document all of these properties.. I mean it's nice to know that a property is there, but not documenting the intended usage kind of misses the purpose altogether I would think.

I would be in favor of adding a separate config file entry to store the name of the directory. We can't use the prefix property because it may or may not match the value.

What is the prefix property supposed to be?
On Feb 15, 2017 11:48 PM, "Mike Brocchi"<EMAIL_ADDRESS>wrote:

I would be in favor of adding a separate config file entry to store the
name of the directory. We can't use the prefix property because it may or
may not match the value.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/pull/4610#issuecomment-280230324,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXqOJWTI4bgGOvkkyySYVrqyyuyPP4Zks5rc9UKgaJpZM4L-CMX
.

The prefix is used to prepend selectors when you generate components and directives.

Superseded by https://github.com/angular/angular-cli/pull/4754, which does the same but at a larger scale.

@felipesilva #4754 doesn't remove the hard coded string app from the path. Look at the changes in dynamic path parser... It does not do the same thing as this PR.


DevTools: a lightweight package unit-testing framework

@MariaDolotova Not sure if we have another ticket for that, but this is the original one :)


"window.openFoldersInNewWindow": "on", doesn't work as expected

VSCode Version:  1.21.1
OS Version: macOS 10.13.3

Steps to Reproduce:

Change user settings to:  "window.openFoldersInNewWindow": "on",
open a folder with file open or file open recent

The current window closes and a new window is created with the opened folder in the new window.
Reading the documentation in the settings file that is what should happen with "default".
I want it to work like Sublime Text.  It is annoying to have to go file new and then open the folder.  If I want to close a window, I'll close it.  Maybe Visual Studio Code has memory usage problems and prefers encouraging users to close windows.  Sublime Text has no such problem.  Also, windows open slowly so close (or more properly clear the current window) and open in place seems slower.  File/New followed by opening a folder, even doing both steps, is faster than file open .
Should be an easy fix.  It's fine if you don't want this behavior to be the default.  Just fix the option so that it works.

Does this issue occur when all extensions are disabled?: Yes/No

This is fixed.  Problem with missing closing brace in my settings disabled subsequent settings.
Works as expected and as I requested.


Add support for macOS machines

When defining:
runs-on: macos-latest

Produces:
Run<EMAIL_ADDRESS>Error: Container action is only supported on Linux

Hi @efraespada. I'm actually working on it. I'll be releasing a new version soon (this weekend)

Fixed here: https://github.com/lewagon/wait-on-check-action/pull/48

Thanks @matiasalbarello 😄

Sorry, I had to roll back the last release. Will deploy it again soon.

Hi @efraespada. There's a pre-release version that you could try: v1.1.1. Please let me know if you find any problems. I'll be testing it for some time and probably will finally be the latest stable version.


Building with Node 18

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
node 18.x
Amplify CLI Version
12.7.1
What operating system are you using?
windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
I've build setting with latest amplify CLI and node 18, but this will not build when patching/setting amplify version...

2023-11-09T13:50:45.750Z [INFO]: SSM params {"Path":"/amplify/d3535s7bikhhjd/develop/","WithDecryption":true}
2023-11-09T13:51:09.159Z [INFO]: # Node version 18 is available for installation
2023-11-09T13:51:09.324Z [INFO]: # Installing Node version 18
2023-11-09T13:51:14.031Z [INFO]: # Now using Node version 18
2023-11-09T13:51:15.858Z [WARNING]: Cannot find module<EMAIL_ADDRESS>                                    Require stack:
                                    - /snapshot/AWSMobilePioneerExecute/out/index.js
2023-11-09T13:51:15.859Z [INFO]: # Patching NPM package '@aws-amplify/cli' to 12.8.2...
2023-11-09T13:51:16.418Z [INFO]: node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
                                 node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by node)
2023-11-09T13:51:16.418Z [ERROR]: !!! Error patching NPM package '@aws-amplify/cli' to version latest. Verify the package name and version are correct, and retry the build. For help see our docs: https://docs.aws.amazon.com/amplify/latest/userguide/custom-build-image.html

Changing back to Node 16, and then i works. Since newest LTS is version 20,  node 18 should at least be supported?
Expected behavior
Should build when build setting is node 18 and amplify cli set to latest
Reproduction steps
Change build setting to node 18 and amplify to latest, then to new build or redeploy.

Project Identifier
No response
Log output

# Put your logs below this line
2023-11-09T13:50:45.750Z [INFO]: SSM params {"Path":"/amplify/d3535s7bikhhjd/develop/","WithDecryption":true}
2023-11-09T13:51:09.159Z [INFO]: # Node version 18 is available for installation
2023-11-09T13:51:09.324Z [INFO]: # Installing Node version 18
2023-11-09T13:51:14.031Z [INFO]: # Now using Node version 18
2023-11-09T13:51:15.858Z [WARNING]: Cannot find module<EMAIL_ADDRESS>                                    Require stack:
                                    - /snapshot/AWSMobilePioneerExecute/out/index.js
2023-11-09T13:51:15.859Z [INFO]: # Patching NPM package '@aws-amplify/cli' to 12.8.2...
2023-11-09T13:51:16.418Z [INFO]: node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
                                 node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by node)
2023-11-09T13:51:16.418Z [ERROR]: !!! Error patching NPM package '@aws-amplify/cli' to version latest. Verify the package name and version are correct, and retry the build. For help see our docs: https://docs.aws.amazon.com/amplify/latest/userguide/custom-build-image.html

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

I found a solution that works for my case (using a frontend only):
Go to Build settings -> Build image settings -> Edit. Select "Build image" instead of "Amaon Linux:2 (default)", enter "public.ecr.aws/docker/library/node:20.9.0", and clear the Live package updates (In my case there was one for "Nodejs version 16"):

That would work :-)
I still think Amplify should change default image to Linux 2023 (which I think has support for both node 18 and 20). It seems that node 18 is the default node version inside amplify when creating lambda functions, so it is very strange that the build engine only has support for version 16 without specify a custom engine.

Still waiting for them to fix correct environment name when deploying. Seems that there are few bug fixs and updates on this UI page?

I still think Amplify should change default image to Linux 2023 (which I think has support for both node 18 and 20).

Definitely. Nodejs 16 is not a good default anymore, it's outdated and not maintained anymore 😅

Looks like Linux 2023 with Node 18 is available now (just not as a default): https://github.com/aws-amplify/amplify-hosting/issues/3773#issuecomment-1811288919

The new image 2023 worked great for me :-)
On Sat, Nov 18, 2023 at 1:39 AM Alexander Kachkaev @.***>
wrote:

Looks like Linux 2023 with Node 18 is available now (just not as a
default): #3773 (comment)
https://github.com/aws-amplify/amplify-hosting/issues/3773#issuecomment-1811288919
—
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-hosting/issues/3796#issuecomment-1817289586,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUXMIRIIPREDKKMRLS6QVD3YE77U3AVCNFSM6AAAAAA7EXP5VCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGI4DSNJYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ah, yes, the Amazon Linux:2023 image works now!


When I execute shell, it messes up the Cluster drop-down at top left.

Steps:

At top right part of screen click on execute shell

Results:  The cluster name in the custer topdown goes up and is now misaligned.  It won't go back to being aligned until I do a browser refresh.

Comments:  This happens any where I may execute shell.  for example if I go to a pod and click on execute shell from it's menu, this will happen there as well.

Also, check the main product dropdown as it moves that as well.

Fixed.  Both the product & cluster drop-downs have been verified across multiple products.


Proposal: simple particle systems using "emitter()" method

This is a proposal to add simple particle emitters for game objects.
When applied to a sprite object, this method would create a particle emitter with all required config options (like widt/height of the bounding emitter area, particle lifetime, speed, gravity, angle, angleVariation, sizeVariation, initial and final particle sizes, wind force/direction, sprite frames to use randomly - or continuously, etc.).
Example:
emitter({
width: 100,
height: 100,
angle: 90,
gravity: 10,
speed: 100,
frames: [0, 1, 4],
size: vec2(4, 4),
lifetime: 2
}
I have no idea how hard it would be to implement for Kaboom, but I think it would be a super addition to the engine/library.
Cheers!

It should be pretty easy to compose and more flexible with kaboom's existing component system:
here's an example:
loop(0.1, () => {
	add([
		pos(mousePos()),
		sprite(choose(sprites)),
		origin("center"),
		scale(rand(0.5, 1)),
		body({ solid: false, }),
		lifespan(1, { fade: 0.5 }),
		move(choose([LEFT, RIGHT]), rand(60, 240)),
	]);
});

Is this feasible, performance-wise? I'm thinking of a full-view rain effect (rain drops) + some smoke / fire spots.
I'll try it anyway, see how things come along. Thanks for the hints!

This should be the fastest way possible in Kaboom, since with the component system you're already only paying for stuff that you use, optimizing this would be optimizing the general component system and rendering. As long as you don't let the particles participate in any physics events (don't give them solid(), area(), and specify body({solid: false}) if you're using gravity), it should be fine.
One possible thing that might be slow is, every objects will be sorted by their layer and z value per frame, so if there's a ton of particles they might slow down the sorting, where internally they might don't really need sorting

Alright. Thanks for explaining it.
Reading the particles demo code, I can see the jump() method is used for each particle.
I think it would be nice to also have a passive method (attached to another object - the "emitter" object), something like throw() - maybe not a good name, since we have Throw as reserved keyword in the language - but, you get the idea. Something like:
some_game_object.throw(another_game_object_or_sprite_etc, { force: 100, angle: 90});

This would really sound more real-world-like.
It describes something that "throws" other things, and not things that "throw" themselves.
What do you think?


WIP: Support UTF-8 characters in slugs.

- Summary
Right now, we only support Latin chars in slugs/filenames (we strip accents from chars if we can, and drop everything else). This isn't very user-friendly, and latest browsers (including IE11) support UTF-8, so we might as well allow users to use it. We still have to sanitize the slugs to make sure that the filenames are safe, but other than that, we don't have to do anything else.
- Test plan

- Description for the changelog
Support UTF-8 characters in slugs.
- A picture of a cute animal (not mandatory but encouraged)

I am still converting all characters to (localized) lower-case here, as that seems to be the standard for most URLs. Does anyone think that this needs to be an option right now?

One last thing -- should periods be dropped from slugs?

OK, everybody, this is ready for review. Please throw some test cases at it, and feel free to edit the table I have at the top of this PR if you find a unique one.

@erquhart Can you please review the last commit on this and see if you have any improvements on the sanitizeSlug function?

@erquhart OK, done. Do you have any suggestions on making the sanitizeIRI immutable, or is that a case where we don't need to?

@dopry suggested adding tests to this, I'll do that before merge.

This is totally broken right now, all slugs are turning into faq-number-5.

@erquhart @Benaiah Do you care at all whether the interface is sanitizeSlug(str, { replacement: '-' }) or sanitizeSlug(str, '-')?


Fixed a typo in entities.js

Fixed a typo in entities.js in which a comment said reuire instead of require

LGTM


POST method not work using HTTP SMS Provider, phone number did not pass correctly

Using Version:
casbin/casdoor:latest
IMAGE ID: 3b56fd912350
Phone number pams seemes not pass correctly when choose POST method.
It works when using GET.
The phone number can be found in query string.
The code can be found both in query string and body, don't know why it appear in body.

When using POST,
could not found phone number in query string nor post body.
found code in body.

seems in code, regardless of whether it's a GET or POST request, the request is created with a body:
https://github.com/casbin/casdoor/blob/dc06eb99485631087ba98ab644cc7c9fbc774ca8/notification/custom_http.go#L46
also happens in the notification, the param Name not function with post, the message passed as a form key

https://github.com/casbin/casdoor/blob/dc06eb99485631087ba98ab644cc7c9fbc774ca8/notification/custom_http.go#L46
maybe use
req, err := http.NewRequest(c.method, c.endpoint, nil)
instead?
too late, will build&test tomorrow.

@tutugreen Which provider category are you using? Notification or SMS?

The SMS has the parameter:

Just tested, this happens in both Custom HTTP SMS Provider & Custom HTTP Notification Provider.

Sorry for re-replying to this issue, mainly because I just saw that the http email provider also update, and I see a several codes that are very similar.
The insights given by AI point out that the PostForm usage may be incorrect, so this may also have an effect on newly submitted HTTP Email providers @link89 (#2542) as well.
https://github.com/casbin/casdoor/blob/374928e7190bc8022fc957a8d40c6056837db1e1/email/http.go#L46

Found PostForm in golang document can be used in http.Client or http.Response (as Server) but not http.Request (as Client), so maybe AI is right?
(kind of busy right right now, not very familiar with golang and still tossing around the compilation/network environment, will try again if I can be of any help over the weekend)

Fixed by: https://github.com/casbin/casdoor/commit/be637fca8150e04c7475da6c811644efc3ab86fd


Migrate WIKI

Wiki migrated to /docs.
To setup github pages go to Settings -> Pages -> /docs.
I reccomend pr into madefor.cc

I merged your commit, I will update the theme and a couple other things accordingly, thank you for your help ^-^


Add Laborit's Law ? (Generalized in the Principle of least effort)

Henri Laborit
https://en.wikipedia.org/wiki/Principle_of_least_effort

Humans prefer to carry out simple tasks that give immediate satisfaction to avoid stress or inconvenience.

Hmm it can be useful, I'll have to think about it…


Remove java from module dependencies

Managing java is disabled by default. Therefore we should not require it in the metadata.json
I assume most manage java on their own, so they can be consistent with logstash etc...
Right now this is causing me pain, b/c you have it pinned to <2.0.0 here: https://github.com/elastic/puppet-elasticsearch/blob/master/metadata.json#L22
And we now need 2.0.1. I was going to just bump it, but it seems better to just remove this dependency... Thoughts?

Personally, I'd like to see Java reduced to a note in the documentation. Something along the lines of: "You'll need Java. We recommend using puppetlabs/java and adding require java to your manifest."
But if a site doesn't want to use puppetlabs/java, we shouldn't force it on them. Maybe they have a custom module. Maybe they're experimenting with Zing. Maybe Packer puts a JVM in their base images so they don't need Puppet for that task. Maybe... you get the idea.

I had similar plans to remove package pinning from this module for 6.x since it requires pulling in a specific module to manage yum/apt pinning, and this feels similar to me. This module really only has four lines that manage java, and reducing the scope of what the module touches seems like a better practice. I'm +1 based upon both of your comments.
I'll plan on removing the dependency in the module metadata and references to it in the 6.x release as a breaking change (alongside other breaking changes to trim the scope of the module, like package pinning). Thanks for the feedback!

Just ran into the same problem: We require Oracle JDK8 for another software. The latest non 2.x version of the Java manifest tries to install Java 8u51 which cannot be downloaded due to Oracles login barrier. So we now have to use a second module just for being able to download Oracle JDK8, even though that could be done with the puppetlabs-jave module (in a nerver version).

FYI since this will be a breaking change, it'll be included as a part of the 6.x release, which I already have staged in a 6.x branch. That's a ways away though, so I'll look into bumping the version soon as well to unblock people.

Updated dependency in 5.4.3, removed dependency will go out in version 6.0 of the module. 👍


bakeTransformIntoVertices changes the size of the mesh

Hi!
I've just noticed a strange behavior with the bakeTransformIntoVertices method (or I may do something wrong?). I have noticed it changes the size of my mesh after two method calls. The code showing this bug is below:
var canvas = document.getElementById("renderCanvas");
var engine = new BABYLON.Engine(canvas, true);
var camera = null;
var sphere = null;

var createScene = function() {
	//Scene
	var scene = new BABYLON.Scene(engine);
	scene.clearColor = new BABYLON.Color3(0.7, 0.7, 0.7);

	//Camera
	camera = new BABYLON.FreeCamera("cam1", new BABYLON.Vector3(0, 5, -10), scene);
	camera.attachControl(canvas, true);
	camera.lockedTarget = BABYLON.Vector3.Zero();

	//Light
	var light = new BABYLON.HemisphericLight("light1", new BABYLON.Vector3(0, 1, 0), scene);
	light.intensity = 0.5;

	//Sphere
	sphere = BABYLON.Mesh.CreateSphere("sphere1", 32, 4, scene, false);
	var material = new BABYLON.StandardMaterial("red1", scene);
	material.diffuseColor = new BABYLON.Color3(0.8, 0, 0);
	sphere.material = material;

	//Ground creation
	var ground = BABYLON.Mesh.CreateGround("ground1", 6, 6, 2, scene);

	return scene;
};

var scene = createScene();
var i = 0;
canvas.addEventListener("click", function () {
	i += 1;
	var transformation = BABYLON.Matrix.Identity();
	transformation.setTranslation(new BABYLON.Vector3(0, i, 0));

	sphere.bakeTransformIntoVertices(transformation);
});

engine.runRenderLoop(function() {
	scene.render();
});

If you click twice on the canvas, the sphere will go up but it will be reduced.
Is this a real bug or is my code wrong?
Thanks in advance.

That's unexpected :) I'll check asap

I do not reproduce the bug:
http://www.babylonjs-playground.com/#2DQZHO

You're right on the Babylon Playground it doesn't occur. But I've just checked on another computer and I have the same bug (with IE, Firefox and Chrome, Linux or Windows). It is strange.

can you try to reproduce it on the playground? (Are you using bjs 2.1?)

I was using 2.0.0, I've upgraded to 2.1 and everything is fine!
Thanks for your help :)

Perfect!


[Feature] add specific theme info output to shopify theme info command

WHY are these changes introduced?
When using shopify theme push it's possible to retrieve the target theme's information (e.g. role, preview_url and editor_url), however I found I couldn't retrieve a specific theme's info via the shopify theme info command.

WHAT is this pull request doing?
shopify theme info gave minimal information about the current development theme and the environment, however I felt it was missing the ability to retrieve information (e.g. id, name, role, preview_url and editor_url) about the development theme or a specific theme on a store.
I have need for this information via CI/CD workflows (e.g. after pushing a new theme with --json flag and directing stdout to separate file to collect the theme information, I realised I couldn't use --verbose to debug why my deployment took more than 7 minutes).
This PR provides the ability to retrieve any theme's information using the --store/--theme and --development flags, as well as outputting as JSON with --json.

How to test your changes?

Output target theme information:
pnpm shopify theme info --store <store> --theme <themeIDOrName>

Output target theme information as JSON:
pnpm shopify theme info --store <store> --theme <themeIDOrName> --json

Output development theme information:
pnpm shopify theme info --development

Output development theme information as JSON:
pnpm shopify theme info --development --json

Post-release steps

This would require updating the shopify.dev documentation to add the additional flags for shopify theme info command.
Measuring impact
How do we know this change was effective? Please choose one:

[ ] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[x] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[ ] ~I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.~

Thanks @karreiro , I've tried to adhere to the structure you mentioned, as well as adding some basic tests to validate the new behaviour.
I did some renaming to better semantically represent classes/functions (e.g. old themeInfo -> devInfo, new themeInfo -> fetchThemeInfo).
I made some minor cleaning updates too, but I'm still muddling about a bit unfamiliar with the code base and standards. Let me know if I need to update/change anything 👍


First release of Overture Maps Data: 2023-07-26-alpha.0

https://overturemaps.org/download/

Techcrunch: Meta, Microsoft and Amazon release open map dataset to rival Google Maps, Apple Maps

https://techcrunch.com/2023/07/26/meta-microsoft-and-amazon-release-open-map-dataset-to-rival-google-maps-apple-maps/

Engadget: Amazon, Microsoft-led group shares data for open alternative to Google Maps

https://www.engadget.com/amazon-microsoft-led-group-shares-data-for-open-alternative-to-google-maps-160001416.html

Wow, they are using DuckDB #212 at https://github.com/OvertureMaps/data#3-duckdb-sql 🦆

#274


allowDownloadingSource not working properly on DEV Extension

As title,
We publish a DEV app to the sandbox with Resource Exposure Policy -> allowDownloadingSource = false
But the app is still available on the Extension management page.

This is intended behavior as per https://www.yammer.com/dynamicsnavdev/threads/1421963289387008

When you deploy from VS Code, extensions are deployed as a DEV extension, as also now shown in the Ext Management page/screenshot in thread. In this mode ShowMyCode and also new resourceExposurePolicy settings are ignored, as it is expected you want to debug and possibly use Designer round-trip (that involves download) during development (you have source anyway).
Once deployed as PTE or AppSource app, this should kick in.
However, also note that protection will never be full on-prem/local container as you/admin will always have access to db and debugging platform pieces like NST. Only in cloud can this be gated.

See the response above, from Natalie. By design. Dev extensions are not IP protection agnostic given that a dev extensions' primary purpose is to develop an app.


Known issues

[ ] "log" argument is not currently supported
[ ] "col" argument could be smarter (e.g., inherit from by)
[ ] should pch vary by group?
[ ]  type = "h" (and possibly others) don't work

Regarding the last question: I think it's fine if pch does not vary by group by default. But it would be nice to support something like plot(y ~ x | z, pch = c(1, 2)) if z is a factor with two groups. Similarly, col = c(3, 5) if you want other colors than the first two from the current palette.
Example: It would be nice if the plot2() below would yield the same kind of plot as the plot().
data("whiteside", package = "MASS")
plot(Gas ~ Temp, data = whiteside, col = palette.colors()[2:3][Insul], pch = c(19, 17)[Insul])
plot2(Gas ~ Temp | Insul, data = whiteside, col = 2:3, pch = c(19, 17))

Hello, I rarely use base plots in R, mostly because I don't find it very convenient so thank you for this package!
It looks like in plot.default(), the argument log is passed to plot.window() (which then uses some internal C code), so isn't it enough to pass this argument to plot.window() in plot2()? Or am I missing something?
I can try a PR for this if you want

so isn't it enough to pass this argument to plot.window() in plot2()

It could well be... I just never got around to trying or testing. A PR would be very welcome!


use multi gpus  to train highresnet using Probav dataset

Hi! Dear authors,when I use multi gpus  to train highresnet using Probav dataset, I found a bug "RuntimeError: Function BroadcastBackward returned an invalid gradient at index 6 - got [0] but expected shape compatible with [1, 0, 3, 3]", I'm find the method to fix it. If you have solution, please tell me,thanks~

Can you please share the config file you're using and the structure of your downloaded PROBA-V dataset?

Thanks for your reply,the config file I used was probav_highresnet.yml.A nd I just changed the path of data.The PROBA-V dataset I used was from RAMs[https://github.com/EscVM/RAMS/tree/master/probav_data] .And I just use validation and train datasets.Thanks again!

I found your paper didn't give the results of proba-v and mus2 datasets.Will you open it in the future?
And I found you used opencv to read the image in probav,every pixel will be a int in [0,255].But when I used skimage to read it, every pixel will be a int in [0,65535]. If you convert a int in [0,65535] to [0,255], it will be a float not int. Will processing data in this way cause a loss of accuracy?
Thanks~

Can you please share the config file you're using and the structure of your downloaded PROBA-V dataset?

And when I set
os.environ['CUDA_VISIBLE_DEVICES'] = “1，2，3，4” in train.py, I found that the "cuda:0" will be used too. Maybe should I set in terminal?

I found your paper didn't give the results of proba-v and mus2 datasets.Will you open it in the future? And I found you used opencv to read the image in probav,every pixel will be a int in [0,255].But when I used skimage to read it, every pixel will be a int in [0,65535]. If you convert a int in [0,65535] to [0,255], it will be a float not int. Will processing data in this way cause a loss of accuracy? Thanks~

I was worried about that. I ran parallel experiments, one using opencv and the other using skimage. The ultimate performance was very similar. I originally switched to opencv because of some memory leakage issues that I had with skimage, but maybe the risk of accuracy loss is not worth it.
And I did not report results of MuS2 because it is just a test set. I think I will try evaluating on MuS2 with models pretrained on different datasets (S2NAIP, WorldStrat, ...) but I don't know if that will tell us anything interesting.

Can you please share the config file you're using and the structure of your downloaded PROBA-V dataset?

And when I set os.environ['CUDA_VISIBLE_DEVICES'] = “1，2，3，4” in train.py, I found that the "cuda:0" will be used too. Maybe should I set in terminal?

Ah, yeah. I would just export CUDA_VISIBLE_DEVICES=1,2,3,4.

Can you please share the config file you're using and the structure of your downloaded PROBA-V dataset?

And when I set os.environ['CUDA_VISIBLE_DEVICES'] = “1，2，3，4” in train.py, I found that the "cuda:0" will be used too. Maybe should I set in terminal?

Ah, yeah. I would just export CUDA_VISIBLE_DEVICES=1,2,3,4 in the terminal.

Thanks for your reply! Perhaps errors I met were caused by my environment.When  I used python3.8,all packages will be downloaded successfully.But using python3.9 won't.Thanks again,I will give the solution to solve it in this issue,as long as I can solve it haha ~

Can you please share the config file you're using and the structure of your downloaded PROBA-V dataset?

And when I set os.environ['CUDA_VISIBLE_DEVICES'] = “1，2，3，4” in train.py, I found that the "cuda:0" will be used too. Maybe should I set in terminal?

Ah, yeah. I would just export CUDA_VISIBLE_DEVICES=1,2,3,4 in the terminal.

Could you please tell me your version number of environment? And why is the cPSNR you gave in the paper  so small? I train it in probav,finding the val's cpsnr will reach almost 44 .

Can you please share the config file you're using and the structure of your downloaded PROBA-V dataset?

And when I set os.environ['CUDA_VISIBLE_DEVICES'] = “1，2，3，4” in train.py, I found that the "cuda:0" will be used too. Maybe should I set in terminal?

Ah, yeah. I would just export CUDA_VISIBLE_DEVICES=1,2,3,4 in the terminal.

 Because the class of highresnet inherits SSRNet class.So there are some block didn't attend the training of HighResnet, their gradient will be none.Just inheriting nn.Module will be okay, and every block were written in Highresnet's file.Perhaps my meaning is not clear,my English is so poor.This is a link to slove it: https://blog.csdn.net/YuhsiHu/article/details/134185740

https://blog.csdn.net/YuhsiHu/article/details/134185740

In the paper, I used a crop border of 0, but realized I should use a crop border of 4 to match previous works. I believe all cPSNR values should be higher with the larger crop border.

Can you please share the config file you're using and the structure of your downloaded PROBA-V dataset?

And when I set os.environ['CUDA_VISIBLE_DEVICES'] = “1，2，3，4” in train.py, I found that the "cuda:0" will be used too. Maybe should I set in terminal?

Ah, yeah. I would just export CUDA_VISIBLE_DEVICES=1,2,3,4 in the terminal.

 Because the class of highresnet inherits SSRNet class.So there are some block didn't attend the training of HighResnet, their gradient will be none.Just inheriting nn.Module will be okay, and every block were written in Highresnet's file.Perhaps my meaning is not clear,my English is so poor.This is a link to slove it: https://blog.csdn.net/YuhsiHu/article/details/134185740

Oh I wonder if it is because HighResNet inherits the self.resize() module from SRCNN, but does not use it...

Can you please share the config file you're using and the structure of your downloaded PROBA-V dataset?

And when I set os.environ['CUDA_VISIBLE_DEVICES'] = “1，2，3，4” in train.py, I found that the "cuda:0" will be used too. Maybe should I set in terminal?

Ah, yeah. I would just export CUDA_VISIBLE_DEVICES=1,2,3,4 in the terminal.

 Because the class of highresnet inherits SSRNet class.So there are some block didn't attend the training of HighResnet, their gradient will be none.Just inheriting nn.Module will be okay, and every block were written in Highresnet's file.Perhaps my meaning is not clear,my English is so poor.This is a link to slove it: https://blog.csdn.net/YuhsiHu/article/details/134185740

Oh I wonder if it is because HighResNet inherits the self.resize() module from SRCNN, but does not use it...

emmm. I think it was caused by mask_encoder and some blocks:
self.mask_encoder = nn.Sequential(
OneHot(num_classes=12),
DoubleConv2d(in_channels=self.mask_channels, out_channels=1, kernel_size=3),
nn.Sigmoid(),
)
    # Fusion
    self.doubleconv2d = DoubleConv2d(
        in_channels=hidden_channels * revisits,  # revisits as channels
        out_channels=hidden_channels,
        kernel_size=kernel_size,
        use_batchnorm=self.use_batchnorm,
    )
    self.residualblocks = nn.Sequential(
        *(
            ResidualBlock(
                in_channels=hidden_channels,
                kernel_size=kernel_size,
                use_batchnorm=self.use_batchnorm,
            )
            for _ in range(residual_layers)
        )
    )

so I rewrite the highresnet inheriting from nn.Module:
`"""
Adapted from: https://https://github.com/worldstrat/worldstrat/blob/main/src/modules.py
Authors: Ivan Oršolić, Julien Cornebise, Ulf Mertens, Freddie Kalaitzis
"""
from basicsr.utils.registry import ARCH_REGISTRY
from .srcnn_arch import SRCNN
from .arch_util import *
from kornia.geometry.transform import Resize
@ARCH_REGISTRY.register()
class HighResNet(nn.Module):
""" High-resolution CNN.
Inherits as many elements from SRCNN as possible for as fair a comparison:
- DoubleConv2d: the in_channels are doubled by use_reference_frame in SRCNN init
- Encoder: nn.Sequential(DoubleConv2d, ResidualBlock)
"""
def __init__(self, in_channels,
    mask_channels,
    revisits,
    hidden_channels,
    out_channels,
    kernel_size,
    residual_layers,
    output_size,
    zoom_factor,
    sr_kernel_size,
    use_reference_frame=False,
    skip_paddings=True, **kws) -> None:
    super().__init__()

    self.in_channels = 2 * in_channels if use_reference_frame else in_channels
    self.mask_channels = mask_channels
    self.revisits = revisits
    self.hidden_channels = hidden_channels
    self.out_channels = out_channels
    self.kernel_size = kernel_size
    self.residual_layers = residual_layers
    self.output_size = output_size
    self.zoom_factor = zoom_factor
    self.sr_kernel_size = sr_kernel_size
    self.use_batchnorm = False
    self.use_reference_frame = use_reference_frame

    self.skip_paddings = skip_paddings
    self.fusion = RecursiveFusion(
        in_channels=self.hidden_channels,
        kernel_size=self.kernel_size,
        revisits=self.revisits,
    )
    self.encoder = DoubleConv2d(
        in_channels=self.in_channels,
        out_channels=self.hidden_channels,
        kernel_size=self.kernel_size,
        use_batchnorm=self.use_batchnorm,
    )
    self.sr = PixelShuffleBlock(
        in_channels=self.hidden_channels,
        out_channels=self.out_channels,
        kernel_size=self.kernel_size,
        sr_kernel_size=self.sr_kernel_size,
        zoom_factor=self.zoom_factor,
        use_batchnorm=self.use_batchnorm,
    )
    self.resize = Resize(
        self.output_size,
        interpolation="bilinear",
        align_corners=False,
        antialias=True,
    )

def forward(self, x, y=None, mask=None):
    """ Forward pass of the High-resolution CNN.

    Parameters
    ----------
    x : Tensor
        The input tensor (low-res revisits).
        Shape: (batch_size, revisits, channels, height, width).
    y : Tensor, optional
        The target tensor (high-res revisits).
        Shape: (batch_size, 1, channels, height, width).
    mask : Tensor, optional
        The mask tensor.
        Shape: (batch_size, revisits, mask_channels, height, width).

    Returns
    -------
    Tensor
        The output tensor (super-resolved images).
        Shape: (batch_size, 1, channels, height, width).
    """
    hidden_channels = self.hidden_channels

    if self.use_reference_frame:
        x = self.compute_and_concat_reference_frame_to_input(x)

    # Note: we could put all these layers in a Sequential, but we
    # would lose the logging abilities for inspection and lose
    # on readability.
    batch_size, revisits, channels, height, width = x.shape
    x = x.view(batch_size * revisits, channels, height, width)

    # Encoded shape: (batch_size * revisits, hidden_channels, height, width)
    x = self.encoder(x)

    x, mask_channels = self.encode_and_concatenate_masks_to_input(
        x, mask, batch_size, revisits, height, width
    )

    x = x.view(batch_size, revisits, hidden_channels + mask_channels, height, width)

    # Fused shape: (batch_size, hidden_channels, height, width)
    x = self.fusion(x)

    # Super-resolved shape:
    # (batch_size, out_channels, height * zoom_factor, width * zoom_factor)
    x = self.sr(x)

    # Ensure output size of (batch_size, channels, height, width)
    x = self.resize(x)

    # Pad with empty revisit dimension: (batch_size, 1, channels, height, width)
    x = x[:, None]
    return x

def compute_and_concat_reference_frame_to_input(self, x):
    # Current shape: (batch_size, revisits, channels, height, width)
    reference_frame = self.reference_frame(x).expand_as(x)
    # Concatenated shape: (batch_size, revisits, 2*channels, height, width)
    x = torch.cat([x, reference_frame], dim=-3)
    return x

def encode_and_concatenate_masks_to_input(
    self, x, mask, batch_size, revisits, height, width
):
    if mask is not None:
        mask, mask_channels = mask, self.mask_channels
        mask = mask.view(batch_size * revisits, mask_channels, height, width)
        # Encoded shape: (batch_size * revisits, mask_channels, height, width)
        mask = self.mask_encoder(mask)
        mask_channels = mask.shape[-3]
        # Concatenated shape:
        # (batch_size * revisits, hidden_channels+mask_channels, height, width)
        x = torch.cat([x, mask], dim=-3)
    else:
        mask_channels = 0
    return x, mask_channels

`

Ah, okay. I am trying to figure out why I can't replicate your error, but thank you for sharing your code - I will try it and make sure it produces similar results.

Ah, okay. I am trying to figure out why I can't replicate your error, but thank you for sharing your code - I will try it and make sure it produces similar results.
The python version I used is 3.8,and I ran the code yesterday-all results are  similar.Thank you for opening your work,this is an excellent work!~

Awesome, thank you for digging into the code! I'll push a fix to the error you mention, with your change.


request: softlist support

Hi
Can basic softlist support be added (including history.xml)?
The most amount of games in mame are in the softlists but a frontend without softlist support is like ignoring > 50% of mame's emulation...

Dupe.


Won't compile on OpenBSD

Won't compile on OpenBSD, says xcb/xcb.h not found.
I know i probably need to change so it looks in /usr/X11R6/include for xcb.h but i don't know how.

Fixed by adding -I/usr/X11R6/include and -L/usr/X11R6/lib to CFLAGS
Also added -L/usr/X11R6/lib to LDFLAGS


Fix case statement

The correct separator is "|" and not ",".

Oh boy 🤦 Thank you for spotting this.


Admin CLI: namespaces set-subscription-expiration-time and get-subscription-expiration-time operations are not documented on web page

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Downloaded Pulsar 2.7.0 and install it (gunzip and tar -xvf)

$ cd apache-pulsar-2.7.0/bin
$ ./pulsar-admin namespaces | grep expi
Warning: Nashorn engine is planned to be removed from a future JDK release
    get-subscription-expiration-time      Get subscription expiration time for
      Usage: get-subscription-expiration-time tenant/namespace
    set-subscription-expiration-time      Set subscription expiration time for
      Usage: set-subscription-expiration-time [options] tenant/namespace
            Subscription expiration time in minutes

No such documentation here --> https://pulsar.apache.org/docs/en/pulsar-admin/
Expected behavior
Documentation for set-subscription-expiration-time and get-subscription-expiration-time are present here
https://pulsar.apache.org/docs/en/pulsar-admin/
Additional context
Add any other context about the problem here.

Thanks for reporting this issue. I have added a pr #9611 that fixes this issue.

That is excellent - thanks so much!


added random number generation to linalg

@lisitsyn, @vigsterkr Pushed #2421 again, this time against the develop branch instead of feature/linalg

@khalednasr any news  here?
This seems to be close to be merged

closing since inactive


Minor code style fixes.

Replacing @import module statements with regular header imports because bazel doesn't tend to generate module names that match Xcode's.

I've removed the non-stylistic changes from this PR and will push them in a separate one so that the commits are cleaner.


Update Maven and Maven Plugins & fix breaking builds

This commit updates maven to 3.6.0
and updates several plugins to their latest versions
I had to update the surefire plugin to 3.0.0-M3 because of
https://stackoverflow.com/questions/53010200/maven-surefire-could-not-find-forkedbooter-class/53016532#53016532

I tested this locally with java 8 and java 11 without any problems.
I suspect that the circleci config is faulty, causing the surefire plugin to crash for some reason.

ugh... finally fixed it. Openjdk changed something which randomly broke the surefire plugin.

Sorry for the late reply.
Thank you very much for contributing!
Looks good to me 👍


Myrtille and android

Is there a way to show the smartphone keyboard when we click at a "textbox" in the remote connection? Or if there is a way to keep keyboard visible, anything like that.
Thanks in advance.

The smartphone keyboard normally shows when you click a textbox. However in Myrtille, these are not textboxes but rendered display. You have to manually "tell" your smartphone to show its keyboard, I'm not sure it's even possible with most smartphones.... or you can use the "keyboard" button into the Myrtille toolbar which displays a on-screen keyboard.

Thanks for the reply. I´m able to show the keyboard using a hidden input, bu i´ll have to do something to send the text to the rdp session.
Thanks

i´ll have to do something to send the text to the rdp session.

Have a look to the "Text" button, into the toolbar, this is what it does


SentinelHubInputTask  support for sentinelhub.Geometry

Currently SentinelHubImputTask support sentinelhub.BBox for fetching data. It should also support sentinelhub.Geometry to support polynomial.

Hi @sanjivjha,
thanks for this suggestion. It would be cool if geometry could be provided, where the data outside of the geometry would be masked automatically masked out, but since eo-learn focuses more on larger areas, this wasn't implemented.
One thing you could do, though:

use the geometry.envelope as your bbox
download data
import geometry vector and turn it to a raster with the Vector2Raster task in eo-learn to calculate the geometry mask, which you can then apply to the data.

If you are willing to extend the SentinelHubInputTask yourself with a PR, we would be very grateful! :)
Cheers!
Matic

Hi @sanjivjha,
thanks for this suggestion. It would be cool if geometry could be provided, where the data outside of the geometry would be masked automatically masked out, but since eo-learn focuses more on larger areas, this wasn't implemented.
One thing you could do, though:

use the geometry.envelope as your bbox
download data
import geometry vector and turn it to a raster with the Vector2Raster task in eo-learn to calculate the geometry mask, which you can then apply to the data.

If you are willing to extend the SentinelHubInputTask yourself with a PR, we would be very grateful! :)
Cheers!
Matic

this was added in https://github.com/sentinel-hub/eo-learn/pull/461
The user must still provide a BBox, but we decided it should stay that way for now.


Go mod updates (skipped some of the k8s modules as they introduced lot of breaking changes, have to tackle them later).
UBI micro base image update to 9.2-13.
Workflow action updates.

GitHub Issues
List the GitHub issues impacted by this PR:

GitHub Issue #

https://github.com/dell/csm/issues/885

Checklist:

[x] I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
[x] I have verified that new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degenerate
[ ] I have maintained at least 90% code coverage
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have maintained backward compatibility

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

Any idea what these 'gofumpt' issues are in the actions?

They are from golangci-lint which was introduced recently. I plan to address them separately in the next PR.


Plugin Incompatibility with Optimizely CMS versions after 12.16.0

Description:
After updating to Optimizely CMS version 12.16.0 and above, I observed that the [Stott.Optimizely.RobotsHandler] is no longer compatible.
Steps to reproduce:
Install Optimizely CMS version 12.16.0 or later.
Install or activate the [Stott.Optimizely.RobotsHandler].

@aslamy can you tell me which version of the module you are installing with CMS 12.16.0?

@aslamy Just to clarify, I have the current verified CMS and Robots Handler version combinations in DXP as of this morning:

CMS Version (CMS Core Version)
Robots Handler

12.23.0 (12.19.0)
2.6.2

12.22.7 (12.18.0)
2.6.1

12.18.0 (12.13.1)
2.6.1

I've got Robots Handkler 2.6.2 with CMS 12.24.0 and it's working OK.

@aslamy can you confirm whether you are still having an issue or not? I will assume this is not an issue if a response is not received within a week and I will then close this issue.

Closing as this has been tested as working on multiple builds and no further communication has been received.


Riak-CS fails to start on CentOS 6.8 (docker) [JIRA: RCS-381]

Hi,
I run riak-cs in a centos 6.8 docker container.
To make sure the data is persistent, I store the following directories in a separate data container:

/var/data
/var/log
/var/lib/riak/
/var/lib/riak-cs/
/var/lib/stanchion/

When I restart my riak-cs container, I cannot restart riak-cs :
[root@aaf0e279323a /]# riak-cs console
config is OK
-config /var/lib/riak-cs/generated.configs/app.2<IP_ADDRESS>.38.29.config -args_file /var/lib/riak-cs/generated.configs/vm.2<IP_ADDRESS>.38.29.args -vm_args /var/lib/riak-cs/generated.configs/vm.2<IP_ADDRESS>.38.29.args
Exec:  /usr/lib64/riak-cs/erts-5.10.3/bin/erlexec -boot /usr/lib64/riak-cs/releases/2.1.0/riak-cs               -config /var/lib/riak-cs/generated.configs/app.2<IP_ADDRESS>.38.29.config -args_file /var/lib/riak-cs/generated.configs/vm.2<IP_ADDRESS>.38.29.args -vm_args /var/lib/riak-cs/generated.configs/vm.2<IP_ADDRESS>.38.29.args              -pa /usr/lib64/riak-cs/lib/basho-patches -- console
Root: /usr/lib64/riak-cs
Erlang R16B02_basho8 (erts-5.10.3) [source] [64-bit] [smp:4:4] [async-threads:64] [kernel-poll:true] [frame-pointer]

=INFO REPORT==== 18-Jan-2017::09:38:30 ===
    alarm_handler: {set,{system_memory_high_watermark,[]}}

=INFO REPORT==== 18-Jan-2017::09:38:30 ===
opening log file: "/var/log/riak-cs/access.log.2017_01_18_09"
Setup running ...
Directories verified. Res = {[ok],[]}
Setup finished processing hooks ...
Eshell V5.10.3  (abort with ^G)
(riak-cs@<IP_ADDRESS>)1> [os_mon] memory supervisor port (memsup): Erlang has closed

=INFO REPORT==== 18-Jan-2017::09:38:31 ===
    alarm_handler: {clear,system_memory_high_watermark}
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
{"Kernel pid terminated",application_controller,"{application_start_failure,riak_cs,{notfound,{riak_cs_app,start,[normal,[]]}}}"}

Crash dump was written to: /var/log/riak-cs/erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,riak_cs,{notfound,{riak_cs_app,start,[normal,[]]}}})
[root@aaf0e279323a /]# nano /var/log/riak-cs/erl_crash.dump

/var/log/riak-cs/access.log.2017_01_18_09 is empty.
Here is what /var/log/riak-cs/crash.log says:
2017-01-18 09:38:31 =CRASH REPORT====
  crasher:
    initial call: application_master:init/4
    pid: <0.148.0>
    registered_name: []
    exception exit: {{notfound,{riak_cs_app,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,133}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]}
    ancestors: [<0.147.0>]
    messages: [{'EXIT',<0.149.0>,normal}]
    links: [<0.147.0>,<0.7.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 376
    stack_size: 27
    reductions: 119
  neighbours:

Removing and re-creating the data container solves the issue.
But I lose all my data so that's neither a fix nor a workaround.
Please tell me how we could solve this :)

Fix:

do NOT mount /var/lib/riak-cs from the data container
make sure you call /etc/init.d/riak-cs stop before killing the container or run riak-admin repair-2i after restarting riak-cs in a container you killed without stoping riak-cs

Actually that does NOT fix the issue.

Please post your issue to the riak-users mailing list. Github issues are not intended for troubleshooting individual installations.

After much trouble trying to fix this, the issue is actually much simpler.
The riak and riak-cs config files where stored in my app container, not in my persistent data container (where the riak data is). Whenever I upgraded the app container to a newly generated one, the conf files and especially the admin user credentials did not match.
IMHO the riak-cs error is completely misleading and useless : "notfound" should be "admin_user_not_found" or "invalid_admin_user". I will create a new issue for that if I get a positive feedback on the ML.


Catchup tmo-main to v3.4.0 rc2

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_espressif
https://github.com/zephyrproject-rtos/hal_espressif/commit/8e5da13712012d2cc480f7abc699235352153e05
https://github.com/zephyrproject-rtos/hal_espressif/commit/abe299333411cb37a1cb1dd0aa2ea35c27382604
<EMAIL_ADDRESS>

mcuboot
https://github.com/zephyrproject-rtos/mcuboot/commit/6902abba270c0fbcbe8ee3bb56fe39bc9acc2774
https://github.com/zephyrproject-rtos/mcuboot/commit/a6aef32619455cb1697c42d66db489c1608f8410
<EMAIL_ADDRESS>

picolibc
https://github.com/zephyrproject-rtos/picolibc/commit/93b5d5f2ad44867b60267417cd6d6250dbf68983
https://github.com/zephyrproject-rtos/picolibc/commit/d07c38ff051386f8e09a143ea0a6c1d6d66dd1d8
<EMAIL_ADDRESS>

zscilib
https://github.com/zephyrproject-rtos/zscilib/commit/0035be5e6a45e4ab89755b176d305d7a877fc79c
https://github.com/zephyrproject-rtos/zscilib/commit/34c3432e81085bb717e4871d21ca419ae0058ec5 (master)
<EMAIL_ADDRESS>

Note: This message is automatically posted and updated by the Manifest GitHub Action.

John, why are you duplicating what I am working on?

Please don't merge this until I have had a chance to review it in regard to the work that I've already been working on.


Update determine-web-part-width.md

Category

[x] Content fix

What's in this Pull Request?
Updated "Determine the rendered web part size" article with fixes.

Docs Build status updates of commit d670388:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/spfx/web-parts/basics/determine-web-part-width.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 895fcc5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/spfx/web-parts/basics/determine-web-part-width.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix a small (but confusing) typo in the README

Unless I'm misunderstanding something, this is a small typo in the README.

Pull Request Test Coverage Report for Build 158

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.63%

Totals

Change from base Build 157:
0.0%

Covered Lines:
144

Relevant Lines:
146

💛  - Coveralls

Good catch indeed, thank you @andyburke!
 More info here.

I believe I have fixed the commit message as requested.

Just saw it now, can you target branch develop?


Node module caching causes cookie-parser error after lowering and re-lifting Sails in test suite: TypeError: Cannot read property 'cookie' of undefined

Node version: 10.5.3
Sails version (sails): 1.1.0
ORM hook version (sails-hook-orm): n/a
Sockets hook version (sails-hook-sockets): n/a
Organics hook version (sails-hook-organics): n/a
Grunt hook version (sails-hook-grunt): n/a
Uploads hook version (sails-hook-uploads): n/a
DB adapter & version (e.g. sails-mysql@5.55.5): n/a
Skipper adapter & version (e.g. skipper-s3@5.55.5): n/a

I have created a minimal reproduction of my code in which Sails is unable to be lifted a second time in tests due to an error in the cookie-parser dependency:
TypeError: Cannot read property 'cookie' of undefined
 at cookieParser (node_modules\cookie-parser\index.js:45:31)
 at sails-cookie-error\node_modules\sails\lib\hooks\http\get-configured-http-middleware-fns.js:134:16
 at getBuiltInHttpMiddleware (node_modules\sails\lib\hooks\http\get-configured-http-middleware-fns.js:144:7)
 at _afterLoadingSessionHookIfApplicable (node_modules\sails\lib\hooks\http\initialize.js:298:43)
 at sails-cookie-error\node_modules\sails\lib\hooks\http\initialize.js:31:18
 at sails-cookie-error\node_modules\sails\lib\app\private\after.js:111:14
 at sails-cookie-error\node_modules\async\dist\async.js:3861:9
 at sails-cookie-error\node_modules\async\dist\async.js:421:16
 at iteratorCallback (node_modules\async\dist\async.js:998:13)
 at sails-cookie-error\node_modules\async\dist\async.js:906:16
 at sails-cookie-error\node_modules\async\dist\async.js:3858:13
 at handlerFn (node_modules\sails\lib\app\private\after.js:85:18)
 at sails-cookie-error\node_modules\async\dist\async.js:3853:24
 at eachOfArrayLike (node_modules\async\dist\async.js:1003:9)
 at eachOf (node_modules\async\dist\async.js:1051:5)
 at _parallel (node_modules\async\dist\async.js:3852:5)
 at Object.parallelLimit [as parallel] (node_modules\async\dist\async.js:3935:5)
 at Sails.emitter.after (node_modules\sails\lib\app\private\after.js:105:11)
 at _waitForSessionHookIfApplicable (node_modules\sails\lib\hooks\http\initialize.js:30:15)
 at Hook.initialize (node_modules\sails\lib\hooks\http\initialize.js:42:7)
 at Hook.wrapper [as initialize] (node_modules\@sailshq\lodash\lib\index.js:3275:19)
 at sails-cookie-error\node_modules\sails\lib\hooks\index.js:122:20
 at sails-cookie-error\node_modules\async\dist\async.js:421:16
 at processQueue (node_modules\async\dist\async.js:1565:20)
 at taskComplete (node_modules\async\dist\async.js:1588:9)
 at sails-cookie-error\node_modules\async\dist\async.js:1612:17
 at sails-cookie-error\node_modules\async\dist\async.js:906:16
 at Hook.loadModules (node_modules\sails\lib\hooks\index.js:178:14)
 at Hook.wrapper [as loadModules] (node_modules\@sailshq\lodash\lib\index.js:3275:19)
 at modules (node_modules\sails\lib\hooks\index.js:86:25)
 at runTask (node_modules\async\dist\async.js:1621:13)
 at sails-cookie-error\node_modules\async\dist\async.js:1559:13
 at processQueue (node_modules\async\dist\async.js:1569:13)
 at Object.auto (node_modules\async\dist\async.js:1555:5)
 at Hook.load (node_modules\sails\lib\hooks\index.js:80:13)
 at Hook.wrapper [as load] (node_modules\@sailshq\lodash\lib\index.js:3275:19)
 at loadHook (node_modules\sails\lib\app\private\loadHooks.js:212:17)
 at sails-cookie-error\node_modules\sails\lib\app\private\loadHooks.js:344:13
 at sails-cookie-error\node_modules\async\dist\async.js:3083:16
 at eachOfArrayLike (node_modules\async\dist\async.js:1003:9)
 at eachOf (node_modules\async\dist\async.js:1051:5)
 at Object.eachLimit (node_modules\async\dist\async.js:3145:5)
 at load (node_modules\sails\lib\app\private\loadHooks.js:342:17)
 at sails-cookie-error\node_modules\async\dist\async.js:3853:24
 at replenish (node_modules\async\dist\async.js:946:17)
 at iterateeCallback (node_modules\async\dist\async.js:931:17)
 at sails-cookie-error\node_modules\async\dist\async.js:906:16
 at sails-cookie-error\node_modules\async\dist\async.js:3858:13
 at sails-cookie-error\node_modules\async\dist\async.js:421:16
 at iteratorCallback (node_modules\async\dist\async.js:998:13)
 at sails-cookie-error\node_modules\async\dist\async.js:906:16
 at process._tickCallback (internal/process/next_tick.js:61:11)

I can get the tests passing by using import-fresh to "re-require" the config/http.js file (by commenting out and uncommenting the marked lines in test/helpers/appHelper.js).
Anyone know what's going on here?

Hi @blah238 Thank you for providing a repo for your issue. I was able to reproduce your issue by following your instructions on the repo.
Can you please give a little more information about what your trying to accomplish?

Hi @raqem glad to hear you were reproduce the issue.
I am primarily trying to upgrade my existing Sails 0.12.x application to 1.x. This issue appeared in our test suite which lifts a Sails instance once at the beginning, lowers it once at the end, and in some tests (generally ones that modify the test database), lowers and re-raises Sails as part of the test setup or teardown to get back to a clean slate.
It would appear that there is some shared state that isn't properly getting cleaned up between lift/lower cycles, and I'm not sure if that's a problem in Sails or my code, but since it only started happening with the Sails 1.x codebase I'm guessing it's a problem with Sails.
But even with my workaround above in my real application's codebase, some of my other tests are having a similar issue with a different 3rd party package (passport and passport-local) after a second lift, so I'm currently looking into that and will post another issue when I can minimally reproduce it as well.
But I'm guessing that there is something about the middleware system in Sails 1.x that has changed and is causing this since it only occurs with 1.x and not 0.12.x.

@blah238 before we start digging into this more: was your example app generated with Sails v1? (I'm assuming it was, but just want to rule out any kind of upgrade issue since you mentioned running into this while upgrading)
In the mean time, might be helpful to have a look at the changelog to see if anything jumps out at you - at first glance, I'm seeing some links to a few issues related to lift & lower, so there may be something relevant there.

@rachaelshaw correct, I used Sails 1.1.0 to generate the example: https://github.com/blah238/sails-cookie-error/blob/b591687ff7d85f5b18293cf52052584c662fd18a/.sailsrc#L6-L7
I did skim through the changelog but didn't see anything pertinent to this issue, although I have run into an error with lift not working at all in tests, which was fixed by updating captains-log and rc. This issue is also present in the 0.12.x branch, so I will open a PR to update those and hopefully get a new 0.12.x release as well.

@rachaelshaw rather than open another issue I have added a branch in my sails-cookie-error repo that reproduces the issue with passport:
Error: Unknown authentication strategy "local"
    at attempt (sails-cookie-error\node_modules\passport\lib\middleware\authenticate.js:186:37)
    at authenticate (sails-cookie-error\node_modules\passport\lib\middleware\authenticate.js:362:7)
    at Object.processLogin [as auth/processlogin] (sails-cookie-error\api\controllers\AuthController.js:32:7)
    at sails-cookie-error\node_modules\sails\lib\router\bind.js:248:46
    at routeTargetFnWrapper (sails-cookie-error\node_modules\sails\lib\router\bind.js:392:9)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at next (sails-cookie-error\node_modules\express\lib\router\route.js:137:13)
    at Route.dispatch (sails-cookie-error\node_modules\express\lib\router\route.js:112:3)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at sails-cookie-error\node_modules\express\lib\router\index.js:281:22
    at Function.process_params (sails-cookie-error\node_modules\express\lib\router\index.js:335:12)
    at next (sails-cookie-error\node_modules\express\lib\router\index.js:275:10)
    at next (sails-cookie-error\node_modules\express\lib\router\route.js:127:14)
    at addResponseMethods (sails-cookie-error\node_modules\sails\lib\hooks\responses\index.js:149:18)
    at routeTargetFnWrapper (sails-cookie-error\node_modules\sails\lib\router\bind.js:392:9)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at next (sails-cookie-error\node_modules\express\lib\router\route.js:137:13)
    at Route.dispatch (sails-cookie-error\node_modules\express\lib\router\route.js:112:3)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at sails-cookie-error\node_modules\express\lib\router\index.js:281:22
    at param (sails-cookie-error\node_modules\express\lib\router\index.js:354:14)
    at param (sails-cookie-error\node_modules\express\lib\router\index.js:365:14)
    at Function.process_params (sails-cookie-error\node_modules\express\lib\router\index.js:410:3)
    at next (sails-cookie-error\node_modules\express\lib\router\index.js:275:10)
    at next (sails-cookie-error\node_modules\express\lib\router\route.js:127:14)
    at _addResViewMethod (sails-cookie-error\node_modules\sails\lib\hooks\views\res.view.js:426:3)
    at routeTargetFnWrapper (sails-cookie-error\node_modules\sails\lib\router\bind.js:392:9)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at next (sails-cookie-error\node_modules\express\lib\router\route.js:137:13)
    at Route.dispatch (sails-cookie-error\node_modules\express\lib\router\route.js:112:3)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at sails-cookie-error\node_modules\express\lib\router\index.js:281:22
    at param (sails-cookie-error\node_modules\express\lib\router\index.js:354:14)
    at param (sails-cookie-error\node_modules\express\lib\router\index.js:365:14)
    at Function.process_params (sails-cookie-error\node_modules\express\lib\router\index.js:410:3)
    at next (sails-cookie-error\node_modules\express\lib\router\index.js:275:10)
    at next (sails-cookie-error\node_modules\express\lib\router\route.js:127:14)
    at addMixins (sails-cookie-error\node_modules\sails\lib\hooks\request\index.js:97:18)
    at routeTargetFnWrapper (sails-cookie-error\node_modules\sails\lib\router\bind.js:392:9)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at next (sails-cookie-error\node_modules\express\lib\router\route.js:137:13)
    at Route.dispatch (sails-cookie-error\node_modules\express\lib\router\route.js:112:3)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at sails-cookie-error\node_modules\express\lib\router\index.js:281:22
    at param (sails-cookie-error\node_modules\express\lib\router\index.js:354:14)
    at param (sails-cookie-error\node_modules\express\lib\router\index.js:365:14)
    at Function.process_params (sails-cookie-error\node_modules\express\lib\router\index.js:410:3)
    at next (sails-cookie-error\node_modules\express\lib\router\index.js:275:10)
    at Function.handle (sails-cookie-error\node_modules\express\lib\router\index.js:174:3)
    at router (sails-cookie-error\node_modules\express\lib\router\index.js:47:12)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (sails-cookie-error\node_modules\express\lib\router\index.js:317:13)
    at sails-cookie-error\node_modules\express\lib\router\index.js:284:7
    at Function.process_params (sails-cookie-error\node_modules\express\lib\router\index.js:335:12)
    at next (sails-cookie-error\node_modules\express\lib\router\index.js:275:10)
    at xPoweredBy (sails-cookie-error\node_modules\sails\lib\hooks\http\get-configured-http-middleware-fns.js:189:7)
    at Layer.handle [as handle_request] (sails-cookie-error\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (sails-cookie-error\node_modules\express\lib\router\index.js:317:13)
    at sails-cookie-error\node_modules\express\lib\router\index.js:284:7
    at Function.process_params (sails-cookie-error\node_modules\express\lib\router\index.js:335:12)
    at next (sails-cookie-error\node_modules\express\lib\router\index.js:275:10)
    at sails-cookie-error\node_modules\skipper\lib\skipper.js:122:47
    at sails-cookie-error\node_modules\body-parser\lib\read.js:130:5
    at invokeCallback (sails-cookie-error\node_modules\raw-body\index.js:224:16)
    at done (sails-cookie-error\node_modules\raw-body\index.js:213:7)
    at IncomingMessage.onEnd (sails-cookie-error\node_modules\raw-body\index.js:273:7)
    at IncomingMessage.emit (events.js:194:15)
    at endReadableNT (_stream_readable.js:1125:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

To work around the issue I am using the decache to clear the AuthController module from the node modules cache between lower/lift cycles. Using decache on the sails module also has the same effect, but may be overkill.
As it seems to be a similar issue if not quite the same I opted not to create a separate issue for it while you are looking into the original cookie-parser issue. Hope that is ok.
Thanks!

A followup to my previous comment, I was able to refactor my example app to work around the passport error: https://github.com/blah238/sails-cookie-error/compare/passport-error...passport-error-fix
The cookie-parser error still occurs, however, if config/http is not cleared from the node module cache.

Hi @blah238 I realized there are some examples of test in Ration (a dummy site created by @mikermcneil during the Platzi course)
Maybe looking through those can help you get some ideas of what to try next.

@raqem I did not see anything particularly relevant in those links but thanks anyways.
I was able to successfully complete my upgrade to 1.x (actually 1.21 which I saw was just released), so I am no longer actively looking into this. I am still using the workaround of clearing config/http for my tests, e.g. https://github.com/blah238/sails-cookie-error/blob/9c9570fd2e1dad91be9bf3f04e2dfac952057d5e/test/helpers/appHelper.js#L50
Hopefully someday I can remove it 😄

Happy to hear you were able to finish the upgrade!


Corresponding author name

Description
The corresponding author's name appears on top of the paper title instead of in the proper space above the email.
(Optional:) Please add any files, screenshots, or other information here.

(Required) What is this issue most closely related to? Select one.
Other
Internal issue ID
e3bb1db3-42c6-400f-911a-607f8ac06d76
Paper URL
https://services.arxiv.org/html/submission/6000872/view
Browser
Chrome/<IP_ADDRESS>
Device Type
Mac

Thank you


Disqus comments not displaying

I added disqusShortname to my config.toml but am still not seeing the disqus comments section showing up. Is the theme able to properly access _internal/disqus.html?

Realized they only show on the individual blog pages, not on the home page. Closing.


Implement increment/decrement feature

It would be nice if each pocket could support an increment and decrement option, similar to redis incr or similar.
See also https://hexdocs.pm/stash/Stash.html#inc/4

Complete in PR #11
v1.2.0


Blocks the app when running on Nexus 6p

I have the following problem when running directly on my mobile phone (Nexus 6p):

I am using the following code:

import RNTesseractOcr from 'react-native-tesseract-ocr';
/**
 * @param {string} imgPath - The path of the image.
 * @param {string} lang - The language you want to process.
 */
RNTesseractOcr.startOcr(imgPath, lang)
  .then((result) => {
    this.setState({ ocrResult: result });
    console.log("OCR Result: ", result);
  })
  .catch((err) => {
    console.log("OCR Error: ", err);
  })
  .done();

Everything works good till the startOcr method. I have replaced the imgPath "file://" with "" and managed to have it going forward
But, it never reaches then or catch when using with my mobile phone (Nexus 6p)
It works well on my emulator (running Nexus 6p as well).

Any idea what to do for this? Or how can I troubleshoot? Once the issue happens, I cannot do anything on my app anymore...all links are not working. Not sure what is the problem.
Thanks!
Bogdan

Hey!! I'm sorry that I couldn't give support to this project in these days, but due to my new job, I'm still organizing my time to continue with this project.
If you still can't solve this issue. Is it possible you to provide the full log when the app crashes on your device?

@arheom Have you resolve the issue? Because i am also using same code and remove 'file://' from the image path. But it is not reaching to then part, it is catching error that OCR Error: Failed to read bitmap. Any help from your side will be appreciated..

@fazeelzama20 @arheom Did you guys solved the issue? I had same issue, file:///storage/emulated/0/documents/a.jpg is the datapath I am using but didn't work

I just released v2.0.0 which has many improvements that solve most of the open issues.
Can you please git it a try and open a new issue in case there is any bug?
@arheom this might solve your issue considering that tesseract recognition is happening in a different thread
https://github.com/jonathanpalma/react-native-tesseract-ocr/blob/8bd4851edb0902a8100a33ec5f4532df0589a262/android/src/main/java/com/reactlibrary/TesseractOcrModule.java#L82-L95
@fazeelzama20 @SwagatRanjit84 you don't have to worry about removing the file:// substring anymore
https://github.com/jonathanpalma/react-native-tesseract-ocr/blob/8bd4851edb0902a8100a33ec5f4532df0589a262/android/src/main/java/com/reactlibrary/TesseractOcrModule.java#L228


[21098] Change default logconsumer to StdoutErr

Description

This PR documents the change of making StdoutErr the default LogConsumer.

Related implementation PR:

eProsima/Fast-DDS#4873

Contributor Checklist

[X] Commit messages follow the project guidelines.
NO Code snippets related to the added documentation have been provided.
[X] Documentation tests pass locally.
NO Applicable backports have been included in the description.

Reviewer Checklist

[x] The PR has a milestone assigned.
[ ] The title and description correctly express the PR's purpose.
[ ] Check contributor checklist is correct.
[ ] CI passes without warnings or errors.

@richiprosima Please test_3 docs

@mergifyio rebase

@richiprosima Please test_3 docs


check.assert.maybe.array.of.unemptyString throws when called with a null or undefined value.

Version: 5.0.0
Observed behavior:
> check.assert.maybe.array.of.nonEmptyString(null);
Error: Invalid string

Expected behavior:
> check.assert.maybe.array.of.nonEmptyString(null);
undefined

Thanks for raising this, I'll dig into it over the weekend.

Fixed and published as 5.1.0.

Thanks!


Hide amounts when sending money face-2-face

Screens are here zpl.io/blDpMY1
zpl.io/V1lmB4X
zpl.io/25JqpD3
zpl.io/VOmQmXr

Decided with Sasha that secret mode won't affect utxo screen by now, links on screens are above

when activated, security mode in the line  "in progress"  incorrectly displayed of elements.

checked


Firebase v0.2

@alexluong Hi, do you need help maintaining this project? Would love to get this plugin back on track for the community. :)

Thanks @Marcusg62 for the offer! I apologize for abandoning the plugin lately. I'd appreciate any help I can get.
I haven't used the plugin for a while, so I'm not sure how compatible the plugin is with the latest versions of Gatsby (#19 #23 #31 #32). If you can provide some sort of summary on how it's doing and confirm those issues, that would be a great start!
I think the plugin API is stable enough to release the v1.0 version, once all the issues are sorted out.

@alexluong Sure, no problem! I've been looking for a project to work on and I can see myself using this one a lot.
From what I gather in my own experience and viewing open issues, everyone is loving the plugin until they run gatsby build. I think this is because we are not using the useFirebase hook/context described here.
However, that documentation does not show up on the plugin page on gatsbyjs.com plugin page.
If we can confirm that issues like #31 are caused by this then we could simply update the readme and I think we would be back on track.

@Marcusg62 You should disregard the doc page on GitHub (https://github.com/alexluong/gatsby-packages/tree/master/packages/gatsby-plugin-firebase). It's v0.1 documentation.
I basically work on the v2 branch and publish the plugin from there, so the doc on Gatsby site or npm are more accurate.
In v2, useFirebase is not part of the plugin's API anymore.

@alexluong Oof, okay it seems we have some real investigation to do then. Let me get a public repo to you so the issue can be recreated. Sound good?

Yup that would be fantastic. Thank you!

I have added a comment to an existing issue since it seems to be the same problem. I added a link to the repository there. :) #31  #


dehazing

do you think  retrain your model on dehazing work andk it will be useful？

do you think retrain your model on dehazing work andk it will be useful？

hello, Have you experimented in the field of dehazing? How is the effect

No, I just found another model and used it to complete my undergraduate graduation project
------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2022年3月5日(星期六) 上午9:20
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [ZhendongWang6/Uformer] dehazing (Issue #29)
do you think retrain your model on dehazing work andk it will be useful？
hello, Have you experimented in the field of dehazing? How is the effect
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

No, I just found another model and used it to complete my undergraduate graduation project
…
------------------ 原始邮件 ------------------ 发件人: @.>; 发送时间: 2022年3月5日(星期六) 上午9:20 收件人: @.>; 抄送: @.>; @.>; 主题: Re: [ZhendongWang6/Uformer] dehazing (Issue #29) do you think retrain your model on dehazing work andk it will be useful？ hello, Have you experimented in the field of dehazing? How is the effect — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: @.***>

What model did you use to pass the undergraduate project? I'm in the middle of my graduation project, too


ripple.height is not a function

I've try to use lumx in my app. This is my index.html

However, I got a error when click on an button:

ripple.height is not a function

This is my module:

Was able to fix this by adding the following:
    <script type="text/javascript" src="lib/node_modules/velocity-animate/velocity.js"></script>
    <script type="text/javascript" src="lib/node_modules/velocity-animate/velocity.ui.js"></script>

LumX depends on velocity, as you can see here : https://github.com/lumapps/lumX/blob/master/bower.json#L47
You have to install all dependencies by running bower install lumx, as stated in the README.
This issue should be closed.


Check file count before attempting a TSI level compaction.

Overview
This check was previously in a different section of code which was lost during a refactor to the new compaction strategy. The compaction planning now makes a check to ensure at least two files are available for compaction in a level.
Fixes #8451.
Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[ ] CHANGELOG.md updated

I was trying to reproduce the issue but I didn't have any luck. This should fix it though.


Cache the value of the function port from k8s api

Issue Ref: https://github.com/kubeless/kubeless/issues/826
Description:
Address the issue of constantly hitting the k8s api to get the port associated with a function. We only need to retrieve this value once upon creating the consumer process.
TODOs:

[ ] Ready to review
[ ] Automated Tests
[ ] Docs

I agree that a simpler solution can be used. I like the idea of enforcing the port to be 8080, since this is already the default behavior if you don't use a custom deployment.

Hi there. I also seem to be experiencing the 5qps limitation reportd in kubeless/kubeless#826). Was this fix abandoned or replaced by something else?

we never changed this but I don't think that a limitation of 5 qps is a limitation because of calls to the kubernetes API. See the discussion here: https://github.com/kubeless/kubeless/issues/826 (but unfortunately no progress there)

we never changed this but I don't think that a limitation of 5 qps is a limitation because of calls to the kubernetes API. See the discussion here: kubeless/kubeless#826 (but unfortunately no progress there)

Thanks @andresmgot. I have read that. Do you have better throughput in clusters you are working with than 5 messages per second or do you experience the same behavior also? I thought from these two threads that wdamron and @dannyqiu identified the k8s API as the issue (hence this issue)?
Whether my topic has 1 or 10 partitions which my producer writes to the consumers seem be be 5/s per controller. As I increase the number of controllers I see a corresponding linear throughput. I just want to check that I am not doing something wrong.

You are probably don't. I think this issue was never fixed but I doubt the bottle neck is the K8s API for resolving the port. If you have time to investigate it, you can modify the function getFunctionPort to simply return 8080:
https://github.com/kubeless/kafka-trigger/blob/68a3798a36e725fb15c2dac4d4dc56274d075c3b/pkg/utils/event_sender.go#L40
And check if that helps.


On request by @tasosalvas - I fixed some bugs

Thanks so much!
dang this whole millions fork situation makes it hard to have a central place for conversation, as forks don't have their own issue queues.
This is the repo of the original author, it's abandoned since 2017, which is what started this whole mess.
I was saying that user @avryhof has went through the trouble of making a different PyPi package, djangocms-forms-maintained instead of djangocms-forms. It was last active on April 28 this year. It's on https://github.com/avryhof/djangocms-forms
I'm not sure if he will respond, either, but if he does at least your updated version will be able to be installed through pip and we'll know we have a sort-of-canonical fork to contribute future fixes to.
His last activity


Remove little used, undocumented, and broken pca

Closes #264

In light of the fact that it's been broken – yeah, we should probably remove it. I don't have opposition to it being included in the project, but unless we have a fix in mind / time allocated to fix it...best not to have broken stuff lying around IMO.


Extracting only cross ontology relations in linker stage for Multishot ingestion

New feature description.
The fields such as importsFrom and appearsIn will be extracted.

Duplicate of #45