feature: rewrite supernode server with golang

Signed-off-by: Allen Sun<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
This PR add a very fundamental HTTP server for Dragonfly's supernode in Golang. This is a very beginning step of Dragonfly to be refactored in golang. With this step, we could continue to add routes and inner implementation of supernode's functionalities.
It uses github.com/spf13/cobra as a cmd framework, and designed to have a daemon which contains a server. Currently, this pr only supports an HTTP endpoint: GET /_ping.
It starts to define the config struct instance:
// Config contains all configuration of supernode.
type Config struct {
	// ListenPort is the port supernode server listens on.
	// default:
	ListenPort int

	// HomeDir is working directory of supernode.
	// default: /home/admin/supernode
	HomeDir string

	// the core pool size of ScheduledExecutorService.
	// When a request to start a download task, supernode will construct a thread concurrent pool
	// to download pieces of source file and write to specified storage.
	// Note: source file downloading is into pieces via range attribute set in HTTP header.
	// default: 10
	SchedulerCorePoolSize int

	// DownloadPath specifies the path where to store downloaded files from source address.
	// This path can be set beyond BaseDir, such as taking advantage of a different disk from BaseDir's.
	// default: $BaseDir/downloads
	DownloadPath string

	// PeerUpLimit is the upload limit of a peer. When dfget starts to play a role of peer,
	// it can only stand PeerUpLimit upload tasks from other peers.
	// default: 5
	PeerUpLimit int

	// PeerDownLimit is the download limit of a peer. When a peer starts to download a file/image,
	// it will download file/image in the form of pieces. PeerDownLimit mean that a peer can only
	// stand starting PeerDownLimit concurrent downloading tasks.
	// default: 4
	PeerDownLimit int

	// When dfget node starts to play a role of peer, it will provide services for other peers
	// to pull pieces. If it runs into an issue when providing services for a peer, its self failure
	// increases by 1. When the failure limit reaches EliminationLimit, the peer will isolate itself
	// as a unhealthy state. Then this dfget will be no longer called by other peers.
	// default: 5
	EliminationLimit int

	// FailureCountLimit is the failure count limit set in supernode for dfget client.
	// When a dfget client takes part in the peer network constructed by supernode,
	// supernode will command the peer to start distribution task.
	// When dfget client fails to finish distribution task, the failure count of client
	// increases by 1. When failure count of client reaches to FailureCountLimit(default 5),
	// dfget client will be moved to blacklist of supernode to stop playing as a peer.
	// default: 5
	FailureCountLimit int

	// LinkLimit is set for supernode to limit every piece download network speed (unit: MB/s).
	// default: 20
	LinkLimit int

	// SystemReservedBindwidth is the network bandwidth reserved for system software.
	// unit: MB/s
	// default: 20
	SystemReservedBindwidth int

	// MaxBindwidth is the network bandwidth that supernode can use.
	// unit: MB/s
	// default: 200
	MaxBindwidth int

	// Whether to enable profiler
	// default: true
	EnableProfiler bool

	// Whether to open DEBUG level
	// default: false
	Debug bool

Ⅱ. Does this pull request fix one issue?

none
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
I think we must add test case here.
While we need to add a very helpful and easy-to-use test frame work for Dragonfly, like PouchContainer does. Also cc @Letty5411 for some input if you could.
Ⅳ. Describe how to verify it
~ $ curl <IP_ADDRESS>:65001/_ping
OK~ $

Ⅴ. Special notes for reviews
none

Codecov Report

Merging #222 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #222   +/-   ##
======================================
  Coverage    72.4%   72.4%
======================================
  Files          29      29
  Lines        1435    1435
======================================
  Hits         1039    1039
  Misses        365     365
  Partials       31      31

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 019d754...7c96d49. Read the comment docs.

LGTM


COMP: Applied gtest PR 4025 to fix build with old clang

From: https://github.com/google/googletest/pull/4025

@dzenanz

Would updated GTest solve this issue for you?

#3979 was merged. Does that fix the problem for you? If not, please update this PR as it now has merge conflicts.

I do think this is superceeded by #3979 and can be closed.  @seanm  Thanks for poking this.  @dzenanz  Thanks for updating google test.

#3979 was merged. Does that fix the problem for you?

We will see on cdash tomorrow...

If am reading the dashboard correctly, GTest compile failure is now gone.

If am reading the dashboard correctly, GTest compile failure is now gone.

Only because it's much worse, it doesn't build at all:
https://open.cdash.org/build/8590216/configure
CMake Error at CMake/itkCompilerChecks.cmake:16 (message):
  Apple Clang 10.0.0 or later is required.

That is due to merging the PR which bumps required C++ version to 17 (from C++14). Maybe it is time to retire those builds?


Issues with GLFW and transparent windows

Hi there, I'm testing GLFW's new transparent windows feature with bgfx and there's something weird going on with the alpha:

Notice that nothing is 100% opaque for some reason.  I'm testing this on Arch Linux using glfw's current master and this patch.
Any ideas?

I forgot to mention that the gears example in GLFW seems to work correctly:

It's probably alpha values that are written in backbuffer that are not 255. You can change some code to force it to write 255 into alpha.

A minimal test with 255 alpha has the same problem:

Oh, do you mean patching bgfx?

Skipping bgfx and using just GLFW with vanilla nanovg also works fine:

Yeah, try without NanoVG, just with 01-cubes example.

I already did :)
All the examples have some transparency even though they should be rendering opaque colors.

Ok investigate, and let me know why it's happening.

I'm just starting with bgfx.  Can you give me some tips to where I should be looking?

Start from 01-cubes. Try changing clear color value, and shaders to fill up alpha value. You could use RenderDoc to understand what's happening.

This is 01-cubes with the default clear color 0x303030ff and a hardcoded opaque red in the shader (see here).  If you look closely you can see that the debug text is also transparent.

Why did you remove glfwWindowHint(GLFW_CLIENT_API, GLFW_NO_API);?

If I don't remove it, the alpha value in bgfx::setViewClear has no effect and I can't make the background transparent.

So basically you're changing behaviour. I don't use GLFW to create context for GL, rather I create it inside glcontext_glx.*
If you do debug build it would assert on creation of GLX context.

I'm testing with the debug builds and I don't get any asserts.  If this is wrong, what would be the proper way to use GLFW's transparent windows with bgfx?

Create GL context with GLFW, and then pass it to bgfx: https://bkaradzic.github.io/bgfx/bgfx.html#_CPPv2N4bgfx12PlatformData7contextE
But you can't use this with entry code, so you have to write your own GLFW window/input handling. Also by doing this you have to handle all context creation for other renderers.

Thanks, that worked! It seems to be working fine with the entry code with just some small changes.

Proper way to support this is to add support transparency to GL context creation. Also GLFW is only one of supported windowing/input system, this needs to work everywhere to be supported by bgfx.

I haven't looked at GLFW's source but I think it needs a combination of settings in both the window and the context to work.  I just posted the patch just in case somebody finds it useful :)


mitral valve - add synonym

Add new synonym for mitral valve to all relevant MP terms:
NEW SYN: left atrioventricular valve
NEW SYN: left AV valve
Amend definition for MP:0000286, make sure it reads better
CURRENT DEF: any structural anomaly of the valve between the left atrium and the left ventricle of the heart, and contains two cusps, the anterior cusp and the posterior cusp, attached to the outer fibrous ring (annulus)

Synonyms have been added to all relevant MP terms and the definition for MP:0000286 has been amended.


move 1.x lookup cases to tck

move 1.x lookup cases to tck

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

move 1.x cases to tck


Compare everyone's .pdf builds

Some time today (we can decide when works) we should all build the .pdf and submit them to the Google Drive. I made a compare-pdfs folder here: https://drive.google.com/drive/folders/1ufNlj8JwVRSddSjCGJJ-5Cqgu7cJE8Vn
We should agree on a commit, probably early afternoon.

Shall we shoot for 2PM, then we can make any needed adjustments so that we are all equal before sending out our draft for internal review.

Okay, I'm not committing anything more for now, so should we build and compare pdfs after we all catch up to Chris after he commits his commenting out of appendices?  Kelli and I should send this draft off to Owen ASAP.

Chris Grandin [2:30 PM]
I put a copy of my PDF on Google drive:
https://drive.google.com/drive/folders/1TUJHhLCugoabL5N8SuPvc9427kP_UppU?tid=0B5lSVg5Eq86uQllqNmdmczFVU2c
The SHA of the commit it is built from is in the filename

I have two commits in mine that others don't have. I can rebuild at the same point as everyone else if you want? What should I do?

I'll do the same - Aaron already has.

I normally compare them manually (flick back and forth between each page of two versions using Alt-tab - pretty easy to see any glaring differences.)
Kelli - merge Chris's latest and push, then upload the .pdf. We can check that any differences are due to your latest commits.

I can do the manual comparisons - someone else want to also? Doesn't take long. Hopefully it's all good (quite impressive when it is!).

Ugh - I thought Chris had merged Aaron and me in, but no. I can't compare his and mine - too much text changed. I'll try mine and Aaron's.

Mine and Chris' are different to... off by several pages due to build so must be some text differences

So far mine and Andy's looks very similar - for some reason my table of contents has an incorrect page number (correct in document and matches Andy's but wrong in table of contents - its the Assessment Section headind

Mine did the same thing.

Aaron's and mine are identical except for the TOC. I think you just didn't latex twice (or three times)  [make sure you do for final versions].

I for sure did NOT Latex multiple times.

