fix for searchEnabled option and corrects types

…of selects

Description

From docs:
searchEnabled
Type: Boolean Default: true
Input types affected: select-one
Usage: Whether a search area should be shown.
Note: Multiple select boxes will always show search areas.
Motivation and Context

https://github.com/jshjohnson/Choices/issues/533
How Has This Been Tested?

https://jsfiddle.net/pvvnxdementor5/9gmv72L1/17/
Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@utrumo hey - multiple changes have gone into master, can you verify whether this fix is still needed please?

hey @utrumo - I have applied your fix over the latest master branch. Thanks 👍


Simple Calculator

Simple Calculator should be able to perform the blow actions:

Addition
Subtraction
Multiplication
Division
Modulus

Advanced Functions:

Factorial
Power
Root
log10
Trignometric functions like sin cos tan

am ready to contribute in this issue


How to exploit the retrieved parameters from neighboring devices?

Pleasure to see the wonderful work! I read the paper and did not find any words to explain how to exploit the x^beta. In other words, how  to fuse the results of common parameters from respective k-th iteration of neighboring devices? Any explanation will be appreciated!

Thanks for your interest in our work. x^beta is used to majorize inter-device reprojection pairs to construct the surrogate function; see Eq. (19) and the paragraph after Proposition 2.

Thanks for your reply! I reread the referred part and realized the usage of x^beta in the surrogate function construction. Really ingenious.


Pre-Publish Checklist: General Guidance Logic

Summary

adds the functions for guidance on general story guidelines
requirements

Relevant Technical Choices

some overlap with this pull in which I set up the base file structure and guidance/tests for media.

I need a little more clarity on the following requirement(s):

Story landscape poster/cover size too small (less than 853 x 640) or wrong aspect ratio (not 4:3) ← we should try to prevent this
Missing story square poster/cover
Story square poster/cover size too small (less than 640 x 640) or wrong aspect ratio (not 1:1) ← we should try to prevent this

The story object available in state only persists the featuredMedia id and the featuredMediaUrl, which doesn't give any indication of the image's size. So I was thinking about how this check could be implemented.
Current stories aren't going to have the sizes of the image persisted, so they'd have to be migrated, I think... There's small modules like npm image-size that can determine an image's dimensions from a URL, so that might help if we go that direction. I suppose we'd have to attach those dimensions in a hook like useLoadStory.
And we can attach the dimensions of the image from inspector/document/publish where the featured media is chosen.
Per the discussion on the ticket, the story cover media will be checked in another PR.

To-do

[x] remove featured media checks
[x] update to sprintf

User-facing changes

None.
Testing Instructions

N/A

Fixes #4912

Regarding the open todos:
Let's not overcomplicate the image size part 🙂
We have all the image & image size information available in the REST API already, no need to do reinvent the wheel. We can discuss what data is needed, change REST API response if necessary, and use it in useLoadStory to update the data.
Agreed though that it needs more clarity on the exact requirements first. Let's discuss that on the ticket itself though.

Regarding the open todos:
Let's not overcomplicate the image size part 🙂
We have all the image & image size information available in the REST API already, no need to do reinvent the wheel. We can discuss what data is needed, change REST API response if necessary, and use it in useLoadStory to update the data.
Agreed though that it needs more clarity on the exact requirements first. Let's discuss that on the ticket itself though.

Per the updated description, I'm going to remove these checks from this PR
I'm also working on the ticket which will handle these checks, so @swissspidy it's great to hear about the API :) I'll just need the featured media dimensions and put it in the useLoadStory.

Regarding the open todos:
Let's not overcomplicate the image size part 🙂
We have all the image & image size information available in the REST API already, no need to do reinvent the wheel. We can discuss what data is needed, change REST API response if necessary, and use it in useLoadStory to update the data.
Agreed though that it needs more clarity on the exact requirements first. Let's discuss that on the ticket itself though.

Per the updated description, I'm going to remove these checks from this PR
I'm also working on the ticket which will handle these checks, so @swissspidy it's great to hear about the API :) I'll just need the featured media dimensions and put it in the useLoadStory.

I've created #5105 to update the REST API responses accordingly.


German Translation

@Derko8 Thank you for making German translation!
It is released in v1.4.0.
Your using empty space character is so cool.
Also, you can use `` to control coloring as in japanese.xml.


added getSocial integration

added get social integration across the website

@Riscum please check your commit, you have just added empty lines

@jagoncalves14 Am I 🤔 ? Did you mean Nuno Carneiro?

closed as we followed another path


fix gcc warning "stringop-truncation"

fix part of #1204

Thanks!
Better to use mjSTRNCPY from engine_array_safety.h (already included).


"Additional command line input" not being passed to JAR

I am running an ON_DEMAND job with arguments from singularity.
The job invokes an executable jar. When I run the JAR locally via command line: java -jar message-processing-1.2.jar 1,2,3,4
"1,2,3,4" is passed as a string to main(String[] args)
I expect the same behavior when I pass "1,2,3,4" as "Additional command line input" but the argument is not being passed.
Any suggestions?

never mind, was a bug on my side. Sorry!


why not create package by bower

It's a great directive for the Ionic Framework.  why not create package by bower.

Its not perfect, but you can do:
"dependencies": {
  "ionic-ion-showWhen": "https://github.com/andrewmcgivery/ionic-ion-showWhen.git"
},


[PD] Manage time with your calendar

From Module-HTML-CSS created by kfklein15: CodeYourFuture/Module-HTML-CSS#32
Coursework content
Set up your Google calendar to show your weekly availability for calls with your peers. Share your calendar with your pair of the week. If you prefer, you can use Calendly instead of Google calendar.
Estimated time in hours
0.5
What is the purpose of this assignment?
This assignment aims to help you start using calendar software effectively to manage your time and to collaborate with your peers and volunteers.
How to submit
Share the link of your calendar or a screenshot on the ticket on your coursework board.
Anything else?

Create a Google calendar
Share your Google Calendar

Stretch
You can also set-up a Calendly page, which you can share with people, so they can book time with you. Just make sure your calendar is up-to-date with your avaiability, or you might get invitations for times you cannot make.


vue 2 version

Is your feature request related to a problem? Please describe.
I would love to use this in my project which uses vue 2.x. Is this possible?

This project is intended to be used with Vue 3 and uses some features of Vue 3. Making it 2.x compatible means extra work and code for every user.
So, we would not add Vue 2.x compatibility to the project.


 It works by adding a go.wok file in the root directory and add a go.mod file in each go module.
To adapt this solution to nx-go, we need to be able to manage versions before 1.18 (without the go.work files) and the next versions.
It can be also nice to add an utility to upgrade the current workspaces to th new module management system.
App & libs creation
When creating apps and libs we have now 4 use cases. (The first match skip the followings)

A go.mod file is in the root directory: the new package is created as before.
A go.work file is in the root directory: the package is created with its own go.mod file in its directory and it is added in the use list in the go.work file.
The option "useWorkspace" is added in the command line the go version is checked, if it is before 1.18 an error is thrown otherwise, a go.work file is added in the root directory.
Same behavior as before 1.18

Conceptually looks good, how do we generate the module import path when in a workspace?
Do we treat it similar to the npmScope for javascript / typescript projects?

Hello @phillipCouto !
Thank you for your answer. I had the same question, I'm just getting started with nx, and I am not sure if adding a goScope property in the nx.json is a good practice. The behavior could be :
If the property is set, then the module import path will be the concatenation of the goScope property and the module relative path. Otherwise, the module import path will be the relative path of the module.
What do you think about this?

Hi! Could you be so kind to explain how to get go workspaces working with nx?
From my understading, I should just initialize the workspace in the root directory of the nx project, is this correct?

Hello @phillipCouto !
Thank you for your answer. I had the same question, I'm just getting started with nx, and I am not sure if adding a goScope property in the nx.json is a good practice. The behavior could be :
If the property is set, then the module import path will be the concatenation of the goScope property and the module relative path. Otherwise, the module import path will be the relative path of the module.
What do you think about this?

Sounds good to me! Really sorry for the late reply. I need to review my Github notification settings!

Hi! Could you be so kind to explain how to get go workspaces working with nx?
From my understading, I should just initialize the workspace in the root directory of the nx project, is this correct?

The current stable version does not yet support it out of the box. As this issue is adding the functionality in question. There is a release candidates for 2.7.0 with support for workspaces though which you can evaluate.
@Anthony-Jhoiro may be better to answer how to use workspaces with 2.7.0 as I have been MIA for a few months and just getting caught up again.


PROVIDE ( GPIO = 0x60004000 ); in tools/sdk/ld/esp32.peripherals.ld (IDFGH-1607)

I was told to move https://github.com/espressif/arduino-esp32/issues/2571 to this queue.
As per that bug,
I had to reapply this patch:
tools/sdk/ld/esp32.peripherals.ld
-PROVIDE ( GPIO = 0x3ff44000 );
+PROVIDE ( GPIO = 0x60004000 );
I got it from there https://github.com/NeoCat/ESP32-P3RGB64x32MatrixPanel/blob/master/README.md 'You should patch the tools/sdk/ld/esp32.peripherals.ld to avoid random pixel noise on the display as following
Please refer section 3.3. in https://www.espressif.com/sites/default/files/documentation/eco_and_workarounds_for_bugs_in_esp32_en.pdf for more details."
also present here http://gitlab.studiopresent.rs/ESP32-dotlab/framework/blob/master/tools/sdk/ld/esp32.peripherals.ld
and also found it here https://github.com/mrfaptastic/ESP32-RGB64x32MatrixPanel-I2S-DMA
https://qiita.com/h_nari/items/d52734440a7256072e8e when translated by google, says " I encountered GPIO 's unintelligible behavior. After examining the cause, it turned out to be a CPU bug (Eratta)"
I'm not sure if any of those people opened a bug or tried to get it changed, but in case none of them did, I'm filing this bug.
I am not knowledgeable about why this fix is needed, although the first and last link does give details that should help

Details:
Some ESP32 peripherals are mapped to two internal memory buses (AHB & DPORT).
When written via DPORT, consecutive writes to the same address may be lost.
Workarounds:
This issue is automatically worked around in the drivers of ESP-IDF V1.0 and newer.
Workaround Details:
When writing the same register address (i.e., FIFO-like addresses) in sequential instructions,
use the equivalent AHB address not the DPORT address.
(For other kinds of register writes, using DPORT registers will give better write
performance.)
Fixes:
This issue is fixed in silicon revision 1.

