Test metrics

This PR added computing test metrics and saving as a csv file during model inference. Sorry for the messy commit history... I'll rebase instead of merge changes from master next time

@smguo thanks! Tests are failing here too, you can see build history here to fix them:
https://travis-ci.com/czbiohub/microDL/builds/103469306

Thanks @jennyfolkesson! Tests are fixed now.

@jennyfolkesson Thanks for making the script work for 2.5D!

@smguo is this PR ready for re-review? It looks like you have some merge conflicts though, let me know if you need help rebasing.

@jennyfolkesson I sorted out the merge conflicts. It's ready for re-review

Thanks @jennyfolkesson! I made the changes as you suggested


Add pre-commit hooks

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


Zlib::Reader: Reading to EOF deadlocks application

Zlib::Reader can deadlock the application if you read to EOF:
require "zlib"

spawn do
  i = 0
  loop do
    puts "[#{i}] looping"
    i += 1
    sleep 1
  end
end

# Wait 3 sec to start
sleep 3

File.open("data.bin", "r") do |file|
  Zlib::Reader.new(file).gets_to_end
end

$ time cr run.cr
[0] looping
[1] looping
[2] looping
^C
real    0m9.508s
user    0m3.162s
sys     0m3.205s

I've created https://github.com/z64/zlib-freeze which contains a sample data blob and the above code that demonstrates the deadlock, as well as an excerpt from lldb in README.md.
Background
I found this while implementing business logic of a websocket protocol that sends chunks of zlib-compressed data over multiple frames, where you buffer each frame received until a "end of flush" binary suffix is read; so you must use a single instance of Zlib::Reader throughout your connections lifetime over multiple frames. Trying to inflate a single blob (shown in the above repo) deadlocked the app.
I suspect the correct behavior here should be to raise an exception; as a workaround I'm infalting into a slice (reader.read(slice)) which will not exhibit this deadlock behavior.

when i use my static crystal analyze tool, i find one bug in zlib flate code, not sure it related here or not, or how to test it (just want to note it somewhere).
https://github.com/crystal-lang/crystal/blob/master/src/flate/reader.cr#97
          ret = LibZ.inflateSetDictionary(pointerof(@stream), dict, dict.size)
          next if ret == LibZ::Error::OK

ret it Int, and compared with enum, this always false.

Interesting! Unfortunately I don't think that applies here, at least I'm pretty sure - I monkey patched read to correct that comparison, as well as a debug p! ret == LibZ::Error::OK.value before that line, and nothing was printed, and the application still deadlocks.

wonder if related to https://github.com/crystal-lang/crystal/issues/4650 ...

Good call, maybe! :slightly_smiling_face:
Reviewing the last few comments it seems like it may be, though the lldb inspections seem to be a bit different. Though what @RX14 said last in that thread sounds plausible. Either way, my zlib-freeze repo 100% reproduces (at least) this issue.. we just need someone who knows how to debug this further. I don't know where to go from here, but happy to dig further if someone points me in the right direction.


Integrate with "sornarcube.com" to measure quality

See detailed instructions there https://about.sonarqube.com/news/2016/09/01/sonarqubedotcom-open-to-aynone.html

https://sonarqube.com/dashboard?id=com.github.vladimir-bukhtoyarov%3Arelease-reactor

done


Cockpit backend frontend integration

Let's start Cockpit-backend from Cockpit-frontend as a subprocess and be able to show the standard streams in the interface :)