When page numbers (or equations, figures etc.) change the second pass updates the references. I do it in a shell so I can see when it says to run again. (I think in 2017 the final version didn't quite have the citation number of pages correct for this reason [currently this is commented out because this is non-citable].

if I'm calling build() from within R when pointing to hake-assessment\doc directory, I thought that batch file was running LaTex like 3 times, maybe I have to change it to 4?

Mine and Kelli's are identical except for her new edits!
Excellent.
We can compare Chris's at some point once he's merged (he's away right now) -  Chris, merge me then checkout  bd3ac2a (my merge from yours) then compile that and submit to Google Drive.

Three minor things I spotted:

Maturity - we didn't update the ogive did we (I can clarify in two places I happened to spot)??

And the SS filenames now are full paths - I can fix.

Suggest moving the two MCMC appendices to become F (i.e. before SS files). Or even before?

no we didn't update maturity ogive this year, only updated table on the number of samples available (for some future analysis/reanalysis)
thanks
agree

re: build.doc() - looks like that should work. Three times is normally enough. I'm not quite sure what latex -synctex=1 does though in the first call. I never delete my .aux etc. files (I know Chris does).

So is this okay (it's in there but flagged): The maturity ogive was the same as that used in Edwards et al. (2018b) because the U.S. government shutdown delayed delivery of the 2018 histological samples. And I'll clarify in Table 16 caption - should it really say "The maturity ogive was determined from a subset of these samples."    Currently a little confusing.

This is what I got from Melissa Head when I asked her to update 2018 ovary samples: "I can update with preliminary information from surveys, but because of the shut down I still have not received samples back from the lab. Thus, I can’t verify exact numbers. I had hoped to complete a detailed analysis with new samples, but the shut down messed that up as well..."
And yes it should, maybe say samples through 2017 b/c we got a new one last year but not this year (good catch on that Table)

I left it b/c I thought maybe there were other years that had samples that
maybe didn't get used in the analysis ... just because they are collected
doesn't mean they were any good.
On Wed, Feb 6, 2019 at 3:38 PM Aaron Berger<EMAIL_ADDRESS>wrote:

This is what I got from Melissa Head when I asked her to update 2018 ovary
samples: "I can update with preliminary information from surveys, but
because of the shut down I still have not received samples back from the
lab. Thus, I can’t verify exact numbers. I had hoped to complete a detailed
analysis with new samples, but the shut down messed that up as well..."
And yes it should, maybe say samples through 2017 b/c we got a new one
last year but not this year (good catch on that Table)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cgrandin/hake-assessment/issues/536#issuecomment-461231966,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6xFIlB8V43HbJFyv6xiuu11240PhDtks5vK2dfgaJpZM4alrUz
.

--
Kelli Faye Johnson, PhD
Research Fish Biologist
Northwest Fisheries Science Center
National Marine Fisheries Service
2725 Montlake Boulevard East
Seattle, Washington 98112
(206) 860-2465
<EMAIL_ADDRESS>

well that's true to and I don't know for sure what was exactly used - better to be vague

Thanks. And I think last year was the first update to the ogive since Dorn and Saunders 1997. So we don't usually update every years (every couple of decades maybe)...

Going with Number of \\fishname\\ ovaries collected for histological analysis. The maturity ogive was determined from a subset of these samples (up to and including 2017) -- see \\citet{JTC2018}. Wasn't going to actually ref the last assessment, but got confusing not to.

Done.

Done.

@cgrandin   Getting back to the topic of this issue (my bad), just merge me then checkout bd3ac2a (my merge from yours) then compile that and submit to Google Drive. You can then compare Aaron or my pdf's with yours (Kelli's has only minor difference due to other commits). Ours were all good (except their TOC pages).

i fixed the issue of the wrong TOC numbering - see commit 579496e9745e34ddd967ab5423e4b1f62511782b

We just fixed the TOC issue (Chris committing). You do need four latex calls if starting from scratch - one or two is enough for me because I do it manually (and see the warnings).

We never checked Chris's .pdf but I'm pretty sure we have the same numbers, so closing this.
FYI - my bad - we could have merged his, then checked out his commit that he posted the .pdf for (it just wouldn't have any of our un-merged stuff), then checked out master to carry on....  Then we would have add identical .pdfs.....


pick off a few more emoji

Left over from #3765.

@mattbk @rohitpaulk @rorepo @kzisme @techtonik Wanna merge this one so we don't forget what it feels like to have someone else merge a PR around here? :-)

:)

Yessssssssssss!
!m @rohitpaulk :dancer:


Add WordPress as an interested organization for GSOD 2021

Add WordPress as an interested organization for Google Season of Docs 2021.

@googlebot I signed it!


Confusion regarding the NSG example screenshots

The NSG example screenshot provided, although useful, confuses people on what rules they need to configure. Specifically the rules for the intra-subnet connectivity. I have seen several NSGs that have the example address space set (<IP_ADDRESS>/24) instead of what is actually the ASE's subnet. Can we please highlight the below rules to fully showcase the address space provided is an example and that the Address should be changed to the specified address space used for that specific ASE?
Rules,
ASE-Internal-Inbound
ASE-internal-outbound

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 89142752-64bc-31c2-9189-aa2c2dcf2997
Version Independent ID: 4ef63a3f-beca-e562-5e69-3cc931bd1022
Content: Networking considerations - Azure App Service Environment
Content Source: articles/app-service/environment/network-info.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

Thanks for the question. We are currently investigating and will update you shortly.

@meepstei Thanks again for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.

Thank you. We are addressing this with an upcoming change to the documentation.
#please-close


Inquiry About Comparison with WF-VAE

Hello, I’ve been following your work, and I find it particularly interesting and helpful. May I ask two questions？

I'd like to learn more about how your work compares to the approach used in WF-VAE (https://github.com/PKU-YuanGroup/WF-VAE). Would you be willing to share some insights on this?

How about the inference speed?

Thank you for your interest in our work.

Following your advice, we have tested the open-source model of WF-VAE, and the comparison results under the same setting (causal model, video compression ratio: 4×8×8, input shape: 17×256×256,  testing data: MCL-JCV, 30 FPS
) is as follows:

Method
Param
PSNR
SSIM
LPIPS
FVD

WF-VAE-L-16chn
317M
33.76
0.870
0.091
90.8

VidTok-16chn
157M
35.04
0.942
0.047
78.9

As for the inference time, we will provide updates on it later.


The rendering of accumulated event edges crashes after a few seconds

A session  to render the events fo the DAVIS is started with the command  roslaunch dvs_renderer  davis_mono.launch.
The command below renders edges for a few seconds renders an edge map but then crashes
rosrun image_view image_view image:=/dvs_accumulated_events_edges
Followings its crash, the dvs_renderer package also crashes. I assumed it was a processing problem and hence  tried reducing the max_events parameter in the /davis_ros_driver to 100 and suppressed the OFF events. However the problem still persists

I'm also running into this issue. Has anyone been able to figure out why this is happening?


Toggle buffer only

How can I apply IlluminationToggle just in current buffer? Please.
From the doc - COMMANDS section, I tried in vain to map either globally OR buffer-range:
nnoremap <buffer> <leader>aht  <Esc>:IlluminationToggle<CR>
nnoremap          <leader>ahtg <Esc>:IlluminationToggle<CR>

Since the toggle function is (source)
fun! illuminate#toggle_illumination() abort
  if !s:enabled
    call illuminate#enable_illumination()
  else
    call illuminate#disable_illumination()
  endif
endf

...I tried to build my own mini function, but these also affect all buffers:
nnoremap <buffer> <leader>asd1 <Esc>:call illuminate#disable_illumination()<CR>
nnoremap <buffer> <leader>asd2 <Esc>:call illuminate#enable_illumination()<CR>

Thanks in advance!

You can enable and disable at a buffer level using a bang, for example
IlluminateDisable!
IlluminateEnable!
IlluminateToggle!

Without the bang will apply globally (however, any previously used bang calls will override all future global invocations).
I'm going to leave this undocumented for a bit so it can be tested.

Thanks @RRethy !! It works.
Might someone just copy-paste:
nnoremap <buffer> <leader>aht <Esc>:IlluminationToggle!<CR>:echo "---- Auto highlight wordUnderCursor toogled BUFFER (add g to map global)----"<CR>
nnoremap          <leader>ahtg <Esc>:IlluminationToggle<CR>:echo "---- Auto highlight wordUnderCursor toogled GLOBALLY (all buffers) ----"<CR>

In the mapping you don't need <buffer> since that just means "make this mapping only for this buffer", it doesn't modify the functionality of the executed command.


Print and draw ROC_curve

Python==3.6
Turi Create==5.5
model = tc.image_classifier.create(train_data)
metrics = model.evaluate(test_data)
print(metrics['accuracy']) -> 0.822
print(metrics['auc']) -> 0.906
print(metrics['roc_curve']) -> KeyError : ['roc_curve']
It had been done for a while.I can not do it for some reason.
ROC_curve can be drawn if this output can be done. Is there any other way?

@kuri54 - Thanks for reporting this issue.
It looks like this is caused by #1335. The roc_curve is still calculated by logistic regression but it is not being through.
We should get this fixed in the next release. If you can downgrade to 5.2.1, you can get the ROC Curve.

Thanks！
Looking forward to Version 5.6.

fixed via #1891


Intercom config.user.custom_data does not reflect in window.intercomSettings - users showing as Lead

Version info

intercom-rails version: 0.4.0
Rails version: 5.2.0

Expected behavior
Logged in User data should shows up
Actual behavior
We have this working for awhile but Users started turning into Leads recently. intercom_custom_data  in controller shows up as <struct user={} companines={}>
Steps to reproduce
No steps to reproduce

Seems intercom_script_tag hash overrides default, closing.


Promises always fulfilled and rejected at the same time

I have the following test
"node:": v0.10.41
"should": "^8.2.1"
"q": "^1.4.1"
Same issue on node v4.x too.
/* eslint-env node, mocha */
'use strict';
describe('Q', function() {
  var Q = require('q');
  var FulfilledPromise = function() {
    var deferred = Q.defer();
    deferred.resolve();
    return deferred.promise;
  };
  var RejectedPromise = function() {
    var deferred = Q.defer();
    deferred.reject(new Error());
    return deferred.promise;
  };
  describe("RejectedPromise#", function() {
    it('is promise', function() {
      RejectedPromise().should.be.a.Promise();
    });
    it('is fulfilled', function() {
      RejectedPromise().should.be.fulfilled();
    });
    it('should not be fulfilled', function() {
      RejectedPromise().should.not.be.fulfilled();
    });
    it('should be rejected', function() {
      RejectedPromise().should.be.rejected();
    });
    it('should not be rejected', function() {
      RejectedPromise().should.not.be.rejected();
    });
  });
  describe("FulfilledPromise#", function() {
    it('is promise', function() {
      FulfilledPromise().should.be.a.Promise();
    });
    it('is fulfilled', function() {
      FulfilledPromise().should.be.fulfilled();
    });
    it('should not be fulfilled', function() {
      FulfilledPromise().should.not.be.fulfilled();
    });
    it('should be rejected', function() {
      FulfilledPromise().should.be.rejected();
    });
    it('should not be rejected', function() {
      FulfilledPromise().should.not.be.rejected();
    });
  });
});

I get the following results,
  Q
    RejectedPromise#
      ✓ is promise
      ✓ is fulfilled -> SHOULD FAIL
      ✓ should not be fulfilled
      ✓ should be rejected
      ✓ should not be rejected -> SHOULD FAIL
    FulfilledPromise#
      ✓ is promise
      ✓ is fulfilled
      ✓ should not be fulfilled -> SHOULD FAIL
      ✓ should be rejected -> SHOULD FAIL
      ✓ should not be rejected

  10 passing (17ms)

Any insights why it always passes

Looks like I just needed to return with a promise and after that it will work.
  Q
    RejectedPromise#
      ✓ is promise
      1) is fulfilled
      ✓ should not be fulfilled
      ✓ should be rejected
      2) should not be rejected
    FulfilledPromise#
      ✓ is promise
      ✓ is fulfilled
      3) should not be fulfilled
      4) should be rejected
      ✓ should not be rejected
  6 passing (19ms)
  4 failing