So this should only affect old rev0 chips and only consecutive writes to the same address. Because of this and the fact there is a performance trade-off, it is better to selectively work around this issue instead of applying a blanket fix.  This is what esp-idf drivers do.
Can you explain what problem this resolved for you?

@negativekelvin people using ESP32 to run RGBPanels via I2S DMA seem to have timing problems without it, I gave the links in my original message. For instance
Patching GPIOhttps://github.com/NeoCat/ESP32-P3RGB64x32MatrixPanel/blob/master/README.md to avoid eratta of ESP32
You should patch the tools/sdk/ld/esp32.peripherals.ld to avoid random pixel noise on the display as following:
/* PROVIDE ( GPIO = 0x3ff44000 ); */
PROVIDE ( GPIO = 0x60004000 );

Ok but have you confirmed this yourself and what do GPIO registers have to do with I2S DMA?
For instance https://github.com/NeoCat/ESP32-P3RGB64x32MatrixPanel/blob/master/README.md mostly uses REG_WRITE so changing the GPIO struct address would have no effect.

@negativekelvin  no, I did not. I just used multiple projects that told me I had to change this, so I did.
It might be possible they are all wrong and have been passing around an obsolete fix. If you think that's the case, feel free to close this.

Hi @marcmerlin ,
@negativekelvin is right that this is only a problem on ESP32 rev0, and only a problem with very specific workloads - writing to the exact same DPORT register twice in consecutive instructions.
I don't see anywhere in the code where this would happen, but it's not inconceivable that it could have happened at some point. Also, as @negativekelvin  points out, the library also uses register macros and for these the suggested "fix" would have no effect.
This advice looks like it was added in the initial commit 2 years ago, so my guess is that it was copied over from some other codebase where it may have been necessary on the rev0 chip:
https://github.com/NeoCat/ESP32-P3RGB64x32MatrixPanel/commit/6143785bc7c0e88439e0ef58a590d3a8f6d25677#diff-04c6e90faac2675aa89e2176d2eec7d8R14
If you do find a situation where changing this address fixes a problem, please let us know and we will reopen.

thanks for the look/review @projectgus , this wouldn't be the first time that people have been copying over an unnecessary workaround.


Use bash for makefile

The shell expansion was happening before the version bump so it was
picking up the previous tag. This uses bash as the Makefile shell so we
can use command substitution.

Coverage remained the same at 70.577% when pulling 1ad741596d559e3189e13bd930b2a14ac5a75bd4 on fix-make into 43a09a61c1d40a08fbf4a6a5395b52968e62883f on master.


Changed command lines in "contributing" to include build tools

in spawned nix-shell.
This way the developer does not need to have cabal-install and ghcid in correct versions installed.

I think we should make these simpler before recommending them

Will work something out!

Done - commands are as simple as before.

Thanks!


macOS 10.16 (Big Sur) support

Module causes crash on Big Sur, possibly related to this Radar: http://www.openradar.appspot.com/7483151 – dynamically setting the styleMask is somehow the cause.
Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [55604]

Application Specific Information:
Crashing on exception: Cannot remove an observer <NSTitlebarView 0x7fdbcba56190> for the key path "_titlebarBackdropGroupName" from <PROPanel 0x7fdbcba29590> because it is not registered as an observer.

Application Specific Backtrace 1:
0   CoreFoundation                      0x00007fff27a1736f __exceptionPreprocess + 242
1   libobjc.A.dylib                     0x00007fff66416a56 objc_exception_throw + 48
2   Foundation                          0x00007fff2a314adb -[NSObject(NSKeyValueObserverRegistration) _removeObserver:forProperty:] + 564
3   Foundation                          0x00007fff2a31485c -[NSObject(NSKeyValueObserverRegistration) removeObserver:forKeyPath:] + 74
4   Foundation                          0x00007fff2a314539 -[NSObject(NSKeyValueObserverRegistration) removeObserver:forKeyPath:context:] + 190
5   AppKit                              0x00007fff252a7175 -[NSTitlebarView viewWillMoveToWindow:] + 73
6   AppKit                              0x00007fff248f13b3 -[NSView _setWindow:] + 247
7   AppKit                              0x00007fff2514caf4 __21-[NSView _setWindow:]_block_invoke.426 + 300
8   AppKit                              0x00007fff248f198f -[NSView _setWindow:] + 1747
9   AppKit                              0x00007fff2514caf4 __21-[NSView _setWindow:]_block_invoke.426 + 300
10  AppKit                              0x00007fff248f198f -[NSView _setWindow:] + 1747
11  AppKit                              0x00007fff2492b2cd __25-[NSWindow setStyleMask:]_block_invoke + 513
12  AppKit                              0x00007fff2492b071 NSPerformVisuallyAtomicChange + 132
13  AppKit                              0x00007fff2492af7b -[NSWindow setStyleMask:] + 170
14  NativeExtension.node                0x00000001135a3a90 _Z9MakePanelRKN3Nan20FunctionCallbackInfoIN2v85ValueEEE + 149
15  NativeExtension.node                0x00000001135a39da _ZN3Nan3impL23FunctionCallbackWrapperERKN2v820FunctionCallbackInfoINS1_5ValueEEE + 188
16  Electron Framework                  0x0000000107c57c3c _ZN2v88internal9Accessors12MakeAccessorEPNS0_7IsolateENS0_6HandleINS0_4NameEEEPFvNS_5LocalINS_4NameEEERKNS_20PropertyCallbackInfoINS_5ValueEEEEPFvS9_NS7_ISB_EERKNSA_INS_7BooleanEEEE + 16844
17  Electron Framework                  0x0000000107c5713a _ZN2v88internal9Accessors12MakeAccessorEPNS0_7IsolateENS0_6HandleINS0_4NameEEEPFvNS_5LocalINS_4NameEEERKNS_20PropertyCallbackInfoINS_5ValueEEEEPFvS9_NS7_ISB_EERKNSA_INS_7BooleanEEEE + 14026

10.15 == Catalina. 11.0 == Big Sur. Not sure which this refers to

Hi Team,
I am also facing the same issue, it crashes on opening the panel window in BigSur.

We've been unable to find a solution for this crash – So far it looks like the changes to the titlebar in Big Sur make this module impossible to update to be compatible going forward. The approach was always hacky to get around the limitations of Electron, but those hacks no longer work.

We've been unable to find a solution for this crash – So far it looks like the changes to the titlebar in Big Sur make this module impossible to update to be compatible going forward. The approach was always hacky to get around the limitations of Electron, but those hacks no longer work.
It's so sad that after all this time Electron still has no native way to create an NSPanel 😢

Yes @tommoor agreed, it would be really great if electron supports this by default.

It was great while it lasted @tommoor
Great work overall! We really enjoyed using this native module.

Was poking around the WhatsApp desktop app which is electron. It looks like they started with electron-panel-window, but completely rewrote it.
This is what their api looks like: https://gist.github.com/ibash/2c9894a8038b71456aeabe413e532c19
What I'm not sure about is whether their panel works on Big Sur or not, I'm not sure where (if anywhere) their panel is used in the app.


Documentation?

Please add: mkdir build
to the documentation, or else make silently does nothing.
Also, it is unclear how to actually compile and run the emitted code. The examples seem to output something that can't be input into a C compiler. This is strange for a library which claims to be easy to use.

Hi @bftjoe,
Thanks for your interest in BuildIt. The Makefile itself has steps to create the appropriate directories. I think the only difference might be that the build system it written for GNU-make and not just make. I will update the instructions in the README to reflect that.
Thanks for pointing it out


Misc improvements (fix broken links, add missing app, updated GH descriptions)

Fix broken links for GHE repos
Add https://github.com/alphagov/feedback to list of FE apps
Re-generate data, which also picked up some descriptions I updated.

👍


implement float.neg

float.neg should datarize to the negate value of its base float object

Job gh:cqfn/eo#229 is not assigned, can't get performer

You @nlchar/z need to have one of these roles in order to do "Request order start": ARC, PO; I'm sorry to say this, but at the moment you've got no roles in this project


Incremental compilation support

Hi guys! Great project, been using it for a while now!
I wanted to ask if incremental compílation is implemented or how can it be used, if already available. Basically, I just want to remove the "[info] TypeScript compiling on ALL source(s)" situation, everytime a change is made on a single file, or no changes has been made at all (but compilation is kind of still required because of other dependencies on it). Could this be possible?

Unfortunately, incremental compilation is not currently supported.  It used to work, but there was an update to the compiler that made it much more difficult, IIRC.  We'd love to get incremental compilation working again.  Personally, I don't have as much time to work on this plugin as I'd like.  If you'd like to take a shot at it, let me know and I can probably help out.


No ScreenShare.plugin.js file in folder HTML

There is no ScreenShare.plugin.js file in the folder HTML.

Did anything go wrong with the instillation?

mkdir: cannot create directory ‘/var/www/’: File exists
mkdir: cannot create directory ‘/var/www/certbot’: File exists
server {
listen 80;
listen [::]:80;
listen 443 ssl;
listen [::]:443 ssl;
server_name bdscreenshare.duckdns.org;

location /.well-known/acme-challenge {
allow all;
alias /var/www/certbot/.well-known/acme-challenge;
}
location /ssws {
proxy_pass http://localhost:8006;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_buffering     off;
proxy_connect_timeout 43200000;
proxy_read_timeout    43200000;
proxy_send_timeout    43200000;
}
location /screenshare {
auth_basic "Private";
auth_basic_user_file AUTH/.htpasswd;
autoindex on;
alias DIR;
add_header 'Access-Control-Allow-Origin' '*';
}
#ssl_certificate /etc/letsencrypt/live/bdscreenshare.duckdns.org/fullchain.pem;
#ssl_certificate_key /etc/letsencrypt/live/bdscreenshare.duckdns.org/privkey.pem;

#if ($ssl_protocol = "") {
#   rewrite ^/(.*) https://$server_name/$1 permanent;
#}

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';
ssl_session_timeout 1d;
ssl_session_cache shared:SSL:50m;
ssl_stapling on;
ssl_stapling_verify on;
add_header Strict-Transport-Security max-age=15768000;
}
ln: failed to create symbolic link ‘/etc/nginx/sites-enabled/bdscreenshare.duckdns.org.conf’: File exists

