text_on_image Creator - Web design #135

https://images01.nicepagecdn.com/page/39/11/html-template-3911068.jpg Design a text_on_image like the above image
Create a file "text_on_image_NUM_by_(YourName).html" in the modules/text_on_image folder.
Use simple HTML and CSS and JAVASCRIPT to create the text_on_image animation. You can use the interface development https://kwickerhub.com/ (This project) or you can write the lines of code yourself.
Step by Step Guide.
Fork this project(Use the 'fork' button in the top right corner) and Clone your Fork.
git clone https://github.com/YOUR_USERNAME/frontend
Open your code Editor and Create a file "text_on_image_NUM_YOUR_NAME_.html" in the "modules/text_on_image" folder of this project you just cloned. No need to create head, title and body tags, Just Add a div tag with some embedded style(i.e use the style tag) and the script tag where necessary.
If you want to add an image resource, please add it in the folder ••
"modules/text_on_image/images_and_icons"
We recommend you use an svg for your image/icon.
Push your Code: You need to push your recent changes back to the cloud. Use the command below in the main directory of this Repository
git push origin dev
or use a GUI tool to avoid mistakes or complexity. LOL.
Then make you Pull Request...
Below is a example of the code structure we need:
<div>
    <!---YOUR CODE---->
</div>

<style>
    /* YOUR STYLE */
</style>

<script>
    // YOUR SCRIPT if any
</script>

The goal of this issue is to create modules that other people/dev/designers can use or easily import into their projects. Avoid the desire to style all elements in the page by using codes like:
<style>

*{

}
/* OR */

div, a, h1, pre{

}

</style>

use classes or id to style the elements to avoid a collision of styles.
Remember to make your module usable across different screens(Make your design responsive).
For more examples:
modules->buttons
modules->cards
for examples of contributions or Pull request accepted in to the project.
And please do not wait for this issue to be assigned to you as we have limited hands but have a lot to do/cover. Please send in your PR.
Good-luck and thank you.

could you please assign this to me?

Can you please assign me this issue.

text_on_image_135_Shubham_Pardeshi_.html is done. please check my PR

@NtemKenyor I am working on this


Exception in template helper: TypeError: Cannot read property '' of undefined