Not working properly

Hey when I write different symbol's expression its not working

and the expression which is doing this issue is

but if I write it in code blocks form then it is working

Can you fix this or help me why is it doing this!
Thank you

bump!

浩瀚星河官方账号邮件7天内处理


Additional metrics to tensorboard

Hello. While using mmdet2 I wrote custom tensorboard hook which uses this metrics
'val/bbox_mAP': 'Validate/Precision total',
'val/bbox_mAP_l': 'Validate/Precision large',
'val/bbox_mAP_m': 'Validate/Precision medium',
'val/bbox_mAP_s': 'Validate/Precision small',

How can I use same metrics during evaluation to save best model weights and to look at graphs in tensorboard?

Thanks to this comment wrote my custom hook with additional metrics for validation for object detection.


Plain ~ is not supported in shell

This is because ~ has special meaning in janet - I think to fix this we may need to top level string preprocessor for the repl that implicitly converts some symbols to string form before passing it to the janet macro expander.
Probably a good use for the janet PEG module.

Alternatively, we can look at working with upstream to extend the parser api in some nice way,

A final choice is to not fix this, it is quite easy to use, but it requires users to know a bit about janet.

Won't fix for now.


Update mandatory-user-profile.md

Updated outdated URLs.
Some markdown corrections with numbered lists, they were out of order.
Took a teeny bit of liberty renaming headings.

Looks pretty good to me. I was quite pleased to see that the internal link change worked properly. I recommend using "Hide whitespace changes" (https://github.com/MicrosoftDocs/windows-itpro-docs/pull/6085/files?utf8=✓&diff=unified&w=1) to see the changes in the correct order, otherwise the changes may appear too scattered to compare the way you are used to. @JohanFreelancer9 , would you like to perform a copy review?

Looks good.

#sign-off

cc @Dansimp


Update README to reflect recent changes.

Since readme was last written the code has changed a lot, so the contents are out of date.
Update the readme overview to give the user the overview of the current state of the code in the repo, so broadly what the code in each file does.

Planner Agent Output: To update the README with an overview of the current state of the code in the improved-spork repository, follow these steps: 1. Create a new branch called 'update-readme'. 2. Delete the existing overview section in the README.md file. 3. Review the code file by file and write a new overview section in the README.md file. 4. Commit the changes to the 'update-readme' branch. 5. Create a pull request to merge the 'update-readme' branch into the main branch. Make sure to mention that the developer is a GPT-4-powered agent in the pull request description.


[App Config] Add correlation request id to bulk operations

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.

@zhoxing-ms and @yanzhudd this is ready to merge


[terra-time-input] Fixed accessibility issue

Summary

What was changed:
Fixed accessibility in AccessibleInput component.
Why it was changed:
aria-label attribute was set to undefined even if the label prop is present.
Testing

This change was tested using:

[x] WDIO
[x] Jest
[x] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-10229

Thank you for contributing to Terra.
@cerner/terra

Closing this PR.
Opening a new PR https://github.com/cerner/terra-framework/pull/2140


:session_timeout with :remember_me

Hello
I'm using 0.9.0 and added the submodules :session_timeout and :remember_me.  I want the session to expire after 60 min unless the remember_me has been used.  If remember_me is used I want to extend the session for 2 weeks.
After login I can see the session cooke and the remember_me_token and remember_me_token_expires_at are entered into the users table after login.
After the session_timeout  time has elapsed, I am prompted to login, which is wrong, since I logged in with remember_me I have shouldn't be logged out.
How can I keep the session open with remember_me and drop the session when remember_me isn't used.
I'm using the default config with a change to the session_time value
Rails.application.config.sorcery.submodules = [:core, :remember_me,:session_timeout]

Rails.application.config.sorcery.configure do |config|
 config.session_timeout = 60.minutes
end

SessionsController
def create

    @user = login(params[:email], params[:password], params[:remember_me])
    if @user
      redirect_back_or_to welcome_path
    else
      flash.now.alert = "Your email or password is invalid. Please try again."
      render :new
    end
 end

  def destroy
    logout
    redirect_to root_path, notice: "You have been logged out."
  end

Hi @cdwilhelm
I'll have some time to check it this week. Let me see what's causing the issue and if I can fix it soon, I'll get back to you later this week. In the meantime, if you have some time to dig a bit more and you find a way to fix it, let me know, I'll be grateful.

@arnvald I did spend a great deal of time studying the code to understand what I was missing in my config. I assumed I was missing something.
it seems that the session_timeout.validate_session needs a condition to skip the reset_sorsery_session if remember_me is selected for the user.
https://github.com/NoamB/sorcery/blob/master/lib/sorcery/controller/submodules/session_timeout.rb#L38-L46
If you have some guidance I can look further into it

Great, I'll check it out this weekend and I'll let you know if I have any idea on what's the best way to implement it.

Hi @cdwilhelm,
I've checked it and the change is very simple. It requires only to remove @current_user = nil from the method you mentioned. So the dirty, monkey-patching solution is to add initializer with following content:
module Sorcery
  module Controller
    module Submodules
      module SessionTimeout
        module InstanceMethods
          def validate_session
            session_to_use = Config.session_timeout_from_last_action ? session[:last_action_time] : session[:login_time]
            if session_to_use && sorcery_session_expired?(session_to_use.to_time)
              reset_sorcery_session
            else
              session[:last_action_time] = Time.now.in_time_zone
            end
          end
        end
      end
    end
  end
end

I need to yet think what to do about it in Sorcery code. I imagine people may want to work it both the way it's currently done and the way you need to make it work, so probably I'll add it to 1.0 version as a setting called remember_me_overrides_session_timeout or similar, and this setting will default to current way. I'll leave the issue open until I decide and implement it.

Thanks for the assistance with this.  I'll give the monkey patch a try this week.    Curt
  From: Grzegorz Witek<EMAIL_ADDRESS>
To: NoamB/sorcery<EMAIL_ADDRESS>Cc: Curt Wilhelm<EMAIL_ADDRESS>Sent: Sunday, February 15, 2015 10:06 AM
Subject: Re: [sorcery] :session_timeout with :remember_me (#670)
Hi @cdwilhelm,I've checked it and the change is very simple. It requires only to remove @current_user = nil from the method you mentioned. So the dirty, monkey-patching solution is to add initializer with following content:module Sorcery
module Controller
module Submodules
module SessionTimeout
module InstanceMethods
def validate_session
session_to_use = Config.session_timeout_from_last_action ? session[:last_action_time] : session[:login_time]
if session_to_use && sorcery_session_expired?(session_to_use.to_time)
reset_sorcery_session
else
session[:last_action_time] = Time.now.in_time_zone
end
end
end
end
end
end
endI need to yet think what to do about it in Sorcery code. I imagine people may want to work it both the way it's currently done and the way you need to make it work, so probably I'll add it to 1.0 version as a setting called remember_me_overrides_session_timeout or similar, and this setting will default to current way. I'll leave the issue open until I decide and implement it.—
Reply to this email directly or view it on GitHub.

This is what worked for me:
module Sorcery
  module Controller
    module Submodules
      module SessionTimeout
        module InstanceMethods
          protected
          def validate_session
            session_to_use = Sorcery::Controller::Config.session_timeout_from_last_action ? session[:last_action_time] : session[:login_time]
            if session_to_use && sorcery_session_expired?(session_to_use.to_time) && remember_me_expired?
              reset_sorcery_session
              @current_user = nil
            else
              session[:last_action_time] = Time.now.in_time_zone
            end
          end

          def remember_me_expired?
            @current_user.remember_me_token_expires_at.nil? ? true : (Time.now.in_time_zone > @current_user.remember_me_token_expires_at.to_time) if @current_user
          end
        end
      end
    end
  end
end


healthchecks?

Hi,
Is there a way to perform health checks on the controller using kubernetes probes?
Thanks

Something a bit more built-in would be ideal, but the following is a reasonable strategy:
livenessProbe:
  exec:
    command:
      - /bin/sh
      - -c
      - '! wget -q -O- localhost:3001/metrics | grep status=\"error\"'
  initialDelaySeconds: 30,
  periodSeconds: 30,

Checks the prometheus metrics to see if there have been any sync errors.

In my case the controller gets into a state where it stops reading ExternalSecret resources. Not sure more detail yet, but in the interim I'm trying the following to ensure it can still read them.
livenessProbe:
  exec:
    command:
    - /bin/sh
    - -c
    - "cd ~ && wget -O es.json --no-check-certificate --header \"Authorization: Bearer $(cat /var/run/secrets/kubernetes.io/serviceaccount/token)\" \"https://$KUBERNETES_SERVICE_HOST:$KUBERNETES_SERVICE_PORT/apis/kubernetes-client.io/v1/namespaces/default/externalsecrets\""
  periodSeconds: 30

Even more comprehensive would be to create an ExternalSecret, and then confirm it's been created, though this would require more RBAC permissions than needed, less than ideal. There's really no escaping having to look through the logs/code on this one perhaps :)

Thanks @timmyers.
Would we want to restart the pod if there are sync errors? Doesn't seem like it's the right healthcheck to perform.

It's definitely not ideal and I can think of cases it wouldn't be what you want.  For our set-up though, generally there are 0 sync errors unless something seems wrong with the pod and all of its communication is failing. A restart seems to fix it, so this might be better than no health check.

Agreed with @timmyers -- we also have syncing stop occurring without producing any errors in the logs, and a kubectl rollout restart kubernetes-external-secrets magically fixes it. I've tried the following and so far so good, but @timmyers's solution seems usable too, albeit both are of course less ideal than something more built-in.
livenessProbe:
  exec:
    command:
    - /bin/sh
    - -c
    - "cd ~ && wget -O es.json --no-check-certificate --header \"Authorization: Bearer $(cat /var/run/secrets/kubernetes.io/serviceaccount/token)\" \"https://$KUBERNETES_SERVICE_HOST:$KUBERNETES_SERVICE_PORT/apis/kubernetes-client.io/v1/namespaces/default/externalsecrets\""
  periodSeconds: 30

Thanks guys, i'll implement the probe suggested by @timmyers until a proper healthcheck is added.

@timmyers @aramse do you have a suggestion for a readiness probe as well for a proper rolling update?

I've ended up removed the livenessProbe right away as it was restarting the container due to errors that are not related to the pod's communications. The container can function as expected and throw errors due to a variety of reasons such as lack of permissions to a specific secret.

I would have readiness probe just be the same check as liveness in this case.
And that's unfortunate :( I have been pretty good with my probe so far (API call to get ExternalSecrets in the default namespace), but I'm still not sure if this accounts for all bad states that this controller can get into.

@aramse so far I have only tried the solution offered by @timmyers.
Can you please elaborate on your solution for the probe?

It's just a GET against the Kubernetes API to retrieve ExternalSecret resources from the default namespace. It's the same effect as kubectl get externalsecrets.
Again, not saying this is a comprehensive fix by any means, but in my case the controller gets into a state where it's unable to detect new ExternalSecret resources, and it's magically fixed by a restart, so this should hopefully cover that at least.

I didn't test wget liveness probe and i don't think it actually solves the problem here because the open tcp connection from the watch request is being dropped on a different network hop and checking if we can open a new connection does not detect that particular issue. The livenessprobe should just work :tm:.
I'd propose to have a /healthz http endpoint that checks if 1) the reconciliation loop is running and 2) we're able to pull ExternalSecrets from the kube-apiserver.


bug in the config of chairs_64

translation range is set to zero in chairs_64.yaml
but translation is involved in chairs' default render output (they can't do any translation at all)

