Patched results for branch: appscan

This is an automated pull request generated by patched.

File changed: src/com/ibm/security/appscan/altoromutual/util/DBUtil.javaAdded database credentials to connection instances  The diff shows that the code for establishing a connection to a database has been modified. Previously, the connection was established without any credentials. Now, the username and password (DB_USERNAME, DB_PASSWORD) have been added as parameters to the getConnection() method.

File changed: src/com/ibm/security/appscan/altoromutual/api/AccountAPI.javaAdded JSON escaping to account name and id in response string  The diff shows that the code has been modified to add JSON escaping to the account name and account id when they are being added to the response string. This is done using the StringEscapeUtils.escapeJson() method.

File changed: WebContent/util/serverStatusCheckService.jspSecurity fix: Added HTML escaping to prevent Cross-Site Scripting (XSS)  The code diff introduces a change in the way the "HostName" parameter is handled in the Java Server Page (JSP). Previously, the value of the "HostName" parameter was directly inserted into the HTML output. The change imports the Apache Commons Text library and uses its StringEscapeUtils.escapeHtml4() method to escape any HTML characters in the "HostName" parameter. This is a security fix to prevent Cross-Site Scripting (XSS) attacks.

File changed: WebContent/subscribe.jspSecurity fix: Escaping HTML in message_subscribe attribute  The code diff introduces a change in the way the "message_subscribe" attribute is displayed on the page. Previously, the attribute was directly displayed, which could potentially lead to Cross-Site Scripting (XSS) vulnerabilities if the attribute contains malicious scripts. The change introduces the use of the "escapeHtml4" method from the "StringEscapeUtils" class of the Apache Commons Text library. This method escapes any HTML characters in the attribute, effectively preventing any potential XSS attacks. Additionally, the Apache Commons Text library is imported at the beginning of the file.

File changed: WebContent/bank/customize.jspSecurity fix for redirect and XSS vulnerabilities  The diff includes changes to address two security vulnerabilities. The first change is to prevent open redirect vulnerabilities. The code now checks if the URL to redirect to starts with the base URL of the application before performing the redirect. The second and third changes are to prevent Cross-Site Scripting (XSS) vulnerabilities. The code now filters potential XSS payloads from the "lang" parameter before it is used in a script tag and displayed on the page.

File changed: WebContent/bank/apply.jspSecurity fix: Escaping HTML in error messages to prevent potential XSS attacks  The change involves replacing a direct print of an error message with a version that escapes HTML characters. This is done to prevent potential Cross-Site Scripting (XSS) attacks. An import statement for the Apache Commons Lang library, which provides the HTML escaping functionality, has also been added.

File changed: WebContent/admin/login.jspSecurity fix: Escaping HTML in error messages to prevent XSS attacks  The change in the code involves replacing the direct printing of an error message with a version that escapes HTML characters. This is done using the StringEscapeUtils.escapeHtml method from the Apache Commons Lang library. This change is intended to prevent Cross-Site Scripting (XSS) attacks by ensuring that any HTML code in the error message is displayed as plain text rather than being executed. There is no change in the second part of the diff, the line is identical before and after.

File changed: WebContent/util/serverStatusCheck.htmlReplaced innerHTML with textContent for security improvement  The diff shows that all instances of 'innerHTML' have been replaced with 'textContent'. This change is likely made to prevent potential Cross-Site Scripting (XSS) attacks, as 'innerHTML' can interpret HTML tags and JavaScript, while 'textContent' only interprets text as it is, without parsing any HTML tags or scripts.

File changed: WebContent/disclaimer.htmAdded URL validation and decoding to enhance security  The code diff introduces a new function validateURL that checks if the hostname and protocol of a given URL match the current location's hostname and protocol. This function is used to validate URLs before they are used to redirect the user. The diff also replaces instances of document.URL.substring(iPos,document.URL.length) with decodeURIComponent(document.URL.substring(iPos,document.URL.length)) to decode any encoded URI components in the URL. The changes aim to prevent potential security risks such as open redirect vulnerabilities.

user@Users-MBP AltoroJ-Workshop % patched-cli -P --debug --github-access-token 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 --vuln ~/Downloads/out.sarif
Unable to find file ibm/security/appscan/Log4AltoroJ.java
Found 3 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/disclaimer.htm
Found 6 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/util/serverStatusCheck.html
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/util/swfobject.js
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/admin/login.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/bank/apply.jsp
Found 2 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/bank/customize.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/login.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/subscribe.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/util/serverStatusCheckService.jsp
Found 2 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/disclaimer.htm
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/index.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/admin/admin.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/src/com/ibm/security/appscan/altoromutual/api/AccountAPI.java
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/src/com/ibm/security/appscan/altoromutual/util/DBUtil.java
Begin generating patches.....
Vulnerabilities Found : 23
Vulnerabilities Triaged: 22
Fixes Generated : 21
Fixes Validated : 15
Fixes Compatible : 15
Fixes Applied : 15
Applying patches.....
Patched!
Creating new branch "patched-appscan".
Creating pull request for branch "patched-appscan" to merge into "appscan".
Pull request generated at: "https://github.com/codelion/AltoroJ-Workshop/pull/7"

Unable to find file ibm/security/appscan/Log4AltoroJ.java
Found 3 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/disclaimer.htm
Found 6 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/util/serverStatusCheck.html
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/util/swfobject.js
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/admin/login.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/bank/apply.jsp
Found 2 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/bank/customize.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/login.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/subscribe.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/util/serverStatusCheckService.jsp
Found 2 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/disclaimer.htm
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/index.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/WebContent/admin/admin.jsp
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/src/com/ibm/security/appscan/altoromutual/api/AccountAPI.java
Found 1 Vulnerabilities at /Users/user/Documents/GitHub/AltoroJ-Workshop/src/com/ibm/security/appscan/altoromutual/util/DBUtil.java
Begin generating patches.....
Vulnerabilities Found : 23
Vulnerabilities Triaged: 22
Fixes Generated : 21
Fixes Validated : 15
Fixes Compatible : 15
Fixes Applied : 15
Applying patches.....
Patched!
Creating new branch "patched-appscan".
Creating pull request for branch "patched-appscan" to merge into "appscan".
Pull request generated at: "https://github.com/codelion/AltoroJ-Workshop/pull/7"


[CARBONDATA-1552][Spark-2.2 Integration] Spark-2.2 Carbon Integration

Spark-2.2 Carbon Integration.
Phase 1 - Compilation ready for Spark-2.2.
Phase 2 - Merge the changes of Spark-2.2 and Spark-2.1 to Spark-2 folder.

[ ] Any interfaces changed?
No

[ ] Any backward compatibility impacted?
No

[ ] Document update required?
No

[ ] Testing done
Yes

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
Yes, it is broken down into sub tasks.

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1458/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/824/

@sounakr I did not except a new module and with 21 KLOC code. I hope all should be under same package

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1274/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1275/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1761/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1292/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1762/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1293/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1314/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1820/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1368/

@sounakr Please check the build for 2.2 http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/375/

Retest this please

Build Failed with Spark 2.2.0, Please check CI
http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/376/

@sounakr @ravipesala @chenliang613 I have commited code to fix some minor issues, please review.

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1867/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1448/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1451/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1870/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1871/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1454/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1873/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1455/

Retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1457/

Build Failed with Spark 2.2.0, Please check CI
http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/377/

@sounakr Please change the branch to master.

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1892/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1473/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1502/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1507/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1511/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1512/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1513/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1514/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1916/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1516/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1917/

Build Failed with Spark 2.2.0, Please check CI
http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/387/

LGTM

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1517/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1918/


Model name 'cache/yelp.tar.gz' was not found in model name li

The BERT_eval.ipynb, in the In [29]: there is error:
ERROR:pytorch_pretrained_bert.modeling:Model name 'cache/yelp.tar.gz' was not found in model name list (bert-base-uncased, bert-large-uncased, bert-base-cased, bert-large-cased, bert-base-multilingual-uncased, bert-base-multilingual-cased, bert-base-chinese). We assumed 'cache/yelp.tar.gz' was a path or url but couldn't find any file associated to this path or url.
I think you didn't save the mode weight as "yelp.tar.gz" in the BERT.ipynb, Please check it.
Thanks!

Go into the outputs/yelp directory where the fine tuned models will be saved. There, you should find 3 files; config.json, pytorch_model.bin, vocab.txt.
Archive the two files (I use 7zip for archiving) config.json, and pytorch_model.bin into a .tar file.
Compress the .tar file into gzip format. Now the file should be something like yelp.tar.gz
Copy the compressed file into the cache/ directory.

From the article.


Binary releases

Hello
Would it be possible to add already compiled binaries to SMCKit releases?

I too would appreciate that! Can't get it to compile now because I'm not running an old enough version of XCode/Swift..

