text:
[lab/login] please add federation

i hope this code is fine
todo

[ ] add user-styles.css file for other instances

federates with

{ name: 'todepond.com', url: 'https://todepond-lablogingetusers.web.val.run' },
{ name: 'svenlaa.com', url: 'https://svenlaa-lablogingetusers.web.val.run' },
{ name: 'evolved.systems', url: 'https://evol-lablogingetusers.web.val.run' },
{ name: 'rossilaz.xyz', url: 'https://mittzy-loginredux_getusers.web.val.run' },

how?

request all those URLs
add the reponse objects to the entries array, including the new instance name
act like everything is fine

other

assumes the first instance in the list in SELF instance
loads user-styles.css file from svenlaa.com for their styles
usernames get a lot longer, will break PodeTond 💚 style
puts instance-specific things into consts at the top of the javascript so it can easily be found when making a new instance
please review the code, suggest changes. i am bad at big picture stuff

* usernames get a lot longer, will break `PodeTond 💚` style

The code was pretty bad anyways (and browser dependent whoch sucks so much). Feel free to remove it / roll it back to gradient only, and I'll figure out something better

* usernames get a lot longer, will break `PodeTond 💚` style

The code was pretty bad anyways (and browser dependent whoch sucks so much). Feel free to remove it / roll it back to gradient only, and I'll figure out something better

it's okay should be do-able :)

check out Logarithm, which seems to have done a lot of these changes! 🤯
https://tristie.org/logarithm/

awesome stuff, I marked as resolved the ones that I think are done :)
i think it's almost there. probably just needs replies/mentions fixing for when you @ someone on your home server without specifying host - then it should implicitly refer to the person on your server. this is for backwards compatible with existing logs
if i have time I'll do it but anyone else is welcome to jump in 🙏

yolo

authors: Svenlaa TodePond tkukec

repo: TodePond/TodePondDotCom


text:
Added ticket proof validation to client.

Hey @nicktaras
This PR adds ZK proof validation into the TN client authenticate function.

@jot2re You may want to have a look at this too:
https://github.com/TokenScript/token-negotiator/pull/160/files#diff-24f1ac19d22913269d99a8a5afa4c13aa7fd2c8b9858529046424841ca6421daR403
Uses code from attestation branch here:
https://github.com/TokenScript/attestation/blob/e828eca3dcf36bf57fcbf95a93310b94b06f865a/src/main/javascript/crypto/src/Authenticator.ts#L130

Once the feedback on Attestation PR 239 gets handled, then it looks fine to me

@micwallace, please feel free to fix any src/client/index.ts conflicts and merge this when ready (Attestation PR is ready etc).

source: gharchive/pull-request

authors: jot2re micwallace nicktaras

repo: TokenScript/token-negotiator

license: MIT

license_type: permissive

license_source: github-api


text:
Add variable dictionary #1

Added English and Japanese variable dictionary.

@joamats
Can I just merge this PR myself?
(Are there any specific repo rules?)

No rules, feel free to merge everything.
João
On Thu, 3 Aug 2023 at 22:36, tonamba @.***> wrote:

@joamats https://github.com/joamats
Can I just merge this PR myself?
(Are there any specific repo rules?)
—
Reply to this email directly, view it on GitHub
https://github.com/TokyoDatathon2023/notebooks/pull/2#issuecomment-1664890714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN6E3D726M7VUI67UFQ3EPTXTRN35ANCNFSM6AAAAAA3DSXEWU
.
You are receiving this because you were mentioned.Message ID:
@.***>

authors: joamats tonamba


text:
Integrate all commit hashes in BlockHeader

resolves #120

@YoonhoKim0527 please check the reply. Will be closed and PR will be made on the main repo.

repo: TomTaehoonKim/simperby


text:
"Use this folder" button not visible at first

Steps to reproduce:

Settings -> Default Save Path (or anything else what shows that "dialog")

Actual behavior:
Unable to choose current folder - no "Use this folder" button on the bottom. It is needed to step up and step down into the folder again to see that button.
Expected behavior:
The is that button and can be used from the first time.
Additional information:
Android 11, 4.0.0 from Play Store. It worked fine with 3.x.

Hi, thanks for your report.
This is not an issue with this app, but rather with the default file manager on Android (since Android 11).
I don't know whether it's a bug or intended behaviour on Google's part.
Did you test version 3.x with Android 10 or 11?
Just to make sure i tested 3.x and managed to reproduce the above behaviour.

I've been using 3.x since the beginning, but I believe it was Android 10 then. I've bumped into that as 4.0 seems to restart saved default path and I had to do it again (which exposed the problem).
I reported it as I though there is "some flag to be set" which is missing, however, that might be indeed the behavior of the default file browser in Android 11. In that case it might be reasonable to close it with "3rd-party issue), especially that there is am existing workaround. I will report back once I meet any other app that use that file selector.

I've tested other apps and they show the same behaviour, so i'll close this for now and see if i can file a bug report upstream if not exists.

source: gharchive/issue

authors: Tommy-Geenexus szpak

repo: Tommy-Geenexus/exif-eraser


text:
fixed missing bottom values on JSON

It's nice to have expected values be the proper type, so you can safely call track.notes.map() without worrying about track.notes being undefined

Current coverage is 87.83% (diff: 100%)

Merging #27 into master will increase coverage by 0.22%

@@             master        #27   diff @@
==========================================
  Files            10         10
  Lines           331        337     +6
  Methods          44         44
  Messages          0          0
  Branches         55         59     +4
==========================================
+ Hits            290        296     +6
  Misses           41         41
  Partials          0          0

Powered by Codecov. Last update c67caeb...08b8872

@tambien - this is the last outstanding PR!  Please merge.  =)
Otherwise, you get errors like track.notes.map isn't a function if notes is undefined because a track doesn't have them.

Hooray!  Wanna bump the npm version too?

authors: appsforartists codecov-io

repo: Tonejs/MidiConvert


text:
Player Position Inaccurate

The player position property is inaccurate after the first play.
This fiddle demonstrates the issue (dev build):
https://jsfiddle.net/timboie/982r3yh7/

i spent a while working through this, and there are too many complexities in tracking the player position (loopStart/loopEnd and playbackRate changes) to do it robustly the way that i was trying. I've decided to remove this feature until I find a better way to go about it.

authors: tambien tboie


text:
PolySynth Oscillator is null when changing type while scheduled

v13.8.2
this._oscillator is null:
https://github.com/Tonejs/Tone.js/blob/dev/Tone/source/OscillatorNode.js#L216
Demo:
https://jsfiddle.net/timboie/x9y25v3n/

Thanks will try it out

Changing oscillator type occasionally throws an error:
Oscillator.js:141 Uncaught TypeError: Cannot read property 'disconnect' of null
at s.default.Oscillator. (Oscillator.js:141)
https://github.com/Tonejs/Tone.js/blob/dev/Tone/source/Oscillator.js#L141
Demo:
https://jsfiddle.net/timboie/Lyprvash/

Removed the lines that were causing the issue. This was an unnecessary optimization which was causing more issues than it was supposed to help.


text:
CORs issue connecting with socket.io (Vue or React) based web pages.

Hey,  I have a question related to socket.io.  I am creating a typical Chat Application using the javascript socket.io library.  All the 'many' internet examples use express as the server so you never see this issue, however I am trying to do the server part in Java (using WebSocketServer running on port 8080).
I keep getting the CORs issue in my browser (see below).
Access to XMLHttpRequest at 'http://localhost:8080/socket.io/?foo-bar=undefined&EIO=3&transport=polling&t=NRV069u' from origin 'http://localhost:8081' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
So my Java code extends WebSocketServer and I am overriding onWebsocketHandshakeReceivedAsServer.
My builder has: builder.put( "Access-Control-Allow-Origin" , "*");  which I believe is what solves the CORs issue.
However, my question is:  My onWebsocketHandshakeReceivedAsServer method is never called.  I have no idea why. Should this be called when the client (ie browser) issues a socket.connect(). or when it first connects with a handshake?  I have tried both, but can never get this method called.   Maybe am doing something stupid, so any hints/tips would be much appreciated!

Hello @SteveyO,
could you please provide a simple example application and your webserver configuration?
Stupid question, but you say you are running the websocket server on 8080, but isnt the webserver already running on that port?
Thank you

Hello @SteveyO,
could you please provide a simple example application and your webserver configuration?
Stupid question, but you say you are running the websocket server on 8080, but isnt the webserver already running on that port?
Thank you

Hi @marci4   Thanks for the quick reply.  Nope, the webserver is running on port 8081 (Vue runs on 8080, but if its busy it shifts the number by 1).  In any case running 2 servers on the same port would give me a binding exception.
So when I start the server the onStart() sysout is printed to the console, but as mentioned above, my question is how the onWebsocketHanshakeReceivedAsServer is triggered?  I haven't managed to get this method called (hence the CORs issue)
public class SignallingServer extends WebSocketServer {

    private static final int PORT = 8080;

    public static void main(String args[]) {
        SignallingServer server = new SignallingServer();
        server.start();
    }
    @Override
    public void onStart() {
        System.out.println("onStart");
    }

    @Override
    public ServerHandshakeBuilder onWebsocketHandshakeReceivedAsServer(WebSocket conn, Draft draft, ClientHandshake request)  {
        System.out.println("OnWebsocketHandshakeReceivedAsServer");
        ServerHandshakeBuilder builder = null;
        try {
            builder = super.onWebsocketHandshakeReceivedAsServer( conn, draft, request );
        } catch (InvalidDataException e) {
           System.out.println(" Server Invalid Data Exception");
        }
        builder.put( "Access-Control-Allow-Origin" , "*");
        return builder;
    }

    public SignallingServer() {
        super(new InetSocketAddress(PORT));
        System.out.println("JAVA Signalling server started on PORT: " + PORT);
    }

My WebCode looks something like this (and I see the CORS issue in the Browser Developer tools so its definitely finding the WebSocketServer).  I suspect it may be due to the options (which includes the handshake) but not sure, as am just starting out with these JavaScript frameworks.
Vue.use(new VueSocketIO({
  debug: true,
  connection: 'http://localhost:8080',
  options: { autoConnect: false, query: "foo-bar" },
  query: "foo-bar"
}))

Hi @marci4   Thanks for the quick reply.  Nope, the webserver is running on port 8081 (Vue runs on 8080, but if its busy it shifts the number by 1).  In any case running 2 servers on the same port would give me a binding exception.
So when I start the server the onStart() sysout is printed to the console, but as mentioned above, my question is how the onWebsocketHanshakeReceivedAsServer is triggered?  I haven't managed to get this method called (hence the CORs issue)
public class SignallingServer extends WebSocketServer {