@KoenWestendorp do you have some ideas about what we should do with sending the runtime (and carburetor) log to the frontend? My idea was intercepting the stdout and stderr streams and sending them to a websocket, kind of like I did with backend (except I piped the child process' standard streams there).
So far I've been unable to intercept or redirect the standard streams of the process itself (not a spawned child process)
We also could create a custom log function but for me personally that's plan Z, as I think it's stupid to have multiple ways to log with some not working.
I did find the gag crate which is able to mute and write println!() to a file, but it doesn't allow for reading the stream directly.

Hmm, not in a position to look at this right now, I'm afraid. Not able to help out with fixing redirecting the streams. Might be able to take a look at that tomorrow, but don't let that block you.
The problem, if I understand you correctly, is that we currently have no way of redirecting the stream.
Have you tried to simply read the stderror on a thread and sending that over the websockets connection using some channel?

Have you tried to simply read the stderror on a thread and sending that over the websockets connection using some channel?

The problem is that I can't seem to find a way to read io::stdout(). I assume because it implements Write, and not Read.


Determine the method for generating batches efficiently

Sub-issue of issue #598
The fastest solution will be to use a MIN/MAX split of a numeric primary key and compute the batches external to the database in order to generate config files for efficient partitioned execution.
Longer term we may need to look into more complex solutions such as RANK_ORDER and MOD division in order to generate batches across combo analytical keys.
Exit criteria for this ticket should be the generation of multiple YAML files that contain partitioned filters.

TODO:

Methods to save the partitions?:
i. Ask user for config-folder instead of config-file and group YAMLs per table(Have multiple YAML config files)
ii. Save all the partitions in the same config file per table (One YAML config file per table)
iii. Save all the partitions in the same config file for all the tables (Single YAML file for all tables)
Add partition filter with existing filter specified by user
Filters to be added after config-manager object is created to reduce hitting Database with multiple queries
Currently, user specified Filter is not supported for Custom-Query validate??
i. Add filter support
ii. Add the partition filter in the query itself

Later:

Add multiple partition logics: Primary key, Mod + Primary Key, Hash + Primary key + Mod, Hash + Mod


prepare v1.6.0

Codecov Report

Merging #348 (85ccac7) into master (ebb4ab5) will decrease coverage by 0.19%.
The diff coverage is 93.93%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master     #348      +/-   ##
==========================================
- Coverage   96.42%   96.24%   -0.19%
==========================================
  Files          22       22
  Lines        3382     3378       -4
==========================================
- Hits         3261     3251      -10
- Misses        121      127       +6

Impacted Files
Coverage Δ

trafilatura/cli.py
93.24% <ø> (-0.05%)
:arrow_down:

trafilatura/readability_lxml.py
95.40% <ø> (-0.06%)
:arrow_down:

trafilatura/xml.py
98.70% <50.00%> (ø)

trafilatura/filters.py
97.26% <83.33%> (ø)

trafilatura/__init__.py
100.00% <100.00%> (ø)

trafilatura/core.py
97.59% <100.00%> (-0.52%)
:arrow_down:

trafilatura/downloads.py
98.79% <100.00%> (+0.01%)
:arrow_up:

trafilatura/feeds.py
89.68% <100.00%> (ø)

trafilatura/metadata.py
98.23% <100.00%> (-0.30%)
:arrow_down:

trafilatura/sitemaps.py
96.12% <100.00%> (-0.08%)
:arrow_down:

... and 2 files with indirect coverage changes


Moya says that response is nil after coming back to the app from lock screen

Hi,
Here is the case:

return to the app from the lock screen;
nearly immediately (1-2 seconds) send the HTTP request via moya;

Actual Result:

moya returns error Moya.Error.Underlying and says that the response (NSHTTPURLResponse) is nil. NSError contains - error NSError?    domain: "NSURLErrorDomain" - code:<PHONE_NUMBER>3709550611 0x000000012c5d9700

Note:
The code where this debug info caught:
File: Moya.swift
Func: internal func convertResponseToResult(response: NSHTTPURLResponse?, data: NSData?, error: NSError?) -> Result<Moya.Response, Moya.Error>
It could be steadily reproduced only within 1-2 seconds after returning to the application from the lock screen.
Please help.

Very strange, thanks for reporting this. Could you provide some more details so we can reproduce this? Is it on a device or just the simulator? iOS 8, 9, or both? The networking code that demonstrates the problem would be helpful, if you can share it. Thanks again!

Yes. Sure. We will upload our app in a private repo and give you access as we do think that the code should be seen as a whole and not as a except from the context.
In short we have chain of two requests (rxswift). The first one goes to HTTP and works well, the subsequent one calls youtube API and fails with the symptoms I described above.
It is reproduced on iOS 9 only. iOS 8 seems to not having this issue.
For App Transport Security the following settings are applied:
<key>NSAppTransportSecurity</key> <dict>   <key>NSAllowsArbitraryLoads</key>       <true/> </dict>

Hey Ash. Just sent you the code that reproduces the issue. We just broke our heads searching for the cause of the issue but still no luck.

Received the email, taking a look ASAP, probably won't be until the weekend. Will update.

Okay, I've tried taking a look but I don't have a device at the moment to test on. I'll try to take a look this weekend. In the mean time, I'd recommend trying to following trying to call the Alamofire request manually (if you can). I'd like to narrow down if this is a problem with Moya, Alamofire, or NSURLConnection. Can you provide any more details, like what device you're using, wifi status, any server logs you have? Thanks!

Device: any iPhone physical (not simulator) device
wifi connection - excellent. Internet connection 10Mbps (i.e. good)
Server logs. As you could see there are two requests sent in a row. The first one is to our server and it's 200OK. The next one HTTPS sent to youtube. We cannot get youtube server logs.
The important thing - if you will allow ~5+ seconds to pass after the moment you unlocked device and until the moment you pull to refresh for the news - everything will work ok. Also the second pull-to-refresh works ok.

Same problem with my App.
Turns out that if the response is empty, .mapJson() will cause this error.

@kevin5396 Interesting! Makes sense, since NSJSONSerialization would fail with empty data. I'm not sure what the best way to solve this is, maybe extend mapJSON to include a parameter for allowing empty data?

@ashfurrow Maybe a silence option to prevent the error from throwing out but rather just return a nil ?

Makes sense! We should provide a default option, and this'll need to be added to both the RxSwift and ReactiveCocoa extensions too. Anyone available to submit a pull request?

So it looks like a PR to fix this issue would modify the mapJSON function.
func mapJSON() throws -> AnyObject {
    do {
        return try NSJSONSerialization.JSONObjectWithData(data, options: .AllowFragments)
    } catch {
        throw Error.Underlying(error as NSError)
    }
}

We would need to add a new parameter like failsOnEmptyResponse: Bool = true. If it's false and data == nil, we need to return some other value. An empty NSArray or NSDictionary might work, or maybe NSNull(). Not sure, open for discussion.
Oh, and we should test it, too 😉

Ash, sorry what's the "PR"? Possible resolution?

@nickolayl Pull Request 😉

@ashfurrow please re-open the issue. This issue still exists in the latest version of Moya.
Asked on StackOverflow
http://stackoverflow.com/questions/38900522/ios-https-get-empty-response-from-server-after-the-app-returns-back-from-the-l

Okay, re-opening for discussion. Does Alamofire have any similar issues?

Don't know. Need to check. Who can check fast?

The issues list is at https://github.com/Alamofire/Alamofire/issues I'm unavailable to help right now, try searching for the symptoms and see what others have experienced.

Had a quick look, but can't seem to find anything similar in the Alamofire issues.

Since there hasn't been any activity on this thread for some time, I am going to go ahead and close it. Please re-open or create a new issue if you would like to discuss further. Thanks.

@ashfurrow @scottrhoyt
Hey, could you reopen the issue?
Steps to reproduce:

Start upload file - task is .uplaod(url)
Press "Home" button
Wait 2-3 seconds
Open app

It should return error received empty network response

Hey @EvsenevDev, thanks for steps to reproduce! Anyone from @Moya/contributors could try to reproduce the issue?

@sunshinejr looks like iOS cancel uploading in background and Alamofire not supports background tasks for now, but not sure.


Fix NPE for unexceptional-status-for-request?

Fixes (unexceptional-status-for-request? {:unexceptional-status nil} 200) => NPE. I.e. if you have no :unexceptional-status key, this will work fine, but if this key is present then nil will be used as fn

Merged this, thanks!


Spelling mistake in analytics 3.0.0 dashboard

"Statstics" should be "statistics"

Closing Since the issue has been stale for a long time.


Fix issue where SparkRapidsAdaptor could be shut down but not through RmmSpark

This should hopefully fix the errors in https://github.com/NVIDIA/spark-rapids/pull/7822#issuecomment-1448996057

build


Greatest Common Divisor Not working

Describe the bug
When I use the gcd.py to find the greatest common divisor of two numbers, it is not giving the correct output. The output seems to be addition instead of finding gcd.
To Reproduce
Steps to reproduce the behavior:

Run python gcd.py
Give 23 and 10 as the  two numbers
The answer would be given as 33

Expected behavior
The answer should be 1.
Screenshots

I would like work on this issue

Shall I work on this?

Fixed gcd#13

i would like to work on it

gcd great common divisor by doing with 10 we get finally 1 as out put

gcd great common divisor by doing with 10 we get finally 1 as out put

ok

I have committed only those files that are required.
2.I have tried commit messages concise and reflective of the code committed.
3.I have used a branch name reflective of the issue.
If there is relevant issue for the PR, I have used closes # to auto-close the issue once PR is merged.

Detailed description
No function or code is there to calculate gcd , file was just adding values and printing, without making any calculations.
Test plan (required)
We can use any set of 2 positive numbers and it produces the right result.
Closing issues
closes https://github.com/NirmalManoj/aim-gsoc/issues/2

i would  like to work on this

Yes. Thank you
On Sun, 19 Mar, 2023, 4:14 pm Ajaychettamaina2004, @.***>
wrote:

i would like to work on this
—
Reply to this email directly, view it on GitHub
https://github.com/NirmalManoj/aim-gsoc/issues/2#issuecomment-1475200833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A54TFK4BUS3UX63EAWA4JJTW43PQ3ANCNFSM6AAAAAAUGCELH4
.
You are receiving this because you commented.Message ID:
@.***>


Error Messages

When I start the computer using the os it says system program problem detected. It said something about gnome-session-client and compwiz or something like that. I really dont know what it means and am wondering if my computer is dying or something. If you can help or know what is causing this then please tell me.

hs_err_pid29513.log
(This is an error log that might help)

@TheMinigun,
To help us help you troubleshoot a problem we ask that you please show us the out;put of:

sudo edit-chroot -all

The log you linked above clearly states:

"A fatal error has been detected by the Java Runtime Environment:"

Perhaps you first need to search for answers on StackExchange or pursue other Linux resources.
Hope this helps,
-DennisL

sudo edit-chroot: command not found.

@TheMinigun,
Then first launch your crouton desktop, open a terminal session and show us the output of:

croutonversion

Hope this helps,
-DennisL


Feature/tutor assessment tracking

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Server: I added multiple integration tests (Spring) related to the features
[x] Server: I added @PreAuthorize and check the course groups for all new REST Calls (security)
[x] Server: I implemented the changes with a good performance and prevented too many database calls
[x] Server: I documented the Java code using JavaDoc style.
[x] Client: I added multiple integration tests (Jest) related to the features
[x] Client: I added authorities to all new routes and check the course groups for displaying navigation elements (links, buttons)
[x] Client: I documented the TypeScript code using JSDoc style.
[x] Client: I translated all the newly inserted strings into German and English

Motivation and Context

Currently, changes of automatic feedback in text-exercises is not tracked. This PR introduces the connection to an external tracking component placed in Athene. There the data is collected and will be analysed at a later point. This way there are no modifications to the Artemis database scheme and it has no impact on the performance of the Artemis server.
Description

Server

Add profile "athene"
Create a jwt token and add an extra header to the assessment route when profile "athene" is set

Client

Store the jwt token in the participation
Send a tracking request (Fire & Forget) with the result when the new header is set and the feedback is loaded, saved or submitted
Route the tracking request directly to athene using nginx (NOTE: This is done on the server, you cannot see it in the code!)

Steps for Testing locally

Start Artemis locally with "ARTEMIS (SERVER & TEXT CLUSTERING)

Log in to Artemis
Navigate to Course Administration
Assess a submission for a text exercise
See that tracking request is send in your browser dev tools (There will be an error because nginx is not running locally)

Nginx Config:
location /athene-tracking {
        proxy_pass https://athene01.ase.in.tum.de/tracking;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

@krusche I've adressed all the issues you mentioned.

Added description about how & where the request is send
Implemented client & server tests
Improved the JavaDoc / JSDoc
Moved the key into the TextSubmission

I will take a look as soon as possible. In the mean time, can we get reviews and tests by other developers as we do it usually?


Draft: Publish ACS CLI version 2.4.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

This is a test PR. Closing for now.


Automated tests

I added some test files in my pull requests, but there's no automation for testing.  Could we collect some ideas how to test?  Not sure whether there is an existing testing framework that fits the needs of this project.  (Sorry for the lengthy issue - IMO tests will be important for sustainability.)
I think creating individual test files for individual problems is sensible. There are different kinds of tests I can think of:

Assert that the file runs smoothly through conversion and Lilypond processing (e.g. for this commit)
Assert that the output of the conversion fulfills certain conditions (like in this commit where the output should contain the string testlyrics)
Assert that the XSLT conversion succeeds or fails (the latter if it receives some bogus input or something it does not support)
Possibly assert that the graphical output (either PDF, PS, or SVG) fulfills certain conditions (but usually the generated Lilypond code should be easier to analyze than graphics)

So, how could one organize these different kinds of checks?  We could add one or multiple <annot> elements with type="assert-test" in the header of each test file.  These <annot>s should describe the tests to be performed. For case 2, it might look like this:
<annot type="assert-test" subtype="ly-analyze">
    grep 'testlyrics' "$ly"
</annot>

subtype="ly-analyze" would indicate that the script supplied as content will analyze the generated Lilypond file.  If that command exits with code 0 (which grep does if it finds testlyrics), the test passes, otherwise it fails.
The different @types for the different kinds of tests I listed above could be:

ly-success
ly-analyze
xsl-success, xsl-fail
svg-analyze, ps-analyze, pdf-analyze

For xsl-success and xsl-fail, only the XSL transformation would have to be performed. For all others, Lilypond would have to be run as well.
A script for testing could look like this:
#!/bin/bash

# Generates a test script from the MEI test files
# and immediately executes it by piping to `source`.

saxonb-xslt \
  -xsl:generate-test-script.xsl \
  -s:generate-test-script.xsl \
  testfiles="$(ls -1 test/*.mei)" \
  | source /dev/stdin

We'd have to write an XSLT that takes all the test MEI files and turns the <annot> elements into commands for testing.
Should I give it a go?

Sounds like a fine idea!
I started off with a very basic script just converting all MEI files and running LilyPond.
Please do whatever you think is appropriate.
Just the <annot> wouldn't make me happy. How 'bout this:
We use the <seriesStmt> (see Guidelines 2.1.5) for basic information on those files (title: MEILER test suite; using the <identifier> and stuff.
For more detailed test commands the <extMeta> should be used (as those are indeed some kind of extended metadata on what the file is for).
Could you do that?

I find <annot>s more convenient than <extMeta> for two reasons:

<annot> is a much more powerful element.  The @type/@subtype system is useful for test categories.  <extMeta> only has @label.
<annot>s can be put in different places.  I did that as an example in my color pull request to make clear which test is responsible for which color.

What's your thought behind using <seriesStmt>?  My tendency as the lazy programmer that I am is to keep everything as minimal as possible, considering these tests aren't actually musicologically useful data.

The idea of <extMeta> is to fill it up with non-MEI markup. For example:
<extMeta>
  <test xmlns="http://www.meil.er/xml">
    <command system="linux">grep 'testlyrics' "$ly"</command>
  </test>
</extMeta>

<seriesStmt> should just state that this is a file for testing purposes (from the MEILER project) and not actually musicologically useful data.

Ah, I didn't notice <extMeta> could contain arbitrary markup.
My idea was to just use bash which should work on Mac, Linux and also Windows 10 (though I have no Windows 10 to test whether Lilypond and Java are already working properly).  I don't think we should distinguish between system="linux", system="windows" and system="mac".
Bash has the disadvantage that it might not work as flawlessly cross-platform as e.g. Python. There are some minute differences between certain commands like sed (not bash itself) in Mac and Linux/Windows environments.  But with bash, it's more straightforward to glue XSLT, Lilypond and tests together.


WebSocket extensions decide whether to be part of handshake or not

@dpwspoon Ready for one more round of review/merge


Added support for omitting fields

exciting stuff! I've wanted this feature for a while; just haven't found the time to implement.
One question -- why use of different arguments names ("omit" vs "exclude") for passing via query parameters vs passing directly into a serializer class constructor? Seems like using one would make the API more consistent?

This was something I wasn't too sure about. When you specify a default include in the serializer options, it feels natural that any include in the query params would be treated as an overwrite. In this case, I was using an options exclude in the capacity of removing any superfluous parent links in the nested serializer, and it felt more intuitive that any query param omit would be additive rather than an overwrite in this case (seemed a little strange that more fields would appear and you had to explicitly add them back!) However I also appreciate that it feels cleaner that the two operations would behave the same and it gives the client full control.

Closing this ... this feature has been in for a while now.


BUG: optimize: check tolerance >= 0 in brent

Fixes gh-4140.

@dlax Would it be a bad thing to merge this as a hotfix, and leave the general issue for later? I could add a comment to indicate that the code may be broken.

Lars a écrit :

@dlax https://github.com/dlax Would it be a bad thing to merge this as
a hotfix, and leave the general issue for later? I could add a comment
to indicate that the code may be broken.

Probably not a "bad thing". I was just suggesting a possible better way
to solve the issue but I perfectly understand that you may not have the
resources for this.

@dlax Pushed a comment in 00120b4c9cf06b70243639e6e5dd0d38fec870f0.

I saw an ok from @argriffing and interpreted @dlax's comment as an ok too, so I merged.


[$250] Login - Incorrect page with an incorrect MC is shown when navigating to an invalid MC link

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.58-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5190900
Email or phone of affected tester (no customers): https://expensify.testrail.io/index.php?/tests/view/5190900
Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify
Enter an existing Gmail account on the login page
Navigate to the email inbox of the account and open the validate email and copy the link
Paste the link in an incognito tab (or another chrome account) and change it to staging
Modify the last portion of the link by a character, i.e. If the original link is like this https://staging.new.expensify.com/v/7453760/123884,
change a single character > https://staging.new.expensify.com/v/7453760/123888
Hit enter and navigate to the link

Expected Result:
The user is redirected the "Magic code expired" page
Actual Result:
"Here's your magic code" page appears with an incorrect magic code
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/a400680b-f60e-477a-8a7d-e071f306358a
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021854430009812006082
Upwork Job ID:<PHONE_NUMBER>812006082
Last Price Increase: 2024-11-07

Issue OwnerCurrent Issue Owner: @DylanDylann

Oh interesting - this is reproducible, I'm going to move this to convert and set this external. It might need to be internal.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Incorrect page with an incorrect MC is shown when navigating to an invalid MC link
What is the root cause of that problem?
New feature
What changes do you think we should make in order to solve the problem?
To be able to see the Magic Code Expired page in this case, we add code to check the validation of the code and display the expired validation code modal for cases with an invalid code.
https://github.com/Expensify/App/blob/f05be952684549101854d0317dc649acf18c5f6e/src/components/ValidateCode/ValidateCodeModal.tsx#L30
// src/components/ValidateCode/ValidateCodeModal.tsx#L37
if (!code.trim() || !ValidationUtils.isValidValidateCode(code)) {
    return <ExpiredValidateCodeModal />;
}

POC
https://github.com/user-attachments/assets/49b32f13-f196-4393-b1a8-96b8a2362438

Proposal
Please re-state the problem that we are trying to solve in this issue.
"Here's your magic code" page appears with an incorrect magic code
What is the root cause of that problem?
There is no Onyx data in the incognito tab. This causes shouldStartSignInWithValidateCode to be false, and signInWithValidateCode to ben't called, which causes the autoAuthState to ben't updated to CONST.AUTO_AUTH_STATE.FAILED.
https://github.com/Expensify/App/blob/27b4786cceb9f44fad1f065b06ee56dc046a9716/src/pages/ValidateLoginPage/index.website.tsx#L32
https://github.com/Expensify/App/blob/27b4786cceb9f44fad1f065b06ee56dc046a9716/src/pages/ValidateLoginPage/index.website.tsx#L44-L59
Finally ValidateCodeModal is shown.
What changes do you think we should make in order to solve the problem?
If the magic code is invalid, we should display a helpful text to the user instead of displaying the expired page. In ValidateCodeModal, we can use isValidValidateCode function to check the validate code is valid or not. If it's invalid we will change the description here.
https://github.com/Expensify/App/blob/eff7bffb673fb4c2f1d89b1c53a9bc1e6a799c1b/src/components/ValidateCode/ValidateCodeModal.tsx#L47-L53
It looks like this and if we click on Go back to sign in here it will redirect to the login input form.

### What alternative solutions did you explore? (Optional)

@DylanDylann can you check out these proposals when you have a moment? TY!

@mkzie2's proposal looks good to me
Note for the PR phase: We can display a Not Found Page instead of designing a new description for this case. Because on the FE we can't validate exact the magic code, we only can check the shape of the magic code based on regex. So in cases where users try to edit the URL, I would prefer to display the Not Found Page
🎀 👀 🎀 C+ Reviewed

@DylanDylann Can you double-check the expectations for this ticket? They want to redirect to the 'Magic code expired' page, so my proposal follows that approach. I considered changing the text to 'invalid' to display in ValidateCodeModal as well, but after reviewing the expectations, I didn't include it in my proposal. But if we want to display the 'inValid' text, we need to confirm with the design team before deciding.

@Expensify/design Could you help to confirm the expect on this issue?

The user is redirected to the "Magic code expired" page (as in OP)
The user is redirected to the Not Found Page
Creating a new page with a new design for this case like this

IMO, because on the FE we can't validate exact the magic code, we only can check the shape of the magic code based on regex. So in cases where users try to edit the URL, I would prefer to display the Not Found Page
cc @dangrous

Hmm. This seems like a bit of a odd use case, but it feels more right to show "Not found" or "Something went wrong" instead of saying the mc code has expired cause it technically hasn't right (the user just tampered)? I'd probably say 2 in this instance then given this doesn't seem like something we'll run into a lot.
Keen to hear what the other @Expensify/design 'ers think

Yeah, I tend to agree with that too.
It seems like super old magic code links still work, even though the magic code itself won't work. So I think I would just make it so that any URL that is accessed where we aren't using 6 digits in the last portion, we should just redirect that to a 404 not found page.

@dangrous Since all design teams agree with option 2 (Display the Not Found Page), please help to review this comment https://github.com/Expensify/App/issues/52124#issuecomment-2466159514. I also updated the alternative solution with the expected.

Proposal updated

Add an alternative solution to show a 'not found' page

yep, this makes sense! Let's go with @mkzie2 (as the first updated proposal) and display that Not Found page. Thank you!

@DylanDylann On native we don't display the validated code modal, should we display the not found page in the case of this issue or not?

@mkzie2 If so, we should do nothing on native

@DylanDylann The PR is ready.

PR in staging - https://github.com/Expensify/App/pull/52407

BugZero Checklist:

[ ] [Contributor] Classify the bug:

Bug classification

Source of bug:

[ ] 1a. Result of the original design (eg. a case wasn't considered)
[ ] 1b. Mistake during implementation
[ ] 1c. Backend bug
[ ] 1z. Other:

Where bug was reported:

[ ] 2a. Reported on production
[ ] 2b. Reported on staging (deploy blocker)
[ ] 2c. Reported on both staging and production
[ ] 2d. Reported on a PR
[ ] 2z. Other:

Who reported the bug:

[ ] 3a. Expensify user
[ ] 3b. Expensify employee
[ ] 3c. Contributor
[ ] 3d. QA
[ ] 3z. Other:

[ ] [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:

[ ] [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:

[ ] [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

Regression Test Proposal Template

[ ] [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:

Regression Test Proposal
Precondition:

Test:

Do we agree 👍 or 👎

Sorry for the delay here - coming back from ooo.
Regression test created - https://github.com/Expensify/Expensify/issues/449534
Payouts due:

[X] Contributor: $250 @mkzie2 (paid in Upwork - https://www.upwork.com/nx/wm/workroom/38999061/overview)
[X] Reviewer: $250 @DylanDylann (paid in Upwork- https://www.upwork.com/nx/wm/workroom/38999015/overview)


[MSKINS-195] Added the missing protocol part back into the button.

Simple fix to restore the Twitter button

I've closed my commit, after being frequently insulted by [~michael-o] I'm then presented with a requirement I view as bad practice by [~sjaranowski] who can't justify their position with reason. I am not going to waste additional effort trying to help a project that doesn't want it.

Demanding is not insulting.


CustomEvents not sent when navigating

We have a site that needs to log lots of custom events from Javascript for actions that do not hit the MVC backend. However, most of these are not sent, despite calling trackEvent() and then immediately calling flush().
In the network tab of dev tools, when tracking the event, and then navigating away, I can see the track call as (canceled) and then the page navigates and the event is not logged in App Insights. Sometimes the events make it, other times they don't.
Various comments seem to say that flush is not synchronous to Azure, which seems a bit pointless, since that is the only time I would ever need to use flush. Also, why does the event onwindowunload not send the remainder of the queue to App Insights before navigating away?

Further info. It seems that if the call is fast enough, it succeeds but if it takes longer than about 500ms, it gets cancelled.

@lukos we do hook into the unonload event to try to send the items in queue asynchronously to avoid any user experience impact. This works to a certain degree  in most browsers except firefox. This is controlled by configuration disableFlushOnBeforeUnload (this defaults to false and hence we do try to hook up to onunload event to send.


[BUG] GpuKryoRegistrator fail on Rapids22.08

Describe the bug
When starting a SparkSQL window and formulating Kryo and GpuKryoRegistrator configuration items, has java.lang.NoClassDefFoundError appears on Rapids22.08: org/apache/spark/sql/rapids/execution/ SerializeConcatHostBuffersDeserializeBatch, but this problem did not occur in the previous version, Rapids22.06. Is this a problem with the configuration item settings or a bug in Rapids22.08?
keyWord:
Rapids22.08: SparkSQL has java.lang.NoClassDefFoundError: org/apache/spark/sql/rapids/execution/SerializeConcatHostBuffersDeserializeBatch issue using GpuKryoRegistrator.
it reported:
Caused by: java.lang.NoClassDefFoundError: org/apache/spark/sql/rapids/execution/SerializeConcatHostBuffersDeserializeBatch
at com.nvidia.spark.rapids.GpuKryoRegistrator.registerClasses(GpuKryoRegistrator.scala:27)
at org.apache.spark.serializer.KryoSerializer.$anonfun$newKryo$8(KryoSerializer.scala:170)
at org.apache.spark.serializer.KryoSerializer.$anonfun$newKryo$8$adapted(KryoSerializer.scala:170)
at scala.collection.mutable.ResizableArray.foreach(ResizableArray.scala:62)
at scala.collection.mutable.ResizableArray.foreach$(ResizableArray.scala:55)
at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:49)
at org.apache.spark.serializer.KryoSerializer.$anonfun$newKryo$5(KryoSerializer.scala:170)
at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
at org.apache.spark.util.Utils$.withContextClassLoader(Utils.scala:222)
at org.apache.spark.serializer.KryoSerializer.newKryo(KryoSerializer.scala:161)
at org.apache.spark.serializer.KryoSerializer$$anon$1.create(KryoSerializer.scala:102)
at com.esotericsoftware.kryo.pool.KryoPoolQueueImpl.borrow(KryoPoolQueueImpl.java:48)
at org.apache.spark.serializer.KryoSerializer$PoolWrapper.borrow(KryoSerializer.scala:109)
at org.apache.spark.serializer.KryoSerializerInstance.borrowKryo(KryoSerializer.scala:336)
at org.apache.spark.serializer.KryoSerializationStream.(KryoSerializer.scala:256)
at org.apache.spark.serializer.KryoSerializerInstance.serializeStream(KryoSerializer.scala:422)
at org.apache.spark.broadcast.TorrentBroadcast$.blockifyObject(TorrentBroadcast.scala:317)
at org.apache.spark.broadcast.TorrentBroadcast.writeBlocks(TorrentBroadcast.scala:138)
at org.apache.spark.broadcast.TorrentBroadcast.(TorrentBroadcast.scala:91)
at org.apache.spark.broadcast.TorrentBroadcastFactory.newBroadcast(TorrentBroadcastFactory.scala:35)
at org.apache.spark.broadcast.BroadcastManager.newBroadcast(BroadcastManager.scala:77)
at org.apache.spark.SparkContext.broadcast(SparkContext.scala:1509)
at org.apache.spark.scheduler.DAGScheduler.submitMissingTasks(DAGScheduler.scala:1388)
at org.apache.spark.scheduler.DAGScheduler.submitStage(DAGScheduler.scala:1226)
at org.apache.spark.scheduler.DAGScheduler.handleJobSubmitted(DAGScheduler.scala:1168)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:2395)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:2387)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:2376)
at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:49)
Configuration items
./spark-sql --master spark://xxxx:7077
--conf spark.serializer=org.apache.spark.serializer.KryoSerializer
--conf spark.kryo.registrator=com.nvidia.spark.rapids.GpuKryoRegistrator \

There are changes in 22.10 that fix this along with  https://github.com/NVIDIA/spark-rapids/issues/6442.
When you submit the application how are you specifying the rapids jar?  Is it in the spark jars directory or passing with --jars, --extraclasspath, or other?  If you can provide that information we can look if there is a workaround in 22.08.

#6442 was about the issue introduced in the upcoming 22.10.0 release, which is fixed as @tgravescs points out. If the title is correct and 22.08 also had this issue, we should look more into this reproducer.

Hi @hailiang9615, were you able to resolve this issue?  If not, can you please provide more information, as requested?

When you submit the application how are you specifying the rapids jar? Is it in the spark jars directory or passing with --jars, --extraclasspath, or other? If you can provide that information we can look if there is a workaround in 22.08.

If you can provide more information about how to reproduce that would be helpful!  Closing for now until we get more feedback.  Please check 22.10 as well, which should be out by the end of October.


[Bug]: bounds not always retained during group_average operations

What happened?
Scenario A (xcdat v0.5.0 + xarray >=v2023.3.0)
This scenario affects xcdat v0.5.0 (regardless of xarray version). In this issue, xcdat does not create time_bounds for annually averaged data.
fn = '/p/css03/esgf_publish/CMIP6/CMIP/NCAR/CESM2/amip/r1i1p1f1/Amon/tas/gn/v20190218/tas_Amon_CESM2_amip_r1i1p1f1_gn_195001-201412.nc'
ds = xc.open_dataset(fn)
print('Time bounds in dataset: ', 'time_bnds' in ds.variables)
ds = ds.temporal.group_average('tas', freq='year')
print('Time bounds in dataset after taking annual average: ', 'time_bnds' in ds.variables)

Time bounds in dataset:  True
Time bounds in dataset after taking annual average:  False

Scenario B (xcdat 0.5.0 and xarray 2023.7.0)
This scenario affects xcdat v0.5.0 (and xcdat v 2023.7.0, but not xcdat v2023.3.0). In this issue, xcdat drops axis attributes after performing a group_average operation.
fn = '/p/css03/esgf_publish/CMIP6/CMIP/NCAR/CESM2/amip/r1i1p1f1/Amon/tas/gn/v20190218/tas_Amon_CESM2_amip_r1i1p1f1_gn_195001-201412.nc'
ds = xc.open_dataset(fn)
ds.lon.attrs
ds = ds.sel(time=slice("1950-01-01", "2000-12-30"))
ds = ds.temporal.group_average('tas', freq='year')
ds.bounds.get_bounds("X")

KeyError: "No bounds data variables were found for the 'X' axis. Make sure the dataset has bound data vars and their names match the 'bounds' attributes found on their related time coordinate variables. Alternatively, you can add bounds with xcdat.add_missing_bounds or xcdat.add_bounds."

This results because the attributes for ds.lon are missing (after taking the group average): ds.lon.attrs

{}

(They were not missing before taking the group average)
What did you expect to happen? Are there are possible answers you came across?
In scenario A, I would have expected annual bounds (this isn't that critical, though).
In scenario B, I would have expected ds.lon.attrs to persist after ds.temporal.group_average() operations. Note that this issue has downstream effects (e.g., taking spatial averages which need the lat/lon bounds).
Minimal Complete Verifiable Example (MVCE)
No response
Relevant log output
No response
Anything else we need to know?
I'm less worried about Scenario A. Scenario B can actually cause downstream problems.
Environment
xcdat v0.5.0
xarray version v2023.7.0

I believe this is a duplicate issue of #458 and was resolved by #465, which will be included in v0.6.0.
Can you try the same code out on the main branch with the latest dev environment?

This works on the main branch. We might consider a feature in the future that adds the correct bounds after group averaging, but that can be raised as a separate issue. I think this can be closed.

This works on the main branch. We might consider a feature in the future that adds the correct bounds after group averaging, but that can be raised as a separate issue. I think this can be closed.

I opened #534 to cover scenario A.

@pochedls I just released v0.5.0 patch 1 on conda-forge to fix scenario B.
conda/mamba should automatically pull the latest version. If you want to update xcdat in an existing environment, you can run mamba update -c conda-forge xcdat or mamba install -c conda-forge xcdat=0.5.0=pyhd8ed1ab_1
I ran your example for scenario B below and it works with v0.5.0 now.
fn = '/p/css03/esgf_publish/CMIP6/CMIP/NCAR/CESM2/amip/r1i1p1f1/Amon/tas/gn/v20190218/tas_Amon_CESM2_amip_r1i1p1f1_gn_195001-201412.nc'
ds = xc.open_dataset(fn)
ds.lon.attrs
ds = ds.sel(time=slice("1950-01-01", "2000-12-30"))
ds = ds.temporal.group_average('tas', freq='year')
ds.bounds.get_bounds("X")

@pochedls I just released v0.5.0 patch 1 on conda-forge to fix scenario B.
conda/mamba should automatically pull the latest version. If you want to update xcdat in an existing environment, you can run mamba update -c conda-forge xcdat or mamba install -c conda-forge xcdat=0.5.0=pyhd8ed1ab_1
I ran your example for scenario B below and it works with v0.5.0 now.
fn = '/p/css03/esgf_publish/CMIP6/CMIP/NCAR/CESM2/amip/r1i1p1f1/Amon/tas/gn/v20190218/tas_Amon_CESM2_amip_r1i1p1f1_gn_195001-201412.nc'
ds = xc.open_dataset(fn)
ds.lon.attrs
ds = ds.sel(time=slice("1950-01-01", "2000-12-30"))
ds = ds.temporal.group_average('tas', freq='year')
ds.bounds.get_bounds("X")

Also just an FYI @xCDAT/core-developers


Fix show_previews regression introduced in 2.73.0

Fixes #1541

Can you just add a Changelog entry?

Thanks for being reactive, Hans! Will fix the linter and bump the changelog right away


[Pages]: Add doc for Using Direct Upload with continuous integration

This PR adds doc for Using Direct Upload with continuous integration like GitHub actions and Circle CI.

Gimme a few before we merge these. No changes, but I want to get the Pages Action out. I'll merge when I'm ready.

We're live! https://github.com/marketplace/actions/cloudflare-pages-github-action


Set up for continuous analysis

Do we want to update the models every time we project forward, or just predict from what we knew in 2013?
The current workflow is, uh, suboptimal:

sbatch richness.job
wait an hour or so while the observer model runs
set CV = TRUE in analysis/serial-mistnet.R, then run it
wait 12 hours
set CV = FALSE in analysis/serial-mistnet.R, then run it again


Code lens never loads

Environment data
.NET Command Line Tools (2.1.103)

Product Information:
 Version:            2.1.103
 Commit SHA-1 hash:  60218cecb5

Runtime Environment:
 OS Name:     Windows
 OS Version:  6.1.7601
 OS Platform: Windows
 RID:         win7-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.103\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.6
  Build    : 74b1c703813c8910df5b96f304b0f2b78cdf194d

VS Code version:
1.21.1
79b44aa704ce542d8ca4a3cc44cfca566e7720f1
x64
C# Extension version:
1.14.0
Steps to reproduce
Unsure,
I have a machine with vs code and the c# extension running windows 10 professional same environment otherwise and code lens loads.
Project builds and restores correctly otherwise.
 Are other IDE features (eg, IntelliSEnse, find all references) working?

Omnisharp log
Starting OmniSharp server at 3/26/2018, 1:27:59 PM
Target: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\smart_singulator_nn_interface.sln
OmniSharp server started
Path: C:\Users\adragose.vscode\extensions\ms-vscode.csharp-1.14.0.omnisharp\OmniSharp.exe
PID: 18396
    Starting OmniSharp on Windows 6.1.7601.65536 (x64)

    Located 1 MSBuild instance(s)
        1: StandAlone 15.0 - "C:\Users\adragose\.vscode\extensions\ms-vscode.csharp-1.14.0\.omnisharp\msbuild\15.0\Bin"

    MSBUILD_EXE_PATH environment variable set to 'C:\Users\adragose\.vscode\extensions\ms-vscode.csharp-1.14.0\.omnisharp\msbuild\15.0\Bin\MSBuild.exe'

    Registered MSBuild instance: StandAlone 15.0 - "C:\Users\adragose\.vscode\extensions\ms-vscode.csharp-1.14.0\.omnisharp\msbuild\15.0\Bin"
        CscToolExe = csc.exe
        CscToolPath = C:\Users\adragose\.vscode\extensions\ms-vscode.csharp-1.14.0\.omnisharp\msbuild\15.0\Bin\Roslyn
        MSBuildExtensionsPath = C:\Users\adragose\.vscode\extensions\ms-vscode.csharp-1.14.0\.omnisharp\msbuild
        MSBuildToolsPath = C:\Users\adragose\.vscode\extensions\ms-vscode.csharp-1.14.0\.omnisharp\msbuild\15.0\Bin

    Detecting Cake files in 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface'.

    Could not find any Cake files

    Initializing in c:\Users\adragose\Documents\Source\smart_singulator_nn_interface

    Auto package restore: False

    Update workspace context

    Resolving projects references

    Detecting projects in 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\smart_singulator_nn_interface.sln'.

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\ClientConnectionServer\ClientConnectionServer.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\SmartSingulatorClassificationApp\SmartSingulatorClassificationApp.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\SmartSingulatorCSConnectionTester\SmartSingulatorCSConnectionTester.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\DomainModels\DomainModels.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\UnitTests\UnitTests.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\GigECameraInterface\GigECameraInterface.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\GigECameraInterfaceTester\GigECameraInterfaceTester.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\FrameWork\FrameWork.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\ProtocolMessages\ProtocolMessages.csproj'

    Queue project update for 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\TwincatInterface\TwincatInterface.csproj'

    Detecting CSX files in 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\ClientConnectionServer\ClientConnectionServer.csproj

    Configuration finished.

    Omnisharp server running using Stdio at location 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface' on host 10132.

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\ClientConnectionServer\ClientConnectionServer.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\SmartSingulatorClassificationApp\SmartSingulatorClassificationApp.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\SmartSingulatorClassificationApp\SmartSingulatorClassificationApp.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\SmartSingulatorCSConnectionTester\SmartSingulatorCSConnectionTester.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\SmartSingulatorCSConnectionTester\SmartSingulatorCSConnectionTester.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\DomainModels\DomainModels.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\DomainModels\DomainModels.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\UnitTests\UnitTests.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\UnitTests\UnitTests.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\GigECameraInterface\GigECameraInterface.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\GigECameraInterface\GigECameraInterface.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\GigECameraInterfaceTester\GigECameraInterfaceTester.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\GigECameraInterfaceTester\GigECameraInterfaceTester.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\FrameWork\FrameWork.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\FrameWork\FrameWork.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\ProtocolMessages\ProtocolMessages.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\ProtocolMessages\ProtocolMessages.csproj'

    Loading project: c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\TwincatInterface\TwincatInterface.csproj

    Adding project 'c:\Users\adragose\Documents\Source\smart_singulator_nn_interface\TwincatInterface\TwincatInterface.csproj'

    Update project: ClientConnectionServer

    Update project: SmartSingulatorClassificationApp

    Update project: SmartSingulatorCSConnectionTester

    Update project: DomainModels

    Update project: UnitTests

    Update project: GigECameraInterface

    Update project: GigECameraInterfaceTester

    Update project: FrameWork

    Update project: ProtocolMessages

    Update project: TwincatInterface

Does the completion list work? Do you have any of the following settings set to false in your VS Code settings?

csharp.referencesCodeLens.enabled
csharp.testsCodeLens.enabled

I have also the same problem, CodeLens is not working after enabling all settings.
"editor.codeLens": true,
"csharp.referencesCodeLens.enabled": true,
"csharp.testsCodeLens.enabled": true

Suddenly started happening, unsure what prompted it. I'll try to repro from a clean slate and report back.

@DustinCampbell I noticed this periodically, too. In my case, there were no errors in the log, and intellisense was working.

This problem didn't go away after issuing the Omnisharp: Restart Omnisharp command, but was fixed after reloading VS Code altogether.

@akshita31 : Do you have any ideas here?

@adragoset @diggudg The latest version of the extension is 1.15.2. Could you try updating and checking if the error still persists.

@natemcmaster Thanks for the information. We will look into.

I've also been running into this problem, but my intellisense is also not working.  Have all the newest versions and I've uninstalled and reinstalled both VSCode and the extension multiple times.

I suspect that's a different problem @JeremyDaug. Could you file a separate issue?

I think I've spotted the cause of this issue. If I'm correct, the original report is different. This would have been introduced when we add the run/debug tests in a class code lens.

Make sure the folder name of your solution matches the the name of solution file .sln.


ChartEditor misses the layers support

Overview
The power of Vega List is layering so we def need to support it. I suggest having a layer tabs on the top or on the left (see e.g. PackageEditor)
@roll and @shashigharti to sync and brainstorm

@roll, are you suggesting something like this?

Thank you!

@shashigharti
Exactly!
TBH I think we can switch from hor/ver tabs to a tree view for navigation like this but for now that was exactly my idea
The most challenging thing here will be handling layers in the store (state)


How to implement a MongoDB store

HI Jeff,
I'm trying to replace your in-memory todoStore with a simple MongoDB data store. I am trying to create a 'Device' service that would deal with devices endpoint and interact with the 'devices' collection inside my 'app' database in MongoDB.
Here's my code so far:
routes/device.js
const { createController } = require('awilix-koa')

const api = deviceService => ({
  createTodo: async ctx => ctx.ok(await deviceService.create(ctx.request.body))
})

exports.default = createController(api)
  .prefix('/device')
  .post('', 'createDevice')

services/deviceService.js
const { BadRequest } = require('fejl')

class DeviceService {
  constructor(deviceStore, logger) {
    this.logger = logger
    this.deviceStore = db
  }
  async createDevice(data) {
    BadRequest.assert(data, 'No device payload given')
    this.deviceStore.connect()
    return this.deviceStore.create(data)
  }
}

module.exports = DeviceService

store/deviceStore
const MongoClient = require('mongodb').MongoClient

class deviceStore {
  constructor(logger) {
    this.logger = logger
  }
  async connect() {
    if (!this.db) {
      const db = await MongoClient.connect('mongoURL')
      this.db = db
    }
    this.collection = this.db.collection('devices')
  }

  async close() {
    if (this.db) {
      try {
        const close = await this.db.close()
      } catch (err) {
        this.logger.error(`Failed to close the database: ${err.message}`)
      }
    }
  }

  async create(data) {
    try {
      const insert = await this.collection.inserMany(data)
    } catch (err) {
      this.logger.error('Error inserting to MongoDB')
    }
  }
}

module.exports = deviceStore

How/when to call connect? I ideally want the connect to happen on the constructor, but the constructor doesn't support promises. I would ideally want something like this:

  constructor(logger) {
    this.logger = logger
    const db = await MongoClient.connect('mongoURL')
    this.collection = this.db.collection('devices')
  }

So that when awilix calls new on the deviceStore, it connects immediately and I don't have to call deviceStore.connect() on each call to the MongoDB collection.

When to call close? I'm unsure where to place the closing of the connection to Mongo.

Ideally you would use a client that does not use async connect calls. For example, many db clients manages the connection for you, giving you the illusion that connecting happens sync in the constructor.
For your case I would recommend connecting in the configureContainer, register it in the container asFunction that just returns your instance, and use the disposer feature to close it.
Makes sense?

Perfect. Thanks.


Piloting Orbit

The Orbit team is interested in learning more from the CNCF and Kubernetes community about how they deal with contributor ladders and metrics, and potentially mapping their model to the k8s contributor model: https://github.com/orbit-love/orbit-model/issues/29
We had some CNCF projects pilot their tool through their respective organizations and it's been found useful to provide insights on new potential contributors/maintainers. We also demo'd the tool recently at k8s contribx to get volunteers:
https://docs.google.com/document/d/1qf-02B7EOrItQgwXFxgqZ5qjW0mtfu5qkYIF1Hl4ZLI/edit
Interested people from Contribex:
Matt Broberg
Kaslin Fields
Jonas Rosland
Jenny Warnke
Paris Pittman
Bob Killen

👋  Hi folks! Josh from Orbit here, our co-founder & CTO. Excited to see how our models can fit together here.

@dzello just to let you know, we have been heads down on kubecon but @idvoretskyi will work with you to start the pilot, he will reach out and coordinate

Following up via email with @dzello :)

We think this is stale. Let's close it. TAG CS Contributor WG


Service catalogue feature

The main objective of the Service Catalog would be to create a connection between API Management and Integration layers by making integration services discoverable to the API Management layer.

Closing as the feature is released.


Setup Rose for shared repository

resolution_fixed   |    by<EMAIL_ADDRESS>

Issue migrated from trac:158 at 2024-01-31 18:09:29 +1100

Scott Wales<EMAIL_ADDRESS>commented

In [changeset:"b8c1adb77fe203127c7fb071ec46e1f5377200f0/puppet"]:
#CommitTicketReference repository="puppet" revision="b8c1adb77fe203127c7fb071ec46e1f5377200f0"
Add Rosie definition for shared repository

Fixes #158

Scott Wales<EMAIL_ADDRESS>changed resolution from `` to fixed

Scott Wales<EMAIL_ADDRESS>changed status from new to closed

<EMAIL_ADDRESS>changed status from reopened to closed

<EMAIL_ADDRESS>commented

I've added the rose configuration for the shared repository, and the location 'u' is now available in rosie go, however it doesn't look like the Rose version on Accessdev supports authentication.
Using a version of Rose from the repository with gpg-agent support gives some error messages, but appears to work, and is saving the password into gpg-agent
saw562@accessdev ~ $ ~/rose/bin/rosie lookup \*
[WARN] https://accessdev.nci.org.au/rosie/test/search: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
[WARN] https://accessdev.nci.org.au/rosie/au/search: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
[WARN] https://accessdev.nci.org.au/rosie/au/get_known_keys: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
[WARN] https://accessdev.nci.org.au/rosie/test/get_known_keys: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
local suite           owner     project title
      u-aa001/trunk@5 mattpryor JULES   JULES Loobos point example
url: https://code.metoffice.gov.uk/rosie/u/search?s=%2A

<EMAIL_ADDRESS>changed resolution from fixed to ``

<EMAIL_ADDRESS>changed status from closed to reopened

<EMAIL_ADDRESS>commented

Actually the error messages are coming from the local accessdev repository - must be a missing configuration in my new rose version. Access to the shared repository is working so I'll close this

<EMAIL_ADDRESS>changed resolution from `` to fixed


Json in leformatter

Allow specify format for {msg} as {msg:json} which will tell formater that the resulting string should be json safe/formatted...

I understand, the :json suffix follows to escaping msg field. It is a little bit confusing, cause actually we do escaping, but not json-ing. It is clear that a sting in json is just quoted escaped string, but is it ok for the naming? Just curious
Another question, if we support it, why msg field only? All other custom fields are also represented as stings. So if we introduce {vars:abc:json}?
third question regarding separation or scoping. For now scope of custom variables has name 'vars' followed by ':' then the variable name. may be use '.' notation to specify the property of the field?
For example:

msg.json - escaped msg
vars:field1.json - escaped custome 'field1'
?

As we agreed. Let's use ':' for namespace and scope separation and '.' for attributes separation.
So it should be:

msg.json
ts.
vars:field1
etc.


Fix findbugs warnings

The first fix was iterating over the EntrySet instead of the KeySet, as we also required the value inside the loop. The second fix was auto-closing of the InputStream in the event of not finding the resource.

Updated the PR to make Cobertura pass again.


Updated some content on the contributor-sustainability.md file.

Replaced "bus factor" with "contributor absence factor".

@Preshh0 I had another PR open when you made this one, and it looks like when we merged my PR, it's not playing nicely with your changes. It might be better to close this PR and do it again when you also resolve the DCO issue.

Alright @geekygirldawn. Closing this now.


update document to reflect the array ordering change and make it consistent in the pkg

Correct me if I get it wrong. Accoring to https://github.com/menpo/cyvlfeat/commit/c8e496f3a72c6ddb313cc0c029419124c0b8fc7c, now the array is in shape of [n_samples, n_features], just like scikit-learn or other python packages. So, https://github.com/menpo/cyvlfeat/blob/102ba95c3f80fc913d7cabaa8e145fd6727f7566/cyvlfeat/fisher/fisher.py#L16-L17
I think you mean

One row per data vector (e.g. a SIFT descriptor)

And there are some inconsistent usage, say vlad, when I update the commits from it use different array ordering. Now we have two different array ordering, which will make users confused. We need to make it consistent.

As you can see from #20 there was a lot of discussion about which ordering was the "right" ordering. And for the fisher module it was agreed in that PR that the [n_samples, n_features] was appropriate for the underlying call to vlfeat.
Obviously it would be best to standardize this and test that the underlying modules actually act correctly - but this is beyond my personal scope as I don't use any of the modules recently contributed. Again - happy to try and generally review and cut releases but don't have the scope to actually make this wrapper feature complete.

First part addressed in #59


Appstudio update test-component-pac-tmjz

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-tmjz-on-pull-request has successfully validated your commit.


added wake.st/twtxt.txt

I just added a .txt file manually to my github repo and copied the most recent timestamp from the hallway, I wonder if that will mess anything up

That should be fine, let's find out.


[SUPPORT] Spark writes data in eight hours

I use spark to write data to hudi, but the timestamp field of the data will be eight hours less. It was normal when I printed it.
Steps to reproduce the behavior:

Expected behavior
The timestamp field should be the same as the printed one.
Environment Description

Hudi version : 0.14.0

Spark version : 3.1.3

Hive version : 3.1.3

Hadoop version : 3.0.0-cdh6.3.2

Storage (HDFS/S3/GCS..) : HDFS

Running on Docker? (yes/no) : no

@bajiaolong It will most probably be adjusting timezone. Can you confirm.


Make windows float if it is non-resizable

It would help a lot if there's an option that automatically makes windows float if it's non-resizable or a new signal...
I tried using signal but it seems that some apps change to non-resizable after its creation (Intellij IDEA, the welcome screen) and one way I think I can do it is polling all windows with yabai -m query, but it's so slow and adds overheat to the system, maybe a signal for windows property change?
Another example is Finder copy progression windows... it would mess up my current space and allocate a big chunk of space just for a tiny window.

This used to be the default, but had to change for reasons that I no longer remember.
You can identify patterns for these windows and create rules that automatically make them float.
e.g: yabai -m rule --add app="^Steam$" space=games manage=off
See https://github.com/koekeishiya/yabai/blob/master/doc/yabai.asciidoc#rule

You could use a similar configuration
# Do not manage windows with certain titles eg. Copying files or moving to bin
yabai -m rule --add title="(Copy|Bin|About This Mac|Info)" manage=off

# Do not manage some apps which are not resizable
yabai -m rule --add app="^(Calculator|VLC|System Preferences)$" manage=off


Select smart multiple select value from Javascript?

How do I select the value of Smart Multiple Select from Javascript everytime when I click on close button ?

Good question, I don't know either. There doesn't seem to be anything on the documentation page about this.

Programmatically set the current item or retrieve it?

Issue is closed because of outdated/irrelevant/not actual
If this issue is still actual and reproducible for latest version of Framework7, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Unclear Description of Model Mounting Feature

The article says "Model mounting enables you to deploy new versions of the model without having to create a new Docker image.". It's unclear to me how this is can be done. As far as I understand, deployments reference specific model versions, and existing model versions cannot be overwritten. In case that it is possible to replace models underneath -- how does the container(s) learn about the new model then? Would AML automatically setup new container instances when a model has been changed?

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

ID: 6dff0312-5ff0-916f-d113-bd8eb4aa7d00
Version Independent ID: e80cc4c2-4be5-e426-e460-c263120875d9
Content: Deploy a custom container as a managed online endpoint - Azure Machine Learning
Content Source: articles/machine-learning/how-to-deploy-custom-container.md
Service: machine-learning
Sub-service: core
GitHub Login: @gvashishtha
Microsoft Alias: gopalv

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

@timoklimmer Hello Timo, I have forwarded this issue to the author for updating. Thanks for your feedback again.
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Fixed Issue #174

Read stations list from file

Read stations list from file

Can you change the title of the PR using conventional commit notation? Eg. feat: Read stations from a file.
Then in the PR description add some details about the change. E.g. added the field stations_file, to use it do .... And also add the phrase Closes #174. This will automatically link the PR to the issue.


Why the s0 model cannot be used directly for evaluation?

I know that s0 model cannot to be loaded in the evaluation network, but I fail to find the difference between s0 and s03 models after reading the code. Could you kindly give me some guidance about it?

It's actually very minor: s0 model handles a single model and s03 model handles multiple objects. So the s03 model accepts an extra channel input that is the sum of all other masks (this follows STM).
s0 model:
https://github.com/hkchengrex/STCN/blob/e03c1585fd852624204b5c4e8d8e828ddb2d406f/model/modules.py#L61
s03 model:
https://github.com/hkchengrex/STCN/blob/e03c1585fd852624204b5c4e8d8e828ddb2d406f/model/modules.py#L96
And the conversion code is here (we randomly init the extra channel):
https://github.com/hkchengrex/STCN/blob/e03c1585fd852624204b5c4e8d8e828ddb2d406f/model/model.py#L219-L224
You can use the s0 model for evaluation with some code changes -- the easiest way is to implement the same conversion, but zero-init the extra channel.


WINNF non-supported TLS ciphers supported by test harness

Should limit the allowed TLS cipher list on test harness to those called-out by the SAS-CBSD protocol spec.

Added fix in latest pull-request #77 (and #71)


Google Analytics

Description
As a stakeholder I would like to know the number of people who look at and sign up for the beta page
Scope of Work

[ ] Add Google Analytics to the Beta sign up page

Demo requirement

The user does x
The system does y
n. Rest of a use case of a flow chart

Acceptance Criteria

The user is able to x
The user sees y
The user hears z

Google Analytics should be added with our project's gmail account so that everyone has access to the data.


wasabibackend: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/zkSNACKs/WalletWasabi/releases.
meta.description for wasabibackend is: "Backend for the Wasabi Wallet"
meta.homepage for wasabibackend is: "https://wasabiwallet.io/"
meta.changelog for wasabibackend is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/rvwx6mrskqhsrr61p657f7w0c5sf1s0x-wasabibackend-<IP_ADDRESS>/bin/WasabiBackend had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found <IP_ADDRESS> with grep in /nix/store/rvwx6mrskqhsrr61p657f7w0c5sf1s0x-wasabibackend-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/rvwx6mrskqhsrr61p657f7w0c5sf1s0x-wasabibackend-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
wasabibackend

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rvwx6mrskqhsrr61p657f7w0c5sf1s0x-wasabibackend-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wasabibackend https://github.com/r-ryantm/nixpkgs/archive/cef71b49d5acefb82258f5e1d1e07459bc89172f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rvwx6mrskqhsrr61p657f7w0c5sf1s0x-wasabibackend-<IP_ADDRESS>
ls -la /nix/store/rvwx6mrskqhsrr61p657f7w0c5sf1s0x-wasabibackend-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

wasabibackend

Maintainer pings
cc @mmahut for testing.

Result of nixpkgs-review pr 165562 run on x86_64-linux 1

1 package built:

wasabibackend


Rented police vehicle ped, dissapearing if not near rent a bike.

When moving the PED for the rented police vehicles too far away from the rent a bike PED, the police vehicle PED dissapears and the rent a bike PED duplicates. Long story short, both peds have to be close or else the police PED will just dissapear and no longer work. Any help would be much appreciated, thanks!

Also does the same thing with the police garage
Customs.lua & Garage.lua


Man0s/event pipeline

If we want to merge this can I ask you to rebase on main, and mark this PR ready for review.

Lets leave this cooking for a bit more before we merge. We need to update base program to 1.16 so we can build this on stable toolchain.

@losman0s can this be closed?

@


Update README to account for PyPI

Current README is still in the dev stage.
We'd split it into two files:

the front page, which will also be displayed on PyPI;
a secondary one for contributions, dev, etc.; we'd put it in docs/ or sth

Issue fixed in #35


[SDP-1302] PATCH /receiver now allows patching the phone number and can handle conflicts

What
PATCH /receiver now allows patching the phone number and can handle conflicts when the provided phone_number or email are already associated with another user.
Also, refactored the related tests to make them more reusable and to cover additional test cases.
Why
Address https://stellarorg.atlassian.net/browse/SDP-1302
Checklist
PR Structure

[x] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR title and description are clear enough for anyone to review it.
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[x] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr436.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr436.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr436.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr436.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr436.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr436.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr436.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr436.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr436.previews.kube001.services.stellar-ops.com


Error when program is setting up wachter

the saving system is working when I am playing the game in the unity editor. But when I build my game and launch it, I get an error when it tries to make a data file. I think it is the wachter it tries to setup
line of code for making datafile:      static DataFile Config = new DataFile("ProgramConfig");
error:
Uploading Crash Report
NotImplementedException: The method or operation is not implemented.
at System.IO.FileSystemWatcher..ctor (System.String path, System.String filter) [0x00006] in :0
at (wrapper remoting-invoke-with-check) System.IO.FileSystemWatcher..ctor(string,string)
at SUCC.DataFileBase.SetupWatcher () [0x0000d] in C:\Users\tfeij\Documents\Unity\The Kingdom\Assets\SUCC\SUCC\DataFiles\DataFileBase.cs:180
at SUCC.DataFileBase..ctor (System.String path, System.String defaultFile, System.Boolean autoReload) [0x000f8] in C:\Users\tfeij\Documents\Unity\The Kingdom\Assets\SUCC\SUCC\DataFiles\DataFileBase.cs:41
at SUCC.DataFile..ctor (System.String path, SUCC.FileStyle style, System.String defaultFile, System.Boolean autoSave, System.Boolean autoReload) [0x0000b] in C:\Users\tfeij\Documents\Unity\The Kingdom\Assets\SUCC\SUCC\DataFiles\DataFile.cs:39
at SUCC.DataFile..ctor (System.String path, System.String defaultFile, System.Boolean autoSave, System.Boolean autoReload) [0x00000] in C:\Users\tfeij\Documents\Unity\The Kingdom\Assets\SUCC\SUCC\DataFiles\DataFile.cs:29
at Game.DataSystem..cctor () [0x00000] in C:\Users\tfeij\Documents\Unity\The Kingdom\Assets\Scripts\SaveLoad\DataSystem.cs:8
Rethrow as TypeInitializationException: The type initializer for 'Game.DataSystem' threw an exception.
at Game.SavingSystem.Start () [0x00022] in C:\Users\tfeij\Documents\Unity\The Kingdom\Assets\Scripts\SaveLoad\SavingSystem.cs:19

Which version of Unity are you on, and which .NET runtime are you using? (Project Settings -> Player -> Configuration -> API Compatibility Level)

Which version of Unity are you on, and which .NET runtime are you using? (Project Settings -> Player -> Configuration -> API Compatibility Level)

I am using unity 2019.2.9f1 and .net standard 2.0

SUCC only supports .NET 4.x. Try switching to that and see if it fixes the issue.

I just checked and this requirement wasn't already on the wiki. Sorry about that, I've added it.

It worked! thanks for the help (and making this saving system :D)

Cheers, I hope it is useful to you :)
If you release a project that uses SUCC, be sure to add it to the wiki.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_8329e6a8-7807-4860-9a83-1420b6fad3c7/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_8329e6a8-7807-4860-9a83-1420b6fad3c7.git

Docs Build status updates of commit d28221a:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-ServiceAccountCannotAccessRepository] Your repository https://github.com/VSC-Service-Account/docs-archive-test-source has enabled Docs Build service account. It seems that at least one of the accounts, e2ebd2, does not have Read permission to the repo. Please ask your repo admin to grant correct permission to service accounts (refer to this document: https://review.docs.microsoft.com/en-us/engineering/projects/ops/engdocs/how-to-grant-service-account-permission-in-your-repository?branch=master#ops-e2e-ppe) and then retry the build. Don't know who to contact? Refer https://repos.opensource.microsoft.com/VSC-Service-Account/repos/docs-archive-test-source/permissions/ to get admin list of the repo if the repo is in one of the organizations Microsoft owns.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Doc Blocks in PHP Unpopulated

Doc blocks in PHP will respond correctly to carriage returns, but do not populate any parameters.
The doc block is also not closed automatically.

Could you show a before-and-after on the code? Also, if you could open the console (Ctrl+`) and type sublime.log_commands(1) and paste what it logs when you press enter? (sublime.log_commands(0) will turn the logging off again afterwards)

YKW? I just tried it on my laptop, which runs OSX Lion, and it worked fine.
When I get back to my desktop, which runs OSX Snow Leopard, I'll try it again.

I think I found it... I had installed PHPDoc previously and then removed it but it synced back onto this computer from my desktop.
It must be intercepting the key commands.
I'll verify and get back to you.
Sent from a mobile device.
On Jan 26, 2012, at 9:21 AM, Nick<EMAIL_ADDRESS>wrote:

what's codedoc? Is that another plugin?

Reply to this email directly or view it on GitHub:
https://github.com/spadgos/sublime-jsdocs/issues/34#issuecomment-3672624

@spadgos Sorry, turn out that is was just me all along.  Thanks for a great sublime package!

No worries. Glad to hear you like the package.


docs(quickstart): add MUI example live preview

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://refine.dev/docs/guides-concepts/contributing/#commit-convention

Notes for reviewers
Translation JSON files can't be put into lz-string, some translations are missing. Updated live-preview's translation JSON files, it should be fixed when live-previews is deployed.

Closing in favor of https://github.com/refinedev/refine/pull/5730


fix readme typos

Do I need to sign up to Vercel in order to contribute in this repo? I couldn't find any contributing guidelines.


Actually stop trying to time out finished Runs ⏰

Changes
In 10b6427 I got really enthusiastic about making sure even our
reads were threadsafe and so I thought I would be clever and,
instead of accessing attributes of a PipelineRun or TaskRun in
a go routine, use a value that wouldn't change - specifically the address.
But the address will change between reconcile loops, because the
reconcile logic will create a new instance of the Run object every time!
🤦♀
Fortunately this doesn't cause any serious problems, it just makes
things slightly less efficient: for every Run you start, a go routine
will remain open until the timeout occurs, and when it fires, it will be
reconciled an extra time, even if it has completed. (In fact keeping
this functionality completed and dropping the "done" map might be a
reasonable option!)
With this change, we now return to using the namespace + name as a key
in the map that tracks the done channels; we pass these by value so that
reads will be threadsafe.
Instead of fixing this separately for the TaskRun and PipelineRun
functions, I've collapsed these and the callback into one. Each handler
instantiates its own timeout handler so there is no reason for the
timeout handler to have special knowledge of one vs the other.
Fixes #3047
Test
I tried several different approaches to add a test case that would
reveal the underlying problem but I now feel like it's more hassle than
it's worth. Approaches:

instantiate the controller in the reconciler tests with a custom
timeout handler that has been overridden to use a custom logger,
so we can check for the log indicating the timeout handler completed
Similar to (1) but instead of checking logs, just pass in a custom
done channel and wait for it to close

Both 1 + 2 require changing the way that NewController works, i.e. the
way we always instantiate controllers. I tried working around this by
taking the same approach as TestHandlePodCreationError and
instantiating my own Reconciler but it a) wasn't instantiated properly
no matter what I tried (trying to use it created panics) and b) had a
confusingly different interface, exposing ReconcileKind instead of
Reconcile
I tried some other approaches but these went nowhere either; I don't
think it's worth adding a test to cover this, but if folks feel strongly
I don't mind opening an issue at least to continue to explore it? I feel
that this bug is one that is very specific to the implementation and I'm
not sure how valuable a test that covers it would be. If we do pursue
it, we might want to do it at the level of an end to end test that
actually checks the logs from a real running controller.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[n/a] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
When a TaskRun or PipelineRun completes, the go routine waiting for it to timeout will now stop (as it was designed to do!) instead of always re-reon

coverage dropped a bit here but note I'm next planning to resurrect #3031 and significantly increase coverage!

pkg/timeout/handler.go:40:2: `defaultFunc` is unused (deadcode)
	defaultFunc        = func(i interface{}) {}

oooo nice thanks linter 🙏

well that seems apt :D

Weird that the v1alpha1 test failed and v1beta1 succeeded 🤔

i dont want to introduce new flakiness but i do want to see if this happens consistently, havent been able to repro yet:
/test pull-tekton-pipeline-integration-tests

I looked into that test failure more - I'm pretty disturbed a test directly related to the changes im making just to happened to flake but it kinda seems like that happened.
The test that fails runs a pipeline with a task that is expected to succeed and a task that is expected to time out; the task that failed was actually the one that is supposed to succeed with:
        ---
        apiVersion: tekton.dev/v1alpha1
        kind: TaskRun
        metadata:
          annotations:
            pipeline.tekton.dev/release: devel
          creationTimestamp: "2020-08-07T21:38:02Z"
          generation: 1
          labels:
            app.kubernetes.io/managed-by: tekton-pipelines
            tekton.dev/pipeline: pipelinetasktimeout
            tekton.dev/pipelineRun: prtasktimeout
            tekton.dev/pipelineTask: pipelinetask1
            tekton.dev/task: success
          name: prtasktimeout-pipelinetask1-ljfbw
          namespace: arendelle-fml4b
          ownerReferences:
          - apiVersion: tekton.dev/v1beta1
            blockOwnerDeletion: true
            controller: true
            kind: PipelineRun
            name: prtasktimeout
            uid: a6f55b45-9020-49aa-8129-cc3ce44fc9e9
          resourceVersion: "4998"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-fml4b/taskruns/prtasktimeout-pipelinetask1-ljfbw
          uid: 237e86b7-d275-4a73-953b-81ada233c195
        spec:
          resources: {}
          serviceAccountName: ""
          taskRef:
            kind: Task
            name: success
          timeout: 1m0s
        status:
          completionTime: "2020-08-07T21:39:22Z"
          conditions:
          - lastTransitionTime: "2020-08-07T21:39:22Z"
            message: TaskRun "prtasktimeout-pipelinetask1-ljfbw" failed to finish within "1m0s"
            reason: TaskRunTimeout
            status: "False"
            type: Succeeded
          podName: prtasktimeout-pipelinetask1-ljfbw-pod-nxbns
          startTime: "2020-08-07T21:38:10Z"
          steps:
          - container: step-unnamed-0
            name: unnamed-0
            waiting:
              reason: PodInitializing
          taskSpec:
            steps:
            - args:
              - 1s
              command:
              - sleep
              image: busybox
              name: ""
              resources: {}

The task is supposed to sleep for 1s (with a 1 min timeout) and then succeed, but the pod was stuck "PodInitializing" for reasons now lost in the sands of time.
So it doesn't SEEM like this is a real problem 🤞 🤞 🤞

/test pull-tekton-pipeline-integration-tests

I'm pretty disturbed a test directly related to the changes im making just to happened to flake but it kinda seems like that happened.

Thinking about it further, i think if an e2e test is gonna flake, the probability that a timeout related test would flake might actually be pretty high - there are a couple of them, run for both v1alpha1 and v1beta1

I think there's a chance we can simplify a lot of this by using impl.EnqueueAfter to enqueue a reconciliation in the future when the timeout should be elapsed.

iiiiinteresting - i can try that out as part of #2905. i guess the only downside is that we get 1 extra reconcile for every Run? (which ironically is the current state, which this PR is undoing) seems worth it to me tho!

/approve


Good written Readme is needed

In order for beginners in the field of OpenSource to enjoy working together, we need a good written Readme.
Please look at some good examples on the internet and provide something appropriate.
Thanks a lot

I would like to work on this issue. Please assign it to me. Thanks!

did it. have fun!


Android: old view of newly created screen is not destroyed after recreateReactContextInBackground()

Description
When app is started and navigates to new ReactFragment or ReactActivity the call to recreateReactContextInBackground() method of ReactInstanceManager results in appearance of two copies of newly opened screen at the same time.
But if I make a 200+ ms delay before calling recreateReactContextInBackground() then I see appearance of the newly opened screen and then it's reload removing initially created view.
This behavior was tested on react native versions: 0.61.3 and 0.62.2
I suspect there is a race condition between the processes of new screen initialization and react context recreation.
React Native version:
System:
OS: macOS 10.15.3
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Memory: 2.32 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.12.0 - /usr/local/bin/node
Yarn: 1.19.1 - /usr/local/bin/yarn
npm: 6.11.3 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 28, 29
Build Tools: 28.0.3, 29.0.2
IDEs:
Android Studio: 3.6 AI-192.7<IP_ADDRESS>41897
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
npmPackages:
react: 16.11.0 => 16.11.0
react-native: 0.61.3 => 0.61.3
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
Steps To Reproduce

Create new project with react-native init ExampleProject
Copy MainActivity to SecondActivity changing main component name to ExampleProject2. Add corresponding record to AndroidManifest.xml
3a. Option 1: Override onResume method of SecondActivity  and add getReactInstanceManager().recreateReactContextInBackground() in it. This is the same thing CodePush does when loading new bundle with rule "on next resume".
3b.  Option 2: Override onPause method of MainActivity  and add getReactInstanceManager().recreateReactContextInBackground() in it. This is the same thing CodePush does when loading new bundle with rule "on next suspend".
Copy with renaming App.js to App2.js.
Make background colors in App.js and App2.js semitransparent with alpha = 0.4 (to witness old view of the screen in front on the new one)
Register new component in instance.js with AppRegistry.registerComponent(appName + '2', () => App2);
Add button to App.js component in any place to navigate to SecondActivity
Add native module as usual that will handle button click and call getCurrentActivity().startActivity(new Intent(currentActivity, SecondActivity.class));
Build and start the app
Click the button to navigate to SecondActivity
You will see 2 copies of App2 component one in front of another. And only the one in front (old one) is scrollable.

Expected Results
Only one instance of App2 will appear on the screen and be fully intractable. And ideally reloaded seamlessly (without blank screen).
Snack, code example, screenshot, or link to a repository:
Example source code: https://github.com/G0retZ/React-Native-Bug
Screenshot of the bug:

Any ideas on how to fix this?

https://github.com/petterh/react-native-android-activity

Hi guys! Do you plan to do anything with this?

Hello, is anyone looking into this? I'm also seeing this happening when using Codepush with react-native 0.63.3

Me personally don't care anymore.
I don't plan to return to RN masochism with related frustrations and sufferings 😊

Closing as stale


Some problems with Atom::d_mtrx in parallel mode

When I use grid [2] for example, then calculations give wrong gap. By checking hashes of the data I found, that PAW data is the same as in serial, but Atom::d_mtrx is not (which is calculated before PAW).

Old commit without parallel PAW works also incorrect in parallel

It seems that the problem is here https://github.com/electronic-structure/SIRIUS/blob/master/src/Potential/generate_d_operator_matrix.cpp#L145

I thought that reduce_gvec is 0 (as it in sirius.json)
maybe here an additional summation appears due to allreduce


unexpected value at params[:tags][0]["Tier"] when trying to remove existing tags

An attempt to remove an existing tag with the tag's explicit value fails:
  * aws_resource_tag[i-0e4f5d02] action remove
================================================================================
Error executing action `remove` on resource 'aws_resource_tag[i-0e4f5d02]'
================================================================================

ArgumentError
-------------
unexpected value at params[:tags][0]["Tier"]

Cookbook Trace:
---------------
/var/chef/cache/cookbooks/aws/providers/resource_tag.rb:54:in `block (3 levels) in class_from_file'
/var/chef/cache/cookbooks/aws/providers/resource_tag.rb:53:in `block (2 levels) in class_from_file'
/var/chef/cache/cookbooks/aws/providers/resource_tag.rb:51:in `each'
/var/chef/cache/cookbooks/aws/providers/resource_tag.rb:51:in `block in class_from_file'

Compiled Resource:
------------------
# Declared in /var/chef/cache/cookbooks/jorhett/recipes/tags.rb:47:in `block in from_file'

aws_resource_tag("i-0e445d02") do
  action [:remove]
  retries 0
  retry_delay 2
  cookbook_name "jorhett"
  recipe_name "tags"
  tags {"Tier"=>"front"}
  not_if { #code block }
end

+1

2 years later...


Sersic profiles are really annoying

Okay I've been trying all day to figure out how to accurately render Sersic profiles in the Fourier domain. I think the main issue is that the Gaussian components cannot capture then inner steep bit so they tend to underestimate the flux by 3-5% for high n profiles.
Possible solutions I've thought of:

Re-scale all of the amplitudes of the components to make sure the sum matches the input flux. I don't super like this solution as it artificially inflates the whole profile when the issue is really in the center.

Go with some 'softened' profile which mellows out in the center. This was done in SDSS (the luv and lux profiles) and maybe also in tractor. Its a decent option but then we have to make sure the definitions are consistent with "traditional" Sersic profiles that most people will expect.

a "hack" that I have implemented now. Basically calculate the expected flux at r < smallest width and adds it back into the amplitude of the smallest component. This essentially boosts it's flux to account for the potential of missing flux. This works okay, total fluxes for n=4 profiles are accurate to within 2% in the tests, but is a little hacky and we will have to test further. I like it cause it attempts to directly address the problem using reasonable assumptions that can be calculated on the fly.

Anyways mostly just venting and definitely open to suggestions

Okay plot twist, after some further testing, the issues actually seemed to be with the outer profiles. I extended the default width of the largest Gaussian component (from 10r_eff to 15r_eff) and that seems to help. This is probably a little bit overkill for most cases, as the profiles as this large radii would be far below the noise level.
Running a few more tests but all 3 renderers seem to agree now with ~2.5% on the total flux

Was this resolved in the recent update where users specify he largest component in real space?

Yes that helps! All 3 renderers are now consistent within 2.5% accurate fluxes in all the tests. The real and hybrid renders are even more accurate than that. I think it's fine to close for now but good to keep an eye on