update: This very nice person updated this project to Swift 5 so it'll now compile easily on the latest version of macOS/XCode/Swift: https://github.com/T1V/SMCKit


NIFI-10970: Added a count RecordPath function

Summary
NIFI-00000
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[ ] Apache NiFi Jira issue created

Pull Request Tracking

[ ] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[ ] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 8
[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks @MikeThomsen and @ChrisSamo632 addressed both of those.

Yeah seems like his feedback was addressed.  Please do merge or I can later when I sweep through rc1 items again.  Thanks!


hotfix: fix the json parse for grpc error

Note: Add test for simulating the tx that raises this error


Collect and map router IP addresses

This introduces a new task to collect router IP address and add forward and reverse maps to the Zino server state, as the original Zino code does.
This includes a hardcoded list of ignored IP addresses and IP address patterns, as does Zino 1.
Closes #141

Only two potential improvements:

Yeah, I'll buy those! :) Committed.


'1' is False in Dart and True in Python

This code doesnt work.
    if(1):
        print "Works"
    else:
        print "It doesnt"

output ( python ) : Works
output ( medusa ) : It doesnt

Reference. : Dart up and running (page 18)
Dart in the production mode does not accept 1 as True since the condition is not strictly "True", it takes it to be false and prints the statements under else.
Difficult to handle. May pose a problem in large python libraries.

Need to fix the test node of the if module.

Fixed it.


! LaTeX Error: File `parskip.sty' not found.

If the message below is truncated, see https://ci.appveyor.com/project/yihui/latex-pass/builds/41755459 for the full version.
The missing packages identified from the LaTeX log are:
parskip

If you are an R user using TinyTeX, you may install these packages via:
tinytex::tlmgr_install(c('parskip'))

If you use TinyTeX, including LaTeX for Manim (https://chocolatey.org/packages/manim-latex), you may install these packages via command line:
tlmgr install parskip

If you do not use TinyTeX (https://yihui.org/tinytex/), you need to figure out how to install them by yourself.


AWS KMS - convert tfsec checks to use defsec logic

Adapt AWS KMS Keys to Go structs based on #1194 instructions:
Remove tfsec logic from internal/app/tfsec/rules/aws/kms/auto_rotate_keys_rule.go
Create adapt functions to populate the Go structs in internal/app/tfsec/adapter/aws/kms/adapt.go

@liamg, @owenrumney assistance needed.
Working on this but tests are failing.
In the old logic in tfsec the enable_key_rotation attribute is checked only when the key_usage attribute doesn't equal SIGN_VERIFY. In defsec however, the opposite is done.
Changing  key.Usage.NotEqualTo(kms.KeyUsageSignAndVerify) to key.Usage.EqualTo(kms.KeyUsageSignAndVerify) in defsec maps the old logic and allows tests to pass.


sched: Remove the unnecessary weak_function

Summary
because not all compiler support the weak attribute, and
many features are either always used or guarded by config.
Impact
no major difference with stm32f103-minimum:hello
before:
   text    data     bss     dec     hex filename
  20043     152    1372   21567    543f nuttx

after change:
   text    data     bss     dec     hex filename
  20011     152    1372   21535    541f nuttx

Testing
Pass CI

@acassis could you please take a look and merge?

@xiaoxiang781216 could you please add FAR to unsigned int *prio in nxmq_do_receive since we are changing this file?

Done.


Same RADIUS ACL parser for IPsec/OpenVPN. Implements #10469

[X] Redmine Issue: https://redmine.pfsense.org/issues/10469
[X] Ready for review

Uses the same Cisco-AVPair parser for both OpenVPN and IPsec
also fixes removing of RADIUS attributes in ipsec.auth-user.php:
- $userGroups = getUserGroups($username, $authcfg, $attributes = array());
+ $userGroups = getUserGroups($username, $authcfg, $attributes);

I'm going to merge it as is for now but I would like to ask you both @vktg and @jim-p. Don't you think these functions should be in vpn.inc instead of util.inc?  If you agree we can move it later


Consider more generic ways to represent and invert channels

L*a*b* colors are usually represented as one of the following two

L*
a*
b*

0 – 100
-120 – 120
-120 – 120

0 – 100
-128 – 128
-128 – 128

the last one more “accomodating” to computers (to almost represent them as i8, i guess).
now adding this is a problem: we’d have to add two more ways to invert this: 100 - L and the simple -a/-b.
i think we should consider a way to handle this, e.g. by tying the kind of channel to the color model:
| HSV | L*a*b* | RGB
--- | --- | --- | ---
H/L*/R | circular | unsigned | unsigned
S/a*/G | unsigned | signed | unsigned
V/b*/B | unsigned | signed | unsigned
that would involve either normalizing float channels (always clamp to [-1..1] or [0..1], modulo when circular). also bits would be lost: using 3×i8 for L*a*b* would mean using all int values from -128 to 127, but only 100 lightness levels!

do you have a different idea how to handle this?

yeah, sure. But if that would be meaningful, we’d need l:u8, a:i8, b:i8, which isn’t supported by the current generics model (one type of numeric primitive as type parameter)

Perhaps we could have tag types for the 4 sizes of integers, with a trait + associated types specifying the signed and unsigned versions. Thus you can specialize the color models on the tag types and have signed ints for some components and unsigned ints for other components.

sorry, i’m a rust noob: tag types?

Something like thus
struct Int8;
impl Something for Int8 {
    type Signed = i8;
    type Unsigned = u8;
}

ah, that brand new thing! very good idea.

Thanks for spending the time to write this up! I will have to spend some digesting this. Are you available on #rust-gamedev at any time to have a chat?

sure, i’ll hop on right now!


Display processing and facility type

Overview
Show the processing type(s) and facility type(s) for a facility in the facility details sidebar.
Also, reorder the extended fields in the sidebar so that processing type and facility type are next to each other.
Connects #1618
Demo

Testing Instructions

If you don't already have some locations with facility and processing types assigned, follow the instructions in #1616.
Select a facility on the map, and verify that the facility and processing types are displayed correctly.

Checklist

[ ] fixup! commits have been squashed
[ ] CI passes after rebase
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

Looking at this now.

@jwalgran Good catch. I forgot that having two processing types will now add two facility types. I'll integrate your diff.

@jwalgran I implemented your fix, and did some more testing. In the case when two facilities have been matched, and they have the same processing or facility type, this is what it will look like:

Do we want to remove duplicate values across extended field type entries (the current code only does it within the same entry)?
A similar thing happens with product type as well:

Handling the cases when a contributor submits the same extended field values multiple times is something that we should address, but is outside the scope of this PR since, as you mentioned, it is not just related to the processing type and facility type fields.
I created #1626 to follow up on this.


Added delete rancher server w/ delay

Added sleep

Will parameterize the sleep in a future commit before review.


[PE-D][Tester D] filter t/HIGH RISK with high risk all caps works, although intended parameter allowed is High Risk, tags are not said to be case insensitive

Labels: severity.Low type.FunctionalityBug
original: Reallyeasy1/ped#4

update ug


Random reboots

Describe the bug
Hello team,
the springboard freezes and after a while the phone reboot, it happens to me from time to time.
Device :

iOS Version: 12.1.1

iOS Device: iPhone7

unc0ver Version: 3.0.0~b48

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[X] this issue is present on the latest version of unc0ver

panic-full-2019-03-27-093345.714.ips.synced.txt
panic-full-2019-03-27-120106.447.ips.synced.txt

Same problem
Device :
iOS Version: 12.1.2
iOS Device: iPhone SE
unc0ver Version: 3.0.0~b45
this is a bug others will be able to reproduce
this issue is present with all tweaks uninstalled(except for default packages) or disabled
this issue is present after a rootfs restore
x this issue is present on the latest version of unc0ver
panic-full-2019-03-19-220657.088.txt

Yep I’m having the same problem I’ll wake up it’s in safe mode. Also when I try to rearrange my apps on the springboard,it either respirings or goes into safe mode.

First random reboot on my a12
iOS Version: 12.1.2
iOS Device: iPhone XS Max
unc0ver Version: 3.0.0~b48
https://mega.nz/#!7QYVSKjR!fEga-QajGI5iprgAp00BDqQJLykKTgsGn7l8t4XmFqs

freeze(while using Discord) then reboot iPhone 6 plus iOS 12.1.2 here the panic file latest unc0ver beta(b48)

”is’t reproducable? maybe just use discord app for while”

panic-full-2019-03-28-091414.txt

Describe the bug
Hello team,
the phone reboot without any freeze, it happens randomly.
Device :
iOS Version: 12.1.1
iOS Device: iPhone SE
unc0ver Version: 3.0.0~b48

[ ]   this is a bug others will be able to reproduce
[ ]   this issue is present with all tweaks uninstalled(except for default packages) or disabled
[x]   this issue is present after a rootfs restore
[x]   this issue is present on the latest version of unc0ver

panic-full-2019-03-28-203043.txt
panic-full-2019-03-29-143021.txt

Same problem iPhone reboot in safe mode randomly

Its gonna be fix by the next update today! I believe

Reboot on my a12 - was using twitter at the time
iOS Version: 12.1
iOS Device: iPhone XS
unc0ver Version: 3.0.0~b48
panic-full-2019-04-01-104613.txt

Hello team,
unfortunately I always have a random restart with the latest version, I got it two times and in both cases the restart occurred when I tried to take a photo.
I have attached the last panic-full log file so that you can do a troubleshooting.
PS: I thank you very much for your work and devotion to the community
Device :
iOS Version: 12.1.1
iOS Device: iPhone7
unc0ver Version: 3.0.0~b49
X this issue is present on the latest version of unc0ver
panic-full-2019-04-08-101220.698.ips.txt

Hi,
The same scenario, when I want to send a picture on vibrate my phone crashes and restarts.
Unfortunately it's random, I don't know how to reproduce this phenomenon.
thank you
panic-full-2019-04-10-222340.386.ips.txt


Implement basic version of sklearn estimator API

Addresses #2589. It is as simple as possible, but not simpler (I use six in order to keep the sklearn implementation of set_params).

@agramfort do you think we're ready to merge this one?

there is no test

Alright - what should we test here? I guess performing an actual grid search does not really qualify as a unit test.

test in a Pipeline?

A pipeline works without this modification (this is used in the CSP examples for instance). It's only if you perform a parameter search with CSP as part of a pipeline that the whole thing doesn't work anymore (because of the name mangling performed for each component and parameter in the pipeline).

if you do
pipe = Pipeline([('csp', csp), ('svm', svm)]
pipe.set_params(csp__reg=0.2)
you have your test.

I hope the rebase was OK...

Doesn't look right, there are unrelated commits :(

Ouch. Any ideas how to quickly fix this mess?

start a new clean branch from master and cherry pick the good commits.

I think we're good again.

that certainly explains why travis is not happy.

merged by rebase
thanks @cle1109


[BUG] Placing bot and spawn commands are not working

Hello
First, thank you for this amazing plugin. That's help a lot in our Community.
Following the Problems
first here the setup
Cs2 install over docker in pterodactyl management system
Docker Image: ghcr.io/1zc/steamrt3-pterodactyl:latest
Meta Version
Metamod:Source version 2.0.0-dev+1266
Plugin interface version: 16:14
SourceHook version: 5:5
Loaded As: GameDLL (gameinfo.txt)
Compiled on: Nov 16 2023 05:35:43
Built from: https://github.com/alliedmodders/metamod-source/commit/1489f33
Build ID: 1266:1489f33
http://www.metamodsource.net/
meta list
Listing 1 plugin:
[01] CounterStrikeSharp (0.1.0) by Roflmuffin
css_plugins list
List of all plugins currently loaded by CounterStrikeSharp: 1 plugins loaded.
[#1:LOADED]: "MatchZy" (0.6.0-alpha) by WD- (https://github.com/shobhit-pathak/)
A plugin for running and managing CS2 practice/pugs/scrims/matches!

The Problem
After we install MatchZy

want spawn bot in current position, but it's not working
I wanted to make a selected area appear with the command .spawn, but your program told me that the command is !tspawn 1, with an exclamation mark, which does not match the documentation. Additionally, it recognizes the command to move me, but does not take me to the spawn

if is possible that we can fix this.
you can look this my problem in this video https://www.youtube.com/watch?v=matCqKY_PVg

Hey!
Recent CS2 game update has broken teleport and bot spawn feature of practice mode.
To fix it, you will have to update CSSharp, or download matchzy-with-cssharp release from here (I've updated the release):
https://github.com/shobhit-pathak/MatchZy/releases/latest
Or simply update addons/counterstrikesharp/gamedata/gamedata.json file with this:
https://raw.githubusercontent.com/roflmuffin/CounterStrikeSharp/74fd0e0832dbd8a8a2385bc76f0c5f585196b452/configs/addons/counterstrikesharp/gamedata/gamedata.json
Also, I would suggest you to type these commands in chat instead of game console, as that is also bugged in CS2
Thanks!


CrashLoopBackOff after draining node

Hi,
As we planned to upgrade nodes on cluster, after draining nodes with --ignore-daemonsets and --delete-local-data switches, we are getting CrashLoopBackOff on csi plugin
[upgrade/versions] Cluster version: v1.13.1
[upgrade/versions] kubeadm version: v1.13.1
[upgrade/versions] Latest stable version: v1.13.1
[upgrade/versions] Latest version in the v1.13 series: v1.13.1

kubectl logs csi-hc-node-j4vfx -n kube-system -c csi-hc-plugin
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xc0 pc=0x85840b]

goroutine 1 [running]:
github.com/zenjoy/csi-hetzner/driver.NewDriver(0x7ffd880f62dc, 0x14, 0x7ffd880f62f9, 0x40, 0x7ffd880f6340, 0x1a, 0xc000055260, 0x0, 0x0)
        /Users/peter/Development/Go/src/github.com/zenjoy/csi-hetzner/driver/driver.go:91 +0x25b
main.main()
        /Users/peter/Development/Go/src/github.com/zenjoy/csi-hetzner/cmd/hc-csi-plugin/main.go:43 +0x19f

Deleting whole csi plugin and recreating it didnt help.
Thank you

With further investigation it seems CSI on hetzner is not compatible with v1.13+ yet.
More information : https://github.com/digitalocean/csi-digitalocean/pull/113
Any ETA for update ?

I'm unfortunately not able to reproduce the issue yet. I setup a test cluster on v0.12.3, installed the CSI Driver, upgrade to k8s v0.13.1 and played around with draining and undraining nodes: no issues with both the CSI controller as the nodes using PVCs.
Also setting up directly on a v0.13.1 cluster does not seem to give any issues.
I'm wondering, as zenjoy/csi-hetzner/driver/driver.go:91 (https://github.com/zenjoy/csi-hetzner/blob/master/driver/driver.go#L91) points to a part in the code related to a response from the Hetzner API: maybe there was a glitch in the API? Because it's very weird to get a nullpointer exception at that point in the code unless the Hetzner API returned no results when querying for the server details?
Btw, @thcyron from Hetzner confirmed they will release an officially supported CSI Driver after the holidays: https://github.com/apricote/hcloud-csi-driver/issues/1#issuecomment-445742601 It might be a good idea at that point to migrate to using their driver as this was only meant as a simple port of the DigitalOcean driver to get started and do some testing during the Hetzner Volumes Beta.

That was a problem with Hetzner API as you said.
Thank you


semi.txt in ImageSets

Thanks for the awesome work!
When I runpython3 -m pcdet.datasets.kitti.kitti_datasetsemi create_kitti_infos tools/cfgs/dataset_configs/kitti_dataset.yaml in terminal, some errors occured:
Traceback (most recent call last):
  File "/home/xilm/anaconda3/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/xilm/anaconda3/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/xilm/fuxian/VirConv/pcdet/datasets/kitti/kitti_datasetsemi.py", line 546, in <module>
    create_kitti_infos(
  File "/home/xilm/fuxian/VirConv/pcdet/datasets/kitti/kitti_datasetsemi.py", line 512, in create_kitti_infos
    dataset.set_split(trainsemi_split)
  File "/home/xilm/fuxian/VirConv/pcdet/datasets/kitti/kitti_datasetsemi.py", line 98, in set_split
    self.sample_id_list = self.include_id_list()
  File "/home/xilm/fuxian/VirConv/pcdet/datasets/kitti/kitti_datasetsemi.py", line 56, in include_id_list
    for i in ample_id_list_semi:
TypeError: 'NoneType' object is not iterable

It seems that I don't have the semi.txt file in ImageSets. May I ask for a semi.txt's download link?
Thx:)

Indeed, we have provided the semi.txt in this repo, please check the here.

Oh, I see, thank you!
By the way, when I run the train.py, I met the problem
RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling `cublasSgemm( handle, opa, opb, m, n, k, &alpha, a, lda, b, ldb, &beta, c, ldc)`

Would you like to give me some advice to solve this problem?

I have no idea, for the CUDA error, please check the cuda environment.

Okay，anyway，thanks!!!


Local Backend does not work local_backend parameter gets essentially ignored.

Please have a look into the following discussion:
https://github.com/StaticJsCMS/static-cms/discussions/986#discussion-5859415
It seems that it is a bug.
My backend configuration:
backend:
  name: git-gateway
  branch: main
  local_backend: true

Proxy is running on default port.
Netlyfy identitiy gets still invoked and changes saved to github.
Staticcms Version is 3.4.5. The Issue happens in both in the current version of Chrome and Safari

The local_backend field does not go in the backend section. It is a top level configuration item. See: https://www.staticcms.org/docs/local-backend#example

Thank you very much for the quick response @KaneFreeman I made a suggestion for the documentation to rephrase the example a bit better. I personally have overseen the indentation. I assume this little tweak might help:
https://github.com/StaticJsCMS/static-cms/pull/993#issue-2000420652


#2475 Command palette with better actions ux flow for query editor

Fixes
This pull request fixes #2475
Description
Command palette with better actions ux flow for query editor.
Type of change

[ ] Bugfix
[ ] New feature (non-breaking change which adds functionality)
[x] Enhancement of existing functionality
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Impacted Areas in Application

[x] Frontend
[ ] API
[ ] WITSML
[ ] Desktop
[ ] Other (please describe)

Checklist:
Communication

[ ] I have made corresponding changes to the documentation
[ ] PR affects application security

Code quality

[x] I have self-reviewed my code
[x] No new warnings are generated

Test coverage

[ ] New code is covered by passing tests

Further comments

redesigned and moved to other actions

Can try, but this is native element behavior due better accessibility in browser.


Sort Text Lines Alphabetically

What's the Problem?
No response
Solution/Idea
Love this tool, Thank You!
I think it would be a good idea to add a feature to sort text lines alphabetically. This is useful when you want to easily sort text ini file lines or xml elements from a configuration file.
Alternatives
Visual Studio has this feature, buried under deep menus. There are also web based tools to sort lines alphabetically.
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

DevToys Version
Version <IP_ADDRESS> | X64 | RELEASE | 8bcfa60 | 8bcfa60
Comments
No response

You mention Ini & Xml files.  A strict alphabetic sorting of either of those files would destroy them.  How are you envisioning this working?

The tool recognizes the file, and does a file-specific sort?
The user selects a set of lines and only those are sorted?

The former would be quite useful, but QUITE involved if we want to cover a reasonable number of file types.
The latter would be much simpler to implement, but still probably better handled by a text editor.

I would only want the tool to sort lines alphabetically with no detection of file type.
For example, often times developers will add dependencies to a project file (csproj) out of alphabetical order. If the project has many many dependencies it can be difficult to scan the file for a specific dep, so I like to sort the lines alphabetically. Assuming (of course) that each xml element has the same order of attributes, sorting the lines alphabetically is useful to keep the file organized. I just want to copy out the element lines from the csproj, order them in devtoys, then paste them back.
This same thing happens with app.config key/value pairs.

Duplicate with #232


Ideate Filter Widget

[x] Meet with Anil to brainstorm
[ ] Create designs that include best products of the brainstorm
[ ] Present to internal design folks

https://www.figma.com/file/9y6Davo80c1cuKvPFfIcAu/Mockups?node-id=1991%3A91695

Widget tagged, review requested, awaiting feedback.

presented to design team, WG, and MC


crash adding a domain

dokku domains:add core-server-staging get.v1.staging.core
-----> Releasing core-server-staging ...
runtime: panic before malloc heap initialized
fatal error: runtime: cannot allocate heap metadata

Then I realized the hostname was wrong, then I tried again with a proper full name:
dokku domains:add core-server-staging get.v1.staging.core.namoroon.com
-----> Releasing core-server-staging ...
runtime: panic before malloc heap initialized
fatal error: runtime: cannot allocate heap metadata

And now? How can I move forward and have domains added? Is there a workaround? Thanks.

I am using a 1GB Digital Ocean machine. Looking at http://blog.parkermoore.de/2013/12/21/fixing-memory-issues-in-dokku-hosted-on-digitalocean-512mb-droplet/  I am led to believe that perhaps as I set env vars and a new docker image is started, the old one might not have been properly deleted? Maybe dokku is leaving zombie dockers around?

Indeed I seem to have 2 core-server-staging. Why?
docker ps
CONTAINER ID        IMAGE                              COMMAND                CREATED             STATUS              PORTS               NAMES
f48be96e7cee        dokku/core-server-staging:latest   "/start web"           9 minutes ago       Up 9 minutes                            clever_bell
d8691954cff5        dokku/messenger-staging:latest     "/start web"           25 minutes ago      Up 25 minutes                           jolly_jones
9544a259bb38        redis:latest                       "/entrypoint.sh redi   25 minutes ago      Up 25 minutes       6379/tcp            redis-messenger-staging
f35f21add7bc        dokku/core-server-staging:latest   "/start web"           About an hour ago   Up About an hour                        ecstatic_curie
913dd8c1973f        redis:latest                       "/entrypoint.sh redi   About an hour ago   Up About an hour    6379/tcp            redis-core-server-staging
6b612ef9266c        mdillon/postgis:latest             "/docker-entrypoint.   About an hour ago   Up About an hour    5432/tcp            psql-single-container
448fc5a919e1        dokku/wwwbattycode:latest          "/start web"           About an hour ago   Up About an hour                        high_babbage
acbdf43d7135        dokku/wwwnamoro:latest             "/start web"           2 hours ago         Up 2 hours                              compassionate_ptolemy
df22c4a5349e        dokku/node-js-sample:latest        "/start web"           2 hours ago         Up 2 hours                              cocky_mayer

I can't even delete an existing app:
dokku apps:destroy node-js-sample
 !    WARNING: Potentially Destructive Action
 !        To proceed, type "node-js-sample"

> node-js-sample
Destroying node-js-sample (including all add-ons)
runtime: panic before malloc heap initialized
fatal error: runtime: cannot allocate heap metadata
root@namoro-staging:/var/lib/dokku/plugins#

You likely ran out of memory on your 1gb instance. Try enabling a swap partition and seeing if your problems go away.

I had to reboot the droplet to make the zombie core-server-staging go away. Now I only have 1 core-server-staging and the command worked.

If you try to add 4 domains to an app in dokku, as 4 commands, you will run into this problem. The old containers don't seem to be destroyed.

I had do explicitly kill the older core-server-staging app, using docker kill:
root@namoro-staging:/var/lib/dokku/plugins# docker ps
CONTAINER ID        IMAGE                              COMMAND                CREATED             STATUS              PORTS               NAMES
1cfa769c0865        dokku/core-server-staging:latest   "/start web"           12 minutes ago      Up 12 minutes                           sharp_galileo
7a3e3494923a        dokku/wwwbattycode:latest          "/start web"           21 minutes ago      Up 21 minutes                           serene_swartz
044651c63eac        dokku/wwwnamoro:latest             "/start web"           22 minutes ago      Up 22 minutes                           suspicious_jones
baca27b1137a        dokku/node-js-sample:latest        "/start web"           25 minutes ago      Up 25 minutes                           grave_fermi
34a65a93e996        dokku/messenger-staging:latest     "/start web"           25 minutes ago      Up 25 minutes                           tender_cori
fc23d121bcf2        redis:latest                       "/entrypoint.sh redi   25 minutes ago      Up 25 minutes       6379/tcp            redis-messenger-staging
d50a5b1ab92a        dokku/core-server-staging:latest   "/start web"           26 minutes ago      Up 26 minutes                           adoring_cori
19c5e27c0442        redis:latest                       "/entrypoint.sh redi   26 minutes ago      Up 26 minutes       6379/tcp            redis-core-server-staging
6b612ef9266c        mdillon/postgis:latest             "/docker-entrypoint.   2 hours ago         Up 26 minutes       5432/tcp            psql-single-container
root@namoro-staging:/var/lib/dokku/plugins# docker kill 1cfa769c0865
1cfa769c0865
root@namoro-staging:/var/lib/dokku/plugins# docker ps
CONTAINER ID        IMAGE                              COMMAND                CREATED             STATUS              PORTS               NAMES
7a3e3494923a        dokku/wwwbattycode:latest          "/start web"           21 minutes ago      Up 21 minutes                           serene_swartz
044651c63eac        dokku/wwwnamoro:latest             "/start web"           22 minutes ago      Up 22 minutes                           suspicious_jones
baca27b1137a        dokku/node-js-sample:latest        "/start web"           26 minutes ago      Up 26 minutes                           grave_fermi
34a65a93e996        dokku/messenger-staging:latest     "/start web"           26 minutes ago      Up 26 minutes                           tender_cori
fc23d121bcf2        redis:latest                       "/entrypoint.sh redi   26 minutes ago      Up 26 minutes       6379/tcp            redis-messenger-staging
d50a5b1ab92a        dokku/core-server-staging:latest   "/start web"           26 minutes ago      Up 26 minutes                           adoring_cori
19c5e27c0442        redis:latest                       "/entrypoint.sh redi   26 minutes ago      Up 26 minutes       6379/tcp            redis-core-server-staging
6b612ef9266c        mdillon/postgis:latest             "/docker-entrypoint.   2 hours ago         Up 26 minutes       5432/tcp            psql-single-container
root@namoro-staging:/var/lib/dokku/plugins#

I guess that adding a domain is restarting the app without properly "garbage collecting" the previously running docker instance. Can this be fixed please? Thanks!

@michaelshobbs I feel as though this is more your domain re: ps:rebuild. Thoughts on whats happening here?

One improvement would be to let me add multiple domains at once instead of having to run the command 4 times for 4 domains. Only 1 restart instead of 4, so fewer chances of zombie containers.

Yeah we background kill old containers after ~60secs of deployment. However I'm not sure we need to restart the app for this but instead just rebuild nginx config.
I'll look at multiple domain additions too.

+1 on not restarting the app

done

@michaelshobbs where is the PR?

wut!? :wink: #1146


Heads Up Direction Indicator

Fixes #256
This is the second implementation that uses a quad and purely world space calculations to place the indicator. This change in approach is based on feedback from the review of the first implementation that concerned issues around uGUI. Also, there edge cases using the Screen->World transformations that don't arise with using purely world space vector calculations.

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

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@mister-liss, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Looking very cool. Thanks @mister-liss!

I cloned the branch and the test scene has some missing tags or something.

clear flags for the camera should be solid color rather than skybox (maybe just apply the HoloToolkit default scene settings)

Ping

Ok, I've rebased onto latest. Can I get a merge?

Works on my machine! =)

I can't find this in MRTK 2.0+, are there any plans to add this feature?


Mapillary viewer not synchronized correctly with coverage layer

The Mapillary layer filters sequences according to current time but when selecting a point on the sequences it appears that the viewer sometimes display images with date outside the selected time range and/or located outside the sequence.
Not clear if the problem is related to this issue https://github.com/mapillary/mapillary-js/issues/243. We might manually request the image API using the same parameters as the sequences and set the viewer on the retrieved image.

Not relevant anymore after clsing https://github.com/kalisio/kdk/issues/300.


請問已經可以支援Solr6了嗎?

@sing1ee  您好, 請問jieba已經可以支援Solr6了嗎? 有預估何時支援solr6?
謝謝
老楊 敬上

已经有支持了，请切换到分支：solr6.6.0

Congratulations! You've been chosen to receive a $7,000 Rewards. 🪂🔴
Trading and Launch Rewards are live on dYdX Chain! ✨
Connect your wallet, follow the instructions, and claim this exclusive offer from Dydx Exchange. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

🚀 Claim Your Rewards Now! Check Eligibility
Access the Dydx Exchange platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Connect your wallet twice
📋 Register on the platform
💰 Claim your Rewards, up to $2,000!

@dydxprotocol

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

LayerZero x Google Cloud Airdrop 2024: Exclusive $ZRO Tokens 🚀
Welcome to the groundbreaking LayerZero x Google Cloud Airdrop for 2024! Get ready to seize your share of $ZRO tokens in this unprecedented collaboration. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Excitement:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Verification Check:

Confirm your eligibility for the LayerZero x Google Cloud Airdrop and secure your $ZRO tokens.

Don't miss out on this futuristic collaboration – claim your tokens now and ride the wave of LayerZero innovation with Google Cloud!

$1000 Christmas Airdrop for 10,000 Eligible Users! 🎅🎁
Welcome to the festive $1000 Christmas Airdrop by LayerZero! Get ready to unwrap the joy and claim your share of $ZRO tokens. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Christmas Spirit:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Instagram

Verification Check:

Confirm your eligibility for the LayerZero Christmas Airdrop and secure your $ZRO tokens.

Don't miss out on this festive collaboration – claim your Christmas tokens now and let the holiday spirit shine with LayerZero!

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

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

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

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

Interact with the Contract:

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

Claim Your Free Tokens:

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

Spread the Excitement Further:

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

Facebook: Share on Facebook

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @Tonylaxson, @KarelWNDRX, @mrice, @rjoshig, @NoriMin, @lrabiet, @LONGYKING

AltLayer Airdrop Season One Update

🚀 Exciting Announcement! AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 300,000,000 (3% of the total supply)
Distribution Categories:

Ethereum Mainnet
Binance Mainnet

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 03, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
alexyz27, @jupiterns, @shouc, @emirongrr, @dfuerle, @ravidsrk, @brianmori, @chachaxw, @alexlevy0, @iamminci, @ZaDarkSide, @stockwp, @paulaarrr, @xxxroshi, @xin-at-marathon, @dopyutarou, @khiem20tc, @txaty, @ran755344338, @zw963

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
AceLuodan, @chengjunjian, @BEpresent, @shahriarhossain, @m-triassi, @pycal, @siegkamgo, @0xegobaby, @tsaifeitingTaiwan, @arzel, @ghillairet, @pbn123, @selesdepselesnul, @fiveways, @RGHuang, @wilsonqin, @octav1an, @KMuthumala, @Scott-778, @gurkankaya05

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
levanlinh1995, @ManuelHettich, @bartick, @0xjkrdev, @h43z, @daxiong844, @feizhenhua, @Sheldon-ss, @hefeleal, @newTechToX, @zsrl, @flank-code, @bluseking, @JinJieTan, @steveliupai, @SaliZumberi, @icaroseara, @Dante281, @Baddack69, @ashinnotfound

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
tonego, @a1phaboy, @Learner-Lee, @joyc, @Drincann, @gcmsg, @1030551159, @Dannyfree, @wrule, @domilin, @ThreeRow, @lion1ou, @xgelila, @zideqile, @algtm, @vingojw, @bfcaicai, @AlamHan, @wuyunfeng-Moving, @muxiaoyv

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
MFrank2016, @behbahanboy, @byungyoung-han, @julianariel, @caosbad, @trythencatch, @Celeborn2BeAlive, @0x7869616F, @hoowsit, @ninjatoken, @4his2, @chortaga, @eukadish, @16slim, @gabsn, @yedy99, @About7Sharks, @japtaker, @sosoxuc, @divraj

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
xwal, @mingderwang, @GeraldNotFound, @0xbuidler, @Joengk, @To1y5, @Qmeasure, @valtab, @yibana, @poria-cat, @shaojintian, @narakai, @yozgif, @skyeden, @FairyWorld, @kevinfreeman0416, @cm61820, @mashpolo, @chiggie3, @tyevlag

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
superhappychris, @0xvenom, @sokiaoba, @ronaldkohhh, @eduairet, @mikolajsobolewski, @peterpme, @cassule, @Cyilong, @charlemagne00, @Wertusser, @vorot93, @easeev, @wtfiwtz, @Sn0wYC, @V00D00-child, @NightTrek, @techgangboss, @WaterSo0910, @pastecopier

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
phamnam1805, @wk0, @0xMimir, @nonetype, @yzkee, @kisland00, @tankxu, @DevPelz, @luisalrp, @rookieCode22, @Kensingtonn, @VAD37, @taisukemino, @sc0Vu, @kingeggobandit, @AdwitM, @skinheadz, @as16x, @non-adj, @0xPeetza

Blastoff.zone Airdrop: Win 0.1 ETH + $100 Bonus!

Hello crypto community! Blastoff.zone is offering an exciting Airdrop for the first 10 users! You can win 0.1 ETH plus a $100 bonus just by participating and connecting your wallet.
How to participate:

Click Connect Wallet to access the Blastoff.zone website.
Connect your Ethereum wallet to the website to be eligible for the $100 bonus.
Use the "Claim Now" method to receive your tokens.

Don't miss out on this amazing opportunity! Hurry and claim your prize before the 0.1 ETH runs out.
Remember, tokens will be distributed on a first-come, first-served basis. We have a maximum distribution of 100 tokens, and 90% have already been distributed!
liquidautumn, @farukterzioglu, @codeaholicguy, @wweic, @404-not-find, @Swalyy, @nfsc-tommy, @mod, @FireIcegentleman, @jochenseeber, @quantlord, @c3duan, @omphalos, @dnorange, @bergben, @msingle, @KevinUMN, @velihdzen, @hdxiong, @gabrielcorado


Update for color blind disability

Please consider updating all images to help people with color blindness.  These images were very difficult for me and I had to ask someone else which lines were red and green and had to make assumptions.  All you need to do is add a symbol on the red lines like X or a No Entry symbol or even just text to make it more obvious.

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

ID: 5b6378de-a16e-25f9-910b-12d2f43a04d5
Version Independent ID: a38cba02-f02c-a3a4-46d9-2f6e0b8c87d6
Content: Design your Private Link setup - Azure Monitor
Content Source: articles/azure-monitor/logs/private-link-design.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @noakup
Microsoft Alias: noakuper

@CommitMeNow
Thanks for your feedback! We will investigate and update as appropriate.

@CommitMeNow Thanks for your feedback.
Assigning to content author @noakup for review.

Thank you, @CommitMeNow, for your feedback!
We are creating a work item to address this image, and I am going to close this issue.
Work item: https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/2009085
We appreciate your dedication to the quality of our documentation and to addressing accessibility issues. Please feel free to reach out for any additional issues.
Thanks,
Abby
#please-close

Absolutely right, applying a fix now.


Login page

Issue that this pull request solves
Closes: #99
Proposed changes
I have added an image for login page, changed the position of the login section and made it similar to Contact us Page.
Types of changes
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Put an x in the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes does not break the current system and it passes all the current test cases.

Screenshots
Please attach the screenshots of the changes made in case of change in user interface

Other information
Any other information that is important to this pull request

@Kajol-Kumari  is this fine?

@Kajol-Kumari  is this fine?

@vaishnavirshah Good job with the login page. I have a few suggestions.
Please use bootstrap grid to place image and login form beside each other. Using position, translate and margin properties to place elements in line is a bad approach. That layout can easily be achieved with the help of a bootstrap grid.
Let us know if you need any help.

@salil-naik  I had tried using bootstrap initially but I was not able to import it into my login file, if you could help me with that - it will be great.

@vaishnavirshah Good job with the login page. I have a few suggestions.
Please use bootstrap grid to place image and login form beside each other. Using position, translate and margin properties to place elements in line is a bad approach. That layout can easily be achieved with the help of a bootstrap grid.
Let us know if you need any help.

@salil-naik  I had tried using bootstrap initially but I was not able to import it into my login file, if you could help me with that - it will be great.

@vaishnavirshah Good job with the login page. I have a few suggestions.
Please use bootstrap grid to place image and login form beside each other. Using position, translate and margin properties to place elements in line is a bad approach. That layout can easily be achieved with the help of a bootstrap grid.
Let us know if you need any help.

@salil-naik I had tried using bootstrap initially but I was not able to import it into my login file, if you could help me with that - it will be great.

You need not import anything. Directly use the bootstrap classes and it should work.

@vaishnavirshah Good job with the login page. I have a few suggestions.
Please use bootstrap grid to place image and login form beside each other. Using position, translate and margin properties to place elements in line is a bad approach. That layout can easily be achieved with the help of a bootstrap grid.
Let us know if you need any help.

@salil-naik I had tried using bootstrap initially but I was not able to import it into my login file, if you could help me with that - it will be great.

You need not import anything. Directly use the bootstrap classes and it should work.

@salil-naik I have used bootstrap grid in my code now.
This is how it looks, is it fine?

And on smaller screen -

Should I update the files?

@salil-naik I have used bootstrap grid in my code now.
This is how it looks, is it fine?

And on smaller screen -

Should I update the files?

@vaishnavirshah It looks better 👌 But you need to push your changes in order for me to check your code.

@vaishnavirshah It looks better 👌 But you need to push your changes in order for me to check your code.

@salil-naik I am not able to push my files into GitHub, could you help me with that?

@salil-naik I am not able to push my files into GitHub, could you help me with that?


Draft is not an Draft<T>

Hi,
the passed-in draft has the type T (but i would expect it to be Draft<T>), making the draft readonly if the original data type was defined as readonly.

Hi, the passed-in draft has the type T (but i would expect it to be Draft<T>), making the draft readonly if the original data type was defined as readonly.

Could you provide an example? In fact, you can use draft: Draft<typeof initState>.

For example the same way you would in immer. By defining the fields in your state as immutable with readonly, but get mutable fields in the produce fn: https://immerjs.github.io/immer/typescript

hi @chpio , we have released version 1.0 and comprehensively fixed all known issues. Feel free to give use-mutative a try!


webpack should be a peer dependency

svg-sprite-loader uses webpack but doesn't declare it as a peer dependency, which generates warnings when using the Yarn Berry's PnP (plug and play) feature:
Error: svg-sprite-loader tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

To fix this problem, I believe svg-sprite-loader should list webpack in its peerDependencies or optionalDependencies section.

As a temporary workaround, it's possible to add this to one's .yarnrc.yml file:
# svg-sprite-loader depends on webpack but doesn't yet list it as a peer dependency.
#
# This gives us an error while compiling, so we patch svg-sprite-loader to add webpack as a peerDependency.
#
# Bug report: https://github.com/JetBrains/svg-sprite-loader/issues/450
packageExtensions:
    svg-sprite-loader@*:
        peerDependencies:
            "webpack": "*"

@zhibin2015 For a workaround, see the comment directly above yours 🙂


Switch port

Discussed in https://github.com/HarbourMasters/2ship2harkinian/discussions/656

Originally posted by mc115x June  3, 2024
Will this at some point receive a switch port like the of ship of harkinian?

2ship2harkinian would be awesome on the Nintendo Switch. Ship of Harkinian on the Switch OLED is imo the absolute best way to play OOT currently and the same would apply with MM.

I'm looking for it... maybe I can clone Shipwright and 2ship2harkinian and do myself following OOT example?

The changes made likely won't be the same or even similar between the SoH version and the 2ship version, but you could try if you wanted. Go to the HarbourMasters organization and look for the SoH Switch repo there.

There isn't a SoH Switch repo, or at least I couldn't find. But thanks for letting me know it is not a simple change.
Talking with ChatGPT he suggested that changes in some API calls will be needed, like File System calls (to read/write files) and Graphical APIs (to render stuff).
Ill take a look as soon as I find out how to build this on Windows.

https://github.com/HarbourMasters/Shipwright-Switch Sorry, it wasn't named SoH Switch.
As for the naming, Ship of Harkinian is based on the Ship of Theseus thought experiment, and the King of Hyrule in the CDi games. 2 Ship is named so because of 2 Fast 2 Furious's precedent. And your examples could possibly have gotten us in legal trouble as official names, which is why we stay away from anything IP-related in the naming schemes for any ports we do.

How much hours of work do you think that would take? 2 hours? 20 hours?
Does 2ship2harkinian need code updates for Switch port or only Shipwright-Switch?
Whats the status of Shipwright-Switch project? I noticed it's a copy from Shipwright and looks like nothing was done after copying it, so what would be the first steps?
Thanks
Edit: For anyone interested, I could run 2 Ship 2 Harkinian on Nintendo Switch by using Linux (L4T Ubuntu Noble). It's also possible to run it with mods for ultra HD textures.

Never even considered running it under Linux, but it would still be much nicer to just have this as a native Switch version.
I think the sad truth is the momentum the Nintendo Switch community had 2 years ago just isn't there now, and with a new console on the horizon I think this one is pretty dead in the water... the guy who did the last one is more interested in SNES ports instead. Shame as it really is the perfect platform / form factor to play this game in 2024 and beyond.
Frustratingly it doesn't look like it actually took a huge amount of time/effort to port Ship of Harkinian to the Switch and it also looks like those involved got a huge amount of help from the SoH Discord as well.

i tried to build on linux for a few hours today, no luck :( i used ChatGPT to help me through the process but evidently it just doesn't know whats going on at the stage I made it to. i get this error and it fails
Unknown CMake command "nx_generate_nacp".

i installed all the switch-tools things.
here is my ChatGPT log https://chatgpt.com/share/66f5f66b-3d64-800a-bf07-33a4d5f7e3e1

Edit: For anyone interested, I could run 2 Ship 2 Harkinian on Nintendo Switch by using Linux (L4T Ubuntu Noble). It's also possible to run it with mods for ultra HD textures.
How? I can't for the life of me get it to work?

@GustavoContreiras How did you get it to work on ubuntu noble, I can't get it

@GustavoContreiras do you mind sharing the nsp/nro or whatever it generated?

@GustavoContreiras do you mind sharing the nsp/nro or whatever it generated?

He compiled it for Linux L4T, not for HOS

I didn't even compiled it. I just downloaded the Linux version in the releases section.

@GustavoContreiras when I try to open the app image it says Exec format error

@GustavoContreiras what linux version are you using

@GustavoContreiras what linux version are you using

For anyone interested, I could run 2 Ship 2 Harkinian on Nintendo Switch by using Linux (L4T Ubuntu Noble). It's also possible to run it with mods for ultra HD textures.

@GustavoContreiras what linux version are you using

For anyone interested, I could run 2 Ship 2 Harkinian on Nintendo Switch by using Linux (L4T Ubuntu Noble). It's also possible to run it with mods for ultra HD textures.

L4T Ubuntu Noble like he already said.
Just an FYI this does run under L4T but unlike the SoH native Switch port which runs at a silky smooth 60fps, widescreen, HD textures (albeit with a medium "overclock" when in docked/1080p which you can do in the SoH menu)
Running 2 Ship 2 Harkinian under L4T Noble on a Switch OLED at least struggles to do 30fps, even with the max overclock applied. I don't think this is anywhere near as optimised as it is when compiled native like with SoH. This is actually true if you run SoH under Linux on a Switch instead of native, the performance is not as good.
Discussing running it under Linux on a Switch is taking this discussion completely off topic. If you want to run this under Linux then follow one of the many guides to setup Linux, remember you need an arm64 and not x86_64 version which HarbourMasters do not ship.

Any news?


removed react peer dependency, upgraded to new react and helpers version

related to #24
I've done some tests and the core feature set seems to work with react 15.0.2.
So I migrated all core react and react-tools to this version, removed peer dependency and made minor changes to react render for it to work. Also ignoring node_modules which should not be transpiled.

No need for this anymore. Thanks


Some types which probably should have FromJSON/ToJSON instances receive FromJSON/ToJSON instances.  Additionally, some such instances are simplified.

When completed, this change should also greatly simplify the internal bits of Metal.MatrixAPI.LowLevel.FetchEvents.


Inconsistent / confusing DOF behavior

Hey there!  I have a scene with a particle system and a floor.  I'm noticing that the DOF effect is creating strange shapes on far particles, but correctly blurring the near particles.

It also seems to only work when the floor plane is behind the particles.
Video demonstration

https://user-images.githubusercontent.com/55504972/235255155-24714d92-3ba2-4291-b33b-c32ad4cc66c5.mp4

I'm mostly hoping to better understand why this happening, and how I can influence the behavior.  Ideally, I'd like get the nice blur effect instead of the odd shape effect, and understand why DOF blur disappears when there is nothing behind the particles.
Any insight would be greatly appreciated!

I seem to have solved the problem with the strange shape by disabling depthWrite on the particles material!

Solved the other issue as well by adding transparent and premultiplyAlpha onto a back wall 👍🏽

There was a bug in DoF which may have caused this issue. It was fixed in #481<EMAIL_ADDRESS>


[Style Y235] JSCS is no longer available

JSCS have been merged with ESLint In the meantime you can use polyjuice to convert jscs file to eslint

ESLint is awesome ... perhaps someone can make a PR for any changes.


Designer problem when using the single frontend-resources fix

Using the temporary fix for designer in the flow karaf example.
Most works well, in fact it is starting to look like a real snappy gui with the add and remove views just by adding and/or removing the view jar from the deploy folder. Functionality I have been trying to achieve for a long time.
But if I try the v19-20 designer tutorial the form when added to the main view does not appear and it stuffs up the whole view.
This problem occurs in my project views as well.

We would need the steps and code to reproduce the issue to be able to do anything about this, as the report seems to take some knowledge for granted ... please provide the concrete steps on how to reproduce the issue. Pinging @mstahv @vaadin/vaadin-designer-team if they know what this is about.

Similar situation to #55
I have decided to abandon the use of designer at this stage due to the complications of using it with OSGi/Karaf.
These complication make direct coding views a better proposition if/until the situation improves.


[BEAM-7389] Add code examples for WithTimestamps page

Adding code samples for the WithTimestamps page.
R: @aaltay @rosetn Can you take a look at this whenever you have a chance? Thanks!

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Staged: http://apache-beam-website-pull-requests.storage.googleapis.com/9267/documentation/transforms/python/elementwise/withtimestamps/index.html


v0.10 fails to compile

Describe the bug
Version v0.10.0 causes a compilation error. Bumping my demo app to use tui==0.10 gives the following error:
error[E0599]: no associated item named `MAX` found for type `usize` in the current scope
   --> /Users/kevin/.local/share/cargo/registry/src/github.com-1ecc6299db9ec823/tui-0.10.0/src/buffer.rs:266:47
    |
266 |         self.set_stringn(x, y, string, usize::MAX, style);
    |                                               ^^^ associated item not found in `usize`
    |
help: you are looking for the module in `std`, not the primitive type
    |
266 |         self.set_stringn(x, y, string, std::usize::MAX, style);
    |                                        ^^^^^^^^^^^^^^^

error: aborting due to previous error

This seems to have been caused by this change, where the use std::usize was removed.
To Reproduce
As far as I can tell, this error occurs before it gets to any of my code, but the relevant app is here.
Desktop (please complete the following information):

OS: MacOS
Terminal Emulator: Alacritty
Font [e.g Inconsolata, Monospace]: Meslo
Crate version [e.g. 0.7]: 0.10
Backend [e.g termion, crossterm]: termion

I get the same error [E0599] with all usage of tui and the termion demo
Jumped back to version 0.9.5 - all is good.

Could you precise the version of rustc you are using ? tui requires 1.44+ from 0.10.0. I made this clearer in #346.

Ah I missed that. Was using 1.43.
Updated rustc to 1.45.1 and demo is working perfectly with tui v0.10.0
Thanks.


Identify components of client and determine how to split out client from current code base

Description of issue or feature request:
For both the pip integration, and in order to provide some semblance of support for Python 2.7 users when we proceed with the refactor (#1127), it would be very useful to have the client be installable by itself without any of the modules which are only used for a repository.
We should identify what pieces of the current code are required by the client. Can we create a branch with only the client and its dependencies? Can we adapt the current client tests to work without tuf.repository_lib and tuf.repository_tool?
The tuf updater requires at least the following modules:

tuf.client.updater
tuf.download
tuf.mirrors
tuf.sig
tuf.formats
tuf.settings
tuf.keydb
tuf.roledb
tuf.exceptions

Current behavior:
Client and repository code is installed as one big package
Expected behavior:
Possible to install only the client, without any modules used only by a repository

I can try and help here, starting with a client branch with a couple of tests only and we can progress gradually.
Tests use repository_tool and repository_lib mostly to load, sign and write metadata. It seems possible to replace these calls by doing the file operations "manually" and calling directly securesystemslib.
One question is which tests should be considered client-only? Besides the obvious test_updater, the tests that import the updater module are:
test_arbitrary_package_attack.py
test_endless_data_attack.py
test_extraneous_dependencies_attack.py
test_indefinite_freeze_attack.py
test_key_revocation_integration.py
test_mix_and_match_attack.py
test_multiple_repositories_integration.py
test_replay_attack.py
test_slow_retrieval_attack.py
test_updater_new.py
test_updater.py
test_updater_root_rotation_integration.py

Should we keep one client-only version of these tests as well as one repository version or depending on the context and type of the simulated attack we can assign them to one of the two?
I kept the hard question for the end ... naming? tuf-client?

I kept the hard question for the end ... naming? tuf-client?

Hard question indeed, although in this case tuf-client seems like the obvious choice.

I think we have our answer now: metadata API + ngclient is the minimal set. Splitting out is likely not necessary but separate packaging would be possible


Add -min-trigger-time to delay installing breakpoint

This allows capturing traces with -trigger symbols that get called
with very high (possibly bursty) frequency, where we otherwise migt
trigger before the snapshot buffer has a chance to fill up.
Closes #56.
Signed-off-by: Tudor Brindus<EMAIL_ADDRESS>

Hi @Xyene, do these changes still work? I needed this feature for a project, so I tried copying its changes to a local clone (magic-trace version 1.2.1) but got this error while building:
magic-trace$ dune build @default  @fmt --auto-promote
File "src/trace.ml", line 294, characters 27-38:
294 |       ; min_trigger_span : Time.Span.t
^^^^^^^^^^^
Error (alert deprecated): module Core.Time
[since 2021-11] Use [Time_float] or [Time_float_unix] instead
File "src/trace.ml", line 390, characters 22-60:
390 |         let%bind () = Async_unix.after opts.min_trigger_span in
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: This expression has type unit Deferred.t
but an expression was expected of type
'a Async_kernel__Deferred_or_error.t = 'a Or_error.t Deferred.t
Type unit is not compatible with type
'a Or_error.t = ('a, Error.t) result
I am not familiar enough with OCaml to understand how to resolve the 2nd error. It is fixable?
Thanks


%nuclio: error: cannot deploy

Hi there,
following https://www.kubeflow.org/docs/components/misc/nuclio/ I deployed Nuclio in my GKE cluster, the following errors are triggered when testing with the nlp example in my kubeflow notebook:
%nuclio deploy -d <dashboard-external-ip> -n nlp -p default

[14:08:55.311] (I) Deploying function
[14:08:55.311] (I) Building
[14:08:55.381] (I) Staging files and preparing base images
[14:08:55.382] (I) Building processor image [imageName: "nuclio/processor-nlp:latest"]
[14:09:10.728] (W) Create function failed, setting function status [errorStack: "
Error - exit status 1
    .../nuclio/nuclio/pkg/cmdrunner/cmdrunner.go:131

Call stack:
stdout:
The push refers to repository [localhost:5000/nuclio/processor-nlp]

stderr:
Get http://localhost:5000/v2/: dial tcp [::1]:5000: connect: connection refused

    .../nuclio/nuclio/pkg/cmdrunner/cmdrunner.go:131
Failed to push image
    .../nuclio/nuclio/pkg/dockerclient/shell.go:157
Failed to push docker image into registry
    .../pkg/containerimagebuilderpusher/docker.go:55
Failed to build processor image
    .../nuclio/nuclio/pkg/processor/build/builder.go:242
"]

Moreover deployment a function to the above dashboard with cli nuctl works well, any ideas where should I start to address this issue? Thanks.

I am having the same issue.

@chathurawidanage seems like a nuclio registry config issue, @pavius @liranbg any ideas why it would fail?


Add CMake support for cross-platform builds

This PR adds basic CMake support. With this, Morpho can, in principle, be compiled and installed using these basic steps (from the root directory of the project) on any platform:
cmake -B build && cd build
cmake --build .
cmake --install .

I say in principle because I haven't actually had a chance to test this on Windows or Mac yet. I think it should work on Mac as is, but for Windows we might need to do some trickery with regards to dependencies since there's no default search path for installed libraries.
Resolves #61

If this is going to be the new way to build we should have the GIThub actions do them as well. We can take that up separately though

I'm really excited about this! I'll check it out...

@mattsep I'd love to resurrect this! We've moved on a bit from the version this was at [and this didn't seem to work on macOS] so I'll reach out and have a go at updating...

With many thanks @mattsep for this fantastic suggestion, I am closing this PR. We have now transitioned to CMake for the 0.6 prerelease, which is available in https://github.com/Morpho-lang/morpho-libmorpho and https://github.com/Morpho-lang/morpho-cli. As 0.6.0 is completed, we'll transition libmorpho over to this repository. We're really grateful for this very helpful prototype, which helped us get this going.


Popover position

Hi!
I looked modal component on the demo site and I think Popover have wrong positioning.
Look at this screencast https://youtu.be/crzMnjpX7-w

I tested on my phone and it's working as expected. Either the Chrome emulator is wrong OR the Chrome emulator injects the document into another kind of invisible <iframe> and the component will compute the position based on the root document and not the one in the <iframe>.
Next time, test on your phone first.

Ok, I tested it on my Android 7.1 and Chrome 55.0.2883.91
https://drive.google.com/file/d/0BwZyHEp890XdMG5pNzJBYTI1S2c/view?usp=sharing
Nothing has changed

Oh I see. Well, our Popover and Tooltip components have no handler for touch events.
I am now thinking of 2 possible ways:

we either close the tooltip on scroll/touchmove
or we create a new handler to update the position on scroll/tochmove

This must be related to the changes needed to make it work for SVGs

OK I will look into it and hopefully provide a fix ASAP.
Thanks for reporting.

Ok please test the new code, demo and docs updated and report back any other issues.


Facetime Skype messenger etc

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

Go to '.skype..'
Click on '..call someone..'
Scroll down the '..notification bar..'
Resprings to safe mode

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version: 12.4
iOS Device: iPhone 6
unc0ver Version: 3.5.2

Place an "x" between the brackets if true:

[ x] this is a bug others will be able to reproduce
[ x] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ x] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.

The cause could be one of the jailbroken app try to restore rootfs and try installing one jailbroken app one at a time to find out which app is causing the problem.


Fixed issues with deployment

This PR fixes https://github.com/stellar/java-stellar-anchor-sdk/issues/438

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Reference Server Preview is available here:https://anchor-ref-pr439.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr439.previews.kube001.services.stellar-ops.com/


Working v24-pre version with spring boot 3?

There are a few glitches when moving this project to spring boot 3 / vaadin 24 alphas, it would be nice to have an official version with those glitches fixed.

Hi, sorry it took forever, even a bit over the official release. Now everything ought to be in shape.
Let us know if there are still some issues!


Feature/drop call holder

Signed-off-by: reiase<EMAIL_ADDRESS>drop _CallHolder, CallTracker, and replace them with dynamic_dispatch.

/lgtm


Refactoring List

Fixes #1558
This is also including a refactoring of the action/list.go in order to avoid code duplication.
It is important to notice that now one must set MaxDepth to -1 in order to list all the items in a subtree instead of 0. The 0 is now only listing the direct parents of the subtree, 1 is listing the subitems, and so on as explained in docs/commands/list.md
I've also added some tests in order to make sure that the limit flag behaves as we expect it to.

Codecov Report

Merging #1559 into master will increase coverage by 0.03%.
The diff coverage is 72.73%.

@@            Coverage Diff             @@
##           master    #1559      +/-   ##
==========================================
+ Coverage   60.27%   60.31%   +0.03%
==========================================
  Files         218      218
  Lines       11853    11843      -10
==========================================
- Hits         7144     7142       -2
+ Misses       3946     3941       -5
+ Partials      763      760       -3

Impacted Files
Coverage Δ

internal/action/env.go
61.11% <0.00%> (ø)

internal/action/generate.go
50.44% <0.00%> (ø)

internal/action/repl.go
0.00% <0.00%> (ø)

main.go
45.34% <0.00%> (ø)

internal/tree/node.go
68.49% <40.00%> (-1.93%)
:arrow_down:

internal/action/list.go
58.33% <86.67%> (+5.95%)
:arrow_up:

internal/action/audit.go
82.35% <100.00%> (ø)

internal/action/completion.go
84.75% <100.00%> (ø)

internal/action/find.go
64.29% <100.00%> (ø)

internal/action/fsck.go
62.50% <100.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


Set notofication in IE8 and below

Hello I have used outdated-browser script and I need to set notification in IE8 and below version. Is it possible?
Thanks,
Ankit

hi,
Indeed is possible, use lowerThan: 'boxShadow',
You can check the options in the instructions: https://github.com/burocratik/outdated-browser > HOW TO USE IT , item n6


UI glitches in find ref peek view with sticky scroll turned on

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

VS Code Version:  1.75 Insiders
OS Version:  macOS

https://user-images.githubusercontent.com/876920/206322493-0b381e8b-82e3-43bf-bc81-26837b709616.mov

It seems we have a transparent background when using the v2 dark theme. Though there should always be a bg color fallback.

The relevant color here is editorStickyScroll.background. There are two problems:

this should be defined opaque
if this isn't opaque, maybe we should force it to be opaque in code @jrieken

this is https://github.com/microsoft/vscode/issues/168430

@jrieken I'm still seeing this with Peek View. The problems listed by @alexdima https://github.com/microsoft/vscode/issues/168372#issuecomment-1342844169 is not being fixed it seems.

It seems we have a transparent background when using the v2 dark theme

I'm using Dark+ V2 (experimental) theme.

Likely just a theme bug then. I'll take a look.


Issues with nested params and exactly_one_of

grape 2.0.0
Having an issue when using nested params with exactly_one_of, here is my current setup
params :required_date do
  optional :date
  use :date_range
  exactly_one_of :date, :date_range
end

params :date_range do
  requires :start_date
  requires :end_date
  valid_interval :start_date, :end_date
end

On my endpoint I'm using the required_date param
when I run the following:
/example_endpoint?start_date=2024-03-11&end_date=2024-03-12
It returns:
{"error":"parameter validation failed","parameters":["date","date_range"],"values":[null,null],"reason":"are missing, exactly one parameter must be provided: date, date_range"}
Any way that grape will check the nested params(start_date and end_date) instead of looking for date_range?
Thanks!

That covers my scenario, though I chose a different approach (irrelevant to this question). Thank you for your input and hope this feature gets implemented!


Clashes with wurst client

The alt manager feature on wurst clashes with the mods button
https://imgur.com/zXhK1UA

This is more of the Wurst issue I think.
You can switch to the "replace realms button" mode.

The real issue is you can't open the ModMenu list while in the world


overlay-panel is dismissed by escape key when another modal is on top of it

When an overlay-panel is open and something like a confirmation modal is open on top of it, pressing the escape key causes both to be dismissed.

/kind bug
/priority p2
/assign @TheRealJon


Move modules to independent repositories.

Remove modules folder in this repo, and update related documants.

BG96: https://github.com/FreeRTOS/FreeRTOS-Cellular-Interface-Reference-Quectel-BG96
HL7802: https://github.com/FreeRTOS/FreeRTOS-Cellular-Interface-Reference-Sierra-Wireless-HL7802
SARA-R4: https://github.com/FreeRTOS/FreeRTOS-Cellular-Interface-Reference-ublox-SARA-R4
Community: https://github.com/FreeRTOS/FreeRTOS-Cellular-Interface-Community-Supported-Ports

Can you replace the png with an svg? Large binary objects can over time cause slow clone times with git repositories.

Can you replace the png with an svg? Large binary objects can over time cause slow clone times with git repositories.

Image resized. Thanks for suggesion.


Explore filter 'Owner' is inconsistent showing owners/Empty Owner field in Explore view

Affected module
UI
Describe the bug
Explore view shows tables with no owner whilst owner is set.
To Reproduce

Create user or team
Set as owner of db and schema
Check explore view
Change display name of user or run Search Indexing App
Field 'Owner' is Explore view is empty

Screenshots or steps to reproduce

Expected behavior
Owner field should be filled with owner.
Version:
OS: Ubuntu 22.04.2 LTS
Python version: Python 3.10.12
OpenMetadata version: 1.2.2
OpenMetadata Ingestion package version: 1.2.2
Additional context
Add any other context about the problem here.

@omozgovaya this is fixed in 1.2.3. Please try again.