Reloading nginx configuration nginx                                                                           [ OK ]
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for bdscreenshare.duckdns.org
Using the webroot path /var/www/certbot for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. bdscreenshare.duckdns.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://bdscreenshare.duckdns.org/.well-known/acme-challenge/Y7_cKqiU9REqWYC2sCRjABJv9Prspq_DMgBd3buQoHE: Error getting validation data

IMPORTANT NOTES:

The following errors were reported by the server:
Domain: bdscreenshare.duckdns.org
Type:   connection
Detail: Fetching
http://bdscreenshare.duckdns.org/.well-known/acme-challenge/Y7_cKqiU9REqWYC2sCRjABJv9Prspq_DMgBd3buQoHE:
Error getting validation data
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Reloading nginx configuration nginx                                                                           [fail]
npm WARN<EMAIL_ADDRESS>No repository field.
Adding password for user screenshare
[Unit]
Description=Screenshare
After=network.target

[Service]
ExecStart=/usr/bin/node /root/Better-Discord-Screen-Share-master/main.js
Restart=always
User=root
Group=root
WorkingDirectory=/root/Better-Discord-Screen-Share-master
Environment=BOT=MzQwOTkyNjQ4MzAxMjQ4NTEz.DF6lrw.hs6w1kRlnXZXSQ-gD2N1dhlsdug
Environment=CHATID=281549912620007424
Environment=ADMIN=jakecrowley#4681
Environment=SUDO=
Environment=PASSHTTP=
Environment=DOMAIN=bdscreenshare.duckdns.org
[Install]
WantedBy=multi-user.target
Failed to get D-Bus connection: No connection to service manager.
Failed to get D-Bus connection: No connection to service manager.
Operation failed: Invalid argument
Failed to get D-Bus connection: No connection to service manager.
./install.sh: line 62: [: =: unary operator expected
Failed to get D-Bus connection: No connection to service manager.
No journal files were found.
An error has occured with launching the server, please send me error.log above to<EMAIL_ADDRESS>

It seems like systemd isn't working and it can't connect to your server to get the certificate. I'm actually working on a much more simple installer and server so if you want to wait for that it should be out in like a week. But try and make sure your ports are open. What Linux version are you on?

I have verified that ports 80 and 443 are opened by running an apache web server. I am on Ubuntu 14.04.

Is it a full instillation of it? And not the windows 10 one?
On Jul 30, 2017 2:05 PM, "jakecrowley"<EMAIL_ADDRESS>wrote:

I have verified that ports 80 and 443 are opened by running an apache web
server. I am on Ubuntu 14.04.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ConnorTheFox/Better-Discord-Screen-Share/issues/2#issuecomment-318925886,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHAO1Uu5EwhG0ru5DlmBeZfjUJbg7BFDks5sTOHtgaJpZM4OnfSc
.

No, it is the built-in windows 10 one. I am retrying now with a full installation of Ubuntu.

Now on a proper installation of Ubuntu.
Getting error:
Failed to issue method call: No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/systemd1/unit/screenshare_2eservice

Huh, are you running it as root?
On Jul 30, 2017 3:39 PM, "jakecrowley"<EMAIL_ADDRESS>wrote:
Now on a proper installation of Ubuntu.
Getting error:
Failed to issue method call: No such interface
'org.freedesktop.DBus.Properties'
on object at path /org/freedesktop/systemd1/unit/screenshare_2eservice
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ConnorTheFox/Better-Discord-Screen-Share/issues/2#issuecomment-318931525,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHAO1YW-szrFiRotKcauPvvuzoeG1rQ1ks5sTPgUgaJpZM4OnfSc
.

I am running it with sudo so yes. Is there another distro of linux i could use instead of ubuntu, maybe that has something to do with it.

No, I wish but the media server only works on Ubuntu. Sorry it's not
working I never made this to be a good install, that's why I'm going to
rework the screenshare server to make it easier
On Jul 30, 2017 3:44 PM, "jakecrowley"<EMAIL_ADDRESS>wrote:

I am running it with sudo so yes. Is there another distro of linux i could
use instead of ubuntu, maybe that has something to do with it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ConnorTheFox/Better-Discord-Screen-Share/issues/2#issuecomment-318931839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHAO1RiOfhM4BMZksxvsxhoc5zRa4uqKks5sTPlNgaJpZM4OnfSc
.

Turns out I had the username wrong in the command! I rerun it and it's installed!

Do you need any other files in the plugins folder other than screenShare.plugin.js?

Nope, but it won't work if it's running on your own network though. The
server has to be off network.
On Jul 30, 2017 4:00 PM, "jakecrowley"<EMAIL_ADDRESS>wrote:

Do you need any other files in the plugins folder other than
screenShare.plugin.js?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ConnorTheFox/Better-Discord-Screen-Share/issues/2#issuecomment-318932801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHAO1SrTpnJ57oaqFhGYialtnIKCXBsTks5sTPzxgaJpZM4OnfSc
.

So my friend is trying to use it and he installed it but the screenshare button isnt appearing
Heres some screenshots
http://prntscr.com/g2a57m
http://prntscr.com/g2a5pn
The bot is in the group as well. I am having my friend test it because it doesnt work on the local network

It appears that something has gone wrong, I found the link that's supposed to lead you to the screenshare icon and its just giving me a 404 Not Found even just going to bdscreenshare.duckdns.org/screenshare gives me a 404 Not Found
http://prntscr.com/g2a81w

The button is there, but it is just invisible, and clicking it does not do anything.

The button is there, it is just invisible, and clicking it makes "Uncaught TypeError: Cannot read property 'write' of undefined" appear in the Console

It seems like your NGINX configuration didn't go through, try going through the manual install

'primus' is undefined because i think it never connects. Going to https://bdscreenshare.duckdns.org/ssws says "Update Required"
http://prntscr.com/g2adj5

Yeah the server isn't serving the correct content, something went wrong
with the nginx configuration I think, so if you want to go through the
manual install page.
https://github.com/ConnorTheFox/Better-Discord-Screen-Share/blob/master/MANUAL.md#setting-up-nginx
On Jul 30, 2017 4:35 PM, "jakecrowley"<EMAIL_ADDRESS>wrote:

The button is there, it is just invisible, and clicking it makes "Uncaught
TypeError: Cannot read property 'write' of undefined" appear in the Console
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ConnorTheFox/Better-Discord-Screen-Share/issues/2#issuecomment-318934796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHAO1YClHKnPJPFRl78gp1UjRREKQrXQks5sTQVNgaJpZM4OnfSc
.

ah ok

ah ok, where would the nginx configuration be?

Nevermind, open port 8006, sorry that's not in the steps. Thats the primus server

Thanks! It's working great now! Me and my friends are gonna use this until the real screenshare feature comes out. It seems that it will be coming out soon because there have been leaks of working video calling / screensharing!

Awesome! I think once the screen sharing comes it will be in the form of
calls and not servers
On Jul 30, 2017 6:00 PM, "jakecrowley"<EMAIL_ADDRESS>wrote:

Thanks! It's working great now! Me and my friends are gonna use this until
the real screenshare feature comes out. It seems that it will be coming out
soon because there have been leaks of working video calling / screensharing!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ConnorTheFox/Better-Discord-Screen-Share/issues/2#issuecomment-318939322,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHAO1WvWhT3Yk8xiLP4-i0yRAwTBsduaks5sTRkdgaJpZM4OnfSc
.


Vertical divider example broken in documentation

Bug Report
The vertical divider example in the documentation is broken.
Steps

Go to https://react.semantic-ui.com/elements/divider/#types-vertical
Look at the Vertical Divider example

Expected Result
Expect to see the "AND" and "OR" dividers appear between the "Lorem ipsum…" columns.
Actual Result
Actually see the "AND" and "OR" dividers squished up to the left of the other columns.
Version
0.82.5
Screenshot

Perhaps this is related to this note from the main Semantic UI documentation:

Due to a change in W3C implementation of absolutely positioned elements in flex containers vertical dividers now currently only support 50/50 splits automatically, and only if not positioned as direct children of flex containers (like grid).

Looks like this may already be tracked in https://github.com/Semantic-Org/Semantic-UI/issues/4342
Apologies if this is a duplicate.

If anyone else has this problem, you can get the vertical divider closer to the expected behavior by giving it a style tag:
<Divider   vertical   style={{     padding: 0,     margin: 0,   position: 'relative', }} />


Book

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s)
For resources
Description
Why is this valuable (or not)?
For interview preparation mostly people use this book.
How do we know it's really free?
It's PDF is attached
For book lists, is it a book? For course lists, is it a course? etc.
it's a Book
Checklist:

[ no] Not a duplicate
[yes ] Included author(s) if appropriate
[yes ] Lists are in alphabetical order
[ yes, PDF] Needed indications added (PDF, access notes, under construction)

The repo does not host books. Please read CONTRIBUTING.md guidelines


NEXT-7312 - Show variants in Product overview / stock

EN:
It would be really clever if you could show the variants of a product in the master / slave system in the product overview. Main product then to unfold and indented the variants. This would have the decisive advantage that you can also see the stock levels and do not have to click through to the point Generate variants in the main product. And searching is possible but not a solution.
DE:
Es wäre wirklich clever, wenn man die Varianten eines Artikels im Master / Slave System in der Artikelübersicht einblenden könnte.   Und suchen geht zwar ist aber keine Lösung.
https://sbp-issuetracker-attachments.s3.eu-west-1.amazonaws.com/1572379930_5db89d1a5991d_1572379910_5db89d06b7ab3_Bildschirmfoto 2019-10-29 um 21.07.27.png

Hey,
if the main variants are collapsed, how do you want to do that with the pagination of the variants? There are systems that work with over 10000 variants.

That is why the "Design" label is set. Here are still some things to be discussed with our design.
Maybe the Design department even decides that this issue can not be implemented today

interested

Maybe it's not a good idea to have a collapse/expand mechanism but it might be possible to have an icon at the articles with variants that links to a product list specific for the article. In the list you see only the variants of that article with an own pagination. So it's more like a filter for a parent ID.

Quick update: We've looked into this idea and decided on this draft: https://share.goabstract.com/71b9510b-5e50-4370-acea-43e4b76f2f34