You can just ignore these outputs then (only relevant for datasets which use a translation range).


various updates

buildToolsVersion to 28, alongside libraries
updated dependencies
java 1.8 compatibility
gradle to 4.10.2

etc

now outdated tbh

I am sorry I couldn't find tim to respond to this. But at the moment I am really busy with university.
Sorry😓!


Feature request: Custom image center

Another feature that I think would be helpful (although probably not easy to implement): being able to specify one point that should be as close to the centre of the cropped thumbnail as possible.
Depicted here:
http://img88.imageshack.us/img88/8151/kittehc.png
Being able to graphically pick one in the admin panel would require some quite involved JavaScript magic, but how about two fields (X and Y coordinates) that can take either pixels or percentages?

This issue should be outdated by now. I'm closing it.


Export Locator

by.cssContainingText returns a ProtractorLocator, but Locator couldn't be imported in a TS file.

@barrtender
I'm seeing you are doing all kind of commits on this PR containing comments and not and no new functionality. Is there a reason for doing that?

@wswebcreation
Yeah I couldn't figure out how to get the circleci to run again. It keeps timing out. Looking at a couple other pull requests it looks like it's timing out for them too. Is this standard, and if so is there a better way for me to rerun to try to get it to not time out?
Thanks,
Eric

@vikerman and @cnishina
Can you see what's happening on the CircleCI. I can't figure this out and I don't have rights to restart them

@vikerman
Tnx for merging, but what about a new release ;-)


github action to convert images to webp where it makes sense

wrote a simple script to accompany the thing, once it's fine tuned a bit it should prob be a separate installable action.
let's see if it works first, a bunch of stuff is different on linux things

Proof of concept why we need to do this logic instead of just looping naïvely:
$ for i in $(git diff-tree --no-commit-id --name-only -r HEAD); do echo $i; done
bar
2
$ while read -r -d '' file; do echo "$file"; done < <(git diff-tree --no-commit-id --name-only -r HEAD -z)
bar 2


Auto sensor reading after pixhawk startup

Hi guys is there any method for sending messages through mavlink console while pixhawk startup or when pixhawk armed.
ı have a sensor called usharp patch from aerotenna like ulanding radar distance sensor ı am reading data when ı write "usharp_patch start" to the mavlink console and watch the data with analyze section. So ı am wondering can ı send that "usharp_start" message to mavlink console when ı power the pixhawk?
Well, maybe changing flight mode features will do that but ı dont know how to change flight mode features either.
btw sensor's driver is uploaded to the pixhawk but ı dont know who  did that ı'll publish the driver as soon as find the driver file

Do I understand correctly that you just want to do a nsh command on startup to start a sensor?
If you're already compiling your own code, you can add the command to the startup here:
https://github.com/PX4/Firmware/blob/master/ROMFS/px4fmu_common/init.d/rcS

Yes just try to add a new command. Normally I write "usharp_patch start" command manually via mavlink console in qground control.What I want is actually this starting process of the sensor triggered with startup like the compass or gyro (sensor dont need calibration btw)
Thank a lot for your help ı will examine your link

I'm closing this as a solution has been posted, please use discuss.px4.io if you need further help.

Also see https://dev.px4.io/v1.9.0/en/concept/system_startup.html


Documentation: Average & Median (#160)

*Added documentation of average
*Added documentation of median
Do the checklist before submitting the PR:

[:heavy_check_mark:] Have you read the guidelines mentioned in CONTRIBUTING.md?
[:heavy_check_mark:] Have you squashed your commits?

Q: What version of Node.js you've used in the project? (e.g. Node v10.11.0)
A:v11.10.1
Q: Mention the Issue Number! (e.g. Fixed #8)
A:#160

Give additional information regarding the PR below:

Codecov Report

Merging #162 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #162   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          77     77
  Lines        1301   1301
=====================================
  Hits         1301   1301

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6a44802...bbc18dd. Read the comment docs.


@cds/core Tag with Badge not displaying correctly (Angular)

Describe the bug
A Tag component containing a Badge component puts the Tag text off-center. The Badge also appears to be shifted out of place.
Screenshot:

How to reproduce

Made a new Angular project with the CLI
Added Clarity Core with ng add @cds/angular
Added this html in the app component:

<cds-tag readonly>This is a test<cds-badge>1</cds-badge></cds-tag>

Expected behavior
Expected the Tag with a Badge to look like it does in the examples.
Versions
Clarity project:

[x] Clarity Core
[ ] Clarity Angular/UI

Clarity version:
v5.5.4
Framework:

[x] Angular
[ ] React
[ ] Vue
[ ] Other:

Framework version:
Angular 12.2.0
Device:

OS: MacOS
Browser: Chrome
Version: 93

Additional notes
Had some trouble getting @cds/angular working on Stackblitz, kept getting "Unexpected token 'export'" from the @cds/core package. Sorry for the inconvenience of no Stackblitz example.

Hi Connor, sorry about the stackblitz trouble. We are aware of it but don't have a great workaround atm.
FYI - you can also find started specifically for core here: https://cds.wtf
I made a quick example with just the html posted in the issue report but I don't see the same issue. It it possible there is something else affecting the element in the image?
https://stackblitz.com/edit/http-server-gtxmbu?file=src/index.html

@hippee-lee Thank you for the stackblitz starters, was able to use it to reproduce the issue here:
https://stackblitz.com/edit/node-5qeujw?file=src/app/app.component.html
It seems to me that the tag + badge behave differently in Angular.
I tried to traverse the DOM and see if any of the CSS was different than a non-Angular tag + badge, but I couldn't find any discrepancies.
I am not sure what else it could be, but it's frustrating lol.

@hippee-lee Thought I should try looking into this again, and I think I see what's going on here.
When a cds-badge element is nested in a cds-tag, the cds-badge should be getting the slot="tag-badge" attribute so that it goes in the appropriate slot.
However, it seems that in Angular, that slot="tag-badge" attribute is not being added to the tag-badge element, therefore, the tag-badge element lands in the tag-content slot, and not the tag-badge slot.

One more note: It also appears that this is a problem with nesting a cds-icon inside a cds-tag. The icon should get the attribute slot="tag-icon" but it does not.
I wonder, could there be more uses of slots across cds/core that might be broken in Angular?


DEFAULTED_ON_CREATE not supported in alternate testing DB?

Hi!
I've successfully set up an alternate testing DB with SQLite as instructed in the readme, however when running my tests, I get the following error:
django.db.utils.InterfaceError: Error binding parameter 1 - probably unsupported type

This appears to come from a field I have defined as:
is_active = models.BooleanField(custom=True,
                                db_column='Is_Active__c',
                                default=models.DEFAULTED_ON_CREATE)

A quick look at the execute method in django/db/backends/sqlite3/base.py reveals that the Is_Active__c param that django is trying to save is:
<salesforce.backend.operations.DefaultedOnCreate object at 0x10f233c50> ... instead of True/False. Changing that param value to either True or False while debugging does indeed solve the problem.
Is there a known issue working with DEFAULTED_ON_CREATE in alternate DBs? Am I missing some kind of configuration?
Thanks!

A similar more complicated issue with primary keys #231 has been fixed so that any database can be used with less restrictions not only for test but also for copy and use it as a live backup of Salesforce. There is no difference between run-time and test, but a difference between Salesforce and other database backends. The problem was that Field methods receive either connection and value or instance and value, but no method gets both information. If the value is None than these methods of SomeField are skipped.
A general solution of DEFAULTED_ON_CREATE is more complicated than the two default values. The value is not known until the record is refreshed from the database. If the value can be set to None later, then it shouldn't be set again to the default value. Your examples for the most frequent problems are fortunately easier and it works for you.
One my objection is that people probably need to test a part also on Salesforce db. The condition settings.ENV == 'test' is more related to the backend than to test versus run-time. Another problem of your approach is that makemigrations would also depend on the current value of ENV variable. That will be a mess and not for everybody.
Two solutions are possible:
A) Added an empty customizable method .before_save(self, value, is_salesforce, is_creating, connection, instance) to the base SfField class. That method will be called automatically before save and bulk_create to solve null values. Important parameters are value, is_salesforce, is_creating to simplify the logic, but the original full parameters connection, instance can be are also available. Terrible solution?
B) It seems easier to emulate these simple cases similarly to Salesforce at the database level:
CREATE TABLE ...
IsActive BOOLEAN DEFAULT(TRUE),
CreatedDate TIMESTAMP  DEFAULT CURRENT_TIMESTAMP,