    private static final int PORT = 8080;

    public static void main(String args[]) {
        SignallingServer server = new SignallingServer();
        server.start();
    }
    @Override
    public void onStart() {
        System.out.println("onStart");
    }

    @Override
    public ServerHandshakeBuilder onWebsocketHandshakeReceivedAsServer(WebSocket conn, Draft draft, ClientHandshake request)  {
        System.out.println("OnWebsocketHandshakeReceivedAsServer");
        ServerHandshakeBuilder builder = null;
        try {
            builder = super.onWebsocketHandshakeReceivedAsServer( conn, draft, request );
        } catch (InvalidDataException e) {
           System.out.println(" Server Invalid Data Exception");
        }
        builder.put( "Access-Control-Allow-Origin" , "*");
        return builder;
    }

    public SignallingServer() {
        super(new InetSocketAddress(PORT));
        System.out.println("JAVA Signalling server started on PORT: " + PORT);
    }

My WebCode looks something like this (and I see the CORS issue in the Browser Developer tools so its definitely finding the WebSocketServer).  I suspect it may be due to the options (which includes the handshake) but not sure, as am just starting out with these JavaScript frameworks.
Vue.use(new VueSocketIO({
  debug: true,
  connection: 'http://localhost:8080',
  options: { autoConnect: false, query: "foo-bar" },
  query: "foo-bar"
}))

If you want to use a Java server, you can't use socket.io (which is fine, I don't think it adds much utility compared to bare websockets, as long as you don't care about supporting ancient browsers).

If you want to use a Java server, you can't use socket.io (which is fine, I don't think it adds much utility compared to bare websockets, as long as you don't care about supporting ancient browsers).

@NoahAndrews Wow,  thanks a lot for the response.  I feel kinda stupid now.  I tried ages to get that working and I was missing that pretty valuable piece of information.
I will try again with one of the recommendations.
Thanks a lot for this,  you saved me many more hours hopelessly trying to get this to work :-)

@NoahAndrews Wow,  thanks a lot for the response.  I feel kinda stupid now.  I tried ages to get that working and I was missing that pretty valuable piece of information.
I will try again with one of the recommendations.
Thanks a lot for this,  you saved me many more hours hopelessly trying to get this to work :-)

Haha, no worries. It's easy to miss.

Haha, no worries. It's easy to miss.

authors: NoahAndrews SteveyO marci4

repo: TooTallNate/Java-WebSocket

license: mit

license_source: bigquery


text:
click at the end/beginning of the sound

Seems like this is an liblame issue, as is stated in http://lame.sourceforge.net/tech-FAQ.txt, but anyway maybe is a way to avoid this by discarding some bytes?

Command-line lame works perfectly fine for me. But node-lame does not. I'm thinking the issue is something else..

authors: ffxsam qwerter

repo: TooTallNate/node-lame


text:
slot for options and filters

Hello,
It would be nice to have a slot when you open the dropdown,
before the list of options that can be set as absolute.
I have attached a screenshot of what I'm looking to achieve.

Hi, thanks for reporting this issue.
This one is most likely very tricky.
What are you trying to achieve, a custom filter inside the menu dropdown?

yes, but just a slot named "options" or "filters" should be enough.
So I can make the HTML structure for the filters and populate the option from an HTTP call.

I've added a slot named #menu-header which is rendered before the options list.
Here's a demo deployment: https://vue3-select-component-git-feat-m-adcc75-thomas-cazades-projects.vercel.app/demo/with-menu-header.html
I think this should cover a lot of use-cases as this is a very basic slot that anyone can customize and put anything they want.

Will notice when it's deployed on a new version.

Available on v0.3.0
cc @foxhound87

Thank you!


text:
Coercing dates to strings adds time of the form '00:00:00'

How to reproduce
Suppose you have an Excel file with the following mixed-type data:

Header

=DATE(2024, 7, 1)

=DATE(2024, 7, 2)

"some string"

Now lets read this Excel file into a Polars dataframe, which coerces the column to strings:
excel_reader.load_sheet(0).to_polars()
This produces the following data frame:

Header

"2024-07-01 00:00:00"

"2024-07-02 00:00:00"

"some string"

Expected behavior
What I would have expected fastexcel to not include the time 00:00:00 for these dates. That is,

Header

"2024-07-01"

"2024-07-02"

"some string"

Test case
Excel sheet: sheet-date.xlsx
def test_date_casting_to_string() -> None:
    excel_reader = fastexcel.read_excel(path_for_fixture("sheet-date.xlsx"))
    sheet = excel_reader.load_sheet(0, column_names=["col1"])
    expected = {
        "col1": ["2024-07-01", "2024-07-02", "some string"],
    }
    pl_assert_frame_equal(sheet.to_polars(), pl.DataFrame(expected))

Yup the issue is that it's detected as datetime by calamine. We can try to do a as_date() afterwards but it would be better if calamine could handle directly dates.
I'll dig into into it this weekend but it won't be a quick fix like the bool to string. I'll probably need to open a PR on calamine side

Thanks @PrettyWood! I suspected that this one would not be as straight-forward.
In any case, no pressure on this. In contrast to #250, this issue here is not blocking our adoption of fastexcel. We can work around this for now by trimming 00:00:00 as a post-processing step. Something like:
sheet_df.with_columns(pl.all().str.replace_all(r"^([0-9]{4}-[0-9]{2}-[0-9]{2}) 00:00:00$", "$1"))

authors: PrettyWood severinh

repo: ToucanToco/fastexcel


text:
replace dependency on dsc module

The puppetlabs/dsc module is quite big (thousands of files) to be dependent on, especially if all you need is to install a windows feature. Updated the code to use the puppet/windowsfeature module instead.

Closing since this is an old pr

Closing since this is an old pr

authors: TraGicCode kreeuwijk

repo: TraGicCode/tragiccode-wsusserver


text:
Mayra

Archivos de Ecommerse

Thanks!

repo: TradeTrust/generic-templates


text:
First draft of prediction type

Not in this PR but maybe could be done at the same time: deprecation of uncertainty.
An alternative would be to extend ScheduleRelationship in StopTimeUpdate but that means having SCHEDULED (which means real time data) and IMPRECISE_REALTIME (real time but imprecise) in the same enum but that seemed not clear enough.
We put this value on StopTimeUpdate because the value could potentially change per stop even if most of the time the value will be the same for all StopTimeUpdate in the same TripUpdate.

Reading a Pull Request is always hard, because it's the answer to a question, and we have to guess what was the question.
So. Here. What are the cases you want to address? I guess it's something like:

A: scheduled according to the GTFS.
B: updated schedule according to some new data.
C: vehicle has not left the departure, but is planning to. (same than above?)
D: vehicle position is lost
E: vehicle is currently broadcasting a position