Exception in template helper: TypeError: Cannot read property 'online' of undefined
    at Object.Template.answerItem.helpers.userStatus (http://localhost:3000/client/template/answers/answer_item.js?96f2d610d91b6621c436db2b7d6dce712c8ecd7a:38:53)
    at bindDataContext (http://localhost:3000/packages/blaze.js?efa68f65e67544b5a05509804bf97e2c91ce75eb:2727:16)
    at Blaze._wrapCatchingExceptions (http://localhost:3000/packages/blaze.js?efa68f65e67544b5a05509804bf97e2c91ce75eb:1606:16)
    at Spacebars.call (http://localhost:3000/packages/spacebars.js?7f53771c84a2eafac2b561c9796dda0d8af8e7f5:171:18)
    at Spacebars.mustacheImpl (http://localhost:3000/packages/spacebars.js?7f53771c84a2eafac2b561c9796dda0d8af8e7f5:108:25)
    at Object.Spacebars.mustache (http://localhost:3000/packages/spacebars.js?7f53771c84a2eafac2b561c9796dda0d8af8e7f5:112:39)
    at Template.answerItem.HTML.DIV.HTML.DIV.HTML.DIV.HTML.DIV.HTML.IMG.class (http://localhost:3000/client/template/answers/template.answer_item.js?a264a2f5b7e515e37ccef05b21702c2820d9e9ae:30:69)
    at Object.Blaze._withCurrentView (http://localhost:3000/packages/blaze.js?efa68f65e67544b5a05509804bf97e2c91ce75eb:2043:12)
    at Blaze._HTMLJSExpander.def.visitAttribute (http://localhost:3000/packages/blaze.js?efa68f65e67544b5a05509804bf97e2c91ce75eb:1971:21)
    at HTML.TransformingVisitor.def.visitAttributes (http://localhost:3000/packages/htmljs.js?567eb96d5d22631c03d6aca6afa4c42f0d1295f2:228:44)

I am getting this error...
My code is running properly so I left it. However, it was getting hard to read my browser console for other errors so I seek help!
userStatus: function() {
		// if (Meteor.users.findOne({_id:this.userId}).status.idle)
		// 	return "user-border-idle"
		if (Meteor.users.findOne({_id:this.userId}).status.online )
			return "user-border-online"
		else
			return null
	},

	//Show user status in text next to username
	isonline: function() {
		if (Meteor.users.findOne({_id:this.userId}).status.online)
			return "is online"
		else
			return null
	},

This is my helper . I keep getting errors for these snippets. But code works as expected...

Maybe you should try to check if the user was found:
userStatus: function() {
        var user = Meteor.users.findOne({_id: this.userId});
        if (user && user.status.online)
            return "user-border-online"
        else
            return null
    },

@jhuenges I've tried this as well but I'm getting the same error.
Exception in template helper: TypeError: Cannot read property 'online' of undefined
    at Object.Template.answerItem.helpers.userStatus (http://localhost:3000/client/template/answers/answer_item.js?43f81b75bceb31496f7b1677bc7799eb1dc9dddf:37:26)
    at bindDataContext (http://localhost:3000/packages/blaze.js?efa68f65e67544b5a05509804bf97e2c91ce75eb:2727:16)
    at Blaze._wrapCatchingExceptions (http://localhost:3000/packages/blaze.js?efa68f65e67544b5a05509804bf97e2c91ce75eb:1606:16)
    at Spacebars.call (http://localhost:3000/packages/spacebars.js?7f53771c84a2eafac2b561c9796dda0d8af8e7f5:171:18)
    at Spacebars.mustacheImpl (http://localhost:3000/packages/spacebars.js?7f53771c84a2eafac2b561c9796dda0d8af8e7f5:108:25)
    at Object.Spacebars.mustache (http://localhost:3000/packages/spacebars.js?7f53771c84a2eafac2b561c9796dda0d8af8e7f5:112:39)
    at Template.answerItem.HTML.DIV.HTML.DIV.HTML.DIV.HTML.DIV.HTML.IMG.class (http://localhost:3000/client/template/answers/template.answer_item.js?a264a2f5b7e515e37ccef05b21702c2820d9e9ae:30:69)
    at Object.Blaze._withCurrentView (http://localhost:3000/packages/blaze.js?efa68f65e67544b5a05509804bf97e2c91ce75eb:2043:12)
    at Blaze._HTMLJSExpander.def.visitAttribute (http://localhost:3000/packages/blaze.js?efa68f65e67544b5a05509804bf97e2c91ce75eb:1971:21)
    at HTML.TransformingVisitor.def.visitAttributes (http://localhost:3000/packages/htmljs.js?567eb96d5d22631c03d6aca6afa4c42f0d1295f2:228:44)

and if you add && user.status to the if statement?

@jhuenges Thank you! This solved it. Could you tell me the logic behind this? Idk why my original code worked, but returned errors. And this works the same why but doesn't return errors.

I guess it works, because it is re-run many times. And at some point the staus.online field is found. So with the little fix we simple avoid the cases in which a) the user b) user.status or c) user.status.online is not known.

hmmm interester

You are probably just trying to access the user before the status field is published.

I'm also running into this problem.
I define a ReactiveVar in my onCreated like this:
Template.myTemplate.onCreated(function(){
  this.data.status = new ReactiveVar('statusName');
});

I then have a helper that checks the status:
Template.myTemplate.helpers({
  isStatus: function( status ) {
    return Template.instance().data.status.get() == status;
  }
});

In the template I use the helper like this:
<template name="myTemplate">
  {{#if isStatus 'statusName'}}
  <!-- other stuff ->>
  {{/if}}
</template>

This will give me this error:
Exception in template helper: TypeError: Cannot read property 'get' of undefined
  at Object.Template.myTemplate.helpers.isStatus (http://localhost:3000/app/client/views/my_template.js?631f07193792a52008a24cdddf3ae499a596dea1:10:50)

I'm scratching my head. So, I'm adding a console.log to the helper:
Template.myTemplate.helpers({
  isStatus: function( status ) {
    console.log( Template.instance().data );
    return Template.instance().data.status.get() == status;
  }
});

Which outputs this:
Object {status: ReactiveVar}
Object {status: ReactiveVar}

Yes, twice. Not once but twice and it THEN throws the error:
Exception in template helper: TypeError: Cannot read property 'get' of undefined
  at Object.Template.myTemplate.helpers.isStatus (http://localhost:3000/app/client/views/my_template.js?631f07193792a52008a24cdddf3ae499a596dea1:10:50)
Exception in template helper: TypeError: Cannot read property 'get' of undefined
  at Object.Template.myTemplate.helpers.isStatus (http://localhost:3000/app/client/views/my_template.js?631f07193792a52008a24cdddf3ae499a596dea1:10:50)

Not once. But twice.
There seems to be a bit of a delay between the console.log output and the errors. Maybe a second or so but a noticeable delay.
Any help and/or insight would be greatly appreciated.


Failed to load OpenCL runtime (expected version 1.1+)

Failed to load OpenCL runtime (expected version 1.1+)

This is not an issue (it is a hack):
https://github.com/ppwwyyxx/tensorpack/blob/04d6055915bed93fbd9239986931cd1853995204/tensorpack/libinfo.py#L5

Does that mean I don't have OpenCL installed?
So do I have to install OpenCL?

read carefully:
https://github.com/ppwwyyxx/tensorpack/blob/04d6055915bed93fbd9239986931cd1853995204/tensorpack/libinfo.py#L4


python3Packages.starlette: 0.13.8 -> 0.14.2

Motivation for this change
doesn't build on master
Maybe we should not update but just fix the tests because this breaks fastapi: https://github.com/tiangolo/fastapi/pull/2335.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

#111079


"getWeather" return strange values.

"world.getWeather" return strange values.
If clear weather:
org.spongepowered.common.weather.SpongeWeather@53793239.
If rain weather:
org.spongepowered.common.weather.SpongeWeather@2cdd2d2.
If thunder weather:
org.spongepowered.common.weather.SpongeWeather@3a0f050f.
"world.getWeather.getName" always returns "weather".

All of your links give 404's btw

It doesn't look like this is implemented yet. https://github.com/SpongePowered/SpongeCommon/blob/master/src/main/java/org/spongepowered/common/weather/SpongeWeather.java It's hard coded right now to return "weather"

@RobertHerhold, this is what returns "world.getWeather".

@gyroninja thank you. Waiting for implementation.

@Azatik Would probably be best if you could open an issue on SpongeCommon just s a reminder that it still needs to be implemented.


Fix http://betterlife-flask.herokuapp.com/admin/incoming/ page error

http://betterlife-flask.herokuapp.com/admin/incoming/ returns internal error

Written by @xqliu
Created at 2015-08-14T10:23:01.000+0800
Link to http://betterlife.atlassian.net/browse/BE-148

The column cate need to renamed to date in Incoming.

Written by @xqliu
Created at 2015-08-14T10:23:47.095+0800


Hi, I got an error after running the leetcode gpt extension

Hi @alhussain-shaikh, thanks for reporting the issue, investigating now 👀

Hi @alhussain-shaikh , can you try the latest release? The issue should be fixed now.

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: began retry configuration implementation

Custom retry strategy behavior. Will merge all retry PRs into the shaffeeullah/storageRetryStrategy branch and then merge that branch into master at the end. This avoids one giant PR.
There is one test currently failing. I believe it is because the options that the makeRequest function is pulling from retry-request are not the options that we're looking for. This change is pending the retry-request library update.

It's exciting to see this work coming together 😄

@shaffeeullah I have opened the retry-request PR here: https://github.com/stephenplusplus/retry-request/pull/35


Maximised window doesn't fill whole screen when on a secondary monitor that has taskbar disabled

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows 10
Bug description
On Windows 10
When Runelite is on a secondary monitor
And the Windows setting "Show taskbar on all displays" is disabled
A maximised Runelite window does not take up the entire screen. Instead, a blank space is left at the bottom, as if a taskbar was present.
Screenshots or videos

RuneLite version
1.9.3
Logs
No response

This is most likely fixed on the latest launcher version. Since you have omitted the launcher version completely from your report, I'm going to close this. Reopen if it is still an issue on 2.5.0.


@orbit/record-cache with ESM not working

When I try to import Orbit packages as ES modules, I get the following error:
record-transform-buffer.ts:33 Uncaught TypeError: Class extends value undefined is not a constructor or null.
It is related to the following line: https://github.com/orbitjs/orbit/blob/fdb35dcc6f774a276387ab8593ef97d6b1c6dd44/packages/%40orbit/record-cache/src/record-transform-buffer.ts#L9
If I change the import path to '.', it works.

Can you provide a reproduction in a simple public project please?

I've found out that the error is triggered only when running Vite dev server, it might be caused by the order of imported files. It works in Vite build though.
I don't know if it's relevant for you anymore, if it is, here is the test project: https://github.com/Thomasan1999/orbit-record-cache-import-test.

I'm getting this error on Vite too. I'm using Yarn 2 though, so I'm not sure if that's related to the error or not.

@Thomasan1999 thanks for the test repo, I will investigate soon. I'm glad it seems to be working in Vite build.
@tchak as a Vite user, do you have any ideas here?

@dgeb Meanwhile, I've opened another issue in the Vite repo. According to sodatea,  it might be related to circular dependencies. A similar issue here.
@samwightt Apparently, if any package provides ESM build, you can exclude them from dependency pre-bundling. @orbit packages provide ESM, so you can use this as a workaround.
import { defineConfig } from "vite";

export default defineConfig({
  optimizeDeps: {
    exclude: [
      '@orbit/indexeddb',
      '@orbit/memory',
      '@orbit/records'
    ]
  }
})

@Thomasan1999 thanks for tracking this down. I can confirm that there is a circular dependency between sync-record-cache.ts and record-transform-buffer.ts in @orbit/record-cache. This cycle would not be trivial to remove, but it is plausible, and I'll consider it. I'm glad that there is an alternate workaround for now.

I decided to remove the cycle in #868 because it cleaned up several aspects of the implementation (see the PR for details). This has been resolved in:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
You can confirm that this fixes the vite/esbuild issue by changing the deps in your test repo to:
-        "@orbit/indexeddb": "0.17.0-beta.21",
-        "@orbit/memory": "0.17.0-beta.21",
-        "@orbit/records": "0.17.0-beta.21"
+        "@orbit/indexeddb": "0.17.0-beta.23",
+        "@orbit/memory": "0.17.0-beta.23",
+        "@orbit/records": "0.17.0-beta.22"

Thanks again for your help tracking this down!

I updated the deps in the test repo and in the project where I actually use them. It works in both now.


Use the shlib wrapper when running nptest

Since there seems to be no way to avoid linking to libssl and libcrypto, just
wrap the test. This unbreaks "shared" builds when using clang and/or OS X.
EDIT: fixed typos.

+1

done, thanks.


⚠ Samsung has degraded performance

In 1077262, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2257 ms

Resolved: Samsung performance has improved in 442ae74.


Allow ITK DisplacementFieldTransform as input to library interface

ITK's DisplacementFieldTransform should probably be converted internally to an elastix DeformationFieldTransform, which internally has a DeformationFieldInterpolatingTransform
Requested by Konstantinos (@ntatsisk)

Should be addressed by supporting external transforms, by the following pull requests:

#944
#946
#948
#949


error when make.

There are errors when make it, is any idea about it?
erlang.mk:5074: warning: overriding commands for target /home/uuu/brod/deps/docopt' erlang.mk:5049: warning: ignoring old commands for target /home/uuu/brod/deps/docopt'
erlang.mk:5074: warning: overriding commands for target /home/uuu/brod/deps/jsone' erlang.mk:5049: warning: ignoring old commands for target /home/uuu/brod/deps/jsone'
make[1]: Entering directory /home/uuu/brod/deps/supervisor3'  ERLC   supervisor3.erl src/supervisor3.erl:200: syntax error before: '::' src/supervisor3.erl:208: syntax error before: '::' make[2]: *** [ebin/supervisor3.app] Error 1 make[1]: *** [app] Error 2 make[1]: Leaving directory /home/uuu/brod/deps/supervisor3'
make: *** [deps] Error 2
it raise error on centos 6.8, but could work on my laptop with ubuntu 16.04.
Thanks in advance!

@buxizhizhoum your OTP in centos6 is probably too old (R16?).
check version: erl -noshell -eval "io:put_chars(erlang:system_info(otp_release)), halt(0)"

It is R14, I will try to update it and have a try after that, thanks a lot!


Generate test cases for scheduler

User Story
As a consumer of algorithm 1, I need to have assurance that it will work as expected so I do not run into issues later.
Description
Come up with the high-level test cases in BDD format (given, when, then) with mock data according to the confirmed data models.
Ideas:

Happy path (correct input produces correct output)
Invalid constraints
No feasible schedule
etc.

Acceptance Criteria

[x] All test cases generated (team identifies any missing tests)
[x] Test cases are written in BDD (Gherkin)
[ ] Mock data is included for every test
[ ] Mock data is structured according to data models

Additional Resources
https://cucumber.io/docs/gherkin/reference/
< data models issue>
< data flow diagram issue>

All test cases generated (team identifies any missing tests) -> see repo
Test cases are written in BDD (Gherkin) -> see repo
Mock data is included for every test -> moved to separate task for sprint 2
Mock data is structured according to data models -> moved to separate task for sprint 2


Cutlet converts こんにちは to Konnichiha instead of Konnichiwa

Cutlet converts こんにちは to Konnichiha instead of Konnichiwa, is it an intentional behaviour or a bug? Because こんにちは should be read as Konnichiwa.

Thanks for reporting that. The issue seems to be that in UniDic 「こんにちは」 is a single token, so it's not possible to recognize the は as the particle in the usual fashion.
If this is an issue for your application, I would recommend registering an exception for こんにちは, as outlined in the README.

This should be resolved in the demo now.


Update session-timeouts.md

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@yogkumgit, this is a request for additional information. Can you please follow up on this? Thanks.

@MSFTTracyP Please help us here. Thanks

@RomanMSFT
Hi,
If you still want to submit this change, please create a new PR in the private repo and have it reviewed by the article author.
Thank you!
cc: @yogkumgit


Non-exhaustive patterns in case error

for code in luna:
class MyClass:
    MyClass
    MyClassVal:
        a:: Int
        b:: Text
    def a: case self of
        a _: a

error is luna: src/Luna/Pass/Transform/Desugaring/PatternTransformation.hs:(40,45)-(46,30): Non-exhaustive patterns in case

Non-exhaustive pattern should never appear, so its a bug, however the code is invalid. The case match pattern a _ is invalid. You cannot match on a variable with its field. It just do not make sense. You can pattern match on a constructor and its fields like Vector _ _ _ OR you can pattern match on a variable a, but you cannot deconstruct a variable-like constructor.

I know that code is invalid and I know how to fix it. It should just be a luna error nat invalid pattern match from Haskell  @wdanilo


New Hex release with float support?

It seems that the latest nimble_options release was Nov 9, 2020, that's quite a while :)... and I could really benefit from the float support added after #63
Thanks <3

done!

Thanks, Josè 🙇♂


Restricting Accounts section - Flash not appearing after redirect

The flash[:notice] in my #authorized_user! is not appearing after redirecting to the root_url. This is causing my permissions_spec.rb "an unauthorized user" text to fail. My other flash messages seem to be all appearing correctly.
module Accounts
  class BaseController < ApplicationController
    before_action :authorize_user!

    def current_account
      @current_account ||= Account.find_by!(subdomain: request.subdomain)
    end
    helper_method :current_account

    def owner?
      current_account.owner == current_user
    end
    helper_method :owner?

    private

    def authorize_user!
      authenticate_user!
      unless current_account.owner == current_user ||
             current_account.users.exists?(current_user.id)
        flash[:notice] = "You are not permitted to view that account."
        redirect_to root_url(subdomain: nil)
      end
    end
  end
end

Hi @jamgar: thanks for getting in touch. Could you please share with me the entire application on GitHub so I can take a closer look?


[CSS] Invalid option

Describe the bug
The following option doesn't exists anymore
https://github.com/thc-tools/webpack-react/blob/c59139493e73d6ca08766c0b9ad84221d6251f4b/packages/quarks/webpack-quark-css/lib/css.js#L32
Expected behavior
Option should be removed

Yep, indeed, was removed in 1.0.0

Will correct it


might want to make the reference to dbrecord a git location, rather than local

or at least mention a setup procedure.

(in stack.yaml, i mean.)

@mwotton Thanks for reporting! We have fixed the issue.

(tangentially, this is very exciting work - if it had been around a few months ago i might have been able to keep using opaleye.)


Cancelation fails on windows for non english users

The code checks for canceled by the user but this message depends on the language.
French for example: Impossible d'exécuter cette commande en raison de l'erreur: L'opération a été annulée par l'utilisateur

Thanks @zvin, anything else we can use on Windows to check? We ran into this on Linux in the past.

We use GetLastError() == ERROR_CANCELLED in a native module here https://github.com/balena-io/etcher/blob/master/src/os/win32/elevate.cpp#L87 , I'm not sure we can get this from powershell or cmd. Or maybe there's a way to force the message to be in English?

Another way might be for us to wrap the user command in its own shell script, so that we can distinguish between runAs errors and user command errors. We do this for Mac and need to do this for Linux.

If you can give me a few days, I will work on this.


Channel.MemberCount returns 0

I've tried to get channel's member count but member count return 0

	dg.AddHandler(func(s *discordgo.Session, m *discordgo.GuildCreate) {

		fmt.Println("Guild Created:", m.Name)
		fmt.Println(m.MemberCount)

		channels := m.Channels

		for _, v := range channels {
			if v.Type == discordgo.ChannelTypeGuildVoice {
				fmt.Println(v.Name, v.MemberCount)
			}

		}

	})
        dg.Identify.Intents = discordgo.MakeIntent(discordgo.IntentsGuildMessages | discordgo.IntentsGuilds |
        discordgo.IntentsGuildMembers | discordgo.IntentsGuildVoiceStates)

by the way, this function worked in discord js
     client.on("guildCreate", (guild) => {

    guild.channels.cache.forEach(channel => {
        if (channel.type == "GUILD_VOICE") {
            console.log(channel.name, channel.members.filter(member => !member.user.bot).size);
        }
    });
});

bu ist work in discord.js
Go

Node.js

discordgo isn't discord.js

how can ı get member count of channel in discordgo ?

Access the guild via the state and loop over all voice states
Then you can count the voice states which have the same channel Ids as your channel
Next time open a discussion instead


feat(filesystem): add symbolic link target, closes #53

Initial draft of the feature. What do you think?
Closes #53.

I think this looks great. Thanks for contributing!


Is the flyway supported for cross database migration?

Which version and edition of Flyway are you using?
flyway-6.5.3
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
Which operating system are you using?
Windows as well as Linux
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
What did you expect to see?
Cross database Migration.
What did you see instead?

Hi. Flyway is indeed cross database. A list of supported databases can be found in our documentation.


Handle model builders producing models with side effects in intermediate caches

This introduces an alternative internal mechanism for applying plugins from inside model builders. This mechanism is more general, as it introduces a concept of a model builder with side effects.
When a side-effecting builder produces a model, it is cached for the current invocation, and can be reused. The side effects are considered idempotent. This means that the first time the model is requested, the side effects apply to the target project. Any consequent request for the model inside the same invocation returns the cached model, without running the side effects again.
However, the intermediate models produced with side effects are not valid for the later invocations. With Isolated Projects, in case of a CC cache miss, Gradle tries to reuse models for all projects that did not have to be reconfigured. In this case, models produced in the previous invocation with side effects are not reused.
For the case of plugin application this provides the following guarantees.
If a top-level model builder applies a plugin to any (maybe even all) projects as a pre-step for its own model, the mechnism guarantees that the plugin will be applied to each requested project even in the case when some of these projects did not have to be reconfigured.

@bot-gradle test without pts

I've triggered the following builds with parameters: -DenablePredictiveTestSelection=false for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle help

Currently, the following commands are supported:
@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN> [without PTS]
Add without PTS to run the build with full test coverage.

A trigger is a special build for this PR on TeamCity, common triggers are:

SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
Specific builds:

BD: BuildDistributions/BuildDocs so that you can preview the generated docs/distribution.
PT: PerformanceTest, all performance tests for Ready For Nightly stage.
APT: AllPerformanceTest, all performance tests, including slow performance tests.
AST: AllSmokeTestsPullRequestFeedback
AFT: AllFunctionalTestsPullRequestFeedback
ASB: AllSpecificBuildsPullRequestFeedback
ACC: AllConfigCacheTestsPullRequestFeedback
ACT: AllCrossVersionTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle merge

queues this PR for testing and merges if all tests pass by:

Creating a merge commit from your PR branch HEAD and the target branch
Running a ReadyForNightly build against the merge commit
When it passes, fast-forward the target branch to this merge commit (i.e. merge the PR)

The merge commit is called a pre-tested commit, which means that it fully tests the integration
of your branch HEAD and latest master, instead of only testing your branch HEAD.
@bot-gradle squash

Squash the current pull request into a single commit. The squash message will come from the pull request body, with:

All Signed-off-by: lines kept.
All authors being Co-Authored-By:.

@bot-gradle cherrypick to <branch>

Cherrypicks the current PR to another branch.
A new PR will be created and a build will triggered automatically if there is no conflict.

@bot-gradle cancel

cancel a running pre-tested commit build or remove it from queue

@bot-gradle clean

clear the conversation history

@bot-gradle help

display this message

To run a command, simply submit a comment.  For detailed instructions see here.

@bot-gradle test PRF

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build


Node Core collaborator, and general involvement

Tracking issue for our ongoing Node.js upstream collaboration efforts.
[edit: simplified description]

@lance

Commits
Comments
Open PRs
Closed PRs

@danbev
--

Commits
Comments
Open PRs
Closed PRs

@lholmquist

Commits
Comments
Open PRs
Closed PRs

@helio-frota

Commits
Comments
Open PRs
Closed PRs

Closing - out of date


Context menu Disable fails

I was able to disable the nodes of jstree using
	var jstreeContents = $('#hierarchy').jstree(true).get_json('#', { 'flat': true });
	$.each(jstreeContents, function( key, value ) {
	    if (value.state.selected == false) {
	         $('#hierarchy').jstree('disable_node', value.id);
	    }
	});

The code above disables the nodes of all unselected items however,
In case the tree is collapsed, the context menu is NOT disabled for all disabled nodes and surfaces on right click (Issue).
While if the tree is NOT collapsed the disable works just fine and context menu does not open up on right click.

Setting a node to disabled will not prevent the contextmenu. You must have some other code in place that prevents the contextmenu from showing, but this is not default jstree behavior. If you want to stop the contextmenu on disabled nodes use the contextmenu.items function and return false if the node in question is disabled.
Best regards,
Ivan


macOS Security Framework fails to import modern PKCS#12 created by OpenSSL 3

Hi,
Im having the following error when running on macbook (M1) with a k3s cluster that was created by k3d:
 cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.19s
     Running `target/debug/test_kube`
Error: SslError: MAC verification failed during PKCS12 import (wrong password?)

This doesn't happen if I use GKE or token based authentication.
I have a repository that reproduces this on my machine: https://github.com/danni-m/PKCS12_issue.
The kubeconfig file im using is:
---
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJkakNDQVIyZ0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQWpNU0V3SHdZRFZRUUREQmhyTTNNdGMyVnkKZG1WeUxXTmhRREUyTXpVNU1qa3pNRGd3SGhjTk1qRXhNVEF6TURnME9ESTRXaGNOTXpFeE1UQXhNRGcwT0RJNApXakFqTVNFd0h3WURWUVFEREJock0zTXRjMlZ5ZG1WeUxXTmhRREUyTXpVNU1qa3pNRGd3V1RBVEJnY3Foa2pPClBRSUJCZ2dxaGtqT1BRTUJCd05DQUFUblVCS1NsT2FpN1J6UTVEandKQktaZFNFYThSTWsvRXpONEJ4N1pnSkQKNjlFS2xRZXZERkl3Mm1rMVpSNzNFNytxR2VpRVlLLzhadW5Tb0tCNGtwdjdvMEl3UURBT0JnTlZIUThCQWY4RQpCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFRmdRVUU0bjlOUzBUODdWaWx2d0hnZ2dSCjU1R1RhWXN3Q2dZSUtvWkl6ajBFQXdJRFJ3QXdSQUlnVlhBRUxBZW5IbVRhVU1GTjViaWZzaE9qYTN3VmRRVm4KTTRXZnhNT0VHWWtDSUdRRE1JT1Vtb2xtd2dEVmZabXo2bGt0Y2lxUHBtRHVxenNrZG9YZ0hiVXUKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=
    server: https://<IP_ADDRESS>:58362
  name: k3d-testing
contexts:
- context:
    cluster: k3d-testing
    user: admin@k3d-testing
  name: k3d-testing
current-context: k3d-testing
kind: Config
preferences: {}
users:
- name: admin@k3d-testing
  user:
    client-certificate-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJrVENDQVRlZ0F3SUJBZ0lJT01iMWYvOHk4a293Q2dZSUtvWkl6ajBFQXdJd0l6RWhNQjhHQTFVRUF3d1kKYXpOekxXTnNhV1Z1ZEMxallVQXhOak0xT1RJNU16QTRNQjRYRFRJeE1URXdNekE0TkRneU9Gb1hEVEl5TVRFdwpNekE0TkRneU9Gb3dNREVYTUJVR0ExVUVDaE1PYzNsemRHVnRPbTFoYzNSbGNuTXhGVEFUQmdOVkJBTVRESE41CmMzUmxiVHBoWkcxcGJqQlpNQk1HQnlxR1NNNDlBZ0VHQ0NxR1NNNDlBd0VIQTBJQUJQbHMxY2ZYdGpQVWIxdUMKZFhCbHVydTBZU3pqR0pGWlEzYXRUTHFDT1FTNlFDQUNMcW5NY29scy82aGhBL2RXY3JJdmFFS1VpWHZIMUs5dApzQkw5OEZxalNEQkdNQTRHQTFVZER3RUIvd1FFQXdJRm9EQVRCZ05WSFNVRUREQUtCZ2dyQmdFRkJRY0RBakFmCkJnTlZIU01FR0RBV2dCU0VzRDdNZElVQnExNGJWdFoybjJ0S1pOMnY4REFLQmdncWhrak9QUVFEQWdOSUFEQkYKQWlBRzB2Yjk4dzV4ekVIL2tORTNBOGh1TmMwRG42N08yMS9WUmtzbFloSWN6Z0loQU9SZlVnSVpaWm40WU54egoydGpUMkhHdUlXS0QvVzVRdGp3Uk5pZjFWWEZjCi0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0KLS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJkekNDQVIyZ0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQWpNU0V3SHdZRFZRUUREQmhyTTNNdFkyeHAKWlc1MExXTmhRREUyTXpVNU1qa3pNRGd3SGhjTk1qRXhNVEF6TURnME9ESTRXaGNOTXpFeE1UQXhNRGcwT0RJNApXakFqTVNFd0h3WURWUVFEREJock0zTXRZMnhwWlc1MExXTmhRREUyTXpVNU1qa3pNRGd3V1RBVEJnY3Foa2pPClBRSUJCZ2dxaGtqT1BRTUJCd05DQUFUMWVDVlhyeTc4V3RSaS9iekQ4c1pZbkIwOUVTZDJCK0lHdDR6c0tTdXMKbWJERGZOWTdvSjhwWGJTeUpyNWkvdCs5VXBoTWljbGVYcHZFUjQycHhLaEZvMEl3UURBT0JnTlZIUThCQWY4RQpCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFRmdRVWhMQSt6SFNGQWF0ZUcxYldkcDlyClNtVGRyL0F3Q2dZSUtvWkl6ajBFQXdJRFNBQXdSUUloQU94bmIrSTZYWEdFNFJ0RWpnelhacG9nOVZxMWJ0cGgKSklWcTRNbllseWJvQWlCNUQ3anFudjRnZGUrRFJFLzRtQ2Uxdk16d1JUSm9ZbnJTcUx3a2VNeGpodz09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
    client-key-data: LS0tLS1CRUdJTiBFQyBQUklWQVRFIEtFWS0tLS0tCk1IY0NBUUVFSUtiU3B6N0NXdFNLZ3FaUHhHWm9tZTZCa1Z6RGxEbkxCRjF4MzFMZEh5dDBvQW9HQ0NxR1NNNDkKQXdFSG9VUURRZ0FFK1d6Vng5ZTJNOVJ2VzRKMWNHVzZ1N1JoTE9NWWtWbERkcTFNdW9JNUJMcEFJQUl1cWN4eQppV3ovcUdFRDkxWnlzaTlvUXBTSmU4ZlVyMjJ3RXYzd1dnPT0KLS0tLS1FTkQgRUMgUFJJVkFURSBLRVktLS0tLQo=

Because you are using rustls, this looks like a duplicate of #542. I'd suggest trying native-tls for now.

@clux Its also happens with native-tls

@clux I pushed the change to my repo to reflect how i try native-tls.

Hm. Damn. It runs successfully on linux against my k3d with rustls-tls.

A workaround for this will be to add openssl-sys = "=0.9.66" to your dependencies to avoid the implicit upgrade to openssl3.

As noted on discord, this is a regression from kube 0.58.0, but only because 0.63 somehow lets in the openssl-sys upgrade that pulls in the openssl 3 from their release on halloween: https://github.com/sfackler/rust-openssl/blob/master/openssl-sys/CHANGELOG.md#v0969---2021-10-31 .
It would be good to have some more eyes on this particularly upstream to find the underlying issue. Pinning openssl-sys is probably only liable to work for so long.
It's strange that it appears on rustls variant of that test case, but the test case is also not disabling default features so both dependencies will be present.

Purging openssl from the dependency tree:
[dependencies]
log = "0.4.14"
anyhow = "1.0.44"
kube = { version = "0.63.2", default-features=false, features = ["derive", "rustls-tls", "client"]}
tokio = { version = "1.0.1", features = ["rt-multi-thread", "time", "fs", "macros", "net"] }
k8s-openapi = { version = "0.13.1", features = ["v1_20"], default-features=false }

gives the error

Error: SslError: No valid private key was found

from https://github.com/kube-rs/kube-rs/blob/120d0001ce58eb18ac59d2a9da1bf8514bc8058c/kube-client/src/client/tls.rs#L90-L117 - so that's the EC issue again.
So it looks like this issue here is related solely to openssl 3.0 (additionally) breaking it on openssl.

This is a problem because that means there's no good way to run kube against k3d on mac's since both tls stacks have issues. If anyone is able to dig in here and look for some workarounds it would be really appreciated.

As noted on discord, this is a regression from kube 0.58.0, but only because 0.63 pulls in the new patch release of openssl-sys that pulls in the openssl 3 from their release on halloween<EMAIL_ADDRESS>(apparently openssl major version changes is not consider breaking for them).

Upgraded the vendored OpenSSL to 3.0.0.

I don't think we're using vendored feature. Actually, enabling vendored feature might be a possible workaround too.

A workaround for this will be to add openssl-sys = "=0.9.66" to your dependencies to avoid the implicit upgrade to openssl3.

The openssl-sys crate will automatically detect OpenSSL installations via Homebrew on macOS and vcpkg on Windows. Additionally, it will use pkg-config on Unix-like systems to find the system installation.
openssl - Rust

v0.9.67 added support for LibreSSL 3.4.0.
@danni-m What's the output of openssl version?

I don't think we're using vendored feature.

Never mind, I just found @danni-m's repo.

@kazk
> openssl version
LibreSSL 2.8.3

Sorry, I didn't realize you had vendered enabled when I commented. openssl-sys simply builds openssl-src when vendored, so that shouldn't be relevant.
I'm currently reading https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/ and https://www.openssl.org/docs/man3.0/man7/migration_guide.html to see if there's any breaking changes that might be relevant to us. I'm guessing using " " as a password is the cause:
https://github.com/kube-rs/kube-rs/blob/7cbd8cde88d713f5b21e1d409ac7064fab64b49f/kube-client/src/client/tls.rs#L7
https://github.com/kube-rs/kube-rs/blob/7cbd8cde88d713f5b21e1d409ac7064fab64b49f/kube-client/src/client/tls.rs#L17-L21

I confirmed https://github.com/danni-m/PKCS12_issue works fine on Linux.
I think the problem is pkcs12_from_pem uses OpenSSL in all target_os:
https://github.com/kube-rs/kube-rs/blob/7cbd8cde88d713f5b21e1d409ac7064fab64b49f/kube-client/src/client/tls.rs#L40-L48
But native_tls::Identity::from_pkcs12 doesn't use OpenSSL on macOS and Windows.
https://github.com/kube-rs/kube-rs/blob/7cbd8cde88d713f5b21e1d409ac7064fab64b49f/kube-client/src/client/tls.rs#L19-L20
https://github.com/sfackler/rust-native-tls/blob/41522daa6f6e76182c3118a7f9c23f6949e6d59f/src/lib.rs#L176-L179
    pub fn from_pkcs12(der: &[u8], password: &str) -> Result<Identity> {
        let identity = imp::Identity::from_pkcs12(der, password)?;
        Ok(Identity(identity))
    }

https://github.com/sfackler/rust-native-tls/blob/41522daa6f6e76182c3118a7f9c23f6949e6d59f/src/lib.rs#L113-L121
#[cfg(any(target_os = "macos", target_os = "ios"))]
#[path = "imp/security_framework.rs"]
mod imp;
#[cfg(target_os = "windows")]
#[path = "imp/schannel.rs"]
mod imp;
#[cfg(not(any(target_os = "macos", target_os = "windows", target_os = "ios")))]
#[path = "imp/openssl.rs"]
mod imp;

Probably this:

PKCS#12 API updates
The default algorithms for pkcs12 creation with the PKCS12_create() function were changed to more modern PBKDF2 and AES based algorithms. The default MAC iteration count was changed to PKCS12_DEFAULT_ITER to make it equal with the password-based encryption iteration count. The default digest algorithm for the MAC computation was changed to SHA-256. The pkcs12 application now supports -legacy option that restores the previous default algorithms to support interoperability with legacy systems.
https://www.openssl.org/docs/man3.0/man7/migration_guide.html#PKCS-12-API-updates

Yeah, found MacOS security framework fails to import RFC 7292 compliant PKCS #12 v1.1 file into keychain using modern cyphers.

It should be noted that OpenSSL 3 will by default move to AES-256-CBC for the encryption by default for the certificate and private key PBE algorithm instead of the legacy RC2-40 or 3DES.

We should be able to work around this by configuring Pkcs12::builder with legacy params when the target OS is mac.
https://github.com/sfackler/rust-openssl/blob/15f263eb7eb61bc241ddc8bc0e5d79b68cb37936/openssl/src/pkcs12.rs#L74-L92
    /// Creates a new builder for a protected pkcs12 certificate.
    ///
    /// This uses the defaults from the OpenSSL library:
    ///
    /// * `nid_key` - `nid::PBE_WITHSHA1AND3_KEY_TRIPLEDES_CBC`
    /// * `nid_cert` - `nid::PBE_WITHSHA1AND40BITRC2_CBC`
    /// * `iter` - `2048`
    /// * `mac_iter` - `2048`
    pub fn builder() -> Pkcs12Builder {
        ffi::init();

        Pkcs12Builder {
            nid_key: Nid::UNDEF,  //nid::PBE_WITHSHA1AND3_KEY_TRIPLEDES_CBC,
            nid_cert: Nid::UNDEF, //nid::PBE_WITHSHA1AND40BITRC2_CBC,
            iter: ffi::PKCS12_DEFAULT_ITER,
            mac_iter: ffi::PKCS12_DEFAULT_ITER,
            ca: None,
        }
    }

Setting the parameters to the commented ones should work. The documentation is outdated with OpenSSL 3.

I'm hoping PKCS#8 support is merged soon (https://github.com/sfackler/rust-native-tls/pull/209). Once we have that, we don't need to depend on openssl on macOS and Windows anymore.

@danni-m If #693 still doesn't work after fcf3a9e (#693), we added openssl-tls feature that uses openssl for TLS on all platforms. You can try that by using the master branch.

Hi All,
I may confirm that latest master have same problem. Testing with macOS Monterey.
Running /kube-rs/target/debug/examples/job_api
Error: native tls error: failed to deserialize DER-encoded PKCS #12 archive: MAC verification failed during PKCS12 import (wrong password?)

Caused by:
    0: failed to deserialize DER-encoded PKCS #12 archive: MAC verification failed during PKCS12 import (wrong password?)
    1: MAC verification failed during PKCS12 import (wrong password?)

Yeah, it's not fixed.
I'd recommend trying openssl-tls feature instead. native-tls feature exists for a historical reason (kube used to use reqwest), and it doesn't make much sense because macos/windows still depends on openssl anyway for creating PKCS#12.
PKCS#8 support in rust-native-tls was merged a few days ago, but I realized we still need to depend on openssl because we need to support other private key formats. We might be able to work around this issue with macos by converting to PKCS#8 instead though.

Hi, i could confirm that now works.
Thx. for your great work.
❯ cargo run --example event_watcher

    Finished dev [unoptimized + debuginfo] target(s) in 0.26s
     Running `/kube-rs/target/debug/examples/event_watcher`
[2022-03-31T13:22:36Z DEBUG kube_client::client::builder] HTTP; http.method=GET http.url=https://<IP_ADDRESS>:8443/api/v1/events? otel.name="list" otel.kind="client"
[2022-03-31T13:22:36Z DEBUG kube_client::client::builder] requesting
[2022-03-31T13:22:36Z DEBUG kube_client::client::builder] HTTP; http.status_code=200
[2022-03-31T13:22:36Z INFO  event_watcher] New Event: Created container dnsutils (via Pod dnsutils)
[2022-03-31T13:22:36Z INFO  event_watcher] New Event: Started container dnsutils (via Pod dnsutils)
[2022-03-31T13:22:36Z INFO  event_watcher] New Event: Container image "k8s.gcr.io/e2e-test-images/jessie-dnsutils:1.3" already present on machine (via Pod dnsutils)
[2022-03-31T13:22:36Z DEBUG kube_client::client::builder] HTTP; http.method=GET http.url=https://<IP_ADDRESS>:8443/api/v1/events?&watch=true&resourceVersion=438543&timeoutSeconds=290&allowWatchBookmarks=true otel.name="watch" otel.kind="client"
[2022-03-31T13:22:36Z DEBUG kube_client::client::builder] requesting
[2022-03-31T13:22:36Z DEBUG kube_client::client::builder] HTTP; http.status_code=200


[IOTS-514] The cloud UI directs to the wrong doc.

In device cloud, the following text redirects to IoT Server docs [1]. Instead, it should direct to [2]. Need help? Read WSO2 Device Cloud documentation. [1] https://docs.wso2.com/display/IoTS300/Android [2] https://docs.wso2.com/display/DeviceCloud/Enrolling+an+Android+DeviceReference: https://wso2.org/jira/browse/IOTS-514

Verified with device cloud and the documentation page redirects to correct documentation - https://docs.wso2.com/display/DeviceCloud/Enrolling+an+Android+Device when clicking on text - 'Need help? Read WSO2 Device Cloud documentation' on the Android device enrollment page.

As it's a UI redirection issue, cannot add any automation tests for this.


pull a list of pushdowns to witness from each flux e2e test and require post-run

Add a function to flux's stdliib/testing.go that walks the AST, finds the test _columns = () => statements, calls the function and returns the list of strings on the .require_pushdown (or similar) member. Call this function in influxdb e2e test harness and verify that the pushdown occurred. The mechanism to ensure it occurred could either be using the meta channel (Adding Metadata to source nodes), or otherwise logging which rewrite rules occured.
DOD

Can specify which pushdowns should have occurred from individual test cases and the test harness enforces this.

I'd like to extend the scope a tiny bit, instead of a list of pushdowns that occurred we should check for a list of planner rules that were applied. This way we can catch both pushdowns and other rules like the Fill  etc.

@nathanielc I am a little skeptical of locking down which planner rules were applied. If at some point we had a situation where a rule's transformation was undone, the test would still pass. Perhaps this seems unlikely, but I expect us to have a large number of rules, and at some point rules will interact with each in non-obvious ways. In my opinion, it's better to lock down the elements of the plan that we want to see.
What about something like this: when we construct the execution DAG, each source and transformation will record that it is being constructed, along with any relevant details about its parameters. We can get anything about the plan that is known statically this way.
There are lots of thing that we may want to check for in the plan, it would be good to have a solution that is robust to all of them. For example, we may wish to know:

That some nodes are not in the plan at all (e.g., all sorts eliminated from the plan)
That nodes are ordered in some particular way (e.g., that we've transposed filter/group combos so that the filter always comes before the group)
That some detail of a node has changed in a particular way (e.g., in a filter node, we may wish to ensure that r.foo = 1 or r.foo = 3 is rewritten to contains(r.foo, [1, 3]) or vice versa)

Also, if we have explain soon, that may help us out here, and make a mechanism like this unnecessary?


anchore-engine fails with 404 errors when using a single container + db in docker-compose.yaml

Is this a request for help?:
yes
Is this a BUG REPORT or a FEATURE REQUEST? (choose one): BUG REPORT
Version of Anchore Engine and Anchore CLI if applicable:
0.7.3
What happened:
While reading https://docs.anchore.com/current/docs/engine/engine_installation/ there is a sentence that states:
"The Engine is comprised of six smaller micro-services that can be deployed in a single container or scaled out to handle load."
I am attempting to create a single anchore-engine container using docker-compose which runs all of the services instead of a container for each micro-service.  Looking through the documentation, I did not find how to run with a single container.
I researched the python code and found that a startup parameter of "-all" will run all of the services.  I created a docker-compose.yaml file based on https://docs.anchore.com/current/docs/engine/quickstart/docker-compose.yaml which uses:
command: ["anchore-manager", "service", "start", "--all"]
When running the single container, plus the postgres db container, a variety of 404 errors are generated in the log.
What did you expect to happen:
I expected the single anchore-engine container to perform normally like it does with the multiple containers.
Any relevant log output from /var/log/anchore:
"docker-compose up" output:
output.txt
What docker images are you using:
anchore/anchore-engine:v0.7.3
"postgres:9"
How to reproduce the issue:
Create a docker-compose.yaml file containing this content:
    version: '2.1'
    volumes:
      anchore-db-volume:
        # Set this to 'true' to use an external volume. In which case, it must be created manually with "docker volume create anchore-db-volume"
        external: false

    services:
      # The primary API endpoint service
      all:
        image: anchore/anchore-engine:v0.7.3
        depends_on:
          - db
        ports:
          - "8228:8228"
        logging:
          driver: "json-file"
          options:
            max-size: 100m
        environment:
          - ANCHORE_ENDPOINT_HOSTNAME=all
          - ANCHORE_DB_HOST=db
          - ANCHORE_DB_PASSWORD=mysecretpassword
        command: ["anchore-manager", "service", "start", "--all"]

      db:
        image: "postgres:9"
        volumes:
          - anchore-db-volume:/var/lib/postgresql/data
        environment:
          - POSTGRES_PASSWORD=mysecretpassword
        expose:
          - 5432
        logging:
          driver: "json-file"
          options:
            max-size: 100m
        healthcheck:
          test: ["CMD-SHELL", "pg_isready -U postgres"]

Run "docker-compose up" and watch the log output.  Note the numerous calls to http://all:8228/* which fail with 404 errors.
Anything else we need to know:
It would be nice if there could be a quick-start example of a docker-compose.yaml, similiar to https://docs.anchore.com/current/docs/engine/quickstart/docker-compose.yaml,  configured to run with a single anchore-engine container.

What specific calls are you making? A 404 indicates the service is running. The response specifics will help determine what service is having an issue.
The default config.yaml used inside the container and manipulated with the env vars exposed to the container are optimized for the single-service-per-container usage, so there may be rough edges here.

I looked at the output.txt and the issues is that the default config.yaml inside the container assumes that only one service is running so all the service configs use the same port and thus cannot all start correctly.
See: https://github.com/anchore/anchore-engine/blob/master/conf/default_config.yaml#L116
If you copy that file out of the container and attach it back as a volume using bind to /config/config.yaml you'll be able to customize it. What you need to do is set a unique port for each service in the 'services' list in the config.yaml. Leave the 'apiext' service on 8228 since that is the external API that clients talk to. That should fix your issue.
I still recommend using separate containers because things like failures of a single process/service are much harder to diagnose/debug when you have 5-6 processes in the container. It uses the same amount of total resources but is much simpler for things like docker-compose logs, and healthchecks to indicate the status of each service. But either way should work.

Thanks. Yeah, if there could be a quick start example/option that's equivalent in simplicity with the one container versus multiple that would help with this kind of need.


cpe_chrome doesn't work until Spotlight is finished indexing

As discussed, I discovered cpe_chrome was failing during our DEP enrollments due to Spotlight not finishing indexing during the initial bootstrap.
Chrome is integral in our deployment (and is installed on all machines), so for now I have opted to disable the return unless node.installed?('com.google.Chrome') function. The Master Preference functionality is a one-time thing, so it is crucial that it works.
Perhaps a case should be written to look for Google Chrome in it's default installation path(s) and if we don't find it there, then use the cpe_utils spotlight functionality.

https://github.com/facebook/IT-CPE/pull/134

Fixed with attached PRs


Default to deployed AirnodeRrpV0 contract addresses in airnode-examples

Rather than have users deploy the AirnodeRrpV0 contract as part of the airnode-examples flow, the default should be be to use the address of the AirnodeRrpV0 contract that API3 has already deployed on that chain. This would save the user a step and also better mimic the experience of Airnode deployment in which we do not ask providers to deploy this contract themselves. These addresses are available for all of the chains airnode-examples supports both in the docs and in airnode-protocol deployments. The exception is for the local flow, which would still need the deployment step, hence deploying AirnodeRrpV0 should still be an option.

update of READ.me needed

Hi, @dcroote, this is a really nice addition an works very well. I tested this along with the tests of issue no. 1412. No problems found.


moment-transform, plugin to manipulate dates through patterns

I've finally decided to do something with that plugin of mine, here it is:
http://a----.github.io/moment-transform/
It allows simple operations (set / add / substract) to parts (year, day, hour, …) from a string.
moment().transform("YYYY-MM-+01 06:00:00.000"); // Tomorrow at 6am

Some options are available like defining your own patterns.

Interesting!  Please create a PR in the moment/momentjs.com repo to add this to the plugins section of the documentation.  Thanks.

Thanks. PR done.


sexpr-wasm can't commute align= offset=

Some of the torture tests fail with this because s2wasm emits them in the opposite order as wasmate, e.g.:
(f64.store align=1 offset=8 (i32.const 0) (f64.const 0))

It would be good to also update store-offset.txt adn load-offset.txt, as well as make sure that the spec repo has the same tests.
s2wasm_known_gcc_test_failures.txt has a list of expected failures. I don't run it on the bots yet (will add this afternoon), to repro:
/s/wasm/experimental/buildbot/assemble_files.py --assembler /s/wasm/experimental/buildbot/work/sexpr-wasm-prototype/out/sexpr-wasm --files /s/wasm/experimental/buildbot/work/s2wasm-out/\*.wast --fails /s/wasm/experimental/buildbot/work/sexpr-wasm-prototype/s2wasm_known_gcc_test_failures.txt --out /s/wasm/experimental/buildbot/work/sexpr-wasm-out/

sexpr-wasm matches the spec repo. See https://github.com/WebAssembly/spec/blob/master/ml-proto/host/parser.mly#L252. Maybe s2wasm should emit them in the correct order. :smile:

Closing, sounds like we've decided on having a fixed order.


Password to databases should be hidden by default

If you go to http://localhost:8088/databaseview/show/2 (where 2 is the id of your database), you will see password in plain sight:

I don't think it's very secured, since https is not enforced by default either :disappointed:

Oh wow. Thanks for reporting that. The password is encrypted in the database, but shouldn't be in plain sight here. I'll pull it out of that view right now.

https://github.com/airbnb/caravel/pull/355

Merged, 0.8.8 is out and addressing the issue. I'm communicating to the community now via the Google group and Gitter channel. Again, thanks for pointing this out.


⚠ Bofrost.de has degraded performance

In 0168067, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1502 ms

Resolved: Bofrost.de performance has improved in bc24622 after 16 minutes.


[Fix]: IndexError during mim download command execution in search.py

Bug Fix: IndexError in mim command
We recently identified and fixed a bug that caused an IndexError: list index out of range exception when running the mim download command in Conda:
mim download mmsegmentation --config pspnet_r50-d8_4xb2-40k_cityscapes-512x1024 --dest .

The issue occurred in search.py at line 339, where a check for value[0] being an instance of dict was being made without first confirming whether value was empty. This resulted in the following error:
Traceback (most recent call):
  ...
  File "C:\Users\Enbla\anaconda3\envs\openmmlab\lib\site-packages\mim\commands\search.py", line 339, in _parse
    If isinstance(value[0], dict):
IndexError: list index out of range

The fix involves adding an additional check to ensure value is not empty before checking if value[0] is a dictionary instance:
elif isinstance(value, (list, tuple)):
    If value and isinstance(value[0], dict):

Following this fix, re-running the mim command successfully installs the model:
processing pspnet_r50-d8_4xb2-40k_cityscapes-512x1024...
Download ---------------------------------------- 187.1/187.1 MiB 2.5 MB/s eta 0:00:00
Successfully downloaded pspnet_r50-d8_512x1024_40k_cityscapes_20200605_003338-2966598c.pth to C:\Windows\System32
Successfully dumped pspnet_r50-d8_4xb2-40k_cityscapes-512x1024.py to C:\Windows\System32.

We recommend users encountering this issue to update to the latest version where this bug has been addressed.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMCls.
The documentation has been modified accordingly, like docstring or example tutorials.

Hi @WikChang,
We'd like to express our appreciation for your valuable contributions to the mim. Your efforts have significantly aided in enhancing the project's quality.
It is our pleasure to invite you to join our community thorugh Discord_Special Interest Group (SIG) channel. This is a great place to share your experiences, discuss ideas, and connect with other like-minded people. To become a part of the SIG channel, send a message to the moderator, OpenMMLab, briefly introduce yourself and mention your open-source contributions in the #introductions channel. Our team will gladly facilitate your entry. We eagerly await your presence. Please follow this link to join us: https://discord.gg/UjgXkPWNqA.
If you're on WeChat, we'd also love for you to join our community there. Just add our assistant using the WeChat ID: openmmlabwx. When sending the friend request, remember to include the remark "mmsig + Github ID".
Thanks again for your awesome contribution, and we're excited to have you as part of our community!

Hi, what is your mmsegmentation version?


noImplicitOverride missing in playground tsconfig options

when v4.3.0-dev.20210401 is selected, the new flag is not available in tsconfig
sorry if this is the wrong spot to raise playground issues

I believe @orta has a process for this, and I think it happens after the stable release. In the meantime, you can just use a comment: // @noImplicitOverride: true
I’ll let Orta decide whether to transfer/close/whatever


Update hold-distribution-errors.md

Removing a whitespace in the cmdlet (with the whitespace the command won't run)
@markjjo for your review

@SeunginLyu PR merged


add EnumSet.allOf implementation

As discussed, J2CL hasn't implemented getEnumConstants yet. You'll have to replace EnumSet.allOf with EnumSet.of(values())


Shard global cv table

@ctiller This is now ready for review.

On second thought, hold off on reviewing this.   Its showing negligible tsan speed improvements.

Is this still active?

This didn't have the desired impact, and is probably superseded by caching poll-cv threads.


Clock.py should start by announcing the current time, whatever it is

Announcing the current time immediate provides a quick check on audio and serial configuration.

Resolved by merge of pwd-8-Clock-announcement branch.


Recover Tax Rate in Classic Network (#101)

These changes aim to implement the burn tax as voted on Classic governance proposal 3568 and currently undergoing vote in proposal 4661 in all Station views and gas fee calculations on classic network only. Tax rates will only be displayed on classic network once the burn tax is activated, and it will not affect any other TXs on different networks.

@MarventusWP #101 PR was merged on mobile branch


Prevent overwriting index.html and styles.css on build

This is more of a feature request.
My problem is that I have some custom code in my styles.css and index.html and these get overwritten each time I build. Currently I keep a copy and then overwrite the build versions that were generated by impact-node.
Since it's rare to modify these files, there is no reason for impact-node to overwrite them each time. I suggest impact-node just generate them if they do not exist, or the on the initial project creation.

Hi, sorry for delay. So you propose this: check for styles.css and index.html before build, if there's no one, then copy default file. Right?

You don't want to just copy the files because the paths change due to the build that makes game.js
It's OK to generate the index.html and styles.css if none exist, but if they already exist in build, and are unchanged since last build, don't overwrite them with defaults. This is because I add some things to style.css and index.html in the build.


Can I help?

Hello! I love to code! Maybe I can help?

Are you on Scratch?
We'd be glad to have an additional member.
What programming and markup languages do you know?

@MegaApuTurkUltra He helped make ScratchExt 2.0. Easy'd be good for html/js.

Seems kay. @The-Cheese-Eater, input please.

Sure! Just so we can see what you'd like to add to the site, could you clone our repository, add your changes, and if we like it, we'll make a pull request. :) Then I'll add you as a organization member.

@The-Cheese-Eater Yay :D

@easyscratcher Join OpenSprites, too :P

@GrannyCookies The Verify Scratch account isn't working.

@all And I can translate OpenSprites to german, too ;D

Isn't it?

That would be pretty cool! :D I've alerted to GrannyCookies to the problem

great

Could you give us more info? Error?

Yeah ^

I just made the system.

That's all you can say really, isn't it :P

Let me add debug stuff

done

what's the error now?

Try now

kay

It works :D

Great! :)


MR-CT training rounds

Hello author, may I ask how many training rounds you set in the experiment of MRI conversion to CT

Hello, I usually train them for 60 epochs for all the cases.


Create endpoint

rejected:B6
reason:system logs are missing

rejected:B6
reason:system logs are missing


Consider exposing promise unhandled rejection hook

Hey, I've written the following proposal here: https://gist.github.com/benjamingr/0237932cee84712951a2
I'd love your feedback.

it is exposed. RSVP.on('error'

@stefanpenner right, and I'm asking you expose it on "process" in addition like the proposal says, Please consider reading it :p

Sounds good. I'll add it to rsvp and es6promise this weekend

Awesome - thanks a ton :)

thanks for investing :)

please, don't emit this event on process object. It could end up conflicting with native node.js/io.js implementation or other libs. If the purpose is to share emitter between dupes, the event should be namespaced  somehow (e.g. process.on('rsvp:possiblyUnhandledRejection'))

@benjamingr thoughts?

@stefanpenner
The whole idea here is to is to fire the same events as native promises and with other libraries so you get a global place to handle errors - please see the design document (at the start of the issue) on what problems it solves.
What @vkurchatkin is describing is why we want to do this.

@benjamingr the idea is good, but there is a reason why developing a standard takes time. There is no consensus on how this should be done.

@vkurchatkin I believe there is, and several libraries have already implemented this. This standard is just a minimal first stage as a preparation for more interesting standards and ideas which is why all it takes is exposing two events on process and nothing more.
If you have any interesting feedback I would greatly value it here: https://gist.github.com/benjamingr/0237932cee84712951a2
You can also find me regularly in the Stack Overflow JavaScript chatroom and I tend to frequent #promises too. You can also contact me by email if you'd prefer (benji at tipranks) (dot com)

@benjamingr i believe the best thing todo is to namespace the event for all implementations. This way it wont conflict with any current or future built-ins.
After-which we can bug standards/language folks to consider this proposal.
something like:
process.on('promise:possiblyUnhandledRejection')

@stefanpenner there are no standards/language folks. This is just NodeJS/io.js and the libraries. The name "possiblyUnhandledRejection" doesn't make much sense outside of promises anyway so prefixing it doesn't make sense IMO.
On the other hand if the need ever arises you can always give it a different name - "possiblyUnhandledRejection" as a name was chosen just because it made sense - there is no obligation to support it in the future but hopefully it will be used and people will find it useful.
The idea is again - to create a global point all promise libraries and native promises report unhandled rejections to so the user can choose what to do on an unhandled rejection (report it, restart the server, special handling, ignore it or whatever they want).

@stefanpenner  note the events have been renamed to unhandledRejection and unhandledRejectionHandled as Domenic and Petka suggested in various threads and as when and bluebird implement.

Where did I suggest that? I liked possiblyUnhandledRejection... no big deal though.

@Domenic To be fair - Petka told me that you suggested these names in a spec and encourages implementing them with this name in bluebird as real events. If you care I can ask him where (cc @petkaantonov) - apologies if I misrepresented your opinion.

@domenic In the original email you suggested unhandledrejection and rejectionhandled and the camelCased versions as per node convention are unhandledRejection and rejectionHandled.

@petkaantonov I suggested error and rejectionhandled actually, then at the bottom had

We may be better off with a separate unhandledrejection event (or, more accurately and as popular libraries call it, possiblyunhandledrejection)

I just want to mark the time and date - @domenic said something nice about bluebird :D (that it's popular)

@stefanpenner this is now implemented in io.js in the 1.4 release. Please consider adding it to RSVP.

@stefanpenner this is now implemented in io.js in the 1.4 release. Please consider adding it to RSVP.

yup I believe I am on board. Unfortunately pretty busy now, will likely look into it further post ember-conf (which is next week)

Q now has this, you're pretty much the last ones left.

Ping @stefanpenner

So, it's been like half a year and native node does this. Would be nice to finally have it in.

Pr welcome? :D

Sure.

Basically
    if (typeof process === "object" && typeof process.emit === "function") {
        try {
             process.emit("unhandledRejection", promise._result, promise);
        } catch (e) { /* don't throw for rejection hooks failing in hostile environment */ }
   }

In https://github.com/tildeio/rsvp.js/blob/7684756417cb69ce91033c7951fcf5ba92f879aa/lib/rsvp/promise.js#L179

Yup exactly

This just cost me like 4 hours stef :(

@benjamingr why didn't you use RSVP.on('error'? emitting events from objects you don't own is generally a bad idea

Because I worked on a code base I did not author that used es6-promise - I just assumed implementations don't swallow exceptions anymore :/

@benjamingr :( sorry about that.
I'm in the midst of some rsvp maintenance, and would like to tackle that as part of this.
Out of curiosity is there a test suite for unhandledRejections ala promise/a+ or some prior art re tests I could use to double check my own interpretation?

cc @domenic @petkaantonov  w.r.t tests.
I think that both the Node spec and the browser unhandled rejection tracking spec in Chrome are based off the bluebird spec for unhandled rejections but I might be wrong.
https://github.com/petkaantonov/bluebird/blob/master/test/mocha/unhandled_rejections.js

@stefanpenner srsly :(

@benjamingr To be clear - just checking for process-emit does not work in a bundled environment. There is currently an outstanding issue for that on WhenJS as well.
You'll probably want to check for process.browser as well.

@joepie91 first of all thank you for your work, I've been in a really busy time in my life and the moments I get to deal with the web platform and node are pretty scarce - hopefully I'll have time in a month :)
Second of all - I'm surprised the APIs are so consistent, I was expecting a lot less variation. The browser events are named the way they are intentionally in bluebird, and native promises now fire the same events with the same name.

@benjamingr There's actually quite a lot of variation, but not so much in the event names - for example, some implementations will use a different event format from other implementations, and the behaviour varies between implementations when you define both a modern handler (window.addEventListener) and a legacy handler (window.onunhandledrejection) in a browser environment.
Anyhow, I've just completed a module that I've been working on for a while (and for which I'd initially compiled the Gist I linked): unhandled-rejection - it basically provides an environment-independent and implementation-independent way to deal with unhandledRejection handlers. I hope I can add RSVP.js to the list soon :)

@stefpanner ping


Issue with Aeon Labs - Home Energy meter after update to 5.4.2 (Latest version as of 7/23 - Docker) from 5.2.2

Hi,
I have been using HEM v1 for sometime with zwavejs2mqtt + HA without any issue. I have set group 1 reporting for both clamps and set it as 30 seconds. This setup has been working fine on 5.2.2, as soon as I updated to 5.4.2 HEM stopped updating the values automatically. If I refresh from zwavejs2mqtt dashboard by click refresh the values are fetched otherwise it just does not refresh.
I made sure old configuration values for Group 1 are still there like 30 sec refresh which I tried changing few times to kickstart HEM. Restarted all of the devices but still did not work. Eventually I came back to 5.2.2. Is there any change in HEM v1 driver or anything else which might be causing this issue?
Thanks!

I have attached two days log. I updated it yesterday and it stopped reporting Node 24 (HEM) or rather updates were not flowing in zwavejs unless you do it manually. I rolled it back and it started working, tried couple of times updating to latest and then rolling back.
5.2.2 Node 24 reports every 30 secs
5.4.2 Node 24 does not report though config set for group 1 is 30 secs, updated couple of times did not work. When i manually refresh i can see in the logs correct value is being fetched.
zwavejs2mqtt-store.zip

Can you re-interview the device and make a log of that too?

I believe you want it for 5.4.2 and not 5.2.2? Will update to 5.4.2 and interview. The log which I had sent should have some interview stuff as well as thats the first thing I tried.

Attached
Manual_Refresh.log
Interview.log
zwavejs2mqtt-store.zip

Same behavior with zwavejs 8.0.5 and HEM Gen 5 (ZW095): manual refresh works but automatic updates are not happening. I'm a new HA/zwavejs user so cannot comment which version still worked, but I know the HEM works since it is sending automatic updates with Openhab and its Z-Wave implementation.

@zwave-js-bot add compat flag to 0x0086:0x0002:0x0009:0.0
// This device reports compound values on the root endpoint
preserveRootApplicationCCValueIDs: true

The endpoint changes in v8 cause the root endpoint to be hidden. This was the case before, but we incorrectly mapped the reports to endpoint 1, so you would see the values change. The bot should create a PR in a few seconds which fixes that.

@github-0 I'll also need a driver log of a re-interview from you.


fix fix core for string predicate in storage layer

Proposed changes
Currently, for string read from plain page, we hold ptr from page to avoid memcpy.
But if page is released, the ptr from page is invalid, core dump happens.
So for string from plain page, memcpy is neccessary.
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

It seems that we are likely to refer to the memory in the page elsewhere, and the same problem exists?


Connector: MySQL Destination

Conduit needs to be able to use MySQL as a destination.

The Vitess connector: https://github.com/conduitio-labs/conduit-connector-vitess fulfills the need for a MySQL destination connector.


searching and case sensitivity

some users have entered their name all in lower case.
I tried searching for one yesterday:
I searched on family name. I typed 'Smith' but they had entered 'smith'; this user did not appear among the many 'Smiths'.
Then I searched for ALL teachers (as this teacher is on the export from the teacher database). All surnames beginning with lower case letters appeared, but sorted separately from those with capitals at the start, so the search results looked a bit like this:
Adams
Barclay
Charlston
Cooper
...
Zemansky
abbot
charwood
frogmore
smith
Could the search AND the listing be made case-insensitive?
The we'd type 'smith' or 'Smith' and we'd see:
Smith A
smith b
Smith c
etc

minor corrections to previous post


Added YoutubeAPI

This project is actually deprecated :(
https://www.tomasvotruba.cz/blog/2019/05/06/end-of-gophp71-org/
I should archive it, thanks for feedback


Perf/icons

Acceptance Criteria

[x] Design Review by @Gagne87, @clastzoo
[x] Technical Review by @hirsch88, @mladenplaninicic, @nobilo
[x] Style Guide Review @hirsch88, @mladenplaninicic, @nobilo
[x] Visual test done by @hirsch88, @nobilo, @mladenplaninicic, @Gagne87, @clastzoo
[x] Functional test done by @hirsch88, @nobilo, @mladenplaninicic
Browser Testing by @hirsch88, @nobilo, @mladenplaninicic, @Gagne87, @clastzoo

Desktop

[x] Chrome
[x] Edge
[x] Safari
[x] Firefox

Tablet

[x] iPad (Landscape / Portrait)

Mobile

[x] Safari iOS
[x] Chrome Preview

[ ] add the ds icons from beginning


aka.ms links 'about-bot-adapter' and 'bot-services' lead to same URL

Sample information
All samples
Describe the bug
When going through the comments of the samples, there are two urls that redirect to the same document.
https://aka.ms/bot-services
https://aka.ms/about-bot-adapter
both lead to: https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-basics?view=azure-bot-service-4.0&tabs=csharp
Expected behavior
Presumably these two links should direct to different docs.
[bug]

@corinagum - which sample file these links are in?

@Kaiqb they are predominately in the generators and nodejs samples:

We used to have separate topics about bot and adapter, but those were combined into one. That is why I think there are two links. The links are going to the combined topic which is correct.


fix(deps): update terraform terraform-ibm-modules/cos/ibm to v8.9.2

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
8.9.1 -> 8.9.2

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.9.2
Compare Source
Bug Fixes

deps: updated KMS module to 4.15.2 in the bucket DAs (#685) (412cdb5)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v1.4.2

Your semantic-release bot :package::rocket:


Crash on Windows

I built WAVM with Visual Studio 2015 and LLVM 4.0.
Running wavm with any test causes program crash with no console output even when -d is set.  GDB reports Thread 1 received signal SIGSEGV, Segmentation fault.
Running Test Test\wast\helloworld.wast gives the following error message.
Test\wast\helloworld.wast:3:2: missing import module="env" export="_fwrite" type="func (i32,i32,i32,i32)->i32"
(module
 ^
Test\wast\helloworld.wast:3:2: missing import module="env" export="memory" type="memory"
(module
 ^
Test\wast\helloworld.wast:3:2: missing import module="env" export="_stdout" type="immutable i32"
(module
 ^
Test\wast\helloworld.wast: testing failed!

Build log: https://ci.appveyor.com/project/rongjiecomputer/wavm/build/1.0.17

I verified that with the latest code I can't reproduce the crash or the error messages running helloworld.wast.
The build log looks ok.
Do Assemble and Disassemble work?
Can you try a Debug or RelWithDebInfo build, and run it in the debugger to see exactly where it's crashing?

Assemble and Disassemble work just fine.
When I ran wavm.exe in debugger, debugger got stuck at a std::string function (from MSVC internal xstring). I tried to step in/out/over, nothing works. I have to abort debugging process to get out.
	_Myt& assign(const _Myt& _Right, const size_type _Roff, size_type _Count = npos)
		{	// assign _Right [_Roff, _Roff + _Count)
		_Right._Check_offset(_Roff); // <------- Stuck at here

Anymore idea?

Can you download my build artifact and test with helloworld.wast? Or can pack your executables for me to compare?

I can reproduce the crash with your build (running wavm helloworld.wast), but it doesn't have debug info so it's hard to tell what's going on.
I suspect the problem is some incompatibility with your LLVM build. Are you building it yourself, or using something prebuilt? I build LLVM locally.

I am using prebuilt LLVM provided by someone else.
I updated the build script, PDB and binaries can be found here, though I don't have PDB for LLVM so it might be impossible to find anything useful.

Using those binaries with PDB, the callstack is in some STL code called by LLVM. I think the problem is likely that LLVM was compiled with a different STL than WAVM. Building LLVM with the same version of VS2015 should solve the problem.

Thanks for taking your time to do all the debugging. Looks like I have no choice other than building LLVM myself.


improvement: 修改table空数据状态和文本溢出显示tips

Codecov Report

Merging #1038 (7cf2e76) into v2.6.x_develop (39b43a9) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop    #1038   +/-   ##
===============================================
  Coverage           60.62%   60.62%
===============================================
  Files                 469      469
  Lines               30047    30047
===============================================
  Hits                18217    18217
  Misses              11830    11830

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Connection loss after long term running. (<=2h)

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Windows 10 (x64)

Kernel Version (Linux Only)

Platform
PC

SDK Version
<IP_ADDRESS>

Language
C++/CLI

Segment
Robot

Issue Description
I`m running the camera in a C++ application (Compiler is VS2015) just for getting the color and
depth images. All process after acquiring images is done on the GPU (Geforce GTX1080 TI).
The device runs well, but after some time (mostly after around 2h) it disconnects, the windows
sound for USB deplugging plays, and the following exception ist thrown:
Ausnahme ausgelöst bei 0x00007FFB76613C58 in NativeApplicationTest.exe: Microsoft C++-Ausnahme: librealsense::windows_backend_exception bei Speicherort 0x000000F0BBAFCF50.
Ausnahme ausgelöst bei 0x00007FFB76613C58 in NativeApplicationTest.exe: Microsoft C++-Ausnahme: std::runtime_error bei Speicherort 0x000000F0BBAFEE88.
Ausnahme ausgelöst bei 0x00007FFB76613C58 in NativeApplicationTest.exe: Microsoft C++-Ausnahme: [rethrow] bei Speicherort 0x0000000000000000.
Ausnahme ausgelöst bei 0x00007FFB76613C58 in NativeApplicationTest.exe: Microsoft C++-Ausnahme: std::runtime_error bei Speicherort 0x000000F0BBAFF1D0.
Ausnahme ausgelöst bei 0x00007FFB76613C58 in NativeApplicationTest.exe: Microsoft C++-Ausnahme: [rethrow] bei Speicherort 0x0000000000000000.
Ausnahme ausgelöst bei 0x00007FFB76613C58 in NativeApplicationTest.exe: Microsoft C++-Ausnahme: std::exception bei Speicherort 0x000000F0BBAFF348.
The exception occurs in the first of the following codelines:
rs2_process_frame(align, frames, &e);
if (check_error(e) == -1) {
rs2_release_frame(frames);
throw exception("Error HelperRealsense - rs2_process_frame");
}
The hardware reset implementation doesn`t work after this exception too.

The main question to focus on is what causes the hardware disconnections. Internally, the hardware / software is being tested for long periods (days) for stability, and while not every unit passes through such test, we are fairly confident in that aspect of the product.
Something in the combination of USB subsystem, cables and the camera is causing (what seems like) a power-cycle. This can be purely electrical, or caused by other drivers (any other devices on the same hub?)

I can't 100% rule out the possibility of a firmware bug, so if you could share the settings you are using (resolution, fps, format of each steam and controls), @RealSense-Customer-Engineering can try to reproduce this.

Hello dorodnic, at first thank you for your answer. I ordered today a new USB-Cable, which has been recommended for the D435 inside the intel forums (the cable: https://www.ntcdistributing.com/usb-3-1-type-c/a-to-c/usb-3-1-a-male-to-c-male-with-dual-screw-locking-cable/) and will test it.
At the active USB-hub, i`m using, the D435 is the only device which is plugged in.
The settings for my device are attached:

Now I`ve tested it with the depth quality tool - the same happens there after running it for an hour.

Maybe I got another hint for you -> the post processing doens`t matter. The same behaviour (the librealsense::windows_backend_exception and all the other stuff) occurs without it too.

And ironic white now it happened with only using the USB-cable which is delivered with the D435 (no hub, noch longer cable, without post-processing). The difference was that only the first line with the librealsense::windows_backend_exception could be found in the callstack.

I think you can close this issue! But Intel should deliver better cables in future.
Im using this one: https://www.ntcdistributing.com/usb-3-1-type-c/a-to-c/usb-3-1-a-male-to-c-male-with-dual-screw-locking-cable/

[Realsense Customer Engineering Team Comment]
@goetzmi,
Thank you for the update!  Happy to hear it was just the cable and nothing else.
Please let us know if you have any other questions.


Feature Request: Please make toast images accept byte array as source

Hi,
I am experimenting with the new Notification API's and so far they look great! However, I work with images in a byte array format a lot and it would be very nice if I could just enter the byte array's as my image source when I want to show them in a toast. For now I would first have to save the picture somewhere which creates the hassle of keeping track of all the pictures etc.
I hope this could be possible in the future
thanks

Hey! This isn't really an Extensions feature, but since I'm also on the team that owns the toast API's themselves, I'd love to talk about why you would need this feature in your app!
So, what app are you making and why do you need temporary images in the toasts? Why aren't those images saved somewhere as files already?
Just trying to understand your scenario. We understand the feature ask, but we want to understand why you're in this scenario where you need the image to only be on the toast, and not stored anywhere else.
Thanks!
Andrew

Thanks for the fast response,
I am making an app that stores data in a 'document' kind of fashion, which makes all the included images be saved as byte arrays. I then want to toast messages which have one of the included images in the toast.
I first tried with external saved images, but then moving my document to another computer would cause me to lose all the images.

Ah, that makes sense.
Yeah, for now you'll have to just save the picture somewhere so that the toast can reference it, and then clean it up later. The logic shouldn't be too complicated - since toast notifications only persist for 7 days by default, you can just have a temp image folder, and periodically look through it and delete images that are older than 7 days, since the toast notification definitely won't be referencing the image anymore at that point.
We might consider allowing directly embedding the images in notifications, but we don't have any immediate plans.
However, thanks for explaining your scenario! It's really useful knowing who would use these features, it helps us prioritize features!
I'll close this issue since it's not a NotificationsExtensions feature, but your feedback has been received and is tracked in our notifications API backlog. Thanks!


Change issue links to web frontend

As frontend is moved to another repo, updating links to issues to reflect that.
We could also consider removing these links to keep the contributing guide just about this repo
An argument against removing the links to frontend changes would be there would be contributors who might miss the first line in the Readme.

@aapeliv, @Roshanjossey merged :)


It should be possible to do a pull request from inside GT

External (non-feenk) developers should be able to contribute to GT through the industry standard GitHub process of pull requests.
Since the released image does not contain repositories, the necessary repository has to be recreated.
Next a fork must be created.
Then a feature branch must be added on which to commit/push changes.
Finally a pull request must be submitted.
The GitHub CLI tool gh can be used here.

There is now a first draft of a proof of concept of this process
https://book.gtoolkit.com/contributing-to-gt-through-a-github-pull-r-7gkxhsrfoc11i8k03v35q7fhb

Here are some additional screenshots to illustrate the Contribute/PR story.
Both terminal screenshots show what should work before you try the process.
Create a private repository in your GitHub account, add some file to it, and make sure you can clone using the 2 URL variants, without a need for any authentication. Then start GT in that terminal.

Using the GitHub web UI you can verify that your fork has the commit in the feature branch.

After you create the pull request (either scripted from GT or using the GitHub web UI), the PR should appear in the upstream repository.

By using the new GtGitHubAPITool instead of GtGitHubCLITool (one external dependency less) and some newly added actions, the following flow/process is now possible.
Make sure the GitHub Personal Access Token is set.

Then either fork/clone/load/register from GtGitRepositoryRegistryHistory

Or fork an existing repository in place and clone/load/register it.

Create a new feature branch.

Make a change to an existing method.

The repository is on the feature branch and sees the change.

Commit the modification/change.

Push it on our fork/branch.

Finally create the pull request.

Which should return a pull request JSON with a URL.

This is really cool!
And... I continue to be wary of storing credentials in a Smalltalk image. There is no way to reliably prevent them from being saved to disk unencrypted with the image. At least with the cli approach one can use ssh-agent with a password protected SSH key.

This is really cool!
And... I continue to be wary of storing credentials in a Smalltalk image. There is no way to reliably prevent them from being saved to disk unencrypted with the image. At least with the cli approach one can use ssh-agent with a password protected SSH key.

I expressed same feedback in Discord thread before this was closed, please look at this message as it may be addressed.

The problem is that even if it's always read from a file, even temporary objects that haven't been garbage collected can be saved to disk during image save. AFAICT there is no way to secure secrets in a Pharo-based image other than using a read-only image.

All true.
But security is never absolute, it sits on scale, different people or environments might have different requirements.
It is important to be aware of the risks and to offer some options.
The way I see it: if it lives in a file on disk it is not different from living inside a saved image, that is all on my own machine. As long as I am aware of not sharing the image with someone unless I clear the secret.
It is all good and well to try keep secrets out, but you need them to access remote systems, so eventually they need to be passed around.

Good point that different users have different security needs. I'll just point out that in the case of git via SSH, file ~= image because one can add an SSH key with a passphrase to the agent, making stealing of the key file much less useful.


Can this benchmark support grad CAM?

❓ Questions and Help
Can this benchmark support grad CAM?
I noticed that this benchmark can create mask montage to show probability heatmaps  during mask segmentation. Can it also be fit for object detection?

Sorry, could you please expand a bit on what you meant by grad CAM?
I didn't understand the question.

Sorry, I didn’t express it clearly.

You can attach a hook in one of the layers of the model to return the feature activation, as discussed in https://github.com/facebookresearch/maskrcnn-benchmark/pull/164
It should be fairly easy, but let me know if you have any further questions.


Update how-to-connect-fix-default-rules.md

constant and expression are two methods for transformations, if you select constant when creating the mapping it will sync the literal text "Authoritativenull" but if you use expresion it will achieve the intended purpose, so using the word constant there makes it a bit confusing as to what method to use.

@Arkthos : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off


⚠ Bofrost.at has degraded performance

In 40ca29a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1149 ms

Resolved: Bofrost.at performance has improved in 1fd6668.


images resized company_visit

@jamestiotio please view I have fixed the company visit image the others are like what I have explained in my telegram messages my deepest apologies
understandable have a nice day

Okay, this LGTM. Will merge.


Bump liquidjs to 5.1.14-rc.0

this PR tests new liquidjs 5.1.14
@tiero @altafan please review

you can bump 5.1.14 @louisinger


Remove epollex poller

@donnadionne

Interesting. I'm definitely glad about removing a lot of test load, but I have a few questions:

Isn't epollex is our most performant polling engine? We should investigate what's the impact of this change on performance.
It would be good to record the impact on the test volume (e.g. difference between the number of test targets before and after) and on test timing (before and after for the most impacted test jobs) as a comment in this thread.

* Isn't epollex our most performant polling engine? We should investigate what's the impact of this change on performance.

I have the same confusion. Is there any public discussion/design that lead to this decision?

And we can see obvious performance drop in the official benchmark dashboard: https://grafana-dot-grpc-testing.appspot.com/?orgId=1&from=1645688323837&to=1652449137355. Is performance not a goal anymore?

So the long and the short of it:
We've got some bad bugs in epollex regarding fd starvation, and our mid
term plan is to move to event engine. In the meantime (a quarter or so) we
need to decide whether to fix epollex or switch to another poller
implementation - and we think epoll1 will be broadly similar to the
performance curve we'll see with the first generation event engine - so
doing this now let's us flush out any potential problems there.
That said, a quick survey of internal code suggests approximately nobody is
holding grpc in such a way that there ought to be any real measurable
difference between the two pollers (epollex has some very finicky
requirements around what can be shared between completion queues and
there's no surfacing of whether or not an application is doing so, besides
a gradual performance degregation over time).
On Sat, Apr 2, 2022, 1:58 AM Jay @.***> wrote:

Isn't epollex our most performant polling engine? We should investigate what's the impact of this change on performance.

I have the same confusion. Is there any public discussion/design that lead
to this decision?
—
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/29160#issuecomment-1086595172, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNG45NJT6J2JDTZHFO7R7DVDAD3JANCNFSM5RDCQ2HA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Note back in the 2019, we (TiKV) did a benchmark of different poll engines (we did that because epollsig was removed, which actually performed even better than epollex), and found throughput was reduced by 20% when using epoll1 instead of epollex.


--clearance false should change the root routing

If you install suspenders with --clearance false, on routes.rb, it still ways:
root :to => 'Clearance::Sessions#new'

I also have this issue. I have created a fix, but for some reason the rspec test I am trying to apply to fit with thoughtbot contribution guidelines isn't working.
Without the Clearance root route, "/" shouldn't be routable. To that end I have attempted:
And 'the root Clearance route should not exist' do
  { :get => "/" }.should_not be_routable
end

But it fails with "undefined method `routable?'".
Apart from proving it with the test, I have resolved this :(


[autofix] Automatic fixes replace single line comment with multi line comment when on same line as @require

Hello, using --fix, I've found some unexpected changes:
for example, @import nib //for mixins becomes @import nib /*for mixins*/
Is it a bug or is there an explanation somewhere ?
I'm using this config (still in the middle of fixing issues)
module.exports = {
    extends: [
        'stylelint-stylus/standard',
    ],
    rules: {
        'stylus/indentation': 4,
        'stylus/at-extend-style': null,
        'stylus/at-rule-empty-line-before': null,
        'stylus/block-opening-brace-space-before': null,
        'stylus/color-hex-case': null,
        'stylus/declaration-colon': null,
        'stylus/hash-object-property-comma': null,
        'stylus/media-feature-colon': null,
        'stylus/no-at-require': null,
        'stylus/number-leading-zero': null,
        'stylus/property-no-unknown': null,
        'stylus/pythonic': null,
        'stylus/selector-list-comma': null,
        'stylus/selector-list-comma-newline-after': null,
        'stylus/selector-type-no-unknown': null,
        'stylus/semicolon': null,
        'stylus/single-line-comment': null,
    },
};

Thanks for the many issue reports. I will check them one by one when I have time.

Fixed in postcss-styl v0.12.3. Please update postcss-style.


[.NET] Low resolution images in an image set don't stretch as they do on other platforms

Platform
What platform is your issue or question related to? (Delete other platforms).

.NET WPF

Issue
The below card renders differently on .NET compared to UWP and Javascript.
Javascript behavior (UWP is similar):

.NET behavior

Json:
{
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "type": "AdaptiveCard",
  "version": "1.2",
  "body": [
    {
      "type": "ImageSet",
      "images": [
        {
          "type": "Image",
          "url": "http://messagecardplayground.azurewebsites.net/assets/person_w1.png"
        },
        {
          "type": "Image",
          "url": "http://messagecardplayground.azurewebsites.net/assets/person_m1.png"
        },
        {
          "type": "Image",
          "url": "http://messagecardplayground.azurewebsites.net/assets/person_w2.png"
        },
        {
          "type": "Image",
          "url": "http://messagecardplayground.azurewebsites.net/assets/person_m2.png"
        }
      ]
    }
  ]
}

@andrewleader FYI.

@shalinijoshi19 @RebeccaAnne was this pushed out because we confirmed this was existing behavior in 1.1, and not a regression?

@Andrewleader I pushed this out because it didnt appear to be a ship blocker at this point in time.  Do you guys think we should block 1.2 RTM for this or can this be handled separately as a patch or a 1.3 release?

Also because there was still ambiguity around the spec for it that has not yet been resolved and I didnt see any activity on it since it had been filed.

A patch can be fine, but we should be clear on whether this was a regression or not. If it was a regression, we definitely need to patch it. If .NET always behaved like this, we could wait till 1.3.
JavaScript and UWP behavior is correct, setting the "size" property to one of the sizes (small/medium/large) should force the image to that size, even if it means upscaling the image.

Sounds fair @andrewleader ; Can you help update the spec with the expected behavior and I will take care of assigning this for more investigation next week after we are freed up from 1.2 release formalities.

There is no spec since this was an original 1.0 feature, but sounds good!

@almedina-ms assigning to you for post 1.2 investigation and fixing. We need to figure out if this is a regression or not. If it is, then it makes the case for a post 1.2 patch release else we can include it for 1.3 directly.


feat(copyRspackPlugin): support transform configuration

Summary
implement the transform option in the CopyRspackPlugin.
related issue: https://github.com/web-infra-dev/modern.js/issues/5610

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

It's also a bit of weird that includeForgottenExports doesn't bundling the types exported from other packages into the api report file, in that the type RawCopyRspackPluginOptions is not being included. This could be related to the limit to the api-extractor as stated in https://github.com/microsoft/rushstack/issues/3430.