This will be created by makemigrations and internal migrate from
is_active = BooleanField(...default=models.DEFAULTED_ON_CREATE('TRUE'))
created_date = DateTimeField(default=models.DEFAULTED_ON_CREATE('CURRENT_TIMESTAMP'),
                             sf_read_only=models.READ_ONLY)

Both require come non trivial code, but B) can be easier explained how to use it.

The right solution should be simpler then A), B) or your code.
The algorithm of inspectdb command was stable long time and it ignored default values that were useful only with non-Salesforce databases.
I wrote a patch for inspectdb

Support for introspection with DefaultedOnCreate(value).  100cc68

to export more information, e.g.
    default=models.DefaultedOnCreate(False)`,
    default=models.DefaultedOnCreate('NotSeen'), choices=[('NotSeen', 'Not Seen'), ...],

Nothing is changed in the backend implementation yet, but you can still simplify your code by:
class TestableBooleanField(models.BooleanField):
    def __init__(self, **kwargs):
        if settings.ENV == 'test' and isinstance(kwargs['default']), DefaultedOnCreate):
            kwargs['default'] = kwargs['default'].arg
        super(TestableBooleanField, self).__init__(default=default, **kwargs)

(not fixed, but a progress)

A problem is also in Salesforce with objects that were just created if they are saved once more without previous refreshing fields that were assigned by Salesforce defaults. We can try a special request that writes some fields and reads some fields in the same request. Useful for those fields with sf_read_only attribute (e.g. a formula that depends on ohter fields) or with DefaultedOnCreate

No field on the Salesforce platform expects a default value from the application.

Most problems are already solved by the PR for version 1.0.
Instead of your proposal testing_default a parameter for DefaultedOnCreate() is implemented, e.g.:
from django.utils.timezone import now

class ...:
    is_active = models.BooleanField(default=models.DefaultedOnCreate(True))
    created_date = models.DateTimeField(default=models.DefaultedOnCreate(now),
                                        sf_read_only=models.READ_ONLY)

A documentation for it is in wiki Introspection and Special Attributes of Fields.
Missing part: tests (a new test project that runs on Salesforce then on 'default' and possibly also with and without migrations)


feat: only movies collection shown for mock DB A/B

Description
This PR modifies existing getStructure API call so that for mock DB movies, only movies collection will be shown for users who have ab_mock_mongo_schema_enabled flag enabled. This is an experimental feature, where in we want to check the relevance of mock DBs. Hence some users will only see movies collection where as others will continue to see all the collections.
PR fixes following issue(s)
Fixes #26937

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

New feature (non-breaking change which adds functionality)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/build-deploy-preview

/ok-to-test

/build-deploy-preview

/ok-to-test

/build-deploy-preview

/ok-to-test


(GH-30) Add ability to compare meta information of found binaries

Description

This pull requests adds the ability to store and compare basic information of the included binary files in each package version.
Related Issue

fixes #30
Motivation and Context

To be able to easier notice the changes regarding binary files between each version.
How Has This Been Tested?

Currently only been tested in a remote devcontainer in vscode.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation. (maybe?)
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes. (not added yet, need help to figure out how to test the changes)
[x] All new and existing tests passed.

Additional
This pull request is currently a WIP, unit tests have not yet been added nor completely tested appropriately.
Wanted to get some feedback on the current implementation before going any further with this one.
example output:
PS /workspaces/chocodiff> cat /tmp/chocodiff/7zip.install.18.6/binary-data.txt

Name                           Value
----                           -----
path                           ./tools/7zip_x32.exe
checksum                       7A2E78C5C2EBC072088B7D8DFF6E00D414E7084C97C2C730CC4C45905668A8F3
CompanyName
fileVersion
productVersion
path                           ./tools/7zip_x64.exe
checksum                       18D0BF6A9A2BC4DD0779B5FCEFE0AA893F938419D755FE9BC6DBFA50D94BD488
CompanyName
fileVersion
productVersion

Codecov Report

Merging #35 into master will decrease coverage by 7.40%.
The diff coverage is 17.64%.

@@             Coverage Diff             @@
##            master      #35      +/-   ##
===========================================
- Coverage   100.00%   92.59%   -7.41%
===========================================
  Files           14       14
  Lines          173      189      +16
===========================================
+ Hits           173      175       +2
- Misses           0       14      +14

Impacted Files
Coverage Δ

...ocolatey-diff/Public/Get-ChocolateyPackageDiff.ps1
82.71% <17.64%> (-17.29%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 63ce723...89b6799. Read the comment docs.

@mkevenaar would you have the possibility to take a look at the current implementation in this draft?
It is not completely ready yet, but I would like to get some feedback before going any further with this.
Sorry about the changes to the formatting, this was a mistake due to automatic formatting in vscode. I will revert those changes when the PR is ready

I have moved most of the relevant code to a new function.
Still need to figure out how to do the unit tests (and especially the mocking).


TypeError: winston.Logger is not a constructor

I think that this because since winston 3.0.0 the way of building the logger changed.

already being discussed in https://github.com/bithavoc/express-winston/issues/175


Translate Jockey

That would be great if the app were also available in several languages

Is there a specific language or set of languages that you'd like translations for? Jockey is already translated into English, Spanish, and Dutch, so technically this would already be complete 😉.
If you'd like to help out with translations, that's awesome, and I can give you some tips to get started.

I would like to translate Jockey into German.
the question is, how do i do that? is it transifex, crowdin, weblate or is there another platform or the texts to translate? love thanks in advance

Jockey doesn't use any services for translation at the moment, but that's something I can look into. There's been one contributed translation (#394), where the translator added translations in the code itself and then opened a pull request.
If you're comfortable with Android Studio, you can absolutely go the same route. Otherwise I can look into setting up a translation service for folks to contribute translations. I saw that Transifex is free for open source, but do you have any opinions between the services you listed?

https://weblate.org/de/hosting/
weblate you can Self-hosted  and it is libre.
https://hosted.weblate.org/
its easy to translate
https://www.transifex.com/
and
https://crowdin.com/
are two another translation services, but not libre
i don't have an android studio, because i'm not a programmer. my wish is simple, the jockey is available in several languages. and german is my native language.
are the sentences or words you need to translate online somewhere?

Hey, sorry for the delay here. I've setup a Transifex project: transifex.com/marverenic/jockey/dashboard/. Shoot a request over and I can add you to the project. If this works well then I'll add more formal instructions for folks that want to translate in the future.

thanks, that worked out I'm the Acrylic Boy there (the name mondstern was already on and I like to paint with acrylic)


numeric_state trigger with attribtes

Home Assistant release (hass --version):
0.19.4
Python release (python3 --version):
Python 3.5.1
Component/platform:
numeric_state trigger and attributes
Description of problem:
It is not possible to use the numeric_state trigger together with an attribute of something. For e.g.
automation:
  - alias: "dryer"
    trigger:
      platform: numeric_state
      entity_id: switch.dryer
      value_template: "{{ states.switch.dryer.attributes.current_power_mwh }}"
      below: 100
      ...

This trigger will never fire.
My guess is, that the value_template always returns a string and this can not be compared to the number in below.
A workaround is, to use a binary_sensor where the comparison can be done within the value_template field.
binary_sensor:
  platform: template
  sensors:
    dryer_running:
      value_template: '{{ states.switch.dryer.attributes.current_power_mwh > 100}}'
      friendly_name: 'Dryer running'

and then have an automation like:
automation:
  - alias: "dryer"
    trigger:
      platform: state
      entity_id: binary_sensor.dryer_running
      from: "on"
      to: "off"
      ...

Can confirm:
alias: test123 trigger:   platform: numeric_state   entity_id: sensor.inlaat   value_template: "{{ states.sensor.inlaat.state }}"   below: 20
is never fired.
while
alias: test123 trigger:   platform: numeric_state   entity_id: sensor.inlaat   below: 20
this does trigger.

Could you try adding the word float at the end? I believe that tries to convert the value to a number before comparison.
automation:
  - alias: "dryer"
    trigger:
      platform: numeric_state
      entity_id: switch.dryer
      value_template: "{{ states.switch.dryer.attributes.current_power_mwh | float }}"
      below: 100

@mib2011 solution seems to work. I would consider this solved then.


How to train other datasets with KAN

May I ask, if I want to train and test other datasets on KAN, how should I implement it?Can you provide code support?

To use KANs in other datasets, you can use the KAN model like a layer. The forward method is defined within the KAN module, so you can pass the input through the KAN layer to get the output you specify.
However, values such as l1 regulation may require additional work as you need to add them manually. In my case, I used sklearn's "make_classification" dataset to train binary classification using 8 dimensions of data, and after configuring the dataset appropriately, I used the
"class Model(nn.Module):
def init(self):
super(Model, self).init()
self.KAN = KAN([PCA_dim,PCA_dim*2-1,1])
def forward(self, x):
output = self.KAN(x)
output = nn.Sigmoid()(output)
output = torch.squeeze(output)
return output"
After constructing these models, I put the parameters into the optimizer and trained it, and the training went fine.


[Bug] Button Widget - Evaluated value is 'undefined' for Button style JS

Description
Release frozen - It is observed that evaluated value is 'undefined' for button style JS
Expected Result:
Evaluated value should display the actual evaluated value
Steps to reproduce the behaviour:

Launch App smith app in the release frozen environment
Drag and Drop button widget
Click on button style JS and observe the evaluated value

Important Details

Version: [11.3]
OS: [MacOS]
Browser [Chrome, Safari]
Environment [release,Release frozen]

Button widget - Button style JS

List widget - Zoom JS

@ajinkyakulkarni we need your help here, This is not related to the widget validation changes and exists from before.
@YogeshJayaseelan can you please attach a screenshot from prod as well?

@somangshu @ajinkyakulkarni Adding screenshot for Prod

button widget - Button style JS

2.List widget - Image - Zoom Js


Interactions config

Codecov Report

Merging #470 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #470   +/-   ##
=======================================
  Coverage   79.97%   79.97%
=======================================
  Files         108      108
  Lines        3361     3361
  Branches       73       73
=======================================
  Hits         2688     2688
  Misses        673      673

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2c43e81...0d2d07a. Read the comment docs.


Refactor to avoid code repetition in psitest_library.jl

The psitest_library.jl file is rather repetitive. In particular, the handling of the add_forecasts flag is very similar across different systems, sometimes involving identical blocks of code.

As a concrete example, the exact block
for t in 1:2
    ini_time = TimeSeries.timestamp(load_timeseries_DA[t][ix])[1]
    forecast_data[ini_time] = load_timeseries_DA[t][ix]
end

appears fourteen times, plus another seven for the same thing without prefixing timestamp.

Another concrete example: search for PSY.set_variable_cost!.

ini_time = TimeSeries.timestamp(ORDC_cost_ts[t])[1]


Scroll

Description ✏
Features:

Auto scrolling
Ability for the user to stop auto scrolling
Ability to go back to auto scrolling by scrolling down, if output is still being rendered.
Scroll to bottom button (only shows when the content is not already scrolled to the bottom)
Fixed input box at the bottom after initial first prompt and enter.
Fixed indexing progress bar at the bottom.
Fixed New Session/Last Session buttons at the bottom
Added a fix to remove scroll bar buttons on StyledMarkDownPreview
Fixed model dropdown when the chat input is at the bottom
Fixed Add Context dropdown user experience (this makes it so it stays inside the container and doesn't create unnecessary scrollbars and overflow
Miscellaneous checks for whether the content in the sidebar has scrollable content, whether the user is scrolling, and other user interactions.

What changed? Feel free to be brief.

Bullet points are helpful.
Screenshots are helpful (if applicable).

Checklist ✅

[ ] I have added screenshots (if UI changes are present).
[ ] I have done a self-review of my code.
[ ] I have manually tested my code (if applicable).

@jpan8866 @Fryingpannn @nang-dev - There is a new PR that will replace this one: https://github.com/trypear/pearai-submodule/pull/177

@jpan8866 - This PR can be closed.  It was replaced by https://github.com/trypear/pearai-submodule/pull/214


fix: Make unification logic less strict

The Plus constraint has up till now been too strict in extension unification. So far we have been deriving things like the following:
a := Plus("C", b)
a := {"A", "B", "C"}
implies
b := {"A", "B"}

(as in minus_test, which this PR removes)
However, plus should be meant as the union of the the singleton set that it specifies with the extension set of another metavariable. Hence in the above example the solution for b could be either {"A", "B"} or {"A", "B", "C"}.
This means that if we have chains of circuit operations which all add the "quantum" resource, they can all be represented as Plus constraints

As it stands, this PR isn't doing anything - you are removing a test OK, but what about adding one of something that you couldn't verify before?? I see #539 but is that test passing already??

Potential improvement: we could assert that if the node is a Lift node, then it generates a "greater than" Plus constraint and otherwise generates a "greater than or equal" Plus constraint. What do you think, @acl-cqc ?

Good question. ISTR this relates to the issues Alex Rice had with resource inference in Tierkreis too. I can see a few possibilities.

As you suggest, keep lift nodes generating an input-does-not-contain constraint. I think this might be a useful thing to do - if nothing need be added, we don't need a lift node. Where else do we generate "greater than" Plus constraints atm, and should those be "strictly equal"?

This may lead to problems with substitution of variables - i.e. lift nodes disappear when graphs are moved into new contexts (perhaps this will only happen during Tierkreis execution and we won't see it yet?). If so, it might help to specify that every Input node has empty extensions; the containing DFG node then takes a (non-disjoint, greater-than-or-equal) union of its inputs with the delta of the containing graph. (This might be a good idea anyway).

Drop Lift nodes. What if we just say, the input extensions of every node must be exactly equal to the union of the output extensions of every predecessor.

As it stands, this PR isn't doing anything - you are removing a test OK, but what about adding one of something that you couldn't verify before?? I see #539 but is that test passing already??

#539 was passing on main by mistake - the PR now shows that the test is failing on main, and that same commit has been added to this branch (and the test now passes.)

As you suggest, keep lift nodes generating an input-does-not-contain constraint. I think this might be a useful thing to do - if nothing need be added, we don't need a lift node. Where else do we generate "greater than" Plus constraints atm, and should those be "strictly equal"?

Before this PR we only generated "strictly greater than" constraints, and following this PR we never generate such constraints.

This may lead to problems with substitution of variables - i.e. lift nodes disappear when graphs are moved into new contexts (perhaps this will only happen during Tierkreis execution and we won't see it yet?). If so, it might help to specify that every Input node has empty extensions; the containing DFG node then takes a (non-disjoint, greater-than-or-equal) union of its inputs with the delta of the containing graph. (This might be a good idea anyway).

Hmm, good point about recontextualising graphs, but i think we can just ignore lift nodes in that context and run inference to re-add them where necessary (once we're adding lift nodes automatically)

Drop Lift nodes. What if we just say, the input extensions of every node must be exactly equal to the union of the output extensions of every predecessor.

This is an option, but definitely one for another PR...


Restarting the container exiting the sql edge

2024-11-24 19:03:19 /usr/bin/find: '/proc/26/task/148/fdinfo': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/task/149/fdinfo': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/task/150/fdinfo': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/task/151/fdinfo': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/task/152/fdinfo': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/task/153/fdinfo': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/task/154/fdinfo': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/task/155/fdinfo': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/map_files': Permission denied
2024-11-24 19:03:19 /usr/bin/find: '/proc/26/fdinfo': Permission denied
2024-11-24 19:03:19 dmesg: read kernel buffer failed: Operation not permitted
2024-11-24 19:03:19 /usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory
2024-11-24 19:03:19 /usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory
2024-11-24 19:03:20 2024/11/24 13:33:20 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp [::1]:1431: connect: connection refused, will reattempt connection.
2024-11-24 19:03:19 Sun Nov 24 13:33:19 UTC 2024 Capturing program information
2024-11-24 19:03:19 Dump already generated: /var/opt/mssql/log/core.sqlservr.11_24_2024_13_33_18.26, moving to /var/opt/mssql/log/core.sqlservr.26.temp/core.sqlservr.26.gdmp
2024-11-24 19:03:19 Moving logs to /var/opt/mssql/log/core.sqlservr.26.temp/log/paldumper-debug.log
2024-11-24 19:03:19 Sun Nov 24 13:33:19 UTC 2024 Capturing program binaries
2024-11-24 19:03:20 Sun Nov 24 13:33:20 UTC 2024 Not compressing the dump files, moving instead to: /var/opt/mssql/log/core.sqlservr.11_24_2024_13_33_19.26.d
(.venv) thunder@thunderbook service_bus_emulator % docker-compose up -d
[+] Running 3/3
 ✔ Network microsoft-azure-servicebus-emulator_sb-emulator  Created                                                                                0.0s
 ✔ Container sqledge                                        Started                                                                                0.2s
 ✔ Container servicebus-emulator                            Started                                                                                0.3s
(.venv) thunder@thunderbook service_bus_emulator % docker-compose stop
[+] Stopping 2/1
 ✔ Container servicebus-emulator  Stopped                                                                                0.1s
 ✔ Container sqledge              Stopped                                                                                0.0s
(.venv) thunder@thunderbook service_bus_emulator % docker-compose up -d
[+] Running 2/2
 ✔ Container sqledge              Started                                                                                0.1s
 ✔ Container servicebus-emulator  Started                                                                                0.2

name: microsoft-azure-servicebus-emulator
services:
  emulator:
    container_name: "servicebus-emulator"
    image: mcr.microsoft.com/azure-messaging/servicebus-emulator:latest
    volumes:
      - "./config.json:/ServiceBus_Emulator/ConfigFiles/Config.json"
    ports:
      - "5672:5672"
    environment:
      SQL_SERVER: sqledge
      MSSQL_SA_PASSWORD: "MyPassword$6783!"
      ACCEPT_EULA: "Y"
    depends_on:
      - sqledge
    networks:
      sb-emulator:
        aliases:
          - "sb-emulator"
  sqledge:
        container_name: "sqledge"
        image: "mcr.microsoft.com/azure-sql-edge:latest"
        networks:
          sb-emulator:
            aliases:
              - "sqledge"
        environment:
          ACCEPT_EULA: "Y"
          MSSQL_SA_PASSWORD: "MyPassword$6783!"
networks:
  sb-emulator:

@thunder-007;
Few additional details:
Platform : Mac/Windows/Linux
Architecture : arm64/amd64
You are likely running into: https://github.com/docker/for-mac/issues/7368
Recycling the containers should help here.

I'm using mac maybe that explains thank @krishankumar95


Add examples for Datagrid headers as accordions

Enhancement to Datagrid table headers
Brief description

... accordions can help to expand and collapse a table. In that case we use accordions in front of the table title. By default, we recommend to expand all tables.

Details
Link to design
Links to other materials
See accordions from Carbon.
Design maintainer(s)

Ashley Bock

Tasks
Before starting work on this epic, please review and complete the following.

[ ] Initial review of design/existing code

Working in Carbon for IBM Products package

[ ] Have you reviewed our
contribution guidelines?
[ ] Have you noted our
code guidelines?
[ ] Did you use the CLI to scaffold your new component?

### Tasks
- [ ] Add table header story using accordions

We've been investigating TanStack Table, a third-party, open-source offering, which provides extensive data table capabilities surpassing what our Carbon Datagrid offers. It provides much more flexibility and customization. TanStack Table is headless which means it can easily be added alongside Datagrid component in your product or application. The benefits of more flexibility for product teams and less maintenance for Carbon makes it a win win. Lastly, it is available in multiple frameworks including React and Web Component so it provides an option to non-React product teams.
For these reasons, we have decided to transition from building our own custom table component to using an example-based approach with TanStack Table. Datagrid will still exist in our library for existing teams but we are announcing the deprecation* of the Datagrid component in v2.54.0 release so teams can begin to work through the transition. Details about how to use both Datagrid and TanStack together can be found here.
*Deprecation means that no new features will be added however sev 1 and sev 2 bugs will be supported.


raycast(3d) does not does not appear to be constant

I made a demo showcasing how to hide nodes obstructing your view utilizing raycasts. With no movement taking place, raycast will alternate between colliding and not colliding super fast. The project in the demo I'm linking will showcase this perfectly. https://github.com/oxrock/Godot-camera-raycasting-demo  By default, player.gd is loaded on the player node. That is my workaround attempt. Load player_OLD.gd on the player node for the pure spazzy experience.

OK, apparently the problem is that raycast isn't colliding with hidden bodies and that was causing the flickering in my demo. Will remake issue with proper info.


Merging a default value overwrites the property

It should use the value set on the existing builder.
I'm not sure how to distinguish the default value (set in the Builder constructor) from an explicit value (set anywhere else). Maybe count the # of times it's set and compare that to a newly-made builder?

I've decided to simply skip values that match the default, as determined by creating a fresh builder. Attempting to keep track of how many times the value is set, thus creating a distinction between "left at the default" and "explicitly set to the default", is just going to confuse.


[Event Request] Table 5612 "FA Depreciation Book" - OnAfterCalcDeprPeriod

Hi, would it be possible to get an event OnAfterCalcDeprPeriod in table 5612 (FA Depreciation Book), like this:
  procedure CalcDeprPeriod()
  var
      DeprBook2: Record "Depreciation Book";
  begin
      if "Depreciation Starting Date" = 0D then begin
          "Depreciation Ending Date" := 0D;
          "No. of Depreciation Years" := 0;
          "No. of Depreciation Months" := 0;
      end;
      if ("Depreciation Starting Date" = 0D) or ("Depreciation Ending Date" = 0D) then begin
          "No. of Depreciation Years" := 0;
          "No. of Depreciation Months" := 0;
      end else begin
          if "Depreciation Starting Date" > "Depreciation Ending Date" then
              Error(
                Text002,
                FieldCaption("Depreciation Starting Date"), FieldCaption("Depreciation Ending Date"));
          DeprBook2.Get("Depreciation Book Code");
          if DeprBook2."Fiscal Year 365 Days" then begin
              "No. of Depreciation Months" := 0;
              "No. of Depreciation Years" := 0;
          end;
          if not DeprBook2."Fiscal Year 365 Days" then begin
              "No. of Depreciation Months" :=
                DepreciationCalc.DeprDays("Depreciation Starting Date", "Depreciation Ending Date", false) / 30;
              "No. of Depreciation Months" := Round("No. of Depreciation Months", 0.00000001);
              "No. of Depreciation Years" := Round("No. of Depreciation Months" / 12, 0.00000001);
          end;
          "Straight-Line %" := 0;
          "Fixed Depr. Amount" := 0;
      end;

      OnAfterCalcDeprPeriod(Rec);
  end;

  [IntegrationEvent(false, false)]
  local procedure OnAfterCalcDeprPeriod(var FADepreciationBook: Record "FA Depreciation Book");
  begin
  end;

Thanks!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Pacakge client_golang v1.11.0 has known vulnerabilities (CVE-2022-216…

…98). Upgrading to fixed version 1.11.1
Description
Starboard v0.14.1 has known vulnerabilities in package prometheus/cleint_golang v1.11.0 (CVE-2022-21698). Upgraded to v1.11.1
Checklist

[x] I've read the guidelines for contributing to this repository.
[x] I've added tests that prove my fix is effective or that my feature works.
[x] I've updated the documentation with the relevant information (if needed).
[x] I've added usage information (if the PR introduces new options)
[x] I've included a "before" and "after" example to the description (if the PR is a user interface change).

Thank you for working on this PR @sm171190 We have already released v0.15.2, that is using github.com/prometheus/client_golang v1.12.1, and we are not going to patch and release v0.14.2.


xdp sniffer has interface name hardcoded

https://github.com/dmachard/go-dnscollector/blob/da8c5ecab45cfcb11ecbf2d55fc8392b4f6f4614/collectors/sniffer_xdp.go#L114
Was trying to use the xdp sniffer, but kept running into errors like this:
ERROR: 2023/06/09 12:51:16.565618 [xdp] collector=xdp - lookup network iface: route ip+net: no such network interface
I suspect because the interface name is hard-coded here.

Thank you for reporting this error.
The fix will be included in the next version


[5.8] Add assertSessionHasInput to TestResponse

This adds an assertSessionHasInput() helper method to the TestReponse class. Inline with the other session assertions, it accepts an array or a key value pair to verify exists in the flashed session array input.
Although you can test this with the available assertions, this new assertion avoids writing brittle tests which rely on internal framework values like the _old_input key.
$response->assertSessionHas('_old_input', [
    'connection_id' => $connection->id,
    'repository' => $repository,
    'source_branch' => $branch,
]);

Instead, you can now write:
$response->assertSessionHasInput([
    'connection_id' => $connection->id,
    'repository' => $repository,
    'source_branch' => $branch,
]);

If merged, I will submit a PR to update the docs as well by adding this to the list of Available Assertions.

I think it would be useful if the assertions prints the actual old input when the assertion fails, similar to how it happens in this pr

I'm not sure the difference in the output this would have. Maybe you could share the suggested code or could PR it if this were merged.


Add ability to provide custom state_id prefixes to meltano run

One thing that was cut late in development when adding incremental job support to meltano run was the ability to add a custom prefix to the auto generated job (now state) names: https://gitlab.com/meltano/meltano/-/merge_requests/2544#note_855957749

I think we've agreed on this already but just want to reiterate given that we've just logged ADR: Refactor/rename "job_id" as "state-id" (#3290 - closed), it is probably best to try to avoid user config/override for the state_id_prefix or job_id_prefix. Just for the reason that if we allow them to configure the naming convention, and then we update what it is called, that will create a breaking change which I think it's best to avoid.

Now that the job -> state transition work has basically wrapped up we could revisit adding this.
@tayloramurphy fwiw this is a pretty easy-peasy change on the dev side. If only configurable as a cli arg weights probably as low as a 2, but if we want to also support this as a per env meltano.yml option than most likely more realistically a weight of 4.

+1 on this. At the moment, we are creating a temporary environment per (our concept of a) pipeline as a workaround.
MELTANO_ENVIRONMENT=<pipeline_id>
meltano add environment "$MELTANO_ENVIRONMENT"

export MELTANO_ENVIRONMENT

meltano run ...

I have an implementation for this working locally, but I'm away on holiday for 2 weeks now so I'll open a PR when I'm back. Until then, a few things:
"prefix" implies before other components of the state ID (i.e. {prefix}-{active environment name}:{extractor name}-to-{loader name}), but this causes errors when resolving state by environment since it seems to take everything before : as the environment name. Moving it to after the : (i.e. {active environment name}:{prefix}-{extractor name}-to-{loader name}) works, but then it's not a true prefix anymore.
Given the first format is preferred, the regex used to destructure information from the state ID will need to be modified a bit. Perhaps this is a bit easier if the prefix and environment name have a more distinct delimiter like --.
({prefix}--){active environment name}:{extractor name}-to-{loader name}

Given the second format is preferred, the option name may need some rethinking. A distinct delimiter might be desirable here as well.
{active environment name}:({prefix}--){extractor name}-to-{loader name}

@ReubenFrankel @aaronsteers I'm actually ok with the second option/format. In that case I think we could just use ":" as another deliminator and basically use that as our "official" segment key.
Strictly speaking, does it have to be a prefix though? What if it was a suffix:
{active environment name}:{extractor name}-to-{loader name}:{optional-suffix}
That's super easy to split on or abuse via regex, predictable, and still allows users to inject a unique attribute.

@pandemicsyn Like the idea of : as a common segement delimiter, although there would have to be enforcement of a limited character-set for the prefix value.
Don't see why a postfix/suffix couldn't work also as --state-id-postfix or --state-id-suffix.
{active environment name}:{extractor name}-to-{loader name}(:{postfix/suffix}

As long as the option is clearer how it modifies the state ID, I don't see a problem.

@ReubenFrankel and @pandemicsyn - I'm inclined to agree with the suffix approach and using ':' as a delimiter.
Agreed this means we should disallow ':' from within the provided suffix and from within the component parts, namely: environment_name, extractor_name, loader_name. (Shouldn't be a problem.)

What I'm not sure about as of now is whether we should be mapping this to #6164.
@ReubenFrankel - Are your use cases for wanting this in line with #6164, or specifically, the use case of wanting to run 'basically' the same pipeline but with different seeds passed via env vars?

@aaronsteers Yes, that is basically our requirement. This issue and #6164 sound very similar to me (even so far as mentioning : delimiting and the concept of a suffix in your initial comment), with the latter detailing more on how this would integrate with meltano.yml and environment variable expansion.
If I understand correctly, these two approaches would be equivalent:

environments:
  dev:
    state_id_suffix: ${PIPELINE_ID}
    # ...

meltano run ...

meltano run --state-id-suffix $PIPELINE_ID ...

Either approach satisfies our use-case, but we lean more towards the CLI due to how we run meltano currently.

@ReubenFrankel - Yes, exactly. And thanks for confirming regarding your use case related to #6164.
We could then take an approach of:

Add --state-id-suffix support in meltano run.
Add state_id_suffix: SUFFIX support in meltano.yml environment definitions (as sampled in @ReubenFrankel's example code above), and support the setting of this via the meltano config CLI.
Long-term,  how these are used and what additional features we'd want (if at all) in a more 'native' meltano construct for something like "sub-environments" or "environment matrices".

The only disadvantage I can see about this ordering, and not going directly into the meltano.yml approach, is that presumably this introduces some small additional risk of environments being misconfigured. I'd like to eventually land on a spec that gives a very high confidence that each config item in the matrix is properly set to match the others. That's something though, I think we can continue to iterate upon.
@tayloramurphy - From the product side, what do you think of this approach of these three steps, green-lighting the first two steps above and holding on the third longer-term question until we get usage data from the first two?

@aaronsteers looking at this proposal, yes I think it makes sense for the first 2 👍 Along with the spec that the suffix is delimited with : and we disallow ':' from within the provided suffix and from within the component parts.
We'd need to spend a moment on how environment variable inheritance works to make sure it's clear to user (similar to what Cody did in https://docs.meltano.com/guide/configuration#environment-variable-expansion ). Otherwise I like it


Fix Swift 5.4 docker setup

Motivation:
Docker build for Swift 5.4 is failing with:
18:27:28 ERROR:  While executing gem ... (OptionParser::InvalidOption)
18:27:28     invalid option: --no-ri
18:27:28 Did you mean?  no-force

Modifications:
Remove --no-ri --no-rdoc.
Result:
Docker build for Swift 5.4 completes successfully.

This change already included in https://github.com/apple/swift-nio-extras/pull/125. Closing.


hercmExplorer should take arguments on argv

Namely, loading a file via argument. Possibly others.

Issue resolved in cda41fbe76b8901be46beff27d090ddce59aeeca


Can it be used on arm chips?

Can it be used on arm chips?
thanks

Hey!
It's should work for Linux.


Allow resending failed messages

When a message fails to send and you get a red X next to it, it'd be nice if there was a button to try resending the message or to remove it.

I think we should have one setting to resend automatically when internet/connection is established back.


Add beta and binomial distribution functions in keras.random

Hi,
while working on my project that is based on keras I realized that the keras.random module is missing the two distribution functions that I need in my project, namely beta and binomial,
So, I've implemented these two functions in all four backends currently being supported by Keras, i.e. TensorFlow, Jax, PyTorch and Numpy.
I've created gists of these implementations for review's sake before creating a PR as recommended by the guidelines:

PyTorch: https://gist.github.com/KhawajaAbaid/16b6ebc7c90a04896001f32d4659f6fb
Jax: https://gist.github.com/KhawajaAbaid/c5c8a6be502af3a559c011bb2723efda
Numpy: https://gist.github.com/KhawajaAbaid/029742532ac8625340c7ed70263ed2da
TensorFlow: https://gist.github.com/KhawajaAbaid/4bcfd373b776c44867484315a84dbc57

Please note that as tensorflow doesn't offer a built-in method for beta function so I've implemented a workaround using a statistical formula to use gamma distributed random variables to derive beta distributed random variable.
Specifically, $U(a, b) = X(a) / (X(a) + Y(b))$ where $U(a,b)$ is the beta distributed random variable using parameters $a$ and $b$ and $X(a)$ and $Y(b)$ are gamma-distributed random variables using parameter $a$ and $b$ respectively.
I think having these two functions part of the keras.random module will greatly help other ML practitioners as they won't have to implement all these variants of these functions to take advantage of backend agnosticism of Keras in their projects.

Sounds good, we can add them. If you're able, please send a PR.

Thank you. I'll create a PR in a few minutes as I've pretty much already implemented everything. :D

I've created a PR at https://github.com/keras-team/keras/pull/18920
(Really sorry, it took longer than I thought)

Hi @KhawajaAbaid ,
As the propsoed PR got merged could you please mark this issue as resolved. Thanks!

Yes sure. Thanks for the reminder.


[DOCUMENTATION]grammar

Section 4.2.3 on page 18 use-case should be use case.

Thanks, I've fixed this and this will appear in the next released version.


(#1006) Add support to sshd process

sshd server process use fork + execv to
create ssh session for connected client

Ref: https://github.com/openssh/openssh-portable/blob/16ea8b85838dd7a4dbeba4e51ac4f43fd68b1e5b/sshd.c#L2112

intercept setrlimit and add our logic to allow to scoping sshd process

Looks great to me!  Thanks @michalbiesek!


⚠ Samsung has degraded performance

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

HTTP code: 200
Response time: 2166 ms

Resolved: Samsung performance has improved in b4fbafa.


UAT | Scrutiny | No home button

Once I am in the View Cases section, there is no back or home button if I want to go to home page and view pending registrations instead.

We have a back button according to figma designs which will take you back to home button.
If we need to have another home button, please let us know where should it be placed.
c.c. @Ramu-kandimalla

A back button should be fine but don't see it here.

@anshumanth-egov The FSO user won't have access to see the pending registrations. The inbox component itself is a home screen for FSO user.
I will remove the employee card and make the relevant changes

I checked in Dev env, able to view the list of cases screen directly after login with FSO credentials


Add procedure for running an element node

Codecov Report

Merging #95 into master will decrease coverage by 49.54%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #95       +/-   ##
===========================================
- Coverage   82.93%   33.39%   -49.55%
===========================================
  Files          67      242      +175
  Lines        1096     3159     +2063
  Branches      115      228      +113
===========================================
+ Hits          909     1055      +146
- Misses        175     1988     +1813
- Partials       12      116      +104

Impacted Files
Coverage Δ

...ackages/element-app/src/redux/fullNode/handlers.js
0% <0%> (ø)

packages/element-app/src/redux/snackbar/reducer.js
0% <0%> (ø)

...ackages/element-app/src/components/Ledger/index.js
0% <0%> (ø)

...ckages/element-app/src/redux/snackbar/container.js
0% <0%> (ø)

packages/element-api/src/express/app.js
93.33% <0%> (ø)

...ent-app/src/components/ExpansionPanelList/index.js
0% <0%> (ø)

...element-app/src/components/AppBar/DrawerContent.js
0% <0%> (ø)

.../src/components/ElementFullNode/ElementFullNode.js
0% <0%> (ø)

packages/element-app/src/index.js
0% <0%> (ø)

packages/element-app/src/pages/dapp/index.js
0% <0%> (ø)

... and 165 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2c5f158...fb2647e. Read the comment docs.


Initial commit of mod_cluster-discovery

This is a close to complete version of the Discovery example. Feedback appreciated. I will have one more pass at the README.md to finish it off in the next day or so.

I had another pass to correct typos, language. The only key remaining change to make is that, I have found, when using Undertow+mod_cluster as a load balancer, authentication credentials need to be added on the load balancer as well as the workers. When this is not done, I found that the client was failing silently with no exception nor error message. I'm wondering if this is an issue that should be adressed?

@rachmatowicz I am taking this for review and merge. I see quite a few nitpics -  do you prefer I comment each one of 'em or just merge and fix myself afterwards? (I prefer the latter)


FIX Pass string with whitespaces to cleos in cleos.sh

when passing string arguments to cleos.sh like --stake-net "100000.0000 EOS" it would fail with unrelated error ERROR: ExtrasError: [EOS] caused by the interpolation of the string argument.

This could combine multiple args to one... can you post example that this fixed?

./cleos.sh system newaccount eosio aza111111114 \
EOS6uoGxeNF69iPSsQHM8fvLGnEQ5BACSgFGS6WbE98DcVafmSgA9 \
EOS6uoGxeNF69iPSsQHM8fvLGnEQ5BACSgFGS6WbE98DcVafmSgA9 \
--buy-ram-EOS "100000.0000 EOS" --stake-net "100000.0000 EOS" --stake-cpu "100000.0000 EOS"

@bytemaster could you provide an input where this combines multiple arguments into one?

Thanks. This helped me past the step:
$ cleos push action eosio.token create '[ "eosio", "1000000000.0000 SYS"]' -p eosio.token
... in this tutorial: https://github.com/EOSIO/eos/wiki/Tutorial-eosio-token-Contract

@bytemaster I believe this is needed so that " are passed into the script.

This is the correct way to maintain the top-level tokenization of the input stream in a bash script.


Object Detection Not working in Landscape

Hi
Object detection not working in Landscape but its working in portrait. Can anybody please tell me Why Object detection not working in the landscape in Android.
Thanks!

Hi,
At the moment this example application supports only the portrait mode, however by modifying the code the landscape support can be easily added. Did you tried to add the landscape support?
If yes, how did you tried?
Regards,
Zoltan

Hi
Yes, I have tried to support in landscape mode too.
I have only change
sensorOrientation = rotation+screenOrientation;
to
sensorOrientation = screenOrientation;
and Its working.
But in landscape, I want to show the  preview  of the camera in full screen So I have changed the
DESIRED_PREVIEW_SIZE =new Size(screenWidth,screenHeigth)
and comment the chooseOptimalSize() function
In that case It's not working. Please help me

Hi,
This weekend I'll be very busy, however hopefully on Sunday I'll have some time to check the problem.
I hope it will not be to late for you.
Thanks for your understanding,
Zoltan

Hi
Ok, No Problem.
Thanks
Shruti

Hi,
I created a branch called landscape-mode: https://github.com/szaza/android-yolo-v2/tree/feature/landscape-mode; Here I pushed some workarounds for your problem.
To comment out the chooseOptimalSize() is not a good idea, however you can change the preview size by replacing the return value of the chooseOptimaSize method. To keep it simple, I replaced the texture.setAspectRatio method in the CameraConnectionFragment.java to textureView.setAspectRatio(1920, 1080);


Updating rr_openrover_basic package

Adding package to melodic, and updating release repo for kinetic

Thanks for the contribution.
It will be much better if you split this into two separate pull requests.  The basic reason is that the sync schedules for Kinetic and Melodic are not synced, so it may be the case that this gets held up because of one or the other of them.  The other reason is that it is good to keep the PRs confined to a single thing so we can easily look at the history and/or revert later if needed.
Additionally, this PR looks like it failed CI.  It failed because the release repository at https://github.com/RoverRobotics-release/rr_openrover_basic-release.git isn't set up properly.  In order to setup that release repository, you'll have to follow the steps at http://wiki.ros.org/bloom/Tutorials/FirstTimeRelease .  I'm going to close this PR for now, but once you have fixed these things, please open new PRs (bloom will do this for you).

Will do, thanks for the advice