A and E are already supported, and you want to address the cases B, C and D.
=> Is this the goal of the PR? Am I missing something?
Regarding IMPROVED_SCHEDULE, if you want to address the case of a real-time update of the schedule time, I would maybe call it UPDATED_SCHEDULE (maybe it's just me, but I find it clearer). It would handle the case B, and IMHO it would also handle the case C.
D is tricky. You want to call it IMPRECISE_REALTIME, but which information is such thing giving? If the track has been lost 5s ago, the "imprecision" is really different than having lost it 1min ago, or even 5min ago. If you had the timestamp of the last update, or the delay, would it address your need?

The base usecase is that producer wants to control if the app will show a real time icon or not. For this usecase we could have done only REALTIME or IMPROVED_SCHEDULE, but from talks with people it seemed that IMPROVED_SCHEDULE doesn't cover all cases where you don't want to show real time indicator. IMPRECISE_REALTIME is there basically for the case where it's real time but not precise enough to be shown with a real time indicator in the app. The actual reason of why it's imprecise doesn't really need to be defined I think.

@mike-swiftly @LeoFrachet Updated with comments and clarifications.

authors: LeoFrachet gcamp

repo: TransitApp/transit


text:
🛑 MeVuelo Packages Availability (ASU - Mobile) is down

In 3068fed, MeVuelo Packages Availability (ASU - Mobile) (https://api.packages.production.travelonux.com/v1/mevuelo/frontend/packages/healthcheck?departure=ASU&api_key=ebfc5bcd-c798-4a53-a45a-5118f8a1e377&resolution=1) was down:

HTTP code: 502
Response time: 123 ms

Resolved: MeVuelo Packages Availability (ASU - Mobile) is back up in 33fba2e.

repo: Travelonux/upptime


text:
🛑 MeVuelo Internal Core API (production) is down

In 3f6d69c, MeVuelo Internal Core API (production) (https://api.internal-core.production.travelonux.com/status) was down:

HTTP code: 404
Response time: 410 ms

Resolved: MeVuelo Internal Core API (production) is back up in 5c23e0e after 8 minutes.


text:
chore: track dependency updates

Sometime we are missing important updates on our dependencies. Dependabot can help about this.
Documentation about dependabot.yml file can be found here: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

@leventozen good point, I'm adding it as well.

repo: Trendyol/baklava


text:
Does redux-query-sync work with Url hashes?

Hey, thanks for the great library. In our app we have routes like /hello/world/#/?type=foo. It seems that the library doesn't work with this kind of url, since the values are not being read/applied to the store. Is there a way of getting it to read/write the search query after the hash?
Thanks

This library is indeed not made with such uses in mind. If you wish to make it work still, you could try change the three places where location.search is being read, making them read location.hash.substring(location.hash.indexOf('?')) instead. And likewise change the lines where newLocation is being made, to something like this:
  search: location.search,
  hash: location.hash.substring(0, location.hash.indexOf('?')) + newLocationSearchString.

I have not tested this, so I have probably still missed some details. Happy to hear if you get it to work.

Thanks, I managed to get it working for our specific use case.

repo: Treora/redux-query-sync

license: Unlicense


text:
adding a double to the model breaks

Hi and thanks for the example.
I have simply updated the model so that price is now a double, as below. However the app simply crashes. Any ideas?
Cheers
public sealed class Car
{
public int Id { get; set; }
public string Brand { get; set; }
public  double Price { get; set; }
}

Not sure but you may have to run a schema update

Issue has now been raised with the dotnet/runtime.

For those running into this issue, it can be solved with a value converter on double/decimal.
class DoubleConverter : ValueConverter<double, string>
{
    public DoubleConverter() : base(Serialize, Deserialize, null) { }
    private static Expression<Func<string, double>> Deserialize => x => double.Parse(x);
    private static Expression<Func<double, string>> Serialize => x => x.ToString();
}

In your DbContext:
protected override void ConfigureConventions(ModelConfigurationBuilder configurationBuilder)
{
    configurationBuilder.Properties<double>().HaveConversion<DoubleConverter>();
}

authors: TrevorDArcyEvans mark-cb matt-andrews

repo: TrevorDArcyEvans/BlazorSQLiteWasm


text:
改行追加

PR Template
Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

OK


text:
⚠ T:Riza Community Forum has degraded performance

In 7c570e7, T:Riza Community Forum (https://community.triza.dev) experienced degraded performance:

HTTP code: 200
Response time: 1909 ms

Resolved: T:Riza Community Forum performance has improved in de30410.

repo: TrizaCorporation/Status


text:
😝 optimise importer warnings/errors

refs https://github.com/TryGhost/Ghost/issues/5422
We have optimised the importer logs a little.

successful import: shows warnings (including the affected entry)
not successful import: shows errors  (including the affected entry)

I would suggest please update any css changes and push on my branch! This is maybe/for sure wrong. I saw templates without using css classes, so i thought it's okay to add the inline css. I have no idea what i am doing 😏
Please use latest Ghost master for testing 🙃

Coverage decreased (-0.05%) to 72.758% when pulling 6e37aaf536d7e83b4dd5d9bf400dd2bf0e05d9b3 on kirrg001:1.0.0-dev/optimise-importer-warnings-errors into 6e841064d22147efbdedfa2b9115662b00cce4d9 on TryGhost:master.

Coverage decreased (-0.05%) to 72.758% when pulling 537db274ac191e247d18632dc07405000544ea18 on kirrg001:1.0.0-dev/optimise-importer-warnings-errors into 6e841064d22147efbdedfa2b9115662b00cce4d9 on TryGhost:master.

Coverage decreased (-0.09%) to 72.712% when pulling 45955dface1d86d199e858ba1223e40939f37606 on kirrg001:1.0.0-dev/optimise-importer-warnings-errors into 6e841064d22147efbdedfa2b9115662b00cce4d9 on TryGhost:master.

Coverage decreased (-0.1%) to 72.697% when pulling 37357b4af093d5043a7a9eeacb17fe702d8611d4 on kirrg001:1.0.0-dev/optimise-importer-warnings-errors into 6e841064d22147efbdedfa2b9115662b00cce4d9 on TryGhost:master.

repo: TryGhost/Ghost-Admin


text:
Epic: Server side error handling: codes, statuses, messaging & i18n

Ghost's error handling leaves quite a lot to be desired at the moment:

Our module which handles error logging, throwing & rendering tries to do a bit too much, without much clarity about what it is meant to do.
There's some really dirty logic in the error handling module to cope with config & theme templates
We have no support for proper log levels or debug messages, which makes it harder to debug ongoing issues than it should be.
There's confusion between error code and status code, and dogfooding our own API via HTTP makes this worse.
There's no centralised concept of codes or identifiers for a particular error also making debugging tricky.
The API doesn't serve enough information about an error, particularly validations.
We have a nice idea of an error message having 3 parts: error + context + help, but these were hardcoded throughout the codebase, and have now been moved out to the translations file, meaning they'll get auto-translated no matter where they are served/rendered.
Themes are lacking in the ability to distinguish between 404 and 500 errors

There are already several issues open about improving these issues:

API response support for warnings as well as errors #3850
Discussion: Error handling, logging and debugging improvements #2001
Refactor flow of error rendering #2030
Improve 422 validation error responses #6050

As well as a couple of client side issues, which mainly exist because the server side/API errors are so inconsistent & lacking in useful content:

Standardize admin client error handling #6431
Improve validation errors usage #6451

So lets break this down a bit into a set of clearer questions / problems, and potential solutions:
1. Status codes vs error codes
All errors that are generated by Ghost itself, should have an error code which identifies them. This code can then be used for translations at the point of render/display, as well as being used for easier debugging.
Status codes are different, all errors can also have a status code that they should be served with, if sent back via HTTP, but this is a separate concept to an error code.
2. Messaging
We should try to pursue and improve upon our concept of errors having 3 parts to a message. The idea is:

line 1 = error = the actual error message. This may not have come from Ghost itself but we should endeavour to replace all errors generated elsewhere with clearer messaging.
line 2 = context = some information about where this error was thrown or why
line 3 = help = usually a URL, where to go to get more help about this error

To enable us to improve this messaging (as well as to enable us to have a concept of error code) all codes & messages should be stored in a centralised file, and the code that needs to send the error should pull the messaging out.
The messaging for an error should stay in English until such time as it's displayed in a place that has a concept of being translated. E.g. if it is getting sent in response to an API call that had a header, or it's being rendered as part of a theme which is translated (neither of these things exist yet).
3. Log levels & debugging
Two slightly different problems, potentially solvable by the same thing. This needs fixing, and should be pursued via the discussion in #2001.
4. Cleaning up the error module
There's a lot that can be done, I think, to separate out and refactor the code in server/errors/index.js into something a bit cleaner and clearer.
If we can come up with a plan on how to move forward with logging/debugging, then we can split out the part which is for logging errors nicely into something which uses whatever tools we decide on. The rendering part can then be separated and cleaned up in accordance #2030.
It's also worth noting, we might want to look at making our server-side error rendering with error templates more configurable, as Ghost swallowing all errors is a problem for people using ghost as a submodule / middleware of a larger app.
From an i18n perspective, the renderer is going to need to be aware of whether or not it should be translating these messages. E.g. if the admin panel is set to German, and we're rendering an admin error then the message should be translated, but if it's being rendered to the theme it needs to remain in English (until such time as we have a theme language/locale setting).
5. API errors
When being served from the API, errors need to not be stripped of all their useful info. As being discussed in #6050 we need to make sure we serve useful information for validation errors in particular.
Ideally, we should update our API to use the JSONAPI.org error format: http://jsonapi.org/format/#error-objects. This didn't exist when we first coded the API, but has now settled into something clear and usable.
6. Themes
As well as cleaning up the error page rendering logic, it would also be great to provide a bit more flexibility at the theme layer. Ideally, error pages rendered from the theme should provide a way to distinguish between a 404 error, and any other error.
The error template currently gets 3 pieces of data: message, code and stack. Code needs to be disambiguated between status code and error code, the message could be expanded to provide our 3 part error message.
We should consider providing error as a context (with a body class, like all other contexts), or whether that doesn't make sense (it sort of does for 404 errors, but not other errors).
Tasks:

[x] disambiguate between status code and error code
[ ] introduce a concept of error code to all errors thrown from Ghost
[ ] centralise the error, context & help components of our error messages & group them by code (+ i18n key?)
[ ] refactor how i18n is done for errors so it's done at the point of display, in accordance with the context in which it is going to be shown
[ ] push forward the discussion in #2001 & come up with a long term plan for logging/debugging
[ ] implement the long term plan for logging/debugging :wink:
[ ] refactor the error module as per #2030
[ ] get rid of the weird logic in the error module i.e. the updateActiveTheme method
[ ] improve the API error format #6050 to serve validation info
[ ] improve the API error format #6050 to serve the Ghost error code, context + help messages
[ ] look at improving tools provided to themes for handling errors (raise an issue)

I've added the later label.
Closing for now in favour of #7116 .

repo: TryGhost/Ghost


text:
🔥 Removed support for {{lang}} helper

refs https://github.com/TryGhost/Toolbox/issues/497

Removes {{lang}} helper which has been completely deprecated since Ghost 5.0. When using the helper in themes with 5.x backend the output will be empty

landed in main as https://github.com/TryGhost/Ghost/commit/c2b18f0c87b659043c08c8e7b4c3c3c43fe54027


text:
每次更新删除旧的文件导致报错。

每次生成的文件名字都不一样，每次更新都会把旧的文件给删了。更新后第一次进网页可能读的还是上一次缓存的文件名，导致找不到文件报错卡在启动页。
请问这种情况应该怎么处理。

文件哈希是对文件内容md5，你文件没有变化的话，文件名字是不会变的

我每次生成的flutter_web_optimizer.js名字都不一样，所以项目更新是不是最好覆盖重名，不手动删除旧文件。

直接覆盖更新即可


text:
DataTable: virtual scroll and fixed column — visual bug with row (1px displacement) and border overlap

TuSimple/naive-ui version (版本)
2.19.7
Vue version (Vue 版本)
3.2.20
Browser and its version (浏览器及其版本)
Chrome(95.0.4638.32)
System and its version (系统及其版本)
MacOS(11.5.2)
Node version (Node 版本)
Reappearance link (重现链接)
https://codesandbox.io/s/wyz0z
Reappearance steps (重现步骤)

Use "virtual-scroll" on NDataTable
Use "fixed" on one or more columns
Have some data in table, more data (more columns) or more slow rendering means more bugged rows
Scroll table vertically and make sure that virtual scroll work — some rows must be dynamically loaded.

It can be reproduced on example from docs https://www.naiveui.com/en-US/os-theme/components/data-table#virtual
Expected results (期望的结果)
No visual bugs on scroll
Actual results (实际的结果)

You see that some random rows in fixed column have bugged border, looks like cell is lower or higher by 1px.
If you hover that row - bug disappears.
Remarks (补充说明)
If add fixed row height, then the bug does not appear.

No, and zoom level doesn't affect that bug.
It is definitely Chrome bug, because in Safari 14.1.2 it works good.

repo: TuSimple/naive-ui


text:
add start and end value to date picker

This function solves the problem (这个功能解决的问题)
we can solve this issue by using "is-date-disabled" but in my case
our client want to open the picker to the start value not the current month value
Expected API (期望的 API)
so if we can add something like default-value maybe
start-at-value
end-at-value
or
allowed-dates or dates-range
ex:

Will do, seems there is a Chinese issue facing the same issue.
I'll add the feature in next version.

close in https://github.com/TuSimple/naive-ui/commit/1c8de54e802e209a71267bcd4a8e05d9576f4324

authors: 07akioni Sepush hsmfawaz


text:
Run tests with Julia 1.5 instead of Julia 1.6

Since Turing (or rather Libtask_jll) is not compatible with Julia 1.6 yet (see e.g. https://github.com/TuringLang/Turing.jl/issues/1554 and the explanations there).
I guess it would be good to open an issue that reminds us to revert this change once a compatible version is available.

Do you understand why the tests here are failing on 1.5? Seems like it's still complaining about segmentation fault (Signal 11 = SIGSEGV)?

No, I don't know why it segfaults. I reran the tests, so it seems to be reproducible.

Have you tried running locally? Trying now myself.

Yes, it segfaults. I try 1.5.3 now. Currently, I assume it is caused by the multithreading tests.

1.5.3 seems to work, at least it passed the point were Julia 1.5.4 failed.

Ah, yeah I'm running 1.5.3 locally :confused:
Isn't this a bit strange though? If it's something with the multithreading, shouldn't this have been caught in DPPL tests?

I don't know which of the changes in 1.5.4 causes the segfaults: https://github.com/JuliaLang/julia/compare/v1.5.3...v1.5.4

I think this is the offending line btw: https://github.com/TuringLang/Turing.jl/blob/master/test/inference/Inference.jl#L106
At least the one where it errors. Basing it off the _varinfo warning showing up just before the error, which should be the _varinfo from "Contexts" testset.

Just wanted to change this line :smile:
I don't think we ever tested DynamicPPL on Julia 1.5.4. I assume we only checked 1.5.3 and 1.6.0 as soon as it became available.

Just wanted to change this line

Haha :smile:
But this is weird. Just running that line we works without issues on my end, even on 1.5.4. Trying to run the tests though, to see if the result is different.

I don't think we ever tested DynamicPPL on Julia 1.5.4. I assume we only checked 1.5.3 and 1.6.0 as soon as it became available.

Ah, that makes sense.

It's the first multi-threaded testset in Inference.jl. As soon as I removed it, I could run the tests successfully on Julia 1.5.4. I wonder if it's a specific algorithm in this testset that is problematic or if it is a general problem.

You're referring to the part where it iterates through the samplers? Do you know which algorithm it fails for?

Yes, exactly, in the part where it loops through the samplers. I added print statements at the top of the for loop and it seems PG is the (first) sampler that fails. HMC worked fine it seems.

Gibbs with PG segfaults as well. So it seems only PG is problematic. I wonder if multithreading with Libtask is broken on Julia 1.5.4.
@KDr2 Is there any change in https://github.com/JuliaLang/julia/compare/v1.5.3...v1.5.4 that would explain problems with Libtask on Julia 1.5.4?

Hmm maybe it's fine to disable these multithreading tests for PG? Standard sampling seems to work, and particle methods are somewhat broken anyway since they don't pass around the RNG (see e.g. https://github.com/TuringLang/AdvancedPS.jl/pull/20#issue-535245931) - maybe that's the reason for the segfault?

Hmm maybe it's fine to disable these multithreading tests for PG? Standard sampling seems to work, and particle methods are somewhat broken anyway since they don't pass around the RNG (see e.g. TuringLang/AdvancedPS.jl#20 (comment)) - maybe that's the reason for the segfault?

I mean, I'm fine with it. Feels like something @yebai should maybe comment on?
For some context: tests are failiing due to PG methods, which means that there are other bugfixes that we can't get through.

I just want to stress that in general particle methods are fine - it's just some problem related to multithreading. And I don't know what change in Julia 1.5.4 could have caused it - maybe it's something Libtask-specific? Maybe related to the RNG issues of particle methods?

Let's just drop the test for now and create an issue. @yebai said he was also fine with it so don't think anyone is opposed to it.

Gibbs with PG segfaults as well. So it seems only PG is problematic. I wonder if multithreading with Libtask is broken on Julia 1.5.4.
@KDr2 Is there any change in JuliaLang/julia@v1.5.3...v1.5.4 that would explain problems with Libtask on Julia 1.5.4?

This is caused by a change of struct jl_task_t, a field was removed in 1.5.4:
@@ -1751,8 +1751,6 @@ typedef struct _jl_task_t {
     jl_gcframe_t *gcstack;
     // saved exception stack
     jl_excstack_t *excstack;
-    // current world age
-    size_t world_age;

     // id of owning thread
     // does not need to be defined until the task runs

So the memory layout of jl_task_t in v1.5.4 is different from v1.5.3.
We should build another jll package for [1.5.4, 1.6.0) to fix this, a PR against Yggdrasil should be made, like the one for v1.6.0 (https://github.com/JuliaPackaging/Yggdrasil/pull/2176), but no code need to be changed except the julia version.

Status Quo:

libtask_jll version
compat Julia Version

0.4.2
1.5

0.4.3
1.6

If we file a new PR for 1.5.4, it will be:

libtask_jll version
compat Julia Version

0.4.2
<=1.5.4

0.4.4
[1.5.4, 1.6.0)

0.4.3
1.6

Is it rational and feasible? How about filing two PR to make this:

libtask_jll version
compat Julia Version
PR

0.4.2
<=1.5.4
N

0.4.4
[1.5.4, 1.6.0)
Y

0.4.5
1.6
Y

IMO it is fine to not have a perfectly ordered versioning scheme in this case but maybe we could just ask in the  PR for 1.5.4 what's commonly done? I am sure others had same/similar problems before.

I found that Julia 1.5.4 is not available neither on Yggdrasil...

authors: KDr2 devmotion torfjelde


text:
SyncedVar hooks

One of the handy things in HLAPI syncvars is that you can define a hook for them to invoke. Can we get the same?

Easy to add. Will get around to it shortly.

Thank you

I'll be busy during the weekend. Don't expect it within the next few hours.

:) Have a great weekend. No rush from me. I'm starting a long trip across the US and will be working slower than ever.

Is the old value required? Or is it enough for a simple callback to be invoked when the value is updated. Going to be a bit tricky I think without a weaver to do that. Might be able to get it to work with reflection.

Not sure what you mean about the old value. What the HLAPI does is invoke a callback that takes a variable of the synced variable's type. Everything else is up to you. I don't believe there's a check to make sure you actually synced the value, but I could be wrong.

SyncVarHooks in the HLAPI gives the previous new value as a parameter that you manually have to set the SyncVar to. Is this needed?

I don't need anything like that. My HLAPI code looks like:
[SyncVar(hook="OnSomeInt"]
int  someInt;
void OnSomeInt(int newInt) {
someInt = newInt;
}

Right, I understand that's the HLAPI way. But would this be alright:
[SyncVar(hook="OnSomeInt")]
int someInt;
int oldInt;
void OnSomeInt() {
//My int has changed? If I want to know the old value. I manually have to do it. Like this:
// .. code that checks someInt vs oldInt
oldInt = someInt;
}

Oh, sorry I didn't understand. So it'll set the value then call the hook essentially. I can work with that.

Added https://github.com/TwoTenPvP/MLAPI/commit/965d644fb7f0a89849d59419132ad2c437c24427

authors: TwoTenPvP angusmf

repo: TwoTenPvP/MLAPI


text:
How to compile/run in Ubuntu

How to compile/run SVisual in Ubuntu?

I'll post instructions later

authors: Tyill cleitonqmc

repo: Tyill/SVisual


text:
KeyPad Not shown in first page

Hi,
Thanks for your Component.
I have a issue when I use your component in android the keypad is not shown in first page. and after I click the county picker and select country and return to first page the Verification button text is removed. please help me.

Hmm, I'll try to reproduce it

Oh yes I see what you mean. Do you know if this only isn't working on an emulator or if it is also a problem on a physical phone? I don't have an android but on iOS it's fine

Hi,
both of it . on emulator and real phone. in real phone (Galaxy j7 prime) some times keypad not shown

A short update for anybody who may be seeing this...
the problem is that on Android calling the focus() method on a TextInput ref does not always focus on the TextInput and show the keyboard. But for some odd reason this is only a problem on Android. I'm definitely open to accepting pull requests and I have been trying to solve this problem for a couple of days but not getting much luck so far...
Thank you shayegh for exposing this really bad bug

Alright! As of version 0.1.3 this issue is resolved, all i did was simply change
this.setState({countryInfo: e}, () => {
  this._ref.focus();
});

to
this._ref.focus();
this.setState({countryInfo: e});

How to upgrade my code?
I use npm update
but the problem still exist

In your package.json how is your semantic versioning for the dependency? Is it prefixed with ^ or ~? Another way to update dependencies is to npm install like normal but add a @latest to the end like so:
npm i --save react-native-phone-auth-component@latest
and if none of these work you I suppose you could just uninstall it and install it again

authors: TylerStanish shayegh


text:
Failed to retrieve member "captureStackTrace" of [CustomErrorClass] for inheritance analysis

Search terms
failed to retrieve member, inheritance analysis
Expected Behavior
I expect to not encounter this message as I did not encounter it previously on 0.20.30 with the same code.
Actual Behavior
I receive the following warning output when building my docs:
Warning: Failed to retrieve member "captureStackTrace" of "ErrorHandlerError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "captureStackTrace" of "ErrorHandlerError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "prepareStackTrace" of "ErrorHandlerError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "stackTraceLimit" of "ErrorHandlerError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "captureStackTrace" of "CommandArgumentError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "captureStackTrace" of "CommandArgumentError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "prepareStackTrace" of "CommandArgumentError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "stackTraceLimit" of "CommandArgumentError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "captureStackTrace" of "CommandDispatchError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "captureStackTrace" of "CommandDispatchError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "prepareStackTrace" of "CommandDispatchError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "stackTraceLimit" of "CommandDispatchError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "captureStackTrace" of "ArgumentParseError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "captureStackTrace" of "ArgumentParseError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "prepareStackTrace" of "ArgumentParseError" for inheritance analysis. Please report a bug.
Warning: Failed to retrieve member "stackTraceLimit" of "ArgumentParseError" for inheritance analysis. Please report a bug.

I was not having this message pop up on 0.20.30 but it triggered a failure in my docs build test action on the Dependabot PR to update to 0.20.32, even though it's just a warning. The action looks for the word "error" in the output because TypeDoc doesn't exit with an error code or anything, so it was a false positive, but I'm reporting the bug since the message told me to do so, haha. Weirdly, this does not happen in another of my modules for this org that also has custom error classes that inherit from Error, so I'm a little perplexed.
Steps to reproduce the bug

git clone https://github.com/discord-samba/command.git
npm install
Edit scripts/typedoc-runner.js and replace the theme value with 'default' to confirm the issue is present on the default theme without any of my modifications
run node scripts/typedoc-runner.js

Note: This will create a docs directory alongside the cloned repo directory as opposed to inside of it

Observe warning output

Due to the fact that I can't reproduce the issue on the other module I have that presents these warnings, I didn't really want to jump through the hoops to produce a minimal reproducible sample repo, so I apologize for the extra needed effort to see the issue for yourself.
Environment

Typedoc version: 0.20.32
TypeScript version: 4.2.3
Node.js version: 14.15.3
OS: Ubuntu 20.04.2 LTS on Windows 10 x86_64

TypeDoc doesn't exit with an error code or anything

But... we do? https://github.com/TypeStrong/typedoc/blob/9a627d8999462ab225fab35c1bb458034b668478/bin/typedoc#L6-L13
There was a bug in early 0.20 that broke this, but it's been fixed for a while now...

Warning: Failed to retrieve member "captureStackTrace" of "ErrorHandlerError" for inheritance analysis. Please report a bug.

You see this in some projects but not all because this property is added to Error in @types/node, so if those aren't installed, it won't be picked up. This should be converted as a static member, but TypeDoc doesn't properly convert these members as static, so we try to find the member on the instance side and fail... annoying to fix it unfortunately. Going to need to think about this one...

TypeDoc doesn't exit with an error code or anything

But... we do?
https://github.com/TypeStrong/typedoc/blob/9a627d8999462ab225fab35c1bb458034b668478/bin/typedoc#L6-L13
There was a bug in early 0.20 that broke this, but it's been fixed for a while now...

I encountered a situation where merging a dependabot PR broke my docs build despite having a docs build test action (which I wrote after a different dependabot PR broke my docs builds). I reviewed the action run to find that the docs build had errored out but the action did not mark that step as failed (I would assume because of no exit code), so the run completed successfully. That led to me adding a grep for Error and an extra step that checks the result of that to determine whether or not there was an error building the docs and error out the test. It's definitely possible that this occurred during the period of time that bug existed and I was just unaware of it.

You see this in some projects but not all because this property is added to Error in @types/node, so if those aren't installed, it won't be picked up. This should be converted as a static member, but TypeDoc doesn't properly convert these members as static, so we try to find the member on the instance side and fail... annoying to fix it unfortunately. Going to need to think about this one...

I do have @types/node installed for sure, no question about that. Thank you for looking into this. I hope it doesn't give you too much trouble.

Turns out fixing this just requires adding a flag... which is kind of annoying, but very minimal code changes.

Awesome. Good work :o)

repo: TypeStrong/typedoc


text:
Is this project abandoned?

typedoc is great and a lot of people love using it. And as far as my quick search goes, there is no real alternative to it. This is the result of a lot of hard work in the past, that I honor a lot. Thanks for bringing this to the community.
However, right now the projects seems abandoned. There are may issues that could easily be closed, such as updating TypeScript or bumping the min nodejs version to 6 that would help a lot of users.
Many contributors took their time to craft pull requests that are on hold for no clear reason. In fact only two PRs have been merged since April, 2018.
Is @aciccarello the only one maintaining this project? Or is it everyone from the TypeStrong organization? Anyway, the importance of this project for the TypeScript community, I think there should be a handful of maintainers working together. I don't know how this can be managed but I am sure it would be possible to find people that volunteer and maybe proved themselves by good quality contributions in the past.
Keep up the good work – we need this project!

I am one of the maintainers of jupyterlab, a large TypeScript project that depends on this library.  I would be happy to help maintain this library, if only to review/merge PRs and keep the up with the TypeScript version.  We have been forced several times to wait to adopt TypeScript language features because TypeDoc was using an older version.

@blakeembrey ^^

Blake, you may remember we collaborated on simulate-event.

There has been decreased activity in this project over the last months, it would be great if some people with fresh energy become engaged. @aciccarello has been very active over the last years but I can totally relate to him that at some point a project like this becomes very exhausting.
As I'm not actively working on this project I would like the current maintainers to handle this decission. I personally think it would be a good idea to add @blink1073 as a maintainer.

Thanks, @sebastian-lenz!  And thank you for all your efforts in creating and maintaining this project.

@webmaster128 Thanks for reaching out. I am the only (semi) active maintainer at the moment but it has been a busy time for me. I still intend to keep working on typedoc but I would support adding another maintainer. I'm glad to hear @blink1073 willing to help out.
#256 and the typedoc gitter channel are probably the best places to talk about strategies. I also am working towards getting a TS 3.0 release out soon.


text:
🛑 Mirrors OPL is down

In e0cc508, Mirrors OPL (https://mirrors.opl.uab.cat) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mirrors OPL is back up in b272474 after 4 minutes.

repo: UAB-OPL/opl-uab-monitoring


text:
🛑 Migasfree Server OPL is down

In 287d063, Migasfree Server OPL (https://migasfree.opl.uab.cat) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Migasfree Server OPL is back up in b8e610d after 5 minutes.


text:
Update stm32 drivers to ChibiOS 3.0

I don't know if there is a desire to keep ChibiOS 2.6 around in tree. This PR simply replaces the old implementation with the new API. I did not change the example as I don't have a way to test it.
@nuft Looks OK for you ?

Folks, I've got fond feelings for ChibiOS v2.6. Can you add some preprocessor trickery to maintain compatibility please? I'll test it on my hardware then and merge once you consider it finished.

Ok, we can do something using CH_KERNEL_MAJOR.

@pavel-kirienko @nuft updated pull request with ChibiOS 2 compatibility.

Normally it should work with ChibiOS 2. I dindn't thoroughly test it though.

@pavel-kirienko can you test it on your setup and merge if it works ?

Tested on my demoboard, seems to work fine. Thanks, and sorry for the delay.

authors: antoinealb nuft pavel-kirienko

repo: UAVCAN/libuavcan


text:
Where to store metadata related to the email account and/or folder

The standard doesn't seem to make clear where to store metadata related to the email account and/or folder that may be important to understanding the contents. For example:

The history of name changes of the account
The history of mail aliases of the account
The history of mail forwarding of the account
The history of users of the account (for role-based accounts)
...

It's probably outside of the scope of the document to specify a format for this metadata, but it should acknowledge the existence of the metadata and describe where it should be stored / linked to.

Addressed by #9

authors: gwiedeman stuartyeates

repo: UAlbanyArchives/mailbag-specification


text:
Support conversion to MiniOCR

Minimal-noise OCR format for full text indexing https://dbmdz.github.io/solr-ocrhighlighting/formats/#miniocr

Moved to https://dbmdz.github.io/solr-ocrhighlighting/0.8.3/formats/#miniocr

authors: kba nichtich

repo: UB-Mannheim/ocr-fileformat


text:
Adding the financiala and personal plots

Hey all, adding the plots generated using the EDA_script file. Please feel free to review and merge the branch.

Thanks Karan. The script is working on my machine.


text:
Code for residual plot

import seaborn as sns
sns.set_theme(style="whitegrid")
X_test.index.name = "Index"
X_test.index
predict_test = ridge_pipeline.predict(X_test)
residual = y_test.copy()
residual.name = "Residuals"
sns.residplot(x=X_test.index, y=residual - predict_test,  color="g")

please change ridge_pipeline to the model you are using with any name, the color can be changed as well

code for saving the figure: can change path in savefig("")
import seaborn as sns
sns.set_theme(style="whitegrid")
X_test.index.name = "Test Data Observations"
predict_test = ridge_pipeline.predict(X_test)
residual = y_test.copy()
residual.name = "Residuals(hours)"
residual_plot = sns.residplot(x=X_test.index, y=residual - predict_test,  color="g")
residual_fig = residual_plot.get_figure()
residual_fig.savefig("residual_fig")

Very nice plot

authors: GuanshuTao YikiSu


text:
Milestone 2 Feedback

test_scatterplot.py error not passing: "Accuracy" grade down by one level. "Scatterplot() for an unknown keyword argument 't'"
R package: no installation instructions in Readme. Grade for "Mechanics" down by 3 levels (this is extremely important).
Everything else is great. Well done guys, and I'm sure these are easy fixes.

@nafi007 Thanks for the feedback! Can you help with reproducing the error you get for test_scatterplot.py? It seems to run fine on my end.

repo: UBC-MDS/magmaviz


text:
Frequency Function and Tests Edited

Dear all,
Please check the changes I made to the function and the tests, as discussed.
Please let me know if I need to do anything else.
Thanks!
Nasim

thanks, it was great

Great! I think that's all four functions merged. I will do an overall review tomorrow and assuming nothing unexpected happens, that should be our last PR before submission.

Thanks everyone!


text:
🛑 Student Media - Motley is down

In be289c7, Student Media - Motley (https://motley.ie) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Student Media - Motley is back up in 2749a74 after 7 minutes.

repo: UCCNetsoc/upptime


text:
error when  generating graph

When i run the command python3 -W ignore graph-gen.py, it reports an error as following:

This is because the order of functions in the C code is inconsistent with that in the generated llvm IR (xx.ll), thus resulting a wrong match of loops  in graph-gen.py. I notice that the given example 'aes' also shows the problem when running graph-gen.py. So how is the final graph (with pragma node) under the 'programl/processed' directory correctly generated ?

I also need help to run this code. Kindly tell me which Python version used for it because installing dependencies shows lots of conflicts . Waiting for your answer I will be grateful .Thanks

The graph generator for multiple functions is not open-sourced yet.
The project was done with Python3.6 but is runnable with other versions as well. You can discard the version number of packages if it doesn't work for you.

Update the graph gen file.

Hi, I have a problem with the implementation of the GNN-DSE code, can you help to solve it?
db_paths for gemver:
../dse_database/poly/databases/gemver_result_updated-0.db
f_db is **:    <_io.BufferedReader name='../dse_database/poly/databases/gemver_result_updated-0.db'>
<class '_io.BufferedReader'>
71%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▍                                                          | 17/24 [00:13<00:05,  1.23it/s]
Traceback (most recent call last):
File "main.py", line 30, in
dataset, pragma_dim = get_data_list()
File "/home/psdz/lining/GNN-DSE-main/src/programl_data.py", line 270, in get_data_list
data = pickle.load(f_db)
_pickle.UnpicklingError: invalid load key, '\x00'.
Error when pickle.load() tries to load  gemver_result_updated-0.db .
Thanks for your help.

repo: UCLA-VAST/GNN-DSE


text:
TAPA breaks SODA due to import issues

https://github.com/UCLA-VAST/soda/runs/6300693249?check_suite_focus=true
ImportError: Failed to import test module: tests.test_core
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/unittest/loader.py", line 436, in _find_test_path
    module = self._get_module_from_name(name)
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/unittest/loader.py", line [37](https://github.com/UCLA-VAST/soda/runs/6300693249?check_suite_focus=true#step:5:37)7, in _get_module_from_name
    __import__(name)
  File "/runner/_work/soda/soda/src/tests/test_core.py", line 8, in <module>
    from soda import core
  File "/runner/_work/soda/soda/src/soda/core.py", line 16, in <module>
    from soda.optimization import cluster
  File "/runner/_work/soda/soda/src/soda/optimization/cluster.py", line 11, in <module>
    from tapa import tapac
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/tapa/tapac.py", line 17, in <module>
    import tapa.core
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/tapa/core.py", line 31, in <module>
    from .codegen.axi_pipeline import get_axi_pipeline_wrapper
ModuleNotFoundError: No module named 'tapa.codegen'

I was able to reproduce this issue by installing TAPA from PyPI. We should avoid relative imports in general to avoid this kind of issues.

Fixed by 00f9ea5c9a7b80a0f406add3555ef1f7783a6e53

repo: UCLA-VAST/tapa


text:
I don't know how to use pato to pick the real DNA: RNA triplexator.

Dear authours,
When I ran PATO's tests, I only find interaction pairs in the tpx.n.par.out file, but it contains non-real interaction pairs. In the output files, The first question I don't know what the TFO and TTS files do,how can I use them?. Second, how did I use these files to find relatively reliable DNA: RNA Triplexator?
I'm looking forward to your reply, thank you.

Hi @jkvoivp
With regard to the tests, ignore the interactions you get there. The interactions in the test files are synthetic and only exist to detect regressions in the software (i.e., to detect if a new commit changes the functioning of PATO).
Now, concerning the TFO and TTS files, those are files that you get when you respectively analyze a single stranded sequence file (i.e., pato -ss single_stranded.fa) and a double stranded sequence file (i.e., pato -ds double_stranded.fa). And these files hold TFO or TTS regions in the sequences that may be likely to form a triplex. However, if you want to predict triple helices that may form between a single stranded sequence file and a double stranded sequence file, you must tell PATO to match their TFO and TTS regions (i.e., execute pato -ss single_stranded.fa -ds double_stranded.fa). After you do that, you will get two output files:

pato.out will hold all the individual triple helices that were found between the sequences in the single stranded file and the sequences in the double stranded file.
pato.summary will hold the interaction strength between each sequence in the single stranded file and each sequence in the double stranded file.

If you want to select candidate triplexes reliably, sort the interacting pairs in pato.summary with respect to their interaction strength (i.e., column Total (rel)), and study the triplexes found between those two sequences.
I hope this helps :).
And if you believe this information is of good interest, I could add it to the README file. Just let le know.

Also, I recommended papers such as https://doi.org/10.3390/ijms21030830 if you want to increase your odds of finding more reliable triplexes by fine tuning the search parameters of PATO

Thank you very much for your reply, with your helpful advices I successfully got the results, thank you, I wish you have a sweeter life.

I'm glad I could help :)

https://github.com/UDC-GAC/PATO/commit/0bad52bdf3c99551c2f164a5e0974f3e18eaf9fe adds this exact information to the README

authors: amatria jkvoivp

repo: UDC-GAC/pato


text:
LRTS locking API breaks multicore-win64 build

Original issue: https://charm.cs.illinois.edu/redmine/issues/1261

machine-common-core.c(1620): error C2065: 'pthread_mutex_t': undeclared identifier
machine-common-core.c(1621): error C2065: 'pthread_mutexattr_t': undeclared identifier
machine-common-core.c(1621): error C2059: syntax error: ')'
machine-common-core.c(1625): error C2065: 'pthread_mutex_t': undeclared identifier
machine-common-core.c(1625): error C2059: syntax error: ')'
machine-common-core.c(1628): error C2065: 'pthread_mutex_t': undeclared identifier
machine-common-core.c(1628): error C2059: syntax error: ')'
machine-common-core.c(1631): error C2065: 'pthread_mutex_t': undeclared identifier
machine-common-core.c(1631): error C2059: syntax error: ')'
machine-common-core.c(1634): error C2065: 'pthread_mutex_t': undeclared identifier
machine-common-core.c(1634): error C2059: syntax error: ')'

Original date: 2016-10-19 21:49:49

~~https://charm.cs.illinois.edu/gerrit/#/c/1925/~~ https://github.com/UIUC-PPL/charm/commit/3a2e4044553a8152b79cd2dc55b0b053eb9447d3

repo: UIUC-PPL/charm


text:
net-cygwin crashes in examples/bigsim/sdag

Original issue: https://charm.cs.illinois.edu/redmine/issues/1291

No body.

Original date: 2017-03-03 17:37:11

net-cygwin is deprecated


text:
SMP/non-SMP agnostic job launching arguments

Original issue: https://charm.cs.illinois.edu/redmine/issues/1844

Currently a user has to know whether Charm++ was built in SMP mode or not when they are running their application. We should support running with the same set of arguments regardless of SMP or non-SMP mode. This would be nice to have in 6.9.0, but is not necessary for it.

Original date: 2018-04-19 21:01:31

What do you propose? ++PEsPer(Host|Socket|Core|PU)?

Original date: 2018-05-10 23:47:03

Bump

Original date: 2018-05-11 00:07:47

I think we might want to avoid "PE" since that term is overloaded in Charm already: a PE is sometimes described like a Core/PU, but other times only encapsulates worker threads (CkNumPes() doesn't count comm threads). I think "Thread" would be better, since we don't need to specify the difference between worker and comm threads anymore, the hwloc-based topology stuff can account for the comm threads automatically.
I'll propose ++threadsPer(Host|Socket|Core|PU) ++processPer(Host|Socket|Core|PU), where the ++threadPer* argument overrides the ++processPer* one in non-SMP mode (++processPer* is still consumed by charmrun but is ignored and maybe a warning is printed). This way, if a user launches a program using ++threadsPerCore 1 ++processPerSocket 1 on a host with say 2 sockets, with 16 cores/socket and 2 PUs/core, we get:

in non-SMP mode: 32 processes, 1 per core.
in SMP mode: 2 processes, 1 per socket, each with 15 worker threads + 1 comm thread.

Does that make sense? Maybe "Thread" is just confusing when running in non-SMP mode...

Original date: 2018-05-11 20:40:32

Where is "PE" described like a Core/PU? The only divergence I am aware of is how a PE is a worker thread in SMP mode and a process in non-SMP mode, and this makes the term a good fit for describing provisioning in an SMP-agnostic way.
I agree that comm threads make the choice terminology difficult, but "thread" feels too unclear in non-SMP mode. My current implementation of the hwloc-informed parameters already steals from the worker thread count to provision a comm thread, so I don't think this is a significant issue.
$ ./hello +oneWthPerPU
...
Charm++> Running in SMP mode: numNodes 1,  7 worker threads per process
...
Charm++> Running on 1 unique compute nodes (8-way SMP).

Original date: 2018-05-11 21:16:37

After reading over our documentation it is better than I remembered at avoiding saying that PEs are cores/hyperthreads.
From the Charm++ manual section 1.2:
"On each PE (PE'' stands for a Processing Element''. PEs are akin to processor cores; see section 1.4 for a precise description), there is a scheduler operating with its own private pool of messages."
Section 1.4:
"In a Charm++ program, a PE is a unit of mapping and scheduling: each PE has a scheduler with an associated pool of messages. Each chare is assumed to reside on one PE at a time. Depending on the runtime command-line parameters, a PE may be associated with a subset of cores or hardware threads."
...
"For example, on a machine with 16-core nodes, where each core has two hardware threads, one may launch a Charm++ program with one or multiple (logical) nodes per physical node. One may choose 32 PEs per (logical) node, and one logical node per physical node. Alternatively, one can launch it with 12 PEs per logical node, and 1 logical node per physical node. One can also choose to partition the physical node, and launch it with 4 logical nodes per physical node (for example), and 4 PEs per node. It is not a general practice in Charm++ to oversubscribe the underlying physical cores or hardware threads on each node."
I read the first part of section 1.4 as meaning that only worker threads are PEs (since chares can't be mapped to comm threads), but the second part of 1.4 reads to me like comm threads count as PEs since it implies that you can run with 32 PEs in 1 logical node and you won't be oversubscribed.
But maybe I'm just reading too much into that part of the documentation, and we should just update the documentation to say that a PE is a worker thread in SMP mode or a process in non-SMP mode. I think your suggestion of PEsPer* is better than ++ThreadsPer* now


text:
fix(FN-3631): enable deletion of payments against fees below tolerance

Introduction :pencil2:
Bug description: If a fee has reported payments less than the tolerance then once a payment was added, an error was being thrown when trying to delete the payment, since there was a check for matching that was not updated when tolerance's were introduced.
This PR fixes this by removing the check and always setting the status of a fee to TO_DO if it has no payments after a payment deletion.
Resolution :heavy_check_mark:

Remove incorrect check for error state that is actually a valid state in the system.

Nice work - can we add an E2E test please to make sure the functionality works as expected?

@ttbarnes I considered adding an e2e-test but this is an really niche edge case and the unit tests provide good coverage so I don't think it warrants it.

I think it's definitely warranted - it's a feature / user journey that a user should be able to complete? Additionally, there was a bug that prevented a user from doing this. Unit tests are great, but it doesn't cover the real world user journey


text:
Dropping git from UMSWC curriculum

From Bennet Fauber's Email:

I would even consider, possibly dropping Git from the core workshop
(yes, we'd have to stop calling it SWC) to make room for the capstone
project and/or more on automation and workflow, and offering the Git
workshop as an optional follow-on topic.  At least, I'd like to hear
or see what people think about that idea.
Git is a huge cognitive load, and I think many of our participants
have neither the code base nor the experience base to make Git and
version control seem compelling.  I wonder whether it wouldn't be
better to mention it, encourage people to come back for it, but to
concentrate on the skills and tools so they can better create
something that will be worth keeping track of in Git?

Is the SWC branding a strong reason to keep Git in the curriculum?  Are there some workshops where Git makes more sense than others?  How would we provide additional Git lessons for interested students?
(Personally, I'm strongly against dropping Git from the curriculum.)

I think git should stay in the core workshop curriculum. Understanding the fundamentals of version control is an important core competency in scientific computing. It is the computational equivalent of the lab notebook. Greg's paper gives a great argument of why we need git http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1004668

I'd +1000 leaving it in. I think git comes off as a huge cognitive load when...

Mixing it with other content like bash, R, or python scripting
Going to far at once. I personally think that most people get hung up at resolving conflicts, which if they're working alone on a single computer (>90% of use cases for beginners), they won't have to worry about

I also think it's important to keep git in the core lesson to introduce the idea to people early before they know enough programming to be dangerous without version control. My suggestion would be to spend an hour talking conceptually about version control before diving into any software. Then i would suggest either practicing git through the RStudio GUI if it's an R workshop, or using something like git kraken (by far the best Git GUI out there).
On a related note, I think we need to start partitioning workshops into truly beginner workshops and ones that are beginner/intermediate for those who have at least some grasp of the command line but aren't familiar with the specific software tools that SWC teaches.
I would also be in favor of more short-length workshops covering a single topic like git (either a 4 hour or 1 day workshop). There are probably a ton of people who want to learn that specific skill, that don't also want to attend a beginner shell or python/R lesson or can't afford to take 2 whole days off of work. This also takes a huge load off of the instructors because it's a much lower commitment in terms of teaching and scheduling.

One reason I brought this up is that we can extend the amount of time we do things, if we choose.  Regular SWC is seriously constrained by what can be fit into two days.  Should we be?
For some kinds of computing, and at some level of programming, Git may be like a lab notebook.  But it's one heck of lot more complicated than a lab notebook, and there are lots of things that would go into a lab notebook that would never make it into Git and vice versa.  Let us not be too slavish with our analogies, which are, after all, ju...  umm, analogies.  ;-)
I agree completely that Git is a great tool, and that it has a place in a well-rounded scientific programming environment.  I'm only questioning whether we are introducing it in the right place, teaching people the right things to do with it, and integrating its introduction into what preceded it.
So, for example, show them git after we've shown them how to write an R program that is integrated into a workflow, and then go back over the steps taken to create that workflow showing where, how, and why git could/should be used along the way.
The complexities of Git take up a lot of bandwidth on the main SWC mailing list.  Repeatedly.  There's a reason for that.
I was mostly done with this comment when Pat chimed in above, but I've had some similar thoughts as those.  My main point, here, is to make explicit the proposition that putting Git where it is and how it currently is introduced and taught detracts not only from the understanding of Git but also from the understanding of the other material.
I don't want to throw it out, but I do want to find a way to make it less of a burden and to make it's purpose more appealing and convincing.  I don't think we're doing that under the current configuration as well as we might.

Agh, sorry, comments got insterspersed and I meant to agree with both Pat and Michelle.  Git's a problem as is, I think, and I think it would be good to toss around some possibly radical ideas about how to deal with it.  Maybe just refocusing what's provided is enough, as Pat suggests.  Personally, I like to start from what I want the participant to be able to do at the end, then work backward to all the things that would be needed to do that.  Maybe that would be a fruitful topic?
Many discussions of Git seem to get confounded because there is git, git with other people, git with github, etc.  If we really could just make it git for one, just saying so might clear enough time and focus the topic enough to make presenting git for one more coherent to the beginner who knoweth no git?

I would add to my comment that by stopping short of conflicts in a workshop I taught in March people were generally very excited to use git and didn't have the headaches that I hear about elsewhere. Usually these headaches come up from going to far or doing too much. If anything, headaches came in when trying to figure out how to interface git with RStudio. If you notice the problems that people are having with git, they are usually when people go to special edge cases or advanced topics.
Ultimately, the benefit of working with SWC/DC is that we have the benefit of working with materials that have been thoroughly peer and field reviewed. No, the materials are not perfect, but I think it's a step too far to think that we can do better on our own without first entering into the broader discussion with others in SWC/DC.

I hope I'm not suggesting abandoning SWC.  If anything, I'm only suggesting that the materials SWC/DC provide, and that many seem to agree cover too much, be trimmed and shaped to our environment in a systematic and thoughtful way, just as you did.
More of that.

I'm going to meander around to saying I support leaving git in, but it's going to take me three wordy paragraphs... 😀
I don't think the git training in SWC is terribly good, convincing, or effective.  I don't think anyone encountering git or source control in general for the first time in SWC is going to think it's something they need, that's relevant to them, or even useful.  I think very few people whose sole exposure to git is the half-day SWC lesson will start using it.  Honestly I don't think that's fixable without making it the sole topic for multiple days, and no one wants to attend that class unless they already think it's relevant to their work.
The best we can hope for in a half-day git training for folks with no source control experience is for learners to leave thinking:

"If someday I have a problem that requires keeping old versions of code around, source control would be the solution." (They have that problem now, but you can't convince people of that -- just like you can't convince them to backup their laptop until the first time they almost lose data.)
"If I hear a project or group is using git I know what it is, and I'm not intimidated about joining."
"If git makes me want to snap my laptop over my leg it's not my fault -- it's git's -- , but I know where to ask for help."

Those three are way short of the lesson's goals, but that's okay.  It still leaves people better off than they started, as long as we avoid intimidating them or turning them off with the really hairy parts of git usage.  As long as people come out knowing where to turn when someday they go, "oh, crap, I don't know what the script looked like when I did that run! I need a system in place to keep track of this," it's worth the half day.

Seems like this debate has been resolved de facto.  Feel free to re-open, if not.

authors: Ry4an bsmith89 jestill justbennet michberr pschloss

repo: UMSWC/Administration


text:
🛑 Pitchi is down

In 2bcfef5, Pitchi ($PITSCHI_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pitchi is back up in 60607a2.

repo: UQ-RCC/portals


text:
Discord Rich Presence Mac OS Issues

Description
A clear and concise description of what the bug is.
How To Reproduce
Steps to reproduce the behaviour:

Using an Apple Silicon attempt to build the game
An error should occur.

Expected Behaviour
A clear and concise description of what you expected to happen.
No error should occur for Apple Silicon
Screenshots
If applicable, add screenshots to help explain your problem.
Additional Context
Add any other context about the problem here.
Temporary Fix
Describe any known workaround for the problem.

Temporary fix implemented, longer term solution not feasible. For Apple Silicion Users, Discord Activity will not be displayed.


text:
[Team 9] Add key press to test the spawn of bosses

Description
Added a key press used for spawning each boss (temporary used for testing, as currently spawning the bosses require you to complete quests):

Press 1: Spawn land boss
Press 2: Spawn water boss
Press 3: Spawn air boss

Type of change

New feature (non-breaking change which adds functionality)
Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Passed the unit tests
Checklist:

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

looks good


text:
Bug: Import issues for MP records that begin on the same date/hour

As part of performance testing, we are noticing import issues for MP records that begin on the same date/hour. The data is old and unusual, but is causing erroneous evaluation errors that do not occur in ECMPS 1.0.
Example 1: ORIS 1012, CS023, MS2, 2, 3 is generating a critical MONLOC-98-A error for unit 2 when starting from official, exporting, importing, and evaluating the monitoring plan.
There are three unit capacity records. One that begins and ends on the same date, another record also beginning on this same date (still active), and an earlier already closed out inactive record.
When the file is imported, the dates get scrambled leaving two active records which causes the evaluation error.
Example 2: ORIS 54, SCT7 is generating a critical DEFAULT-74-A error. In this case, there are two O2X default records both beginning on 12/22/2004, hour 11.
When the file is imported, the end date is dropped from one of the records leaving two active records which causes the evaluation error.
Example 3: ORIS 889, 2 similar DEFAULT-74-A issue as above. There are two CO2N default records both beginning on 6/1/2000, hour 0.
When the file is imported, the end date is dropped from one of the records leaving two active records which causes the evaluation error.
Example 4: ORIS 55496, CT-01 similar DEFAULT-74-A issues as above. There are two O2X default records both beginning on 4/1/2003, hour 0. One ends 6/30/2006 and the other ends 9/30/2012.
When the file is imported, the end date is 9/30/2012 for both records causing the evaluation error.
We need to determine and document other monitoring plan records that could also have this issue.
Check:

Methods
Analyzer Range
System
System Fuel Flow
System Component
Qualifications (and children LME, Percent, and LEE records)
Formulas
Span
Rect. Duct WAFs
Loads
Location Attributes
Supplemental MATS Methods
Unit Control
Unit Fuel
16. Monitoring Plan Comments Skip this. ECMPS 2.0 doesn't appear to use begin_date/end_date. It's using the add_date of the record so this shouldn't be an issue. Able to import and evaluate MP comments with the same begin_date without issue.
17. Stack Pipe Skip this. The Configuration Manager will handle this. I also don't see any existing duplicates in the database that would cause these issues.
18. Unit Stack Configuration Skip this. The Configuration Manager will handle this. I also don't see any existing duplicates in the database that would cause these issues.

Methods: Cholla 1 - Add SO2 method
o	Revert + import: ends original method, but created method does not appear in UI
o	Import: ends both methods (evaluation leads to PROGRAM-11-A error)
System: Cholla 1 - Add System 110
o	Import: ends both records
o	Revert + import: ends original record, but created record does not appear in UI
System Component: Cholla 1 – Add system component P02 to System 112
o	Import: ends both records
o	Revert + import: ends original record, but created record does not appear in UI
Analyzer Range: Cholla 1 – Add analyzer range for System Component DO3 (System 111)
o	Import: ends both records
o	Revert + import: ends original record, but created record does not appear in UI
System Fuel Flow: Dogwood Energy Facility CT-1 – Add fuel flow for system G10
o	Import: end date of created record is deleted
o	Revert + import: ends original record, but created record does not appear in UI
Qualifications: Seminole CT1 – Add qualification (no QPs)
o	Import: no change, but refreshing view by Save and Exit in View/Edit of created record shows both records ended
o	Revert + import: original record remains unchanged, but created record does not appear
6a. Qualifications (QPs): Seminole CT1 – Add QP only
o	Import: no change
o	Revert + import: created record does not appear
6b. Qualification LEE: Seminole 1 – Add qualification LEE
o	Import: no change
o	Revert + import: created record does not appear
6c. Qualification LME: McPherson 2 GT1 – Add qualification LME
o	Import: no change
o	Revert + import: created record does not appear
Formulas: Cholla 1 – cannot add formula with identical Formula ID; [FORMULA-18-A] - Another [Monitor Formula] record already exists with the same [formulaId,locationId].
Span (flow / non-flow): Cholla 1 – cannot add identical span; [SPAN-55-A] - Another [Monitor Span] record already exists with the same [locationId,componentTypeCode,beginDate,beginHour,spanScaleCode].
Rect. Duct WAFs: J H Campbell 1
o	Import: no change
o	Revert + import: ends original record, but created record does not appear in UI
Loads: J H Campbell 1
o	Import: no change
o	Revert + import: created record does not appear
Location Attributes: J H Campbell 1
o	Import: ends both records
o	Revert + import: ends original record, but created record does not appear in UI
Supplemental MATS Methods: Cholla 1 – Add Supplemental Method
o	Import: ends both records
o	Revert + import: ends original record, but created record does not appear in UI
Unit Control: Cholla 1 – cannot add identical Unit Control: [CONTROL-15-A] - Another [parameterCode,controlCode,installDate] record already exists with the same [unitControl].
Unit Fuel: Cholla 1 – cannot add identical Unit Fuel: duplicate key value violates unique constraint "uq_unit_fuel"

Unit capacity:
The issue is fixed. Tested using ORIS 54, SCT7
Defaults:
The issue is fixed. Tested using ORIS 54, SCT7 / ORIS 889, 2 / ORIS 55496, CT-01
Method:
Added an ended SO2 record but not showing on UI, because inactive checkbox is unclickable. We can see that inactive record exist in JSON by export data again. And no data get scrambled, which means the potential issue is fixed.
Tested using Cholla 1.
System component:
Added an ended P02 component. No data get scrambled during export and import. Evaluation will have the following error: COMPON-80-A. Potential issue is fixed.
Tested using Cholla 1.
Analyzer range:
Added an ended analyzer range. No data get scrambled during export and import.
Passed the evaluation, no error reported. Potential issue is fixed.
Tested using Cholla 1.
System fuel flow:
Added an ended system fuel flow, No data get scrambled during export and import.
Export and import did not lead to any scramble of the fuel flow records.
The evaluation have the following errors:
FUELFLW-17-A, QUAL-38-C. Potential issue is fixed.
Tested using Dogwood Energy Facility CT-1
Tested using Dogwood Energy Facility CT-1
Tested using Dogwood Energy Facility CT-1
Tested using Dogwood Energy Facility CT-1
Tested using Dogwood Energy Facility CT-1
Tested using Dogwood Energy Facility CT-1

repo: US-EPA-CAMD/easey-ui


text:
Switching to consistent constituent abbreviations

before:
table(discqw$CONSTIT)

 NO23   SSC    TN    TP
23516 20291 18638 22859

after:
discqw$CONSTIT <- droplevels(discqw$CONSTIT)

    SSC      TN      TP NO3_NO2
  20291   18638   22859   23516

Ok, looks good to me.

authors: cschroed-usgs supercasey


text:
Make season a factor

Fix order of columns in season plots by making season a factor

Merging myself b/c very minor edit to plots

repo: USGS-R/lake-temperature-process-models


text:
project and translate sites

I left the final sites output as a remake object, could save it to disk if we want

Oops, Lindsay was much more thorough than I was. 2nd PR?

Fixed in #43!

authors: aappling-usgs lindsaycarr wdwatkins

repo: USGS-VIZLAB/gage-conditions-gif


text:
make accessible to screen readers

[ ] provide alt text that includes the actual data shown
[x] alt text for each of the images
[ ] read the screen readers section of this notebook for additional suggestions https://observablehq.com/@9a849ed5a351d187/adventures-in-d3-accessibility

Looks like this has largely been addressed with
Adding notes from the PR:

[ ] Get the focus to switch to the Dialog when it is open, so that the user can use keyboard navigation within the dialog.
See: Definitely important for accessibility, per Getting started with Vue accessibility article
See: Briefly explored a few things per this, this, and this, but they didn't work and I didn't dig further b/c I wanted to get the other changes up. I think the key is the 'ref' piece and triggering focus when the dialog is opened.
[ ] Test and make modifications, as needed. Unclear how the d3 titles will be handled.

repo: USGS-VIZLAB/pools-and-fluxes


text:
📃:

:red_circle: Tree :
:red_circle: To implement Binary trees :
:red_circle: **We can add tree traversals ** :
Screenshots 📷
<N/A >

:white_check_mark: To be Mentioned while taking the issue :

Full name :  Chiluka Akshitha
What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.)
~GSSOC ,Hacktoberfest

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@AKSHITHA-CHILUKA please add documentation for traversal techniques too. And tell me what all tree you are gonna cover in this issue? Only basic tree or any other like BST, AVL or something like that.
All the best

Algorithms_and_Data_Structures/
├── Trees/
│   ├── Menu_Driven_Code_for_Binary_Tree.py
│   ├── Menu_Driven_Code_for_Binary_Search_Tree.py
│   ├── Menu_Driven_Code_for_Avl_Tree.py
│   ├── Menu_Driven_Code_for_Tree_Traversals.py
│   ├── Menu_Driven_Code_for_DFS.py
│   ├── Menu_Driven_Code_for_Inorder_Traversal.py
│   ├── Menu_Driven_Code_for_Preorder_Traversal.py
│   ├── Menu_Driven_Code_for_Postorder_Traversal.py
│   ├── README.md

Shall I start working?

Shall I start working?

Yeah sure


text:
Update README to prevent future issues

Does this make sense here? Will this minimize issues in the future? The lack of a manager role seems to be the problem I was having.

:+1:

I do have the manager role listed in mine, and mine works; news to me that it was required, but at the least not gonna hurt anything; :+1: .

authors: apetro jhanstra timlevett

repo: UW-Madison-DoIT/angularjs-portal


text:
Improve README (DARPA feedbacks)

From @davenquinn

UW-xDD/text2graph_llm: A tool to transform textual data into structured graph representations, using LLMs to identify and extract relationships between locations and geological entities from text. <-- Typo in README. Should be "pip install pre-commit" not "pip install per-commit"; Maybe give a basic example in the README for how to run the tool

[x] Fix typo
[x] Add quick start

addressed in #37


text:
daemon在同步数据时报错，程序关闭

2018-05-16 13:40:46 ERROR: CheckProofOfWork(): nBits below minimum work
2018-05-16 13:40:46 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=1737424)
重启后又报了类似错误
2018-05-16 18:38:21 ERROR: CheckProofOfWork(): nBits below minimum work
2018-05-16 18:38:21 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=1826978)

first u have to checkout the hash of the first block  is same as ours.
then our main net is not online,please use test net right now.
thanks!

because your block of proofwork is below our limited value .

if u have block  in  last  version ， please  delete old blocks;

authors: AlfredZKY bicliu lialvin thor830428

repo: UlordChain/UlordChain


text:
Cura 9595 m4 conan v2

@casperlamboo this is the correct m4 branch.
See corresponding CCI PR
https://github.com/conan-io/conan-center-index/pull/12892
Specify library name and version:  lib/1.0
This is also a good place to share with all of us why you are submitting this PR (specially if it is a new addition to ConanCenter): is it a dependency of other libraries you want to package? Are you the author of the library? Thanks!

[ ] I've read the guidelines for contributing.
[ ] I've followed the PEP8 style guides for Python code in the recipes.
[ ] I've used the latest Conan client version.
[ ] I've tried at least one configuration locally with the conan-center hook activated.

Another PR for Conan 2.0 seemed to already have been merged upstream. Closing this PR in favor of conan-io/conan-center-index#13135

repo: Ultimaker/conan-center-index


text:
Update Decimal.php

Fix: PHP Fatal error: Cannot use 'Int' as class name as it is reserved in /app/code/Umc/Base/Model/Core/Attribute/Type/Int.php on line 20

Same as here: https://github.com/UltimateModuleCreator/Umc_Base/pull/27#issuecomment-249876123

authors: UltimateModuleCreator mozgbrasil


text:
🛑 Solagro is down

In d57af77, Solagro (https://solagro.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Solagro is back up in 5990225 after 6 minutes.

repo: UnSeulT/upptime


text:
Unable to import template

Hi!
I'm trying to import your template to my zabbix server and get following error:
Cannot find graph "Disk space usage {#FSNAME} - history" used in screen "System performance - plus".

Graph prototype linked to parent template is not included in the export file. That is removed from this template for now, as I cannot find suitable idea to deal with it. Sorry for late reply and your inconvenience.

ok, thanks. I solve this issue same manner.


text:
getting nicknames from accounts

I trying to do simple script to grab Steam nickname of current account, but even with it I'm failing.
Works good in my idler script
	bot.on("accountInfo", function(name) {
		console.log("Your Online Name: " + name);
	});

but this doesn't work,
var BotManager = require('node-steam-bot-manager');

function myNick() {
    var botsManager = new BotManager();

    botsManager.on("accountInfo", function(name) {
		botsManager.infoDebug(botAccount.getAccountName()+ ": your nickname ->" + name);
    });
    botsManager.infoDebug("Starting...");
    botsManager.startManager(function (err) {
        if (err)
            botsManager.errorDebug("Failed to start.");
    });
}

new myNick();

module.exports = myNick;

I found this: https://github.com/DoctorMcKay/node-steam-user#accountinfo
but I don't really get it, where I should put this to grab current nickname?

You can call getDisplayName() on the botAccount object you get from a loggedIn event...
Try to listen to 'loggedIn' and fetch the botAccount from the callback.
Such as below:
    botsManager.on("loggedIn", function(botAccount) {
		botsManager.infoDebug(botAccount.getAccountName()+ ": your nickname ->" + name);
    });

I will be updating the library now to include node-steam-user functionality and also further fixes.

should I change only these line above?
Getting something like that:
https://i.imgur.com/3o0MSKm.png
getDisplayName() showing name between [ ] in menu of bot? if yes, I have everywhere undefined

I don't believe I use the accountInfo event in my code though. So that is what It is better to just call botAccount.getDisplayName() just as I sent earlier.

fixed, thanks!

authors: Undeadkillz nextTOPMODEL

repo: Undeadkillz/node-steam-bot-manager


text:
CinematicView not accepted as View by Configurator

Prevents Lua script from saving

This was fixed in #443

authors: gralkapk straubar

repo: UniStuttgart-VISUS/megamol


text:
No Package GEOS available

I am installing Unidata AWIPS 17.1 on CentOS 7 using the install script and am met with 2 issues. The first is the installation of netcdf 4.1.2, which is easily remedied by downloading the primary and devel rpms. The other issue is a missing package called GEOS.
---> Package xz-devel.x86_64 0:5.2.2-1.el7 will be installed
---> Package zlib-devel.x86_64 0:1.2.7-17.el7 will be installed
--> Running transaction check
---> Package awips2-postgresql.x86_64 0:9.5.8-1.el7.centos will be installed
--> Processing Dependency: geos for package: awips2-postgresql-9.5.8-1.el7.centos.x86_64
---> Package nss-softokn-freebl.i686 0:3.28.3-8.el7_4 will be installed
--> Finished Dependency Resolution
Error: Package: awips2-postgresql-9.5.8-1.el7.centos.x86_64 (awips2repo)
           Requires: geos
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

This issue was resolved by downloading/installing the package geos-3.4.2-2.el7.x86_64.rpm.