SPEC-0007: rename validate to normalize

Valiate usually convey a notion of boolean or raising an error, here we are normalizing because we are rreturning potentially a different object.

The intent here was validate, not normalize, although I can see why that would be a sensible replacement. I mean, we're not trying to normalize the input to that function, we're trying to ensure that it is something that can be converted to rng.
Perhaps fully correct would be both: validate and normalize [the seed]"

I mean, we're not trying to normalize the input to that function, we're trying to ensure that it is something that can be converted to rng.

But default_rng is what we are suggesting to be called, and it does more than validate. It actually does convert to a Generator.
However, I was also thinking "validate and normalize", unless "normalize" implies "validate" when the input is already a Generator.

I agree with @mdhaber, and I think we do want to normalize, int/None and other are convenience, and any internal implementation should only allow Generators, so those should validate that arguments are generator.
More generally you will find the saying "Parse don't validate" (I'll let you google it), and here it could apply because before default_rng the type id Generator|None|int, and after it's only Generator, and you do want as much as possible to be able to reason about the type.
(technically I don't even like rng = np.random.default_rng(rng), I even think it should not have the same name after normalisation to reflect the change in type).

unless "normalize" implies "validate"

I believe it does as it can't normalize an invalid value, but I'm happy to have both.

Actually going further, maybe the spec should say that user exposed functions should normalize (to a generator) and that private functions should validate (a generator only).

Actually going further, maybe the spec should say that user exposed functions should normalize (to a generator) and that private functions should validate (a generator only).

That phrasing works for me.

Actually going further, maybe the spec should say that user exposed functions should normalize (to a generator) and that private functions should validate (a generator only).

I would rather just say what exposed functions do... normalize. Whether private functions need to validate is up to the library. I don't see why a private function should need to validate if all public functions normalize.


memflow-pcileech vmware / remote implementation

I have the following code from example:

My Win10 VM is open, MemProcFS can read from it:

However, the example does not work:

Is there anything I can do to fix this and achieve fast live memory reads/writes or is it currently a technical issue?
I'm very new to this and it would be great if you could tell if I'm doing something wrong or is it actually not working right now? :D

Hey there, better place for this issue would be memflow-pcileech project. Anyways, does leechcore require to set the device argument to "vmware://" or is "vmware" sufficient? I personally haven't tried anything besides FPGA yet.

Both are fine I think (vmware:// and vmware), this for example works:

Device is straight put into LC_CONFIG:
https://github.com/memflow/memflow-pcileech/blob/main/memflow-pcileech/src/lib.rs#L38
Does it need anything else being setup apart from running as admin?

Don't think so

I couldnt see any additional steps that memprocfs is doing to initialize leechcore, but there probably is something i overlooked. Otherwise im kinda out of ideas right now, will have to test this on my setup at one point.

Also wanted to ask, is it currently possible to dump memory remotely, e.g. using pcileech -remote? (LC_CONFIG.szRemote)

Oh I see, is support for it planned anytime soon?

https://github.com/memflow/memflow-pcileech/blob/3febc1b6a76f0f17fcdc70836c1d48051565b3e9/memflow-pcileech/src/lib.rs

No one used them before but it should be quite straight forward to add those parameters, do you have an example on how they would be set? I Assume remote and remoteDisableCompress are bools and szRemote is just a string that we should pass through?

Not sure how they're set in the code specifically, this is what I was using:
.\MemProcFS.exe -device PMEM://C:\winpmem_64.sys -remote rpc://insecure:computername.local

https://github.com/ufrisk/MemProcFS/blob/ba8dd59afe2edcce64801ec976c92b2e2973d94f/includes/leechcore.h

It seems to only require szRemote to be set:
https://github.com/ufrisk/MemProcFS/blob/f1abe87dc2411fc6c097e4a97a8dd94edb6a8e52/vmm/vmmdll_core.c#L604
I gave it a shot and added a remote parameter that you should be able to set now. Do you mind giving it a shot? You can find it on the latest commit on the main branch.

Can't seem to make it work :(
Pretty new to Rust as well, and with no documentation (that I could find) on how to pass args there I'm stuck 😞.

Probably just passing them wrong

I noticed yesterday that more complex argument formatting will confuse our argument parser. For the time being you can parse it manually like so:
let args = ConnectorArgs::new(None, "device=pmem,remote=\"rpc://insecuret:hp\"".parse().unwrap(), None);

I also added new test cases here:
https://github.com/memflow/memflow/commit/929130564b9cbdb092f15b68377e61b13f0d94ef#diff-47b7e5a3ad9ec55ac75b25991ae1fe1d633f4769f02c40200d91cba3d46c1d27R396
So i can fix them up. Ideally the : syntax should probably go away but i havent decided upon that yet. Hope this helps for now, sorry for the inconvenience.

Had some issues with ConnectorArgs struct, debugged it a bit, if anyone comes by, the solution is to use this memflow version (because those structs are different between stable and beta as of now):

Thank you so much again, I can confirm it is working, or at least it's using the library to connect to the remote PC successfully:

You can close this issue if you want to, or use it to track vmware integration in the future if you'd want to add it 😄
Renaming to vmware/remote issues would be helpful since this thread ended on a different topic xD!

I updated the title but would like to keep this open until the original issues are resolved (and arg parsing works fine).

Could you please advise if that's a bug or am I doing something wrong? Looks like the integration with memflow-win32
is broken?

Again, had to use the "0.2.0-beta9" version for memflow-win32 crate, this fixed my issue, although API is different, maybe there's a documentation to it already?

I also can't seem to find a way to find process info by process name, only for ntoskrnl, meaning the following example doesn't work:

Can't find process_info_list() as well

Can't find process_info_list() as well

I also can't seem to find a way to find process info by process name

With version 0.2 of memflow all os implementations are generic over the base traits found in the memflow repository (Os, Process).
You should be able to find the methods, it could be that you are not including those traits in your source file and intellij-rust cannot find the traits, could you share code?
It would be advised to use the memflow applied videos as a loose reference as they have not been updated/corrected for 0.2, however they still provide good general information that carries over.
@h33p might update the videos for 0.2 (once the release has been stabilized), I don't know.

Thank you so much @dankope, I didn't include the trait, fixed my issue

@ko1N @h33p can close this as I think all issues have been addressed

I noticed yesterday that more complex argument formatting will confuse our argument parser. For the time being you can parse it manually like so:
let args = ConnectorArgs::new(None, "device=pmem,remote=\"rpc://insecuret:hp\"".parse().unwrap(), None);

I also added new test cases here: 9291305#diff-47b7e5a3ad9ec55ac75b25991ae1fe1d633f4769f02c40200d91cba3d46c1d27R396
So i can fix them up. Ideally the : syntax should probably go away but i havent decided upon that yet. Hope this helps for now, sorry for the inconvenience.

So this parser confusion is now fixed on the next branch and will be released in 0.2.0-beta10 somewhat soon. You should be able to put in the arguments in the format you "expect" with this update :)


34 - Implement method to destroy full toggle

Developing #34, which is required to destroy the toggle and the blocks inside it when the root is deleted with 'backspace', and when the 'delete block' button through the block settings (native EditorJS element) is clicked.

Hello @juanhurtado10, @MarioRodriguezS, and @jcamilocp. This PR closes #34.
An event was added in the delete button (toolbar block) to delete the blocks inside the toggle at the same time that the toggle root is deleted.
Also, the event was added to execute it when the backspace key is typed in the toggle root and this is empty.
This image shows the behaviors previously explained:

@juliansg022 LGTM 🚀 !! What about the tests?

@juanhurtado10 You're right, the tests to these events are missing. I'll work on them.


Table Milestone 4 - Integrator Support

😯 Problem to Solve
The purpose of this Work Item is to make sure we capture and create any necessary content to assist developers as they test integrating the table at the end of each Milestone.
💁 Proposed Solution

We'll capture integrator support as part of documenting each feature.


Switch to using IronLanguages/dlr

From @slozier on May 17, 2017 19:20
We are currently supporting two different DLRs which is a waste of effort. We should switch the codebase to use IronLanguages/dlr.
Copied from original issue: IronLanguages/main#1654

Done!


Captions and transcripts grey background stripes in Firefox

What

C’s&T’s in firefox there are grey background stripes that do not show in chrome (they shouldn’t show on any browser)
https://wellcome.slack.com/archives/CUA669WHH/p1663236385925419?thread_ts=1663233504.218509&cid=CUA669WHH
Where

https://preview.wellcomecollection.org/guides/exhibitions/YyGb2xEAAHzJwTh0/captions-and-transcripts
You will need the exhibition guide toggle turned on to view it

I've been trying this out in firefox but cannot replicate, going to catch up with Alice to see if i can replicate and then fix


Improve diagnostics of unexpected exceptions in AppInsights._onerror

This pull request attempts to improve diagnostics information we log in AppInsithgs._onerror method when encountering unexpected exceptions to help us understand the cause of the following error:
AI (Internal): _onerror threw an exception: {} while logging error: null

In addition to dumping the names and the properties of the unexpected exception, the _onerror method now also writes toString representation of the exception object.

Hi @olegsych, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

 If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


running sublime text 2 in unbuntu 14.04 and ctrl+space marking just stopped working

ctrl+space to push a new mark onto the ring
this used to work great,
I just did the big update --> Unbuntu -> 12.10 -> 13 -> 14.04
and now the ctrl+space is no longer working.
I realized how lost I am without that key binding. The other bindings in the plugin seem to work great.
Any ideas what could have gone wrong?

I remap it to ctrl+@


Progress of "code style changes"

NOTE: This issue is created in order to keep track of code style changes and code base cleanup that I'm working on. For more details, please, refer to one of the issue or PR links that are listed below.
Libraries cleanup (include and lib folders):

cleanup in include folder (PR #92, merged);
cleanup in lib/BlockchainExplorer (PR #65, merged);
cleanup in lib/Common (PR #66, merged);
cleanup in lib/crypto (not doing, it's third-party lib and should be moved outside lib dir);
cleanup in lib/CryptoNoteCore (PR #94, merged);
cleanup in lib/CryptoNoteProtocol (PR #68, merged);
cleanup in lib/Http (PR #71, merged);
cleanup in lib/InProcessNode (PR #69, merged);
cleanup in lib/JsonRpcServer (PR #70, merged);
cleanup in lib/Logging (PR #72, merged);
cleanup in lib/Mnemonics (PR #73, merged);
cleanup in lib/NodeRpcProxy (#74, merged);
cleanup in lib/P2p (PR #77, merged);
cleanup in lib/PaymentGate (PR #76, merged);
cleanup in lib/Platform (PR #86, merged);
cleanup in lib/Rpc (PR #80, merged);
cleanup in lib/Serialization (PR #82, merged);
cleanup in lib/System (PR #83, merged);
cleanup in lib/Transfers (PR #85, merged);
cleanup in lib/Wallet (PR #88, merged);
cleanup in lib/WalletLegacy (PR #91, merged).

Sources cleanup (src folder)

cleanup in config (PR #93, merged);
cleanup in ConnectivityTool (PR #93, merged);
cleanup in Daemon (PR #93, merged);
cleanup in Miner (PR #93, merged);
cleanup in PaymentGateService (PR #93, merged);
cleanup in SimpleWallet (PR #93, merged);

Regressions (that will be fixed in the subsequent PRs):

[fixed] changes in StringBuffer or StringView classes breaks two UnitTests;
[fixed] changes in lib/BlockchainExplorer breaks BlockchainExplorerTests.getPoolStateEmpty; and BlockchainExplorerTests.getPoolStateMany;
[fixed] changes in PR #75 broke test TransactionValidation.gen_tx_check_input_unlock_time, test data was updated to match new logic (PR #84);
[fixed] fixed regressions in lib/P2p that broke test UnitTests.peer_list.peer_list_general (PR #84);

NOTE: I'll close this issue once all code style related changes will be done.

This one was huge, but it is finally completed and can be closed 🎉 🍾 🤘

@nnian please, close this issue 🙂

Sure i will wait until travis is done with it. https://travis-ci.org/qwertycoin-org/qwertycoin


[Android] Enable developers to force Fresco to resize an image

Here's a little background. Resizing is inferior to scaling. See http://frescolib.org/docs/resizing-rotating.html#_
Currently, React Native has a heuristic to use resize when the image is likely to be from the device's camera. However, there may be other cases where a developer wants to use resize. For example, when the developer knows they'll be downloading a large image from a service but the image will be rendered at a small size on the device.
This change adds a resizeMethod prop to the Image component so developers can choose how Fresco resizes the image. The options are 'auto', 'resize', or 'scale'. When 'auto' is specified, a heuristic is used to choose between 'resize' and 'scale'. The default value is 'auto'.
Test plan (required)
In a small test app, verified that the resizeMethod prop properly influences the mechanism that is used to resize the image (e.g. resize or scale).
Adam Comella
Microsoft Corp.

By analyzing the blame information on this pull request, we identified @andreicoman11 and @foghina to be potential reviewers.

Looks good, but I'm worried we might add other types of resizing in the future, e.g. downsampling? Looks like you can't do this on a per-request basis in Fresco (yet?), but in the future it might be possible. So, I'd rather go with an API like resizeType="scale|resize|downsample". Not sure what a good prop name would be, since resizeMode is taken (should've been scaleType probably, too late to change). WDYT?

@foghina Using an enum instead of a boolean sounds like a good idea to me to enable more flexibility in the future. Here are some other possible prop names:

resizeMethod
resizeMechanism

There's another issue to consider when switching to an enum. Currently, RN has a heuristic to decide between "resize" and "scale". If we let the developer pick the mechanism thru an enum prop, do we get rid of the heuristic? Or do we keep the heuristic under an enum value of "auto"?
Based on all of these considerations, here's my preference for the prop's signature: resizeMechasim="auto|resize|scale"
Thoughts?

resozeMethod sounds good.

Or do we keep the heuristic under an enum value of "auto"?

Sounds excellent. Thanks!

@rigdern updated the pull request - view changes

@foghina Thanks for the feedback.

Added one small comment regarding docs.

@rigdern updated the pull request - view changes

@rigdern updated the pull request - view changes

Thanks!
@facebook-github-bot shipit

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.

Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.


Add a determinant solver

Proposal
There is a matrix operator but not a determinant solver. There should be a way to find determinant and inverse

matrix too.

please assign it to me I am a GSoC 2021 aspirant.

It's already there in

Matrix
Single Matrix
Input Fields
Determinant (up to 5x5)

In future I am planning to add more operations for the matrix, if I place all functions in the sidenav, then the list becames so long

oh okay but I guess the tool for finding the inverse of a matrix is not there. Can I work on that

can youreview above suggestion please

can you please checkout above suggestion

Feel free to ask your doubts, if any
Deadline 15 March,2021 (11:59 PM IST)

Do add inverse of matrix option in between these options rather than in sidenav

okay


Update ops.h -- Eliminate a Warning Message of Type Inconsistency

In this source code file, the type of t.NumElements() is a signed integer, while the type of v.size() is unsigned. For the "!=" operator between them, a warning message appears when TensorFlow is compiled with a C++ application.

Hi @tedlz123,
I am going to close this as a duplicate of #21846. If I'm wrong, please re-open.
Thanks!

I signed the CLA!


"mrsk config" exposes env secrets

There will be cases when a user is asked to copy the output of mrsk config for debugging. Currently it's a bad idea since all secrets are exposed in env_args, which also makes the following statement in README false:
Marking an ENV as secret currently only redacts its value in the output for MRSK.

Happy to see redact or similar applies to mrsk config, but the keys should be listed there.

Yes, all env inputs are meant to be listed. But we can add redacting.


Counter signature Regression

This issue was created after discussion on https://github.com/openssl/openssl/issues/8923#issuecomment-666325543.
According to RFC-5652 (https://tools.ietf.org/html/rfc5652#section-11.4):

Countersignature attribute values have ASN.1 type Countersignature:
 Countersignature ::= SignerInfo

Countersignature values have the same meaning as SignerInfo values
for ordinary signatures, except that:

The signedAttributes field MUST NOT contain a content-type
attribute; there is no content type for countersignatures.
The signedAttributes field MUST contain a message-digest
attribute if it contains any other attributes.
The input to the message-digesting process is the contents octets
of the DER encoding of the signatureValue field of the SignerInfo
value with which the attribute is associated.

But the patch #8944 made content-type attribute mandatory when calling CMS_SignerInfo_sign for counter-signature.
So conditions of CMS_si_check_attributes should be changed; or its call should be conditioned to whether or not the SignerInfo is for a counter signature.
This behavior was not present in OpenSSL 1.0.2t and has been observed in (at least) 1.1.1g.

@st-elo Would you be able to provide some openssl test or sample code so that this scenario could be added to a test.
I am not going to be able to address this for a while since I have higher 3.0 priorities. The change itself shouldnt be that hard.
I can review if you want to add a PR. (i.e: look in the unsigned attributes for a countersignature - if there is one then use a different table for the check. Add a second table for the countersignature case. The biggest change would be adding a test)

@st-elo Would you be able to provide some openssl test or sample code so that this scenario could be added to a test.
I am not going to be able to address this for a while since I have higher 3.0 priorities. The change itself shouldnt be that hard.
I can review if you want to add a PR. (i.e: look in the unsigned attributes for a countersignature - if there is one then use a different table for the check. Add a second table for the countersignature case. The biggest change would be adding a test)

ping @st-elo

Yes ! I'll do so ASAP. I'll also give the workaround we use, which lowers controls on content-type attribute for all signerinfo.

Marking as inactive, to be closed at the end of 3.4 dev barring further input


[C++] Error when running Substrait plan using extract function: "argument was not an enum"

Describe the bug, including details regarding any error messages, version, and platform.
I'm writing bindings in substrait-r for the Substrait extract() function.  When I try to run this in Acero, I get the error shown at the bottom of the example R code below.
tbl <- tibble::tibble(x = as.Date("1987-10-09"))
temp_parquet <- tempfile()
arrow::write_parquet(tbl, temp_parquet)

plan_json <- sprintf('{
  "extensionUris": [
    {
      "extensionUriAnchor": 1,
      "uri": "https://github.com/substrait-io/substrait/blob/main/extensions/functions_arithmetic.yaml"
    },
    {
      "extensionUriAnchor": 2,
      "uri": "https://github.com/substrait-io/substrait/blob/main/extensions/functions_comparison.yaml"
    }
  ],
  "extensions": [
    {
      "extensionFunction": {
        "functionAnchor": 2,
        "name": "extract"
      }
    }
  ],
  "relations": [
    {
      "rel": {
        "project": {
          "common": {

          },
          "input": {
            "read": {
              "baseSchema": {
                "names": [
                  "x"
                ],
                "struct": {
                  "types": [
                    {
                      "date": {
                        "nullability": "NULLABILITY_NULLABLE"
                      }
                    }
                  ]
                }
              },
              "localFiles": {
                "items": [
                  {
                    "uriFile": "file://%s",
                    "parquet": {

                    }
                  }
                ]
              }
            }
          },
          "expressions": [
            {
              "scalarFunction": {
                "functionReference": 2,
                "outputType": {
                  "i64": {
                    "nullability": "NULLABILITY_NULLABLE"
                  }
                },
                "arguments": [
                  {
                    "value": {
                      "selection": {
                        "directReference": {
                          "structField": {

                          }
                        },
                        "rootReference": {

                        }
                      }
                    }
                  }
                ],
                "options": [
                  {
                    "name": "component",
                    "preference": [
                      "YEAR"
                    ]
                  }
                ]
              }
            }
          ]
        }
      }
    }
  ]
}', temp_parquet)

arrow:::do_exec_plan_substrait(plan_json)
#> Error: Invalid: Expected Substrait call to have an enum argument at index 0 but the argument was not an enum.
#> /Users/dewey/Desktop/rscratch/arrow/cpp/src/arrow/engine/substrait/extension_set.cc:754  call.GetEnumArg(arg_index)
#> /Users/dewey/Desktop/rscratch/arrow/cpp/src/arrow/engine/substrait/extension_set.cc:875  ParseEnumArg(call, 0, kTemporalComponentParser)
#> /Users/dewey/Desktop/rscratch/arrow/cpp/src/arrow/engine/substrait/relation_internal.cc:549  FromProto(expr, ext_set, conversion_options)
#> /Users/dewey/Desktop/rscratch/arrow/cpp/src/arrow/engine/substrait/serde.cc:160  FromProto(plan_rel.has_root() ? plan_rel.root().input() : plan_rel.rel(), ext_set, conversion_options)

Component(s)
C++

Hmm, I think the component portion of extract is a "required enum argument" and not an "option":
    name: extract
    description: Extract portion of a date/time value.
    impls:
      - args:
          - name: component
            options: [ YEAR, MONTH, DAY, SECOND ]
            description: The part of the value to extract.
          - name: x
            value: timestamp
        return: i64

So I would expect:
"scalarFunction": {
                "functionReference": 2,
                "outputType": {
                  "i64": {
                    "nullability": "NULLABILITY_NULLABLE"
                  }
                },
                "arguments": [
                  {
                    "enum": "YEAR"
                  },
                  {
                    "value": {
                      "selection": {
                        "directReference": {
                          "structField": {

                          }
                        },
                        "rootReference": {

                        }
                      }
                    }
                  }
                ],
                "options": []
              }


Email alerts for contact form

As a site admin, when someone uses the contact form, I would like there to be an email sent to me so that I don't have to keep remembering to check this.

There are two versions of this:

Email alert when an email comes in
Email sent to admins with the actual content of the contact form so that admins don't have to log into the site to see it

https://www.npmjs.com/package/apostrophe-contactmail - very little documentation, doesn't use the existing plugins we're using.


The following NoSuchMethodError was thrown building PlatformScaffold(dirty):

I/flutter (13031): ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
I/flutter (13031): The following NoSuchMethodError was thrown building PlatformScaffold(dirty):
I/flutter (13031): The method '>' was called on null.
I/flutter (13031): Receiver: null
I/flutter (13031): Tried calling: >(0)
I/flutter (13031):
I/flutter (13031): When the exception was thrown, this was the stack:
I/flutter (13031): #0      Object.noSuchMethod (dart:core-patch/object_patch.dart:50:5)
I/flutter (13031): #1      int.< (dart:core-patch/integers.dart:84:18)
I/flutter (13031): #2      int.<= (dart:core-patch/integers.dart:99:37)
I/flutter (13031): #3      new BottomNavigationBar (package:flutter/src/material/bottom_navigation_bar.dart:196:17)
I/flutter (13031): #4      PlatformNavBar.createAndroidWidget (package:flutter_platform_widgets/src/platform_nav_bar.dart:148:15)
I/flutter (13031): #5      PlatformScaffold.createAndroidWidget (package:flutter_platform_widgets/src/platform_scaffold.dart:136:47)
I/flutter (13031): #6      PlatformWidgetBase.build (package:flutter_platform_widgets/src/widget_base.dart:21:14)
I/flutter (13031): #7      StatelessElement.build (package:flutter/src/widgets/framework.dart:3974:28)
I/flutter (13031): #8      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3924:15)
I/flutter (13031): #9      Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
I/flutter (13031): #10     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:3907:5)
I/flutter (13031): #11     ComponentElement.mount (package:flutter/src/widgets/framework.dart:3902:5)
I/flutter (13031): #12     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3084:14)
I/flutter (13031): #13     Element.updateChild (package:flutter/src/widgets/framework.dart:2887:12)
I/flutter (13031): #14     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
I/flutter (13031): #15     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
I/flutter (13031): #16     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:3907:5)
I/flutter (13031): #17     StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:4053:11)
I/flutter (13031): #18     ComponentElement.mount (package:flutter/src/widgets/framework.dart:3902:5)
I/flutter (13031): #19     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3084:14)
I/flutter (13031): #20     Element.updateChild (package:flutter/src/widgets/framework.dart:2887:12)
I/flutter (13031): #21     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
I/flutter (13031): #22     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
I/flutter (13031): #23     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2340:33)
I/flutter (13031): #24     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding&WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:700:20)
I/flutter (13031): #25     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:285:5)
I/flutter (13031): #26     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1016:15)
I/flutter (13031): #27     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:958:9)
I/flutter (13031): #28     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:874:5)
I/flutter (13031): #32     _invoke (dart:ui/hooks.dart:236:10)
I/flutter (13031): #33     _drawFrame (dart:ui/hooks.dart:194:3)
I/flutter (13031): (elided 3 frames from package dart:async)

bottomNavBar: PlatformNavBar(
currentIndex: _selectedTabIndex,
itemChanged: (index) => setState(
() {
_selectedTabIndex = index;
},
),
items: [
BottomNavigationBarItem(
icon: Image.asset('images/icon_nav_bidprice_normal.png'),
activeIcon: Image.asset('images/icon_nav_bidprice_selected.png'),
title: Text('任务')),
BottomNavigationBarItem(
icon: Image.asset('images/icon_nav_transport_normal.png'),
activeIcon: Image.asset('images/icon_nav_transport_selected.png'),
title: Text('运力')),
BottomNavigationBarItem(
icon: Image.asset('images/icon_nav_welfare_normal.png'),
activeIcon: Image.asset('images/icon_nav_welfare_selected.png'),
title: _selectedTabIndex == 2 ? null : Text('福利')),
BottomNavigationBarItem(
icon: Image.asset('images/tab_income_normal.png'),
activeIcon: Image.asset('images/tab_income_highlight.png'),
title: Text('收入')),
BottomNavigationBarItem(
icon: Image.asset('images/icon_nav_my_normal.png'),
activeIcon: Image.asset('images/icon_nav_my_selected.png'),
title: Text('我的')),
],
),

This is my code ,I put BottomNavigationBarItem in PlatformNavBar,then when I run this on android,the bug came out.Does anyone has any idea?

Does _selectedTabIndex have a value when the page loads. Could it be null?
Otherwise could you give a better example with code rather than a screenshot.

If this is still an issue please update with a more complete example. If not I will be closing this issue.

Without more information I am closing this issue. Feel free to reopen with a more complete example


Tic tac Toa Game extension

Is your feature request related to a problem? Please describe.
It's just a new feature , it is not related to any problem
Describe the solution you'd like
In which two participants one is user and other is computer they both play and 3*3 board if each cell continuous are filled with same digit i.e 0 or one then according to digit  win the participant or computer
How to play? 🕹
Controls :
Mouse: Move
Click: cell on board
automatically filled the cell when clicking on it.
R: Retry
can u assign this issue to me @Sulagna-Dutta-Roy

Closing this as already exists here #154


[ai_coder] Create a "hello world"

Let's create a "hello world" program in python that prints a certain text. The text should be somewhat funny and original and related to the topic of LLMs automatically creating pull requests.
Context file hello_world.py

[ai_coder] Opening PR 10

[ai_coder] Worked on it: https://github.com/pereferrera/ai_coder/pull/10

[ai_coder] Worked on it: https://github.com/pereferrera/ai_coder/pull/10

[ai_coder] Worked on it: https://github.com/pereferrera/ai_coder/pull/10


Include 3rdparty/jemalloc (Fix for Ubuntu 18.10+, Debian Stable, etc.)

Description
As of jemalloc 5, jemalloc default build can not be used in libraries that dlopened. However, libmxnet.so is dlopened by Python (ctypes). We can thus not link to system libjemalloc.so but must rather link to a libjemalloc compiled as part of our build process.
jemalloc 5 is distributed as part of Ubuntu 18.10 and higher, as well as Debian Stable.
Users on these systems will be unable to compile MXNet with USE_JEMALLOC=ON (which is the default).
This PR contains the necessary changes.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[X] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[X] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[X] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[X] Include 3rdparty/jemalloc

Comments

We include a patched version of jemalloc that adds CMake support. Once the patch is mainlined, we can switch to the official repo. The patch is currently hosted at https://github.com/leezu/jemalloc/tree/add/cmake-2019. All credits go to @mattsta (see https://github.com/jemalloc/jemalloc/issues/303)

@yajiedesign our existing Windows CI builds do not use jemalloc (-- Could NOT find Jemalloc (missing: JEMALLOC_LIBRARY JEMALLOC_INCLUDE_DIR)). Also it's not mentioned in https://mxnet.apache.org/get_started/windows_setup#build-from-source
So I'll not support building with 3rdparty/jemalloc in this PR on Windows for now.
Same for the edge builds.


RPC Config is not properly inhehrited when a script is loaded

Godot version
3fa8fad
System information
Debian Linux x86
Issue description
#79205 introduces a regression to the way rpc configs are inherited, causing this error:
ERROR: Unable to get the RPC configuration for the function "foo" at path: "/root/Node". This happens when the method is missing or not marked for RPCs in the local script.

even though the function exists both in the server and the client. If you print(self.foo), it even tells you that it's rpc: Node(client.gd)::foo (rpc)
Before #79205 GdScriptCompiler::_populate_class_members used GDScriptCache::get_full_script to access the base script. This causes the parent script to be compiled (if it is not compiled yet), which in turn initializes the rpc_config property with a copy of the base value in gdscript.cpp::_init_rpc_methods_properties
However, GDScriptCache::get_shallow_script does not compile and thus does not initialize the rpc_config of the base script, causing the rpc functions not being included in the rpc config.
Steps to reproduce
Extend a gdscript with a @rpc function annotation and try to do a network call:
server.gd:
extends Node

func _ready():
	var peer := ENetMultiplayerPeer.new()
	peer.create_server(1337)
	multiplayer.multiplayer_peer = peer

@rpc("any_peer") func foo():
	print("Server")

parent.gd:
extends Node

@rpc func foo(): pass

client.gd:
extends "parent.gd"

func _ready():
	var peer := ENetMultiplayerPeer.new()
	peer.create_client("localhost", 1337)
	multiplayer.connected_to_server.connect(func (): self.foo.rpc_id(1))
	multiplayer.multiplayer_peer = peer

Minimal reproduction project
test.zip

CC @anvilfolk

I knew there had to be some regressions with something :) I'll try to take a look sometime soon, but don't let that stop anyone else from trying!
Really good report @Dragoncraft89!
Now the question is how hard is it going to be to get this to work without force-compiling the dependency, which is what led to the other serious bug 🤔

OP, could your issue possibly be related to mine? Here's mine: https://github.com/godotengine/godot/issues/80087.
In my bug, the nodes facing the issue are being instantiated using preload(). I'm wondering if it could be caused by the same problem. Only thing is I'm not sure if we're running the same version of Godot since I don't know what the PR version corresponds to.

I'm coming up on a little more free time so I hope to take a look at this relatively soon! They do sound very related, and it's possible fixing this one will fix that one, so we can try that first :) Thanks for linking the issues!

@marcol1 I just tested version 4.1.1 and my issue does not occur in that release. Therefore it seems the linked PR hasn't made it to that release.
It seems that you experience a different issue. Would you mind uploading a minimal example project to your issue? I'm having trouble to recreate your issue from the description alone and I would take a look if I have something to test :)

@Dragoncraft89 Sure, I'll make one when I get the chance and ping you once I upload it.


Plotting healpix pixels at order < 3 shows borders at order 3

Our current healpix map plotting implementation is limited to plotting pixels at order 3 and above. Any pixels at a lower order are split into their order 3 pixels. This is because the mocpy method we use to generate the matplotlib paths only generates one point per pixel corner, and this breaks down for larger pixels. We can either modify the mocpy method, or combine the paths generated to fix this issue and show lower order pixels without borders inside them.

Closed by #413


Current file path finding method isn't great

Use std filesystem header to improve it.

Branch filesystemUpgrade is working on this. This should also solve issue #6 when finished.

Current main branch file path method only works on my machine. Fix in progress in filesystemUpgrade branch.

Use std filesystem header to improve it.

Turns out no, don't do that.

Fixed in filesystemUpgrade branch


[Shortcut Guide] Support delayed display of shortcuts except for taskbar shortcuts

Summary of the Pull Request
Support delayed display of shortcuts except for taskbar shortcuts as described in #21403.

PR Checklist

[ ] Closes: #xxx
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments
Currently the users can only activate all the shortcut guides at once. However, some users requested a way to activate the taskbar hints only (Related issues: #6265 #8765 #11931).
My solution is to allow the users to chose to show the taskbar shortcuts first and delay the display of the rest contents. This feels natural as the users want to quickly switch the application in focus by using the Win + [Number] shortcut. They can quickly find the number key of interest by pressing the Win key first.
By setting the delay of showing the rest shortcut guides, the screens of the users who only want to check the Win + [Number] shortcuts are not distrupted by the rest shortcut guides anymore.

Validation Steps Performed

If the user sets the delay to zero, then the original behavior takes effect (no delay of the rest shortcuts).

If the user sets the delay to a value larger than zero, the shortcuts except for the tasbar shortcuts will be delayed to display.

If the user chooses to activate by custom shortcut, then the original behavior takes effect (no delay of the rest shortcuts).

@microsoft-github-policy-service agree

Great feature. What about making the background fully transparent in case of delayed showing (when only the taskbar numbers are shown)?

Great feature. What about making the background fully transparent in case of delayed showing (when only the taskbar numbers are shown)?

It is feasible to do that. However, I think the semi-transparent background can make the taskbar numbers more readable and lead the focus of the user to the position of the taskbar numbers.

Interesting. Thanks for picking this up.
Wanna ask to align the text of both settings (Press duration) so they look alike, and to make it more clear what setting is for what area. Actually, if the .header is good, we shouldn't need the .descriptions. For example:

.header

Press duration for global Windows shortcuts (ms)
[   500]

Press duration for taskbar icon shortcuts (ms)
[ 2000]

I notice a difference in animation. In the "original" version there's a short "slide+tranparency", is it possible to apply the same to all sections?

Thanks for your great suggestions. @Jay-o-Way

Actually, if the .header is good, we shouldn't need the .descriptions.

Will remove the .descriptions of the two settings.

I notice a difference in animation. In the "original" version there's a short "slide+tranparency", is it possible to apply the same to all sections?

Yeah, there should be animation when displaying the "global shortcuts".

I'm thinking of two similar and independant parts now. What I would call "global shortcuts" and "taskbar icon shortcuts"

I like this idea. We should do it.
I will update the settings descriptions, apply the animation, and also change the naming in the next couple of days.

@Jay-o-Way Hi, could you please review again? I just pushed the improvements and updated the description of the PR. I also updated the demo gifs as well, please take a look.

At quick glance looks good. I'll look again when I'm back on comp.

Hm, can't seem to activate the Shortcut Guide from this pr on my computer. I must be missing something..?

clever.  This feature took me a second to actually parse what it was doing!

@OkamiWong please fix the merge conflict and then i'd like to get a review done so we can merge this in.  neat.

when you are ready, click the "ready for review" button so it isn't a draft anymore

Works great!
Just one thing - but I'm not sure if it's related to this pr at all... ScG only appears on my primary monitor, not the secondary.

Works great! Just one thing - but I'm not sure if it's related to this pr at all... ScG only appears on my primary monitor, not the secondary.

Thanks for reviewing! Just confirmed that this is not related to this PR by tried the ScG on the latest main branch.

Hi @Jay-o-Way . When will this get merged? I noticed that you approved this PR but it still says the merging is blocked and review is required.

@OkamiWong
First we need an approval from a core team member like @crutkas .


Use buffer prop to calculate when to redraw canvas

This is a rebased version of #913
Overview of PR
The README states that the canvas should redraw when there is 1/2 of the buffer left off-screen on
any side of the viewport. However, the code calculates the redraw based on 1/2 of the viewport and
not the buffer. This PR fixes this. This means that for buffers larger than the default, we
re-render way less often, providing for better performance with large timelines. As it is now, for
many tasks (~1000) the canvas continuously re-renders when scrolling, and the rendering cannot keep
up with scrolling, forcing the items to appear as they jump around a lot.

@LudvigHz thank you, I am curious, did you get a chance to test out the new beta release with your app? have you seen any issues?


Questions about code

Dear Author, I'm very interested in this wonderful work of yours, but due to my weak code ability, I can't find your code of online-clustering part... Could you please tell me which part of this code I should pay more attention to?

Thanks for your interests. Please check here: https://github.com/tfzhou/ProtoSeg/blob/1c4a7784bbce96c06fe72d55255af15e6cf1ca96/lib/models/nets/hrnet.py#L54


Implement enumeration of all simple paths in a CFG

This PR implements path enumeration for CFGs. All possible simple paths in the directed graph from source to sink are generated, as well as single unrolled versions for cycles (to execute the body for-loops and similar constructs at least twice).

The Codacy check fails, because it considers the test class to be too large. Thoughts?

@gandreadis I don't think the 70 line rule makes much sense for test classes, so I think we can ignore it. That doesn't mean our test classes can/should be 1k lines, but 70 is way too few. We should ignore/suppress it. I'll work on adding Detekt to Gradle this evening, then we can suppress some warnings manually and disable Detekt altogether in Codacy.

@JSAbrahams I've added some class-level documentation to the file


Error: “Could not connect to LiveReload server”

Can't get this working .... I used Live Reload + Browser Extensions outside of VS Code without issues.

me too

same issue for me, the server seems not be started


LGTM.com - false positive

Description of the false positive
Report of unsanitized usage of Zip entry.getName used in toString
 public String toString() {
    return ":" + zip.getName() + "(" + entry.getName() + "):";
    | Unsanitized archive entry, which may contain '..', is used in a file system operation.
 }

The warning is clearly not true. The entry.getName() should clearly not be sanitized because it is used in a toString operation. Sanitizing would make diagnosing harder. Secondly, the entry.getName() is used in string concatenations that modify the name already significantly. The result can no longer be used in IO operations.
URL to the alert on the project page on LGTM.com
https://lgtm.com/projects/g/bndtools/bnd/snapshot/34125c8a02ac25b5c16b4aa2f70c1116461e3b81/files/biz.aQute.bndlib/src/aQute/bnd/osgi/ZipResource.java?sort=name&dir=ASC&mode=heatmap#L78

Thank you for reporting this FP.  It looks like the main cause of this FP is the spurious dispatch in Attrs.java from Map::put to PersistentMap.java, which cannot happen.  I'll look into improving our type inference to see if we can rule out this dispatch - it ought to be possible, since it looks like the maps just get assigned through private method calls originating from either Collections.emptyMap() or standard hashmaps.

Deeply impressed :-)

I tried to fix it by cleaning up the PersistentMap code when it calculates the File object. It then cleans up the key for any dirty stuff. However, this seems not to be picked up.

Detecting code patterns that are valid sanitizers is generally tricky, and it's important not to be too general when designing such checks as it may lead to unfortunate false positives.  The ZipSlip query contains a few sanitizer patterns that are common for the use case of unpacking zip files, which is the usual context for the results of this query.  However, in your case sanitizing keys in PersistentMap is not likely to look the same as a normal ZipSlip sanitizer as the needs are a bit different, so it makes sense that we don't pick up on such sanitizer.

I guess the use of Pattern upsets. You, tip what I could add to make it recognize. Name?
BTW thanks for this kind of support 👍 greatly appreciated.

Unfortunately, I don't think there's a good way of changing the code to avoid the alert, since as long as the maps in Attrs.java can't be given a more specific type than Map<X, Y> then it's hard to rule out dispatch to PersistentMap, which is the root of the problem.  As I mentioned above, the real fix is to improve our type inference in the QL libraries, but that's a long term thing, so for now I think the best suggestion I can give is to suppress the alert with an alert suppression comment.


Attribute update perf

A fix we made in attribute._normalizeValue from 7.3 to 8.0 is showing up in profiling. This PR restores the old implementation for size<=4 use cases for performance.
Before:
├─ initialize layers: 34.3 iterations/s ±20.04%
├─ update layers: 13.5 iterations/s ±6.94%
After:
├─ initialize layers: 37.5 iterations/s ±20.41%
├─ update layers: 39.4 iterations/s ±6.43%
Change List

Improve attribute._normalizeValue perf
Bench tests

Coverage decreased (-0.02%) to 83.075% when pulling 71bfbdff21c410b3f3878bf7eafaa7fd244b3de3 on x/update-bench into c7b1b9ec720b0b8cfcb1f978aba828a1307c1d22 on master.


Cannot change quantity on purchase receipt

Hi,
I notice you cannot change the quanity on receipt, what do you propose if a vendor is part delivering the items, so for example if you order 10 items from the vendor and they are delivering 5 in week 1 and 5 in week 2. It seems this modification cannot cope with this which is unusal as its only targetting the cost of the item
Alan

Latest changes for 2021R2 branch allows partial receipt.


readDatapoint.ino crashes on ESP32

Hi,
I tried to run the example on a Adafruit HUZZAH32 – ESP32 Feather Board and switched Serial and Serial1 for better debugging.
Sadly the example keeps crashing when calling VitoWifi.loop(); in the loop.
Any ideas?
Thank you in advance.
Best regards,
E-co

I'll check this evening (only havze a Wemos Lolin32 at my disposal, but the behaviour should be the same). To be honest, I only have tested the esp8266 which is working
Is there any crash info? (stack dump)

Could it be that I didn't mind the pin mappings in the examples?
I didn't specify any pins in the examples to avoid ifdef-clutter. But it renders the examples unusable on the ESP32.
Furthermore, I also didn't implement the pin mapping in the Optolink.
I can override VitowifiClass::setup(HardwareSerial* serial) with VitowifiClass::setup(HardwareSerial* serial, int8_t rxPin, int8_t txPin) and subsequently override Optolink::begin(HardwareSerial* serial); with Optolink::begin(HardwareSerial* serial, int8_t rxPin, int8_t txPin).

Shouldn't this be part of the hardware serial lib?
(https://github.com/espressif/arduino-esp32/blob/master/cores/esp32/HardwareSerial.cpp)

On the Huzzah, you can use RX and TX for the pins as these are defined but Serial1 is not defined/initialized by default.

This is my current setup:

could you test with the test-esp32 branch?
I've only tested myself using the globalCallback-esp32 example.

Compiles nicely and doesn't crash.
Adjusted   VitoWifi.setup(&Serial1, 16, 17); to match 16=RX and 17=TX.
Will check it with the Vito tomorrow.

I tested globalCallback-esp32 myself with a Wemos Lolin32 on a Vitodens 200, with Vitotronic 200, type HO1. I'd love to hear your feedback.
Main developement is on a esp8266 as I try to keep it online for stability testing (which is in doubt for the moment).

The code seems to be stable now - just my board setup seems to be wrong: None of the codes I sent, are recognized. Maybe I got the wrong transmit diode.....

make sure there's no "optical shortcut" and that the optics are aligned. I'll look into the types of parts I have.

I use a SFH309FA (24°) transistor (with black body!) and a SFH487-2 led, both 3mm versions. I followed this guide: http://openv.wikispaces.com/Bauanleitung+ESP8266.

That link was the base of my setup the SFH487-2 seems to be end-of-sales, but I was able to get some at ebay. Will try to better seperate the diodes and better shield the vito receiver from any disturbing light....work in progress

Tried to build a cap to prevent the optical shortcut, but no luck so far.

where does it hang? Does it stay in the "reset" state?
I'm working on the docs with pictures from my setup.
You could also try to power up the heating (toggle mains power) while the optocoupler is attached. On mine, the heating won't start. It's a sign that the coupler works.

Yes, reset state.
Heating starts are usual.
I guess I have to wait for the other LEDs I ordered... ;-)

One step further: my heating doesn't use the 300 protocol, but the KW protocol, which also starts with a heartbeat of 5s, but is stateless. Have to figure out how to "synchronize" to the heartbeat in order to destinguish the heartbeat from the answer...

The KW protocol is on my to do-list.
Closing this one in favor to #4


action_sheet [nfc]: Give more-uniform formatting to list of options

This makes it a bit easier to scan the list.
Inspired by the thread at:
https://github.com/zulip/zulip-flutter/pull/853#discussion_r1721681638
(/cc @sm-sayedi)

Sure, LGTM; please merge at will, or wait for @sm-sayedi's review if you would like.

Thanks for the review! Merged.


Delete Polls When User Is Deleted

Not sure if this is a bug or should just be put as a feature but when users are deleted VIA user profile UI option, their discussions and posts get deleted but their polls don't.
There should be added functionality that when this action occurs, the user's polls in the database get deleted as well.

We either want to keep the poll or CASCADE on delete. Flarum for beta 8 has a DB changes PR, not sure if CASCADE or keeping discussions & posts like reddit does was decided.

@datitisev or @CDK2020 lets get this implemented by the end of this month if possible 🤗

I'm actually facing an issue as well with not being able to delete the user when they've engaged in a poll. See https://github.com/flarum/core/issues/1802#event-2444347556

We probably want to support [deleted] users, so apart from a migration (set null on delete), some code will also have to be rewritten to allow for non existent users's votes.


minor documentation edits and typo fixes

What type of PR is this?
/kind documentation
What this PR does / why we need it:
This contains some minor edits for readability of documentation, as well as a couple typo fixes.
Which issue(s) this PR fixes:
I'm not sure an issue is warranted.
Special notes for your reviewer:
Some of the docs pages are pretty inconsistent with respect to addressing the reader: they use "you can do X" or "here we see Y" arbitrarily. I'd love to converge towards "you", addressing the reader directly. Let me know if I can take on this effort as well.
Does this PR introduce a user-facing change?:
NONE

@fabianbaier Can do, but I'll focus on typography and wording for now. I don't know enough about the specifics yet so I can't really improve the content.


Feature: Update GeoLocation to have Latitude and Longitude as attributes.

Having them as Attributes instead of a string value would allow them to be used on a Map card.
(and potentially do geofencing with cell data enabled devices, or systems with broad enough WiFi range?)

You're on fire :p
For this HASS.Agent needs to support attributes - it's on the list. But yea afterwards the geolocation sensor can be upgraded - also on the list 😁

I guess with that also comes... an Update sensor with appropriate attributes (for Windows Updates)? (Not sure if that would work in the HA framework, as the WU sensor does not work on either of my laptops, and I'm not sure if you can populate it with the correct data)
(And an update sensor for the HASS.Agent itself so we can alert on new agent updates centrally in HA. Especially useful if you monitor multiple systems that you do not regularly log in to)

Yea the WindowsUpdates sensor is plannend to be upgraded when attributes are supported, because currently there's not enough space (255 chars max) to show the names of all pending updates - so it just shows a counter. But it probably won't support HA's own updating mechanism (not really an advantage to do so I think).
The HASS.Agent update sensor is nice, could even be accompanied by a UpdateAgent command so you can automatically update HASS.Agent remotely :)
[hassagent-86], [hassagent-87]

I'm closing most feature requests from github's issue list. They're not ignored, just moved to the HASS.Agent Issue Tracker (you can find your link in a comment above).
That tracker allows me to organise better through what's pending, being done, being released, etc. - instead of one long list, which is beginning to stress me out :p
I will however post a reply here when I've implemented your request, and feel free to still post here when you have any questions/additions.


Addressing multi agent test race condition

What this PR does / why we need it:
This addresses the helm test command overwriting any change in state to a release during its execution. While I'm not certain which behavior is more desired, when other actors execute a helm test while the installation is pending an install with --atomic of --wait a data race occurs on the status.  If the test execution begins while the release is in pending-upgrade and install/upgrade completes setting the status to deployed  before test completes the end status will be pending-upgrade.
fluxcd/flagger#816
Special notes for your reviewer:
While attempting to add unit tests to validate my data race I uncovered a data race detected that failed the tests.  I included a commit to address this.  This work was done a few months ago, but sat on it due to uncertainty of it was a worthwhile contribution.
If applicable:

[ ] this PR contains documentation
[x] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

iiuc, the problem is one "agent" is executing a helm install|upgrade, and another "agent" is concurrently attempting to run a helm test?
Or, have I misunderstood?

Correct.  If you have some CICD agent deploying a change and something like Flagger(which supports Helm webhooks) in cluster that  triggers a test prior to the release agent completing a task you may see the failure in this described scenario.

Rebased to address the circleci config failure.

Rebased again to keep up to date.


How to disable Mixpanel programmatically in a certain condition?

I want to disable Mixpanel programmatically in a certain condition. How to do that? and how to re-enable Mixpanel again?

@xareelee this can be one in several ways depending on what exactly you're trying to do. you could:

Use our A/B testing framework to define a boolean tweak which can be set from the UI. Wrap your .track and .people calls in a handler that only fires when the boolean is true. With this method you can turn tracking on/off from our UI, but the Mixpanel object will still be initialized.

Use APNs (or some other push / message framework) to send a bit of JSON from your servers to the client on startup (probably a boolean as well). Check the value on didFinishLaunchingWithOptions and only init the sharedInstance if the value is true.

Each of these can be done in a variety of different ways, but I think in general this type of thing is the best way to selectively enable tracking.

I need to disable Mixpanel when the user is in China. I've written a IP observer, and when the IP address is detected from China, the Mixpanel will be disabled.
I can disable Google Analytics by setting optOut, but I'm not sure how to opt out Mixpanel temporary.

you can use .register to set "$ignore":true, which will force our servers to drop the event when it comes in. this won't prevent events from being flushed in the first place - to do that you'll need to suppress the .track calls or the Mixpanel singleton entirely. let me know if this helps!

Hi @arittr, thanks for your reply.
I'll try to solve this problem by aspect-oriented programming to make -[Mixpanel sharedInstance] return nil in the runtime to suppress the event tracking.

that sounds good - lmk if you run into any issues with this!

Marking resolved.


add SimpleWebXR integration first draft

XRTK - Mixed Reality Toolkit Pull Request
Overview
SimpleWebXR integration

What's the current status now @StephenHodgson / @Rufus31415 , are we any closer?

I haven't had time to dig into the single pass stuff, but it seems possible. Just need more free time to work on this ⌛


Linux Version 4.0.5 and PECL

I notice version 4.0.5 of sqlsrv and pdo_sqlsrv have been released on PECL ?
I don't see any commit here in the PHP-7.0-Linux branch ?
Diffing 4.0.4 and 4.0.5, it seems most of the change are present (mine), but some are missing, especially the version number.
Also missing: the package.xml used to generate the pecl archive.
Can you please add the missing files / changes, and tag 4.0.5 here ?

I also think the version macros are a bit confusing
   #define PHP_SQLSRV_VERSION "4.0.5"

Unused, but check during package upload on PECL
  #define VER_FILEVERSION_STR "<IP_ADDRESS>"

Used in MINFO and zend_module_entry
So "pecl list" reports 4.0.5, while phpinfo and reflection report <IP_ADDRESS>
Would it be simpler to only use PHP_SQLSRV_VERSION everywhere ?
(of course, same comment about PHP_PDO_SQLSRV_VERSION)

@remicollet should be fixed with our latest release - https://github.com/Microsoft/msphpsql/releases/tag/4.0.6-Linux. Let us know what you think.